Oracle Database 12c Error Messages

Oracle Database
Error Messages
12c Release 1 (12.1)
E49325-10
September 2016
Oracle Database Error Messages, 12c Release 1 (12.1)

E49325-10
Copyright 1996, 2016, Oracle and/or its affiliates. All rights reserved.
Primary Author: Rhonda Day
This software and related documentation are provided under a license agreement containing restrictions on
use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your
license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license,
transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse
engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is
prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If
you find any errors, please report them to us in writing.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on
behalf of the U.S. Government, the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software,
any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are
"commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agencyspecific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the
programs, including any operating system, integrated software, any programs installed on the hardware,
and/or documentation, shall be subject to license terms and license restrictions applicable to the programs.
No other rights are granted to the U.S. Government.
This software or hardware is developed for general use in a variety of information management applications.
It is not developed or intended for use in any inherently dangerous applications, including applications that
may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you
shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its
safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this
software or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of
their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are
used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron,
the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro
Devices. UNIX is a registered trademark of The Open Group.
This software or hardware and documentation may provide access to or information about content, products,
and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly
disclaim all warranties of any kind with respect to third-party content, products, and services unless
otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates
will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party
content, products, or services, except as set forth in an applicable agreement between you and Oracle.
Contents
Preface ................................................................................................................................................................ xi
Audience ....................................................................................................................................................... xi
Documentation Accessibility ..................................................................................................................... xi
Related Documents...................................................................................................................................... xi
Conventions.................................................................................................................................................. xi
Using Messages
1.1
Locating Message Documentation ................................................................................................
1-1
1.1.1
Oracle Database Messages ..................................................................................................
1-1
1.1.2
Product Specific Messages ..................................................................................................
1-1
1.1.3
Operating System-Specific Messages ................................................................................
1-1
1.2
Accuracy of Messages .....................................................................................................................
1-2
1.3
Message Format ...............................................................................................................................
1-2
1.4
Recognizing Variable Text in Messages .......................................................................................
1-2
1.5
Message Stacks .................................................................................................................................
1-2
1.6
Contacting Oracle Support Services .............................................................................................
1-3
1.7
Oracle Exception Messages ............................................................................................................
1-3
1.8
Trace Files .........................................................................................................................................
1-4
1.9
The Alert File ....................................................................................................................................
1-4
ACFS-00501 to ACFS-11111
ACFSK-00004 to ACFSK-00091
ADVM-00501 to ADVM-11111
ADVMK-00001 to ADVMK-00028
AMDU-00200 to AMDU-00503
ASMCMD-08001 to ASMCMD-09529
iii
AUD-00611 to AUD-00809
CLSCH-01001 to CLSCH-03718
10
CLSDNSSD-00000 to CLSDNSSD-03999
11
CLSGN-00000 to CLSGN-32767
12
CLSMDNS-00000 to CLSMDNS-02255
13
CLSNS-00000 to CLSNS-00035
14
CLSR-00001 to CLSR-06507
15
CLSRSC-00001 to CLSRSC-04015
16
CLSS-00001 to CLSS-03202
17
CLST-01101 to CLST-03203
18
CLSU-00100 to CLSU-00912
19
CLSW-00001 to CLSW-01000
20
CRS-00001 to CRS-29006
21
DBV-00200 to DBV-00201
22
DGM-16900 to DGM-17032
23
DIA-48001 to DIA-51705
24
DRG-10000 to DRG-52403
25
EVM-00001 to EVM-00901
26
EXP-00000 to EXP-00114
27
GIPC-00000 to GIPC-00020
28
IMG-00001 to IMG-02014
iv
29
IMP-00000 to IMP-00402
30
JMS-00101 to JMS-00256
31
JMS-00400 to JMS-00448
32
KFED-00400 to KFED-00403
33
KFNDG-00200 to KFNDG-00701
34
KFOD-00316 to KFOD-00403
35
KUP-00552 to KUP-11602
36
LCD-00100 to LCD-00219
37
LFI-00002 to LFI-01525
38
LPX-00000 to LPX-01160
39
LRM-00100 to LRM-00123
40
LSX-00001 to LSX-00345
41
MGTCA-01001 to MGTCA-01117
42
NCR-00001 to NCR-04028
43
NID-00001 to NID-00604
44
NDFN-00020 to NDFN-00025
45
NMP-00001 to NMP-00011
46
NNC-00001 to NNC-00501
47
NNF-00001 to NNF-04009
48
NNL-00001 to NNL-01078
49
NNO-00050 to NNO-00854
50
NPL-00100 to NPL-00420
51
NZE-28750 to NZE-29249
52
NZE-43000 to NZE-43021
53
O2F-00301 to O2F-00341
54
O2I-00101 to O2I-00133
55
O2U-00200 to O2U-00212
56
OCI-00601 to OCI-31199
57
OKSK-00000 to OKSK-00029
58
ORA-00000 to ORA-00877
59
ORA-00900 to ORA-01499
60
ORA-01500 to ORA-02098
61
ORA-02100 to ORA-04099
62
ORA-04930 to ORA-07499
63
ORA-07500 to ORA-09859
64
ORA-09870 to ORA-12100
65
ORA-12150 to ORA-12236
66
ORA-12315 to ORA-12354
67
ORA-12400 to ORA-12498
68
ORA-12500 to ORA-12699
69
ORA-12700 to ORA-19400
70
ORA-19500 to ORA-19997
vi
71
ORA-19999 to ORA-24279
72
ORA-24280 to ORA-28709
73
ORA-29250 to ORA-32799
74
ORA-32800 to ORA-32857
75
ORA-33000 to ORA-37999
76
ORA-38001 to ORA-39965
77
ORA-40001 to ORA-40570
78
ORA-41001 to ORA-42804
79
ORA-43750 to ORA-45907
80
ORA-46000 to ORA-46900
81
ORA-47000 to ORA-47999
82
ORA-48001 to ORA-51705
83
ORA-53000 to ORA-54047
84
ORA-54500 to ORA-56974
85
ORA-57000 to ORA-57000
86
ORA-60001 to ORA-65535
87
PCC-02010 to PCC-02474
88
PGA-20900 to PGA-22014
89
PGU-00100 to PGU-50101
90
PLS-00001 to PLS-01918
91
PLW-05000 to PLW-07206
vii
92
PRCA-01000 to PRCA-01126
93
PRCC-01000 to PRCC-01110
94
PRCD-01000 to PRCD-01324
95
PRCF-01001 to PRCF-02030
96
PRCG-01000 to PRCG-01132
97
PRCH-01000 to PRCH-01061
98
PRCI-01000 to PRCI-01168
99
PRCN-02018 to PRCN-03087
100
PRCO-00001 to PRCO-00019
101
PRCR-01000 to PRCR-01194
102
PRCS-01000 to PRCS-01118
103
PRCT-01000 to PRCT-01454
104
PRCW-01001 to PRCW-01017
105
PRCZ-01000 to PRCZ-02051
106
PRGH-01001 to PRGH-01018
107
PRGO-01003 to PRGO-11371
108
PRGR-00100 to PRGR-00133
109
PRIF-00001 to PRIF-00053
110
PRKA-02001 to PRKA-02005
111
PRKC-01000 to PRKC-01177
112
PRKE-01008 to PRKE-01011
viii
113
PRKF-01000 to PRKF-01258
114
PRKH-01014 to PRKH-03450
115
PRKN-01031 to PRKN-01041
116
PRKO-00371 to PRKO-09088
117
PRKP-01000 to PRKP-01088
118
PRKR-01001 to PRKR-01082
119
PRKU-01001 to PRKU-01060
120
PRKZ-01029 to PRKZ-01085
121
PROCL-00001 to PROCL-00110
122
PROC-00001 to PROC-00110
123
PROTL-00001 to PROTL-00604
124
PROT-00001 to PROT-00606
125
PRVE-00004 to PRVE-10168
126
PRVF-00001 to PRVF-10409
127
PRVG-00219 to PRVG-12887
128
PRVP-01041 to PRVP-03563
129
QSM-00501 to QSM-03287
130
RDE-00000 to RDE-08001
131
RDJ-00001 to RDJ-00136
132
RMAN-00201 to RMAN-20514
133
SCLC-01000 to SCLC-01037
ix
134
SCLS-01000 to SCLS-01005
135
SQL-01075 to SQL-02159
136
TNS-00000 to TNS-12699
137
UDE-00001 to UDE-00054
138
UDI-00001 to UDI-00054
139
SQL*Loader-00100 to SQL*Loader-03120
140
VID-00611 to VID-00721
141
WLMD-02005 to WLMD-02019
142
WLMF-03002 to WLMF-03025
143
WLMV-08000 to WLMV-08000
144
XOQ-00101 to XOQ-02560
145
INS-00001 to INS-30000
146
INS-30001 to INS-35000
147
INS-35001 to INS-40000
148
INS-40001 to INS-45000
Preface
This manual describes error messages that may appear while using products that are
part of Oracle Database. Each message listing in the manual contains the message
statement, an explanation of the probable causes of the message, and a recommended
action. If the message is a warning or indicates that an error occurred, then the
message listing indicates a corrective action.
Audience
Oracle Database Error Messages is intended for all Oracle Database users.
Documentation Accessibility
For information about Oracle's commitment to accessibility, visit the Oracle
Accessibility Program website at http://www.oracle.com/pls/topic/lookup?
ctx=acc&id=docacc.
Access to Oracle Support
Oracle customers that have purchased support have access to electronic support
through My Oracle Support. For information, visit http://www.oracle.com/pls/
topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?
ctx=acc&id=trs if you are hearing impaired.
Related Documents
For more information, see the documentation that ships with this release of Oracle
Database.
For information specific to Oracle Database working on your host operating system,
see your operating system-specific Oracle documentation (specific book titles vary by
operating system) and system release bulletins, if available.
Oracle error message documentation is only available in HTML. If you only have
access to the Oracle Documentation CD, you can browse the error messages by range.
Once you find the specific range, use your browser's "find in page" feature to locate
the specific message. When connected to the Internet, you can search for a specific
error message using the error message search feature of the Oracle online
documentation.
Conventions
The following text conventions are used in this document:
xi
xii
Convention
Meaning
boldface
Boldface type indicates graphical user interface elements associated

with an action, or terms defined in text or the glossary.
italic
Italic type indicates book titles, emphasis, or placeholder variables for

which you supply particular values.
monospace
Monospace type indicates commands within a paragraph, URLs, code

in examples, text that appears on the screen, or text that you enter.
1
Using Messages
This chapter gives you general information and helpful tips about error messages. This
chapter covers the following topics:
Locating Message Documentation (page 1-1)
Accuracy of Messages (page 1-2)
Message Format (page 1-2)
Recognizing Variable Text in Messages (page 1-2)
Message Stacks (page 1-2)
Contacting Oracle Support Services (page 1-3)
Oracle Exception Messages (page 1-3)
Trace Files (page 1-4)
The Alert File (page 1-4)
1.1 Locating Message Documentation

This section describes how to locate message documentation when given an error
message.
1.1.1 Oracle Database Messages

These messages are generated by Oracle Database when running any Oracle program.
This manual documents messages that are common across Oracle products and tools.
1.1.2 Product Specific Messages

These messages are specific to one product and are documented in manuals for that
product.
1.1.3 Operating System-Specific Messages

These messages are specific to one operating system. A range of message code
numbers are reserved for each operating system. For example, the range ORA-07500 to
ORA-07999 is reserved for DEC VAX/VMS messages; these messages are listed in the
appropriate operating system-specific documentation.
The prefix of the message indicates where to find information about the message. For
example, some messages in this manual have the prefix "ORA". If you encounter a
message without a prefix, first check the manuals for the release of Oracle you are
using, then check this manual.
Using Messages 1-1
Accuracy of Messages
1.2 Accuracy of Messages

The accuracy of the messages in this manual is our primary concern. Occasionally, an
enhancement to a message is not incorporated into the Oracle software. Should you
encounter a message generated on your system that differs from the message in this
book, be assured the improved message text is usually incorporated in the next release
of the software.
1.3 Message Format

All messages displayed are prefixed by text that indicates which component issued the
message. For example, the prefix "ORA" shows that the message was generated by
Oracle Database. The location of messages in this book depends on the prefix of the
message.
All messages are listed in order by the message code number. To look up a message,
use the message code number.
1.4 Recognizing Variable Text in Messages

To help you find and fix errors, Oracle embeds object names, numbers, and character
strings in some messages. These embedded variables are represented by string,
number, or character, as appropriate. For example:
ORA-00020: maximum number of processes (number) exceeded
The preceding message might actually appear as follows:

ORA-00020: maximum number of processes (50) exceeded
1.5 Message Stacks

Occasionally, you may see a message stack. This is simply a series of related messages
issued at different levels of Oracle Database.
The following message stack is a generic example:
ORA-06502: PL/SQL: numeric or value error
ORA-06512: at "SCOTT.VALUE_ERR", line 1
ORA-06512: at line 1
The following message stack is a VAX/VMS example:

ORA-01034: Oracle not available
ORA-07625: smsget: $MGBLSC failure
%SYSTEM-W-NOSUCHSEC, no such (global) section
In this example, notice that the message at the bottom of the stack is issued by the
VMS operating system. Seeing the messages at each level in the system may help you
trace the originating event. For example, in this case, Oracle may not be available
simply because it has not been started, and consequently there is no system global area
(SGA). If you need the help of Oracle Support Services, then be sure to report all the
messages in the stack.
1-2 Error Messages
Contacting Oracle Support Services
1.6 Contacting Oracle Support Services

Some messages recommend contacting Oracle Support Services to report a problem.
When you contact Oracle Support Services, please have the following information
available:
The hardware, operating system, and release number of the operating system on
which Oracle Database is running
The complete release number of Oracle Database (for example, release 9.2.0.1.0 or
release 9.0.1.1.2)
All Oracle programs (with version numbers) in use when the error occurred. For
example, SQL*Net V2.0 or SQL*Forms V3.0
If you encountered one or more error codes or messages, then the exact code
numbers and message text, in the order they appeared
The problem severity, according to the following codes:
1 = Program not usable. Critical impact on operations.
2 = Program usable. Operations severely restricted.
3 = Program usable with limited functions. Not critical to overall operations.
4 = Problem circumvented by customer. Minimal effect, if any, on operations.
You will also be expected to provide the following:
Your name
The name of your organization
Your Oracle Support ID Number
Your telephone number
1.7 Oracle Exception Messages

Oracle's extensive self-checking helps detect internal errors. Oracle uses the following
catchall message for Oracle internal exceptions:
ORA-00600: internal error code, arguments: [number], [number], [], [], [], []
An actual message might appear as follows:

ORA-00600: internal error code, arguments: [1042], [3], [upilam], [], [], []
The message text can be followed by up to six arguments, which indicate the origin
and attributes of the error. The first argument is the internal error number. Other
arguments are various numbers, names, and character strings. Empty brackets may be
ignored.
In addition to being returned to the user, internal errors are also written to the Alert
file along with additional information about the event causing the message. The Alert
file also lists any trace files that may have been generated because of an internal error.
See the following sections for descriptions of the trace and alert files.
If you receive an ORA-00600 message, report it to Oracle Support Services.
Using Messages 1-3
Trace Files
1.8 Trace Files

A trace file is created each time an Oracle instance starts or an unexpected event
occurs in a user process or background process. The name of the trace file includes the
instance name, the process name, and the Oracle process number. The file extension or
file type is usually TRC, and, if different, is noted in your operating system-specific
Oracle documentation. The contents of the trace file may include dumps of the system
global area, process global area, supervisor stack, and registers.
Two initialization parameters are used to specify the location of the trace files.
The BACKGROUND_DUMP_DEST initialization parameter specifies the location of
trace files created by the Oracle background processes PMON, DBWR, LGWR, and
SMON.
The USER_DUMP_DEST initialization parameter specifies the location of trace files
created by user processes such as SQL*Loader or Pro*C.
The Alert file also describes the location of trace files generated when internal errors
occur. See the next section for a description of the Alert file.
You may need to format the trace file before using it to diagnose problems. To format
a trace file, use the DUMPFMT utility, which is available on most systems and is
described in your operating system-specific Oracle documentation. Oracle Support
Services may ask you for a formatted trace file to help solve a problem.
See Also:
Oracle Database Administrator's Guide for more information about trace files
1.9 The Alert File

The Alert file is a log file that records information about internal errors and
administrative activities, such as backups. When an internal error occurs, the message
is sent to the terminal screen as well as written to the Alert file. Oracle also writes
additional information about internal errors to the Alert file, such as the location and
name of any trace files generated because of the error.
The name of the Alert file is operating system-specific. The location of the Alert file is
the same as the location of the background process trace files. This location is specified
by the BACKGROUND_DUMP_DEST initialization parameter. For more information, see
your Oracle operating system-specific documentation.
If your system uses an operator's console, some messages from Oracle may appear on
the console. All important messages are written to the Alert file as well as the
operator's console. Because non-Oracle messages also appear on this console, the Alert
file is a better record for tracing all Oracle administrative activity and errors than the
console log.
The Alert file also records information about administrative activities, such as backups
and archiving online redo log files.
See Also:
Oracle Database Administrator's Guide for more information about the Alert file
1-4 Error Messages
2
ACFS-00501 to ACFS-11111
ACFS-00501: unable to allocate a buffer
Cause: A request for process virtual memory failed. This message is accompanied by
other message(s) providing details on the error.
Action: Correct the problem indicated by the other message(s). If possible, change
options to reduce required memory and/or take steps to increase memory available
to the process. Otherwise, report this error to Oracle Support Services.
ACFS-00502: Failed to communicate with the ACFS driver. Verify the ACFS driver
has been loaded.
Cause: The ACFS control device could not be accessed.
Action: Verify the ACFS driver is loaded and running.
ACFS-00506: Failed to read 'string'.
Cause: An open file could not be read.
Action: The most likely cause is a file permission problem.
ACFS-00507: Failed to seek to string prior to writing the volume disk header.
Cause: A seek to the volume failed. This message is accompanied by other message(s)
providing details on the error.
Action: Correct the problem indicated by the other message(s). If the solution is not
clear, contact Oracle Support Services.
ACFS-00508: unable to obtain device major and minor number for volume string
Cause: Failed to obtain volume information. This message is accompanied by other
message(s) providing details on the error.
ACFS-00509: unsupported file type for string, not a block device
Cause: Volume provided was not recognized as a block device. This message is
accompanied by other message(s) providing details on the error.
ACFS-00510: unable to obtain volume id for string
Cause: Volume id was not obtained. This message is accompanied by other
ACFS-00501 to ACFS-11111 2-1
ACFS-00514: unable to close handle

Cause: Handle could not be closed. This message is accompanied by other message(s)
ACFS-00516: stat of string failed
Cause: Stat() failed. This message is accompanied by other message(s) providing
details on the error.
ACFS-00517: unable to obtain block device sector size
ACFS-00518: unable to obtain volume size in sectors
ACFS-00521: Failed to determine file type of string.
ACFS-00522: unable to get drive structure
ACFS-00524: unable to obtain partition information
ACFS-00525: failed to seek to string
Cause: Failed to seek to volume. This message is accompanied by other message(s)
ACFS-00526: read of volume disk header failed
Cause: Failed to read volume. This message is accompanied by other message(s)
2-2 Error Messages
ACFS-00527: unable to dismount volume
Cause: Could not dismount volume. This message is accompanied by other
ACFS-00531: write of volume disk header failed
Cause: Write to volume failed. This message is accompanied by other message(s)
ACFS-00547: Both the primary and alternate superblocks are damaged.
Cause: The file system metadata was found to be damaged.
Action: Run fsck (Unix or Linux) or acfschkdsk.exe (Windows) as soon as possible to
fix the metadata inconsistency.
ACFS-00548: Failed to communicate with the ACFS driver. Verify that cluster
membership has been established.
Cause: The ACFS driver's control device could not be accessed.
Action: Verify the driver is loaded and running. Also, verify that the ASM instance is
accessible.
ACFS-00549: mount path string already contains a volume mount point for volume
string
Cause: The mount path contained a reparse point that references a a different volume
than the mount request.
Action: Verify the path is correct. If it is, the existing volume mount point must be
removed before a new one can be created. Use acfsdismount to remove the mount
point.
ACFS-00555: unsupported file type for string, not a device file
Cause: Volume provided was not recognized as a device file. This message is
ACFS-00556: invalid vfs name string
Cause: a helper command was called with an unexpected vfs name argument
Action: Verify that ACFS helper commands are installed in the '/sbin/helpers/acfs'
directory and that '/etc/vfs' contains the correct information for ACFS. If the solution
is not clear, contact Oracle Support Services.
ACFS-00562: An attempt to create Oracle Registry ACFS key string resulted in a
registry error. string
Cause: An error was returned by the Oracle Registry service when attempting to
create an ACFS key. This message is accompanied by other message(s) that provide
details as to the exact cause of the failure.
ACFS-00501 to ACFS-11111 2-3
Action: Correct the problem indicated by the other message(s). If the cause of the
problem is unclear, contact Oracle Support Services.
ACFS-00564: unable to delete Oracle Registry key string while trying to recover
from an error string
Cause: Removal of a key from the Oracle Registry failed.
Action: Run ocrcheck to verify the Oracle Registry is working properly.
ACFS-00565: unable to delete Oracle Registry key string string
Cause: Removal of mount key from Oracle Registry failed.
Action: Use acfsutil registry to verify the mount key exists in the Oracle Registry.
ACFS-00566: invalid handle received when attempting to close an ACFS mount key
within Oracle Registry
Cause: An error was returned during the closing of a key in the Oracle Registry.
Action: Run ocrcheck to verify the Oracle Registry is working properly. Report to
Oracle Support Services.
ACFS-00567: unknown Oracle Registry error encountered closing key
Cause: An error was returned while closing the key from the Oracle Registry.
ACFS-00568: closing of a key resulted in Oracle Registry error number
Action: Verify the Oracle Registry is accessible. If it is not accessible and the cause is
unclear, report this error to Oracle Support Services.
ACFS-00569: invalid handle received when attempting to delete an ACFS mount
key within Oracle Registry
Cause: An error was returned while removing a key from the Oracle Registry.
Action: Report this error to Oracle Support Services.
ACFS-00570: The ACFS mount key specified for deletion does not exist within
Oracle Registry.
Cause: The mount key could not be located in the Oracle Registry.
Action: Use acfsutil registry to ensure the mount entry exists in the Oracle Registry.
ACFS-00571: The ACFS mount key specified for deletion is not empty.
Cause: The mount key specified for deletion from the Oracle Registry contained
dependent subkeys.
Action: View the mount entries in the Oracle Registry using "acfsutil registry" and
remove any dependent mount entries before retrying this operation.
ACFS-00572: permission denied to delete the ACFS mount entry from Oracle
Registry
Cause: The user permissions were insufficient to remove the key from the Oracle
Registry.
Action: Verify the Oracle Registry is accessible and that command is being run from a
properly authorized user ID.
2-4 Error Messages
ACFS-00573: Oracle Registry error encountered while deleting an ACFS mount key
Cause: An error was returned while removing the key from the Oracle Registry.
ACFS-00575: deletion request of key resulted in Oracle Registry error number
Action: Run ocrcheck to verify that Oracle Registry is working properly. If problem
persists, report to Oracle Support Services.
ACFS-00584: failed to look up ACFS mount points in the Oracle Registry string
Cause: An error was returned while looking up a mount point in the Oracle Registry.
Action: Run ocrcheck to verify the Oracle Registry is working properly. If problem
ACFS-00585: null parameter received
Cause: A null parameter was passed to the Oracle Registry.
ACFS-00587: unknown Oracle Registry error encountered during operation on
ACFS mount entry
Cause: An error was returned while accessing the key from the Oracle Registry.
ACFS-00589: key operation resulted in Oracle Registry error number
Cause: An error was returned during a key operation with the Oracle Registry.
ACFS-00592: Seek to volume failed. Verify the volume exists.
Cause: Seek to a location on the volume failed.
Action: Verify the volume exists on this node and that it is accessible.
ACFS-00593: The Oracle Registry returned the following error while attempting to
access ACFS key string string
Cause: Failed to access either the SYSTEM, SYSTEM.ACFS or SYSTEM.ACFS.Mounts
keys in Oracle Registry.
Action: Run ocrcheck to verify the Oracle Registry is working properly. Examine the
appended error message from the Oracle Registry service.
ACFS-00594: Failed to access ACFS mount information. The Oracle Registry
returned the appended error for ACFS key string. string
Cause: Failed to access ACFS mount information from the Oracle Registry.
Action: Examine the appended error message from the Oracle Registry.
ACFS-00595: Failed to access ACFS mount value information. The Oracle Registry
Cause: Failed to access ACFS mount value information from the Oracle Registry. This
might be due to Oracle Registry corruption or a sudden loss of the Oracle Registry
service.
ACFS-00501 to ACFS-11111 2-5
Action: Examine the appended error message from the Oracle Registry. Run ocrcheck
to verify the Oracle Registry is working properly.
ACFS-00596: A failure occurred while accessing the Oracle Registry ACFS key
"SYSTEM" for security purposes and follows this message: string
Cause: Failed to retrieve key access rights for the Oracle Registry ACFS key
"SYSTEM"
Action: Run ocrcheck to verify the Oracle Registry is working properly. Evaluate the
error message returned from the Oracle Registry appended to this message. If
necessary, run ocrdump and make sure the "SYSTEM" key exists and is accessible.
ACFS-00597: Failed to initialize the Oracle Registry's SCLS context. The SCLS error
is included with this message.
Cause: An operating system initialization failed.
Action: Evaluate the attached SCLS error message. Run ocrcheck to verify the Oracle
Registry is functioning correctly.
ACFS-00598: An error occurred while looking up the current user's operating
system account name. The error is included with this message.
Cause: ACFS was attempting to add an entry to the Oracle Registry. During this
attempt a lookup of the current user's name failed in the operating system failed.
Action: Evaluate the attached error message to determine why the current user name
could not obtained from the operating system.
close the ACFS key string string
Cause: Possibly due to Oracle Registry corruption or a sudden loss of the Oracle
Registry service.
ACFS-00600: Failed to access ACFS mount subkey information. The Oracle
Registry returned the appended error. string
ACFS-00601: Failed to initialize this utility's access to the Oracle Registry. Verify
the registry service has started.
Cause: Either the Oracle Registry service was unavailable or the registry
configuration was incomplete/inaccurate.
Action: Run ocrcheck to verify the registry service is working properly.
ACFS-00602: An internal error (BADARG) occurred while trying to determine the
Oracle Registry configuration.
Cause: An Oracle internal error.
Action: Contact Oracle.
ACFS-00603: Failed to retrieve the Oracle Cluster Registry, OCR, configuration
Cause: Failed to obtain OCR information.
Action: Run ocrcheck to verify OCR is working properly.
2-6 Error Messages
ACFS-00604: Failed to retrieve the Oracle Local Registry, OLR, configuration

Cause: Failed to obtain Oracle Local Registry information.
Action: Run ocrcheck -local to verify the OLR is working properly.
ACFS-00605: Failed to retrieve the Oracle Registry configuration for an unknown
reason
Cause: Failed to obtain Oracle Registry information.
Action: Run ocrcheck to verify the registry is working properly.
ACFS-00606: Could not determine if the system is configured for RAC or Oracle
Restart environment.
Cause: The Oracle Registry service configuration could not be detected
Action: Run ocrcheck to verify the Oracle registry service.
ACFS-00607: Failed to access or create Oracle Registry keys required for ACFS
operation
Cause: Oracle Registry keys required for operation either could not be accessed or
created.
Action: Another error message number will follow this message. Analyze its output.
Run ocrcheck to verify the Oracle registry is functioning properly. Also, verify acfsutil
was invoked with administrative rights when attempting to add the ACFS mount
points.
ACFS-00619: This is a string computer, but the file system was created on a string
string computer.
Cause: The file system was created on a computer which has a different Endian than
the current system. Little Endian machines (such as the intel x86 based systems) store
the Least Significant bit in the first byte of an integer value. Big Endian machines
(such as Solaris SPARC and AIX Power based systems) store the Most Significant bit
in the first byte of an integer value.
Action: Use a system with the same Endian as the system which created the file
system.
ACFS-00620: This feature is not available for Oracle version string or lower on this
platform.
Cause: Informational.
Action: None
ACFS-00621: Unable to determine privileges
Cause: An error occured retrieving the user credentials.
Action: Verify the mount point is an ACFS mount point and it is not offline.
ACFS-00622: must provide a base mount point
Cause: A mount point on the base site was not provided.
Action: Provide an existing mount point on the base site.
ACFS-00623: must provide a target mount point
Cause: A mount point on the target site was not provided.
Action: Provide an existing mount point with an empty file system on the target site.
ACFS-00501 to ACFS-11111 2-7
ACFS-00624: The path specified is too long.

Cause: The path specified exceeded the allowed maximum path length.
Action: Verify the path was entered correctly, or use a different path.
ACFS-00625: string is not a valid ACFS mount point.
Cause: The mount point path specified was not a valid mount point.
Action: Provide a valid ACFS mount point.
ACFS-01001: Size specified cannot exceed size of volume.
Cause: Volume size was smaller than the requested size.
Action: Select a size that is less than or equal to the volume size and retry the ACFS
format command.
ACFS-01002: ACFS requires a minimum volume size of numberMB.
Cause: Volume was too small.
Action: Select a larger volume and retry.
ACFS-01004: string was not formatted.
Cause: An error occurred during the formatting of the volume.
Action: This message is accompanied by another error message. Respond as indicated
for that message."
Cause: A request for process virtual memory by the ACFS format command failed.
This message is accompanied by other message(s) providing details on the error.
ACFS-01006: unable to open volume device 'string'
Cause: Volume device could not be opened. This message is accompanied by other
ACFS-01008: unable to open file system string
Cause: File system was not accessible.
Action: Verify the volume associated with the file system is enabled and online before
retrying.
ACFS-01010: Volume already contains an ACFS file system. To reformat the
volume, reissue string with the stringf option.
Cause: The on-disk metadata indicated that an ACFS file system is located on the
volume.
Action: Verify the intended volume and reissue the format command with the force
flag to overwrite the existing ACFS file system.
ACFS-01011: Volume contains an ACFS file system that is being checked. To
reformat the volume, reissue string with the stringf option.
Cause: The volume contained a file system that was in the process of being checked
by fsck (Unix or Linux) or acfschkdsk.exe (Windows).
2-8 Error Messages
ACFS-01014: write of volume label failed
Cause: A write to the volume during file system creation failed. This message is
ACFS-01018: failed to allocate a buffer for number bytes
ACFS-01019: This volume contains a mounted ACFS file system. The file system
must be dismounted with acfsdismount on all nodes.
Cause: The volume was in use by another file system.
Action: Dismount the ACFS file system with acfsdismount and retry the command.
ACFS-01020: This volume contains a mounted non-ACFS file system. The file
system must be dismounted with 'advmutil dismount'.
Cause: The volume was in use by another non-ACFS file system.
Action: Dismount the non-ACFS file system with 'advmutil dismount' and retry the
command.
ACFS-01033: write to volume failed
ACFS-01038: write failed during setup of root directory entry
ACFS-01041: write of snaps directory entry failed
ACFS-01043: write of lost+found directory entry failed
ACFS-00501 to ACFS-11111 2-9
ACFS-01044: write of file entry table failed

ACFS-01045: write of global bitmap failed
ACFS-01046: read of global bitmap file entry failed
Cause: A read of the volume during file system creation failed. This message is
ACFS-01047: write of global bitmap file entry failed
ACFS-01049: seek to snap map header failure
Cause: A seek to the volume during file system creation failed. This message is
ACFS-01050: write to snap map header failure
ACFS-01051: partial write to snap map header failure
ACFS-01052: write to snap map info entry failure
ACFS-01053: partial write to snap map info entry failure
2-10 Error Messages
ACFS-01054: write to snap map storage entry failure
ACFS-01055: partial write to snap map storage entry failure
ACFS-01150: unable to synchronize in-memory file data to disk
Cause: A request to flush all in-memory copies of buffers associated with the open
handle failed. This message is accompanied by other message(s) providing details on
the error.
Action: Correct the problem identified by the other message(s). If the problem has
been resolved and the file system is unusable, retry the ACFS format command.
ACFS-01151: Ignoring invalid block size number, using number
Cause: An ACFS format command unsupported block size was specified.
Action: No action required. A supported block size will be used.
ACFS-01152: The length of accelerator volume name exceeds number.
Cause: Accelerator volume name length exceeded the maximum length displayed in
the message.
Action: Select an accelerator volume name with length less than or equal to the
maximum length displayed in the message and retry the command.
ACFS-01154: The accelerator volume contains a mounted ACFS file system. The file
system must be dismounted with acfsdismount on each node.
Cause: The specified volume could not be used as an accelerator volume because it
was in use by a mounted file system.
ACFS-01155: The accelerator volume contains a mounted non-ACFS file system.
The file system must be dismounted with 'advmutil dismount'.
was in use by a mounted non-ACFS file system.
command.
ACFS-01156: The Oracle ASM Dynamic Volume Manager (Oracle ADVM)
compatibility attribute for the disk group is less than 12.1.0.2.0.
Cause: An attempt to create a file system with an accelerator volume failed because
the ADVM compatibility attribute for the disk group was not set to 12.1.0.2.0 or
higher.
Action: Use the Oracle ASM Configuration Assistant (ASMCA) tool or the SQL
statement ALTER DISKGROUP to upgrade COMPATIBLE.ADVM attribute.
ACFS-00501 to ACFS-11111 2-11
ACFS-01159: The accelerator volume must be different from the volume containing
the file system.
Cause: The file system could not be created because the same volume was specified
for both the accelerator and the file system.
Action: Choose a different volume for the accelerator and retry the command.
ACFS-01160: The specified accelerator volume was smaller than numberMB.
Cause: The file system could not be created because the specified accelerator volume
was below the minimum allowed size reported in the message.
Action: Select a larger accelerator volume and retry the command.
ACFS-01164: The specified device 'string' is already in use with a CRS-managed file
system.
Cause: The file system could not be created because the specified device was already
registered with CRS (Cluster Ready Services).
Action: Select an unused device, or use srvctl to modify the association for this device
and retry the file system creation.
Cause: A request for process virtual memory by mount command failed. This
message is accompanied by other message(s) providing details on the error.
ACFS-02006: unable to terminate the Oracle Registry connection
Cause: Either the Oracle Registry service was unavailable or the Oracle Registry
Action: Run crs_stat and ocrcheck to verify CSS and the Oracle Registry are working
properly. If they are not accessible and the cause is unclear, report this error to Oracle
Support Services.
ACFS-02012: Mount of string failed, volume string does not exist. Verify that string
exists on this node.
Cause: Could not mount the file system retrieved from the Oracle Registry.
ACFS-02014: Mount of string failed. Error number was returned.
Cause: Mount operation failed.
Action: Verify the mount point and volume both exist and are accessible before
retrying the mount command.
ACFS-02015: Failed to open mount point string. Verify the mount point exists.
Cause: Mount point could not be opened.
Action: Verify the mount point exists and is accessible before retrying the mount
command.
ACFS-02017: Failed to open volume string. Verify the volume exists.
Cause: The volume could not be opened.
Action: Verify the ASM instance is operational and the volume is enabled and
accessible before retrying the mount command.
2-12 Error Messages
ACFS-02018: Volume string contains an ACFS file system that is being checked.
Allow the file system check to complete.
by the ACFS checker.
Action: Allow the ACFS checker to complete before retrying the mount. If the ACFS
checker is not running on this file system and a file system check was previously
interrupted, reissue the ACFS checker.
ACFS-02026: unable to verify the host names passed in are part of the cluster
Cause: Either CSS was unavailable or the CSS configuration was incomplete/
inaccurate.
Action: Run crs_stat to verify CSS is working properly.
ACFS-02027: unable to obtain the local CSS node name
inaccurate.
ACFS-02046: Volume string cannot be mounted. Examine the system event log for
possible causes.
Cause: The volume mount failed. This could be caused by an out of space condition if
this is the first mount of a file system on a node.
Action: Examine the system event log for more detail.
ACFS-02050: unable to set in-memory mount information
Cause: Could not communicate with the mounted file system.
accessible before retrying.
ACFS-02081: Warning: acfschkdsk.exe should be run on volume string at your
earliest convenience
Cause: A flag in the superblock indicates that a metadata inconsistency has been
found on this volume.
Action: Run acfschkdsk.exe as soon as possible to fix the metadata inconsistency.
ACFS-02082: unable to verify if the host names provided are part of the cluster
Cause: Could not obtain information about the cluster.
Action: Run crs_stat to verify health of CSS.
ACFS-02083: cannot get the local CSS node name
Cause: Could not obtain local CSS node name.
ACFS-02090: unable to retrieve ACFS mount information from CRS
Cause: Failed to retrieve mount information the CRS.
Action: Analyze the error messages that precede this message.
ACFS-02092: Mount of string failed, node string is not a member of the CSS cluster.
Action: Verify the node listed in the entry is a member of the CSS cluster.
ACFS-00501 to ACFS-11111 2-13
ACFS-02119: creating administrative network share for mount point string at share
name 'string'
Cause: Informational
Action: None
ACFS-02120: administrative network share for mount point string already exists at
share name 'string'
Action: None
ACFS-02121: administrative network share 'string' already exists, but does not share
mount point string
Cause: Attempted to create an administrative network share for the specified ACFS
mount point, but the required share name was already in use.
Action: Remove the conflicting network share using 'net share share name /delete'.
Remount the ACFS file system to retry creating an administrative network share for
the mount point.
ACFS-02122: retrieving information for administrative network share 'string' failed
Cause: While creating an administrative network share for the specified ACFS mount
point, failed to retrieve information on any network share that might already exist at
the required share name. This message is accompanied by other messages providing
Action: Correct the error indicated by the accompanying messages. Remount the
ACFS file system to retry creating an administrative network share for the mount
point.
ACFS-02123: creating administrative network share for mount point string at share
name 'string' failed
Cause: Failed to create an administrative network share for the specified ACFS mount
point. This message is accompanied by other messages providing details on the error.
point.
ACFS-02124: could not create administrative network share for mount point string
at share name 'string'
Action: Correct the error indicated by the accompanying messages.
ACFS-02125: volume 'string' is already in use
Action: Verify the volume specified.
ACFS-02126: Volume string cannot be mounted.
Cause: The volume mount failed. This message is accompanied by other messages
Action: Correct the problem indicated by the other messages and retry the mount
command.
2-14 Error Messages
ACFS-02127: unable to transfer mount data to the ACFS driver

Cause: The mount failed because the transfer of mount data from the mount
command to the ACFS driver failed. This message is accompanied by other messages
Action: Correct the problem identified by the other messages. If the cause is unclear,
contact Oracle Support Services.
ACFS-02128: unable to clean up mount data passed to ACFS driver
Cause: The operation to clean up mount data from a temporary location / failed.
Action: None. This state will not have any repercussions and it will be remedied
automatically during the next restart.
ACFS-02129: Volume string cannot be mounted. Volume is out of space.
Cause: The volume mount failed because the volume was out of space.
Action: Correct the problem by resizing the ADVM volume and then retry the mount
command.
ACFS-02130: Volume string cannot be mounted. Volume version does not match
the ACFS driver version.
Cause: The volume mount failed because the loaded ACFS driver does not support
the volume version.
Action: Use 'acfsdriverstate' command to determine the state of the ACFS driver and
address any issues that are reported. Retry the mount command after the installed
driver has been verified.
ACFS-02131: Volume string cannot be mounted. Cluster membership is not
established.
Cause: The volume mount failed because the ACFS driver could not communicate
with Oracle Clusterware.
Action: Verify the online state of Oracle Clusterware using command 'crsctl check
CRS' and address any issues that are reported. Retry the mount command once
Oracle Clusterware is fully operational.
ACFS-02132: Volume string cannot be mounted. Insufficient kernel resources to
complete the mount.
Cause: The volume mount failed due to insufficient kernel resources.
Action: Reduce the load activity on the system and retry the mount command.
ACFS-02133: Volume string cannot be mounted. Metadata inconsistency found ondisk.
Cause: The volume mount failed due to a metadata inconsistency found in the
volume superblock.
Action: Run command 'fsck -t acfs' as soon as possible to fix the metadata
inconsistency and then retry the mount command.
ACFS-03001: Failed to open string. Verify that string exists.
Cause: The mount point or file could not be opened.
Action: Verify the mount point or file is accessible before retrying.
ACFS-03003: Cannot decrease the volume by this amount.
Cause: Requested size exceeded the size of the file system.
ACFS-00501 to ACFS-11111 2-15
Action: Select a size that is smaller than the size of the file system and retry.
ACFS-03004: Cannot reduce volume size below 200 MB.
Cause: Requested size was below the minimum volume size of 200MB."
Action: Select a volume that is 200MB or larger."
ACFS-03008: The volume could not be resized. The volume expansion limit has
been reached.
Cause: The file system's internal storage bitmap has a five extent limit. Growing the
file system may fail if it has already been grown four or more times, using up all
available storage bitmap extents.
Action: If the file system has been grown four or more times, running the ACFS Fixer
may allow future volume expansions.
ACFS-03013: unable to open string
Cause: Volume could not be opened to remove the file system.
Action: Verify the volume is not mounted on any node in the cluster before retrying.
ACFS-03033: unable to open string
Cause: The log file specified could not be created and/or opened.
Action: If a file exists by the same name as the log file specified, verify that this is a
file that can be overwritten.
ACFS-03044: Failed to open mount point string. Verify the mount point exists.
Cause: Mount point could not be opened for snapshot operation.
Action: Verify the mount point exists and is accessible before retrying the snap
command.
ACFS-03052: unable to delete snapshot string due to open files
Cause: There are files open in the snapshot.
Action: Use lsof or similar tool to find the processes with open files. No files can be
open in the snapshot for the snapshot delete operation to succeed.
ACFS-03054: snapshot string is not a valid snapshot name
Cause: Possible causes include: 1) The snapshot name exceeded the limit of 255
characters. 2) The snapshot name equaled "." or "..". 3) The snapshot name contained
"/" (Unix or Linux). 4) The snapshot name contained "" or ":" (Windows). 5) The
snapshot name contained an illegal character for NTFS file names (Windows).
Action: Verify that the snapshot name meets the criteria listed in the cause statement.
ACFS-03091: Failed to open string. This may mean the string driver is not loaded/
running
Cause: The driver's control device could not be accessed.
Action: Verify the driver is loaded and running.
ACFS-03096: error opening configuration file string
Cause: The configuration file cannot be created and/or opened.
Action: If the configuration file exists, verify the file can be opened.
ACFS-03097: error accessing configuration file string
Cause: Seek to the end of the configuration file failed.
Action: If the configuration file exists, verify the file is accessible.
2-16 Error Messages
ACFS-03106: Invalid combination of arguments. stringa was previously specified to

add an ACFS mount point to Oracle Registry.
Cause: Invalid option combination.
Action: Retry the command with one set of operations.
ACFS-03107: Invalid combination of arguments. stringd was previously specified to
remove an ACFS mount point from the Oracle Registry.
ACFS-03108: Neither string nor string is an ADVM volume.
Cause: Volume specified was not an ADVM volume.
Action: Retry the command with an ADVM volume.
ACFS-03110: unable to access the Oracle Registry string
Action: Run ocrcheck to verify the Oracle Registry is working properly. Analyze the
appended Oracle Registry service error message.
Cause: A request for process virtual memory by acfsutil registry failed This message
is accompanied by other message(s) providing details on the error.
ACFS-03115: an error occurred while attempting to disconnect from Oracle Registry
Action: Run ocrcheck to verify the Oracle Registry service is working properly. If the
cause of the problem is unclear, contact Oracle Support Services.
ACFS-03117: unable to verify if the hostnames provided are part of the cluster
ACFS-03118: cannot obtain the node number of host string via CSS or the Oracle
Registry
Cause: Could not determine the node number for the specified host.
Action: Verify that the specified host is a member of this cluster.
ACFS-03119: Incorrect data format in file 'number'.
Cause: The file data was not in the expected format.
Action: Contact Oracle Support Services.
ACFS-03120: Note: Reported snapshot space usage is inaccurate.
Cause: The snapshot storage calculated was not expected.
Action: No action is required. To get a more accurate count, dismount the file system
on all nodes and run fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ACFS-00501 to ACFS-11111 2-17
ACFS-03122: failed to create Oracle Registry ACFS key string string

Cause: Failed to create ACFS key(s) SYSTEM.ACFS and/or SYSTEM.ACFS.Mounts in
the Oracle Registry.
Action: Run ocrcheck to verify the Oracle Registry service is working properly. Verify
acfsutil is executed with operating system administrator privileges.
ACFS-03123: failed to create Oracle Registry ACFS key string because it already
exists
Cause: The Oracle Registry ACFS key already exists.
Action: Run ocrcheck to verify the Oracle Registry service is working properly.
ACFS-03124: failed to create Oracle Registry ACFS subkey because it already exists
Cause: The Oracle Registry mounts subkey already exists.
ACFS mount entry is in an inconsistent state delete it, then re-add it using acfsutil
with the registry option. If the problem persists, contact Oracle Support Services.
ACFS-03125: error retrieving the volume using Oracle Registry key: string
Cause: Could not retrieve volume information from mount entry in the Oracle
Registry.
ACFS-03126: error retrieving the mount point using Oracle Registry key: string
Cause: Could not retrieve mount point information from mount entry in the Oracle
Registry.
ACFS-03127: error retrieving the mount options using Oracle Registry key: string
Cause: Could not retrieve mount options from mount entry in the Oracle Registry.
ACFS-03128: error retrieving the version using Oracle Registry key: string
Cause: Could not retrieve the version for mount entry in the Oracle Registry.
ACFS-03129: error retrieving the nodes list using Oracle Registry key: string
Cause: Could not retrieve the nodes list for mount entry in the Oracle Registry.
access the security attributes of key string: \n string
Cause: Could not access the security information of Oracle Registry. This message is
accompanied by other message(s) from the Registry providing details on the error.
Action: Correct the problem identified by the other message(s). If the cause is unclear,
ACFS-03134: An error occurred while accessing Oracle Registry for a delete mount
point operation. string
Cause: Could not retrieve data from the Oracle Registry. This message is
2-18 Error Messages
ACFS-03135: unable to locate mount point string in Cluster Ready Services
Cause: An attempt to access the ACFS mount point failed because the mount point
information could not be retrieved from CRS.
Action: Verify the mount point is registered with CRS using the 'acfsutil registry
device' commands.
ACFS-03136: unable to locate volume string in Cluster Ready Services
Cause: An attempt to access the ASM volume failed because the volume information
could not be retrieved from CRS.
Action: Verify the volume is registered with CRS using the 'acfsutil registry device'
commands.
ACFS-03137: Multiple entries exist for the mount point string. Rerun the command
with the volume name.
Cause: Could not locate unique entry for mount point in the Oracle Registry.
Action: Retry acfsutil registry with volume name.
ACFS-03138: failed to create and set Oracle Registry ACFS mount info key string
Cause: Could not create and set a mount info key in the Oracle Registry.
ACFS-03139: error retrieving the disk group name using Oracle Registry key: string
Cause: Could not retrieve the disk group name from the mount entry in the Oracle
Registry.
ACFS-03140: error retrieving the volume name using Oracle Registry key: string
Cause: Could not retrieve the volume name from the mount entry in the Oracle
Registry.
ACFS-03141: unable to open device string
Cause: The device could not be opened.
Action: Check the diskgroup is mounted and the specified volume is enabled.
ACFS-03142: Failed to retrieve the diskgroup and volume name for device string.
See the attached error.
Cause: Possible internal error.
Action: Check the attached error. If not serviceable, contact Oracle.
ACFS-03143: The specified mount point does not exist and therefore cannot be
deleted.
Cause: The Oracle Registry has not been configured for ACFS or the specified mount
point does not exist.
Action: Run "acfsutil registry" to list out the available ACFS mount points.
ACFS-03145: unable to remove ACFS volume string from Oracle Registry
Cause: Could not remove volume from Oracle Registry.
ACFS-00501 to ACFS-11111 2-19
Action: Verify the volume exists in the Oracle Registry using the acfsutil registry
command.
ACFS-03146: Warning: The ACFS mount point group ownership cannot be reinitialized in the Oracle Registry. The registry is initialized from the ACFS control
device on first use, and may have changed ownership since then. Current Key
Ownership: string
Cause: An attempt was made to re-initialize the ACFS mount point group ownership
in the Oracle Registry. This may be because the ACFS control device /dev/ofsctl
or /dev/acfsctl has changed owners.
Action: Re-initializing the ACFS mount point group ownership in the Oracle Registry
is not supported.
ACFS-03147: invalid ACFS file identifier provided
Cause: The ACFS file identifier provided by the user had an illegal value.
Action: Re-enter a number other than 0 or -1.
ACFS-03148: ioctl call to obtain pathname associated with file id number failed
Cause: An internal ioctl operation to map from an ACFS file identifier to a pathname
failed. This message is accompanied by other message(s) providing details on the
error.
ACFS-03149: constructed pathname is too large
Cause: The length of the pathname being constructed has exceeded the system limit
of %d characters. This may be due to changes in the file system namespace while the
command is running.
Action: Try the command again. If the problem persists, contact Oracle Support
Services.
ACFS-03151: The ACFS file identifier provided is not associated with a user file or
directory.
Cause: The ACFS file identifier, although valid, was not for a user file or directory.
Action: None. There is no pathname associated with this ACFS file identifier.
ACFS-03152: The ACFS file identifier provided is invalid for the mountpoint
specified.
Cause: The ACFS file identifier was not a valid identifier for the mountpoint
specified.
Action: Verify that the correct ACFS file identifier and mountpoint were specified.
ACFS-03153: The file system name space has changed and a pathname cannot be
obtained.
Cause: The ACFS file identifier was valid, but could not be used to obtain a full file
pathname.
ACFS-03154: Failed to determine the full pathname. Too many directory levels.
Cause: acfsutil has received information from the operating system that it could not
process fully.
2-20 Error Messages
ACFS-03157: unsupported file type for string, not a mount point

Cause: An invalid entry was passed on the command line.
Action: The acfsutil info acfs command requires that the input be a mount point.
ACFS-03158: unsupported file type for string, not a mount point or a file
Action: The acfsutil size command requires that the input be a mount point or a file.
ACFS-03161: Device : string : Mount Point : string already exists in the Oracle
Registry
Cause: This entry has already been added to the Oracle Registry.
Action: None
ACFS-03162: Warning: The file system was resized, but an error occurred while
resizing the ADVM volume. File system size now number MB, volume size number
MB.
Cause: An error occurred during ADVM volume resize.
Action: Reissue the resize command.
ACFS-03165: Unable to add the file system on device string to the ACFS registry. It
is currently managed by CRS.
Cause: The file system is currently managed by CRS and a file system cannot be
managed by both CRS and the ACFS registry.
Action: Remove the file system resource from CRS or continue to use CRS to manage
the file system.
ACFS-03166: Unable to add a STOP_DEPENDENCY to the ACFS registry for
device string.
Cause: The ACFS registry resource could not be updated.
Action: Verify the ACFS registry state ('crsctl stat res ora.registry.acfs -p')
ACFS-03167: Unable to remove the STOP_DEPENDENCY for device string from
the ACFS registry.
ACFS-03168: Internal error: string number
ACFS-03169: Unable to set log file size.
Cause: The ACFS driver was unable to set the log file size.
Action: Check the log file to see the reason of failure.
ACFS-03170: Minimum log file size is number.
Action: Log file size has to be bigger than or equal to the minimum size.
ACFS-00501 to ACFS-11111 2-21
ACFS-03171: Insufficient contiguous free ASM Diskgroup space. Check the ASM
alert log.
Cause: ADVM could not resize the volume because ASM did not have enough
contiguous free diskgroup storage.
Action: Increase the free space in the diskgroup. Check the ASM alert log.
ACFS-03172: ADVM is busy with Mirror recovery. Try again later.
Cause: ADVM could not resize the volume because it is recovering the mirrored
volumes.
Action: Try again later. The system console log will contain mirror recovery started
and completed messages. For example: [Oracle ADVM] Mirror recovery for volume
asm/volume-name started. [Oracle ADVM] Mirror recovery for volume asm/
volume-name completed.
ACFS-03173: ADVM or ASM is unable to resize the volume. Check the ASM alert
log.
Cause: ADVM or ASM is unable to resize the volume.
Action: Check the ASM alert log.
Cause: The ADVM compatibility attribute for the disk group was not set to version
11.2.0.3.0 or higher to allow the creation of a read/write snapshot.
ACFS-03177: maximum log file size cannot exceed number MB
Action: Retry the command with a log file size that is smaller than the maximum size.
ACFS-03178: unable to delete snapshot string while cluster is in rolling migration
Cause: The cluster was in rolling migration. Snapshot deletions are not allowed
during rolling migration.
Action: Complete the rolling migration and then delete the snapshot.
ACFS-03179: unable to create snapshot 'string' while cluster is in rolling migration
Cause: The cluster was in rolling migration. Snapshot creations are not allowed
Action: Complete the rolling migration and then create the snapshot.
ACFS-03180: Unable to obtain ASM volume device information for 'string'
Cause: The operation for retrieval of ASM volume device information failed. This
ACFS-03185: Unable to obtain ASM volume extent information for string
Cause: The operation for retrieval of ASM volume extent information failed. This
2-22 Error Messages
ACFS-03186: Supplied ACFS file offset value is greater than the file allocation size
of number
Cause: The supplied file offset value in bytes supplied must be smaller than the file
allocation size.
Action: 'acfsutil file info filename' provides the file allocation size. Choose a smaller
value.
ACFS-03187: Extent number (mirror number) is not in use.
Action: None
ACFS-03203: Invalid snap command.
Action: Use a valid 'acfsutil snap' command combination. Valid commands are
'acfsutil snap create', 'acfsutil snap delete', and 'acfsutil snap info'
ACFS-03204: Snapshot 'string' is already read-only.
Cause: A request was made to convert a snapshot to be read-only but the snapshot
was already read-only.
Action: None
ACFS-03205: Snapshot 'string' is already read-write.
Cause: A request was made to convert a snapshot to be read-write but the snapshot
was already read-write.
Action: None
ACFS-03206: The ADVM compatibility attribute for the diskgroup was below the
required version (string) for the 'acfsutil snap convert' command.
Cause: The ADVM compatibility attribute has not been upgraded to a version that
supports the 'acfsutil snap convert' command.
Action: Use the ASMCA tool or the SQL ALTER DISKGROUP statement to upgrade
COMPATIBLE.ADVM attribute to the specified version.
ACFS-03207: invalid combination of options
Cause: The 'acfsutil snap convert' command was passed an invalid option
combination which included both the -r and -w options.
Action: Remove either the -r or -w option from the 'acfsutil snap convert' command.
ACFS-03208: The /r option is not supported on this operating system
Cause: The 'acfsutil snap convert /r' option was specified. This functionality requires
a minimum operating system version of Windows Server 2008 R2.
Action: Upgrade operating system to Windows Server 2008 R2 or use the 'acfsutil
snap create' command to create a read-only snapshot.
ACFS-03212: There are too many snapshots for the file system associated with
string. Only number are allowed. Reduce the number of snapshots before
proceeding.
Cause: An attempt to create more than the maximum allowed number of active
snapshots was rejected.
Action: Delete a snapshot before creating a new one.
ACFS-00501 to ACFS-11111 2-23
ACFS-03213: Creation of a snapshot failed due to presence of snapshots that

prevent this functionality.
Cause: A snapshot creation which specified a parent snapshot was not processed
because of compatibility issues with existing snapshots. Possible causes include: 1)
Snapshots of the file system were found that were created before ADVM
compatibility attribute was set to 12.1. 2) Snapshots of the file system were found that
were created after ADVM compatibility was set to 12.1 but while 11.2 snapshots
existed.
Action: Delete all snapshots associated with the file system and retry the command.
compatibility attribute for the disk group is less than 12.1.
12.1 or higher to allow the creation of a snapshot with a parent snapshot.
ACFS-03216: The ADVM compatibility attribute for the diskgroup was below the
required version (string) for unlimited volume expansions.
Cause: A request to resize the ACFS file system failed because the volume expansion
limit was reached. This limit was hit because the ADVM compatibility attribute
associated with the diskgroup was too low.
the COMPATIBLE.ADVM attribute to the specified version.
ACFS-03300: unable to set tag name on file string
Cause: The ACFS driver was unable to complete the request.
Action: Verify memory or storage resources are sufficient.
ACFS-03301: unable to unset tag name on file string
ACFS-03302: tag name syntax invalid or length too long
Cause: Tag name contains invalid characters or has too many characters.
Action: Change tag name to use valid characters or shorten the tag name.
ACFS-03303: invalid combination of arguments
Cause: The acfsutil tag info -t or -r arguments work only on file pathnames.
Action: Remove the -t or -r arguments from the ofsutil tag info command.
ACFS-03304: Unable to open mount point string. Verify that the mount point exists.
Cause: Mount point cannot be opened to display tag name information.
Action: Verify that the mount point exists and is accessible before retrying the tag info
command.
ACFS-03305: unable to retrieve all tag names for string
Cause: Unable to return the full list of tag names.
Action: Verify there is sufficient memory resources available.
2-24 Error Messages
ACFS-03306: tag name does not exist in file string

Cause: Cannot unset a tag name on a file that does not exist.
Action: Verify the tag name to unset is correct.
ACFS-03308: The ADVM compatibility attribute for the diskgroup must be set to
version 11.2.0.2.0 to allow the acfsutil repl and tag commands.
Cause: The ADVM compatibility attribute has not been upgraded to version 11.2.0.2.0
or beyond.
COMPATIBLE.ADVM attribute.
ACFS-03309: path name string does not resolve to an ACFS file system
Cause: A path name supplied on an 'acfsutil tag' command did not resolve to an
ACFS file system.
Action: Remove the non-ACFS path name from the 'acfsutil tag' command.
ACFS-03310: amount of change since mount: number MB
Action: None
ACFS-03313: unable to collect ACFS statistics for mount point string
Cause: 'acfsutil info fs -s' was unable to communicate with the ACFS driver.
Action: Verify that the file system is online and that the ADVM/ACFS drivers are
loaded and running.
ACFS-03314: interval cannot exceed number seconds
Cause: Statistics interval exceeded maximum number of seconds per interval.
Action: Select an interval that is less than or equal to 2592000 seconds and retry
"acfsutil info fs -s".
ACFS-03315: count cannot exceed number
Cause: Number of statistics intervals exceeded maximum number allowed.
Action: Select a total count that is less than or equal to 2^63-1 and retry "acfsutil info
fs -s".
ACFS-03316: interval must be a positive integer
Cause: A zero or negative integer was provided.
Action: Provide a positive integer for the statistics interval.
ACFS-03317: unable to set tag on file "string" because its tag name storage is full
Cause: The limit of the file's tag name storage has been reached.
Action: Remove any unused tags on this file and try the command again.
ACFS-03318: unable to set tag name "string" because this name is reserved
Cause: The tag name specified is reserved.
Action: Choose another tag name which is not reserved.
ACFS-03319: Set tag on file: string
Action: None
ACFS-00501 to ACFS-11111 2-25
ACFS-03320: Removing tag(s) on file: string

Action: None
ACFS-03321: The ADVM compatibility attribute for the diskgroup is below the
required version (string) for the 'acfsutil tag' commands.
supports tagging.
ACFS-03322: The ADVM compatibility attribute for the diskgroup is below the
required version (string) for the 'acfsutil repl' commands.
supports replication.
ACFS-03323: stringc option requires the stringt option
Cause: The 'c' option was specified without the 't' option. The 'c' option invokes case
insensitive substring matching on the tag names specified using the 't' option.
Action: To use the 'c' option, add the 't' option to specify a tag.
ACFS-03324: Unable to obtain metric data for string
Cause: An internal ioctl operation to access metric data from ACFS file system failed.
ACFS-03344: Error, strings option with repetition interval applied to multiple file
systems.
Cause: A request to report file system statistics periodically was rejected because it
applied to multiple file systems. A single file system must be specified explicitly when
supplying the 's' option with a time interval.
Action: Reissue the request specifying a single file system or omitting the repetition
interval.
ACFS-03450: Continue to panic the cluster [y|n] ?
Cause: The 'acfsutil panic' command was issued to panic the cluster.
Action: Respond Y(yes) to proceed or N(no) to cancel.
ACFS-03451: Continue to panic the system [y|n] ?
Cause: The 'acfsutil panic' command was issued to panic the system.
ACFS-03452: failed to move file or directory from string to string
Cause: An attempt to rename a file or directory failed because the target was an
existing, populated directory or the user permissions were insufficient to perform the
operation.
Action: Retry the operation after removing the target files or correcting the
permissions.
2-26 Error Messages
ACFS-03500: Unable to access kernel persistent log entries.

Cause: Could not get or set persistent log configuration data.
Action: Make sure that the Oracle kernel drivers are loaded/started (run
'acfsdriverstate loaded'). If loaded/started, make sure that you have root/
administrator privileges.
ACFS-03501: The 'query' option may not be used with any other options.
Cause: Additional options to 'query' were specified on the command line.
Action: Do not use any other options with the 'query' option.
ACFS-03502: The specified maximum log file size is less than number MB or is
greater than number MB.
Cause: An invalid log file size was entered on the command line.
Action: Specify a value equal to or greater than the minimum size and equal to or less
than the maximum size.
ACFS-03503: The specified interval is less than number seconds.
Cause: An invalid interval value was entered on the command line.
Action: Enter an interval value equal to or greater than the minimum.
ACFS-03504: An invalid high water level value (number percent) was specified.
Cause: The high water level must be greater than the low water level and less than
100 percent.
Action: Enter a valid high water level value.
ACFS-03505: An invalid low water level value (number percent) was specified.
Cause: The low water level must be greater than zero and less than the high water
level.
Action: Enter a valid low water level value.
ACFS-03506: The selected percentage does not generate an even integer. Changing
to number percent.
Cause: The specified percentage of the buffer size generates a remainder.
Action: None. Informational.
ACFS-03507: The specified buffer size is less than number KB or is greater than
number KB.
Cause: An invalid buffer size value was entered on the command line."
Action: Enter a value equal to or greater than the minimum or equal to or less than
the maximum size.
ACFS-03508: The specified maximum number of log files is less than number or
greater than number.
Cause: An invalid maximum number of log files was entered on the command line.
Action: Specify a value equal to or greater than the minimum and equal to or less than
the maximum.
ACFS-03509: string is not a Grid infrastructure home.
Cause: An invalid Grid infrastructure home was entered on the command line.
Action: Specify a valid Grid infrastructure home.
ACFS-00501 to ACFS-11111 2-27
ACFS-03510: There are more log files on the system than are being configured.
Removing the oldest files.
Cause: A new, lower, maximum number of allowable OKS persistent log files was
configured and there are currently more log files on the system. Deleting the oldest
files."
ACFS-03511: Deleting string.
Cause: A log file was deleted to satisfy the new configuration.
ACFS-03512: Renaming string to string.
Cause: A log file was renamed to place it in time modified sequential order.
ACFS-03513: The OKS persistent log configuration settings cannot be queried.
Cause: The OKS persistent log was not running.
Action: Start the log with 'acfsutil plogconfig -d gridhome'.
ACFS-03514: The directory 'string' can not be converted to an absolute path.
Cause: A directory name was specified that could not be converted to an absolute
path. The name was either an invalid relative path or, on Windows, included an
invalid drive letter.
Action: Specify the directory name in the form of an absolute path. On Windows, the
absolute path includes the drive letter.
ACFS-03528: failed to determine Oracle Base
Cause: The operation to retrieve the Oracle Base location failed. This message is
ACFS-03529: Warning: The 'd' option was specified with an argument, which is no
longer used - argument ignored.
Cause: 'acfsutil plogconfig' now gets the log location internally. The specified log
location was ignored and the command continued using the internally derived
location.
Action: None
ACFS-03530: The 'terminate' option may not be used with any other options.
Cause: Conflicting options were specified on the command line.
Action: Do not use any other options with the 'terminate' option.
ACFS-03539: Base time stamp not found in log file.
Cause: Informational. The likely cause is that the running OKS driver is an older
version that does not support time stamp conversion.
Action: None
ACFS-03540: The specified interval is greater than number seconds.
Action: Enter an interval value equal to or less than the maximum.
2-28 Error Messages
ACFS-03541: The symbolic link 'string' to 'string' cannot be created.

Cause: Likely, the link name was a non-empty directory. OKS persistent logging was
started but no symbolic was created to the target directory.
Action: If a symbolic link is desired, delete the link target and its contents and reissue
the command.
ACFS-03542: The specified OKS log directory 'string' is invalid because it is NFS
mounted.
Cause: The specified logging directory was NFS mounted.
Action: Enter a node local location for the OKS log.
ACFS-03543: The OKS persistent log is not active.
Action: Start the log with 'acfsutil plogconfig -d [log_dir]'.
ACFS-03544: Directory 'string' exists as a file.
Cause: An OKS persistent log directory could not be created because it exists as a file.
Action: Either delete the file or choose another directory name.
ACFS-03602: Plug-in is already enabled on 'string'
Cause: An attempt was made to enable the plug-in when it is already enabled.
Action: First disable the plug-in then retry the command.
ACFS-03603: Plug-in is not enabled on 'string'
Cause: A plug-in command was attempt when the plug-in is not enabled.
Action: Enable the plug-in and then retry the command.
ACFS-03604: Unable to perform plug-in operation on 'string'
Cause: The plug-in operation failed. This message is accompanied by other
ACFS-03610: Invalid plug-in metric type: string
Cause: An invalid plug-in metric type was specified.
Action: Enter a valid metric type from the following list: "acfsmetric1"
ACFS-03611: Invalid interval specified.
Cause: An invalid interval was specified.
Action: Enter a valid interval between 1 and 3600 seconds.
ACFS-03612: Unable to retrieve list of plug-in enabled tags.
Cause: ACFS was unable to retrieve the list of tags for which the plug-in is collecting
metrics. This message is accompanied by other message(s) providing details on the
error.
ACFS-03613: Unable to write plug-in config file.
Cause: ACFS was unable to write the plug-in config file to disk.
ACFS-00501 to ACFS-11111 2-29
Services.
ACFS-03614: Plug-in cannot be enabled for more than number tags.
Cause: An attempt was made to enable the plug-in for more than the maximum
allowed number of tags.
Action: Enable plug-in with fewer tags.
ACFS-03615: An error occured when copying the list of tags.
Cause: This is an internal error.
Services.
ACFS-03621: missing plug-in metric type
Cause: No plug-in metric type was specified.
ACFS-03623: unable to modify the ACFS registration for mount point 'string'
Cause: Could not modify the ACFS registration for the specified mount point.
Action: Examine the accompanying error messages and respond accordingly. If the
solution is not clear, contact Oracle Support Services.
ACFS-03624: unable to modify registration for ACFS volume 'string'
Cause: Could not modify the ACFS registration for the ACFS volume.
ACFS-03626: invalid combination of -C and -f options
Cause: The 'acfsutil log' command was issued with both the -f and -C options. This is
a conflict, because the log file names are pre-specified for -C and may not be specified
using -f.
Action: Re-issue the 'acfsutil log' command with only the desired option. With -C, the
log files will be generated in the persistent log directory in the form
yymmddhhmmss.log. With -f the specified name will be used.
ACFS-03627: logging behavior change specified with cluster option
Cause: The 'acfsutil log' command was issued with both the -C option and and an
option that modifies the logging behavior.
Action: Re-issue the 'acfsutil log' command without the -C option to modify the ACFS
logging behavior. To create logs on all cluster nodes, issue 'acfsutil log -C' with no
other options.
ACFS-04001: Failed to open path string. Verify that string exists.
Cause: Path could not be opened.
Action: Verify the path is accessible before retrying.
Cause: A request for process virtual memory by acfsdismount command failed. This
2-30 Error Messages
ACFS-04011: Failed to open volume string. Verify that string exists.

Cause: Volume could not be opened.
ACFS-04013: acfsdismount /all operation did not complete. Unable to retrieve a
mount point from the list of active ACFS file systems to dismount. It is possible
that not all file systems were dismounted.
Cause: Failed to obtain the next file system to dismount.
Action: Use acfsmountvol to determine if there are any file systems still mounted and
reissue 'acfsdismount /all' if necessary.
ACFS-04032: removing administrative network share for mount point string at
share name 'string'
Action: None
ACFS-04033: administrative network share 'string' does not share mount point
string as expected
Cause: Attempted to remove the administrative network share associated with the
specified ACFS mount point, but the network share does not share the specified ACFS
mount point as expected.
Action: Examine the network share at the specified share name. If the network share
shares an unmounted ACFS file system, manually remove the network share using
'net share share name /delete'
ACFS-04034: administrative network share for mount point string does not exist at
share name 'string'
Action: None
ACFS-04035: retrieving information for administrative network share 'string' failed
Cause: While removing the administrative network share associated with the
specified ACFS mount point, failed to retrieve information on the administrative
network share. This message is accompanied by other messages providing details on
the error.
Action: Check for a network share at the specified share name. If a network share
exists at the specified share name and it shares an unmounted ACFS file system,
manually remove the network share using 'net share share name /delete'
ACFS-04036: removing administrative network share for mount point string at
share name 'string' failed
Cause: Failed to remove the administrative network share associated with the
specified ACFS mount point. This message is accompanied by other messages
Action: Manually remove the administrative network share at the specified share
name using 'net share share name /delete'
ACFS-00501 to ACFS-11111 2-31
ACFS-04037: could not remove administrative network share for mount point string
ACFS-04038: Volume string is still mounted. Dismount will complete as soon as
activity ceases on the file system.
Cause: At the conclusion of the file system dismount request, the file system was still
mounted. This could be a result of open files on the mount point. The dismount will
finish as soon as activity ceases on the file system.
Action: To force dismount to complete, terminate any processes or applications that
are using the file system.
ACFS-04058: Ignoring unsupported ACFS command option: 'string'
Cause: An unsupported 'umount.acfs' command option was specified.
Action: No action required. The unmount will proceed without the option.
ACFS-04150: unable to retrieve mount point information from the ACFS driver
Cause: During unmount processing, an attempt to retrieve mount point information
from the ACFS driver failed.
Action: Verify the mount point is a valid ACFS file system before retrying the
unmount command. If the problem persists, contact Oracle Support Services.
ACFS-04151: unmount of mount point string failed
Cause: The file system unmount failed. This message is accompanied by other
ACFS-05001: must specify 'primary' or 'standby'
Cause: Command syntax requires 'primary' or 'standby' argument.
Action: At command line, indicate primary or standby for replication command.
ACFS-05002: must provide an Oracle Net alias to the primary replication site
Cause: The Oracle Net alias to connect to the primary replication site was not
specified.
Action: Provide Oracle Net alias to connect to the primary replication site.
ACFS-05003: must provide a primary mount point
Cause: The mount point on the replication primary site for the file system to be
replicated was not provided.
Action: Provide an existing mount point on the primary site for the file system to be
replicated.
ACFS-05004: cannot allocate a list of tag names
2-32 Error Messages
ACFS-05005: invalid tag name: string
Cause: User specified a tag name that has incorrect syntax.
Action: See the platform specific Oracle documentation for correct syntax for ACFS
tag names.
ACFS-05006: unable to initialize replication process data structures
Cause: Failed to determine path names for replication directories.
Action: Verify the specified mount point is an ACFS file system.
ACFS-05007: cannot initialize interrupt signal handler
Cause: The system could not initialize the mechanism to handle interrupts.
ACFS-05008: cannot lock file string to serialize ACFS replication commands
Cause: Failed to open and lock the specified file. This message accompanied by other
ACFS-05009: ACFS replication initialization is already in progress.
Cause: Initialization was in progress on the replication site.
Action: Wait for the other initialization on replication site to complete.
ACFS-05010: ACFS replication initialization is still in progress.
Cause: The command cannot be run until replication initialization completes.
Action: Monitor initialization progress with the 'acfsutil repl info' command.
ACFS-05011: cannot open directory: string
Cause: Failed to open the specified directory. This message is accompanied by other
ACFS-05012: ACFS replication is already initialized.
Cause: ACFS replication has already been initialized on this system.
Action: Initialization cannot be undone unless replication is terminated or the file
system is reformatted.
ACFS-05013: ACFS replication cannot be initialized.
Cause: This message is accompanied by other message(s) providing details on the
error.
ACFS-05014: cannot verify replication configuration
error.
ACFS-00501 to ACFS-11111 2-33
ACFS-05015: cannot cleanup replication directories
Cause: The application failed to cleanup from a previous replication instantiation.
Action: Verify user permissions and that the replication directory is available.
ACFS-05016: cannot update replication configuration with new trace level
Cause: The application was unable to communicate with the ACFS driver.
Action: Verify that the ADVM/ACFS drivers are loaded and running.
ACFS-05017: cannot create file: string
Cause: The application failed to create the specified file. This message is accompanied
by other message(s) providing details on the error.
ACFS-05018: cannot get primary ADVM volume information for string
Cause: The application failed to get the ADVM volume path for the mounted ACFS
file system.
Action: Verify that the file system is mounted and of type ACFS.
ACFS-05019: cannot allocate space for the ADVM volume path
ACFS-05020: cannot start replication daemons
Cause: CRS has failed to start the replication daemons.
Action: Verify that CRS is running. Check the CRS logs to determine why the
replication daemons failed to start.
ACFS-05021: cannot stop replication daemons
Cause: CRS has failed to stop the replication daemons.
replication daemons failed to stop.
ACFS-05022: internal CRS error
Cause: The application failed to initialize communication with CRS.
ACFS-05023: error checking for file: string
Action: None
ACFS-05024: The standby replication site is initialized. ACFS replication will
begin.
Action: None
2-34 Error Messages
ACFS-05025: waiting for the standby replication site to initialize

Action: None
ACFS-05026: caught interrupt; ACFS replication initialization is shutting down.
Action: None
ACFS-05027: cannot remove file: string
Action: Verify the ASM instance is operational and the state of the file system using
'acfsutil info fs' before retrying the command.
ACFS-05028: cannot obtain current time for events log
Cause: The application failed to get the current time for logging.
ACFS-05029: cannot write to the events log
Cause: The application failed to write to the specified file. This message is
ACFS-05030: cannot clean up configuration file
Cause: Initialization failed and the configuration file created during failed
initialization could not be removed.
ACFS-05031: standby file system is not empty
Cause: The file system was not empty.
Action: Use an empty standby file system; either reformat the file system or remove
all files and directories under standby mount point/.
ACFS-05032: unable to determine user permissions
Cause: An error occurred attempting to acquire the user permissions. This message is
Action: Correct the problem indicated by the other message(s). Otherwise, report this
error to Oracle Support Services.
ACFS-05033: must provide a standby mount point
Cause: A mount point on the standby replication site was not provided.
Action: Provide an existing mount point with an empty file system on the standby
replication site.
ACFS-05034: cannot obtain path for directory: string
Cause: The application failed to locate the specified directory.
Action: Verify that the replication directory is available.
ACFS-05035: cannot open file for write: string
Cause: The application failed to open the specified file. This message is accompanied
ACFS-00501 to ACFS-11111 2-35
ACFS-05036: cannot write to file: string
ACFS-05037: cannot move file string to directory string
Cause: The application failed move the specified file.
ACFS-05038: cannot register Oracle Net service name
Cause: Unable to register the Oracle Net service name with the ASM instance.
ACFS-05039: cannot unregister Oracle Net service name
Cause: Unable to unregister the Oracle Net service name from the ASM instance.
ACFS-05040: cannot obtain Oracle Net service name from alias provided
Cause: Unable obtain the Oracle Net service name from the Oracle Net alias provided
on the command line.
Action: Verify that the Oracle Net alias exists and is properly formed.
ACFS-05041: Oracle Net service name is greater than string bytes
Cause: The Oracle Net service name specified for replication is greater than the
maximum allowed.
Action: Reduce the size of the Oracle Net service name being used for replication.
ACFS-05042: insufficient privileges to perform replication command.
Administrator access is required.
Cause: The caller does not have sufficient privileges to perform the replication
command.
Action: Execute the replication command from a user with administrator access.
ACFS-05043: insufficient privileges to perform replication command. ASM
administrator group access is required.
command.
Action: Execute the replication command from a user with ASM administrator group
access.
ACFS-05044: cannot obtain node name
Cause: Unable to get local node name through CRS.
Action: Verify that CRS is running.
ACFS-05045: invalid interval specified for replication statistics
Cause: The caller specified an invalid time interval for replication statistics.
2-36 Error Messages
Action: Verify the syntax of the time interval using 'acfsutil repl info' help flag and
retry.
ACFS-05046: invalid date range specified for replication statistics
Cause: The caller specified an invalid date range for replication statistics.
Action: Verify the syntax of the date range using 'acfsutil repl info' help flag and retry.
ACFS-05047: time specified is in the future
Cause: The caller specified a date in the future.
Action: Verify the time specified is before the current time.
ACFS-05048: start time specified is newer than the end time specified
Cause: The caller specified a date range where the start time was more recent the end
time.
Action: Verify the start time is before the end time.
ACFS-05049: validating the remote connection
Action: None
ACFS-05050: remote connection cannot be established
Cause: The user name, password, or Oracle Net alias used to connect to the remote
site was not correct or the remote site was unreachable.
Action: Verify the connection information is correct and the status of the remote site.
ACFS-05051: remote connection has been established
Action: None
ACFS-05052: standby replication site requires reinitialization
Cause: Initialization was unable to complete on the primary replication site and left
the standby replication site in an indeterminate state.
Action: On the standby replication site, run 'acfsutil repl terminate' and 'acfsutil repl
init' before retrying initialization on the the primary replication site.
ACFS-05053: replication's Oracle Net service name conflicts with the existing ASM
service name
Cause: The service name for replication specified in the Oracle Net alias conflicts eith
the Oracle Net service name that ASM uses.
Action: Review the Oracle Net alias for replication in tnsnames.ora and use a different
service name for the replication alias.
ACFS-05054: standby replication file system is mounted on more than one cluster
node
Cause: The standby replication file system was mounted on more than one node in
the cluster.
Action: Unmount the file system on all but one node on the standby replication site
and retry the initialization.
ACFS-05055: invalid connection string for the primary replication site
Cause: The user name, password, or Oracle Net alias used to connect to the primary
replication site was not correct or was unreachable.
ACFS-00501 to ACFS-11111 2-37
Action: Verify the connection information is correct and the status of the primary
replication site.
ACFS-05056: invalid connection string for the standby replication site
Cause: The user name, password, or Oracle Net alias used to connect to the standby
Action: Verify the connection information is correct and the status of the standby
replication site.
ACFS-05058: command issued on the incorrect replication site
Cause: The command was issued on the incorrect replication site.
Action: Verify the command syntax. If issued on the primary file system, reissue on
the standby file system. If issued on the standby file system, reissue on the primary
file system.
ACFS-05059: ACFS replication not initialized
Cause: ACFS replication information cannot be retrieved as replication has not been
initialized.
Action: None
ACFS-05060: waiting for ACFS replication to terminate
Action: None
ACFS-05061: ACFS replication command interrupted
Action: None
ACFS-05062: cannot query CRS resource
Cause: The application failed to communicate with CRS.
Action: Verify that CRS is running. Check the CRS logs to determine why the CRS
resource is not responding.
ACFS-05063: cannot relocate CRS resource
Cause: The application failed to relocate CRS resource.
resource cannot be relocated.
ACFS-05064: the service name 'string' is not registered on the standby site
Cause: Possible causes include: 1.) Replication was not initialized on the standby site.
2.) Mismatched service names. If the -c option is not used, the service name specified
in the alias for the standby file system did not match the service name specified for
the primary file system in the alias on the standby site. 3.) The alias for the standby
site referred to the wrong set of nodes.
Action: Possible actions include: 1.) Verify replication is initialized on the standby
site. 2.) Verify the service name used to connect to the standby site matches the one
registered on the standby site. Run 'lsnrctl status' on the standby site to verify. 3.)
Verify that the nodes listed in the standby alias have the standby file system
mounted.
2-38 Error Messages
ACFS-05065: cannot transfer files to the standby file system 'string'

Cause: Possible causes include: 1.) The standby mount point did not exist or was not
an ACFS file system. 2.) The standby file system was full.
Action: Possible actions include: 1.) Verify that the standby mount point exists and is
an ACFS file system. 2.) Verify that there is free space on the standby file system.
ACFS-05066: ACFS replication is already paused
Cause: ACFS replication was paused by a previous call.
Action: None
ACFS-05067: cannot rename file string to string in directory string
Cause: The application failed to rename the specified file.
ACFS-05068: ACFS replication has not been paused
Cause: ACFS replication was not paused. Resume operation is not needed.
Action: None
ACFS-05069: ACFS replication update must specify at least one attribute
Cause: The command to update the replication configuration did not specify any
attributes to update.
Action: Specify at least one replication attribute to be updated.
ACFS-05070: command must be run on the primary replication site
Cause: 'acfsutil repl update' command was not run on the primary replication site.
Action: Execute 'acfsutil repl update' on the primary replication site.
ACFS-05071: invalid username or password used to connect to the standby site
Cause: The username or password specified on the command line or in the wallet was
incorrect.
Action: Verify the username and password are correct when connecting to the
standby site.
ACFS-05072: cannot open events file string
Cause: Failed to open events log file.
ACFS-05073: cannot query events log file
Cause: Failed to query events log file.
ACFS-05075: cannot terminate replication
Cause: Failed to terminate replication.
ACFS-05076: unable to determine CRS user/group
Cause: The application failed to determine CRS user and/or group.
ACFS-00501 to ACFS-11111 2-39
user and/or group cannot be determined.
ACFS-05077: could not complete replication synchronization
Cause: Failed to complete synchronization of primary and standby replication sites.
ACFS-05078: failed to synchronize primary and standby replication sites
Cause: Failed to synchronize replication sites.
ACFS-05079: waiting for replication update to complete
Action: None
ACFS-05083: Initialization of the primary file system could not complete because
the standby is already configured for replication.
Cause: The standby file system was not expecting initialization data from this
primary. Possible causes include: 1. Stale replication state detected on standby file
system from a previous instantiation. 2. An incorrect replication standby site was
supplied. 3. An incorrect replication standby file system was supplied.
Action: 1. Run 'acfsutil repl terminate' on the standby site for the standby file system
before retrying the initialization of the primary. 2. Verify the correct standby site is
used. 3. Verify the correct standby file system is used.
ACFS-05084: The replication standby file system has been newly initialized and is
refusing files from the primary. The primary may need to be terminated and newly
initialized.
Cause: The standby file system was not expecting any data from the primary except
initialization data. A possible cause may be the standby file system was terminated
and newly initialized, but the primary was not.
Action: Verify the primary site and primary file system. Run 'acfsutil repl terminate'
on the primary site for the primary file system before retrying the initialization of the
standby.
ACFS-05085: cannot start replication because incompatible ACFS features already
exist
Cause: Failed to start replication: Either security or encryption or both is enabled on
the file system.
Action: Undo security or encryption or both, then try to initialize replication again. To
undo encryption and security respectively: acfsutil encr set -m mount-point -u acfsutil
sec prepare -m mount-point -u
ACFS-05086: listener is not running on the standby site
Cause: The listener was not started on the remote site or an incorrect node name was
specified in the standby alias definition.
Action: Verify the listener is started on the standby site. Check that the standby alias
contains the correct node names.
2-40 Error Messages
ACFS-05087: The event log does not cover the time range specifed.
Cause: The events log did not cover any portion of the time range specified in the
command.
Action: Change the time range or use an events log that covers the range specified.
ACFS-05088: replicated file system size is below the minimum of stringG
Cause: An attempt was made to initialize replication on a file system that did not
have sufficient space.
Action: Resize the file system to at least the minimum size specified.
ACFS-05089: replication statistics cannot be queried on the standby site
Cause: An attempt was made to query the replication statistics on the standby site.
Action: Query the replication statistics from the primary site.
ACFS-05090: interval is greater than string years
Cause: The interval specified was greater than the maximum allowed.
Action: Retry the command with a lower interval value.
ACFS-05091: The mount path specified exceeds the maximum length allowed on
this platform.
Cause: The specified mount path exceeded the maximum length on this platform.
Action: Use a valid mount path.
ACFS-05092: replicated file system free space is near the minimum threshold of
stringGB per active node, continuing with initialization
Cause: Initialization of replication was issued on a file system that is near the
minimum threshold of free space.
Action: Consider resizing the file system to allow for optimal replication performance.
ACFS-05093: could not retrieve active node count on file system: string, error: string
Cause: Could not get the number of nodes active on the specified file system.
Action: Verify at least one cluster node has the file system mounted, or address the
specified operating system dependent error code provided. If the solution is not clear,
ACFS-05094: replicated file system free space is below the minimum of stringGB
per active node, actual free space left: stringGB
Action: Resize the file system such that free space is at least the minimum size
specified.
ACFS-05159: Last sync time with primary: string
Action: None
ACFS-05170: Cannot initialize replication while the cluster is in rolling migration
Cause: An attempt to initialize replication was rejected because the cluster was in
rolling migration. Replication initialization is not allowed during rolling migration.
Action: Complete the rolling migration and then initialize replication.
ACFS-00501 to ACFS-11111 2-41
ACFS-05171: Cannot terminate replication while the cluster is in rolling migration

Cause: An attempt to terminate replication was rejected because the cluster was in
rolling migration and the file system was mounted on more than one node.
Action: Either complete the rolling migration and then terminate replication, or
unmount this file system on the other nodes and then terminate replication.
ACFS-05172: Replication cannot be terminated because background processes are
not running.
Cause: Replication background processes were stopped and cannot finish processing
replication data.
Action: Run 'acfsutil repl bg start mountpoint' to restart replication background
processes and complete the apply of existing replication data, or run 'acfsutil repl
terminate standby immediate mountpoint' to terminate replication immediately
without applying the remaining replication data.
ACFS-05200: Stopping ACFS replication daemons on string
Action: None
ACFS-05201: Starting ACFS replication daemons on string
Action: None
ACFS-05202: ACFS replication daemons started successfully on string
Action: None
ACFS-05203: ACFS replication daemons stopped successfully on string
Action: None
ACFS-05204: Attempting to restart replication daemons on string
Action: None
ACFS-05205: Failed to initialize replication because ACFS Security is in use on the
standby file system 'string'.
Cause: ACFS replication initialization failed on the standby file system because ACFS
Security was in use on the file system.
Action: If you are sure you want to use the indicated file system as standby, reformat
the standby file system and retry the command.
ACFS-05206: Failed to initialize replication on ACFS Security enabled file system
'string' because ACFS Security is not initialized on the standby site.
Cause: Replication initialization failed on ACFS Security enabled primary file system
because ACFS Security was not initialized on the standby site.
Action: There are two possible options based on user's preference. 1. If ACFS Security
is desired on primary and standby file systems, follow the below mentioned steps in
sequence: a. Terminate replication on standby file system by executing 'acfsutil repl
terminate' command. b. Initialize ACFS Security on standby site by executing 'acfsutil
sec init' command. c. Reinitialize replication on standby file system by executing
2-42 Error Messages
'acfsutil repl init' command. d. Retry 'acfsutil repl init' command on the primary file
system. 2. If ACFS Security is not desired on primary and standby file systems, follow
the below mentioned steps in sequence: a. Terminate replication on standby file
system by executing 'acfsutil repl terminate' command. b. Remove ACFS Security on
primary file system by using 'acfsutil sec prepare' command. c. Reinitialize replication
on standby file system by executing 'acfsutil repl init' command. d. Retry 'acfsutil repl
init' command on the primary file system.
ACFS-05207: A request to initialize replication failed because the primary
replication file system is enabled for ACFS Security and standby site is not
initialized for ACFS Security.
Cause: A request to initialize replication failed because the primary replication file
system was enabled for ACFS Security and standby site was not initialized for ACFS
Security.
below mentioned steps in sequence: a. Terminate replication on standby file system
by executing 'acfsutil repl terminate' command. b. Remove ACFS Security on primary
file system by using 'acfsutil sec prepare' command. c. Reinitialize replication on
standby file system by executing 'acfsutil repl init' command. d. Retry 'acfsutil repl
replication file system is enabled for ACFS Encryption and standby site has PKCS
wallet.
Cause: Replication initialization failed because the use of PKCS wallet for an ACFS
Replication standby site is not supported.
Action: There are two possible options based on user's preference. 1. If ACFS
Encryption is desired on primary and standby file systems a. Terminate replication on
standby file system by executing 'acfsutil repl terminate' command. b. Convert the
PKCS wallet to SSO wallet on standby by executing 'acfsutil keystore migrate'
command. c. Reinitialize replication on standby file system by executing 'acfsutil repl
init' command. d. Retry 'acfsutil repl init' command on the primary file system. 2. If
ACFS Encryption is not desired on primary and standby file systems a. Terminate
replication on stanby filesystem by executing 'acfsutil repl terminate' command. b.
Remove ACFS Encryption on primary filesystem by using 'acfsutil encr set'
init' command. d. Retry 'acfsutil repl init' command on the primary file system.
replication file system is enabled for ACFS Encryption and an error occurred in
accessing OCR at standby site.
Cause: Internal error.
ACFS-05210: Failed to initialize replication because ACFS Encryption is in use on
the standby file system 'string'.
Encryption was in use on the file system.
ACFS-00501 to ACFS-11111 2-43
the standby file system to remove encryption and retry the command.
ACFS-05211: Failed to initialize replication on ACFS Encryption enabled file
system 'string' because PKCS wallet existed on standby site.
ACFS-05212: Failed to initialize replication on ACFS Encryption enabled file
system 'string' because an error occurred in accessing the OCR at standby site.
ACFS-05214: Failed to prepare ACFS Security on replication enabled file system
Cause: An attempt to prepare ACFS Security on replication enabled file system failed
Action: Initialize ACFS Security on the standby site by executing the 'acfsutil sec init'
command and retry the operation.
ACFS-05216: Failed to set ACFS encryption on a replication enabled file system
'string' because PKCS wallet is not supported as ACFS encryption key store on
standby site.
Cause: An attempt to set ACFS encryption on replication enabled file system failed
because the standby site was having a PKCS wallet as ACFS encryption key store.
Action: If ACFS encryption is desired on primary and standby file systems follow the
steps mentioned below in sequence: a. Convert the PKCS wallet to SSO wallet on
standby site by executing the 'acfsutil keystore migrate' command. b. Retry the
'acfsutil encr set' command.
ACFS-05217: Failed to set ACFS Encryption on replication enabled file system
'string' because an error occurred accessing the OCR at standby site.
ACFS-05218: Cannot proceed because another conflicting 'acfsutil' command is in
progress.
Cause: The command could not proceed because one of the following 'acfsutil'
commands was in progress in the cluster. a. 'acfsutil repl init' b. 'acfsutil sec prepare'
c. 'acfsutil encr set' d. 'acfsutil audit enable'
Action: Retry the command after some time.
2-44 Error Messages
ACFS-05219: Cannot proceed because CRS stack is not up.

Cause: The command could not proceed because CRS stack was not up.
Action: Verify that Cluster Ready Services (CRS) stack is up by executing 'crsctl check
crs' and Cluster Synchronization Services (CSS) is running by executing 'crsctl check
css'. If the CRS stack is not up or the CSS is not running, check with the CRS
administrator to bring it up. If it does not resolve the problem, contact Oracle Support
Services.
ACFS-05220: Cannot proceed because ACFS replication initialization is in progress.
Cause: The command could not proceed because ACFS replication initialization was
in progress.
Action: Verify that the ACFS replication initialization is complete by executing
'acfsutil repl info' and retry.
ACFS-05221: Failed to prepare ACFS Security on a replication enabled file system
'string' because ACFS audit is not initialized on the standby site.
Cause: An attempt to prepare ACFS Security on a replication enabled file system
failed because ACFS Audit was not initialized on the standby site.
Action: Initialize ACFS Audit on the standby site by executing the 'acfsutil audit init'
ACFS-05222: Failed to initialize replication on ACFS Audit prepared filesystem
string because ACFS Audit is not initialized on the standby site.
Cause: Replication initialization failed on an ACFS Audit prepared primary file
system because ACFS Audit was not initialized on the standby site.
Action: If ACFS Audit is desired on primary and the standby file systems, follow the
steps mentioned below in sequence: a. Terminate replication on the standby file
system by executing 'acfsutil repl terminate' command. b. Initialize ACFS Audit on
the standby site by executing 'acfsutil audit init' command. c. Reinitialize replication
on the standby file system by executing 'acfsutil repl init' command. d. Retry 'acfsutil
repl init' command on the primary file system.
ACFS-05223: Failed to prepare ACFS Audit on replication enabled file system
Cause: An attempt to prepare ACFS Audit on a replication enabled file system failed
because ACFS Audit was not initialized on the standby site.
ACFS-05224: Failed to prepare ACFS Audit on replication enabled file system
ACFS-05226: Failed to set ACFS Encryption on a replication enabled file system
'string' because ACFS audit is not initialized on the standby site; moreover, PKCS
wallet is not supported as ACFS Encryption key store on the standby site.
Cause: In ACFS Audit initialized cluster, an attempt to set ACFS Encryption on
replication enabled filesystem failed because standby site is not ACFS audit initailized
and PKCS wallet is not supported as ACFS Encryption key store on the standby site.
Action: follow the steps mentioned below in sequence. a. Initialize ACFS Audit on the
standby site by executing 'acfsutil audit init' command. b. Convert the PKCS wallet to
ACFS-00501 to ACFS-11111 2-45
SSO wallet on standby by executing 'acfsutil keystore migrate' command. c. Retry

command 'acfsutil repl init' on the primary site.
ACFS-05227: Failed to set ACFS Security on a replication enabled file system
'string' because ACFS Security is not initialized on the standby site; moreover,
ACFS Audit is not initialized on standby site.
Cause: In an ACFS Audit initialized cluster, an attempt to prepare ACFS Security on a
replication enabled filesystem failed because the standby site was neither Audit
initialized nor Security initialized.
standby site by executing 'acfsutil audit init' command. b. Initialize ACFS Security on
the standby site by executing 'acfsutil sec init' command. c. Retry command 'acfsutil
repl init' on the primary site.
ACFS-05228: Failed to set ACFS Encryption on a replication enabled file system
Cause: An attempt to set ACFS Encryption on a replication enabled file system failed
ACFS-05229: Failed to prepare ACFS Security on replication enabled file system
'string' because an error occurred accessing the OCR at the standby site.
ACFS-05230: Failed to get standby site's encryption state.
Cause: An attempt to get standby site's encryption status failed because standby site
was unreachable.
Action: Verify the status of remote site and retry the command.
ACFS-05231: Failed to get standby site's security state.
Cause: An attempt to get standby site's security status failed because standby site was
unreachable.
ACFS-05232: Failed to get standby site's audit state.
Cause: An attempt to get standby site's audit status failed because standby site was
unreachable.
ACFS-05233: Cannot prepare a file system for ACFS Security while the cluster is in
rolling migration.
Cause: An attempt to prepare a file system for ACFS Security was rejected because
the cluster was in rolling migration. ACFS Security prepare operation is not allowed
Action: Complete the rolling migration and retry the command.
2-46 Error Messages
ACFS-05234: Cannot set ACFS Encryption parameters while the cluster is in rolling
migration.
Cause: An attempt to set ACFS Encryption parameters was rejected because the
cluster was in rolling migration. ACFS Encryption set operation is not allowed during
rolling migration.
ACFS-05235: Cannot enable ACFS Audit while the cluster is in rolling migration.
Cause: An attempt to enable ACFS Audit was rejected because the cluster was in
rolling migration. ACFS Audit enable operation is not allowed during rolling
migration.
ACFS-05354: Clock difference detected between primary and standby replication
sites.
Cause: A difference in the system clocks has been detected between the primary and
standby replication sites.
Action: Update the time on the primary and standby replication sites to match, and
reissue the 'acfsutil repl info -s' command with a new time interval.
ACFS-05356: The Oracle Local Registry, OLR, cannot be accessed to query the
software version.
Cause: The OLR is not accessible or is not configured correctly.
Action: Run 'ocrcheck -local' to verify the OLR is accessible and working properly.
ACFS-05500: ACFS replication error. Contact Oracle Support Services. string
Cause: An ACFS replication operation failed.
ACFS-05501: ACFS replication error. Customer action required. string
error.
Action: Correct the problem indicated by the other message(s) immediately. If the
ACFS-05502: ACFS replication error. System administration needed. string
error.
Action: The replication daemon(s) will try to correct this situation by moving to
another node in the cluster, if available. The problem indicated by the other
message(s) should be addressed as soon as possible for replication to continue
without further error. If the cause of the problem is unclear, contact Oracle Support
Services.
ACFS-05503: ACFS replication string daemon shutting down. string
error.
ACFS-00501 to ACFS-11111 2-47
ACFS-05505: The standby replication file system is full.

Cause: The standby replication file system is out of space.
Action: Resize the standby file system or delete snapshots from the standby file
system if any exist; otherwise, replication may not proceed.
ACFS-05506: The primary replication file system is full.
Cause: The primary replication file system is out of space.
Action: Delete unnecessary files from the primary file system to free up space, resize
the primary file system, or delete snapshots from the primary if any exist; otherwise,
replication may not proceed.
ACFS-05507: The standby replication site failed number times to transport
replication files from host string.
Cause: The replication transport mechanism failed to transport files from the standby
replication site.
Action: Make sure the replication transport daemon is running and that proper
permissions are set on the replication file systems.
ACFS-05508: The primary replication site failed number times to transport
Cause: The replication transport daemon failed to transfer files from the primary
replication site.
ACFS-05511: The standby replication site host, string, is experiencing number I/O
errors.
Cause: I/O on the standby replication site failed.
ACFS-05512: The primary replication site host, string, has experienced number I/O
errors.
Cause: I/O on the primary replication site failed.
ACFS-05513: replication monitor daemon has detected a problem
Cause: An error log file was received.
Action: Check the ACFS alert logs and 'acfsutil repl info' to determine the cause.
ACFS-05514: The replication monitor daemon has not received receipt or error files
within the set threshold.
Cause: The time allowed for receiving receipt or error files has surpassed.
Action: Make sure all replication resources are running using 'acfsutil repl bg info' on
both the primary and standby replication sites.
ACFS-05515: The replication monitor received an invalid receipt file and will not
process it.
Cause: The receipt file that the replication monitor process received is not valid.
2-48 Error Messages
Action: Make sure proper permissions are set on the replication directories and that
I/O requests can be processed.
ACFS-05516: The apply daemon failed to regenerate an apply file.
Cause: The apply daemon has requested more than the allowed number of
regnerations on an apply file.
Action: Restart the file system replication resource using 'acfsutil repl bg start'.
ACFS-05517: ACFS replication on string: string
Action: None
ACFS-05518: string is not an ACFS mount point
Cause: The command required an ACFS mount point for execution.
Action: Retry the command using an ACFS mount point.
ACFS-05519: must provide an Oracle Net alias to the standby replication site
Cause: The Oracle Net alias, which is used to connect to the standby replication site,
was not specified.
Action: Provide the Oracle Net alias to connect to the standby replication site.
ACFS-05520: cannot update replication configuration
ACFS-05521: cannot initialize replication configuration
ACFS-05522: Cannot terminate replication. Pending operations are unable to
complete because the replication standby file system is full.
Cause: The standby replication file system is full and replication could not complete
applying data before terminating.
Action: Resize the standby file system, delete snapshots from the standby file system
if any exist, or use 'acfsutil repl terminate immediate' to force a terminate on the
standby without applying any outstanding replication data. Any outstanding
replication data will be lost if 'acfsutil repl terminate immediate' is issued.
05600-05604 reserved for replication exceptions
ACFS-05605: ACFS replication daemon string is exiting due to replication
termination. string
Action: None 05606-05625 reserved for replication exceptions
ACFS-05700: All the tag names specified during the "acfsutil repl init" operation
must exactly match those specified on the command line.
Cause: Either at least one tag name was not specified during replication initialization
or a specified tag name does not match that used during the "acfsutil repl init"
operation.
Action: Use the exact tag names specified during the "acfsutil repl init" operation.
ACFS-00501 to ACFS-11111 2-49
ACFS-05701: Comparing primary mount point (<<<) to standby mount point (>>>):
Action: None
ACFS-05702: Testing for extra files on standby.\nStandby mount point (<<<) to
primary mount point (>>>):
Action: None
ACFS-05703: Results for file comparison of primary to standby mount points:
Action: None
ACFS-05704: Files successfully compared = number
Action: None
ACFS-05705: Files which failed comparison = number
Action: None
ACFS-05706: Results for extra files on standby test:
Action: None
ACFS-05707: Total files checked = number
Action: None
ACFS-05708: Extra files found = number
Action: None
ACFS-05709: A status check on a file failed. Skipping file: string
Cause: Either the primary file system is actively being modified or an internal error
occurred.
Action: If possible, ensure the primary file system is not changing while the tool is
running.
ACFS-05710: ACFS tags do not support character devices. Skipping file: string
Action: None
ACFS-05711: ACFS tags do not support block devices. Skipping file: string
Action: None
ACFS-05712: ACFS tags do not support FIFOs. Skipping file: string
Action: None
2-50 Error Messages
ACFS-05713: ACFS tags do not support sockets. Skipping file: string

Action: None
ACFS-05714: <<< string\n>>> File missing!
Cause: The specified file was not replicated to the standby file system.
Action: None
ACFS-05715: Found: string
Cause: The specified file is an extra file on the standby file system.
Action: None
ACFS-05716: <<< Tag names exist on file string\n>>> No tag names exist on file
string
Cause: The file on the primary file system has tag names but the file on the standby
file system has no tag names.
Action: Tag names on files can be displayed with the "acfsutil tag info" command.
ACFS-05717: <<< Extended attribute mismatch for string\n>>> Extended attribute
mismatch for string
Action: None
ACFS-05718: An unexpected result occurred during primary to standby comparison.
Continuing. Affected files: string string
Cause: An unexpected result occurred when comparing the primary to the standby.
Action: None. The file was skipped.
ACFS-05719: An unexpected result occurred during standby to primary comparison.
Continuing. Affected files: string string
Cause: An unexpected result occurred when comparing the standby to the primary.
ACFS-05720: File type was not recognized. Continuing. Affected files "string" and
"string"
Cause: An unrecognized file type was encountered which will be ignored.
Action: Informational
ACFS-05721: Could not open the file specified for a checksum operation: string
Cause: Either the primary file system was modified or an internal error occurred.
Action: If possible, do not modify files on the primary file system when running this
tool.
ACFS-05722: A file read failed during a checksum operation: string
tool.
ACFS-05723: Unable to obtain security attributes on file "string"
Cause: Check the access rights on the indicated file.
Action: Ensure the files security attributes can be read using a file manager.
ACFS-00501 to ACFS-11111 2-51
ACFS-05724: Unable to convert a security descriptor to a string on file "string"

Cause: The Windows security identifier (SID) may not be available on this system.
Action: Check the Windows SID is available on this host.
ACFS-05728: Failed to retrieve file system status information from a system call for
mount point "string."
Cause: A system call for the status of the file system failed.
Action: Ensure the file system is accessible via "acfsutil info fs".
ACFS-05730: Mount point "string" does not support Oracle ACFS tagging.
Cause: The "-a" option was passed on the command line to compare ACFS tags. A file
system being checked did not support ACFS tagging.
Action: Disable ACFS tag name comparison by omitting the "-a" option.
ACFS-05731: Mount point "string" does not support extended attributes, therefore,
the ACFS tag name portion of the comparisons will not be performed.
Action: None
ACFS-05732: The specified standby mount point does not exist: "string" .
Cause: Failed to access the specified standby mount point.
Action: Use a networked file system to provide access to the standby file system on
the primary node where the 'acfsutil repl compare' will be preformed.
ACFS-05733: Successfully compared: string string
Action: None
ACFS-05734: Successfully verified existence: string string
Action: None
ACFS-05737: string file attribute comparison failed: permissions=string,
links=number, uid=number, gid=number, bytes=number, file: string
Action: None
ACFS-05738: string file size or file contents comparison failed, file: string
Action: None
ACFS-05739: string security descriptor comparison failed, file: string
Action: None
ACFS-05740: string file type comparison failed, file: string
Action: None
2-52 Error Messages
ACFS-05741: string file type comparison failed, directory: string

Action: None
ACFS-05742: string file type comparison failed, soft link: string
Action: None
ACFS-05743: string file type comparison failed, socket: string
Action: None
ACFS-05744: string file type comparison failed, character device: string
Action: None
ACFS-05745: string file type comparison failed, block device: string
Action: None
ACFS-05746: string file type comparison failed, FIFO: string
Action: None
ACFS-05747: Directory 'string' is a nested ACFS reparse point and was not included
in the file system comparison.
Action: None
ACFS-05748: The 'strings' option requires either the 'stringa' option or 'stringt'
option.
Cause: An incorrect combination of options was specified.
Action: Combine the 's' option with either the 'a' option or 't' option.
ACFS-05749: The specified primary and standby mount points are the same path
and will not be compared.
Cause: The provided primary and standby mount point paths resolved to the same
location.
Action: Rerun the command specifying the unique mount point paths for the primary
file system and the standby file system.
ACFS-05801: The primary replication file system string is at least number%% full.
Cause: Free space in the primary replication file system fell below a monitored
threshold.
ACFS-05802: The primary replication file system string has numberGB or less space
available per active node.
Cause: The primary replication file system was found to be running low on space.
ACFS-00501 to ACFS-11111 2-53
ACFS-05803: The primary replication file system string has 2GB or less space
available per active node. Replication is being terminated.
Cause: The primary replication file system was found to be too low on space in order
to run efficiently.
Action: Restart replication with a larger primary file system that has free space equal
to at least 4GB per active node.
ACFS-05804: The standby replication file system string is out of sync with the
primary by at least number minutes.
Cause: The time period to process changes on the standby file system was exceeded.
Action: Check that the network connectivity between the primary and standby
replication systems is functional.
ACFS-05805: The standby replication file system string is out of sync with the
primary by at least 60 minutes.
Cause: The standby replication file system finished applying changes from the
primary that were made more than 60 minutes ago. The standby is at least 60 minutes
out of sync with the primary.
ACFS-05806: The primary replication file system string has reached an appropriate
free space level.
Cause: A previously-reported free space shortage in the primary replication file
system was relieved.
Action: None
ACFS-05807: The standby file system string is less than 15 minutes out of sync now.
Cause: A previously-reported out of sync time difference between the standby
replication file system and the primary reached an appropriate out of sync time for
replication to run efficiently.
Action: None
ACFS-05808: The primary replication file system string had an unrecoverable error
and replication has been terminated for that file system.
Cause: The primary file system encountered an unrecoverable error in the kernel that
has caused replication for this file system to be terminated. The cause will be in the
OKS persistent log.
Action: Replication must be restarted. To do this, terminate replication on the standby
file system, run mkfs (Unix or Linux) or acfsformat.exe (Windows) on the volume for
the standby file system, remount that volume, and then restart replication for both file
systems.
ACFS-05809: invalid query of replication apply events on the standby site
Cause: An attempt was made to query the replication apply events on the standby site
which failed because the information is available only on the primary site.
Action: Query the replication apply events from the primary site.
2-54 Error Messages
ACFS-05810: invalid query of replication transport events on the standby site

Cause: An attempt was made to query the replication transport events on the standby
site which failed because the information is available only on the primary site.
Action: Query the replication transport events from the primary site.
ACFS-05811: ACFS replication initialization failed in Oracle Restart environment.
Cause: Initialization failed because the system was configured with Oracle Restart.
ACFS replication is not supported for Oracle Restart configurations.
Action: Initialize ACFS replication in an environment that is configured with single or
multi-node RAC.
ACFS-07016: metadata read failed at disk offset: string size: number bytes
Cause: An attempt to read metadata at the indicated disk offset failed. Refer to the
accompanying message(s) for more information on the problem.
Action: Correct the problem described in the accompanying messages if possible and
rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ACFS-07017: metadata read failed at disk offset: string\n bytes requested: number
bytes returned: number
Cause: A metadata read at the indicated offset was incomplete. The amount of data
returned did not match the amount requested. Refer to the accompanying message(s)
for more information on the problem.
ACFS-07018: metadata write failed at disk offset: string size: number bytes
Cause: An attempt to write metadata at the indicated disk offset failed. Refer to the
Action: If the ACFS Fixer is currently running, then no further action is needed. The
ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run the
ACFS Fixer to resolve the problem.
ACFS-07019: metadata write failed at disk offset: string\n bytes requested: number
bytes written: number bytes
Cause: A metadata write at the indicated offset was incomplete. The amount of data
written did not match the amount requested. Refer to the accompanying message(s)
ACFS-07021: The File_Entry_Table is corrupt and many of the files in the file
system may \nnot be recoverable. It is strongly recommended that the file system
be restored \nfrom a backup copy.
Cause: The ACFS Checker/Fixer found an inconsistency with the File_Entry_Table
metadata. The File_Entry_Table is a critical system structure that is necessary for a
functioning file system.
Action: Restore the file system from a backup copy.
ACFS-07022: I/O request for (disk offset + size): string exceeds file system size:
string\nfor structure:\nstring
Cause: An I/O request was made for data that exceeded the size of the file system."
ACFS-00501 to ACFS-11111 2-55
ACFS-07023: read failed for metadata structure at disk offset: string size: number
bytes\nstructure type: string \nfor structure:\nstring
Cause: An attempt to read a metadata structure from disk failed. Refer to
ACFS-07024: File_Entry_Table entry: string exceeds the maximum value for this file
system: string
Cause: An entry was referenced that exceeded the File_Entry_Table limit.
ACFS-07025: File_Entry_Table entry: string already processed for structure:\nstring
Cause: File_Entry_Table entries must be unique within a file system, but there were
multiple references for this specific entry.
ACFS-07026: file extent exceeds file system size: string\nextent: _FileOffset: string
_Length: string _PhysicalDiskOffset: string\nfor file:\nstring
Cause: The extent values of the indicated file referenced data beyond the size of the
file system. There are two possible causes: 1. The extent _Length and/or
_PhysicalDiskOffset property were incorrect. 2. The file system size value was
incorrect.
ACFS-07027: metadata structure at disk offset: string contains incorrect or invalid
type\n found: string, but expected to find: string or string\nfor structure:\nstring
Cause: The type property of the indicated metadata structure was not valid. The type
must be a DATA extent or a HEADER extent.
ACFS-07028: DATA extent structure has incorrect _granularity value\n found:
number, but expected to find: number\nfor structure:\nstring
Cause: The _granularity property of the indicated DATA extent structure was invalid.
Its value must be -1.
2-56 Error Messages
ACFS-07029: HEADER extent structure has incorrect _granularity value\n found:

number, but expected to find: >= 0\nfor structure:\nstring
Cause: The _granularity property of the indicated HEADER extent structure was
invalid. Its value must be greater than or equal to zero.
ACFS-07030: file has invalid _FE_OsdSecurity value\nfor file:\nstring
Cause: The _FE_OsdSecurity property of the indicated file was invalid.
ACFS-07031: extent structure has incorrect _ExtentOffset value\n found: string, but
expected to find: string\nfor structure:\nstring
Cause: The _ExtentOffset property of the indicated extent structure did not match its
disk offset.
ACFS-07032: extent structure has incorrect _UpHeaderNodePtr value\n found:
string, but expected to find: string\nfor structure:\nstring
Cause: The _UpHeaderNodePtr property of the indicated extent structure was
incorrect. There are two possible causes: 1. The _UpHeaderNodePtr property did not
match its parent. 2. The parent identifier property was incorrect.
ACFS-07033: extent structure has incorrect _granularity value\n found: number, but
expected to find: number\nfor structure:\nstring
Cause: The _granularity property of the indicated extent structure did not match its
calculated depth.
ACFS-07034: extent structure has incorrect _NextFreeExtent value\n found: number
maximum: number\nfor structure:\nstring
Cause: The _NextFreeExtent property of the indicated extent structure was incorrect.
ACFS-07035: extent[number] appears to be uninitialized\nfor structure:\nstring
Cause: An extent of the indicated extent structure appeared to be in use, but all of its
values were zero.
ACFS-00501 to ACFS-11111 2-57
ACFS-07036: extent[number] has invalid _Length value\n found: 0, but expected to

find: > 0\nfor structure:\nstring
Cause: The _Length property of an extent of the indicated extent structure had a value
of zero. _Length values must be greater than zero.
ACFS-07037: extent[number] has incorrect _SnapIncarnationNumber value\n
found: number maximum: number\nfor structure:\nstring
Cause: The _SnapIncarnationNumber property of the indicated extent structure
exceeded the maximum value for the file system.
ACFS-07038: extent[number] has a non-contiguous _FileOffset value\n found:
Cause: The _FileOffset property of an extent of the indicated extent structure was not
contiguous with the _FileOffset of the previous extent.
ACFS-07039: extent[number] is not in use but it contains non-zero values:\n
_FileOffset: string\n _Length: string\n _PhysicalDiskOffset: string\n
_SnapIncarnationNumber: number\nfor structure:\nstring
Cause: An extent of the indicated extent structure was not in use, but it contained
non-zero values. There are two possible causes: 1. The extent values were not reset to
zero when the extent was freed. 2. The _NextFreeExtent property of the extent
structure was incorrect.
ACFS-07040: calculated extent structure allocation size (sum of data sizes) does not
match expected value\n calculated: string, but expected to find:string\nfor
structure:\nstring
Cause: The sum of all valid extents within the indicated extent structure did not
match the value of the corresponding extent in the parent extent structure.
ACFS-07041: DATA extent list not found\nfor file:\nstring
Cause: The list of DATA extent structures of the indicated file did not include the
initial DATA extent structure. There are two possible causes: 1. The
_LastExtentPointer property of the file was incorrect. 2. The structure identified by
the _LastExtentPointer value was not a DATA extent structure.
2-58 Error Messages
ACFS-07042: DATA extent node list missing entry for extent structure:\nstring
Cause: The list of DATA extent structures of the indicated file was incomplete. One or
more DATA extent structures was missing. There are three possible causes: 1. The
the _LastExtentPointer value was not a valid DATA extent structure. 3. The
_NextDataExtent property of one or more DATA extent structures was incorrect.
ACFS-07043: metadata structure has invalid or incorrect type:\n found: string, but
Cause: The type property of the indicated metadata structure did not match the type
expected for this structure.
ACFS-07044: DATA extent list has more nodes than expected\n found: number, but
expected to find: number\nfor file:\nstring
Cause: The list of DATA extent structures of the indicated file contained more nodes
than expected. The _NextDataExtent property of one or more DATA extent structures
was incorrect.
ACFS-07045: DATA extent list has fewer nodes than expected\n found: number, but
Cause: The list of DATA extent structures of the indicated file contained fewer nodes
than expected. There are two possible causes: 1. One or more of the DATA extent
structures did not have a valid structure header. 2. The _NextDataExtent property of
one or more DATA extent structures was incorrect.
ACFS-07046: file has _LastExtentPointer that does not match calculated value\n
calculated: string, but expected to find: string\nfor file:\nstring
Cause: The _LastExtentPointer property of the indicated file did not match the file's
last DATA extent structure. There are three possible causes: 1. The _LastExtentPointer
value was incorrect. 2. The last DATA extent structure was not found because the The
ACFS-07047: extent node list missing entry for extent structure:\nstring
Cause: The list of extent structures of the indicated file was incomplete. One or more
extent structures was missing. There are three possible causes: 1. The
_LastExtentPointer property of the file was incorrect. 2. One or more extent structures
ACFS-00501 to ACFS-11111 2-59
did not have a valid structure header. 3. The _LastExtentPointer property of one or
more extent structures was incorrect.
ACFS-07048: metadata structure has invalid _generation_number value\n found:
Cause: The _generation_number property of the indicated metadata structure was
incorrect.
ACFS-07049: extent list has more nodes than expected\n found: number, but
Cause: The list extent structures of the indicated file contained more nodes than
expected. The _LastExtentPointer property of one or more extent structures was
incorrect.
ACFS-07050: extent list has fewer nodes than expected\n found: number, but
Cause: The list of extent structures of the indicated file contained fewer nodes than
expected. There are two possible causes: 1. One or more of the extent structures did
not have a valid structure header. 2. The _LastExtentPointer property of one or more
extent structures was incorrect.
ACFS-07051: file has incorrect _LinkCount value\n found: number, but expected to
find: number\nfor file:\nstring
Cause: The _LinkCount property of the indicated file did not match the number of
hard links found for the file. There are four possible causes: 1. The _LinkCount
property was incorrect. 2. One or more directory entries for this file was invalid or
was not found. 3. A Directory_Entry structure for this file had an incorrect file
identifier. 4. The _LinkCount property of an ACFS Internal File was not equal to one.
ACFS-07052: file has invalid _ProtectionBits value\n found: number, but expected
to find: number\nfor file:\nstring
Cause: The _ProtectionBits property of the indicated files was incorrect.
2-60 Error Messages
ACFS-07053: file has invalid _ParentID value\n found: string, but expected to find:
string\nfor file:\nstring
Cause: The _ParentID property of the indicated file was not correct. There are two
possible causes: 1. The _ParentID value did not match the file's parent directory. 2.
The _ParentID value did not match any valid directory.
ACFS-07054: file has invalid _WindowsAttributes value(s)\n found: string\n, but
expected to find: 0\nfor file:\nstring
Cause: The _WindowsAttributes property of the indicated file was invalid. The
_WindowsAttributes value must be zero since file was not created on a Windows
system.
_FileOffset: string\n _Length: string\n _PhysicalDiskOffset: string\nfor file:
\nstring
Cause: One of the extents of the indicated file was not in use, but it contained nonzero values. There are two possible causes: 1. The extent values were not reset to zero
when the extent was freed. 2. The _NextFreeExtent property of the file was incorrect.
ACFS-07057: extent[number] has incorrect _FileOffset\n found: string, but expected
to find: 0\nfor file:\nstring
Cause: The _FileOffset property of the initial extent of the indicated file was not zero.
The _FileOffset for a file's initial extent must be zero as it identifies the beginning of
the file.
ACFS-07058: file with local extents has invalid _LastExtentPointer value\n found:
string, but expected to find: 0\nfor file:\nstring
Cause: The _LastExtentPointer property of the indicated file was not zero which is
required for files with local extents.
ACFS-07060: extent[number] appears to be uninitialized\nfor file:\nstring
Cause: An extent of the indicated file appeared to be in use, but all of its values were
zero.
ACFS-00501 to ACFS-11111 2-61
ACFS-07061: extent[number] has invalid _Length value\n found: 0, but expected to

find: > 0\nfor file:\nstring
Cause: The _Length property of an extent of the indicated file had a value of zero.
_Length values must be greater than zero.
ACFS-07062: extent[number] has incorrect _SnapIncarnationNumber value\n
found: number maximum: number\nfor file:\nstring
Cause: The _SnapIncarnationNumber property of the indicated file exceeded the
maximum value for the file system.
ACFS-07063: extent[number] has a non-contiguous _FileOffset value\n found:
string, but expected to find: string\nfor file:\nstring
Cause: The _FileOffset property of an extent of the indicated file was not contiguous
with the _FileOffset of the previous extent.
ACFS Fixer to resolve the problem
ACFS-07064: file _AllocationSize value not equal to sum of extents\n found: string,
but expected to find: string\nfor file:\nstring
Cause: The _AllocationSize property of the indicated file was not equal to the sum of
the _Length properties of the file's extents. There are three possible causes: 1. The
_AllocationSize value was incorrect. 2. The _Length property of one or more of the
file's extents was incorrect. 3. The _NextFreeExtent property of the file was incorrect.
ACFS-07065: File_Entry_Table calculated allocation size (sum of data extents) does
not match its _FileSize value\n found: string calculated: string\nfor file:\nstring
Cause: The _FileSize property of File_Entry_Table did not match the sum of the file's
extent _Length values. There are two possible causes: 1. The _Length property of one
or more extents of the File_Entry_Table was incorrect. 2. The _FileSize property of the
File_Entry_Table was incorrect.
_SnapIncarnationNumber: number\nfor file:\nstring
2-62 Error Messages
ACFS-07073: file has _FileEntry structure with incorrect or invalid _FileEntryType
value\n found: string, but expected to find: string\nfor file:\nstring
Cause: The _FileEntryType property of the indicated file did not match its expected
value. There are two possible causes: 1. The _FileEntryType value was incorrect for
this particular file. 2. The _FileEntryType value was not on the list of valid values.
ACFS-07074: file has _FileEntry structure with incorrect file identifier\n found:
Cause: The file identifier property of the indicated file did not match its position
within the File_Entry_Table entry.
ACFS-07075: file has incorrect _FileSize value\n found: string minimum: string
\nfor file:\nstring
Cause: The _FileSize property of the indicated file was incorrect.
ACFS-07076: file has invalid _AllocationSize value\n found: string minimum:
Cause: The _AllocationSize property of the indicated file was invalid. The
_AllocationSize value for this file cannot be less than the value described in the
message.
ACFS-07077: Local_Bitmap has incorrect _FileOffset value for Extent[1]\n found:
Cause: The _FileOffset property in Extent[1] of the indicated Local_Bitmap was not
zero.
ACFS-07078: Local_Bitmap has incorrect _Length value in Extent[1]\n found:
Cause: The _Length property in Extent[1] of the indicated Local_Bitmap did not
match the file system's allocation unit size.
ACFS-00501 to ACFS-11111 2-63
ACFS-07079: Local_Bitmap has invalid _PhysicalDiskOffset value for Extent[1]\n

found: 0, but expected to find: > 0\nfor file:\nstring
Cause: The _PhysicalDiskOffset property in Extent[1] of the indicated Local_Bitmap
was equal to zero. This _PhysicalDiskOffset value must be greater than zero.
ACFS-07080: Local_Bitmap has incorrect _PhysicalDiskOffset value for Extent[1]\n
found: string maximum: string\nfor file:\nstring
exceeded the size of the file system.
Action: n/a
ACFS-07081: file has invalid _granularity value\n found: number, but expected to
Cause: The _granularity property of the indicated system file was incorrect. Many
system files require local extents which is indicated by a _granularity value of -1.
ACFS-07082: Global_BitMap space requirement exceeds _AllocationSize value.
Bitmap requires string bytes, allocated space: string bytes\nfor file:\nstring
Cause: The _AllocationSize property of the Global_BitMap was not large enough to
store the Global_BitMap data. There are two possible causes: 1. The _AllocationSize
value was incorrect. 2. The value used to indicate the number of bits needed to map
file system storage was incorrect.
ACFS-07083: Global_BitMap has invalid _granularity value\n found: number, but
Cause: The _granularity property of the indicated Global_BitMap was incorrect. The
Global_BitMap file must have a _granularity value of -1 which indicates that the file
has local extents.
ACFS-07084: Snap_Map has mismatch between _FileSize and _AllocationSize
values\n _FileSize: string _AllocationSize: string\nfor file:\nstring
Cause: The _FileSize and _AllocationSize properties of the indicated Snap_Map file
did not match. The values for these properties must match for a Snap_Map file. One
or both values was incorrect.
2-64 Error Messages
ACFS-07085: file has _FileSize value that exceeds _AllocationSize value\n

_FileSize: string _AllocationSize: string\nfor file:\nstring
Cause: The _FileSize property of the indicated file exceeded the amount of storage
allocated to the file. The _AllocationSize property describes the amount of storage
available for the file. One of of these properties was incorrect.
ACFS-07086: file has _AllocationSize value that is invalid for the file system\n
found: string, but expected to find: multiple of string\nfor file:\nstring
Cause: The _AllocationSize property of the indicated file was incorrect. Its value must
be a multiple of the file system allocation unit size.
ACFS-07087: file has _AllocationSize value but no extent information\n
_AllocationSize: string\nfor file:\nstring
Cause: The _AllocationSize property of the indicated file was greater than 0, but there
was no corresponding extent information. There are two possible causes: 1. The
_AllocationSize should have been zero. 2. The _NextFreeExtent value was incorrect.
ACFS-07088: Map_File has incorrect _FileSize value\n found: string, but expected
to find: multiple of number\nfor file:\nstring
Cause: The _FileSize property of the indicated Map_File was incorrect. The _FileSize
value for a Map_File must be a multiple of the META_MAP_ENTRY size.
ACFS-07089: Volume_Log has invalid _FileSize value\n found: string, but expected
to find: 0\nfor file:\nstring
Cause: The _FileSize property of the indicated Volume_Log file was not equal to zero.
The _FileSize value for a Volume_Log must be zero.
ACFS-07090: Volume_Log has invalid _granularity value\n found: number, but
Cause: The _granularity property of the indicated Volume_Log file was incorrect.
Volume_Log files must have a _granularity value of -1 which indicates that the file
has local extents.
ACFS-00501 to ACFS-11111 2-65
ACFS-07091: Volume_Log has incorrect _NextFreeExtent value\n found: number,

but expected to find: 0 or 1\nfor file:\nstring
Cause: The _NextFreeExtent property of the indicated Volume_Log file was incorrect.
A Volume_Log file can have at most one extent.
ACFS-07092: file has invalid _security_data_offset value\nfor file:\nstring
Cause: The _security_data_offset property of the indicated file did not have a
corresponding entry in any Security_Metadata file. There are three possible causes: 1.
The _security_data value was incorrect. 2. The Security_Metadata file had incorrect
data at the corresponding offset. 3. The Security_Metadata file was not found.
ACFS-07094: file has invalid _SnapMetaIncarnationNumber value\n found:
number maximum: number\nfor file:\nstring
maximum _SnapIncarnationNumber value for the file system.
ACFS-07095: CHARACTER special file has invalid major_device_number value\n
Cause: The major_device_number property of the indicated CHARACTER special file
was invalid. major_device_number values must be greater than zero.
ACFS-07096: file has incorrect _EAOffset value\n found: string, but expected to
find: string\nfor file:\nstring
Cause: The _EAOffset property of the indicated file was incorrect.
ACFS-07097: file has invalid _TimeofCreation value\n found: string, but expected
to find: string\nfor file:\nstring
Cause: The _TimeofCreation property of the indicated file was incorrect.
ACFS-07098: file has invalid _TimeLastAccessed value\n found: string, but
expected to find: string\nfor file:\nstring
Cause: The _TimeLastAccessed property of the indicated file was incorrect.
2-66 Error Messages
ACFS-07099: file has invalid _TimeLastModified value\n found: string, but
Cause: The _TimeLastModified property of the indicated file was incorrect.
ACFS-07100: file has invalid _FileSize value\n found: string minimum: string\nfor
file:\nstring
Cause: The _FileSize property of the indicated file was invalid. The _FileSize value for
this file cannot be less than the value described in the message.
ACFS-07101: file has invalid _TimeLastChanged value\n found: string, but
Cause: The _TimeLastChanged property of the indicated file was incorrect.
ACFS-07102: file has invalid _TimeofCreation value\n found: 0\nfor file:\nstring
Cause: The _TimeofCreation property of the indicated file was invalid. The
_TimeofCreation value must be non-zero.
ACFS-07103: file has invalid _TimeLastAccessed value\n found: 0\nfor file:
\nstring
Cause: The _TimeLastAccessed property of the indicated file was invalid. The
_TimeLastAccessed value must be non-zero.
ACFS-07104: file has invalid _TimeLastModified value\n found: 0\nfor file:
\nstring
Cause: The _TimeLastModified property of the indicated file was invalid. The
_TimeLastModified value must be non-zero.
ACFS-07105: file has invalid _TimeLastChanged value\n found: 0\nfor file:
\nstring
Cause: The _TimeLastChanged property of the indicated file was invalid. The
_TimeLastChanged value must be non-zero.
ACFS-00501 to ACFS-11111 2-67
ACFS-07106: file has invalid _WindowsAttributes value(s)\n found: string\n valid
values: string\nfor file:\nstring
Cause: The _WindowsAttributes property of the indicated file was invalid. One or
more of the _WindowsAttributes values were not within the range of valid values.
Refer to the corresponding messages for a list of valid values.
ACFS-07107: file has incorrect _rep_incarnation value\n found: number, but
Cause: The _repFE_incarnation_number property of the indicated file was incorrect.
ACFS-07108: file has incorrect _rep_VFN value\n found: string, but expected to
Cause: The _rep_VFN property of the indicated file was incorrect.
ACFS-07109: file has incorrect _rep_SCN value\n found: string, but expected to
Cause: The _rep_SCN property of the indicated file was incorrect.
ACFS-07110: file has incorrect _EncrMetaOffset value\n found: string, but expected
Cause: The _EncrMetaOffset property of the indicated file was incorrect.
ACFS-07111: file has incorrect _Vault_MetaOffset value\n found: string, but
Cause: The _Vault_MetaOffset property of the indicated file was incorrect.
ACFS-07112: file has incorrect _EncrSecFlags value\n found: string, but expected to
Cause: The _EncrSecFlags property of the indicated file was incorrect.
2-68 Error Messages
ACFS-07113: file has incorrect _EA_ContainerUnits value\n found: number, but
Cause: The _EA_ContainerUnits property of the indicated file was incorrect.
ACFS-07115: Local_Bitmap has incorrect _FileSize value\n found: string, but
Cause: The _FileSize property of the indicated Local_Bitmap was invalid. The
_FileSize value for a Local_Bitmap must be zero.
ACFS-07116: BLOCK special file has invalid major_device_number value\n found:
0, but expected to find: > 0\nfor file:\nstring
Cause: The major_device_number property of the indicated BLOCK special file was
invalid. major_device_number values must be greater than zero.
ACFS-07117: Directory_Entry structure has invalid file identifier value:\n found:
string maximum: string\nfor structure:\nstring
Cause: The file identifier property of the indicated Directory_Entry structure
exceeded the maximum file identifier for the file system.
ACFS-07118: System metadata file is corrupt and cannot be repaired\nfor file:
\nstring
Cause: The ACFS Checker/Fixer found an inconsistency with the indicated system
metadata file. This metadata file cannot be repaired due to the nature of the
corruption.
ACFS-07119: _Locator structure has incorrect _global_dir_blk value\n found:
Cause: The _global_dir_blk property of the indicated structure was incorrect.
ACFS-07120: _Locator structure has invalid node identifier for entry number in
_node_number array\n found: number maximum: number\nfor structure:\nstring
Cause: A node identifier in the _node_number array of the indicated structure that
ACFS-00501 to ACFS-11111 2-69
ACFS-07121: _Locator structure has invalid file identifier for entry number in
_local_dir_blk array\n found: string maximum: string\nfor structure:\nstring
Cause: A file identifier for a Local_Metadata_Directory in the _local_dir_blk array of
the indicated _Locator structure exceeded the maximum file identifier for the file
system.
ACFS-07122: _Locator structure has incorrect _local_dir_blk_disk_offset for entry
number in _local_dir_blk_disk_offset array\n found: string, but expected to find:
Cause: The disk offset for a Local_Metadata_Directory in the
_local_dir_blk_disk_offset array of the indicated _Locator structure was incorrect.
There are two possible causes: 1. The _local_dir_blk_disk_offset value was incorrect.
2. The structure at the _local_dir_blk_disk_offset was not a Local_Metadata_Directory
structure.
ACFS-07123: _Locator structure has duplicate entries for node number\nfor
structure:\nstring
Cause: There was more than one entry for the same node within the _Locator
structure(s). Node identifies must be unique.
ACFS-07124: _Locator structure has duplicate entries for Local_Metadata_Directory:
Cause: There was more than one entry for the same Local_Metadata_Directory within
the _Locator structure(s). Local_Metadata_Directory file identifiers must be unique.
ACFS-07125: _Locator structure has incorrect _node_count value\n found: number,
but expected to find: number\nfor structure:\nstring
Cause: The _node_count property of the indicated _Locator structure did not match
the number of valid nodes found.
ACFS-07126: _Locator structure has incorrect _next_locator_blk_disk_offset value
\n found: string\nfor structure:\nstring
Cause: The _next_locator_blk_disk_offset property of the indicated _Locator structure
was incorrect. There are two possible causes: 1. The _next_locator_blk_disk_offset
2-70 Error Messages
was incorrect. 2. The structure at the _next_locator_blk_disk_offset was not a _Locator

structure.
ACFS-07127: Global_Virtual_FileID_Pool structure has incorrect
_repFreeVFNGroup value\n found: string, but expected to find: string\nfor
structure:\nstring
Cause: The _repFreeVFNGroup property of the indicated Global_Virtual_FileID_Pool
ACFS-07128: Global_Virtual_FileID_Pool structure has incorrect
_repFreeVFNIncarnNum value\n found: string, but expected to find: string\nfor
structure:\nstring
Cause: The _repFreeVFNIncarnNum property of the indicated
Global_Virtual_FileID_Pool structure was incorrect.
ACFS-07129: Replication_Log_Initiator structure has incorrect _initiator_node_id
value\n found: number, but expected to find: number\nfor structure:\nstring
Cause: The _initiator_node_id property of the indicated Replication_Log_Initiator
ACFS-07130: Replication_Log_Initiator structure has incorrect
_new_rlog_recovered value\n found: number, but expected to find: number\nfor
structure:\nstring
Cause: The _it_rep_logs_processed property of the indicated
Replication_Log_Initiator structure was incorrect.
ACFS-07131: Replication_Log_Initiator structure has incorrect _next_cord_id value
\n found: string, but expected to find: string\nfor structure:\nstring
Cause: The _next_cord_id property of the indicated Replication_Log_Initiator
ACFS-00501 to ACFS-11111 2-71
ACFS-07132: Replication_Log_Initiator structure has incorrect _next_segment_id

value\n found: string, but expected to find: string\nfor structure:\nstring
Cause: The _next_segment_id property of the indicated Replication_Log_Initiator
ACFS-07133: Local_Bitmap has incorrect _AllocationSize value\n found: string, but
Cause: The _AllocationSize property of the indicated Local_Bitmap did not match the
_Length value of its first extent.
ACFS-07134: invalid global_dir_fileid value\n found: string, but expected to find:
string
Cause: The ACFS Checker/Fixer found an inconsistency within the file system.
ACFS-07135: Global_Metadata_Directory structure has incorrect _node_number
Cause: The _node_number property of the indicated Global_Metadata_Directory
ACFS-07136: Global_Metadata_Directory structure has incorrect
_global_free_blk_list value\n found: string, but expected to find: string\nfor
structure:\nstring
Cause: The _global_free_blk_list property of the indicated
Global_Metadata_Directory structure was incorrect.
_global_bitmap_fileid value\n found: string, but expected to find: string\nfor
structure:\nstring
Cause: The _global_bitmap_fileid property of the indicated
2-72 Error Messages

_SuperBlock_fileid value\n found: string, but expected to find: string\nfor
structure:\nstring
Cause: The _SuperBlock_fileid property of the indicated Global_Metadata_Directory
ACFS-07139: Global_Metadata_Directory structure has incorrect _gdrfl_fileid value
Cause: The _gdrfl_fileid property of the indicated Global_Metadata_Directory
ACFS-07140: Global_Metadata_Directory structure has incorrect _dotofs_dir_fileid
Cause: The _dotofs_dir_fileid property of the indicated Global_Metadata_Directory
ACFS-07141: Global_Metadata_Directory structure has incorrect _ready_dir_fileid
Cause: The _ready_dir_fileid property of the indicated Global_Metadata_Directory
_repl_config_fileid value\n found: string, but expected to find: string\nfor
structure:\nstring
Cause: The _repl_config_fileid property of the indicated Global_Metadata_Directory
ACFS-07143: Global_Metadata_Directory structure has incorrect _mmap_log_fileid
Cause: The _mmap_log_fileid property of the indicated Global_Metadata_Directory
ACFS-00501 to ACFS-11111 2-73

_repGlobalVFNPool_fileid value\n found: string, but expected to find: string\nfor
structure:\nstring
Cause: The _repGlobalVFNPool_fileid property of the indicated
_repl_config_tbl_fileid value\n found: string, but expected to find: string\nfor
structure:\nstring
Cause: The _repl_config_tbl_fileid property of the indicated
_repLogCutInitiatorBlock_fileid value\n found: string, but expected to find: string
\nfor structure:\nstring
Cause: The _repLogCutInitiatorBlock_fileid property of the indicated
_repLogCutInitiatorBlock_offset value\n found: string, but expected to find: string
Cause: The _repLogCutInitiatorBlock_offset property of the indicated
ACFS-07148: Global_Metadata_Directory structure has incorrect _snap_map_fileid
Cause: The _snap_map_fileid property of the indicated Global_Metadata_Directory
ACFS-07149: Global_Metadata_Directory structure has incorrect _snaps_dir_fileid
Cause: The _snaps_dir_fileid property of the indicated Global_Metadata_Directory
2-74 Error Messages

_global_tagdir_fileid value\n found: string, but expected to find: string\nfor
structure:\nstring
Cause: The _global_tagdir_fileid property of the indicated
ACFS-07151: Global_Metadata_Directory structure has incorrect _ea_change_fileid
Cause: The _ea_change_fileid property of the indicated Global_Metadata_Directory
ACFS-07152: orphan directory 'string' (file identifier: string) \nadded to 'lost
+found' directory
Cause: The indicated directory did not have a valid entry in any parent directory. The
ACFS Fixer move the file to the 'lost+found' directory.
Action: No further action is needed.
ACFS-07154: An attempt to create a low-fragmentation memory heap failed.
\nstring will attempt to continue with the standard memory heap but may run out
of memory.
Cause: A call to the Windows HeapCreate function failed. Refer to the accompanying
message(s) for more information on the error.
Action: No further action is required unless there is an error using the standard
memory heap. If there is an error using the standard memory heap then refer to the
accompanying message(s) for information to resolve the problem.
ACFS-07155: An attempt to initialize a low-fragmentation memory heap failed.
of memory.
Cause: A call to the Windows HeapSetInformation function failed. Refer to the
accompanying message(s) for more information on the error.
Action: The program will automatically attempt to continue with the standard
memory heap but could run out of memory. No further action is required unless there
is an error using the standard memory heap. To use low-fragmentation heaps, refer to
Microsoft documentation on GlobalFlags values for executables that are not
compatible with low-fragmentation heaps. Then use the regedit utility to unset those
flags on the executable.
ACFS-07156: Local_Metadata_Directory structure has incorrect
_map_file_disk_offset value\n found: string, but expected to find: string\nfor
structure:\nstring
Cause: The _map_file_disk_offset property of the indicated
Local_Metadata_Directory structure was incorrect.
ACFS-00501 to ACFS-11111 2-75

_vol_log_disk_offset value\n found: string, but expected to find: string\nfor
structure:\nstring
Cause: The _vol_log_disk_offset property of the indicated Local_Metadata_Directory
ACFS-07158: unable to create Security_Metadata file offset list\nfor file:\nstring
Cause: The ACFS Checker could not create the Security_Metadata file offset list. Refer
to the accompanying message(s) for more information on the problem.
ACFS-07159: Local_Metadata_Directory structure has incorrect _smf_fileid value \n
found: string, but expected to find: string\nfor structure:\nstring
Cause: The _smf_fileid property of the indicated Local_Metadata_Directory structure
was incorrect.
ACFS-07160: Local_Metadata_Directory structure has incorrect _it_rlog_fileid value
Cause: The _it_rlog_fileid property of the indicated Local_Metadata_Directory
ACFS-07161: Local_Metadata_Directory structure has incorrect _rlog_fileid value\n
Cause: The _rlog_fileid property of the indicated Local_Metadata_Directory structure
was incorrect.
ACFS-07162: Local_Metadata_Directory structure has incorrect _it_rmap_file_fileid
Cause: The _it_rmap_file_fileid property of the indicated Local_Metadata_Directory
ACFS-07163: Local_Metadata_Directory structure has incorrect _rmap_file_fileid
Cause: The _rmap_file_fileid property of the indicated Local_Metadata_Directory
2-76 Error Messages
_repLocalVFNPool_fileid value\n found: string, but expected to find: string\nfor
structure:\nstring
Cause: The _repLocalVFNPool_fileid property of the indicated
ACFS-07165: invalid file identifier: string
Cause: The file identifier enetered must be a valid numeric value, greater than or
equal to 0, and less than the maximum file identifier value for the file system.
Action: Re-enter a valid file identifier value.
ACFS-07168: Global_BitMap has incorrect value for bitmap size\n found: string,
Cause: The bitmap size property of the indicated Global_BitMap file was incorrect. Its
value did not the bitmap size that was calculated for the file system.
ACFS-07169: Global_BitMap has incorrect _AllocationSize value\n found: string,
Cause: The _AllocationSize property of the indicated Global_BitMap file was
incorrect. The _AllocationSize value was not large enough to store the Global_BitMap
data as determined by the ACFS Checker.
ACFS-07170: Global_BitMap has incorrect values for Extent[0]\n found:
_FileOffset: string _Length: string _PhysicalDiskOffset: string\n, but expected to
find: _FileOffset: string _Length: string _PhysicalDiskOffset: string\nfor file:
\nstring
Cause: The _PhysicalDiskOffset property of the first extent of the indicated
Global_BitMap file was incorrect. The Global_BitMap data must begin at the disk
offset described in the message.
ACFS-07171: attempt to read SuperBlock FileEntry failed\nfor file:\nstring
Cause: An attempt to read SuperBlock metadata failed. Refer to the accompanying
message(s) for more information on the problem.
ACFS-00501 to ACFS-11111 2-77
ACFS-07172: file has incorrect values for Extent[number] \n found: _FileOffset:

string _Length: string _PhysicalDiskOffset: string \n, but expected to find:
_FileOffset: string _Length: string _PhysicalDiskOffset: string \nfor file:\nstring
Cause: One or more values of an extent of the indicated file was incorrect.
ACFS-07175: file has incorrect values for Extent[number]\n found: _FileOffset:
string _Length: string \n, but expected to find: _FileOffset: string _Length: string
\nfor file: \nstring
ACFS-07176: file has invalid _AllocationSize value\n found: string, but expected to
Cause: The _AllocationSize property of the indicated file was incorrect.
ACFS-07177: file has incorrect _FileSize value\n found: string, but expected to find:
ACFS-07178: file has incorrect _granularity value\n found: number, but expected to
Cause: The _granularity property of the indicated file was incorrect. Some ACFS
internal files must have a _granularity value equal to -1 which indicates that the file
has local extents.
ACFS-07179: file has incorrect _NextFreeExtent value\n found: number, but
Cause: The _NextFreeExtent property of the indicated file was incorrect.
ACFS-07180: There is an inconsistency between the ACFS Map_File and the ACFS
Log_File.
Cause: An inconsistency was found between the ACFS Map and Log Files which
prevented the processing of transaction data.
2-78 Error Messages
ACFS-07184: Log_File not processed for node number\nfor file:\nstring
Cause: A Log_File was found but not processed. Unprocessed Log_Files could result
in false errors being reported because transaction data was not applied to the file
system.
Action: There are two actions possible: 1. Run the ACFS Fixer which will
automatically process all valid Log_Files. 2. Run the ACFS Checker and respond yes
to any question pertaining to Log_File processing.
ACFS-07185: The ACFS Map _FileSize: number indicates that there is transaction
data \nto be processed, but the ACFS Log _AllocationSize: number indicates that
\nthere is no data available. \nACFS Map_File:\nstring \nACFS Log_File: \nfor
file: \nstring
ACFS-07188: Map_File has entry with incorrect _Length value\n found: number
\nfor file:\nstring
Cause: There are two possible causes: 1. The Map_File entry's _Length was equal to
zero. 2. The Map_File entry's _Length was not a multiple of the volume's sector size as
detailed in the message.
ACFS-07189: Map_File has entry with incorrect _ActualDiskOffset value\n found:
string minimum: string\nfor file:\nstring
Cause: The _ActualDiskOffset property for an entry in the indicated Map_File was
incorrect. The _ActualDiskOffset value in a Map_File entry must be greater than the
previous entry's _ActualDiskOffset.
ACFS-07190: Map_File has an entry with invalid _LogDiskOffset value\n found:
string minimum: string maximum: string\nfor file:\nstring
Cause: The _LogDiskOffset property for an entry in the indicated Map_File was
incorrect. The _LogDiskOffset value in a Map_File entry must be within the
corresponding Log_File data.
ACFS-07191: Map_File has duplicate entries for _ActualDiskOffset:string\nfor file:
\nstring
Cause: The indicated Map_File contained more than one entry for the same disk
offset. _ActualDiskOffset values must be unique within a Map File.
ACFS-00501 to ACFS-11111 2-79
ACFS-07192: Map_File has incorrect Map_Entry _Length for the
Volume_Disk_Header\n found: number, but expected to find: number\nfor file:
\nstring
Cause: The _Length property for an entry in the indicated Map_File was incorrect.
The entry was for a Volume_Disk_Header structure, but its _Length value did not
match the size of a Volume_Disk_Header structure.
ACFS-07193: Map_File entry with an invalid _ActualDiskOffset value\n found:
string maximum: string\nfor file:\nstring
incorrect. The _ActualDiskOffset value that exceeded the size of this file system.
ACFS-07195: metadata write failed while processing Volume_Log transaction data
at disk offset: string\nfor file:\nstring
Cause: An error occurred while writing Volume_Log transaction data to the file
system. Refer to the accompanying message(s) for more information.
ACFS-07196: write failed for Map_File metadata structure at disk offset: string size:
number bytes\nstructure type: string \nfor file:\nstring
Cause: An attempt to write a metadata structure to disk failed. Refer to accompanying
ACFS-07197: discarding Volume_Log and Map_File contents on node number due
to processing error
Cause: An error occurred while processing file system transaction data. Refer to the
ACFS-07199: write failed for Volume_Log metadata structure at disk offset: string
size: number bytes\nstructure type: string \nfor file:\nstring
Cause: An attempt to update a metadata structure of the indicated Volume_Log file
failed. Refer to accompanying message(s) for more information on the problem.
2-80 Error Messages
ACFS-07200: duplicate _SnapFetaFenum: string found for the following snapshots:

\n
Cause: The _SnapFetaFenum property of the indicated snapshots had the same value.
_SnapFetaFenum values must be unique.
Action: If the message was generated by the ACFS Fixer, then no further action is
needed. The ACFS Fixer will resolve the problem. If the message was generated by
the ACFS Checker, then run the ACFS Fixer to resolve the problem. Frequent
metadata inconsistencies may point to internal errors. In this case, contact Oracle
Support Services.
ACFS-07201: Global_Free_Block list is corrupt
Cause: A metadata inconsistency was found within the Global_Free_Block list for the
file system.
ACFS-07202: Free_Block_List has incorrect _free_blk_count value\n found: string,
but expected to find: string\nfor structure:\nstring
Cause: The _free_blk_count property of the indicated Free_Block_List was incorrect.
ACFS-07203: results for Snap_Map data may be limited or incorrect due to
inconsistencies with Snap_Map metadata
Cause: The acfsdbg utility has identified the metadata inconsistency reported in the
accompanying message.
Action: Run the ACFS Fixer to resolve the problem. Frequent metadata
inconsistencies may point to internal errors. In this case, contact Oracle Support
Services.
ACFS-07204: write failed for Global_BitMap metadata structure at disk offset:
string size: number bytes\nstructure type: string \nfor file:\nstring
Cause: An attempt to update a metadata structure of the indicated Global_BitMap file
ACFS-07205: functionality may be limited due to File_Entry_Table metadata
inconsistency
Services.
ACFS-07206: read failed for Local_BitMap metadata structure at disk offset: string
Cause: An attempt to read a metadata structure of the indicated Local_BitMap file
ACFS-00501 to ACFS-11111 2-81
ACFS-07207: functionality related to snapshots disabled due to problems accessing
Snap_Map file
Services.
ACFS-07208: Local_BitMap (file identifier: string) has incorrect size\n found:
string, but expected to find: string \nfor file:\nstring
Cause: The size property of the indicated Local_BitMap was incorrect.
ACFS-07209: Local_BitMap (file identifier: string) has incorrect Global_BitMap file
offset: string or incorrect disk offset: string \nfor file:\nstring
Cause: The Global_BitMap offset property of the indicated Local_BitMap was
incorrect.
ACFS-07211: mismatch between Local_BitMap (file identifier: string) and
temporary Global_BitMap for disk offset: string
Cause: The bitmap data of the indicated Local_BitMap did not match the
corresponding bitmap data of the temporary Global_BitMap for the described disk
offset.
ACFS-07212: temporary Global_BitMap bit set for disk offset: string exceeds
maximum offset: string
Cause: The bitmap data of the temporary Global_BitMap referenced storage that is
beyond the size of this file system.
ACFS-07215: Volume_Disk_Header has invalid _VolSignature value\n found:
'string'\n, but expected to find: string, string, string, or string\nfor structure:
\nstring
Cause: The _VolSignature property of the indicated Volume_Disk_Header was not a
valid ACFS volume signature.
2-82 Error Messages
ACFS-07216: Volume_Disk_Header has incorrect _Checksum value\n found:

Cause: The _Checksum property of the indicated Volume_Disk_Header did not
match its calculated value.
ACFS-07217: Volume_Disk_Header version does not match string version\n found:
number.number, but expected to find: number.number\nfor structure:\nstring
Cause: The _MajorVersionNumber and _MinorVersionNumber properties of the
indicated Volume_Disk_Header did not match the version of the ACFS Checker/
Fixer or ACFS debug utility that was being used. The ACFS Checker/Fixer or ACFS
debug utility was not compatible with this file system. There are two possible causes:
1. The version information in the Volume_Disk_Header structure was not correct. 2.
The ACFS Checker/Fixer or ACFS debug utility was not the correct version for the
file system.
Action: There are two possible actions: 1. If the file system version displayed in the
message is valid then run a compatible version of the ACFS Checker/Fixer or ACFS
debug utility. 2. If the file system version displayed in the message is not valid then
restore the file system from backup.
ACFS-07218: Volume_Disk_Header has incorrect _VolVolumeSize value\n found:
string maximum: string\n- temporarily assuming Volume Size: string\nfor
structure:\nstring
Cause: The _VolVolumeSize property of the indicated Volume_Disk_Header
exceeded the size of the volume. The ACFS Checker temporarily assumed the
maximum volume size during processing.
string minimum: string\n- temporarily assuming Volume Size: string\nfor
structure:\nstring
Cause: The _VolVolumeSize property of the indicated Volume_Disk_Header was less
than the minimum supported volume size as detailed in the message. The ACFS
Checker temporarily assumed the maximum volume size during processing.
ACFS-07220: Volume_Disk_Header has incorrect _VolClusterSize value\n found:
string, but expected to find: string\n- assuming default size: string\nfor structure:
\nstring
Cause: The _VolClusterSize property of the indicated Volume_Disk_Header was
incorrect. The ACFS Checker temporarily assumed the default value during
processing.
ACFS-00501 to ACFS-11111 2-83
ACFS-07221: Volume_Disk_Header has incorrect _VolFETALPosition value\n

found: string, but expected to find: string\n- assuming default File_Entry_Table
offset: string\nfor structure:\nstring
Cause: The _VolFETALPosition property of the indicated Volume_Disk_Header was
incorrect. The ACFS Checker temporarily assumed the default File_Entry_Table offset
during processing.
ACFS-07222: Volume_Disk_Header has incorrect _VolOrigVolumeSize value\n
found: string must be aligned on a string byte boundary\nfor structure:\nstring
ACFS-07223: Volume_Disk_Header has incorrect _VolExtentHeaderSize value\n
found: string, but expected to find: string\n- assuming default value: string\nfor
structure:\nstring
Cause: The _VolExtentHeaderSize property of the indicated Volume_Disk_Header
was incorrect. The ACFS Checker temporarily assumed the default value during
processing.
ACFS-07224: cannot process command due to Snap_Map File metadata
inconsistency
Cause: An acfsdbg command was not executed due to a metadata inconsistency.
Services.
ACFS-07225: Volume_Disk_Header has invalid _VolFileSystemEndian value\n
found: character, but expected to find: string or string\nfor structure:\nstring
Cause: The _VolFileSystemEndian property of the indicated Volume_Disk_Header
was invalid.
ACFS-07226: Volume_Disk_Header has invalid _VolStateFlag values.\n found:
string\n, but expected to find: string or string\nfor structure:\nstring
Cause: The _VolStateFlag property of the indicated Volume_Disk_Header contained
one or more invalid values.
ACFS-07227: missing snapshot name or identifier
Cause: A snapshot name or identifier was not entered as required for this command.
2-84 Error Messages
Action: Re-enter the command with a valid snapshot name or snapshot identifier.
ACFS-07228: cannot determine disk geometry for volume: string
Cause: The program was unable to determine the geometry of the indicated volume.
Refer to the accompanying message(s) for more information on the problem.
ACFS-07229: volume: string has invalid sector size\n found: number, but expected
to find: number\n- assuming default value: number
Cause: The sector size of the indicated volume was invalid. The ACFS Checker
temporarily assumed the default sector size during processing.
ACFS-07230: cannot determine size for volume: string
Cause: The program was unable to determine the size of the indicated volume. Refer
ACFS-07231: seek to end of volume failed for volume: string offset: string
Cause: The program was unable to seek to the end of the indicated volume. Refer to
the accompanying message(s) for more information on the problem.
ACFS-07232: seek to end of volume failed for volume: string\n requested offset:
string returned offset: string
Cause: The request to seek to the end of the indicated volume failed. The offset set
returned did not match the offset requested. Refer to the accompanying message(s)
ACFS-07233: read failed for Primary Volume_Disk_Header at disk offset: string
Cause: An attempt to read the Primary Volume_Disk_Header at the indicated disk
offset failed. Refer to the accompanying message(s) for more information on the
problem.
ACFS-07234: read failed for Alternate Volume_Disk_Header at disk offset: string
Cause: An attempt to read the Alternate Volume_Disk_Header at the indicated disk
problem. problem.
ACFS-00501 to ACFS-11111 2-85
ACFS-07235: extent[number] has invalid _PhysicalDiskOffset value\n found: 0, but

expected to find: greater than 0\nfor file:\nstring
Cause: The _PhysicalDiskOffset property of an extent structure of the indicated file
had a value of zero. _PhysicalDiskOffset values must be greater than zero.
ACFS-07236: extent[number] has invalid _PhysicalDiskOffset value\n found: 0, but
expected to find: greater than 0\nfor structure:\nstring
Cause: The _PhysicalDiskOffset property of an extent of the indicated extent structure
ACFS-07237: read failed for File_Entry_Table extent metadata structure at disk
offset: string\nfor file:\nstring
Cause: An attempt to read an extent metadata structure of the indicated file failed.
ACFS-07239: File_Entry_Table count incorrect\n found: number, but expected to
Cause: The number of entries found in the File_Entry_Table file did not match the
expected number of entries. One or more of the extent structures was invalid.
ACFS-07240: Invalid Security_Metadata_File
Cause: File system checking has identified the metadata inconsistency reported in the
message.
Support Services.
ACFS-07241: Security_Metadata file has invalid _security_descriptor record\nfor
file:\nstring
Cause: A _security_descriptor record of the indicated Security_Metadata file was
invalid.
ACFS-07243: Security_Metadata file has no valid _security_data records\nfor file:
\nstring
Cause: The indicated Security_Metadata file did not contain any valid valid
_security_data records.
2-86 Error Messages
ACFS-07245: Security_Metadata file contains invalid _security_descriptor data
\nfor file:\nstring
Cause: The indicated Security_Metadata file contained at least one invalid
_security_data record. Refer to the accompanying message(s) for more information on
the problem.
ACFS-07246: Security_Metadata file _Private structure is invalid for:\nfor file:
\nstring
Cause: The _Private structure of the indicated Security_Metadata file was invalid.
ACFS-07247: Security_Metadata file has invalid Hash_Table data\nfor file:\nstring
Cause: The Hash_Table of the indicated Security_Metadata file contained inconsistent
data. Refer to the accompanying message(s) for more information on the problem.
ACFS-07250: Security_Metadata file _Private structure has invalid _maxFree value
\n found: number minimum: number\nfor structure:\nstring
Cause: The _maxFree property of the indicated _Private metadata structure was
incorrect.
ACFS-07251: Security_Metadata file _Private structure has invalid
_freeDataListTail value\n found: number minimum: number\nfor structure:
\nstring
Cause: The _freeDataListTail property of the indicated _Private metadata structure
was incorrect.
ACFS-07252: Security_Metadata file node not on _freeDataList\nfor file:\nstring
Cause: One or more of the _security_data nodes of the indicated Security_Metadata
file was not found on the free data node list. The _next property for one or more of the
_security_data nodes was incorrect.
ACFS-00501 to ACFS-11111 2-87
ACFS-07254: Security_Metadata file has invalid _security_record for

_Administrator default\nfor file:\nstring
Cause: The default _Administrator _security_record of the indicated
Security_Metadata file was invalid.
ACFS-07256: file has unexpected _ProtectionBits value\n found: number, but
Cause: The _ProtectionBits property of the indicated files was not expected.
Action: No action is needed if the protection bits were intentionally set differently
from the default.
ACFS-07257: unable to process request for volume string; volume is not open
Cause: An attempt to read metadata failed because the volume was not open. Refer to
the accompanying messages for more information on the problem.
rerun the acfsdbg utility.
ACFS-07258: unable to reset context to snapshot string due to File_Entry_Table
metadata inconsistency
Services. Services.
ACFS-07259: file system does not contain a valid Local_Metadata_Directory
Cause: There was no valid Local_Metadata_Directory in the file system. At least one
Local_Metadata_Directory is required.
ACFS-07260: Volume_Disk_Header has incorrect _VolNumOFSNodes value\n
found: number, but expected to find: number\nfor structure:\nstring
Cause: The _VolNumOFSNodes property of the indicated Volume_Disk_Header
structure was incorrect. Its value did not match the number of valid ACFS nodes
found.
ACFS-07261: unable to reset context to snapshot string due to Snap_Map file
Services.
2-88 Error Messages
ACFS-07262: unable to reset context to snapshot %(1) because it no longer exists

Cause: The identified snapshot no longer exists due to on-disk metadata changes that
are allowed whenever the acfsdbg utility is operating in read-only mode.
Action: Enter the 'primary' or 'snap snapshot name' command to set context.
ACFS-07263: Free_Block_List has incorrect _first_free_group value\n found:
Cause: The _first_free_group property of the indicated Free_Block_List structure was
incorrect.
ACFS-07264: Free_Block_List has incorrect _last_free_blk value\n found: number,
Cause: The _last_free_blk property of the indicated Free_Block_List structure was
incorrect.
ACFS-07265: write failed for Free_Block metadata structure at disk offset: string
size: number bytes\nfor structure:\nstring
Cause: An attempt to write a Free_Block metadata structure to disk failed. Refer to
ACFS-07266: write failed for Free_Block_List metadata structure at disk offset:
string size: number bytes\nfor structure:\nstring
Cause: An attempt to write a Free_Block_List metadata structure to disk failed. Refer
to accompanying message(s) for more information on the problem.
ACFS-07267: file marked for deletion (file identifier: string, disk offset: string)
cannot be removed due to inconsistent file metadata
Cause: Inconsistent metadata was found for the indicated file that was marked for
deletion. The file could not be deleted.
ACFS-07268: file marked for deletion (file identifier: string, disk offset: string) has
invalid _LinkCount value\n found: number, but expected to find: 0
Cause: The indicated file was marked for deletion, but its _LinkCount property was
not zero. Files to be deleted must have a _LinkCount value of zero. The file could not
be deleted.
ACFS-00501 to ACFS-11111 2-89
ACFS-07269: file marked for deletion (file identifier: string, disk offset: string) has
invalid _SynchFlag value\n found: string\n, but expected to find: string
Cause: The _SynchFlag property of the indicated file was incorrect. The file was
marked for deletion but its _SynchFlag did not have the appropriate value. The file
could not be deleted.
ACFS-07271: orphan file : string (file identifier: string) added to 'lost+found'
directory
Cause: The indicated file did not have a valid entry in any parent directory. The ACFS
Fixer move the file to the 'lost+found' directory.
ACFS-07272: read failed for extent metadata structure at disk offset: string\nfor
file:\nstring
Cause: An attempt to read an extent metadata structure for the indicated file failed.
ACFS-07274: missing or invalid snapshot name
Cause: No snapshot name was provided or the name entered was not valid.
Action: Re-enter the command with a valid snapshot name.
ACFS-07275: cannot read File_Entry_Table _FileEntry metadata structure\n- file
system validation cannot continue
Cause: An attempt to read the _FileEntry metadata structure of the File_Entry_Table
failed. The File_Entry_Table is a critical ACFS metadata structure that is required for
file system validation or repairs. The ACFS Checker/Fixer could not process the file
system. NOTE: It is also possible that there was no ACFS file system on this volume.
Action: Correct the problem indicated by the accompanying messages if possible and
rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows). If the problem cannot be
resolved then restore the file system from a backup copy.
ACFS-07276: File_Entry_Table _FileEntry metadata structure is invalid\n- file
Cause: The File_Entry_Table's _FileEntry metadata structure is either corrupt or is
missing critical information. NOTE: It is also possible that there is no ACFS file
system on the volume.
ACFS-07280: checking File_Entry_Table entry: string at disk offset: string
Cause: The ACFS Checker found a File_Entry_Table entry that has not been
processed. This entry was an orphan file or an orphan internal metadata structure.
2-90 Error Messages
ACFS-07282: read failed for File_Entry_Table entry: string at disk offset string
Cause: An attempt to read a File_Entry_Table entry failed. Refer to the accompanying
ACFS-07283: orphan File_Entry_Table metadata structure found for\n identifier:
string at disk offset: string\n structure type: string
Cause: A File_Entry_Table entry was found that had not been processed. This entry
was an orphan file or an invalid internal metadata structure.
ACFS-07284: orphan system file found for file identifier: string at disk offset:string
Cause: The indicated system file did not have a valid parent directory.
ACFS-07285: snapshot: string (identifier: number) has invalid File_Entry_Table
identifier: string that exceeds the maximum value for this file system: string
Services.
ACFS-07286: orphan file found for file identifier: string at disk offset: string
Cause: The indicated file did not have a valid parent directory.
ACFS-07287: orphan Free_Block metadata structure found for file identifier: string
at disk offset: string
Cause: The indicated Free_Block metadata structure was not found on any free block
list.
ACFS-07288: orphan file 'string' (file identifier: string) \nadded to 'lost+found'
directory
Cause: The indicated file did not have a valid entry in any directory which meant that
the file did not have a valid file name. The file was given the generic name described
in the message and moved to the 'lost+found' directory.
ACFS-00501 to ACFS-11111 2-91
ACFS-07289: orphan Local_Metadata_Directory metadata structure found for file

identifier: string at disk offset: string
Cause: The indicated Local_Metadata_Directory metadata structure was not found on
any _Locator list for Local_Metadata_Directory structures.
ACFS-07290: orphan Free_List_Header metadata structure found for file identifier:
string at disk offset: string
Cause: The indicated Free_List_Header metadata structure was not found on any
valid Local_Metadata_Directory structure.
ACFS-07291: orphan _Locator metadata structure found for file identifier: string at
disk offset: string
Cause: The indicated _Locator metadata structure was not found in any list of valid
_Locator structures.
ACFS-07292: orphan Global_Metadata_Directory metadata structure found for file
Cause: The File_Entry_Table contained a duplicate Global_Metadata_Directory
metadata structure. Global_Metadata_Directory structures must be unique.
ACFS-07294: orphan Global_Virtual_FileID_Pool metadata structure found for
Cause: The File_Entry_Table contained a duplicate entry for the
Global_Virtual_FileID_Pool metadata structure. Global_Virtual_FileID_Pool
structures must be unique.
ACFS-07295: orphan Local_Virtual_FileID_Pool metadata structure found for
Cause: The indicated Local_Virtual_FileID_Pool metadata structure was not found on
any valid Local_Metadata_Directory structure.
2-92 Error Messages
ACFS-07296: orphan Replication_Log_Initiator metadata structure found for

Cause: The File_Entry_Table contained a duplicate entry for a
Replication_Log_Initiator metadata structure. Replication_Log_Initiator structures
must be unique.
ACFS-07297: File_Entry_Table entry: string at disk offset: string is not a valid
metadata structure
Cause: The indicated entry in the File_Entry_Table was not a metadata structure
recognized by ACFS.
ACFS-07298: cannot convert file identifier: 'string' to numeric value
Cause: The format entered for the file identifier was invalid.
Action: Use the acfsdbg utility help (-h) option for a list of commands and format
options for entering data.
ACFS-07300: directory Hash_Table contains duplicate entries for offset: string\nfor
file:\nstring
Cause: The Hash_Table of the indicated directory file had duplicate entries for the
offset described in the message. Hash_Table entries must map to unique offsets.
ACFS-07301: directory _hash_key: string for offset: string has no corresponding file
entry\nfor file:\nstring
Cause: The _hash_key property of the indicated directory file was invalid. Its value
did not reference a valid file entry.
ACFS-07302: directory _hash_key for offset: string is incorrect\n found: string, but
Cause: The _hash_key property of the indicated directory file was incorrect. Its value
did not match the hash value calculated for the corresponding file entry.
ACFS-07303: Security_Metadata file Hash_Table contains multiple entries for
Cause: The Hash_Table of the indicated Security_Metadata file had duplicate entries
for the offset described in the message. Hash_Table entries must map to unique
offsets.
ACFS-00501 to ACFS-11111 2-93
ACFS-07304: Security_Metadata file _hash_key: string for offset: string has no
corresponding entry\nfor file:\nstring
Cause: The _hash_key property of the indicated Security_Metadata file was invalid.
Its value did not reference a valid entry.
ACFS-07305: Security_Metadata file _hash_key for offset: string is incorrect\n
found: string, but expected to find: string\nfor file:\nstring
Cause: The _hash_key property of the indicated Security_Metadata file was incorrect.
Its value did not match the hash value calculated for the corresponding entry.
ACFS-07306: Hash_Table _hash_key order is incorrect\nfor file:\nstring
Cause: The _hash_key properties of the Hash_Table of the indicated file were not
ordered correctly.
ACFS-07308: Hash_File_Index structure for block number at disk offset: string
already processed\nfor file:\nstring
Cause: The Hash_File node list of the indicated file was invalid. One or more of the
Hash_File structures had an invalid _next property.
ACFS-07309: cannot access Hash_File_Index node metadata structure at disk offset:
Cause: An attempt to access the indicated Hash_File_Index metadata structure failed.
ACFS-07310: Hash_File_Index node has incorrect _next value\n found: string, but
Cause: The _next property of the indicated Hash_File_Index structure was incorrect.
2-94 Error Messages
ACFS-07311: Hash_Bucket for block number at disk offset: string already processed
Cause: The Hash_Bucket structure of the indicated file has already been processed.
One or more of the Hash_File structures had an invalid _next property.
ACFS-07312: cannot access Hash_Bucket metadata structure at disk offset: string
\nfor file:\nstring
Cause: An attempt to access the indicated Hash_Bucket metadata structure failed.
ACFS-07313: Hash_Bucket has incorrect _controlling_bkt value\n found: number,
Cause: The _controlling_bkt property of the indicated Hash_Bucket structure was
incorrect.
ACFS-07314: Hash_Bucket has incorrect _split_count value\n found: number, but
Cause: The _split_count property of the indicated Hash_Bucket structure was
incorrect.
ACFS-07315: Hash_Bucket has incorrect _next value\n found: number, but expected
Cause: The _next property of the indicated Hash_Bucket structure was incorrect.
ACFS-07316: cannot access Hash_File_Master_Block metadata structure at disk
Cause: An attempt to access the indicated Hash_File_Master_Block metadata
structure failed. Refer to the accompanying message(s) for more information on the
problem.
ACFS-07317: Hash_File metadata structure for block:number at disk offset: string
Cause: The list of nodes of the indicated Hash_File file was invalid. One or more of
the Hash_File structures had an invalid _next property.
ACFS-00501 to ACFS-11111 2-95
ACFS-07318: Hash_File_Master_Block structure has incorrect _initial_bkt_count
Cause: The _initial_bkt_count property of the indicated Hash_File_Master_Block
ACFS-07319: Hash_File_Master_Block structure has incorrect _double_count value
\n found: number, but expected to find: number\nfor file:\nstring
Cause: The _double_count property of the indicated Hash_File_Master_Block
ACFS-07320: Hash_File_Master_Block structure has incorrect value for entry
number in _hash_bucket_group array\n found: number, but expected to find:
number\nfor structure:\nstring
Cause: The entry in _hash_bucket_group array of the indicated
Hash_File_Master_Block was incorrect.
ACFS-07321: _hash_entry number has no corresponding entry\nfor file:\nstring
Cause: The _hash_entry property in the Hash_Table of the indicated file did not have
a valid entry associated with it.
ACFS-07322: metadata read failed at disk offset: string size: number bytes\nfor file:
\nstring
Cause: An attempt to read metadata of the indicated file failed. Refer to the
bytes returned: number\nfor file:\nstring
Cause: An attempt to read metadata of the indicated file failed. The amount of data
2-96 Error Messages
ACFS-07327: metadata write failed at disk offset: string size: number bytes\nfor
file:\nstring
Cause: An attempt to write metadata of the indicated file failed. Refer to
ACFS-07331: metadata write failed at disk offset: string\n bytes requested: number
bytes written: number\nfor file:\nstring
Cause: An attempt to write metadata of the indicated file failed. The amount of data
ACFS-07332: cannot convert snapshot identifier: 'string' to numeric value
Cause: The format entered for the snapshot identifier was invalid.
ACFS-07333: invalid snapshot identifier entered: string\n minimum: 1 maximum:
number
Cause: The snapshot identifier entered was not within the valid range for this file
system.
Action: Re-enter the command with a snapshot identifier that is within the valid
range described in the message.
ACFS-07334: invalid snapshot name 'string' entered
Cause: The snapshot name entered did not exist.
Action: Re-enter the command with the name or identifier of a valid snapshot.
ACFS-07335: Directory_Node has invalid _dir_entry_free_list_tail value\n found:
number maximum: number\nfor structure:\nstring
Cause: The _dir_entry_free_list_tail property of the indicated Directory_Node
ACFS-07336: Directory_Node structure has invalid _next_free_dirnode value\n
Cause: The _next_free_dirnode property of the indicated Directory_Node structure
was incorrect.
ACFS-07337: Directory_Entry structure has incorrect file identifier for file 'string'\n
Cause: The file identifier property of the indicated Directory_Entry structure did not
match the file identifier of the corresponding file.
ACFS-00501 to ACFS-11111 2-97
ACFS-07338: Directory_Entry structure has incorrect _rec_len value for file
'string'\n found: number, but expected to find: number\nfor structure:\nstring
Cause: The _rec_len property of the indicated Directory_Entry structure was
incorrect.
ACFS-07339: Directory_Entry structure has incorrect _name_len value for file
Cause: The _name_len property of the indicated Directory_Entry structure was
incorrect.
ACFS-07340: Directory_Entry structure has invalid or incorrect _attributes for file
'string'\n found: string\n, but expected to find: string\nfor structure:\nstring
Cause: The _attributes property of the indicated Directory_Entry structure did not
match the _attributes property of the corresponding file.
ACFS-07341: starting disk offset string exceeds ending disk offset string
Cause: The starting storage map offset was greater than the ending offset.
Action: Re-enter the command with valid disk offsets.
ACFS-07342: Directory_Entry structure has incorrect filename for file\n found:
'string', but expected to find: 'string'\nfor structure:\nstring
Cause: The filename property of the indicated Directory_Entry structure did not
match the name of the file.
ACFS-07343: unused Directory_Entry structure has incorrect _name_len value\n
incorrect.
'string'\n found: number maximum: number\nfor structure:\nstring
Cause: The _rec_len property of the indicated Directory_Entry structure was greater
than the maximum value.
2-98 Error Messages
'string'\n found: number minimum: number\nfor structure:\nstring
Cause: The _rec_len property of the indicated Directory_Entry structure was less than
the minimum value.
ACFS-07346: Directory_Entry structure has invalid _name_len value\n found:
number operating system maximum: number\nfor structure:\nstring
greater than the maximum value for this operating system.
ACFS-07347: Directory_Entry structure has incorrect _name_len value\n found:
greater than the maximum value for this entry.
ACFS-07350: command disabled due to lack of File_Entry_Table context; enter
'primary' or 'snap' to set context
Cause: The acfsdbg utility could not process the request because the File_Entry_Table
context was not set. The acfsdbg utility requires a valid File_Entry_Table context to
locate on-disk metadata structures.
Action: Enter 'primary' or 'snap snapshot name' command to set context.
ACFS-07351: requested Snap_Info_Entry structure not available due to
Services.
ACFS-07352: snapshot directory contains files with incorrect attributes; attempting
to continue processing
Cause: The _attributes property for a file in the indicated snapshot directory was
incorrect. The _attributes value indicated that the file was not a directory. All files in a
snapshot directory must be directories.
ACFS-00501 to ACFS-11111 2-99
ACFS-07354: file has incorrect or invalid _attributes value\n found: string\n, but
Cause: The _attributes property of the indicated file was incorrect.
ACFS-07355: Cannot fix orphaned files because the lost+found directory is
damaged.
Cause: Fsck could not move the orphan files because there was an inconsistency with
the lost+found directory. Files that do not have a valid parent directory are
considered to be orphan files and are moved to the lost+found directory.
ACFS-07356: file is a symbolic link but has no storage for the target name \nfor
file:\nstring
Cause: The indicated file was a symbolic link but did have a target. The target of a
symbolic link must have storage.
ACFS-07360: deleting file due to invalid _attributes: string\nfile:\nstring
Cause: The _attributes property of the indicated file was invalid. The file must be
deleted in order to preserve the integrity of the file system.
ACFS-07361: truncating file 'string' to number bytes\nfor file:\nstring
Cause: The indicated file was truncated in order to preserve file system integrity.
ACFS-07363: Volume_Disk_Header has invalid _VolFeatureFlag values.\n found:
message.
Support Services.
ACFS-07364: file has incorrect values for Extent[number]\n found: _Length: string
_PhysicalDiskOffset: string\n, but expected to find: _Length: string
_PhysicalDiskOffset: string\nfor file:\nstring
Cause: One or more or the extent properties of the indicated file was incorrect.
2-100 Error Messages
ACFS-07365: extent metadata structure has incorrect values for Extent[number]\n
found: _FileOffset: string _Length: string _PhysicalDiskOffset: string \n, but
expected to find: _FileOffset: string _Length: string _PhysicalDiskOffset: string
Cause: One or more properties of the indicated extent metadata structure was
incorrect.
ACFS-07366: directory has incorrect _attributes value\n found: string\n, but
Cause: The _attributes property of the indicated directory file was incorrect.
ACFS-07369: directory has invalid _FileSize value\n found: number minimum:
number\nfor file:\nstring
Cause: The _FileSize property of the indicated directory file was incorrect.
ACFS-07370: directory has invalid _FileSize: string _AllocationSize: string values
\nfor file:\nstring
Cause: The _FileSize and _AllocationSize properties of the indicated directory file
were incorrect.
ACFS-07374: cannot access directory _Private structure for block number at disk
Cause: An attempt to access the indicated directory _Private metadata structure
failed. Refer to the accompanying message(s) for more information on the problem.
ACFS-07375: directory _Private structure at disk offset: string contains invalid data
\nfor file:\nstring
Cause: The _Private structure of the indicated directory file contained invalid data.
ACFS-00501 to ACFS-11111 2-101
ACFS-07376: directory _Private structure has incorrect header type at disk offset:
string, this file may not be a directory\n found: string, but expected to find: string
\nfor file:\nstring
Cause: The indicated file did not contain a _Private directory metadata structure as
required for directory files. It appeared that the file was incorrectly identified as being
a directory.
ACFS-07377: directory has invalid node list\nfor file:\nstring
Cause: The node list of the indicated directory file was invalid. There are three
possible causes: 1. One or more of the file's directory structures had an invalid
structure header. 2. The _next_dirnode property of one or more of the file's directory
structures was incorrect. 3. The _first_dirnode property of the _Private directory
ACFS-07378: directory _Private structure has incorrect _last_dirnode value\n
found: number, but expected to find: number\nfor file:\nstring
Cause: The _last_dirnode property of the indicated _Private directory structure was
incorrect.
ACFS-07379: directory has invalid free block list\nfor file:\nstring
Cause: The free block list of the indicated directory file was invalid. There are three
structure header. 2. The _next_free_dirnode property of one or more of the file's
directory structures was incorrect. 3. The _dir_entry_free_list_head property of the
_Private directory structure was incorrect.
ACFS-07381: directory _Private structure has incorrect _dir_entry_free_list_tail
value\n found: number, but expected to find: number\nfor file:\nstring
Cause: The _ dir_entry_free_list_tail property of the indicated _Private directory
ACFS-07382: directory has invalid hash block free list; invalid reference for free
hash block\n found: number maximum: number\nfor file:\nstring
Cause: The hash block free list of the indicated directory file was invalid. There are
two possible causes: 1. The _hash_blk_free_list property of the _Private directory
structure referenced a block that exceeded the directory's size. 2. The _next_free_blk
property of a directory free block referenced a block that exceeded the directory's size.
ACFS-07383: directory has invalid hash block free list\nfor file:\nstring
Cause: The free hash block list of the indicated directory file was invalid. There are
three possible causes: 1. One or more of the file's directory structures had an invalid
structure header. 2. The next_free_blk property of one or more of the file's directory
structures was incorrect. 3. The hash_blk_free_list property of the _Private directory
ACFS-07384: snapshot: string (identifier: number) has invalid
_SnapIncarnationNumber\n found: 0, but expected to find: > 0\nfor structure:
\nstring
message.
Support Services.
ACFS-07385: directory has orphan Directory_Node metadata structure for block
number at disk offset: string\nfor file:\nstring
Cause: The indicated directory file had a Directory_Node metadata structure that was
not found on any directory node list.
ACFS-07386: directory has incorrect _FileSize value\n found: string, but expected
ACFS-07388: directory contains invalid _Private structure for block number at disk
Cause: A _Private metadata structure of the indicated directory file was found in the
wrong block. _Private metadata structures must be located at block one of a
directory's metadata.
ACFS-07389: directory has orphan free block number at disk offset: string\nfor file:
\nstring
Cause: The indicated directory file had a free block that was not found on the
directory's free list.
ACFS-00501 to ACFS-11111 2-103
ACFS-07391: directory has invalid metadata structure string type for block number
Cause: The structure found at the block of the indicated directory file was not a valid
directory metadata structure.
ACFS-07392: Directory_Entry has incorrect or invalid _attributes value\n found:
string\n, but expected to find: string\nfor file:\nstring
Cause: The _attributes property of the indicated Directory_Entry was incorrect.
ACFS-07395: directory has incorrect or invalid _attributes values\n found: string\n,
ACFS-07396: directory has incorrect Hash_Table data\nfor file:\nstring
Cause: The Hash_Table of the indicated directory file contained inconsistent data.
ACFS-07399: directory has incorrect _LinkCount value\n found: number, but
Cause: The _LinkCount property of the indicated directory file was incorrect.
ACFS-07400: mismatch between _NOLSTXPTR feature and _NOUPHDRPTR
feature\n _NOLSTXPTR: string _NOUPHDRPTR: string\nfor file:\nstring
message.
Support Services.
ACFS-07401: write failed for Deferred_Remove_File_List metadata structure at disk
offset: string size: number bytes\nstructure type: string \nfor file:\nstring
Cause: An attempt to write metadata on the indicated file failed. Refer to
ACFS-07402: Deferred_Delete_Storage_List structure has invalid delete list
pointers: _PrevDeferredListLink: string _NextDeferredListLink: string\nfor
structure:\nstring
Cause: The _PrevDeferredListLink or _NextDeferredListLink property of of the
indicated structure were incorrect. Both values must be zero or non-zero.
ACFS-07403: write failed for Deferred_Remove_Storage_List metadata structure at
disk offset: string size: number bytes\nstructure type: string \nfor file: \nstring
Cause: An attempt to write metadata of the indicated failed. Refer to accompanying
ACFS-07407: Snap_Map_Header contains invalid _SnapCreatePending field
\nfound: 0, but expected to find: > 0\nfor structure:\nstring
Services.
ACFS-07408: Snap_Map_Header contains invalid _SnapDeletePending field
Services.
ACFS-07411: snapshot metadata checking will be limited due to an error reading
snapshot metadata
Cause: An attempt to read snapshot metadata failed. Snapshot validation was limited
since not all snapshot metadata was not available.
ACFS-07413: unable to create internal structure needed for processing
Cause: Refer to the accompanying message(s) for more information on the problem.
ACFS-00501 to ACFS-11111 2-105
ACFS-07414: snapshot: string (identifier: number) has invalid snap_map_tuples for

file:\nstring
message.
Support Services.
ACFS-07415: invalid snap_map_tuple: ( string, string ) for disk offset: string
message.
Support Services.
ACFS-07416: file has invalid _FileSize value\n found: string minimum: string\nfor
file:\nstring
Cause: The _FileSize property of the indicated file was invalid.
ACFS-07417: Snap_Map_Header structure has invalid _snap_incarnation values;
_SnapHighestActiveIncarnNumber: number must be less than
_SnapNextIncarnationNumber: number\nfor structure:\nstring
Cause: One or both of the _SnapHighestActiveIncarnNumber and
_SnapNextIncarnationNumber properties of the indicated Snap_Map_Header
metadata structure was incorrect.
ACFS-07418: Snap_Map_Header structure has invalid _SnapCreatePending value
\n found: number, but expected to find: number or < number\nfor structure:\nstring
Cause: The _SnapCreatePending property of the indicated Snap_Map_Header
metadata structure was incorrect. The _SnapCreatePending value must be zero or less
than the value indicated in the message.
ACFS-07419: Snap_Map_Header structure has invalid _SnapDeletePending value
Cause: The _SnapDeletePending property of the indicated Snap_Map_Header
metadata structure was incorrect. The _SnapDeletePending value must be zero or less
ACFS-07420: found partially created snapshot for snapshot: 'string'
Cause: Initialization of the indicated snapshot did not complete. There are two
possible causes: 1. The volume went offline while the snapshot was being created. 2.
The process creating the snapshot was unexpectedly terminated do to a shutdown of
the system.
ACFS Fixer to resolve the problem. The ACFS Fixer will remove this snapshot.
ACFS-07421: found partially deleted snapshot
Cause: A snapshot was not completely deleted. There are several possible causes: 1.
The volume was unmounted before the asynchronous phase of snapshot deletion had
completed. 2. The volume went offline while the snapshot was being deleted. 3. The
process deleting the snapshot was unexpectedly terminated do to a shutdown of the
system.
ACFS-07423: snapshot 'string' has invalid file identifier\n found: string maximum:
Cause: The file identifier property of the indicated snapshot was invalid. Its value
ACFS-07424: snapshot 'string' has invalid _SnapIncarnationNumber value\n
Cause: The _SnapIncarnationNumber property of the indicated snapshot was invalid.
ACFS-07425: snapshot (_snapid value: string) has invalid name: 'string'\nfor
structure:\nstring
Cause: The name of indicated snapshot contained invalid characters.
ACFS-07426: snapshot 'string' has invalid _SnapVisibility value\n found: number,
but expected to find: number or number\nfor structure:\nstring
Cause: The _SnapVisibility property of the indicated snapshot was invalid.
ACFS-00501 to ACFS-11111 2-107
ACFS-07427: duplicate _SnapIncarnationNumber: number found for snapshots

'string' and 'string'
Cause: The _SnapIncarnationNumber property of the indicated snapshots had the
same value. _SnapIncarnationNumber values must be unique across all snapshots.
ACFS Fixer to resolve the problem. The ACFS Fixer will delete the second snapshot.
ACFS-07429: Snap_Map_Header structure has incorrect _SnapCount value\n
Cause: The _SnapCount property of the indicated Snap_Map_Header metadata
structure was incorrect. The _SnapCount value did not match the number of valid
snapshots found.
ACFS-07430: cannot determine free space for volume associated with directory
'string'; attempting to continue with current directory 'string'
Cause: A temporary file is needed to store information during processing. This file
was targeted for the indicated directory. The ACFS Checker was unable to determine
the mount of space available for the volume associated with the directory. Refer to the
Action: No further action is needed. The ACFS Checker/Fixer will attempt to
continue processing with the current directory.
ACFS-07431: cannot determine free space for volume associated with current
directory 'string'
was targeted for the current directory. The ACFS Checker was unable to determine
ACFS-07432: insufficient space available to store temporary file in\ndirectory
'string' or directory 'string'\nspace needed: number bytes\n- unable to continue
Cause: A temporary file is needed to store information during processing but there
was not enough space to store the file in either of the The size of this file is dependent
on the size of the file system. indicated directories.
Action: Provide sufficient space as described in the message to store the the
temporary file in either of the indicated directories. Rerun the ACFS Checker/Fixer
once there is sufficient storage to store the temporary file.
ACFS-07435: invalid path name length for temporary file\n length: number
minimum: number maximum: number
Cause: The path name for a temporary file does not exist or its length exceeds the
maximum for this system. Refer to the accompanying message(s) for more
information on the problem.
ACFS-07436: string has encountered an internal error: invalid parameter passed to

fb_create
Cause: The ACFS Checker/Fixer or ACFS Debug utility has encountered an
unexpected, internal error.
ACFS-07437: string has encountered an internal error: invalid parameter passed to
fb_ref\n disk offset: string size: string fbSize: string fbCacheSize: string
ACFS-07438: file has storage allocated to it that is also allocated to another file\nfor
file:\nstring
Cause: Storage allocated to the indicated file was also allocated to at least one other
file. Storage can only be allocated to a single file. Storage can never be allocated to
multiple files.
ACFS-07439: Snapshot_BitMap conflicts with the Global_BitMap for disk offset:
string
Cause: One or more snapshot bitmaps claimed storage that was also claimed by the
Global_BitMap.
ACFS Fixer to resolve the problem. The ACFS Fixer will remove all snapshots whose
bitmap conflicts with the Global_BitMap.
ACFS-07440: Snapshot_BitMap has bit set for non-existing snapshot for disk offset:
string
Cause: One or more bitmaps reserved for unused snapshot incorrectly claimed
storage. Bitmaps for snapshots that are not in use cannot claim any storage.
ACFS-07441: Snapshot_BitMap has bits set for storage at disk offset: string that is
beyond the file system size
Cause: One or more snapshot bitmaps incorrectly claimed storage that exceeded the
size of the file system.
ACFS-07443: Global_BitMap has invalid value for number of bits set\n found:
Cause: The Global_BitMap property that indicates the number of bits set exceeded the
size of the bitmap.
ACFS-00501 to ACFS-11111 2-109
ACFS-07444: Global_BitMap has invalid value for number of bits set.\n found:
Cause: The Global_BitMap property that indicates the number of bits set did not
match the amount of storage allocated to all valid files.
ACFS-07445: Global_BitMap has invalid value for next offset to search\n found:
Cause: The Global_BitMap property that indicates the next offset to search for
available bits to allocate exceeded the size of the bitmap.
ACFS-07446: mismatch between temporary Global_BitMap and on-disk
Global_BitMap
Cause: The temporary Global_BitMap that was populated by traversing all valid file
system data did not match the on-disk copy of the Global_BitMap.
ACFS-07447: invalid snap_map_tuple for disk offset: string\n found: ( 0, 0 ), but
expected non-zero values\nfor file:\nstring
message.
Support Services.
ACFS-07448: invalid snap_map_tuple for disk offset: string\n found: ( 0, 0 ), but
expected non-zero values
message.
Support Services.
ACFS-07449: snapshot 'string' storage bitmap is incorrectly set for disk offset: string
Cause: The bitmap of the indicated snapshot claimed storage that was allocated to
allocated file. Storage can only be allocated to a single file. Storage can never be
allocated to multiple files.
ACFS-07450: snapshot 'string' storage bitmap is not set for disk offset: string
Cause: The bitmap of the indicated snapshot did not claim storage that was allocated
to one of its files. A snapshot's bitmap must claim all storage allocated to its files.
ACFS-07451: snapshot 'string' storage bitmap is incorrectly set for disk offset: string
with no corresponding file data
Cause: The bitmap of the indicated snapshot claimed storage but the storage was not
allocated to any file.
ACFS-07452: unable to locate directory for snapshot 'string' (id: number)\n
processing will continue for other snapshots
Cause: The directory of the indicated snapshot was not found. This snapshot could
not be processed.
ACFS-07453: Snap_Root_Directory file identifier for snapshot 'string' was incorrect
Cause: The Snap_Root_Directory file identifier property of the indicated snapshot
was incorrect.
ACFS-07455: unable to open file: string
Cause: An attempt to open a file failed. Refer to the accompanying message(s) for
more information on the error.
ACFS-07458: The request to cancel string was incomplete because volume string
was not accessible. The file system cannot be mounted in this state.\nRerun string
once the volume is accessible to enable file system mounts.
Cause: The ACFS Checker/Fixer could not reset the volume to allow for file system
mounts because the volume was not accessible. Refer to the accompanying message(s)
for more information on the error.
Action: Rerun the ACFS Checker/Fixer once the volume is accessible to enable file
system mounts.
ACFS-00501 to ACFS-11111 2-111
ACFS-07459: Volume_Label metadata structure has invalid _VolLabelLength value

\n found: number maximum: number\nfor structure:\nstring
Cause: The _VolLabelLength property of the indicated Volume_Label metadata
structure exceeded the maximum value.
ACFS-07460: Volume_Label metadata structure has invalid _VolIDLength value\n
Cause: The _VolIDLength property of the indicated Volume_Label metadata structure
exceeded the maximum value.
ACFS-07461: Volume_Label metadata structure has invalid _ClusterNameLength
value\n found: number maximum: number\nfor structure:\nstring
Cause: The _ClusterNameLength property of the indicated Volume_Label metadata
ACFS-07462: file has incorrect or invalid _attributes values\n found: string\n valid
values: string\nfor file:\nstring
Cause: The _attributes property of the indicated file contained invalid and/or
incorrect values.
ACFS-07464: file has invalid _attributes value\n found: string\nfor file:\nstring
Cause: The _attributes property of the indicated file contained invalid values. These
values are not supported on Windows systems.
ACFS-07465: file has _attributes set that are mutually exclusive\n found: string
\nfor file:\nstring
Cause: The _attributes property of the indicated file describe more than one type of
file. File types are mutually exclusive.
ACFS-07466: file has no _attributes value\nfor file:\nstring
Cause: The _attributes property of the indicated file did not describe a file type. The
_attributes property must describe a valid file type.
ACFS-07467: metadata structure has a non-zero value for field: string\nfor
structure:\nstring
Cause: The indicated ACFS metadata structure had a reserved or unused field that
contained a non-zero value. The field was overwritten or was not initialized correctly.
ACFS-07468: file has invalid _SynchFlags value\n found: string\nfor file:\nstring
Cause: The _SynchFlags property of the indicated file contained values that were not
within the range of valid values.
ACFS-07469: file cannot be modified; _SynchFlag value:\n found: string\nfor file:
\nstring
Cause: The indicated file had an internal inconsistency that prevented it from being
modified.
ACFS-07470: file cannot be accessed; _SynchFlag value:\n found: string\nfor file:
\nstring
accessed.
ACFS-07471: file incorrectly marked for deletion with _SynchFlag value:\n found:
Cause: The _SynchFlag property of the indicated file incorrectly identified the file as
marked for deletion while it was still part of a valid directory.
ACFS-07474: invalid program name\n found: string, but expected to find: string or
string
Cause: The ACFS Checker/Fixer or Debug utility has been renamed to a value that is
not recognized.
Action: Rename the program to the corresponding value listed in the message and
rerun the program.
ACFS-00501 to ACFS-11111 2-113
ACFS-07481: An I/O error occurred while reading ACFS metadata, some snapshot
metadata checks will not be performed.
Cause: The I/O error prevented full snapshot checking because required ACFS
metadata was not available. Refer to the accompanying message(s) for more
information on the error.
ACFS-07482: snapshot string with _snapid value: string has invalid parent snapshot
with _snapid value: string
Cause: The indicated snapshot does not have a valid parent.
ACFS-07483: snapshot with _snapid value: string has invalid ancestor snapshot
Cause: The indicated snapshot has an invalid ancestor snapshot.
ACFS-07484: valid ACFS volume path name required
Cause: A valid volume path name was not entered.
Action: Rerun the ACFS Checker/Fixer or Debug utility with a valid ACFS volume
path name as the final argument.
ACFS-07485: unable to determine temporary directory
Cause: An attempt to determine the system's temporary directory failed. For UNIX
systems this directory is either "/usr/tmp" or "/tmp". For Windows systems this
directory is the system's temporary folder. Refer to the accompanying message(s) for
ACFS-07486: unable to determine current directory
Cause: An attempt to determine the current directory failed. Refer to the
ACFS-07487: unable to open volume: string
Cause: An attempt to open a volume failed. Refer to the accompanying message(s) for
ACFS-07488: This volume is now in a mountable state. \nThe file system was not
checked before changing the volume's state. \nUse of this file system may
encounter serious errors since it has \nnot been checked.
Cause: The volume was forced into a mountable state without checking the integrity
of the file system. The file system may contain incorrect or invalid data.
Action: Run the ACFS Checker/Fixer before attempting to mount the file system.
ACFS-07489: maximum number of passes: number exceeded, program terminating

Cause: There are two possible causes: 1. There is a problem with the file system that
the ACFS Fixer cannot repair. 2. The ACFS Fixer has encountered an internal
problem.
ACFS-07498: extent[number] has invalid _Length value\n found: string, but
expected to find multiple of: string\nfor file:\nstring
Cause: The _Length property of an extent structure of the indicated file was invalid.
_Length values must be a multiple of the file system allocation unit size.
ACFS-07499: extent[number] has invalid _Length value\n found: string, but
expected to find multiple of: string\nfor structure:\nstring
Cause: The _Length property of an extent of the indicated extent structure was
invalid. _Length values must be a multiple of the file system allocation unit size.
ACFS-07500: extent[number] has invalid _FileOffset value\n found: string, but
Cause: The _FileOffset property of an extent structure of the indicated file was
invalid. _FileOffset values must be a multiple of the file system allocation unit size.
ACFS-07501: extent[number] has invalid _FileOffset value\n found: string, but
Cause: The _FileOffset property of an extent of the indicated extent structure was
ACFS-07502: extent[number] has invalid _PhysicalDiskOffset value\n found:
string, but expected to find multiple of: string\nfor file:\nstring
was invalid. _PhysicalDiskOffset values must be a multiple of the file system
allocation unit size.
ACFS-07503: extent[number] has invalid _PhysicalDiskOffset value\n found:
string, but expected to find multiple of: string\nfor structure:\nstring
ACFS-00501 to ACFS-11111 2-115
ACFS-07504: snapshot with _snapid value: string has invalid ancestor snapshot
(_cycle)
ACFS-07505: metadata structure read failed at disk offset: string for structure: string
Cause: An attempt to read the indicated metadata structure at the described disk
problem.
rerun the program.
ACFS-07519: Snap_Map_Header structure has invalid _SnapConvertPending value
\n found: number, but expected to find: less than number\nfor structure:\nstring
Cause: The _SnapConvertPending property of the indicated Snap_Map_Header
metadata structure was incorrect. The _SnapConvertPending value must be zero or
less than the value indicated in the message.
ACFS-07520: Snap_Map_Info structure has invalid _SnapInfoFlags value\n found:
Cause: The _SnapInfoFlags property of the indicated Snap_Map_Info metadata
structure was invalid.
ACFS-07521: Snap_Map_Info structure has invalid _SnapAncestorIncarn value\n
found: string\nfor structure:\nstring
Cause: The _SnapAncestorIncarn property of the indicated Snap_Map_Info metadata
ACFS-07522: snapshot: string (identifier: number) has invalid _SnapParentId:
number, parent snapshot does not exist
message.
Support Services.
ACFS-07523: snapshot: string (identifier: number) has invalid _SnapParentId value

\n found: number, but expected to find: 0\nfor structure:\nstring
message.
Support Services.
ACFS-07524: snapshot: string (identifier: number) has invalid _SnapAncestorIncarn
value\n found: number, but expected to find: 0\nfor structure:\nstring
message.
Support Services.
ACFS-07525: snapshot: string (identifier: number) has invalid _SnapAncestorIncarn
value\n found: number, must be less than _SnapIncarnationNumber: number\nfor
structure:\nstring
ACFS-07526: Volume_Disk_Header has invalid _VolStateFlag values.\n found:
string,\n but expected to find: string \nfor structure:\nstring
ACFS-07527: Volume Disk Header has invalid VolFeatureFlag values \n found:
string \n string \n but expected to find: string \n string \n for structure:\nstring
message.
Support Services.
ACFS-07528: found partially created snapshot: string (identifier: number)
the system.
ACFS-00501 to ACFS-11111 2-117
ACFS-07529: found partially deleted snapshot: string (identifier: number)
system.
Action: n/a
ACFS-07530: snapshot: string (identifier: number) has invalid file identifier\n
found: string maximum: string\nfor structure:\nstring
ACFS-07531: snapshot: (identifier: number) has invalid name: 'string'\nfor
structure:\nstring
ACFS-07532: snapshot: string (identifier: number) has invalid _SnapVisibility value
found: number, but expected to find: number, number or number\for structure:
\nstring
ACFS-07533: duplicate _SnapIncarnationNumber: number found for the following
snapshots:\n
same value. _SnapIncarnationNumber values must be unique.
Support Services.
ACFS-07534: request for disk offset: string exceeds the size for this file system:
string
Cause: A request was made for a disk offset that exceeded the size of the file system.
Action: Reenter the command with a disk offset that is within the limits of the file
system.
ACFS-07536: snapshot: string (identifier: number) has invalid parent snapshot

identifier: number, maximum: number\nstructure:\nstring
ACFS-07537: snapshot: string (identifier: number) has invalid ancestor snapshot:
string (identifier: number)
ACFS-07538: snapshot: string (identifier: number) has invalid ancestor snapshot
(_cycle)
ACFS-07539: Snap_Map_Info structure has invalid _SnapAncestorIncarn value\n
found: number\nfor structure:\nstring
ACFS-07540: deleting snapshot: string (identifier: number) to maintain file system
integrity
Cause: The ACFS Fixer had to delete a snapshot to maintain the integrity of the file
system. Refer to the corresponding message(s) for more information on the
problem(s) associated with the snapshot.
ACFS-07541: Snap_Map_header has invalid value for SnapMapFlags\n found:
string\n string\n but expected to find: string\n string\nfor structure: string
message.
Support Services.
ACFS-07570: snap_map_tuple for disk offset: string conflicts with primary file
system\n found: ( string, string )\n expected: ( 0, 0 )
message.
ACFS-00501 to ACFS-11111 2-119
Support Services.
ACFS-07571: snap_map_tuple for disk offset: string not set in Global BitMap\n
snap_map_tuple: ( string, string )
message.
Support Services.
ACFS-07572: invalid snap_map_tuple found for for disk offset string,\nfirst value
must be less than or equal to second value\n snap_map_tuple: ( string, string )
message.
Support Services.
ACFS-07573: orphan snap_map_tuple found for for disk offset string\n
message.
Support Services.
ACFS-07575: command takes no arguments
Cause: The command entered does not take any arguments.
Action: Reenter the command with no arguments.
ACFS-07585: unable to set File_Entry_Table context
Cause: The ACFS Debug utility was not able to set the File_Entry_Table context.
Lookups by file identifier were disabled. Refer to the accompanying message(s) for
more information on the problem.
Action: Correct the problem described in the accompanying messages if possible by
rerunning the ACFS Fixer.
ACFS-07586: Do you want to continue [y|n] ?
Cause: The ACFS Checker/Fixer or Debug utility detected a situation that could leave
the file system in an inconsistent or unusable state. Refer to the corresponding error
message for more information.
ACFS-07588: metadata read failed at disk offset: string size: string bytes \n- cannot
read beyond file system size: string
Cause: An attempt to read metadata failed because the data requested was beyond
the size of the file system.
ACFS-07590: metadata write failed at disk offset: string size: string bytes\n- cannot
write beyond file system size: string
Cause: An attempt to write metadata failed because the write location was beyond the
Action: The ACFS Fixer will resolve the problem. No further action is needed.
ACFS-07592: metadata structure has incorrect header for:\nstring
Cause: One or more properties of the header of the indicated metadata structure
contained invalid or incorrect values. Refer to accompanying messages for more
ACFS-07601: unable to determine size of file: string
Cause: An attempt to determine the size of the indicated file failed. Refer to the
ACFS-07602: failed to create temporary paging file 'string'
Cause: An attempt to create the indicated temporary paging file failed. Refer to the
ACFS-07603: write failed at position: string for temporary paging file 'string'
Cause: An attempt to write to the indicated temporary paging file failed. Refer to the
ACFS-07604: seek failed at position: string for temporary paging file 'string'
Cause: An attempt to seek within the indicated temporary paging file failed. Refer to
ACFS-07606: read failed at position: string for temporary paging file 'string'
Cause: An attempt to read the indicated temporary paging file failed. Refer to the
ACFS-00501 to ACFS-11111 2-121
Cause: An attempt to read metadata at the indicated offset was incomplete. The
amount of data read did not match the amount requested. Refer to the accompanying
ACFS-07611: Global_BitMap has bits incorrectly set for storage beyond the file
system size\nfor file:\nstring
Cause: The Global_BitMap had bits set in an area reserved for future expansion. All of
these storage bits must be zero. There is no valid storage associated with these bits.
ACFS-07612: file has invalid _NextFreeExtent value:\n found: number minimum:
ACFS-07613: file has invalid _NextFreeExtent value:\n found: number maximum:
ACFS-07614: Global_BitMap's first extent is not located at the expected disk offset
\n found: string, but expected to find: string\nfor file:\nstring
Cause: The first extent of the indicated Global_BitMap was not located at the correct
disk offset. The Global_BitMap's first extent must be located at the disk offset
described in the message.
ACFS-07615: Global_BitMap file has extents that overlap\n Extent[number]
_Length: string _PhysicalDiskOffset: string\n Extent[number] _Length: string
Cause: The extents of the indicated Global_BitMap mapped some or all of the same
storage. All extents within a file must map storage that is mutually exclusive.
ACFS-07616: string has encountered an internal error: could not post error to ACFS
Fixer
unexpected, internal error. Refer to the accompanying message(s) for more
ACFS-07619: truncating file from number bytes to number bytes to ensure metadata
consistency; file content following file offset: number has been lost\nfor file:
\nstring
Cause: The ACFS Fixer was not able to fully repair the indicated file due to an
inconsistency within its metadata. The file had to be truncated to maintain the
integrity of the file system.
Action: Restore the file from a backup copy.
ACFS-07622: resetting _security_descriptor to administrator default value for:\nfor
file:\nstring
Cause: The _security_descriptor the indicated file was invalid or incorrect. It was reset
to the default administrator value.
ACFS Fixer will reset the _security_descriptor to the administrator default value for
the file.
ACFS-07623: unable to repair problem with file _attributes; deleting file to
maintain file system integrity\nfor file:\nstring
Cause: The ACFS Fixer was not able to resolve a problem with the _attributes
property of the indicated file. The file had to be deleted to maintain the integrity of
the file system.
ACFS-07624: file cannot be repaired; deleting file to maintain file system integrity
\nfor file:\nstring
Cause: The ACFS Fixer was not able to repair a problem with the indicated file. The
file had to be deleted to maintain file system integrity.
ACFS-07625: failed to create system directory\nfor file:\nstring
Cause: The ACFS Fixer was not able to create a directory for the indicated internal
system file. Refer to the accompanying message(s) for more information on the
problem.
ACFS-07628: invalid snapshot name 'string' entered
Cause: The snapshot entered did not exist.
Action: Enter the name of a valid snapshot to continue.
ACFS-00501 to ACFS-11111 2-123
ACFS-07629: numeric argument too large: number

Cause: The numeric value entered as an argument exceeded the largest possible value
for this type of argument.
Action: Enter a value that is within the valid range of values for the type of argument.
ACFS-07647: local extent limit reached for extending files; indirect extents not
supported for extending files\nfor file:\nstring
Cause: The ACFS Fixer was not able to create an indirect extent to extend the
indicated file.
ACFS-07648: cannot set Global_BitMap bits for offset: string for number bytes\nfor
file:\nstring
Cause: The ACFS Fixer was unable to set the range of bits described in the message.
ACFS-07649: deleting snapshot to maintain file system integrity
ACFS-07650: unable to repair _VolStateFlag value in Volume_Disk_Header
Cause: The ACFS Fixer was unable to update the _VolStateFlag in the
Volume_Disk_Header. Refer to the accompanying message(s) for more information
on the problem.
ACFS-07652: Volume_Disk_Header has invalid _VolOSCreatedOn value\n found:
number, but expected to find: 1 (Windows_XP), 2 (Linux), 3 (Solaris), or 4 (AIX)
Cause: The _VolOSCreatedOn property of the indicated Volume_Disk_Header was
incorrect. Its value must be one of the values listed in the message.
ACFS-07653: Security_Metadata file _Private structure has invalid
_freeDataListTail value\n found: 0, but expected to find: > 0\nfor structure:
\nstring
Cause: The _freeDataListTail property of the indicated Security_Metadata _Private
metadata structure was invalid. The value must be greater than zero.
ACFS-07655: This file system had been removed. It has now been restored.
Cause: This file system was removed via the acfsutil rmfs utility. It has now been
restored by the ACFS Fixer.
Action: The ACFS Fixer has restored the file system. No further action is required.
ACFS-07656: unable to continue
Cause: The ACFS Checker/Fixer or Debug utility has encountered a fatal error and
cannot continue. Refer to the accompanying message(s) for more information on the
error.
ACFS-07658: Ensure that volume string is not mounted on this node. \nNote that
data displayed may not be current if volume string is mounted on any other node
due to file system caching
Cause: The volume cannot be mounted on this node while running the acfsdbg utility
in read-only mode. This restriction is limited to Windows systems. The acfsdbg utility
reads metadata directly from disk and data may not be current if the file system is
mount on any other nodes due file system caching.
Action: Check to determine if the volume is mounted on any node. The volume must
be unmounted on this node before continuing. The volume should also be
unmounted on all others node if possible. If the volume cannot be unmounted on
other nodes, then reenter any request if the metadata values displayed appear to be
stale. Note: You may have to reenter the request several times to retrieve the latest
metadata.
ACFS-07659: command is disabled in read-only mode
Cause: The command entered attempted to modify file system metadata while
running in read-only mode. Modifications to file system metadata are not allowed
when running the ACFS Debug utility in read-only mode.
Action: Rerun the acfsdbg utility in write mode to modify metadata.
ACFS-07660: unable to modify metadata for volume string; volume is not open
Cause: An attempt to modify metadata failed because the volume was not open. Refer
ACFS-07661: metadata lookup by file identifier is disabled due to lack of
File_Entry_Table context; enter 'primary' or 'snap snapshot name' to set the context
Cause: The acfsdbg utility could not process the request because there was no
File_Entry_Table context. The acfsdbg utility requires a valid File_Entry_Table
context for lookups by file identifier since the same file identifier may appear in
multiple snapshots.
ACFS-07662: unable to set snapshot context due to Snap_Map file metadata
inconsistency
Cause: An attempt to set the metadata lookup context to a snapshot failed because
there was a problem accessing the SnapMap metadata. Refer to the accompanying
ACFS-00501 to ACFS-11111 2-125
rerun the ACFS debug utility.
ACFS-07663: disk offset request: string is not aligned on a sector: number bytes;
results may be inconsistent
Cause: The disk offset entered was not sector aligned. All ACFS metadata structures
are sector aligned.
Action: Reenter the offset so that is properly aligned as described in the
corresponding message.
ACFS-07664: read failed for metadata structure at disk offset: string for number
bytes
Cause: An attempt to read a metadata structure at the indicted disk offset failed. Refer
ACFS-07666: unrecognized metadata found at disk offset: string
Cause: The data found at the indicated disk offset did not contain a valid ACFS
metadata structure type. There are two possible causes: 1. The data at the disk offset
was not an ACFS metadata structure. 2. The metadata structure at the disk offset was
in an inconsistent state.
Action: If the data at the disk offset should be an ACFS metadata structure, then run
the ACFS Fixer to resolve the problem.
ACFS-07667: request for file identifier: string exceeds the maximum value for this
file system: string
Cause: A request was made for a file identifier that exceeded the maximum for the file
system.
Action: Reenter the command with a file identifier that is within the limits of the file
system.
ACFS-07669: metadata lookup by file identifier is disabled due to File_Entry_Table
Services.
ACFS-07685: string is unable to detect the ACFS driver on this system.
\nProceeding could leave the file system in an inconsistent and possibly
\nunusable state if the file system is mounted or being fixed on another system.
Cause: The ACFS Checker/Fixer or Debug utility issued a system call to the ACFS
driver that failed. It appeared that the ACFS driver was not loaded on this system.
Action: The ACFS driver should be loaded on all nodes if possible. Verify that the file
system is not mounted or being fixed on any node. Rerun the ACFS Checker/Fixer or
Debug utility once these steps are complete.
ACFS-07690: data displayed may not be current if volume string is mounted on any
node due to file system caching
Cause: The acfsdbg utility reads metadata directly from disk. Metadata updates to
disk may be delayed due standard file system caching.
Action: Check to determine if the volume is mounted on any node. Unmount the
volume on all nodes if possible. If the volume cannot be unmounted from all nodes,
then reenter any request if the metadata values displayed appear to be stale. Note:
You may have to reenter a request several times to retrieve the latest metadata.
ACFS-07691: command entered: 'string' is invalid or not unique
Cause: There are two possible causes: 1. The command entered was not recognized by
the acfsdbg utility. 2. A partial command name was entered and there was more than
one command that matched the characters entered.
Action: Use the acfsdbg utility help (-h) option for a list of valid commands. Renter
the command, ensuring that enough of the command name is entered to make it
unique.
ACFS-07692: cannot convert disk offset as specified: string
Cause: The format entered for the disk offset was invalid.
ACFS-07693: Volume_Disk_Header has invalid _VolVolumeSize value\n found:
string must be aligned on a number byte boundary\nfor structure:\nstring
Cause: The _VolVolumeSize property of the Volume_Disk_Header was invalid. Its
value must be aligned on the byte boundary described in the message.
ACFS-07694: too many arguments for string
Cause: Too many arguments were supplied for the string option. The string option
takes one argument.
Action: Reenter the command with only one argument for the string option.
ACFS-07695: The ACFS driver should be loaded on all nodes for a safe check of
this file system.
system is not mounted or being checked on any node. Rerun the ACFS Checker/Fixer
or Debug utility once these steps are complete.
ACFS-07696: The file system on volume string is currently in the string state. This
state indicates that a file system check is currently in progress.
Cause: There are two possible causes: 1. The file system on this volume was being
checked on this system or another system in the cluster. 2. The ACFS Checker/Fixer
was unexpectedly terminated leaving the file system state incorrectly set.
Action: Verify that the file system is not being checked on any node. There are a two
possible options if the file system is not being checked on any node: 1. Respond Y(yes)
when prompted to run the ACFS Checker/Fixer. 2. Run the ACFS Fixer with the [f]
option to reset the file system state to allow the file system to be mounted. NOTE: Use
caution with this option as file system repairs from a previous run of the ACFS
Checker/Fixer may be incomplete.
ACFS-00501 to ACFS-11111 2-127
ACFS-07697: unable to determine program name

Cause: The ACFS Checker/Fixer or Debug utility was invoked in a non-standard way
such that the program name could not be determined.
Action: Run the ACFS Checker/Fixer or Debug utility using a standard method.
ACFS-07698: orphan directory found for file identifier: string at disk offset: string
Cause: No parent directory entry was found for the indicated directory file. 1. The
directory file had no corresponding parent directory entry. 2. The directory file had a
parent directory entry, but there was a problem with corresponding parent directory
file.
Action: If the ACFS Fixer is currently running, then no further action is needed. If the
ACFS Checker is running, then run the ACFS Fixer to resolve the problem. The ACFS
Fixer will attempt to repair any directories that are in an inconsistent state first. Any
directory file that does not have a valid parent directory entry following directory
repairs will be moved to the 'lost+found' directory with all of its files.
ACFS-07701: There are metadata transaction log file(s) that have not been
processed. Failure \nto process these transaction logs may result in metadata
inconsistencies. \nDo you want to process the transaction log(s)? [y|n]
Cause: Transaction Log files contain updates to the file system's metadata. The ACFS
Checker found at least one transaction log that was not completely processed. This
indicates that metadata updates were not completed which could leave the file system
Action: Respond yes to process metadata transaction log(s).
ACFS-07705: There are files marked for deletion that have not been removed from
the \nfile system. Failure to remove these files could result in false errors \nbeing
reported. \nDo you want to remove files that are marked for deletion? [y|n]
Cause: The ACFS Checker found files that were marked for deletion but had not been
removed from the file system. False errors may be reported due to the presence of
there files.
Action: Respond yes to remove these files.
ACFS-07708: unable to read File_Entry_Table entry: string at disk offset: string
Cause: An attempt to read the File_Entry_Table for the indicated entry failed. Refer to
ACFS-07709: orphan file (file identifier: string, disk offset: string) marked for
deletion not on delete list
Cause: The indicated file was marked for deletion but it was not found on any of the
delete file lists.
ACFS-07710: orphan file found for file identifier: string at disk offset: string
Cause: No directory entry was found for the indicated file. There are two possible
causes: 1. The file had no corresponding directory entry. 2. The file had a directory
entry, but there was a problem with corresponding directory file.
file that does not have a valid directory entry following directory repairs will be
moved to the 'lost+found' directory.
ACFS-07711: orphan metadata structure (type: string) found for file identifier:
Cause: The indicated metadata structure was found but had no corresponding parent
metadata structure.
ACFS Fixer will move the structure to the free list. If the ACFS Checker is running,
then run the ACFS Fixer to resolve the problem.
ACFS-07720: new allocation size is invalid\n found: number, but expected to find
multiple of: number\nfor file:\nstring
Cause: The new allocation size property of the indicated file was incorrect. Its value
must be a multiple of the file system allocation unit size.
ACFS-07721: file has invalid _NextFreeExtent value\n found: number maximum:
ACFS-07722: file has invalid _NextFreeExtent value:\n found: number minimum:
1\nfor file:\nstring
ACFS-07723: could not clear temporary Global_BitMap bits at offset: string for
number bits
Cause: The ACFS Fixer was unable to free the indicated storage on the temporary
Global_BitMap.
Action: See the preceding error message, and take corrective action.
ACFS-07724: unable to set temporary Global_BitMap bits at offset: string for
number bits
Cause: The ACFS Fixer was unable to reserve the indicated storage on the temporary
Global_BitMap.
ACFS-07725: unable to allocate storage; file system has no free space
Cause: The ACFS Fixer was unable to allocate storage because there was no free
storage available.
ACFS-00501 to ACFS-11111 2-129
Action: There are two options: 1. Free up some storage by deleting some files. 2. Add
available storage by increasing the size of the file system via the 'acfsutil size'
command.
ACFS-07726: could not find sufficient free storage to rebuild Global_BitMap extent
\n found: string requested: string\nfor file:\nstring
Cause: The ACFS Fixer could not find enough contiguous storage to rebuild the
Global_BitMap file's extent map.
command.
ACFS-07727: could not rewrite Global_Bitmap data for file:\nstring
Cause: The ACFS Fixer could not update the file system's storage bitmap. Refer to the
rerun the ACFS Fixer.
ACFS-07728: The Global_BitMap file has reached the maximum number of extents
(number). The file system can no longer be expanded. Running string in fixer mode
will attempt to consolidate the storage bitmap into fewer extents which would
allow for file system expansion via the 'acfsutil size' command.
Cause: The ACFS Checker found the file system's storage bitmap was using its
maximum number of extents.
Action: Running the ACFS Checker/Fixer in Fixer mode will attempt to consolidate
the file system's storage bitmap into two extents allowing future file system
expansion using 'acfsutil size', assuming additional storage is available.
ACFS-07729: The Global_Bitmap file has been\n consolidated into number extents.
\nThis may allow for file system expansion via the 'acfsutil size' command.
Cause: The Global_Bitmap file was using the maximum number of extents supported.
The ACFS Fixer has consolidated the Global_Bitmap file into fewer extents thus
allowing future file system growth using the 'acfsutil size' command if unused
storage is available.
Action: No Action Needed.
ACFS-07733: directory _Private structure has invalid _first_dirnode value\n found:
Cause: The _first_dirnode property of the indicated _Private directory structure was
invalid. Its value exceeded the maximum value for the directory.
ACFS-07734: directory _Private structure has invalid _last_dirnode value\n found:
ACFS-07735: directory _Private structure has invalid _hash_blk_free_list value\n

Cause: The _hash_blk_free_list property of the indicated _Private directory structure
was invalid. Its value exceeded the maximum value for the directory.
ACFS-07736: directory _Private structure has invalid _dir_entry_free_list_head
Cause: The _dir_entry_free_list_head property of the indicated _Private directory
structure was invalid. Its value exceeded the maximum value for the directory.
ACFS-07737: directory _Private structure has invalid _dir_entry_free_list_tail value
Cause: The _dir_entry_free_list_tail property of the indicated _Private directory
ACFS-07740: Could not consolidate the file system's temporary\n storage bitmap to
less than number extents. Need\n at least number bytes free contiguous storage.
Cause: The file system's internal storage bitmap could not be consolidated to less than
five extents because there was insufficient free contiguous storage.
Action: Deleting some files larger than the amount of contiguous storage needed may
free up sufficient contiguous storage so consolidation of the file system's internal
storage bitmap may occur. The 'acfsutil info file filename' command may be used to
examine a candidate file's contiguous extents.
ACFS-07741: could not rebuild file system storage bitmap\n free contiguous bytes
found: number\n contiguous bytes requested: number\nfor file: string
Cause: The ACFS Fixer could not find enough contiguous free storage to rebuild the
file system's storage bitmap.
ACFS-07742: _ustEAContainerEntry property has an invalid value\n found: number
for structure:\nstring
Cause: The _ustEAContainerEntry property of the indicated _ustEAContainer
structure was not within the range of valid offset values.
ACFS Fixer to resolve the problem. The ACFS Fixer reconstructs the structure to
retain as much valid information as possible and may eliminate inaccessible
information.
ACFS-00501 to ACFS-11111 2-131
ACFS-07743: _ustEAEntryHdrFlags property has an invalid value\n found: string

for _ustEAContainerEntry at offset: string for structure:\nstring
Cause: The _ustEAEntryHdrFlags property of the indicated _ustEAContainer
structure contained one or more invalid values.
ACFS-07744: _ustEAEntryHdrNextFreeOffset property has an invalid value\n
found: number, but expected to find: number for _ustEAContainerEntry at offset:
number for structure:\nstring
Cause: The _ustEAEntryHdrNextFreeOffset property of the indicated
_ustEAContainer structure was incorrect.
ACFS-07745: _ustEAEntryHdrNameLen property has an invalid value\n found:
number, but expected to find no greater than: number\n for _ustEAContainerEntry
at offset: string for structure:\nstring
Cause: The _ustEAEntryHdrNameLen property of the indicated _ustEAEntryHdr
property at the _ustEAContainerEntry offset for the indicated _ustEAContainer
structure was invalid. Its value exceeded the maximum length for an extended
attribute name or ACFS tag name.
retain as much valid information as possible and may eliminate inaccessible or
invalid information.
ACFS-07746: ACFS tag name contains invalid syntax\n found: string for
_ustEAContainerEntry at offset: string for structure:\nstring
Cause: The _ustEAEntryName property of the indicated _ustEAContainerEntry
property in the _ustEAContainer structure contained invalid syntax for an ACFS tag
name.
ACFS-07747: _ustEAEntryValueLen property has an invalid value\n found:
number, but expected to find: number\n for _ustEAEntry offset: string for structure:
\nstring
Cause: The _ustEAEntryValueLen property of the indicated _ustEAEntry property in
the _ustEAEntryContainer structure contained an invalid value length.
ACFS-07748: _ustEAEntryValue property has an invalid value\n found: string, but

expected to find: string\n for _ustEAEntry offset: string for structure:\nstring
Cause: The _ustEAEntryValue property of the indicated _ustEAEntry property in the
_ustEAEntryContainer structure contained an invalid value string for an ACFS tag
name.
ACFS-07749: _ustEAContainerHdrNextContainer property has an invalid value\n
found: string for structure:\nstring
Cause: The _ustEAContainerHdrNextContainer property of the indicated
_ustEAContainer structure contained an invalid offset value.
ACFS-07750: _ustEAContainerHdrNumEAEntries property has an invalid value\n
found: number, but expected to find: number for structure:\nstring
Cause: The _ustEAContainerHdrNumEAEntries property of the indicated
_ustEAContainer structure contained an incorrect count of valid entries.
ACFS-07751: Inconsistent amount of available space\n found: number, but expected
to find: number\n for structure:\nstring
Cause: The _ustEAContainer structure had an incorrect amount of free space.
ACFS-07752: _LocalTags property has invalid characters for _FileEntry:\nstring
Cause: The _LocalTags property of the indicted _FileEntry structure contained invalid
characters for ACFS tag names.
ACFS-07753: _ustEAEntry property offset: number is marked free\n but is missing
from the free list for structure:\nstring
ACFS-00501 to ACFS-11111 2-133

ACFS-07754: _ustEAContainer property has inconsistent\n total free and assigned
_ustEAContainerEntry property space\n found: number, but expected to find:
Cause: The _ustEAContainer structure contained free and active
_ustEAContainerEntry property entries that indicate its total space exceeded the size
of a _ustEAContainer structure.
ACFS-07755: _ustEAContainerHdrNextFreeOffset property has an invalid value\n
found: number, but expected to find less than: number for structure:\nstring
Cause: The ustEAContainerHdrNextFreeOffset property of the indicated
_ustEAContainer structure was not within the range of valid offset values.
information.
ACFS-07756: _ustEAEntryHeader.ustEAEntryHdrNextFreeEAOffset property has
an invalid value\n found: number, but expected to find less than: number for
_ustEAContainerEntry at offset: number for structure:\nstring
Cause: The _ustEAEntryHeader.ustEAEntryHdrNextFreeEAOffset property of the
indicated _ustEAContainerEntry property for the _ustEAContainer structure was not
within the range of valid offset values.
information.
ACFS-07757: file extended attribute container structure exceeds file system size:
string\n _Length: string\nfor structure:\nstring
Cause: The extended attribute container structure of the indicated file referenced meta
data beyond the size of the file system. There are two possible causes: 1. The extended
attribute container structure disk offset was incorrect. 2. The file system size value
was incorrect.
ACFS-07758: _ustEAEntryHdrNameLen property has an invalid value\n found:
number, but expected non-zero value\n for _ustEAContainerEntry at offset: string
structure was invalid. Its value was zero but must be non-zero for an extended
attribute name entry.
ACFS-07759: _ustEAEntryValueLen property has an invalid value\n found:
number, but expected to find less than: number\n for _ustEAEntry offset: string for
structure:\nstring
the _ustEAEntryContainer structure contained an invalid value length that was larger
than expected for this structure.
ACFS-07760: _ustEAContainerHdrNextFreeOffset property has an invalid value\n
found: number, but expected to find: number for structure:\nstring
Cause: The _ustEAContainerHdrNextFreeOffset property of the indicated
information.
ACFS-07761: directory _Private structure has invalid _dir_bitmap_start value\n
Cause: The _dir_bitmap_start property of the indicated _Private directory structure
ACFS-07762: Directory contains invalid bitmap block number at disk offset: string
\nfor file:\nstring
Cause: A bitmap block of the indicated directory file was found in the wrong location.
Directory bitmap blocks must be located contiguously after the first bitmap block.
ACFS-07763: Directory bitmap is not contiguous from block number to block
Cause: A discontinuity was seen in the directory bitmap. Directory bitmap blocks
must be located contiguously after the first bitmap block.
ACFS-00501 to ACFS-11111 2-135
ACFS-07764: Directory bitmap has incorrect last block\n found: number expected:
Cause: The directory bitmap does not end where expected.
ACFS-07765: Version 11.2.0.3 or earlier directory contains bitmap block number at
disk offset: string\nfor file:\nstring
Cause: The directory _Private structure indicates that the directory does not have a
bitmap, yet a bitmap block was found in the directory.
ACFS-07766: Directory bitmap does not match state of block number\n bitmap:
string block: string\nfor file:\nstring
Cause: The directory bitmap indicates an incorrect state for the directory block.
ACFS-07767: Directory bitmap contains non-zero value for bit number mapping
beyond end of directory:\nstring
Cause: The directory bitmap contains a non-zero bit in the range mapping blocks
beyond the end of the directory.
ACFS-07768: Directory _Private structure has invalid _dir_bitmap_size value\n
found: string minimum: string\nfor structure:\nstring
Cause: The _dir_bitmap_size property of the indicated _Private directory structure
was invalid. Its value did not meet the minimum value for the directory.
ACFS-07769: Number of bitmap blocks found does not match value of
_dir_bitmap_size in directory _Private structure\n found: number expected: number
Cause: The number of bitmap blocks in the directory does not match the number of
blocks that were expected.
ACFS-07770: System directory _Private structure has invalid on-disk version\n
found: string expected: string\nfor structure:\nstring
Cause: The on-disk version of the indicated _Private directory structure was invalid.
ACFS-07771: directory _Private structure has invalid directory bitmap end value\n
Cause: The calculated end of the directory bitmap of the indicated _Private directory
ACFS-07864: A request to cancel string was made \nwhile the file system was
being repaired. This could leave the file system \nin an inconsistent state. It is
strongly recommended that string \nbe rerun to complete file system repairs.
Cause: The ACFS fixer was cancelled before all file system repairs were completed.
Action: Rerun the ACFS fixer to complete file system repairs.
ACFS-07900: Security_Metadata file _Private structure has invalid _freeDataList
Cause: The _freeDataList property of the _Private structure of the indicated
Security_Metadata file was incorrect. The _freeDataList value exceeded the maximum
value for this Security_Metadata file.
ACFS-07901: Hash_Bucket metadata structure has incorrect _controlling_bkt value
\n found: string maximum: string\nfor structure:\nstring
incorrect. Its value exceeded the maximum value for the hash table.
ACFS-07902: Hash_File_Master_Block metadata structure has incorrect value for
entry number in _hash_bucket_group array\n found: number minimum: number
Hash_File_Master_Block structure was incorrect.
ACFS-07903: Hash_Bucket metadata structure has invalid data; expected all zeros
ACFS-07907: directory file has no storage allocated to it\nfor file:\nstring
ACFS-00501 to ACFS-11111 2-137
ACFS-07908: Root_Directory cannot be repaired\nfile:\nstring
Cause: The ACFS Checker/Fixer found an inconsistency with the Root_Directory
metadata.
Action: The Root_Directory is a critical system file that is necessary for a functioning
file system. Restore the file system from a backup copy.
ACFS-07909: System metadata was truncated, possibly resulting in the deletion of
files.
ACFS-07924: Snap_Map_header has invalid value for RW snap storage not in map
Cause: The Snap_Map_header property that indicates the amount of RW snap storage
not recorded in the Snap_Map file is incorrect.
ACFS-07925: Snap_Map_header has invalid value for snap storage in map\n
Cause: The Snap_Map_header property that indicates the amount of snap storage
recorded in the Snap_Map file is incorrect.
ACFS-07926: Snap_Map_header has invalid value for snap map flags\n found:
Cause: The Snap_Map_header flags field is invalid.
ACFS-07928: Plug-in configuration file has invalid _FileSize value\n found: string,
Cause: The _FileSize property of the indicated plug-in configuration file was
incorrect.
ACFS-07929: The string command is unable to open the storage accelerator volume
string that is associated with this file system.
Cause: fsck (Unix or Linux) or acfschkdsk.exe (Windows) could not open the specified
storage accelerator volume. This could be because the ASM disk group containing the
storage accelerator volume is not mounted.
Action: Verify that the ASM disk group containing the storage accelerator volume is
mounted. Then rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ACFS-07930: Continuing will result in the storage accelerator volume being
removed from the file system, which could leave the file system in an inconsistent
and possibly unusable state if critical system metadata is stored on the storage
accelerator volume.
Action: If the accelerator volume has no known problems, verify that the ASM disk
group containing the storage accelerator volume is mounted. Then rerun fsck (Unix or
Linux) or acfschkdsk.exe (Windows). Or, if the accelerator volume is known to have
problems such as disk corruption and you wish to have fsck (Unix of Linux) or
acfschkdsk.exe (Windows) disassociate the accelerator volume from the file system,
allow it to continue.
ACFS-07932: Volume string does not contain a valid ACFS storage accelerator.
message.
Support Services.
ACFS-07933: Accelerator volume string is associated with a different file system.
message.
Support Services.
ACFS-07934: The file identifier for the accelerator volume storage bitmap is
invalid.\n found: string maximum: string
message.
Support Services.
ACFS-07935: The _FileEntry metadata structure for the accelerator volume storage
bitmap is invalid.
message.
ACFS-00501 to ACFS-11111 2-139
Support Services.
ACFS-07936: Extent structure has incorrect _VolId value.\n found: string\nfor
structure:\nstring
message.
Support Services.
ACFS-07937: File extent exceeds accelerator volume size.\n string\nextent:
_FileOffset: string _Length: string _PhysicalDiskOffset: string\nfor file:\nstring
message.
Support Services.
ACFS-07938: Accelerator Global_BitMap has invalid value for number of bits set.
\n found: string maximum: string\nfor file:\nstring
message.
Support Services.
ACFS-07939: Accelerator Global_BitMap has invalid value for number of bits set.
message.
Support Services.
ACFS-07940: Accelerator Global_BitMap has invalid value for next offset to search.
message.
Support Services.
ACFS-07941: mismatch between temporary Global_BitMap and on-disk accelerator

Global_BitMap
message.
Support Services.
ACFS-07942: Accelerator Global_BitMap has bits incorrectly set for storage beyond
the file system size for file:\nstring
message.
Support Services.
ACFS-07943: The specified volume is an accelerator volume. Cannot proceed.
Cause: The volume specified on the command line was an accelerator volume. The
command requires the primary file system volume.
Action: Rerun the command specifying the primary file system volume.
ACFS-09025: Failed to update the Windows Registry for volume string.
Cause: An attempt to store data in the Windows registry failed. This message is
accompanied by other message(s) that provide details as to the exact cause of the
failure.
Action: Correct the problem indicated by the accompanying messages and retry the
operation.
ACFS-09100: Creating volume 'string' in diskgroup 'string'.
Action: None
ACFS-09101: Failed to create volume 'string' in diskgroup 'string'.
Cause: The volume was unable to be created in the diskgroup. Possible Causes: 1)
ASM is not running. 2) User is not part of the ASMADMIN group. 3) An ASM specific
error occurred.
Action: 1) Verify that ASM is running ('srvctl status asm') 2) Verify that the user is
part of the ASMADMIN group. 3) Check the ASM logs and output for an ASM
specific error.
ACFS-09102: Unable to verify creation of ACFS Oracle database Home.
Cause: A command was given to ASM to create the specified volume and no errors
were detected. However, post creation checks failed to find that the volume that was
created and/or enabled.
Action: Run sqlplus (or asmcmd) to manually create the volume.
ACFS-09103: Enabling volume 'string' on diskgroup 'string'.
ACFS-00501 to ACFS-11111 2-141
Action: None
ACFS-09104: Enable of volume 'string' failed.
Cause: ASM was instructed to enable the specified volume and failed.
Action: Attempt a manual enable via sqlplus or asmcmd.
ACFS-09105: Volume 'string' not found in 'string'.
Cause: The specified volume does not exist.
Action: Create volume via sqlplus or asmcmd.
ACFS-09106: Diskgroup 'string' not found.
Cause: The specified diskgroup does not exist.
Action: Create diskgroup via sqlplus or asmcmd.
ACFS-09107: ASM mounting diskgroup 'string'.
Action: None
ACFS-09108: ASM mount of diskgroup 'string' failed.
Cause: ASM found the specified diskgroup but could not mount it.
Action: Try mounting the diskgroup manually via sqlplus. If the mount fails, check
ASM logs for errors related to the diskgroup, clear errors, and try again.
ACFS-09109: string driver failed to load.
Cause: The driver failed to load.
Action: View the system specific OS kernel log (for instance, /var/log/messages on
Linux, Event Log on Windows). If the drivers have not previously been unloaded
('crsctl stop crs', 'acfsload stop', 'acfsroot uninstall'), it is not possible to reload them. If
a specific error has occurred, than clear the error condition and try again. If the OS
and\or architecture is not supported by the drivers, than contact Oracle Support
Services for an updated driver package.
ACFS-09110: Offline mount point 'string' was dismounted for recovery.
Cause: Informational. The mount point referenced was fenced due to an underlying
volume failure. In this case, the mount point was successfully dismounted for
recovery.
Action: None
ACFS-09111: Offline mount point 'string' was recovered.
Cause: Informational - the mount point referenced was fenced due to an underlying
volume failure. In this case, the mount point was successfully remounted, which has
renabled IO to the file system.
Action: None
ACFS-09112: The following process IDs have open references on mount point
'string':
Cause: During shutdown of the CRS stack, it was determined that a process had files
open on the mount point in the process of being dismounted. This prevents the
dismount from succeeding.
Action: Terminate any process\applications that are using files on the mount point
that is being dismounted before stopping the CRS stack.
ACFS-09113: These processes will now be terminated.

Action: None
ACFS-09114: completed
Action: None
ACFS-09115: The command 'string' returned an unexpected value.
Action: An internal error occurred during the installation process. Restart the
installation process.
ACFS-09116: Offline mount point 'string' was not recovered.
Cause: An inaccessible mount point could not be restored to working condition.
Action: Manual intervention is required to clear the offline mount point. Dismount
the mount point and remount it manually to restore access to the mount point.
ACFS-09117: Manual intervention is required.
Cause: Informational, from previous errors.
Action: Clear previous errors and retry.
ACFS-09118: string driver in use - cannot unload.
Cause: This may be seen during 'crsctl stop crs', 'acfsload stop', or 'acfsroot uninstall'.
Applications (possibly ASM) have open references on the driver.
Action: Terminate applications, including ASM, that may be using the driver and
retry.
ACFS-09119: string driver failed to unload.
Cause: An unknown error has occurred when trying to unload the driver.
Action: Check system specific logs (/var/adm/messages on Linux, Event Log on
Windows) and clear any error conditions that are preventing the unload.
ACFS-09120: The 'string' machine architecture not supported.
Cause: ADVM/ACFS device drivers have not yet been ported to this CPU type or OS.
This occurs when the customer manually tries to load the drivers on an architecture
or system OS type that ACFS is not supported, such as VMS.
Action: Contact Oracle Support Services to determine if an updated driver is available
for this OS and architecture, or install ACFS on a supported architecture and OS.
ACFS-09121: Failed to detect control device 'string'.
Cause: ADVM/ACFS device drivers have been started but the devices that should
have been created have not been.
Action: Try 'acfsload stop' followed by 'acfsload start' or restarting the crs stack 'crsctl stop crs', 'crsctl start crs'. If the control devices still do not exist, contact Oracle
Support Services.
ACFS-09122: ADVM device not determined from mount point 'string'.
ACFS-00501 to ACFS-11111 2-143
ACFS-09123: 'string' command not found.

Cause: A required component of ACFS is missing. This could be an incomplete install,
removal of files from the system after install, or an unknown cause.
Action: Re-install by running 'acfsroot install'. If that does not work, than contact
Oracle Support Services. In the event that handle.exe // is not found, than please
install handle from sysinternals.com or another site, and make sure that the PATH
environment variable contains the install location. Retry the operation.
ACFS-09124: string driver failed to detach from the system driver stack.
Cause: The ACFS driver is being used by one or more mounted file systems.
Action: Unmount all ACFS file systems and retry the operation.
ACFS-09125: ADVM/ACFS is not supported on this OS: 'string'
Cause: ADVM/ACFS device drivers have not been ported to this OS.
Action: None
ACFS-09126: Attempting to terminate the program 'string' with OS process ID
'string'.
Cause: The process was using an ACFS file system, which was being forcibly
unmounted. A kill signal was sent to allow the unmount to proceed.
Action: This message is informational.
ACFS-09127: Not all ADVM/ACFS drivers have been loaded.
Cause: ADVM/ACFS device drivers have been started but not all of them are
detected as running.
Action: Try 'acfsload stop' followed by 'acfsload start'. If that does not start all drivers,
than contact Oracle Support Services.
ACFS-09128: unknown query type 'string'
ACFS-09129: ADVM/ACFS not installed
Cause: No ADVM/ACFS drivers or commands have been found on the system. All
ADVM and ACFS actions will be disabled.
Action: Install components using 'acfsroot install options'. No ACFS file systems or
ADVM volume devices will be available until ADVM/ACFS has been installed.
ACFS-09130: Root access required
Cause: The user this command is executing as does not have sufficient privileges to
run this command.
Action: Run this command as a user with administrative privileges.
ACFS-09135: string installation aborted.
Action: See preceding error message for more information.
ACFS-09136: PID string could not be killed.
Cause: Failed to kill a Process ID during a force unmount of a file system.
Action: Manually kill the process and retry the unmount.
ACFS-09137: Failed to set group on directory 'string'.

Cause: The group of the directory could not be changed.
Action: Make sure the user has permission to do so.
ACFS-09138: command 'string' completed with an error: string
Cause: 'acfsutil' did not successfully run.
Action: Correct the problem described in the accompanying error message from
'acfsutil'. If this error was returned within the context of a CRS resource execution,
retry the CRS action after the problem is resolved.
ACFS-09139: Attempting recovery of offline mount point 'string'
Cause: An ACFS mount point reported by the 'acfsutil' command was not accessible.
Action: This message is informational. CRS will attempt to recover the mount point.
ACFS-09140: Unable to determine the correct drivers for this version of Windows:
ID:string Major:string Minor:string Product Type:string
Cause: Error. ACFS is not supported on this Windows Version.
Action: Report this message to Oracle Support Services to determine if an update to
ACFS is available.
ACFS-09149: unable to determine device mount status - unsupported OS name
'string'
Cause: The standard method to determine mount state of a device was unavailable. It
is possible that ADVM/ACFS is not supported on the OS.
Action: Report the value of OS to Oracle Support Services.
ACFS-09150: Unexpected output from 'acfsutil info fs': 'string'.
Action: None
ACFS-09151: Ignoring request to mount due to existence of "oracle_nomounts" file:
string
Cause: "An "oracle_nomounts" file was present, causing file system mount processing
to be skipped during a CRS resource operation."
Action: Normal mount operations can be resumed by removing the
"oracle_nomounts" file.
ACFS-09152: Program 'string' with OS process ID 'string' will not be terminated.
Cause: The process is using an ACFS file system which is being forcibly unmounted
but it will not be terminated because it is a system critical process.
Action: Manual intervention may be required.
ACFS-09153: Program 'string' with OS process ID 'string' is using mount point
'string'.
Cause: The process is using the mount point.
Action: None - Informational.
ACFS-09154: Loading 'string' driver.
Action: None
ACFS-00501 to ACFS-11111 2-145
ACFS-09155: Checking for existing 'string' driver installation.

Action: None
ACFS-09156: Detecting control device 'string'.
Action: None
ACFS-09157: Detecting driver 'string'.
Action: None
ACFS-09158: Configuration file 'string' in the /boot directory is not accessible.
Cause: A populated /boot directory, which contains static files required to install
kernel modules, was not detected on the system.
Action: After restoring the /boot directory and the kernel configuration files, re-run
"acfsroot install".
ACFS-09160: Can not use the silent and verbose options at the same time.
Cause: The -s and -v options were used in the command. These options are mutually
exclusive.
Action: Re-execute the command with one of the options or neither.
ACFS-09161: acfsroot install: Install ADVM/ACFS components.
Action: None
ACFS-09162: acfsroot uninstall: Uninstall ADVM/ACFS components.
Action: None
ACFS-09163: acfsroot version_check: Check ADVM/ACFS version.
Action: None
ACFS-09164: acfsroot enable: Enable ADVM/ACFS CRS resources.
Action: None
ACFS-09165: acfsroot disable: Disable ADVM/ACFS CRS resources.
Action: None
ACFS-09166: string [-h] [-s | -v]
Cause: Syntax error or help [-h] option was passed.
Action: Use syntax as specified in the 'Usage' message.
ACFS-09167: ADVM/ACFS is not installed or loaded. Run 'acfsroot install'.
Cause: An operation was requested that requires ADVM/ACFS to be running.
Action: Run 'acfsroot install' and then run the requested operation.
ACFS-09168: The CRS query "string" cannot be parsed.

ACFS-09169: The CRS attribute value specification "string" is invalid.
ACFS-09170: The file system's CRS resource name "string" is invalid.
ACFS-09171: The CRS resource for the file system on device string cannot be
retrieved
ACFS-09172: The CRS resource for the file system on device string cannot be
registered
ACFS-09173: The srvctl command line "string" failed to execute. (number)
ACFS-09174: unable to communicate with CRS
ACFS-09175: Invalid trace level. Valid values for trace level are 0, 1 or 2.
Cause: An invalid trace level was provided.
Action: Use a supported trace level: 0, 1, or 2.
ACFS-09176: Entering 'string'
Action: None
ACFS-09177: Return from 'string'
Action: None
ACFS-09178: Return code = string
Action: None
ACFS-09179: Command executed: 'string', output = 'string'
Action: None
ACFS-00501 to ACFS-11111 2-147
ACFS-09180: Sub-command is 'string'

Action: None
ACFS-09181: Kernel version is 'string'
Action: None
ACFS-09182: Variable 'string' has value 'string'
Action: None
ACFS-09183: Query = 'string'
Action: None
ACFS-09184: string [-h] [-s | -v | -t <0,1,2>]
Cause: Either a syntax error or unknown option was specified, or the help (-h) option
was specified.
ACFS-09185: string [-h] [-s | -v | -t <0,1,2>] [-l directory]
was specified.
ACFS-09186: Usage: acfsroot uninstall [-h] [-s | -v | -t <0,1,2>]
was specified.
ACFS-09187: Usage: acfsroot version_check [-h] [-t <0,1,2>] [-l location]
was specified.
ACFS-09188: cannot use the trace option with the silent or verbose options
Cause: Conflicting options were specified.
Action: Specify only one of -s, -v, and -t.
ACFS-09189: [-t <0,1,2> ] - trace level
was specified.
ACFS-09190: User group 'string' does not exist.
Cause: The group name is required to create ADVM/ACFS devices with the correct
attributes. The group name could not be found in the /etc/group file nor in the
various remote services like LDAP, AD, NIS/Yellow Pages, DNS, etc.
Action: Ensure that the required group exists, then re-run the command.
ACFS-09191: Usage: acfsroot version_check [-h] [-t <0,1,2>]

was specified.
ACFS-09200: Supported
Cause: ADVM/ACFS device drivers have been ported to this OS or CPU type.
ACFS-09201: Not Supported
Cause: ADVM/ACFS device drivers have not yet been ported to this OS or CPU type.
Action: None
ACFS-09203: true
Cause: ADVM/ACFS device drivers were installed/loaded.
Action: None
ACFS-09204: false
Cause: ADVM/ACFS device drivers were not installed/loaded.
Action: None
ACFS-09205: usage: string [-h] [-orahome <home_path>] {installed | loaded |
version | supported | validate} [-s]
ACFS-09206: usage: string [-orahome <ORACLE_HOME>] {installed | loaded |
version | supported} [-s]
Cause: Syntax error.
ACFS-09207: The user this command is executing as does not have permission to
execute Perl in 'string'.
Cause: Perl permissions are read/write/execute owner (0700). The user this
command is executing as is not the owner of the perl binary.
Action: Enter the db home as an argument to -orahome. Ensure that the user
executing the command has execute permission on the perl binary in that db home.
ACFS-09208: Enter the location of the db home for this database to '-orahome'.
ACFS-09210: The ADVM/ACFS drivers are supported but have not been verified
on this Operating System version.
Cause: The drivers have not been explicitly tested on this operating system version
but are expected to work properly.
ACFS-00501 to ACFS-11111 2-149
ACFS-09211: usage: string [-h] [-orahome <home_path>] {installed | loaded |

ACFS-09225: Failed to start OKS persistent logging.
Cause: The drivers were successfully loaded but OKS persistent logging failed to
start.
Action: run "acfsutil plogconfig -d GridHome" to perform a manual start.
ACFS-09226: ADVM/ACFS drivers not correct for this OS - cannot load.
Cause: The device drivers installed are not compatible with the currently running
operating system
Action: run "acfsroot install options" to install the correct drivers.
ACFS-09250: Unable to get the ASM administrator user name from the ASM
process.
Cause: ASM processes have not been found running on this system. This will prevent
the requested action from being completed.
Action: Start ASM ('srvctl start asm') and retry the operation.
ACFS-09251: Mount point 'string' unmounted.
Action: None
ACFS-09252: The following process IDs have open references on mount point
'string':
Action: None
ACFS-09253: Failed to unmount mount point 'string'. Mount point likely in use.
Cause: Other processes have outstanding open references on the mount point.
Action: Terminate applications using files on the mountpoint than retry the //
operation (' crsctl stop crs' ).
ACFS-09254: Manual intervention is required.
Cause: Follow up message to ACFS-9253.
ACFS-09255: Creating 'string' mount point.
Action: None
ACFS-09256: Failed to create mountpoint 'string'.
Cause: The mount point may already exist, the user executing the command may
have insufficient permission, or a system specific error may have occurred.
Action: Choose another mount point, execute the action from an account with the
required permissions, or resolve the specified error shown before this message.
ACFS-09257: Mounting device 'string' on mount point 'string'.
Action: None
ACFS-09258: Failed to mount device 'string' on mount point 'string'.
Cause: The mount point may be in use, the user executing this command may have
insufficient permissions, or another system specific error may have occurred.
Action: Make sure that the mount point is available, ensure the user executing the
command has the correct permissions, or resolve any system error shown before this
message.
ACFS-09259: Mount point 'string' already has a device mounted on it.
Cause: There is already a device mounted on this mount point.
Action: If the new device is meant to replace the old device on this mount point,
unmount the old one first and retry the operation. Otherwise this error may be
ignored.
ACFS-09260: Failed to connect to the ASM instance.
Cause: ASM connection attempt failed.
Action: Ensure that the ORACLE_SID environment variable is correctly set to // the
value of the ASM instance. In addition, verify that ASM is running ('srvctl status
asm').
ACFS-09261: Invalid _ORA_NAME format.
Action: Report this to Oracle Support Services.
ACFS-09262: Invalid sub-command 'string'.
Cause: This is an internal error or the user attempted to run the script manually with
an incorrect sub-command.
Action: Contact Oracle Support Services or use a correct sub-command.
ACFS-09263: Valid sub-commands are 'start', 'stop', 'check', and 'clean'.
Cause: This results in an incorrect usage of the command.
Action: Run the command with an option (command) that is supported, such as
'start', 'stop', 'check', or 'clean'.
ACFS-09264: Mount point 'string' is not mounted.
Action: None
ACFS-09274: Resource 'string' is not online.
Action: None
ACFS-09275: The clean failed to unmount the required mountpoint(s) - re-trying.
Cause: Informational. A file system could not be unmounted. This could be due to
new process being started just before the unmount.
Action: None. 9276 - 9288 UNUSED
ACFS-09289: string not set in environment.
Cause: The referenced environment variable was not set. This makes it impossible to
continue with the requested action.
Action: Ensure that the referenced variable is set and retry the operation.
ACFS-00501 to ACFS-11111 2-151
ACFS-09290: Waiting for ASM to shutdown.

Cause: The resource cannot be terminated while ASM is running.
Action: Wait for ASM to stop. Stop it manually if that does not happen.
ACFS-09291: Waiting for the Windows 'sc stop string' command to complete.
Cause: Informational. System activity is preventing the driver from stopping.
Action: If the driver does not unload, a node reboot may be necessary
ACFS-09300: ADVM/ACFS distribution files found.
Action: None
ACFS-09301: ADVM/ACFS installation cannot proceed:
Cause: Previous errors have caused the installation to reach a point where it cannot
continue.
Action: Fix previous errors.
ACFS-09303: No installation files found for OS kernel version string.
Cause: If '-l' (distribution directory) was specified, the directory may not be valid.
Action: Choose a proper distribution location version.
ACFS-09304: Installation cannot proceed: Failed to unload ADVM/ACFS drivers.
Cause: Applications (possibly ASM) have open references on the drivers.
Action: Terminate applications and ASM that may be using the drivers, and retry the
installation.
ACFS-09305: ADVM/ACFS installation cannot proceed:
Action: Clear previous error and retry.
ACFS-09306: Failed to uninstall previous installation.
Cause: Could not remove ADVM/ACFS commands and or drivers.
Action: Commands and/or drivers are likely in use. Wait for operations to finish,
unload the drivers, and retry the installation.
ACFS-09307: Installing requested ADVM/ACFS software.
Action: None
ACFS-09308: Loading installed ADVM/ACFS drivers.
Action: None
ACFS-09309: ADVM/ACFS installation correctness verified.
Action: None
ACFS-09310: ADVM/ACFS installation failed.
Cause: A previous error caused this installation to fail.
Action: Correct previous error and retry the installation.
ACFS-09311: not all components were detected after the installation.

Cause: ADVM/ACFS commands and drivers were found in the installation area but
did not get placed in their assigned locations.
Action: Re-install using 'acfsroot install -l options'. If necessary, contact Oracle Support
Services.
ACFS-09312: Existing ADVM/ACFS installation detected.
Action: None
ACFS-09313: No ADVM/ACFS installation detected.
Cause: An attempt was made to un-install ADVM/ACFS components that did not
exist on the system.
Action: None - there is no problem.
ACFS-09314: Removing previous ADVM/ACFS installation.
Action: None
ACFS-09315: Previous ADVM/ACFS components successfully removed.
Action: None
ACFS-09316: Valid ADVM/ACFS distribution media detected at: 'string'
Action: None
ACFS-09317: No ADVM/ACFS distribution media detected at location: 'string'
Cause: If -l (location) is used, the directory specified may be invalid.
Action: Use the correct directory.
ACFS-09318: ORACLE_HOME is not set.
ACFS-09319: Unknown OS kernel version 'string' detected.
ACFS-09320: Missing file: 'string'.
Cause: A required command or driver is not found on the installation media (pre
install) or system (post install).
Action: If post install, try running acfsroot again. Otherwise, contact Oracle Support
Services.
ACFS-09321: Creating udev for ADVM/ACFS.
Action: None
ACFS-00501 to ACFS-11111 2-153
ACFS-09322: completed
Action: None
ACFS-09323: Creating module dependencies - this may take some time.
Action: None
ACFS-09324: Alternate drivers installed.
Action: None
ACFS-09327: Verifying ADVM/ACFS devices.
Action: None
ACFS-09328: unknown query type 'string'.
ACFS-09329: Failed to uninstall driver: 'string'.
Cause: Acfsinstall failed to uninstall the driver.
Action: Drivers may be in use. Correct previously reported errors and retry uninstall.
If that fails, contact Oracle Support Services.
ACFS-09330: Binary 'string' not installed.
Cause: A component that should have been installed was not installed.
Action: Rerun 'acfsroot install'.
ACFS-09339: The environment variable ORACLE_HOME is not set.
ACFS-09340: failed to install string driver.
Cause: Acfsinstall failed to install the driver.
Action: Run acfsinstall manually to see reported errors, resolve them, and retry.
ACFS-09341: Binary 'string' not found.
Cause: One of the binaries that make up the ACFS package is missing.
Action: Reinstall the ACFS package and retry the operation.
ACFS-09343: Unable to retrieve OS kernel version from module string.
Cause: Running modinfo against the usm driver failed.
Action: None - the current OS kernel version will be used instead.
ACFS-09344: Missing directory: 'string'.
Cause: A required directory is not found on the system.
ACFS-09345: Unable to create directory: 'string'.

Cause: Creation of a required directory failed.
ACFS-09346: Unable to install file: 'string'.
Cause: Copying to the given destination failed.
Action: Rerun acfsroot after correcting the OS error.
ACFS-09347: Unable to set permission bits (string) on: 'string'.
Cause: Setting the given permission bits failed.
Action: Manually set the permissions to the required level.
ACFS-09348: Unable to remove 'string'.
Cause: A previously installed file was unable to be removed.
Action: Attempt to manually remove the file.
ACFS-09349: Unable to configure driver 'string'.
Cause: A driver was installed but add_drv failed to write a configuration file.
Action: Correct the OS error and re-run acfsroot install.
ACFS-09350: Failed to create a symbolic link from 'string' to 'string'.
Cause: Creating a symbolic link failed.
ACFS-09351: Unable to remove devlink entry for 'string'.
Cause: An entry for the driver was found in /etc/devlink.tab but it was not possible
to remove the entry.
Action: Manually remove the entry from /etc/devlink.tab and re-run acfsroot
uninstall
ACFS-09352: Unable to write to 'string'.
Cause: A file required modifications but it was not possible to write to it.
Action: Check the file permissions.
ACFS-09353: Unable to unconfigure string.
Cause: A call to rem_drv failed.
Action: Correct the OS error and re-run acfsroot uninstall.
ACFS-09354: Unable to create symlink: 'string'.
Cause: Ensure that a file with the same name does not already exist and the user has
permission.
Action: Remove the existing file and make sure the user has the required permission.
ACFS-09355: Performing AIX setup failed with error code 'string'.
Cause: Running AIX initial setup has failed.
Action: Correct the error and re-run the root install script.
ACFS-09356: Saving the AIX ODM changes for 'string' failed with error code
'string'.
Cause: Running the AIX savebase command failed.
ACFS-00501 to ACFS-11111 2-155
ACFS-09357: Getting the ASMADMIN group failed with error code 'string'.
Cause: Previous installation steps may have failed.
Action: Correct the preceding error and re-run the root install script.
ACFS-09358: Adding the AIX ODM entry for 'string' failed with error code 'string'.
Cause: Running the AIX odmadd command failed.
ACFS-09360: The command aixsetup failed with error code 'string'.
Cause: Running the aixsetup script failed.
ACFS-09361: Removing device 'string' failed with error code 'string'.
Cause: Running the device's undefine method failed.
Action: Correct the error and re-run the root uninstall script.
ACFS-09362: Warning: deleting the AIX ODM entry for 'string' failed with error
code 'string'.
Cause: Running the odmdelete command failed.
Action: Manually remove the entry or ignore the message.
ACFS-09363: Opening the file /etc/vfs for read failed.
Cause: The /etc/vfs file is not readable.
Action: Check the permission of the file and ensure it has read permission.
ACFS-09364: Opening the file /etc/vfs for append failed.
Cause: The /etc/vfs file is not writable.
Action: Check the permission of the file and ensure it has write permission.
ACFS-09365: The directory 'string' is not being removed.
Cause: The directory was scheduled to be uninstalled, but it contained files that were
not installed by acfsroot.
Action: Manually remove the directory.
ACFS-09366: Relative path for mount point 'string' is not supported.
Cause: Mount point was provided as a relative path.
Action: Specify the mount point in the form of an absolute path.
ACFS-09381: Modification of ADVM/ACFS drivers resource failed.
Cause: An attempt to modify the ACFS drivers resource resulted in an error.
ACFS-09382: Modification of ADVM/ACFS drivers resource succeeded.
Action: None
ACFS-09383: ADVM/ACFS uninstall cannot proceed
Cause: ADVM/ACFS uninstall cannot proceed due to an error. This message is
Action: Correct the problem indicated in the other messages.

ACFS-09384: Invalid OS kernel variation 'string'.
Cause: The command found an OS kernel variation (e.g., "el5", etc) that it did not
recognize as a valid ADVM/ACFS supported kernel.
Action: Boot a supported kernel
ACFS-09385: Usage: acfsroot version_check [-h] [-l location]
ACFS-09388: An absolute path name must be specified for the alternate location.
Cause: A relative path name to the distribution files was specified.
Action: Enter the absolute path name instead.
ACFS-09389: ORACLE_HOME is not set to the location of the Grid Infrastructure
home.
Cause: The ORACLE_HOME environment variable was not set correctly.
Action: Make sure that the ORACLE_HOME environment variable is set to the
location of the Grid Infrastructure home and that it is properly exported.
ACFS-09390: The command 'string' returned unexpected output that may be
important for system configuration:
Cause: One of the operating system commands used to configure the system returned
an unexpected error. This message is accompanied by other message(s) providing
details of the error.
Action: See the operating system documentation for the specific command for more
information on this error.
ACFS-09391: Checking for existing ADVM/ACFS installation.
Action: None
ACFS-09392: Validating ADVM/ACFS installation files for operating system.
Action: None
ACFS-09393: Verifying ASM Administrator setup.
Action: None
ACFS-09394: The installed driver string has a build date of string which does not
match the loaded kernel module build date of string.
Cause: The most likely cause is that an upgrade or patch procedure failed to unload
the kernel module.
Action: Reboot the system before attempting to use ACFS.
ACFS-09395: Environment variable ODMDIR is not set, unable to proceed with
system configuration.
Cause: Environment variable ODMDIR was not set.
Action: Ensure that the ODMDIR environment variable is set to the location of a valid
AIX ODM device configuration database.
ACFS-00501 to ACFS-11111 2-157
ACFS-09396: Environment variable ODMDIR specifies a nonexistent path, unable

to proceed with system configuration.
Cause: Environment variable ODMDIR specified a nonexistent path.
ACFS-09397: Modification of ADVM/ACFS registry resource failed.
Cause: An attempt to modify the ACFS registry resource resulted in an error.
ACFS-09398: Modification of ADVM/ACFS registry resource succeeded.
Action: None
ACFS-09399: Calling 'acfsroot install' to install compatible ADVM/ACFS drivers.
Action: None
ACFS-09400: Could not open the Service Control Manager.
Cause: You do not have administrator access.
Action: Log onto a user account with administrator privileges and retry.
ACFS-09401: Failed to install the driver.
Cause: The specified driver could not be installed.
Action: Respond based on the accompanying error message.
ACFS-09402: The driver file path is too long.
Cause: The path to the driver exceeded system limits.
Action: Move the driver to a shorter path or create a shorter link.
ACFS-09403: The driver can be either installed or removed, not both.
Cause: The /i and the /u switches are mutually exclusive.
Action: Use either /i to install or /u to uninstall the driver.
ACFS-09404: Specify either /i (install) or /u (uninstall).
Cause: Either /i to install or /u to uninstall the driver is required.
Action: The /i or the /u switch must be specified.
ACFS-09405: Only one driver can be installed at a time.
Cause: Multiple drivers were specified with the /i option.
Action: Enter only one driver on the command line.
ACFS-09406: Specify either /a (ADVM) or /o (ACFS) or /l (OKS).
Cause: The driver to be installed or uninstalled was not specified.
Action: Enter the driver option on the command line.
ACFS-09407: Could not find driver "string" in the current directory.
Cause: The driver could not be found in the directory specified.
Action: Verify and enter the correct driver path name.
ACFS-09408: The current directory is %"s".

Action: None
ACFS-09409: CreateService failed (ERROR_SERVICE_EXISTS).
Cause: The driver service already exists.
Action: None. The service is active.
ACFS-09410: CreateService failed.
Cause: The driver service could not be created.
Action: Correct the problem indicated by the accompanying error message and retry
the operation.
ACFS-09411: CreateService succeeded.
Action: None
ACFS-09412: The driver was installed successfully.
Action: None
ACFS-09413: RegCreateKeyEx failed.
Cause: Failed to create a Windows registry key.
the operation.
ACFS-09414: RegSetValueEx (TypesSupported) failed.
Cause: Failed to set the Windows registry key.
the operation.
ACFS-09415: RegSetValueEx (EventMessageFile) failed.
the operation.
ACFS-09416: OpenService failed.
Cause: Could not start the driver.
the operation.
ACFS-09417: The driver was started successfully.
Action: None
ACFS-09418: StartService failed (SERVICE_ALREADY_RUNNING).
Action: None. The driver is already running.
ACFS-09419: StartService failed.
Cause: The driver failed to start.
ACFS-00501 to ACFS-11111 2-159
the operation.
ACFS-09420: The driver is not currently installed on this node.
Cause: The driver is not installed to start.
Action: Install the driver using the '/i' option.
ACFS-09421: The driver is already installed on this node.
Cause: An attempt was made to install a driver that is already installed.
Action: None
ACFS-09422: The driver was removed successfully.
Action: None
ACFS-09423: Failure trying to remove the driver, DeleteService failed.\n The driver
service is pending deletion or is in an invalid state.
Cause: The driver could not be removed.
Action: Make sure that all references to the driver have been removed and, if the
driver is "oracleacfs.sys", that "acfsutil detach" has been run. Verify that the driver is
in the STOPPED state and then retry the operation. If the driver removal still fails,
you probably need to reboot the node."
ACFS-09424: The driver was stopped successfully.
Action: None
ACFS-09425: The driver could not be stopped: StopService failed.
Cause: The driver could not be stopped.
the operation.
ACFS-09426: Unable to set the file attributes for file string.
Cause: The file attributes for the oject file could not be set.
Action: Reset the attributes with "attrib -r <file_name>" and then retry the operation.
ACFS-09427: Failed to unload ADVM/ACFS drivers. A system reboot is
recommended.
Cause: An attempt to unload the ADVM/ACFS drivers was unsuccessful due to an
unanticipated condition or configuration. The operating system state did not allow
the driver to be unloaded successfully.
Action: Reboot the system to reestablish the operating system environment.
ACFS-09428: Failed to load ADVM/ACFS drivers. A system reboot is
recommended.
ACFS-09429: Failed to install ADVM/ACFS files.

Cause: An unexpected condition has been detected. The files were previously verified
to exist.
Action: Check the file permissions. Contact Oracle Support if the problem cannot be
resolved.
ACFS-09441: /i Install the driver
ACFS-09442: /u Uninstall the driver
ACFS-09443: /a Perform the operation for the ADVM driver
ACFS-09444: /o Perform the operation for the ACFS driver
ACFS-09445: /l Perform the operation for the OKS driver
ACFS-09446: path Path to the driver. If not specified,\n defaults to oracleadvm.sys,
oracleacfs.sys, or\n oracleoks.sys in the current directory\n
ACFS-09450: Examples:
Action: None
ACFS-09451: string /i /a (Install the ADVM driver from the current directory)
Action: None
ACFS-09452: string /u /o (Uninstall the ACFS driver)
Action: None
ACFS-09453: string /i /o c:\drivers\oracleacfs.sys (Install ACFS with the specified
file)
Action: None
ACFS-09454: Unable to delete the driver file string after stopping driver.
Cause: A call to the Windows DeleteFile function to delete the driver file failed.
ACFS-00501 to ACFS-11111 2-161
Action: Manually delete the specified driver file using Windows Explorer. If you were
installing the driver please retry after deletion.
ACFS-09455: Unable to copy driver file string to the path string.
Cause: Could not copy the driver file to the specified directory because the Windows
CopyFile function failed.
Action: Manually delete any previous driver file from the specified directory using
Windows Explorer and retry the install.
ACFS-09456: An attempt to stop the driver string failed.
Cause: The driver could not be properly stopped; it is in an invalid state.
Action: Reboot system.
ACFS-09457: The driver file does not match the driver chosen to install.
Cause: The driver file is not consistent with the driver option used.
Action: Specify a path to oracleoks.sys when using the /l option. path to
oracleacfs.sys with the /o option and path to oracleadvm.sys with the /a option.
ACFS-09458: The Windows 'string' service is in an invalid state. The new driver
cannot be installed.
Cause: An attempt to install the new driver failed because the existing service could
not be stopped properly.
Action: Reboot system and then retry the install.
ACFS-09459: ADVM/ACFS is not supported on this OS version: 'string'
Cause: ADVM/ACFS device drivers have not been ported to this OS version.
Action: None
ACFS-09500: Location of Oracle Home is 'string' as determined from the internal
configuration data
Action: None
ACFS-09501: Location of Oracle Home is 'string' as determined from the
ORACLE_HOME environment variable
Action: None
ACFS-09502: Location of Oracle Home is 'string' as determined from the location of
the Oracle library files
Action: None
ACFS-09503: ADVM and ACFS driver media location is 'string'
Action: None
ACFS-09504: Copying file 'string' to the path 'string'
Action: None
ACFS-09505: Using acfsutil executable from location: 'string'

Action: None
ACFS-09506: The files 'string' and 'string' are the same, not copying.
Cause: Informational. The file was not copied because the target and source point to
the same file.
Action: None
ACFS-09507: Searching the alternative location: 'string'
Cause: Informational. The installation files were not found in the specified location. A
likely path containing that location will be searched.
Action: None
ACFS-09508: ACFS installation aborted (component string).
Cause: Installation was aborted due to an error.
ACFS-10101: Authentication failed.
Cause: The specified ACFS Security administrator password was wrong.
Action: Re execute the command and provide the correct ACFS Security
administrator password at the prompt.
ACFS-10120: ACFS Encryption not initialized.
Cause: ACFS Encryption was not initialized.
Action: Run 'acfsutil encr init [-p]' as system administrator to initialize encryption.
ACFS-10149: Realm description cannot exceed number characters
Cause: Realm description cannot exceed 1023 characters
Action: Select a shorter realm name and retry.
ACFS-10150: Realm description not specified within double quotation marks
Cause: Invalid description specified for realm.
Action: Enclose the realm description within double quotation marks.
ACFS-10151: Unmatched single quote or double quote.
Cause: Matching quote was not found.
Action: Add a matching quote and retry.
ACFS-10152: Realm name cannot exceed number characters.
Cause: Realm name length exceeded 255 characters.
ACFS-10153: Realm 'string' not found on mount point 'string'.
Cause: Realm was not found on mount point.
Action: Ensure that the realm exists using the command 'acfsutil sec info -m
<mount_point> -n'.
ACFS-10154: Failed to create realm 'string' on mount point 'string'.
ACFS-00501 to ACFS-11111 2-163
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec<host_name>.log'.

ACFS-10155: Realm 'string' created.
Cause: Realm was created.
Action: None
ACFS-10156: Failed to destroy realm 'string' on mount point 'string'.
ACFS-10157: Realm 'string' destroyed.
Cause: Realm was destroyed.
Action: None
ACFS-10158: Improper value specified for -l option.
Cause: Invalid argument format was specified for -l option.
Action: Specify the argument in the format 'commandrule:ruleset'. A comma
separated list can also be specified as 'cmd1:rs1,cmd2:rs2,cmd2:rs3'. For example: * acfsutil sec realm add r1 -m /mnt -l READ:rs1 * - acfsutil sec realm add r1 -m /mnt -l
READ:rs1,MKDIR:rs2
ACFS-10159: The command requires at least one of the options -u, -G, -l, -f, or -e.
Cause: None of the options -u, -G, -l, -f, or -e were specified with this command.
Action: Specify at least one of the options -u, -G, -l, -f, or -e with this command.
ACFS-10160: Failed to add user 'string' to the realm 'string'.
ACFS-10161: Added user 'string' to realm 'string'.
Cause: User was added to realm.
Action: None
ACFS-10162: Failed to add group 'string' to realm 'string'.
ACFS-10163: Added group 'string' to the realm 'string'.
Cause: Group was added to the realm.
Action: None
ACFS-10164: Failed to add filter 'string:string' to the realm 'string'.
ACFS-10165: Added filter 'string:string' to the realm 'string'.

Cause: Filter was added to the realm.
Action: None
ACFS-10166: Failed to add 'string' to the realm 'string'.
ACFS-10167: Added 'string' to the realm 'string'.
Cause: Pathname was added to the realm.
Action: None
ACFS-10168: Failed to turn encryption ON for realm 'string'.
ACFS-10169: Encryption turned ON for realm 'string'.
Cause: Encryption was turned ON for realm.
Action: None
ACFS-10170: Failed to delete user 'string' from realm 'string'.
ACFS-10171: Deleted user 'string' from realm 'string'.
Cause: User was deleted from realm.
Action: None
ACFS-10172: Failed to delete group 'string' from the realm 'string'.
ACFS-10173: Deleted group 'string' from realm 'string'.
Cause: Group was deleted from realm.
Action: None
ACFS-10174: Failed to delete filter 'string:string' from the realm 'string'.
ACFS-10175: Deleted filter 'string:string' from realm 'string'.
Cause: Filter was deleted from realm.
Action: None
ACFS-00501 to ACFS-11111 2-165
ACFS-10176: Failed to delete 'string' from realm 'string'.

ACFS-10177: Deleted 'string' from realm 'string'.
Cause: Pathname was deleted from realm.
Action: None
ACFS-10178: Failed to turn encryption OFF for realm 'string'.
ACFS-10179: Encryption turned OFF for realm 'string'.
Cause: Encryption was turned OFF for realm.
Action: None
ACFS-10180: Failed to get realm files or directories for realm 'string'.
ACFS-10181: Failed to get groups for realm 'string'.
ACFS-10182: Failed to get users for realm 'string'.
ACFS-10183: Failed to get filters for realm 'string'.
ACFS-10184: Failed to get realm encryption attributes of realm 'string'.
ACFS-10185: '-e' requires both '-a' and '-k'.
Cause: At least one of the options -a or -k is missing with -e option.
Action: Specify both '-a' and '-k' with '-e' and retry.
ACFS-10186: Realm 'string' already exists on mount point 'string'.
Cause: Realm was already found on mount point.
Action: Specify another realm name and retry.
ACFS-10187: Failed to get all realms on mount point 'string'.

ACFS-10188: Attributes of realm 'string' retrieved.
Cause: Realm attributes were retrieved.
Action: None
ACFS-10189: Failed to update attributes of realm 'string'.
ACFS-10190: Updated attributes of realm 'string'.
Cause: Updated realm attributes.
Action: None
ACFS-10206: File or directory 'string' does not belong to an ACFS file system
Cause: A File or directory specified in 'acfsutil sec realm add/delete' command did
not belong to an ACFS file system.
Action: Specify only ACFS file or directory in the command 'acfsutil sec realm add/
delete'.
ACFS-10221: Rule name cannot exceed number characters.
Cause: Rule name length exceeded 255 characters.
Action: Select a rule name that is smaller than 255 characters and retry.
ACFS-10223: Invalid rule type is specified.
Cause: Invalid rule type was provided on the command line with '-t'.
Action: Provide one of the following with '-t': * - username <user_name> * application <application_name> * - time <start_time>,<end_time> * - hostname
<host_name>
ACFS-10224: Rule type 'username', 'application' or 'hostname' must have only one
rule value.
Cause: An incorrect number of arguments were provided with rule type 'username',
'application' or 'hostname'.
Action: Provide only one argument after the rule type 'username', 'application' or
'hostname'. * For example, '-t username alice' * '-t application 'c:\programs
\mozilla.exe' * '-t application '/sbin/cat' * '-t hostname myhost.domain.com'
ACFS-10225: Rule type 'time' must have both start time and end time separated by a
comma.
Cause: Either the start time or end time was not provided.
Action: Specify both start time and end time (comma separated) after rule type time. *
For example, '-t time 10:10:40,23:01:12'
ACFS-10226: '-o' requires either 'ALLOW' or 'DENY'.
Cause: A valid rule option was not provided.
Action: Specify either 'ALLOW' or 'DENY' as rule the option.
ACFS-00501 to ACFS-11111 2-167
ACFS-10227: Failed to perform rule create operation on 'string'.

ACFS-10228: Rule 'string' is created.
Cause: Rule was created.
Action: None
ACFS-10229: Rule 'string' not found.
Cause: Rule was not found.
Action: Ensure that the rule exists by executing 'acfsutil sec info -m mnt -l rule-name'.
ACFS-10230: Failed to perform rule edit operation on 'string'.
ACFS-10231: Rule 'string' updated.
Cause: Rule was updated.
Action: None
ACFS-10232: Failed to destroy rule 'string'.
Cause: Internal error
ACFS-10233: Rule 'string' destroyed.
Cause: Rule was destroyed.
Action: None
ACFS-10234: Failed to get rule 'string' information.
ACFS-10235: Rule 'string' already exists.
Cause: Rule was already found on mount point.
Action: Specify another rule name and retry.
ACFS-10236: Time format string must be HH:MM:SS.
Cause: The time format provided was not formatted as 'HH:MM: SS', where HH
translates to hours, MM to minutes and SS to seconds.
Action: Specify the time in correct format and retry.
ACFS-10237: Rule type 'string' specified does not match the actual type 'string' of
rule 'string'
Cause: The rule type specified did not match the actual rule typed.
Action: Specify the actual rule type to update the rule value and retry.
ACFS-10238: Failed to get all rules on mount point 'string'.

ACFS-10239: Failed to get information for rule 'string'.
ACFS-10240: Cannot destroy rule 'string'. The rule is in use by one or more rule
sets.
Cause: The rule was being used in one or more rule set(s) in the file system.
Action: Remove the rule from the rule set(s) and retry.
ACFS-10241: Rule set name cannot exceed number characters.
Cause: Rule set name length exceeded 255 characters.
Action: Select a shorter rule set name and retry.
ACFS-10242: '-o' requires either ALL_TRUE or ANY_TRUE.
Cause: The rule set option was not set to either ALL_TRUE or ANY_TRUE.
Action: Specify either ALL_TRUE or ANY_TRUE with the rule set option '-o'.
ACFS-10243: Failed to create rule set 'string' on mount point 'string'.
ACFS-10244: Rule set 'string' is created.
Cause: Rule set was created.
Action: None
ACFS-10245: Rule set 'string' not found on mount point 'string'.
Cause: Rule set was not found on mount point.
Action: None
ACFS-10246: Failed to add rule 'string' to the rule set 'string'.
ACFS-10247: Added rule 'string' to the rule set 'string'.
Cause: Rule was added to the rule set.
Action: None
ACFS-10248: Failed to delete rule 'string' from the rule set 'string'.
ACFS-00501 to ACFS-11111 2-169
ACFS-10249: Deleted rule 'string' from rule set 'string'.

Cause: Rule was deleted from the rule set.
Action: None
ACFS-10250: Failed to destroy rule set 'string' on mount point 'string'.
ACFS-10251: Rule set 'string' destroyed.
Cause: Rule set was destroyed.
Action: None
ACFS-10252: Failed to get rules for rule set 'string'.
ACFS-10253: Failed to get list of command rules.
ACFS-10254: Rule set 'string' already exists.
Cause: Rule set was already found on mount point.
Action: Specify another rule set name and retry.
ACFS-10255: Rule 'string' already exists in rule set 'string'.
Cause: Rule was already part of rule set.
Action: None
ACFS-10256: Rule 'string' is not found in rule set 'string'.
Cause: Rule was not found in the rule set.
Action: Ensure that the realm exists using the command 'acfsutil sec info -m -s rulesetname'.
ACFS-10257: Failed to get all rule sets on mount point 'string'.
ACFS-10258: Failed to get information for rule set 'string'.
ACFS-10259: Invalid command rule 'string'.
Cause: Invalid command rule was specified.
Action: Execute 'acfsutil sec info -m <mount_point> -c' to get all the valid command
rules. * Re-execute the command with valid command rule.
ACFS-10260: File object 'string' and the realm 'string' should be in the same file
system.
Cause: File object was not in the same file system as that of the realm.
Action: Specify file objects from the same file system as that of the realm.
ACFS-10261: Cannot destroy rule set 'string'. The rule set is in use by one or more
realms.
Cause: The rule set is being used in filter(s) that are part of one or more realms in the
file system.
Action: Remove the filter(s) from the realms that are using this rule set and retry.
ACFS-10262: Application path name for rule type 'application' cannot exceed
'number' characters.
Cause: Application path name for rule type 'application' exceeded 511 characters
Action: Select a shorter application path name for rule type 'application' and retry.
ACFS-10263: Host name for rule type 'hostname' cannot exceed 'number' characters.
Cause: Host name for rule type 'hostname' exceeded 255 characters.
Action: Select a shorter host name for rule type 'hostname' and retry.
ACFS-10264: Invalid value for rule type 'string' as the given path name 'string' is a
symbolic link
Cause: Path name provided for rule type 'application' was a symbolic link. Symbolic
links are not supported for rule type 'application'.
Action: Specify a path name which is not a symbolic link and re-execute the
command.
ACFS-10271: Encryption algorithm can be only 'AES'.
Cause: The encryption algorithm provided was not 'AES'.
Action: Specify 'AES' as the algorithm with '-a' and retry.
ACFS-10272: Key length must be either 128, 192, or 256.
Cause: The key length specified with '-k' was not 128, 192 or 256.
Action: Specify either 128, 192, or 256 with '-k' and retry.
ACFS-10273: Failed to set the encryption parameter on realm 'string'.
ACFS-10274: Failed to update rule set option.
ACFS-10275: Failed to get rule sets for mount point 'string'.
ACFS-00501 to ACFS-11111 2-171
ACFS-10276: Rule set 'string' option updated to 'string'.

Cause: Rule set option updated.
Action: None
ACFS-10277: '-e' requires either ON or OFF.
Cause: The realm encryption status specified with '-e' was not 'on' or 'off'
Action: Specify either 'on' or 'off' with -e and retry.
ACFS-10278: Encryption parameters are not set on the file system, realm encryption
is unavailable.
Cause: The encryption parameters were not set on the file system.
Action: A system administrator must execute an 'encr set' command
ACFS-10284: Failed to get security information for 'string'.
ACFS-10285: Pathname 'string' does not exist.
Cause: Specified pathname was not found.
Action: Specify a valid pathname.
ACFS-10286: User 'string' does not exist.
Cause: User was not found.
Action: Specify a valid user.
ACFS-10287: Group 'string' does not exist.
Cause: Group was not found
Action: Specify a valid group.
ACFS-10288: User 'string' already added to the realm 'string'.
Cause: User was already added to the realm.
Action: None
ACFS-10289: Group 'string' already added to the realm 'string'.
Cause: Group was already added to the realm
Action: None
ACFS-10290: Realm filter 'string' already added to the realm 'string'.
Cause: Filter was already added to the realm.
Action: None
ACFS-10291: Pathname 'string' already added to the realm 'string'.
Cause: Pathname was already added to the realm.
Action: None
ACFS-10292: User 'string' is not part of the realm 'string'.
Cause: User was not part of the realm.
Action: None
ACFS-10293: Group 'string' is not part of the realm 'string'.

Cause: Group was not part of the realm.
Action: None
ACFS-10294: Pathname 'string' is not part of the realm 'string'.
Cause: Pathname was not part of the realm.
Action: None
ACFS-10295: Realm filter 'string' is not part of the realm 'string'.
Cause: Filter was not part of the realm.
Action: None
ACFS-10296: Realm filter 'string:string' could not be added to the realm 'string'.
Cause: The filter was not added because the filter with command rule 'ALL' was
already part of the realm.
Action: Either add the command rules individually or add 'ALL' if all of the
command rules are desired. Individual command rules cannot be added when 'ALL'
is already present.
ACFS-10297: Realm filter 'ALL' could not be added since another filter exists in
realm 'string'.
Cause: Filter 'ALL' was not added because another filter existed in the realm .
command rules are desired. 'ALL' command rule cannot be added when individual
command rules are already present.
ACFS-10298: User name cannot exceed number characters.
Cause: User name length exceeded 64 characters.
Action: Select a shorter user name and retry.
ACFS-10299: Group name cannot exceed number characters.
Cause: Group name length exceeded 64 characters.
Action: Select a shorter group name and retry.
ACFS-10322: System realm 'SYSTEM_SecurityMetadata' created.
Cause: System realm 'SYSTEM_SecurityMetadata' was created.
Action: None
ACFS-10323: System realm 'SYSTEM_Logs' created.
Cause: System realm 'SYSTEM_Logs' was created.
Action: None
ACFS-10324: Rulesets cannot be cloned before cloning rules on mount point
'string'.
Cause: Rule sets were not cloned because some rules were not present on mount
point.
Action: Clone rules first using command 'acfsutil sec rule clone' and then clone rule
sets.
ACFS-10342: System realm 'SYSTEM_BackupOperators' created.
Cause: System realm 'SYSTEM_BackupOperators' was created.
ACFS-00501 to ACFS-11111 2-173
Action: None
ACFS-10350: Incorrect password was entered in all attempts to open the encryption
key store. Encrypted files will not be available.
Cause: Incorrect password was entered in all attempts to open the encryption key
store during the mount command.
Action: Unmount the file system and remount it, providing the correct password.
Encrypted files will not be available until the file system is unmounted and
remounted with the correct password.
ACFS-10355: System realm 'SYSTEM_Antivirus' created.
Cause: System realm 'SYSTEM_Antivirus' was created.
Action: None
ACFS-10356: waiting for the operation to complete...
Action: None
ACFS-10357: System realm 'SYSTEM_Audit' created.
Action: None
ACFS-10400: Encryption is set on mount point 'string'.
Cause: Encryption was set on mount point.
Action: None
ACFS-10401: Failed to set encryption parameters on mount point 'string'.
Action: Refer to encryption log in '<mount_point>/.Security/encryption/logs/encr<host_name>.log'.
ACFS-10402: Encryption turned 'string' on 'string'.
Cause: Encryption was turned either ON or OFF on the pathname.
Action: None
ACFS-10403: Failed to turn encryption 'string' on 'string'.
ACFS-10405: Failed to get encryption information on 'string'.
ACFS-10406: Re-key operation is complete on 'string'.
Cause: Re-key operation was complete on the pathname.
Action: None
ACFS-10407: Failed to perform re-key operation on 'string'.

ACFS-10410: encryption is already disabled on the file system
Cause: Encryption was already disabled on the file system.
Action: None, encryption is already disabled.
ACFS-10411: encryption is already enabled on the file system
Cause: Encryption was already enabled on the file system.
Action: None, encryption is already enabled.
ACFS-10412: Encryption parameters were not provided, using default algorithm
(string) and key length (number).
Cause: Encryption parameters were not provided.
Action: None, default values have been used.
version 11.2.0.2.0 to allow the acfsutil encryption and security commands.
or beyond.
ACFS-10414: Encryption has been initialized for the cluster.
Cause: An administrator initialized encryption for the cluster.
Action: None
ACFS-10415: File system level encryption is on, file level encryption operations are
not allowed
Cause: A file level encryption operation was attempted while file system level
encryption was enabled. File level encryption operations are not allowed when file
system level encryption is turned on.
Action: None
ACFS-10416: File is realm secured\n
Cause: An encryption operation was attempted on a realm secured file and no action
was performed. A realm secured file can only be encrypted and decrypted by
changing the encryption parameters of containing realm(s) or by deleting the file from
all realms.
Action: If changing the encryption status of this file is required, contact a Security
Administrator to modify the encryption parameters of the containing realm(s).
ACFS-10419: Skipping directory 'string' because it does not belong to the file
system mounted on 'string'
Cause: The directory does not belong to the specified mounted ACFS file system.
Action: None
ACFS-10420: Encryption parameters specified for realm 'string' match existing
settings.
Cause: An attempt to set encryption parameters for a realm specified values the same
as those already set.
Action: None
ACFS-00501 to ACFS-11111 2-175
version 'string' to allow acfsutil encryption commands.
Cause: An adminstrator attempted an encryption set or volume level rekey operation,
but the ADVM compatibility attribute had not been upgraded to a supported version.
version 'string' to allow 'acfsutil sec' commands.
Cause: A security adminstrator attempted an ACFS Security operation, but the
ADVM compatibility attribute had not been upgraded to a supported version.
COMPATIBLE.ADVM attribute and retry the operation.
ACFS-10423: This encryption operation is not allowed on a standby file system.
Cause: An encryption operation that is not allowed on a standby file system was
attempted. The following acfsutil encryption commands are not allowed on a standby
file system: 'encr set', 'encr on', 'encr off', and 'encr rekey'.
Action: None
ACFS-10424: This ACFS Security operation is not allowed on a standby file system.
Cause: An ACFS Security operation that is not allowed on a standby file system was
attempted. The following acfsutil security commands are not allowed on a standby
file system: 'sec prepare', 'sec save/load/enable/disable', 'sec realm create/destroy/
clone/add/delete', 'sec rule create/destroy/clone/edit', and 'sec ruleset create/
destroy/clone/edit'
Action: None
ACFS-10450: Unauthorized encryption operation attempted on 'string'.
Cause: A user attempted an encryption operation on the given file and the operation
was denied.
Action: None
ACFS-10451: File level encryption operation attempted on realm secured file
'string'.
Cause: A user attempted to perform a file level encryption command on a realm
secured file and the operation was denied.
Action: None
ACFS-10452: Failed to decrypt 'string'.
ACFS-10453: Unable to get encryption parameters for the file system mounted on
'string'.
ACFS-10454: File system level encryption turned on for mount point 'string'.
Cause: A system administrator enabled file system level encryption.
Action: None
ACFS-10455: New volume encryption key generated for mount point 'string'.
Cause: A system administrator updated the volume encryption key for the mount
point. The file encryption keys for all encrypted files on the file system were reencrypted using the new volume encryption key.
Action: None
ACFS-10456: New file encryption key generated for file 'string'.
Cause: A system administrator updated the volume encryption key for the file. The
data in the file was re-encrypted using the new key.
Action: None
ACFS-10457: New file encryption keys generated for all files in directory 'string'.
Cause: A system administrator updated the volume encryption key for the files in the
given directory. The file contents were re-encrypted using the new key.
Action: None
ACFS-10458: Encryption turned off for path 'string'.
Cause: A user successfully decrypted a file or directory.
Action: None
ACFS-10459: Encryption turned off for directory 'string' and its contents.
Cause: A user successfully decrypted a directory and its contents.
Action: None
ACFS-10460: File system level encryption turned off for mount point 'string'.
Cause: A system administrator disabled file system level encryption.
Action: None
ACFS-10461: Encryption turned on for path 'string'.
Cause: A user successfully encrypted a file or directory.
Action: None
ACFS-10462: Encryption turned on for directory 'string' and its contents.
Cause: A user successfully encrypted a directory and its contents.
Action: None
ACFS-10463: Skipping file 'string' because it does not belong to the file system
mounted on 'string'
Cause: The file does not belong to the specified mounted ACFS file system.
Action: None
ACFS-10464: ACFS Encryption operations are not allowed on files of this type.
Cause: An attempt was made to encrypt, decrypt, or rekey a file of one of the
following Oracle file types: data, control, online redo log, archive log, backup,
incremental backup, or flashback.
Action: None
ACFS-10500: Pathname cannot exceed number characters.
Cause: Pathname length exceeds 255 characters.
Action: Select a name that is smaller than %d characters and retry.
ACFS-00501 to ACFS-11111 2-177
ACFS-10550: Security wallet created.

Cause: Security wallet was created.
Action: None
ACFS-10551: Security wallet creation failed.
ACFS-10564: Incorrect password for encryption key store.
Cause: An incorrect password was entered while opening the encryption key store.
Action: Retry the command and enter the correct password.
ACFS-10565: Encryption key store created.
Cause: Encryption key store was created.
Action: None
ACFS-10566: Encryption key store creation failed.
ACFS-10573: Encryption key store not found.
Cause: Encryption key store did not exist.
Action: Run 'acfsutil encr init' command and retry.
ACFS-10574: ACFS encryption already initialized, cannot reinitialize.
Cause: 'acfsutil encr init'can has already been executed and the encryption key store
already existed.
Action: None
ACFS-10575: Incorrect encryption key store.
Cause: The encryption key store may have been deleted and re-created.
Action: Recover the correct key store from a backup and retry.
ACFS-10576: Incorrect encryption key, new volume encryption key not created.
ACFS-10577: Encryption parameters not set.
Cause: A command that requires encryption parameters to be set first was run before
encryption parameters were set on the file system.
Action: Run 'acfsutil encr set' and retry.
ACFS-10578: Unable to communicate new encryption settings to cluster members.
ACFS-10579: Key store is not valid for encryption.
Cause: The encryption key store was either not created using 'acfsutil encr init' or it
was corrupted.
Action: Restore the encryption key store from a backup and retry.
ACFS-10586: Internal error.
Cause: Internal error occurred.
Action: Contact Oracle support service.
ACFS-10588: Internal error : WLT number.
ACFS-10589: Internal error : BSF number.
ACFS-10590: Internal error : XML number.
ACFS-10591: Internal error : TSP number.
ACFS-10592: Internal error : IOC number.
ACFS-10593: Internal error : UGP number.
ACFS-10594: Internal error : OCR number : string.
ACFS-10596: Unable to get the hostname for the current node.
Cause: The current user does not have access to the requested information.
ACFS-10597: The user 'string' and the group 'string' do not belong to the same
domain.
Cause: The user and the group were not part of the same domain.
Action: Use 'net user' command to verify and retry with user and group that belong to
the same domain.
ACFS-10598: Unable to retrieve domain name information for 'string'.
Cause: Unable to retrieve domain name information.
Action: Make sure the node is part of proper domain.
ACFS-10599: Current user does not have system administrative privileges to
initialize ACFS security.
Cause: The user was not part of system administrators group.
ACFS-00501 to ACFS-11111 2-179
Action: Run 'acfsutil sec init' with administrative privileges.

ACFS-10600: Failed to store first security administrator 'string' in wallet.
ACFS-10601: Failed to update first security administrator 'string' information.
ACFS-10602: Passwords do not match.
Cause: Verification of the password did not succeed.
Action: Re-execute and provide the same password on both the prompts.
ACFS-10603: Security administrator group already set in wallet.
Cause: Security administrator group was already set in wallet.
Action: None
ACFS-10604: Security administrator group not set in wallet.
Action: Contact Oracle Support Service.
ACFS-10606: User 'string' is not a security administrator.
Cause: User was not a security administrator.
Action: Only a security administrator has privilege to execute the security commands.
Add the user to security administrator list by executing 'acfsutil sec admin add' and
retry.
ACFS-10607: User 'string' is not member of security administrator group.
Cause: User was not a member of security administrator's group.
Action: Add the user to the security administrator's group.
ACFS-10609: Administrator update in driver failed.
ACFS-10610: Failed to get current user information.
ACFS-10611: Failed to assign user 'string' as security administrator.
ACFS-10612: Failed to remove user 'string' from security administrator(s) list.

ACFS-10613: Failed to change ACFS Security administrator password for current
user.
ACFS-10614: Security administrator 'string' already added.
Cause: User was already a security administrator.
Action: None
ACFS-10615: User 'string' is not a security administrator.
Action: None
ACFS-10616: Incorrect ACFS Security administrator password.
Cause: The password supplied was incorrect.
Action: Re-execute and provide the correct ACFS Security administrator password for
the current user.
ACFS-10617: Password cannot exceed number characters.
Cause: The password entered exceeded the maximum allowed characters.
Action: Enter the password within the specified number of characters.
ACFS-10618: Security administrator 'string' could not be added.
Cause: Security administrator was not added.
ACFS-10619: Security administrator 'string' added.
Cause: Security administrator was added.
Action: None
ACFS-10620: Security administrator 'string' could not be removed.
Cause: Security administrator was not removed.
ACFS-10621: Removal of the last security administrator 'string' is not allowed.
Cause: The security administrator was not removed being the only security
administrator in this system.
Action: Add another security administrator to remove the intended security
administrator.
ACFS-10622: Security administrator 'string' removed.
Cause: Security administrator was removed.
Action: None
ACFS-10623: ACFS security already initialized, cannot reinitialize.
Cause: ACFS security was already initialized and could not be reinitialized.
ACFS-00501 to ACFS-11111 2-181
Action: None
ACFS-10624: User 'string' is not member of the group 'string'.
Cause: The user was not member of the group.
Action: Add the user to the group and retry.
ACFS-10625: Failed to prepare file system for security operations on mount point
'string'.
ACFS-10626: Mount point 'string' is already prepared for security.
Cause: Mount point was already prepared for security. Prepare should be executed
only once for an ACFS formatted file system that is mounted.
Action: None
ACFS-10627: Mount point 'string' is now prepared for security operations.
Cause: " Mount point was prepared for security operations.
Action: None
ACFS-10629: Failed to enable security on mount point 'string'.
ACFS-10630: Security is already enabled on mount point 'string'.
Cause: Security was already enabled on mount point.
Action: None
ACFS-10631: Security is now enabled on mount point 'string'.
Cause: Security was enabled on mount point.
Action: None
ACFS-10632: Security is already disabled on mount point 'string'.
Cause: Security was already disabled on mount point.
Action: None
ACFS-10633: Security is now disabled on mount point 'string'.
Cause: Security was disabled on mount point.
Action: None
ACFS-10634: Failed to disable security on mount point 'string'.
ACFS-10635: Failed to get security administrator group.
ACFS-10636: Security administrator group retrieved.

Cause: Security administrators group was retrieved.
Action: None
ACFS-10637: File system is not prepared for ACFS security on mount point 'string'.
Cause: File system was not prepared for security operations on mount point.
Action: Execute 'acfsutil sec prepare' to prepare security operation on mount point.
ACFS-10638: Backup and log directories created.
Cause: Backup and log directories were created.
Action: None
ACFS-10639: Failed to create directory 'string' on mount point 'string'.
ACFS-10640: Failed to create log directory on mount point 'string'.
ACFS-10641: Failed to create backup directory on mount point 'string'.
ACFS-10643: Security is already enabled on realm 'string'.
Cause: Security was already enabled on realm.
Action: None
ACFS-10644: Security is already disabled on realm 'string'.
Cause: Security was already disabled on realm.
Action: None
ACFS-10645: Failed to set owner of file 'string' to 'string'.
Cause: Current user is not owner of the file.
Action: Login as the file owner and re-run the command.
ACFS-10646: Failed to create secbackup.xml file on mount point 'string'.
initialize ACFS encryption.
Action: Run 'acfsutil encr init' with administrative privileges.
ACFS-00501 to ACFS-11111 2-183
ACFS-10648: ACFS security already initialized, recovery failed.

Cause: Previous execution of 'acfsutil sec init' had failed. Recovery actions also failed
in the subsequent execution of 'acfsutil sec init'.
Action: Contact Oracle support services.
ACFS-10649: ACFS encryption already initialized, recovery failed.
Cause: Previous execution of 'acfsutil encr init' had failed. Recovery actions also failed
in the subsequent execution of 'acfsutil encr init'.
ACFS-10650: Invalid file name 'string' for ACFS security metadata.
Cause: The file was invalid for saving or loading ACFS security metadata.
Action: Specify a valid file.
ACFS-10651: Failed to save ACFS security metadata of mount point 'string'.
ACFS-10652: Saved ACFS security metadata of mount point 'string'.
Cause: ACFS security metadata of mount point '%s' was saved.
Action: None
ACFS-10653: Failed to save ACFS security string metadata of mount point 'string'.
ACFS-10654: Directory '.Security' does not exist on mount point 'string'.
Cause: Mount point was not prepared for ACFS security.
Action: Execute 'acfsutil sec prepare' on the mount point.
ACFS-10655: Failed to get hostname.
ACFS-10656: Failed to get timestamp.
ACFS-10657: Absolute and relative pathnames are not allowed with '-p' option.
Cause: Filename was provided with absolute or relative path.
Action: Specify only name of the file with '-p' option and retry.
ACFS-10658: ACFS Security has been initialized on the cluster with user 'string' as
the initial Security Administrator and 'string' as the Security Administrator group.
Cause: An administrator initialized ACFS Security on the cluster.
Action: None
ACFS-10659: Cannot destroy realm 'string' because it is a system-created realm.

Cause: A request to destroy a system-created realm was denied because that
operation is not allowed.
Action: None
ACFS-10660: Current user does not have required OS privileges to set ACFS
encryption parameters.
Cause: Current user does not have root or administrator privileges to run 'acfsutil
encr set'.
Action: Run 'acfsutil encr set' as a user who has root or administrator privileges.
ACFS-10661: Current user does not have required OS privileges to rekey the ACFS
encr rekey'.
Action: Run 'acfsutil encr rekey' as a user who has root or administrator privileges.
ACFS-10662: Current user 'string' does not have security administrator privileges.
Cause: A command requiring Security Administrator privileges was issued but the
user is not in the Security Administrators group.
Action: Add current user to the Security Administrators group or log on as a user
who has the required privileges, then retry the command.
ACFS-10663: User name 'string' is not a fully qualified name.
Cause: Fully qualified name was not specified. The supplied user name was not
prefixed with a Windows Server Domain name.
Action: Specify a domain user name prefixed with Windows Server Domain name.
For example, HOSPITAL-ADMIN\Alice where HOSPITAL-ADMIN is a Windows
Server Domain name and Alice is the user name.
ACFS-10664: Group name 'string' is not a fully qualified name.
Cause: Fully qualified name was not specified.The supplied group name was not
Action: Specify domain group name prefixed with Windows Server Domain name.
For example: HOSPITAL-ADMIN\Doctors where HOSPITAL-ADMIN is a Windows
Server Domain name and Doctors is the group name.
ACFS-10665: Group 'string' is a local group and not a Windows Server Domain
group.
Cause: Specified group was not a Windows Server Domain group.
Action: Specify a domain group name prefixed with Windows Server Domain name.
For example, HOSPITAL-ADMIN\Doctors, where HOSPITAL-ADMIN is a Windows
ACFS-10666: User 'string' is a local user and not a Windows Server Domain user.
Cause: Specified user was not a Windows Server Domain user.
ACFS-00501 to ACFS-11111 2-185
ACFS-10667: Windows Server Domain 'string' does not exist.

Cause: Failed to get Windows Server Domain controller for the domain either because
of not access to domain or domain does not exist.
Action: Specify the name of an existing Windows Server Domain.
ACFS-10675: Failed to load ACFS security metadata on mount point 'string'.
ACFS-10676: Loaded ACFS security metadata on mount point 'string'.
Cause: ACFS security metadata was loaded on mount point.
Action: None
ACFS-10677: Failed to load string on mount point 'string'.
ACFS-10679: Unable to resolve the user id 'string'.
Cause: The user was not found on the system.
Action: None
ACFS-10680: XDK version not compatible.
Cause: Oracle XDK version was incompatible.
Action: Install the correct Oracle XDK version and retry.
ACFS-10681: ACFS kernel version is not compatible. The kernel version on the
system is 'string' while the expected kernel version is 'string' or above.
Cause: ACFS kernel version was incompatible.
Action: Install the correct version and retry.
ACFS-10682: Kernel major version is not compatible.
Cause: Kernel major version was incompatible.
ACFS-10683: Kernel release version is not compatible.
Cause: Kernel release version was incompatible.
ACFS-10684: Kernel update version is not compatible.
Cause: Kernel update version was incompatible.
ACFS-10685: Kernel port update version is not compatible.
Cause: Kernel port version was incompatible.
ACFS-10686: Kernel patch version is not compatible.
Cause: Kernel patch version was incompatible.
ACFS-10687: Kernel one off version is not compatible.

Cause: Kernel one off version was incompatible.
ACFS-10688: Unable to resolve the group id 'string'.
Cause: The OS group ID could not be resolved to a name. Usually this occurs because
the OS group has been removed.
Action: None
ACFS-10689: Failed to update security administrators information in the driver,
some of the subsequent commands may fail.
Cause: Updating driver security administrator data failed during mount. The mount
completes, but subsequent security commands may be affected. This is an internal
error.
ACFS-10690: Cannot edit groups in realm 'string'.
Cause: No changes were made to the groups in the realm as the operation is not
allowed.
Action: None
ACFS-10691: Changed ACFS Security administrator password for current user.
Action: None
ACFS-10700: Failed to store volume encryption key.
ACFS-10701: Failed to get volume encryption key.
ACFS-10702: Snapshots exist for the file system mounted on 'string'. New
encryption parameters will not apply to files in these snapshots.
Cause: One or more snapshots existed for the file system when this encryption
operation was done. The new encryption parameters set by this command will apply
only to new files created in the file system and not to existing files in any snapshots.
Note that none of the encryption commands affect files in any snapshots. Any
snapshots created after the command was run will use the new encryption
parameters.
Action: None
ACFS-10703: Snapshots exist for the file system mounted on 'string'. Encryption
status of files in these snapshots will not change.
operation was done. The operation did not modify file data in any snapshots on the
file system, so this data may still be available on disk unencrypted. Note that none of
the encryption commands affect files in any snapshots.
ACFS-00501 to ACFS-11111 2-187
Action: If you plan to use snapshots and encryption together, it is recommended that
any snapshots be created after encrypting data on the file system. If the data on the
file system was encrypted when some snapshots already existed, you may delete
existing snapshots to ensure that data is not available in unencrypted form via any
files in these snapshots.
ACFS-10704: Snapshots exist for the file system mounted on 'string'. Encryption
keys of files in these snapshots will not be rekeyed.
operation was done. The operation did not rekey FEKs of files in any snapshots of the
file system, so the FEKs of these files will continue to remain encrypted with the old
parameters. Note that none of the encryption commands affect files in any snapshots.
Action: To ensure that all FEKs, including those of files in any snapshots, are
encrypted with the new encryption parameters, this command should be run when
the file system has no snapshots. If the command was run when some snapshots
existed you may delete these snapshots. Any snapshots created after the command
was run will use the new encryption parameters.
ACFS-10705: Cannot perform encryption operation because volume encryption
keys for the file system mounted at 'string' are not available.
Cause: The encryption operation failed because the required volume encryption keys
for the file system were not available to the ACFS file system driver. This could
happen because an incorrect key store password was supplied during mount or
because of some other error during mount.
Action: Remount the file system, providing the correct password during the mount
operation if required. Address any other errors reported during mount. If the issue
persists, contact Oracle Support Services.
ACFS-10706: Cannot perform encryption operation because an encryption undo
operation is in progress.
Cause: The encryption operation failed because the system administrator was running
encryption undo ('acfsutil encr set -u') on the file system. It is also possible that a
previous encryption undo operation had not completed cleanly.
Action: There is no action to be taken by users who are not system administrators. If
this message is seen by a system administrator and an encryption undo operation is
not in progress, then a previous encryption operation did not complete properly. Run
the 'acfsutil encr set -u' command again to complete the operation.
ACFS-10707: Cannot perform encryption undo operation because file system level
encryption is on.
Cause: The encryption undo operation failed because file system level encryption was
on.
Action: Turn file system level encryption off and retry the operation.
ACFS-10708: An earlier key store migrate operation did not complete. Provide the
same password as the one used in the previous attempt.
Cause: An earlier run of 'acfsutil keystore migrate' command did not complete.
Action: When prompted for a password (ACFS-10349), provide the same password as
the one used in the previous attempt.
ACFS-10709: Existing ACFS encryption key store is already password-protected.
Action: None
ACFS-10710: Existing ACFS encryption key store is already not passwordprotected.

Action: None
ACFS-10711: Recovery of ACFS encryption key store completed successfully.
Action: None
ACFS-10712: ACFS encryption key store migration to password-protected key store
completed successfully.
Action: None
ACFS-10713: ACFS encryption key store migration to password-free key store
Action: None
ACFS-10714: The environment variable OKV_HOME is not set.
Cause: The attempt to access the Oracle key vault server to obtain the volume
encryption keys failed because the OKV_HOME environment variable was not set.
Action: Set the environment variable OKV_HOME and retry the command.
ACFS-10715: failed to find the PKCS library in path 'string'
encryption keys failed because the PKCS library was not found in '$OKV_HOME/lib'.
Action: Ensure that the OKV_HOME environment variable is set to point to the path
that contains OKV client data, including the PKCS library. If not, set OKV_HOME
and retry the command. If the problem persists, contact Oracle Support Services.
ACFS-10716: failed to load the PKCS library
encryption keys failed because the OKV PKCS library could not be loaded from
'$OKV_HOME/lib'.
ACFS-10717: failed to find Oracle Key Vault (OKV) client configuration file
encryption keys failed because the OKV client configuration file, okvclient.ora, was
not found in '$OKV_HOME/conf'.
that contains OKV client data, including the OKV client configuration file,
okvclient.ora. If not, set OKV_HOME and retry the command. If the problem persists,
ACFS-10718: failed to login to OKV server
Cause: A login attempt to Oracle Key Vault (OKV) server failed.
ACFS-00501 to ACFS-11111 2-189
Action: Ensure that correct password is provided, verify okvclient.ora file entries for
servers, verify both the servers are still running, and then retry. If the problem
ACFS-10719: failed to store encryption keys in file system wallet
ACFS-10720: Key store must be either SSO, PKCS, or OKV.
Cause: An attempt to store an encryption key was rejected because the specified key
store was not one of: SSO, PKCS or OKV.
Action: Retry the command specifying either SSO, PKCS, or OKV as the key store.
ACFS-10721: failed to save encryption keys, file system wallet already exists in
directory 'string'
Cause: An attempt to create a new wallet and save encryption keys in it failed because
the wallet already existed in the said location.
Action: Delete or move the wallet and retry the command.
ACFS-10725: Failed to start encryption logging on mount point 'string'.
ACFS-10726: Failed to start security logging on mount point 'string'.
ACFS-10727: Failed to start global security and encryption logging.
Cause: Global security and encryption logging services could not be started. The log
file for this node will not be updated.
Action: n/a
ACFS-10728: ACFS encryption logging directory not found on mount point 'string'.
Cause: The ACFS encryption logging directory '<mount_point>/.Security/
encryption/logs/' could not be opened.
Action: Ensure the logging directory exists and the system administrator can open
and create files in this directory, then unmount the file system and remount it
manually to restore logging functionality.
ACFS-10729: ACFS security logging directory not found on mount point 'string'.
Cause: The ACFS security logging directory '<mount_point>/.Security/realm/logs/'
could not be opened.
Action: Ensure the logging directory exists and the security administrator can open
ACFS-10730: ACFS security and encryption logging directory not found in
CRS_HOME.
Cause: The ACFS security and encryption logging directory '<CRS_HOME>/log/
<host_name>/acfssec' could not be opened.
and create files in this directory.
ACFS-10731: Could not get local host name, ACFS encryption logging will not be
available on mount point 'string'.
Cause: The local host name could not be determined, ACFS encryption logs for this
host in '<mount_point>/.Security/encryption/logs/' will not be written.
Action: Ensure the operating system host name is set correctly and the system
administrator can read this value, then unmount the file system and remount it
ACFS-10732: Could not get local host name, ACFS security logging will not be
Cause: The local host name could not be determined, ACFS security logs for this host
in '<mount_point>/.Security/realm/logs/' will not be written.
Action: Ensure the operating system host name is set correctly and the security
ACFS-10733: Could not get local host name, ACFS security and encryption logging
will not be available for this host
Cause: The local host name could not be determined, ACFS security and encryption
logs for this host in '<CRS_HOME>/log/<host_name>/acfssec' will not be written.
administrator can read this value.
ACFS-10751: Realm_Metadata file has invalid realm record\nfor file:\nstring
Cause: A realm record of the indicated Realm_Metadata file was invalid.
ACFS-10753: Realm_Metadata file has no valid realm records\nfor file:\nstring
Cause: The indicated Realm_Metadata file did not contain any valid valid realm
records.
ACFS-10755: Realm_Metadata file contains invalid realm record data\nfor file:
\nstring
Cause: The indicated Realm_Metadata file contained at least one invalid realm record.
ACFS-10756: Realm_Metadata file _Private structure is invalid for:\nfor file:
\nstring
Cause: The _Private structure of the indicated Realm_Metadata file was invalid. Refer
ACFS-00501 to ACFS-11111 2-191
ACFS-10757: Realm_Metadata file has invalid Hash_Table data\nfor file:\nstring

Cause: The Hash_Table of the indicated Realm_Metadata file contained inconsistent
ACFS-10760: Realm_Metadata file _Private structure has invalid _maxFree value\n
found: number minimum: number\nfor structure:\nstring
incorrect.
ACFS-10761: Realm_Metadata file _Private structure has invalid _freeDataListTail
value\n found: number minimum: number\nfor structure:\nstring
was incorrect.
ACFS-10762: Realm_Metadata file node not on _freeDataList\nfor file:\nstring
Cause: One or more of the _security_data nodes of the indicated Realm_Metadata file
was not found on the free data node list. The _next property for one or more of the
ACFS-10764: Realm_Metadata file has invalid _security_record for _Administrator
default\nfor file:\nstring
ACFS-10766: Realm_Metadata file has no valid realm data records\nfor file:
\nstring
Cause: The indicated Realm_Metadata file did not contain any valid valid realm data
records.
ACFS-10768: Number of realms created on mount point 'string' has reached the
limit number.
Cause: A request to create a realm was denied because the number of realms created
on the mount point has reached the limit.
Action: Destroy any of the unused realms and retry the command.
ACFS-10769: Number of rulesets created on mount point 'string' has reached the
limit number.
Cause: A request to create a ruleset was denied because the number of rulesets
created on the mount point has reached the limit.
Action: Destroy any of the unused rulesets and retry the command.
ACFS-10770: Number of rules created on mount point 'string' has reached the limit
number.
Cause: A request to create a rule was denied because the number of rules created on
the mount point has reached the limit.
Action: Destroy any of the unused rules and retry the command.
ACFS-10771: Number of realms that file 'string' is part of has reached the limit
number.
Cause: A request to add the file to a realm was denied because the number of realms
that the file is part of has reached the limit.
Action: Remove the file from one or more realms and retry the command.
ACFS-10772: Security at the realm level will not be in effect until file system-level
security is enabled.
Cause: Security is disabled at the file system level. When file system-level security is
disabled, enabling realm-level security does not enable the authorization checks
provided by the realm.
Action: Enable Security at file system level.
ACFS-10773: Unable to lock ACFS Security wallet.
Cause: The ACFS Security wallet lock was not acquired.
Action: Verify that Cluster Ready Services(CRS) stack is up by executing 'crsctl check
crs' and Cluster Synchronization Services(CSS) is running by executing 'crsctl check
css'. If the CRS stack is not up, check with the CRS administrator to bring it up. If it
does not resolve the problem contact Oracle Support Services.
ACFS-10774: Unable to unlock ACFS Security wallet.
Cause: The ACFS Security wallet lock was not released.
ACFS-10775: Cannot proceed as another instance of 'acfsutil' command is updating
the security administrator information.
Cause: ACFS Security wallet is locked by another instance of 'acfsutil' command.
ACFS-10776: Invalid 'acfsutil' version 'string'
ACFS-10777: Unable to lock ACFS encryption key store.
Cause: The ACFS encryption key store lock could not be acquired.
ACFS-00501 to ACFS-11111 2-193
ACFS-10778: Unable to unlock ACFS encryption key store.
Cause: The ACFS encryption key store lock was not released.
ACFS-10779: Cannot proceed as another instance of 'acfsutil' command is updating
the encryption key store.
Cause: An acfsutil encryption request found the ACFS encryption key store locked by
another instance of the acfsutil command.
ACFS-10780: The file system mounted on 'string' has been prepared for ACFS
Security, undo ACFS Security first.
Cause: ACFS Encryption cannot be undone when the file system has been prepared
for ACFS Security.
Action: Undo ACFS Security prepare on the mount point by executing 'acfsutil sec
prepare -m <mount_point> -u' as security administrator and retry.
ACFS-10781: existing snapshots preclude undoing ACFS security or encryption for
the file system mounted on 'string'
Cause: An attempt to undo ACFS security or encryption for the indicated file system
failed because there were existing snapshots for the file system. ACFS security and
encryption can only be undone for a file system with no snapshots. This message may
be displayed before or after all files have been decrypted by the 'acfsutil encr set -u'
command. In both cases, the file system retains its encryption 'prepared' state and
files can be encrypted without running 'acfsutil encr set' again.
Action: Remove all snapshots by executing 'acfsutil snap delete' and retry.
ACFS-10782: The file system mounted on 'string' has not been prepared for ACFS
Security, nothing to be undone.
Cause: The file system was not prepared for ACFS Security.
Action: None
ACFS-10783: ACFS Encryption is not set on the file system mounted on 'string',
nothing to be undone.
Cause: ACFS Encryption was not set on the file system.
Action: None
ACFS-10784: Could not destroy all realms, unable to undo ACFS Security.
Cause: All realms were not destroyed.
Action: Re-execute the command.
ACFS-10785: Could not destroy all rules, unable to undo ACFS Security.
Cause: All rules were not destroyed.
ACFS-10786: Could not destroy all rulesets, unable to undo ACFS Security.
Cause: All rulesets were not destroyed
ACFS-10787: Failed to prepare ACFS Security on mount point 'string' as replication
is active on this mount point.
Cause: Replication was active on the mount point. ACFS Replication and ACFS
Security cannot co-exist on the same mount point.
Action: Terminate replication by using command 'acfsutil repl term' and then retry.
ACFS-10788: ACFS Security undo operation on mount point 'string' completed.
Cause: ACFS Security undo operation on the mount point was completed.
Action: None
ACFS-10789: Failed to undo ACFS Security on mount point 'string'.
ACFS-10790: Failed to set ACFS Encryption on mount point 'string' as replication is
active on this mount point.
Encryption cannot co-exist on the same mount point.
ACFS-10791: Failed to undo ACFS encryption on mount point 'string'.
ACFS-10792: Cannot add filter 'string:string' to the cloned realm as the rule set
'string' does not exist on the mount point 'string'.
Cause: Filters could not be added to cloned realm because rule sets were not present
on mount point.
Action: Clone rules and rule sets first and then add command rules to the cloned
realm using 'sec realm add' command.
ACFS-10793: File objects cannot be added to cloned realm as file objects do not
exist on destination mount point.
Cause: File objects could not be added to cloned realm because file objects were not
present on destination mount point.
Action: Copy File objects to destination mount point and then add file objects to the
cloned realm using 'sec realm add' command.
ACFS-10794: File 'string' does not exist on mount point 'string'.
Cause: Information of file could not be obtained, because either file name specified is
not correct or file does not exist on given mount point.
Action: Specify the correct file name or specify the mount point where the file exists.
ACFS-10795: Cannot load ACFS security meta data because the destination mount
point 'string' already has some user-created rules, rule sets or realms.
Cause: ACFS security load was not done as the destination mount point had some
user created rules, rule sets or realms.
ACFS-00501 to ACFS-11111 2-195
Action: Run 'acfsutil sec prepare -u' followed by 'acfsutil sec prepare' on the
destination mount point and then retry the command, or use a file system with no
security objects (like realms, rules and rule sets) except system realms.
ACFS-10796: A prior failed encryption initialization cannot be recovered for this
request because the prior initialization specified a password-protected key store.
Cause: A prior failed encryption initialization was not recovered for this request
because the prior initialization specified a password-protected key store.
Action: Execute the command 'acfsutil encr init' with option 'p'.
ACFS-10797: A prior failed encryption initialization cannot be recovered for this
request because the prior initialization specified a non-password-protected key
store.
because the prior initialization specified a non-password-protected key store.
Action: Execute the command "acfsutil encr init' without option 'p'.
ACFS-10798: ACFS Encryption undo operation on mount point 'string' completed.
Cause: ACFS Encryption undo operation on the mount point was completed.
Action: None
ACFS-10799: For cloning realms with 'string' option, destination mount point must
be same as source mount point.
Cause: Cloning of file system objects is not supported if destination mount point is
different from source mount point.
Action: Run 'acfsutil sec realm clone' without -f option, copy file objects to the
destination mount point, and then add files using 'acfsutil sec realm add' command.
ACFS-10800: Failed to complete ACFS Security undo operation on mount point
'string'.
Cause: ACFS Security undo operation did not complete because some rules, rulesets,
or realms exist for the given file system.
Action: Retry the operation after making sure that no other 'acfsutil sec' commands
are running for the given file system.
ACFS-10801: failed to acquire a lock on ACFS security wallet
Cause: The ACFS security wallet could not be initialized because the lock on the
wallet could not be obtained.
css'. If the CRS stack is not up, check with the CRS administrator to bring it up. If this
ACFS-10802: unable to release the lock being held on the ACFS security wallet
Cause: After security initialization, the lock on ACFS security wallet could not be
released.
ACFS-10803: cannot proceed because another instance of 'acfsutil' command is

updating the ACFS security wallet
Cause: An attempt to update the ACFS security wallet failed because the ACFS
security wallet was locked by another instance of the acfsutil command.
Action: Retry the command later.
ACFS-10850: Password must have at least number characters.
Cause: The password was not long enough.
Action: Provide the password with number of characters greater than minimum
required length.
ACFS-10851: Password must have at least one digit and letter in it.
Cause: The password did not have either a digit or a letter in it.
Action: Provide a password containing at least one digit and letter.
ACFS-10901: Failed to add the read-only snapshot file 'string' to realm 'string'.
Cause: A file specified for addition to a security realm was a read-only snapshot file.
Action: None
ACFS-10902: Failed to add the read-write snapshot file 'string' to realm 'string'.
Cause: A file specified for addition to a security realm was a read-write snapshot file.
Action: None
ACFS-10903: Snapshot 'string' of mount point 'string' is not prepared for ACFS
Security.
Cause: Snapshot was not prepared for security operations on mount point.
Action: None
ACFS-10914: Security is already enabled in snapshot 'string' of mount point 'string'.
Cause: Security was already enabled in snasphot of mount point.
Action: None
ACFS-10915: Security is already enabled on realm 'string' in snapshot 'string' of
mount point 'string'
Cause: Security was already enabled on realm in snapshot.
Action: None
ACFS-10916: Security is now enabled in snapshot 'string' of mount point 'string'.
Cause: Security was enabled in snapshot of mount point.
Action: None
ACFS-10917: Failed to enable security in snapshot 'string' of mount point 'string'.
ACFS-10918: Security is already disabled in snapshot 'string' of mount point
'string'.
Cause: Security was already disabled in snapshot of mount point.
Action: None
ACFS-00501 to ACFS-11111 2-197
ACFS-10919: Security is already disabled on realm 'string' in snapshot 'string' of

mount point 'string'.
Cause: Security was already disabled on realm in snapshot.
Action: None
ACFS-10920: Failed to disable security in snapshot 'string' of mount point 'string'.
ACFS-10921: Realm 'string' not found in snapshot 'string' of mount point 'string'.
Cause: Realm was not found in snapshot of mount point.
<mount_point> -S <snapshot_name> -n'.
ACFS-10922: Failed to get security related information of snapshot 'string' of mount
point 'string'.
ACFS-10923: Failed to get users for realm 'string' in snapshot 'string' of mount point
'string'.
ACFS-10924: Failed to get groups for realm 'string' in snapshot 'string' of mount
point 'string'.
ACFS-10925: Failed to get realm encryption attributes of realm 'string' in snapshot
'string' of mount point 'string'.
ACFS-10926: Attributes of realm 'string' in snapshot 'string' of mount point 'string'
retrieved.
Cause: Attributes of realm in snapshot were retrieved.
Action: None
ACFS-10927: Failed to get all rules in snapshot 'string' of mount point 'string'.
ACFS-10928: Failed to get information of rule 'string' in snapshot 'string' of mount
point 'string'.
ACFS-10929: Rule 'string' not found in snapshot 'string' of mount point 'string'.
Cause: Rule was not found in the snapshot.
Action: Ensure that the rule exists by executing 'acfsutil sec info -m <mount_point> -S
<snapshot_name> -l'.
ACFS-10930: Failed to get all rule sets in snapshot 'string' of mount point 'string'.
ACFS-10931: Failed to get rules for rule set 'string' in snapshot 'string' of mount
point 'string'.
ACFS-10932: Rule set 'string' not found in snapshot 'string' of mount point 'string'.
Cause: Rule set was not found in snapshot of mount point.
Action: Ensure that the rule set exists by executing 'acfsutil sec info -m
<mount_point> -S <snapshot_name> -s'.
ACFS-10933: Failed to delete the read-only snapshot file 'string' from realm 'string'.
Cause: Security operations cannot be performed on a read-only snapshot file.
Action: None
ACFS-10934: Failed to delete the read-write snapshot file 'string' from realm 'string'.
Cause: Security operations cannot be performed on a read-write snapshot file.
Action: None
ACFS-10935: ACFS Security cannot be enabled or disabled because 'string' is a
read-only snapshot
Cause: A request to enable or disable ACFS Security specified a read-only snapshot.
Action: None
ACFS-10936: ACFS Security is now disabled in snapshot 'string' of mount point
'string'.
Action: None
ACFS-10937: ACFS Security is now enabled on realm 'string' in snapshot 'string' of
Action: None
ACFS-10938: ACFS Security is now disabled on realm 'string' in snapshot 'string' of
Action: None
ACFS-10939: ACFS Security is now enabled on realm 'string' in mount point
'string'.
Action: None
ACFS-00501 to ACFS-11111 2-199
ACFS-10940: ACFS Security is now disabled on realm 'string' in mount point

'string'.
Action: None
ACFS-10941: Failed to create 'string' file on mount point 'string'
Cause: An attempt to create a file on the indicated mount point failed, most likely
because the user lacked the requisite permission.
Action: Ensure that the user has the required permission and retry. Otherwise, contact
ACFS-10942: Insufficient disk space on mount point 'string'
Cause: The requested operation failed because the file system was full.
Action: Resize the file system and retry.
ACFS-10945: ACFS Auditing source 'string' is already enabled on mount point
'string'.
Action: None
ACFS-10946: ACFS Auditing source 'string' is already disabled on mount point
'string'.
Action: None
ACFS-10947: Audit trail on mount point 'string' is marked as read.
Action: None
ACFS-10948: Audit trail on mount point 'string' is archived.
Action: None
ACFS-10949: ACFS Auditing has been initialized on the cluster with 'string' as the
Oracle ACFS auditor OS group and 'string' as the Oracle ACFS audit manager OS
group.
Action: None
ACFS-10950: Audit trail archive for mount point 'string' is purged.
Action: None
initialize auditing.
Action: Run 'acfsutil audit init' as an OS user with administrative privileges.
ACFS-10952: Auditing already initialized; cannot reinitialize.
Cause: An attempt was made to initialize auditing after it was already initialized.
Action: None
ACFS-10953: Auditing is not initialized.

Cause: A command was issued which requires auditing to be intialized for the cluster,
but auditing has not been initialized.
Action: Initialize auditing by reissuing 'acfsutil audit init' command.
ACFS-10954: Failed to enable auditing on mount point 'string'.
Action: Refer to audit log '<mount_point>/.Security/audit/audit-<host_name>.log'.
ACFS-10955: Failed to disable auditing on mount point 'string'.
ACFS-10956: Failed to enable auditing for realm 'string' on mount point 'string'.
ACFS-10957: Failed to disable auditing for realm 'string' on mount point 'string'.
ACFS-10958: Current user does not have privileges to run audit commands.
Cause: Command was executed as user who is not part of audit manager OS group or
auditors OS group.
Action: Run command as user who is part of audit manager OS group or auditors OS
group.
ACFS-10960: Failed to get audit information for the mount point 'string'.
ACFS-10961: Failed to get audit manager OS group.
ACFS-10962: Failed to get auditor OS group.
ACFS-10963: Auditing is not enabled on mount point 'string'.
Cause: A command was issued that requires auditing to be enabled at the file system
level, but it is not enabled.
Action: Run 'acfsutil audit enable', and retry the command.
ACFS-10964: Failed to archive audit trail on mount point 'string'.
ACFS-10965: Failed to mark audit trail on mount point 'string' as read
ACFS-00501 to ACFS-11111 2-201

ACFS-10966: Audit trail on mount point 'string' is already marked as read.
Cause: Audit trail was already marked as read on mount point.
Action: None
ACFS-10967: Audit trail on mount point 'string' not found.
Cause: An 'acfsutil audit' command was issued but auditing has not been initialized.
Action: Run 'acfsutil audit init' as an OS user with administrative privileges, then
reissue the original command.
ACFS-10968: Failed to create audit trail XML file 'string' for mount point string.
ACFS-10969: Failed to purge audit trail archive file for mount point 'string'.
ACFS-10970: Failed to purge audit trail archive because it is not marked 'read' for
Cause: Audit trail was not yet marked as 'read' on mount point.
Action: Run 'acfsutil audit read' and retry the command.
ACFS-10971: Current user does not have privileges to run this audit command.
Cause: Command was executed as user who is not part of audit manager OS group.
Action: Run command as user who is part of audit manager OS group.
ACFS-10972: Failed to update audit managers and auditors group information in
the driver; some of the subsequent audit related commands may fail.
Cause: Audit Managers and Auditors information was not communicated to the
ACFS driver during mount. The mount command was successful but the subsequent
audit commands will not work on this host until the problem is corrected.
version 'string' to enable auditing on mount point 'string'.
Cause: A security adminstrator or audit manager or administrator attempted to
enable auditing, but the 'COMPATIBLE.ADVM' attribute for the disk group had not
been upgraded to a supported version.
the COMPATIBLE.ADVM attribute and enable auditing using the 'acfsutil audit
enable' command.
ACFS-10974: Auditing cannot be enabled on mount point 'string', because ADVM
compatibility is lower than 'string'.
Cause: A security adminstrator or system administrator attempted to enable auditing
as part of 'acfsutil sec prepare' or 'acfsutil encr set' which was successful, but auditing
could not be enabled because the 'compatible.advm attribute had not been upgraded
to a supported version.
enable' command.
ACFS-10975: Failed to get audit information for realm 'string' on mount point
'string'.
ACFS-10976: Failed to create audit trail XML file because the old audit trail XML
file exists for mount point 'string'.
Cause: A request to archive the audit trail found an existing audit trail XML file.
Action: Run 'acfsutil audit purge' and retry the command.
ACFS-10977: Auditing is enabled for realm 'string' on mount point 'string'.
Action: None
ACFS-10978: Auditing is disabled for realm 'string' on mount point 'string'.
Action: None
ACFS-10979: Cannot proceed because file system is not prepared for ACFS
Security.
Cause: An attempt to enable or disable audit on Security source failed because the file
system was not prepare for ACFS Security.
Action: Execute 'acfsutil sec prepare' to prepare ACFS Security on the file system and
retry 'acfsutil audit' command.
ACFS-10980: Cannot proceed because file system is not set for ACFS Encryption.
Cause: An attempt to enable or disable audit on Encryption source failed because the
file system was not set for ACFS Encryption.
Action: Execute 'acfsutil encr set' to set ACFS Encryption on the file system and retry
'acfsutil audit' command.
ACFS-10998: ACFS Audit not initialized
Cause: ACFS Audit was not initilized.
Action: Run 'acfsutil audit init' command.
ACFS-10999: Audit trail archive file on mount point 'string' was not found.
Cause: An 'acfsutil audit read' command was issued but the audit trail backup file did
not exist.
Action: Run 'acfsutil audit archive' as an OS user with Audit Manager privileges, then
ACFS-11000: ACFS Auditing is already initialized with different Audit Managers
and Auditors group.
Cause: Values provided on the command line did not match those with which ACFS
Auditing was initialized earlier.
Action: Run 'acfsutil audit init' command with the Audit Managers and Auditors
group provided for the previous initialization.
ACFS-00501 to ACFS-11111 2-203
ACFS-11001: Error in parsing command line arguments.

Cause: There was a syntax error is the command line arguments.
Action: Check the command line syntax and re-run the command again.
ACFS-11002: Error: a device name must be supplied with the -l option.
Cause: Either the -l option was not present in the command line or it had no
argument.
Action: Make sure you run the command with the '-l device-name' option.
ACFS-11003: AIX ODM initialization failed, odmerr number
Cause: AIX ODM internal operation error.
Action: Internal error - contact Oracle Customer Support.
ACFS-11004: failed to lock AIX ODM database, odmerr number
Cause: The method could not lock the AIX ODM database.
Action: Check to see what other method has locked it.
ACFS-11005: failed to look up AIX ODM PdDv object class, odmerr number
Cause: The user may lack required permission or the entry may not exist.
Action: Ensure that the object exists and that the user has the required permission;
otherwise, contact Oracle Customer Support.
ACFS-11006: failed to open AIX ODM CuDv object class, odmerr number
ACFS-11007: failed to add to AIX ODM CuDv object class, odmerr number
Cause: An attempt to add the device's entry to the ODM CuDv object class failed.
Action: Ensure the user has the required permission.
ACFS-11008: failed to close the AIX ODM CuDv object class, odmerr number
Action: Contact Oracle Customer Support.
ACFS-11010: failed to look up AIX ODM CuDv object class, odmerr number
ACFS-11015: failed to load kernel extension string, errno number (string)
Cause: Loading the kernel extension into the kernel failed.
Action: Check the error message and resolve the error.
ACFS-11017: failed to configure kernel extension string, errno number (string)
Cause: Could not configure the device's driver in the kernel.
ACFS-11018: failed to get a major number for device string
Cause: The method could not get a major number for the device.

ACFS-11019: failed to get a minor number for device string
Cause: The method could not get a minor number for the device.
ACFS-11022: failed to configure device string, errno number (string)
Cause: Attempt to configure the device's driver in the kernel got an error.
ACFS-11024: failed to remove the old device file string, errno number (string)
Cause: The method failed to remove the device file.
Action: Ensure that the user has permission and no other application is still using the
device.
ACFS-11026: failed to create new device file string, errno number (string)
Cause: The user may not have permission or a file with the same name already exists.
Action: Ensure that the file does not already exist and that the user has the required
permission to create it.
ACFS-11028: failed to set permission of the new device file string, errno number
(string)
Cause: The method failed to set permission of the device special file.
Action: Ensure the user has the required privilege.
ACFS-11030: failed to set group of the new device file string, errno number (string)
Cause: The method failed to set the owning group of the device special file.
ACFS-11031: failed to open the ASMADMIN group file, errno number (string)
Cause: The method could not open the file containing the group to own the device.
Action: Ensure the installation completed successfully.
ACFS-11032: failed to read from the ASMADMIN group file, errno number (string)
Cause: The method could not read the file containing the group to own the device.
ACFS-11034: failed to set device state to AVAILABLE, odmerr number
Cause: The method could not change the device's state.
Action: AIX ODM internal error - contact Oracle Customer Support.
ACFS-11036: No operation was performed because device state is string instead of
DEFINED.
Cause: The method expected a DEFINED device state.
ACFS-11038: failed to unconfigure kernel extension string, errno number (string)
Cause: The method could not unconfigure the kernel extension.
ACFS-00501 to ACFS-11111 2-205
ACFS-11040: failed to unload kernel extension string, errno number (string)

Cause: The method could not unload the extension from kernel.
ACFS-11044: no minor number was returned for device string
Cause: The operating system did not return a device minor number as requested.
ACFS-11046: failed to set device state to DEFINED, odmerr number
Cause: The method failed to change the device's state.
ACFS-11050: failed to delete attributes of device string, odmerr number
Cause: The method failed to remove the device's attributes from the AIX ODM CuAt
object class.
Action: Internal AIX ODM error - contact Oracle Customer Support.
ACFS-11052: failed to delete customized object of device string, odmerr number
Cause: The method failed to remove the device's entry from the AIX ODM CuDv
object class.
ACFS-11053: failed to release major number for device string
Cause: The method failed to release the device's major number.
ACFS-11055: failed to remove device special file string, errno number (string)
Cause: The method failed to remove the device special file.
Action: Check the error message and resolve it.
ACFS-11060: failed to unload kernel extension string
Cause: Could not unload the extension from kernel.
ACFS-11061: failed to look up the group id for group string
Cause: The named group probably does not exist.
Action: Make sure the group exists in the /etc/group file.
ACFS-11062: failed to create directory string, errno number (string)
Cause: The directory could not be created.
Action: Check the permission of the base directory to make sure it is writeable.
ACFS-11063: failed to set permission on directory string, errno number (string)
Cause: The permission of the directory could not be changed.
ACFS-11064: failed to set group on directory string, errno number (string)
ACFS-11065: invalid device minor number number

Cause: The device minor number being used is out of range.
ACFS-11066: the ADVM driver is not loaded
Cause: The ADVM driver is expected to exist in the kernel but it does not.
Action: Load the ADVM driver and then try it again.
ACFS-11067: directory /dev/asm does not exist or is not accessible, errno number
(string)
Cause: The ADVM driver probably has not been successfully loaded.
ACFS-11068: The state of device string is unknown. No operation was performed.
Cause: Unknown.
ACFS-11069: Error: device name is too long, exceeding 255 characters.
Cause: The chosen device name exceeds the limit of 255 characters.
Action: Use a device name that is shorter than the limit.
ACFS-11111: string
Cause: None
Action: None
ACFS-00501 to ACFS-11111 2-207
3
ACFSK-00004 to ACFSK-00091
ACFSK-00004: The Security file for volume mounted at %2 cannot be created (error
status %3), and so the volume cannot be used by this node.
Cause: This is not a simple disk-full condition.
Action: Try mounting again and, if that fails, run acfschkdsk to fix the filesystem.
ACFSK-00005: The Security file for volume %2 cannot be created (error status %3),
and so the volume cannot be used by this node.
ACFSK-00006: The Security file for volume with device minor number %2 cannot
be created (error status %3), and so the volume cannot be used by this node.
ACFSK-00007: The Security file for volume mounted at %2 cannot be created
because the filesystem is full.
Cause: because the filesystem is full. The volume cannot be used by this node until
the Security file is successfully created.
Action: Either expand the storage available for this ACFS volume using the "acfsutil
size" command or reduce the space being used.
ACFSK-00008: The Security file for volume %2 cannot be created because the
filesystem is full.
be created because the filesystem is full.
ACFSK-00010: The Security file for volume mounted at %2 cannot be created due to
insufficient memory.
Cause: probably due to insufficient memory, and so the filesystem cannot be used at
this node.
ACFSK-00004 to ACFSK-00091 3-1
ACFSK-00011: The Security file for volume %2 cannot be created due to

this node.
be created due to insufficient memory.
this node.
ACFSK-00013: The Security information for volume mounted at %2 file %3 is
missing.
Cause: An ACL granting full access to Administrators has been associated with the
file.
Action: Modify the ACL as required.
ACFSK-00014: The Security information for volume %2 file %3 is missing.
file.
ACFSK-00015: The Security information for volume with device minor number %2
file %3 is missing.
file.
ACFSK-00019: Volume %2 now OFFLINE. Internal ACFS Location %3 .
Cause: A problem accessing valid file system metadata was seen at a critical point
during processing. All attempts to read or write files will fail on this node.
Action: unmount and remount the file system on this node. See the ACFS
Administration Guide for more information about OFFLINE file systems.
ACFSK-00020: RECOVERY requested for volume %2 . Internal ACFS Location %3 .
Cause: ACFS has initiated recovery for the volume.
Action: n/a
ACFSK-00021: FSCK-NEEDED set for volume %2 . Internal ACFS Location %3 .
Cause: A problem has been detected with the file system metadata in the above
volume.
Action: Normal operation can continue, but it is advisable to run fsck/acfschkdsk in
the fixer mode on the file system as soon as it is feasible to do so. See the ACFS
Administration Guide for more information about FSCK-NEEDED.
ACFSK-00022: Mount for volume at %2 succeeded but there was a previous
metadata error.
Cause: Metadata error.
Action: Run fsck/acfschkdsk as soon as possible.
3-2 Error Messages
ACFSK-00023: Mount for volume %2 succeeded but there was a previous metadata
error.
ACFSK-00024: Mount for volume with device minor number %2 succeeded but
there was a previous metadata error.
ACFSK-00025: On the volume mounted at %2, file %3 is memory mapped for write
on this node and another node is about to modify it.
Cause: Concurrent sharing is not supported for mmaped files. This may result in the
file contents becoming inconsistent.
Action: Un-mmap the file.
ACFSK-00026: On the volume mounted at %2 file %3 is memory mapped for write
on this node and another node is about to modify it.
ACFSK-00027: On the volume with device minor number %2 file %3 is memory
mapped for write on this node and another node is about to modify it.
ACFSK-00028: An attempt to open a file reached the system limit for open ACFS
files.
Cause: The number of open files was already at the system limit when an attempt was
made to open another file.
Action: This limit can be increased by changing the AcfsMaxOpenFiles tuneable using
the acfsutil command.
ACFSK-00029: Volume %2 is now offline
Cause: See preceding messages.
Action: See preceding messages.
ACFSK-00030: ASM Instance has Failed.
Cause: The ASM instance was either intentionally stopped or it failed.
Action: See ASM trace messages if this was not intentional. Restart ASM.
ACFSK-00032: Mount failed for device minor number %2 with status %3 .
Cause: Mount request failed with status indicated.
Action: Try to mount again. If it fails again, run the file system checker and try to
mount again. If that fails, inform Oracle Support Services.
ACFSK-00033: Information pertaining to a metadata error has been saved in the file
%2 .
Cause: A metadata error was detected and relevant data was saved for future
examination.
Action: Display the file to learn which volume experienced the problem and then run
acfschkdsk when it is feasible to do so. Include the contents of the mentioned file if
reporting this problem to Oracle.
ACFSK-00034: In volume mounted at %2, snapshots for memory-mapped file with
file identifier %2 are no longer valid.
Cause: ACFS was unable to obtain sufficient storage within the volume in order to
maintain the validity of the snapshot versions of this file.
Action: To avoid further errors of this type, either expand the storage available for
this ACFS volume or reduce the space being used. Run the command "acfsutil info id
%3" to get the pathname of the file.
ACFSK-00035: In volume %2, snapshots for memory-mapped file with file
identifier %3 are no longer valid.
ACFSK-00036: In volume with device minor number %2, snapshots for memorymapped file with file identifier %3 are no longer valid.
ACFSK-00038: Module failed to load and start with status %2. Build information:
%3 %4 %5
Cause: The operating system could not load the ACFS driver.
Action: Contact Oracle Support Services if the corrective action based on the status is
not clear.
ACFSK-00040: Mount failed for device minor number %2 with status %3 . Error
found in superblock.
Cause: ACFS does not recognize a valid ACFS superblock on the indicated device.
Action: If there should be a valid ACFS file system on the indicated device, run
acfschkdsk to attempt to repair the superblock.
ACFSK-00041: Mount failed for device minor number %2 with status %3. Cluster
membership is not established.
Cause: This node is not a member of the cluster.
Action: Ensure ASM is up and functional.
3-4 Error Messages
ACFSK-00042: Mount failed for device minor number %2 with status %3.
Insufficient kernel resources to complete the mount.
Cause: The mount request failed due to a lack of operating system resources. This is
likely to be a transient failure.
Action: Try to mount again. If it fails again, inform Oracle Support Services.
ACFSK-00044: Metadata validation error encountered on volume mounted at %2. A
read retry succeeded for file identifier %3 starting disk offset %4.
Cause: ACFS detected a problem with the content of metadata read from the disk but
reading again provided valid data.
Action: No action required. A layer in the storage stack may be malfunctioning.
ACFSK-00045: Metadata validation error encountered on volume %2. A read retry
succeeded for file identifier %3 starting disk offset %4.
ACFSK-00046: Metadata validation error encountered on volume with device minor
number %2. A read retry succeeded for file identifier %3 starting disk offset %4.
read retry failed for file identifier %3 starting disk offset %4.
Cause: ACFS detected a problem with the content of metadata read from the disk and
reading again did not provide valid data.
Action: Run the file system checker as soon as possible.
failed for file identifier %3 starting disk offset %4.
number %2. A read retry failed for file identifier %3 starting disk offset %4.
ACFSK-00052: Volume %2 (Major: %3, Minor: %4) mount failed. Volume is out of
space.
Cause: Mount failed due to insufficient space available in the volume.
ACFSK-00053: Volume %2 (Major: %3, Minor: %4) mount failed. Volume version
does not match the ACFS driver version.
Cause: The mount failed because the version of ACFS in the kernel is not compatible
with the version of the volume stored on disk.
Action: If this file system was created with newer drivers, the ADVM compatibility
was increased, and new features were used, then it is not possible to mount this file
system with an older driver. Otherwise, ensure the correct drivers and tools are
installed. Running fsck/acfschkdsk may provide further clues.
ACFSK-00054: Volume %2 (Major: %3, Minor: %4) mount failed with internal
status code (%5).
Cause: The mount failed because ACFS detected an internal error.
Action: Verify that the version of ACFS being run is corect. If it is, inform Oracle
Support Services.
ACFSK-00055: Volume %2 (Major: %3, Minor: %4) mount failed. Cluster
membership is not established.
Cause: The mount failed because this node is not in a cluster.
Action: Ensure ASM is configured properly. Wait until the node has joined a cluster
and try again.
ACFSK-00056: Volume %2 (Major: %3, Minor: %4) mount failed. Insufficient
kernel resources to complete the mount.
Cause: The mount failed because of a resource problem, possibly temporary and
probably kernel memory.
Action: Try the mount again. If it fails again, inform Oracle Support Services.
ACFSK-00057: Volume %2 (Major: %3, Minor: %4) mount failed. Error in
superblock.
Cause: A problem has been detected in the superblock.
Action: Run fsck/acfschkdsk when possible and try to mount again. If it fails again,
inform Oracle Support Services.
ACFSK-00061: An ACFS Assertion failed at %2 line %3.
Cause: An ACFS Assertion failed.
Action: See the next message from Oracle OKS which may contain the location of a
file containing further information. Include the contents of this file if reporting the
problem to Oracle
ACFSK-00062: An I/O error was encountered while invalidating a replication log
record. Replication is being terminated for file system %2.
Cause: This leaves the primary and standby sites out of sync, so replication is being
terminated for file system %2.
Action: n/a
ACFSK-00063: Acfs kernel extension configuration failed. Diagnostic codes: %2
%3 / %4 %5 / %6 .
Cause: An error was seen during Acfs configuration and/or initialization.
Action: Inform Oracle Support Services and provide the message displayed.
ACFSK-00064: Logging to the file %2 has stopped. Backup the log archive %3%4 to
a new location if required, and then remove the log archive to restart logging.
Cause: Log file size limit reached while the log archive still exists.
Action: Backup the log archive to a new location if required, and then remove the log
archive.
3-6 Error Messages
ACFSK-00065: Log file %2 has been archived at location %3%4.

Cause: The log file was archived since the file reached its specified size limit.
Meanwhile, logging to the original file will continue.
archive. Failing to do this before the log file fills again will result in loss of log data.
ACFSK-00066: An archive of the log file %2 exists at location %3%4.
Cause: Active log file is reaching its specified size limit and the log archive has not
been removed. Logging will stop after active log file reaches its specified size limit
and the log archive still has not been removed.
archive. Failing to do this before the log file fills again will result in loss of log data.
ACFSK-00067: Logging to the file %2 has stopped. Backup the log archive %3%4 to
a new location if required, and then remove the log archive to restart logging.
Cause: Log file size limit reached while the log archive still exists.
Action: Contact an ACFS Security Administrator to backup the log archive to a new
location if required, and then remove the log archive.
ACFSK-00068: Log file %2 has been archived at location %3%4.
Cause: The log file was archived since the file reached its specified size limit.
Meanwhile, logging to the original file will continue.
location if required, and then remove the log archive. Failing to do this before the log
file fills again will result in loss of log data.
ACFSK-00069: An archive of the log file %2 exists at location %3%4.
Cause: Active log file is reaching its specified size limit and the log archive has not
been removed. Logging will stop after active log file reaches its specified size limit
and the log archive still has not been removed.
location if required, and then remove the log archive. Failing to do this before the log
file fills again will result in loss of log data.
ACFSK-00070: %2 saw exception %3 .
Cause: An unexpected exception was detected.
Action: Inform Oracle Support Services and provide the message displayed.
ACFSK-00071: Volume encryption keys are not available for the file system
mounted at %2, encrypted files will not be available.
Cause: Volume encryption keys (VEKs) were not available to the file system. Possible
causes are: 1) The ACFS Encryption key store was missing. This is indicated by
message ACFS-10573 during mount. 2) The ACFS Encryption key store was
corrupted. 3) ACFS Encryption was configured to use a password-protected key store
and an incorrect key store password was supplied when mounting the file system. 4)
ACFS Encryption was configured to use a password-protected key store and the file
system was mounted via the ACFS Mount Registry.
Action: Immediately unmount and remount the file system without using the ACFS
Mount Registry, providing the correct password if required. If the problem persists,
ACFSK-00072: A call to fcntl(2) F_SETFL has cleared O_DIRECT while I/O was
active for the file with file identifier %2 in the volume %3. This is not allowed.
Cause: User-space code called fcntl and cleared the O_DIRECT open flag of a file
being used for Direct I/O.
Action: Ensure that user-space code does not reset O_DIRECT when calling fcntl
F_SETFL.
ACFSK-00073: ACFS _FCB hash size is %2.
Action: None
ACFSK-00074: ASSERTION FAILURE: %2 File: %3 Line: %4.
Cause: An internal ACFS assertion has failed.
Action: Contact Oracle Support.
ACFSK-00075: Oracle kernel distributed lock manager hash size is %2.
Action: None
ACFSK-00076: Buffer cache size: %2MB in %3 buckets.
Action: None
ACFSK-00077: WARNING: the OKS and ACFS drivers have different build
information.
Cause: Warning - The ACFS label version should match the OKS label version.
Action: None
ACFSK-00078: ACFS build %2.
Action: None
ACFSK-00079: ACFS contains fixes '%2'.
Action: None
ACFSK-00080: OKS build %2.
Action: None
ACFSK-00081: OKS contains fixes '%2'.
Action: None
ACFSK-00082: The storage consumption statistics for snapshots of volume
mounted at %2 is no longer accurate.
Action: Running fsck/acfschkdsk will fix the snapshot statistics. These statistics are
for reporting purposes only.
3-8 Error Messages
ACFSK-00083: Logging to the audit trail %2 has stopped. Backup the audit trail
archive %3%4 to a new location if required, and then remove the audit trail archive
to restart logging.
Cause: Audit trail size limit reached while the audit trail archive still exists.
Action: Backup the audit trail archive to a new location if required, and then remove
the audit trail archive.
ACFSK-00084: Audit trail %2 has been archived at location %3%4.
Cause: The audit trail was archived since the file reached its specified size limit.
Meanwhile, logging to the original audit trail will continue.
the audit trail archive using 'acfsutil audit purge' command. Failing to do this before
the audit trail fills again will result in loss of log data.
ACFSK-00085: An archive of the audit trail %2 exists at location %3%4.
Cause: Active audit trail is reaching its specified size limit and the audit trail archive
has not been removed. Auditing will stop after active audit trail reaches its specified
size limit and the audit trail archive still has not been removed.
the audit trail archive. Failing to do this before the audit trail fills again will result in
loss of audit trail data.
read retry on mirror %3 succeeded for file identifier %4 starting disk offset %5.
Cause: ACFS detected a problem with the content of metadata read from the disk, but
retrying using the mirror cited in the message provided
on mirror %3 succeeded for file identifier %4 starting disk offset %5.
number %2. A read retry on mirror %3 succeeded for file identifier %3 starting disk
offset %4.
ACFSK-00089: failed to free storage from a deleted large file on the volume
mounted at string; will continue to attempt to free the storage
Cause: ACFS failed to free the space from a deleted large file because the filesystem
had no free storage.
Action: Remove smaller files, a directory, or a snapshot to free some blocks, or run
'fsck -a' to return the space from the large file.
ACFSK-00090: failed to free storage from a deleted large file on volume string; will
continue to attempt to free the storage
ACFSK-00091: failed to free storage from a deleted large file on the volume with
device minor number string; will continue to attempt to free the storage
3-10 Error Messages
4
ADVM-00501 to ADVM-11111
ADVM-00501: unable to allocate a buffer
ADVM-00502: Failed to communicate with the ACFS driver. Verify the ACFS
driver has been loaded.
Cause: The ACFS control device could not be accessed.
Action: Verify the ACFS driver is loaded and running.
ADVM-00506: Failed to read 'string'.
Cause: An open file could not be read.
Action: The most likely cause is a file permission problem.
ADVM-00507: Failed to seek to string prior to writing the volume disk header.
Cause: A seek to the volume failed. This message is accompanied by other message(s)
ADVM-00508: unable to obtain device major and minor number for volume string
ADVM-00509: unsupported file type for string, not a block device
Cause: Volume provided was not recognized as a block device. This message is
ADVM-00510: unable to obtain volume id for string
Cause: Volume id was not obtained. This message is accompanied by other
ADVM-00501 to ADVM-11111 4-1
ADVM-00514: unable to close handle

Cause: Handle could not be closed. This message is accompanied by other message(s)
ADVM-00516: stat of string failed
Cause: Stat() failed. This message is accompanied by other message(s) providing
ADVM-00517: unable to obtain block device sector size
ADVM-00518: unable to obtain volume size in sectors
ADVM-00521: Failed to determine file type of string.
ADVM-00522: unable to get drive structure
ADVM-00524: unable to obtain partition information
ADVM-00525: failed to seek to string
Cause: Failed to seek to volume. This message is accompanied by other message(s)
ADVM-00526: read of volume disk header failed
Cause: Failed to read volume. This message is accompanied by other message(s)
4-2 Error Messages
ADVM-00527: unable to dismount volume
Cause: Could not dismount volume. This message is accompanied by other
ADVM-00531: write of volume disk header failed
Cause: Write to volume failed. This message is accompanied by other message(s)
ADVM-00547: Both the primary and alternate superblocks are damaged.
Cause: The file system metadata was found to be damaged.
Action: Run fsck (Unix or Linux) or acfschkdsk.exe (Windows) as soon as possible to
fix the metadata inconsistency.
ADVM-00548: Failed to communicate with the ACFS driver. Verify that cluster
membership has been established.
Cause: The ACFS driver's control device could not be accessed.
Action: Verify the driver is loaded and running. Also, verify that the ASM instance is
accessible.
ADVM-00549: mount path string already contains a volume mount point for
volume string
Cause: The mount path contained a reparse point that references a a different volume
than the mount request.
Action: Verify the path is correct. If it is, the existing volume mount point must be
removed before a new one can be created. Use acfsdismount to remove the mount
point.
ADVM-00555: unsupported file type for string, not a device file
Cause: Volume provided was not recognized as a device file. This message is
ADVM-00556: invalid vfs name string
Cause: a helper command was called with an unexpected vfs name argument
Action: Verify that ACFS helper commands are installed in the '/sbin/helpers/acfs'
directory and that '/etc/vfs' contains the correct information for ACFS. If the solution
is not clear, contact Oracle Support Services.
ADVM-00562: An attempt to create Oracle Registry ACFS key string resulted in a
registry error. string
Cause: An error was returned by the Oracle Registry service when attempting to
create an ACFS key. This message is accompanied by other message(s) that provide
details as to the exact cause of the failure.
ADVM-00501 to ADVM-11111 4-3
ADVM-00564: unable to delete Oracle Registry key string while trying to recover
from an error string
Cause: Removal of a key from the Oracle Registry failed.
ADVM-00565: unable to delete Oracle Registry key string string
Cause: Removal of mount key from Oracle Registry failed.
Action: Use acfsutil registry to verify the mount key exists in the Oracle Registry.
ADVM-00566: invalid handle received when attempting to close an ACFS mount
ADVM-00567: unknown Oracle Registry error encountered closing key
Cause: An error was returned while closing the key from the Oracle Registry.
ADVM-00568: closing of a key resulted in Oracle Registry error number
Action: Verify the Oracle Registry is accessible. If it is not accessible and the cause is
unclear, report this error to Oracle Support Services.
ADVM-00569: invalid handle received when attempting to delete an ACFS mount
ADVM-00570: The ACFS mount key specified for deletion does not exist within
Oracle Registry.
Cause: The mount key could not be located in the Oracle Registry.
Action: Use acfsutil registry to ensure the mount entry exists in the Oracle Registry.
ADVM-00571: The ACFS mount key specified for deletion is not empty.
Cause: The mount key specified for deletion from the Oracle Registry contained
dependent subkeys.
Action: View the mount entries in the Oracle Registry using "acfsutil registry" and
remove any dependent mount entries before retrying this operation.
ADVM-00572: permission denied to delete the ACFS mount entry from Oracle
Registry
Cause: The user permissions were insufficient to remove the key from the Oracle
Registry.
Action: Verify the Oracle Registry is accessible and that command is being run from a
properly authorized user ID.
4-4 Error Messages
ADVM-00573: Oracle Registry error encountered while deleting an ACFS mount

key
Cause: An error was returned while removing the key from the Oracle Registry.
ADVM-00575: deletion request of key resulted in Oracle Registry error number
ADVM-00584: failed to look up ACFS mount points in the Oracle Registry string
Cause: An error was returned while looking up a mount point in the Oracle Registry.
Action: Run ocrcheck to verify the Oracle Registry is working properly. If problem
ADVM-00585: null parameter received
Cause: A null parameter was passed to the Oracle Registry.
ADVM-00587: unknown Oracle Registry error encountered during operation on
ACFS mount entry
Cause: An error was returned while accessing the key from the Oracle Registry.
ADVM-00589: key operation resulted in Oracle Registry error number
Cause: An error was returned during a key operation with the Oracle Registry.
ADVM-00592: Seek to volume failed. Verify the volume exists.
Cause: Seek to a location on the volume failed.
ADVM-00593: The Oracle Registry returned the following error while attempting
to access ACFS key string string
Cause: Failed to access either the SYSTEM, SYSTEM.ACFS or SYSTEM.ACFS.Mounts
keys in Oracle Registry.
Action: Run ocrcheck to verify the Oracle Registry is working properly. Examine the
appended error message from the Oracle Registry service.
ADVM-00594: Failed to access ACFS mount information. The Oracle Registry
ADVM-00501 to ADVM-11111 4-5
ADVM-00595: Failed to access ACFS mount value information. The Oracle Registry
Cause: Failed to access ACFS mount value information from the Oracle Registry. This
might be due to Oracle Registry corruption or a sudden loss of the Oracle Registry
service.
ADVM-00596: A failure occurred while accessing the Oracle Registry ACFS key
"SYSTEM" for security purposes and follows this message: string
Cause: Failed to retrieve key access rights for the Oracle Registry ACFS key
"SYSTEM"
Action: Run ocrcheck to verify the Oracle Registry is working properly. Evaluate the
error message returned from the Oracle Registry appended to this message. If
necessary, run ocrdump and make sure the "SYSTEM" key exists and is accessible.
ADVM-00597: Failed to initialize the Oracle Registry's SCLS context. The SCLS
error is included with this message.
Cause: An operating system initialization failed.
Action: Evaluate the attached SCLS error message. Run ocrcheck to verify the Oracle
Registry is functioning correctly.
ADVM-00598: An error occurred while looking up the current user's operating
system account name. The error is included with this message.
Cause: ACFS was attempting to add an entry to the Oracle Registry. During this
attempt a lookup of the current user's name failed in the operating system failed.
Action: Evaluate the attached error message to determine why the current user name
could not obtained from the operating system.
to close the ACFS key string string
Cause: Possibly due to Oracle Registry corruption or a sudden loss of the Oracle
Registry service.
ADVM-00600: Failed to access ACFS mount subkey information. The Oracle
Registry returned the appended error. string
ADVM-00601: Failed to initialize this utility's access to the Oracle Registry. Verify
the registry service has started.
Action: Run ocrcheck to verify the registry service is working properly.
ADVM-00602: An internal error (BADARG) occurred while trying to determine the
Oracle Registry configuration.
Action: Contact Oracle.
4-6 Error Messages
ADVM-00603: Failed to retrieve the Oracle Cluster Registry, OCR, configuration

Cause: Failed to obtain OCR information.
Action: Run ocrcheck to verify OCR is working properly.
ADVM-00604: Failed to retrieve the Oracle Local Registry, OLR, configuration
Cause: Failed to obtain Oracle Local Registry information.
Action: Run ocrcheck -local to verify the OLR is working properly.
ADVM-00605: Failed to retrieve the Oracle Registry configuration for an unknown
reason
Cause: Failed to obtain Oracle Registry information.
Action: Run ocrcheck to verify the registry is working properly.
ADVM-00606: Could not determine if the system is configured for RAC or Oracle
Restart environment.
Cause: The Oracle Registry service configuration could not be detected
Action: Run ocrcheck to verify the Oracle registry service.
ADVM-00607: Failed to access or create Oracle Registry keys required for ACFS
operation
Cause: Oracle Registry keys required for operation either could not be accessed or
created.
Action: Another error message number will follow this message. Analyze its output.
Run ocrcheck to verify the Oracle registry is functioning properly. Also, verify acfsutil
was invoked with administrative rights when attempting to add the ACFS mount
points.
ADVM-00619: This is a string computer, but the file system was created on a string
string computer.
Cause: The file system was created on a computer which has a different Endian than
the current system. Little Endian machines (such as the intel x86 based systems) store
the Least Significant bit in the first byte of an integer value. Big Endian machines
(such as Solaris SPARC and AIX Power based systems) store the Most Significant bit
in the first byte of an integer value.
Action: Use a system with the same Endian as the system which created the file
system.
ADVM-00620: This feature is not available for Oracle version string or lower on
this platform.
Action: None
ADVM-00621: Unable to determine privileges
Cause: An error occured retrieving the user credentials.
Action: Verify the mount point is an ACFS mount point and it is not offline.
ADVM-00622: must provide a base mount point
Cause: A mount point on the base site was not provided.
Action: Provide an existing mount point on the base site.
ADVM-00501 to ADVM-11111 4-7
ADVM-00623: must provide a target mount point

Cause: A mount point on the target site was not provided.
Action: Provide an existing mount point with an empty file system on the target site.
ADVM-00624: The path specified is too long.
Cause: The path specified exceeded the allowed maximum path length.
Action: Verify the path was entered correctly, or use a different path.
ADVM-00625: string is not a valid ACFS mount point.
Cause: The mount point path specified was not a valid mount point.
Action: Provide a valid ACFS mount point.
ADVM-01001: Size specified cannot exceed size of volume.
Cause: Volume size was smaller than the requested size.
Action: Select a size that is less than or equal to the volume size and retry the ACFS
format command.
ADVM-01002: ACFS requires a minimum volume size of numberMB.
Cause: Volume was too small.
Action: Select a larger volume and retry.
ADVM-01004: string was not formatted.
Cause: An error occurred during the formatting of the volume.
Action: This message is accompanied by another error message. Respond as indicated
for that message."
ADVM-01006: unable to open volume device 'string'
Cause: Volume device could not be opened. This message is accompanied by other
ADVM-01008: unable to open file system string
Action: Verify the volume associated with the file system is enabled and online before
retrying.
ADVM-01010: Volume already contains an ACFS file system. To reformat the
volume, reissue string with the stringf option.
Cause: The on-disk metadata indicated that an ACFS file system is located on the
volume.
4-8 Error Messages
ADVM-01011: Volume contains an ACFS file system that is being checked. To

reformat the volume, reissue string with the stringf option.
by fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ADVM-01014: write of volume label failed
ADVM-01018: failed to allocate a buffer for number bytes
ADVM-01019: This volume contains a mounted ACFS file system. The file system
must be dismounted with acfsdismount on all nodes.
ADVM-01020: This volume contains a mounted non-ACFS file system. The file
system must be dismounted with 'advmutil dismount'.
Cause: The volume was in use by another non-ACFS file system.
command.
ADVM-01033: write to volume failed
ADVM-01038: write failed during setup of root directory entry
ADVM-01041: write of snaps directory entry failed
ADVM-00501 to ADVM-11111 4-9
ADVM-01043: write of lost+found directory entry failed

ADVM-01044: write of file entry table failed
ADVM-01045: write of global bitmap failed
ADVM-01046: read of global bitmap file entry failed
Cause: A read of the volume during file system creation failed. This message is
ADVM-01047: write of global bitmap file entry failed
ADVM-01049: seek to snap map header failure
Cause: A seek to the volume during file system creation failed. This message is
ADVM-01050: write to snap map header failure
ADVM-01051: partial write to snap map header failure
ADVM-01052: write to snap map info entry failure
4-10 Error Messages
ADVM-01053: partial write to snap map info entry failure
ADVM-01054: write to snap map storage entry failure
ADVM-01055: partial write to snap map storage entry failure
ADVM-01150: unable to synchronize in-memory file data to disk
Cause: A request to flush all in-memory copies of buffers associated with the open
handle failed. This message is accompanied by other message(s) providing details on
the error.
Action: Correct the problem identified by the other message(s). If the problem has
been resolved and the file system is unusable, retry the ACFS format command.
ADVM-01151: Ignoring invalid block size number, using number
Cause: An ACFS format command unsupported block size was specified.
Action: No action required. A supported block size will be used.
ADVM-01152: The length of accelerator volume name exceeds number.
Cause: Accelerator volume name length exceeded the maximum length displayed in
the message.
Action: Select an accelerator volume name with length less than or equal to the
maximum length displayed in the message and retry the command.
ADVM-01154: The accelerator volume contains a mounted ACFS file system. The
file system must be dismounted with acfsdismount on each node.
was in use by a mounted file system.
ADVM-01155: The accelerator volume contains a mounted non-ACFS file system.
The file system must be dismounted with 'advmutil dismount'.
was in use by a mounted non-ACFS file system.
command.
ADVM-00501 to ADVM-11111 4-11
ADVM-01156: The Oracle ASM Dynamic Volume Manager (Oracle ADVM)

Cause: An attempt to create a file system with an accelerator volume failed because
the ADVM compatibility attribute for the disk group was not set to 12.1.0.2.0 or
higher.
ADVM-01159: The accelerator volume must be different from the volume
containing the file system.
Cause: The file system could not be created because the same volume was specified
for both the accelerator and the file system.
Action: Choose a different volume for the accelerator and retry the command.
ADVM-01160: The specified accelerator volume was smaller than numberMB.
Cause: The file system could not be created because the specified accelerator volume
was below the minimum allowed size reported in the message.
Action: Select a larger accelerator volume and retry the command.
ADVM-01164: The specified device 'string' is already in use with a CRS-managed
file system.
Cause: The file system could not be created because the specified device was already
registered with CRS (Cluster Ready Services).
Action: Select an unused device, or use srvctl to modify the association for this device
and retry the file system creation.
Cause: A request for process virtual memory by mount command failed. This
ADVM-02006: unable to terminate the Oracle Registry connection
Action: Run crs_stat and ocrcheck to verify CSS and the Oracle Registry are working
properly. If they are not accessible and the cause is unclear, report this error to Oracle
Support Services.
ADVM-02012: Mount of string failed, volume string does not exist. Verify that
string exists on this node.
ADVM-02014: Mount of string failed. Error number was returned.
Cause: Mount operation failed.
Action: Verify the mount point and volume both exist and are accessible before
retrying the mount command.
4-12 Error Messages
ADVM-02015: Failed to open mount point string. Verify the mount point exists.
Cause: Mount point could not be opened.
Action: Verify the mount point exists and is accessible before retrying the mount
command.
ADVM-02017: Failed to open volume string. Verify the volume exists.
Cause: The volume could not be opened.
accessible before retrying the mount command.
ADVM-02018: Volume string contains an ACFS file system that is being checked.
Allow the file system check to complete.
by the ACFS checker.
Action: Allow the ACFS checker to complete before retrying the mount. If the ACFS
checker is not running on this file system and a file system check was previously
interrupted, reissue the ACFS checker.
ADVM-02026: unable to verify the host names passed in are part of the cluster
inaccurate.
ADVM-02027: unable to obtain the local CSS node name
inaccurate.
ADVM-02046: Volume string cannot be mounted. Examine the system event log for
possible causes.
Cause: The volume mount failed. This could be caused by an out of space condition if
this is the first mount of a file system on a node.
Action: Examine the system event log for more detail.
ADVM-02050: unable to set in-memory mount information
Cause: Could not communicate with the mounted file system.
ADVM-02081: Warning: acfschkdsk.exe should be run on volume string at your
earliest convenience
Cause: A flag in the superblock indicates that a metadata inconsistency has been
found on this volume.
Action: Run acfschkdsk.exe as soon as possible to fix the metadata inconsistency.
ADVM-02082: unable to verify if the host names provided are part of the cluster
ADVM-02083: cannot get the local CSS node name
Cause: Could not obtain local CSS node name.
ADVM-00501 to ADVM-11111 4-13

ADVM-02090: unable to retrieve ACFS mount information from CRS
Cause: Failed to retrieve mount information the CRS.
ADVM-02092: Mount of string failed, node string is not a member of the CSS
cluster.
Action: Verify the node listed in the entry is a member of the CSS cluster.
ADVM-02119: creating administrative network share for mount point string at
share name 'string'
Action: None
ADVM-02120: administrative network share for mount point string already exists at
share name 'string'
Action: None
ADVM-02121: administrative network share 'string' already exists, but does not
share mount point string
Cause: Attempted to create an administrative network share for the specified ACFS
mount point, but the required share name was already in use.
Action: Remove the conflicting network share using 'net share share name /delete'.
Remount the ACFS file system to retry creating an administrative network share for
the mount point.
ADVM-02122: retrieving information for administrative network share 'string'
failed
Cause: While creating an administrative network share for the specified ACFS mount
point, failed to retrieve information on any network share that might already exist at
the required share name. This message is accompanied by other messages providing
point.
ADVM-02123: creating administrative network share for mount point string at
point.
ADVM-02124: could not create administrative network share for mount point string
4-14 Error Messages
ADVM-02125: volume 'string' is already in use

Action: Verify the volume specified.
ADVM-02126: Volume string cannot be mounted.
Cause: The volume mount failed. This message is accompanied by other messages
Action: Correct the problem indicated by the other messages and retry the mount
command.
ADVM-02127: unable to transfer mount data to the ACFS driver
Cause: The mount failed because the transfer of mount data from the mount
command to the ACFS driver failed. This message is accompanied by other messages
Action: Correct the problem identified by the other messages. If the cause is unclear,
ADVM-02128: unable to clean up mount data passed to ACFS driver
Cause: The operation to clean up mount data from a temporary location / failed.
Action: None. This state will not have any repercussions and it will be remedied
automatically during the next restart.
ADVM-02129: Volume string cannot be mounted. Volume is out of space.
Cause: The volume mount failed because the volume was out of space.
Action: Correct the problem by resizing the ADVM volume and then retry the mount
command.
ADVM-02130: Volume string cannot be mounted. Volume version does not match
the ACFS driver version.
Cause: The volume mount failed because the loaded ACFS driver does not support
the volume version.
Action: Use 'acfsdriverstate' command to determine the state of the ACFS driver and
address any issues that are reported. Retry the mount command after the installed
driver has been verified.
ADVM-02131: Volume string cannot be mounted. Cluster membership is not
established.
Cause: The volume mount failed because the ACFS driver could not communicate
with Oracle Clusterware.
Action: Verify the online state of Oracle Clusterware using command 'crsctl check
CRS' and address any issues that are reported. Retry the mount command once
Oracle Clusterware is fully operational.
ADVM-02132: Volume string cannot be mounted. Insufficient kernel resources to
complete the mount.
Cause: The volume mount failed due to insufficient kernel resources.
Action: Reduce the load activity on the system and retry the mount command.
ADVM-00501 to ADVM-11111 4-15
ADVM-02133: Volume string cannot be mounted. Metadata inconsistency found

on-disk.
Cause: The volume mount failed due to a metadata inconsistency found in the
volume superblock.
Action: Run command 'fsck -t acfs' as soon as possible to fix the metadata
inconsistency and then retry the mount command.
ADVM-03001: Failed to open string. Verify that string exists.
Cause: The mount point or file could not be opened.
Action: Verify the mount point or file is accessible before retrying.
ADVM-03003: Cannot decrease the volume by this amount.
Cause: Requested size exceeded the size of the file system.
Action: Select a size that is smaller than the size of the file system and retry.
ADVM-03004: Cannot reduce volume size below 200 MB.
Cause: Requested size was below the minimum volume size of 200MB."
Action: Select a volume that is 200MB or larger."
ADVM-03008: The volume could not be resized. The volume expansion limit has
been reached.
Cause: The file system's internal storage bitmap has a five extent limit. Growing the
file system may fail if it has already been grown four or more times, using up all
available storage bitmap extents.
Action: If the file system has been grown four or more times, running the ACFS Fixer
may allow future volume expansions.
ADVM-03013: unable to open string
Cause: Volume could not be opened to remove the file system.
Action: Verify the volume is not mounted on any node in the cluster before retrying.
ADVM-03033: unable to open string
Cause: The log file specified could not be created and/or opened.
Action: If a file exists by the same name as the log file specified, verify that this is a
file that can be overwritten.
ADVM-03044: Failed to open mount point string. Verify the mount point exists.
Cause: Mount point could not be opened for snapshot operation.
Action: Verify the mount point exists and is accessible before retrying the snap
command.
ADVM-03052: unable to delete snapshot string due to open files
Cause: There are files open in the snapshot.
Action: Use lsof or similar tool to find the processes with open files. No files can be
open in the snapshot for the snapshot delete operation to succeed.
ADVM-03054: snapshot string is not a valid snapshot name
Cause: Possible causes include: 1) The snapshot name exceeded the limit of 255
characters. 2) The snapshot name equaled "." or "..". 3) The snapshot name contained
"/" (Unix or Linux). 4) The snapshot name contained "" or ":" (Windows). 5) The
snapshot name contained an illegal character for NTFS file names (Windows).
4-16 Error Messages
Action: Verify that the snapshot name meets the criteria listed in the cause statement.
ADVM-03091: Failed to open string. This may mean the string driver is not loaded/
running
Cause: The driver's control device could not be accessed.
Action: Verify the driver is loaded and running.
ADVM-03096: error opening configuration file string
Cause: The configuration file cannot be created and/or opened.
Action: If the configuration file exists, verify the file can be opened.
ADVM-03097: error accessing configuration file string
Cause: Seek to the end of the configuration file failed.
Action: If the configuration file exists, verify the file is accessible.
ADVM-03106: Invalid combination of arguments. stringa was previously specified
to add an ACFS mount point to Oracle Registry.
ADVM-03107: Invalid combination of arguments. stringd was previously specified
to remove an ACFS mount point from the Oracle Registry.
ADVM-03108: Neither string nor string is an ADVM volume.
Cause: Volume specified was not an ADVM volume.
Action: Retry the command with an ADVM volume.
ADVM-03110: unable to access the Oracle Registry string
Action: Run ocrcheck to verify the Oracle Registry is working properly. Analyze the
appended Oracle Registry service error message.
Cause: A request for process virtual memory by acfsutil registry failed This message
is accompanied by other message(s) providing details on the error.
ADVM-03115: an error occurred while attempting to disconnect from Oracle
Registry
ADVM-03117: unable to verify if the hostnames provided are part of the cluster
ADVM-00501 to ADVM-11111 4-17
ADVM-03118: cannot obtain the node number of host string via CSS or the Oracle
Registry
Cause: Could not determine the node number for the specified host.
Action: Verify that the specified host is a member of this cluster.
ADVM-03119: Incorrect data format in file 'number'.
Cause: The file data was not in the expected format.
ADVM-03120: Note: Reported snapshot space usage is inaccurate.
Cause: The snapshot storage calculated was not expected.
Action: No action is required. To get a more accurate count, dismount the file system
on all nodes and run fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ADVM-03122: failed to create Oracle Registry ACFS key string string
Cause: Failed to create ACFS key(s) SYSTEM.ACFS and/or SYSTEM.ACFS.Mounts in
the Oracle Registry.
Action: Run ocrcheck to verify the Oracle Registry service is working properly. Verify
acfsutil is executed with operating system administrator privileges.
ADVM-03123: failed to create Oracle Registry ACFS key string because it already
exists
Cause: The Oracle Registry ACFS key already exists.
Action: Run ocrcheck to verify the Oracle Registry service is working properly.
ADVM-03124: failed to create Oracle Registry ACFS subkey because it already
exists
Cause: The Oracle Registry mounts subkey already exists.
ACFS mount entry is in an inconsistent state delete it, then re-add it using acfsutil
with the registry option. If the problem persists, contact Oracle Support Services.
ADVM-03125: error retrieving the volume using Oracle Registry key: string
Cause: Could not retrieve volume information from mount entry in the Oracle
Registry.
ADVM-03126: error retrieving the mount point using Oracle Registry key: string
Cause: Could not retrieve mount point information from mount entry in the Oracle
Registry.
ADVM-03127: error retrieving the mount options using Oracle Registry key: string
Cause: Could not retrieve mount options from mount entry in the Oracle Registry.
ADVM-03128: error retrieving the version using Oracle Registry key: string
Cause: Could not retrieve the version for mount entry in the Oracle Registry.
4-18 Error Messages
ADVM-03129: error retrieving the nodes list using Oracle Registry key: string
Cause: Could not retrieve the nodes list for mount entry in the Oracle Registry.
to access the security attributes of key string: \n string
Cause: Could not access the security information of Oracle Registry. This message is
accompanied by other message(s) from the Registry providing details on the error.
Action: Correct the problem identified by the other message(s). If the cause is unclear,
ADVM-03134: An error occurred while accessing Oracle Registry for a delete
mount point operation. string
Cause: Could not retrieve data from the Oracle Registry. This message is
ADVM-03135: unable to locate mount point string in Cluster Ready Services
Cause: An attempt to access the ACFS mount point failed because the mount point
information could not be retrieved from CRS.
Action: Verify the mount point is registered with CRS using the 'acfsutil registry
device' commands.
ADVM-03136: unable to locate volume string in Cluster Ready Services
Cause: An attempt to access the ASM volume failed because the volume information
could not be retrieved from CRS.
Action: Verify the volume is registered with CRS using the 'acfsutil registry device'
commands.
ADVM-03137: Multiple entries exist for the mount point string. Rerun the
command with the volume name.
Cause: Could not locate unique entry for mount point in the Oracle Registry.
Action: Retry acfsutil registry with volume name.
ADVM-03138: failed to create and set Oracle Registry ACFS mount info key string
Cause: Could not create and set a mount info key in the Oracle Registry.
ADVM-03139: error retrieving the disk group name using Oracle Registry key:
string
Cause: Could not retrieve the disk group name from the mount entry in the Oracle
Registry.
ADVM-03140: error retrieving the volume name using Oracle Registry key: string
Cause: Could not retrieve the volume name from the mount entry in the Oracle
Registry.
ADVM-00501 to ADVM-11111 4-19
ADVM-03141: unable to open device string

Cause: The device could not be opened.
Action: Check the diskgroup is mounted and the specified volume is enabled.
ADVM-03142: Failed to retrieve the diskgroup and volume name for device string.
See the attached error.
Cause: Possible internal error.
Action: Check the attached error. If not serviceable, contact Oracle.
ADVM-03143: The specified mount point does not exist and therefore cannot be
deleted.
Cause: The Oracle Registry has not been configured for ACFS or the specified mount
point does not exist.
Action: Run "acfsutil registry" to list out the available ACFS mount points.
ADVM-03145: unable to remove ACFS volume string from Oracle Registry
Cause: Could not remove volume from Oracle Registry.
Action: Verify the volume exists in the Oracle Registry using the acfsutil registry
command.
ADVM-03146: Warning: The ACFS mount point group ownership cannot be reinitialized in the Oracle Registry. The registry is initialized from the ACFS control
device on first use, and may have changed ownership since then. Current Key
Ownership: string
Cause: An attempt was made to re-initialize the ACFS mount point group ownership
in the Oracle Registry. This may be because the ACFS control device /dev/ofsctl
or /dev/acfsctl has changed owners.
Action: Re-initializing the ACFS mount point group ownership in the Oracle Registry
is not supported.
ADVM-03147: invalid ACFS file identifier provided
Cause: The ACFS file identifier provided by the user had an illegal value.
Action: Re-enter a number other than 0 or -1.
ADVM-03148: ioctl call to obtain pathname associated with file id number failed
Cause: An internal ioctl operation to map from an ACFS file identifier to a pathname
failed. This message is accompanied by other message(s) providing details on the
error.
ADVM-03149: constructed pathname is too large
Cause: The length of the pathname being constructed has exceeded the system limit
of %d characters. This may be due to changes in the file system namespace while the
command is running.
Services.
ADVM-03151: The ACFS file identifier provided is not associated with a user file
or directory.
Cause: The ACFS file identifier, although valid, was not for a user file or directory.
4-20 Error Messages
Action: None. There is no pathname associated with this ACFS file identifier.
ADVM-03152: The ACFS file identifier provided is invalid for the mountpoint
specified.
Cause: The ACFS file identifier was not a valid identifier for the mountpoint
specified.
ADVM-03153: The file system name space has changed and a pathname cannot be
obtained.
Cause: The ACFS file identifier was valid, but could not be used to obtain a full file
pathname.
ADVM-03154: Failed to determine the full pathname. Too many directory levels.
Cause: acfsutil has received information from the operating system that it could not
process fully.
ADVM-03157: unsupported file type for string, not a mount point
Action: The acfsutil info acfs command requires that the input be a mount point.
ADVM-03158: unsupported file type for string, not a mount point or a file
Action: The acfsutil size command requires that the input be a mount point or a file.
ADVM-03161: Device : string : Mount Point : string already exists in the Oracle
Registry
Cause: This entry has already been added to the Oracle Registry.
Action: None
ADVM-03162: Warning: The file system was resized, but an error occurred while
resizing the ADVM volume. File system size now number MB, volume size number
MB.
Cause: An error occurred during ADVM volume resize.
Action: Reissue the resize command.
ADVM-03165: Unable to add the file system on device string to the ACFS registry.
It is currently managed by CRS.
Cause: The file system is currently managed by CRS and a file system cannot be
managed by both CRS and the ACFS registry.
Action: Remove the file system resource from CRS or continue to use CRS to manage
the file system.
ADVM-03166: Unable to add a STOP_DEPENDENCY to the ACFS registry for
device string.
ADVM-00501 to ADVM-11111 4-21
ADVM-03167: Unable to remove the STOP_DEPENDENCY for device string from

the ACFS registry.
ADVM-03168: Internal error: string number
ADVM-03169: Unable to set log file size.
Action: Check the log file to see the reason of failure.
ADVM-03170: Minimum log file size is number.
Action: Log file size has to be bigger than or equal to the minimum size.
ADVM-03171: Insufficient contiguous free ASM Diskgroup space. Check the ASM
alert log.
Cause: ADVM could not resize the volume because ASM did not have enough
contiguous free diskgroup storage.
Action: Increase the free space in the diskgroup. Check the ASM alert log.
ADVM-03172: ADVM is busy with Mirror recovery. Try again later.
Cause: ADVM could not resize the volume because it is recovering the mirrored
volumes.
Action: Try again later. The system console log will contain mirror recovery started
and completed messages. For example: [Oracle ADVM] Mirror recovery for volume
asm/volume-name started. [Oracle ADVM] Mirror recovery for volume asm/
volume-name completed.
ADVM-03173: ADVM or ASM is unable to resize the volume. Check the ASM alert
log.
Cause: ADVM or ASM is unable to resize the volume.
Action: Check the ASM alert log.
11.2.0.3.0 or higher to allow the creation of a read/write snapshot.
ADVM-03177: maximum log file size cannot exceed number MB
Action: Retry the command with a log file size that is smaller than the maximum size.
ADVM-03178: unable to delete snapshot string while cluster is in rolling migration
Cause: The cluster was in rolling migration. Snapshot deletions are not allowed
Action: Complete the rolling migration and then delete the snapshot.
4-22 Error Messages
ADVM-03179: unable to create snapshot 'string' while cluster is in rolling

migration
Cause: The cluster was in rolling migration. Snapshot creations are not allowed
Action: Complete the rolling migration and then create the snapshot.
ADVM-03180: Unable to obtain ASM volume device information for 'string'
Cause: The operation for retrieval of ASM volume device information failed. This
ADVM-03185: Unable to obtain ASM volume extent information for string
Cause: The operation for retrieval of ASM volume extent information failed. This
ADVM-03186: Supplied ACFS file offset value is greater than the file allocation
size of number
Cause: The supplied file offset value in bytes supplied must be smaller than the file
allocation size.
Action: 'acfsutil file info filename' provides the file allocation size. Choose a smaller
value.
ADVM-03187: Extent number (mirror number) is not in use.
Action: None
ADVM-03203: Invalid snap command.
Action: Use a valid 'acfsutil snap' command combination. Valid commands are
'acfsutil snap create', 'acfsutil snap delete', and 'acfsutil snap info'
ADVM-03204: Snapshot 'string' is already read-only.
Cause: A request was made to convert a snapshot to be read-only but the snapshot
was already read-only.
Action: None
ADVM-03205: Snapshot 'string' is already read-write.
Cause: A request was made to convert a snapshot to be read-write but the snapshot
was already read-write.
Action: None
ADVM-03206: The ADVM compatibility attribute for the diskgroup was below the
required version (string) for the 'acfsutil snap convert' command.
supports the 'acfsutil snap convert' command.
ADVM-00501 to ADVM-11111 4-23
ADVM-03207: invalid combination of options

Cause: The 'acfsutil snap convert' command was passed an invalid option
combination which included both the -r and -w options.
Action: Remove either the -r or -w option from the 'acfsutil snap convert' command.
ADVM-03208: The /r option is not supported on this operating system
Cause: The 'acfsutil snap convert /r' option was specified. This functionality requires
a minimum operating system version of Windows Server 2008 R2.
Action: Upgrade operating system to Windows Server 2008 R2 or use the 'acfsutil
snap create' command to create a read-only snapshot.
ADVM-03212: There are too many snapshots for the file system associated with
string. Only number are allowed. Reduce the number of snapshots before
proceeding.
Cause: An attempt to create more than the maximum allowed number of active
snapshots was rejected.
Action: Delete a snapshot before creating a new one.
ADVM-03213: Creation of a snapshot failed due to presence of snapshots that
prevent this functionality.
Cause: A snapshot creation which specified a parent snapshot was not processed
because of compatibility issues with existing snapshots. Possible causes include: 1)
Snapshots of the file system were found that were created before ADVM
compatibility attribute was set to 12.1. 2) Snapshots of the file system were found that
were created after ADVM compatibility was set to 12.1 but while 11.2 snapshots
existed.
Action: Delete all snapshots associated with the file system and retry the command.
compatibility attribute for the disk group is less than 12.1.
12.1 or higher to allow the creation of a snapshot with a parent snapshot.
ADVM-03216: The ADVM compatibility attribute for the diskgroup was below the
required version (string) for unlimited volume expansions.
Cause: A request to resize the ACFS file system failed because the volume expansion
limit was reached. This limit was hit because the ADVM compatibility attribute
associated with the diskgroup was too low.
the COMPATIBLE.ADVM attribute to the specified version.
ADVM-03300: unable to set tag name on file string
ADVM-03301: unable to unset tag name on file string
4-24 Error Messages
ADVM-03302: tag name syntax invalid or length too long

Cause: Tag name contains invalid characters or has too many characters.
Action: Change tag name to use valid characters or shorten the tag name.
ADVM-03303: invalid combination of arguments
Cause: The acfsutil tag info -t or -r arguments work only on file pathnames.
Action: Remove the -t or -r arguments from the ofsutil tag info command.
ADVM-03304: Unable to open mount point string. Verify that the mount point
exists.
Cause: Mount point cannot be opened to display tag name information.
Action: Verify that the mount point exists and is accessible before retrying the tag info
command.
ADVM-03305: unable to retrieve all tag names for string
Cause: Unable to return the full list of tag names.
Action: Verify there is sufficient memory resources available.
ADVM-03306: tag name does not exist in file string
Cause: Cannot unset a tag name on a file that does not exist.
Action: Verify the tag name to unset is correct.
ADVM-03308: The ADVM compatibility attribute for the diskgroup must be set to
version 11.2.0.2.0 to allow the acfsutil repl and tag commands.
or beyond.
ADVM-03309: path name string does not resolve to an ACFS file system
Cause: A path name supplied on an 'acfsutil tag' command did not resolve to an
ACFS file system.
Action: Remove the non-ACFS path name from the 'acfsutil tag' command.
ADVM-03310: amount of change since mount: number MB
Action: None
ADVM-03313: unable to collect ACFS statistics for mount point string
Cause: 'acfsutil info fs -s' was unable to communicate with the ACFS driver.
Action: Verify that the file system is online and that the ADVM/ACFS drivers are
loaded and running.
ADVM-03314: interval cannot exceed number seconds
Cause: Statistics interval exceeded maximum number of seconds per interval.
Action: Select an interval that is less than or equal to 2592000 seconds and retry
"acfsutil info fs -s".
ADVM-03315: count cannot exceed number
Cause: Number of statistics intervals exceeded maximum number allowed.
ADVM-00501 to ADVM-11111 4-25
Action: Select a total count that is less than or equal to 2^63-1 and retry "acfsutil info
fs -s".
ADVM-03316: interval must be a positive integer
Cause: A zero or negative integer was provided.
Action: Provide a positive integer for the statistics interval.
ADVM-03317: unable to set tag on file "string" because its tag name storage is full
Cause: The limit of the file's tag name storage has been reached.
Action: Remove any unused tags on this file and try the command again.
ADVM-03318: unable to set tag name "string" because this name is reserved
Cause: The tag name specified is reserved.
Action: Choose another tag name which is not reserved.
ADVM-03319: Set tag on file: string
Action: None
ADVM-03320: Removing tag(s) on file: string
Action: None
ADVM-03321: The ADVM compatibility attribute for the diskgroup is below the
required version (string) for the 'acfsutil tag' commands.
supports tagging.
ADVM-03322: The ADVM compatibility attribute for the diskgroup is below the
required version (string) for the 'acfsutil repl' commands.
supports replication.
ADVM-03323: stringc option requires the stringt option
Cause: The 'c' option was specified without the 't' option. The 'c' option invokes case
insensitive substring matching on the tag names specified using the 't' option.
Action: To use the 'c' option, add the 't' option to specify a tag.
ADVM-03324: Unable to obtain metric data for string
Cause: An internal ioctl operation to access metric data from ACFS file system failed.
4-26 Error Messages
ADVM-03344: Error, strings option with repetition interval applied to multiple file
systems.
Cause: A request to report file system statistics periodically was rejected because it
applied to multiple file systems. A single file system must be specified explicitly when
supplying the 's' option with a time interval.
Action: Reissue the request specifying a single file system or omitting the repetition
interval.
ADVM-03450: Continue to panic the cluster [y|n] ?
Cause: The 'acfsutil panic' command was issued to panic the cluster.
ADVM-03451: Continue to panic the system [y|n] ?
Cause: The 'acfsutil panic' command was issued to panic the system.
ADVM-03452: failed to move file or directory from string to string
Cause: An attempt to rename a file or directory failed because the target was an
existing, populated directory or the user permissions were insufficient to perform the
operation.
Action: Retry the operation after removing the target files or correcting the
permissions.
ADVM-03500: Unable to access kernel persistent log entries.
Cause: Could not get or set persistent log configuration data.
Action: Make sure that the Oracle kernel drivers are loaded/started (run
'acfsdriverstate loaded'). If loaded/started, make sure that you have root/
administrator privileges.
ADVM-03501: The 'query' option may not be used with any other options.
Cause: Additional options to 'query' were specified on the command line.
Action: Do not use any other options with the 'query' option.
ADVM-03502: The specified maximum log file size is less than number MB or is
greater than number MB.
Cause: An invalid log file size was entered on the command line.
Action: Specify a value equal to or greater than the minimum size and equal to or less
than the maximum size.
ADVM-03503: The specified interval is less than number seconds.
Action: Enter an interval value equal to or greater than the minimum.
ADVM-03504: An invalid high water level value (number percent) was specified.
Cause: The high water level must be greater than the low water level and less than
100 percent.
Action: Enter a valid high water level value.
ADVM-03505: An invalid low water level value (number percent) was specified.
Cause: The low water level must be greater than zero and less than the high water
level.
ADVM-00501 to ADVM-11111 4-27
Action: Enter a valid low water level value.

ADVM-03506: The selected percentage does not generate an even integer.
Changing to number percent.
Cause: The specified percentage of the buffer size generates a remainder.
ADVM-03507: The specified buffer size is less than number KB or is greater than
number KB.
Cause: An invalid buffer size value was entered on the command line."
Action: Enter a value equal to or greater than the minimum or equal to or less than
the maximum size.
ADVM-03508: The specified maximum number of log files is less than number or
greater than number.
Cause: An invalid maximum number of log files was entered on the command line.
Action: Specify a value equal to or greater than the minimum and equal to or less than
the maximum.
ADVM-03509: string is not a Grid infrastructure home.
Cause: An invalid Grid infrastructure home was entered on the command line.
Action: Specify a valid Grid infrastructure home.
ADVM-03510: There are more log files on the system than are being configured.
Removing the oldest files.
Cause: A new, lower, maximum number of allowable OKS persistent log files was
configured and there are currently more log files on the system. Deleting the oldest
files."
ADVM-03511: Deleting string.
Cause: A log file was deleted to satisfy the new configuration.
ADVM-03512: Renaming string to string.
Cause: A log file was renamed to place it in time modified sequential order.
ADVM-03513: The OKS persistent log configuration settings cannot be queried.
Action: Start the log with 'acfsutil plogconfig -d gridhome'.
ADVM-03514: The directory 'string' can not be converted to an absolute path.
Cause: A directory name was specified that could not be converted to an absolute
path. The name was either an invalid relative path or, on Windows, included an
invalid drive letter.
Action: Specify the directory name in the form of an absolute path. On Windows, the
absolute path includes the drive letter.
ADVM-03528: failed to determine Oracle Base
Cause: The operation to retrieve the Oracle Base location failed. This message is
4-28 Error Messages
ADVM-03529: Warning: The 'd' option was specified with an argument, which is
no longer used - argument ignored.
Cause: 'acfsutil plogconfig' now gets the log location internally. The specified log
location was ignored and the command continued using the internally derived
location.
Action: None
ADVM-03530: The 'terminate' option may not be used with any other options.
Cause: Conflicting options were specified on the command line.
Action: Do not use any other options with the 'terminate' option.
ADVM-03539: Base time stamp not found in log file.
Cause: Informational. The likely cause is that the running OKS driver is an older
version that does not support time stamp conversion.
Action: None
ADVM-03540: The specified interval is greater than number seconds.
Action: Enter an interval value equal to or less than the maximum.
ADVM-03541: The symbolic link 'string' to 'string' cannot be created.
Cause: Likely, the link name was a non-empty directory. OKS persistent logging was
started but no symbolic was created to the target directory.
Action: If a symbolic link is desired, delete the link target and its contents and reissue
the command.
ADVM-03542: The specified OKS log directory 'string' is invalid because it is NFS
mounted.
Cause: The specified logging directory was NFS mounted.
Action: Enter a node local location for the OKS log.
ADVM-03543: The OKS persistent log is not active.
Action: Start the log with 'acfsutil plogconfig -d [log_dir]'.
ADVM-03544: Directory 'string' exists as a file.
Cause: An OKS persistent log directory could not be created because it exists as a file.
Action: Either delete the file or choose another directory name.
ADVM-03602: Plug-in is already enabled on 'string'
Cause: An attempt was made to enable the plug-in when it is already enabled.
Action: First disable the plug-in then retry the command.
ADVM-03603: Plug-in is not enabled on 'string'
Cause: A plug-in command was attempt when the plug-in is not enabled.
Action: Enable the plug-in and then retry the command.
ADVM-00501 to ADVM-11111 4-29
ADVM-03604: Unable to perform plug-in operation on 'string'

Cause: The plug-in operation failed. This message is accompanied by other
ADVM-03610: Invalid plug-in metric type: string
Cause: An invalid plug-in metric type was specified.
ADVM-03611: Invalid interval specified.
Cause: An invalid interval was specified.
Action: Enter a valid interval between 1 and 3600 seconds.
ADVM-03612: Unable to retrieve list of plug-in enabled tags.
Cause: ACFS was unable to retrieve the list of tags for which the plug-in is collecting
metrics. This message is accompanied by other message(s) providing details on the
error.
ADVM-03613: Unable to write plug-in config file.
Cause: ACFS was unable to write the plug-in config file to disk.
Services.
ADVM-03614: Plug-in cannot be enabled for more than number tags.
Cause: An attempt was made to enable the plug-in for more than the maximum
allowed number of tags.
Action: Enable plug-in with fewer tags.
ADVM-03615: An error occured when copying the list of tags.
Services.
ADVM-03621: missing plug-in metric type
Cause: No plug-in metric type was specified.
ADVM-03623: unable to modify the ACFS registration for mount point 'string'
Cause: Could not modify the ACFS registration for the specified mount point.
ADVM-03624: unable to modify registration for ACFS volume 'string'
Cause: Could not modify the ACFS registration for the ACFS volume.
4-30 Error Messages
ADVM-03626: invalid combination of -C and -f options

Cause: The 'acfsutil log' command was issued with both the -f and -C options. This is
a conflict, because the log file names are pre-specified for -C and may not be specified
using -f.
Action: Re-issue the 'acfsutil log' command with only the desired option. With -C, the
log files will be generated in the persistent log directory in the form
yymmddhhmmss.log. With -f the specified name will be used.
ADVM-03627: logging behavior change specified with cluster option
Cause: The 'acfsutil log' command was issued with both the -C option and and an
option that modifies the logging behavior.
Action: Re-issue the 'acfsutil log' command without the -C option to modify the ACFS
logging behavior. To create logs on all cluster nodes, issue 'acfsutil log -C' with no
other options.
ADVM-04001: Failed to open path string. Verify that string exists.
Cause: Path could not be opened.
Action: Verify the path is accessible before retrying.
Cause: A request for process virtual memory by acfsdismount command failed. This
ADVM-04011: Failed to open volume string. Verify that string exists.
Cause: Volume could not be opened.
ADVM-04013: acfsdismount /all operation did not complete. Unable to retrieve a
mount point from the list of active ACFS file systems to dismount. It is possible
that not all file systems were dismounted.
Cause: Failed to obtain the next file system to dismount.
Action: Use acfsmountvol to determine if there are any file systems still mounted and
reissue 'acfsdismount /all' if necessary.
ADVM-04032: removing administrative network share for mount point string at
share name 'string'
Action: None
ADVM-04033: administrative network share 'string' does not share mount point
string as expected
Cause: Attempted to remove the administrative network share associated with the
specified ACFS mount point, but the network share does not share the specified ACFS
mount point as expected.
Action: Examine the network share at the specified share name. If the network share
shares an unmounted ACFS file system, manually remove the network share using
'net share share name /delete'
ADVM-00501 to ADVM-11111 4-31
ADVM-04034: administrative network share for mount point string does not exist
Action: None
ADVM-04035: retrieving information for administrative network share 'string'
failed
Cause: While removing the administrative network share associated with the
specified ACFS mount point, failed to retrieve information on the administrative
network share. This message is accompanied by other messages providing details on
the error.
Action: Check for a network share at the specified share name. If a network share
exists at the specified share name and it shares an unmounted ACFS file system,
manually remove the network share using 'net share share name /delete'
ADVM-04036: removing administrative network share for mount point string at
Action: Manually remove the administrative network share at the specified share
name using 'net share share name /delete'
ADVM-04037: could not remove administrative network share for mount point
string at share name 'string'
ADVM-04038: Volume string is still mounted. Dismount will complete as soon as
activity ceases on the file system.
Cause: At the conclusion of the file system dismount request, the file system was still
mounted. This could be a result of open files on the mount point. The dismount will
finish as soon as activity ceases on the file system.
Action: To force dismount to complete, terminate any processes or applications that
are using the file system.
ADVM-04058: Ignoring unsupported ACFS command option: 'string'
Cause: An unsupported 'umount.acfs' command option was specified.
Action: No action required. The unmount will proceed without the option.
ADVM-04150: unable to retrieve mount point information from the ACFS driver
Cause: During unmount processing, an attempt to retrieve mount point information
from the ACFS driver failed.
Action: Verify the mount point is a valid ACFS file system before retrying the
unmount command. If the problem persists, contact Oracle Support Services.
ADVM-04151: unmount of mount point string failed
Cause: The file system unmount failed. This message is accompanied by other
4-32 Error Messages
ADVM-05001: must specify 'primary' or 'standby'
Cause: Command syntax requires 'primary' or 'standby' argument.
Action: At command line, indicate primary or standby for replication command.
ADVM-05002: must provide an Oracle Net alias to the primary replication site
Cause: The Oracle Net alias to connect to the primary replication site was not
specified.
Action: Provide Oracle Net alias to connect to the primary replication site.
ADVM-05003: must provide a primary mount point
Cause: The mount point on the replication primary site for the file system to be
replicated was not provided.
Action: Provide an existing mount point on the primary site for the file system to be
replicated.
ADVM-05004: cannot allocate a list of tag names
ADVM-05005: invalid tag name: string
Cause: User specified a tag name that has incorrect syntax.
Action: See the platform specific Oracle documentation for correct syntax for ACFS
tag names.
ADVM-05006: unable to initialize replication process data structures
Cause: Failed to determine path names for replication directories.
Action: Verify the specified mount point is an ACFS file system.
ADVM-05007: cannot initialize interrupt signal handler
Cause: The system could not initialize the mechanism to handle interrupts.
ADVM-05008: cannot lock file string to serialize ACFS replication commands
Cause: Failed to open and lock the specified file. This message accompanied by other
ADVM-05009: ACFS replication initialization is already in progress.
Cause: Initialization was in progress on the replication site.
Action: Wait for the other initialization on replication site to complete.
ADVM-05010: ACFS replication initialization is still in progress.
Cause: The command cannot be run until replication initialization completes.
Action: Monitor initialization progress with the 'acfsutil repl info' command.
ADVM-00501 to ADVM-11111 4-33
ADVM-05011: cannot open directory: string

Cause: Failed to open the specified directory. This message is accompanied by other
ADVM-05012: ACFS replication is already initialized.
Cause: ACFS replication has already been initialized on this system.
Action: Initialization cannot be undone unless replication is terminated or the file
system is reformatted.
ADVM-05013: ACFS replication cannot be initialized.
error.
ADVM-05014: cannot verify replication configuration
error.
ADVM-05015: cannot cleanup replication directories
Cause: The application failed to cleanup from a previous replication instantiation.
Action: Verify user permissions and that the replication directory is available.
ADVM-05016: cannot update replication configuration with new trace level
ADVM-05017: cannot create file: string
Cause: The application failed to create the specified file. This message is accompanied
ADVM-05018: cannot get primary ADVM volume information for string
Cause: The application failed to get the ADVM volume path for the mounted ACFS
file system.
Action: Verify that the file system is mounted and of type ACFS.
ADVM-05019: cannot allocate space for the ADVM volume path
ADVM-05020: cannot start replication daemons
Cause: CRS has failed to start the replication daemons.
4-34 Error Messages
ADVM-05021: cannot stop replication daemons
Cause: CRS has failed to stop the replication daemons.
replication daemons failed to stop.
ADVM-05022: internal CRS error
Cause: The application failed to initialize communication with CRS.
ADVM-05023: error checking for file: string
Action: None
ADVM-05024: The standby replication site is initialized. ACFS replication will
begin.
Action: None
ADVM-05025: waiting for the standby replication site to initialize
Action: None
ADVM-05026: caught interrupt; ACFS replication initialization is shutting down.
Action: None
ADVM-05027: cannot remove file: string
ADVM-05028: cannot obtain current time for events log
Cause: The application failed to get the current time for logging.
ADVM-05029: cannot write to the events log
ADVM-05030: cannot clean up configuration file
Cause: Initialization failed and the configuration file created during failed
initialization could not be removed.
ADVM-00501 to ADVM-11111 4-35
ADVM-05031: standby file system is not empty

Cause: The file system was not empty.
Action: Use an empty standby file system; either reformat the file system or remove
all files and directories under standby mount point/.
ADVM-05032: unable to determine user permissions
Cause: An error occurred attempting to acquire the user permissions. This message is
Action: Correct the problem indicated by the other message(s). Otherwise, report this
error to Oracle Support Services.
ADVM-05033: must provide a standby mount point
Cause: A mount point on the standby replication site was not provided.
Action: Provide an existing mount point with an empty file system on the standby
replication site.
ADVM-05034: cannot obtain path for directory: string
Cause: The application failed to locate the specified directory.
ADVM-05035: cannot open file for write: string
Cause: The application failed to open the specified file. This message is accompanied
ADVM-05036: cannot write to file: string
ADVM-05037: cannot move file string to directory string
Cause: The application failed move the specified file.
ADVM-05038: cannot register Oracle Net service name
Cause: Unable to register the Oracle Net service name with the ASM instance.
ADVM-05039: cannot unregister Oracle Net service name
Cause: Unable to unregister the Oracle Net service name from the ASM instance.
ADVM-05040: cannot obtain Oracle Net service name from alias provided
Cause: Unable obtain the Oracle Net service name from the Oracle Net alias provided
on the command line.
Action: Verify that the Oracle Net alias exists and is properly formed.
4-36 Error Messages
ADVM-05041: Oracle Net service name is greater than string bytes

Cause: The Oracle Net service name specified for replication is greater than the
maximum allowed.
Action: Reduce the size of the Oracle Net service name being used for replication.
ADVM-05042: insufficient privileges to perform replication command.
Administrator access is required.
command.
Action: Execute the replication command from a user with administrator access.
ADVM-05043: insufficient privileges to perform replication command. ASM
administrator group access is required.
command.
Action: Execute the replication command from a user with ASM administrator group
access.
ADVM-05044: cannot obtain node name
Cause: Unable to get local node name through CRS.
Action: Verify that CRS is running.
ADVM-05045: invalid interval specified for replication statistics
Cause: The caller specified an invalid time interval for replication statistics.
Action: Verify the syntax of the time interval using 'acfsutil repl info' help flag and
retry.
ADVM-05046: invalid date range specified for replication statistics
Cause: The caller specified an invalid date range for replication statistics.
Action: Verify the syntax of the date range using 'acfsutil repl info' help flag and retry.
ADVM-05047: time specified is in the future
Cause: The caller specified a date in the future.
Action: Verify the time specified is before the current time.
ADVM-05048: start time specified is newer than the end time specified
Cause: The caller specified a date range where the start time was more recent the end
time.
Action: Verify the start time is before the end time.
ADVM-05049: validating the remote connection
Action: None
ADVM-05050: remote connection cannot be established
Cause: The user name, password, or Oracle Net alias used to connect to the remote
site was not correct or the remote site was unreachable.
Action: Verify the connection information is correct and the status of the remote site.
ADVM-05051: remote connection has been established
ADVM-00501 to ADVM-11111 4-37
Action: None
ADVM-05052: standby replication site requires reinitialization
Cause: Initialization was unable to complete on the primary replication site and left
the standby replication site in an indeterminate state.
Action: On the standby replication site, run 'acfsutil repl terminate' and 'acfsutil repl
init' before retrying initialization on the the primary replication site.
ADVM-05053: replication's Oracle Net service name conflicts with the existing
ASM service name
Cause: The service name for replication specified in the Oracle Net alias conflicts eith
the Oracle Net service name that ASM uses.
Action: Review the Oracle Net alias for replication in tnsnames.ora and use a different
service name for the replication alias.
ADVM-05054: standby replication file system is mounted on more than one cluster
node
Cause: The standby replication file system was mounted on more than one node in
the cluster.
Action: Unmount the file system on all but one node on the standby replication site
and retry the initialization.
ADVM-05055: invalid connection string for the primary replication site
Cause: The user name, password, or Oracle Net alias used to connect to the primary
Action: Verify the connection information is correct and the status of the primary
replication site.
ADVM-05056: invalid connection string for the standby replication site
Cause: The user name, password, or Oracle Net alias used to connect to the standby
Action: Verify the connection information is correct and the status of the standby
replication site.
ADVM-05058: command issued on the incorrect replication site
Cause: The command was issued on the incorrect replication site.
Action: Verify the command syntax. If issued on the primary file system, reissue on
the standby file system. If issued on the standby file system, reissue on the primary
file system.
ADVM-05059: ACFS replication not initialized
Cause: ACFS replication information cannot be retrieved as replication has not been
initialized.
Action: None
ADVM-05060: waiting for ACFS replication to terminate
Action: None
ADVM-05061: ACFS replication command interrupted
Action: None
4-38 Error Messages
ADVM-05062: cannot query CRS resource

ADVM-05063: cannot relocate CRS resource
Cause: The application failed to relocate CRS resource.
resource cannot be relocated.
ADVM-05064: the service name 'string' is not registered on the standby site
Cause: Possible causes include: 1.) Replication was not initialized on the standby site.
2.) Mismatched service names. If the -c option is not used, the service name specified
in the alias for the standby file system did not match the service name specified for
the primary file system in the alias on the standby site. 3.) The alias for the standby
site referred to the wrong set of nodes.
Action: Possible actions include: 1.) Verify replication is initialized on the standby
site. 2.) Verify the service name used to connect to the standby site matches the one
registered on the standby site. Run 'lsnrctl status' on the standby site to verify. 3.)
Verify that the nodes listed in the standby alias have the standby file system
mounted.
ADVM-05065: cannot transfer files to the standby file system 'string'
Cause: Possible causes include: 1.) The standby mount point did not exist or was not
an ACFS file system. 2.) The standby file system was full.
Action: Possible actions include: 1.) Verify that the standby mount point exists and is
an ACFS file system. 2.) Verify that there is free space on the standby file system.
ADVM-05066: ACFS replication is already paused
Cause: ACFS replication was paused by a previous call.
Action: None
ADVM-05067: cannot rename file string to string in directory string
Cause: The application failed to rename the specified file.
ADVM-05068: ACFS replication has not been paused
Cause: ACFS replication was not paused. Resume operation is not needed.
Action: None
ADVM-05069: ACFS replication update must specify at least one attribute
Cause: The command to update the replication configuration did not specify any
attributes to update.
Action: Specify at least one replication attribute to be updated.
ADVM-05070: command must be run on the primary replication site
Cause: 'acfsutil repl update' command was not run on the primary replication site.
Action: Execute 'acfsutil repl update' on the primary replication site.
ADVM-00501 to ADVM-11111 4-39
ADVM-05071: invalid username or password used to connect to the standby site

Cause: The username or password specified on the command line or in the wallet was
incorrect.
Action: Verify the username and password are correct when connecting to the
standby site.
ADVM-05072: cannot open events file string
Cause: Failed to open events log file.
ADVM-05073: cannot query events log file
Cause: Failed to query events log file.
ADVM-05075: cannot terminate replication
Cause: Failed to terminate replication.
ADVM-05076: unable to determine CRS user/group
Cause: The application failed to determine CRS user and/or group.
user and/or group cannot be determined.
ADVM-05077: could not complete replication synchronization
Cause: Failed to complete synchronization of primary and standby replication sites.
ADVM-05078: failed to synchronize primary and standby replication sites
Cause: Failed to synchronize replication sites.
ADVM-05079: waiting for replication update to complete
Action: None
ADVM-05083: Initialization of the primary file system could not complete because
the standby is already configured for replication.
Cause: The standby file system was not expecting initialization data from this
primary. Possible causes include: 1. Stale replication state detected on standby file
system from a previous instantiation. 2. An incorrect replication standby site was
supplied. 3. An incorrect replication standby file system was supplied.
Action: 1. Run 'acfsutil repl terminate' on the standby site for the standby file system
before retrying the initialization of the primary. 2. Verify the correct standby site is
used. 3. Verify the correct standby file system is used.
4-40 Error Messages
ADVM-05084: The replication standby file system has been newly initialized and
is refusing files from the primary. The primary may need to be terminated and
newly initialized.
Cause: The standby file system was not expecting any data from the primary except
initialization data. A possible cause may be the standby file system was terminated
and newly initialized, but the primary was not.
Action: Verify the primary site and primary file system. Run 'acfsutil repl terminate'
on the primary site for the primary file system before retrying the initialization of the
standby.
ADVM-05085: cannot start replication because incompatible ACFS features already
exist
Cause: Failed to start replication: Either security or encryption or both is enabled on
the file system.
Action: Undo security or encryption or both, then try to initialize replication again. To
undo encryption and security respectively: acfsutil encr set -m mount-point -u acfsutil
sec prepare -m mount-point -u
ADVM-05086: listener is not running on the standby site
Cause: The listener was not started on the remote site or an incorrect node name was
specified in the standby alias definition.
Action: Verify the listener is started on the standby site. Check that the standby alias
contains the correct node names.
ADVM-05087: The event log does not cover the time range specifed.
Cause: The events log did not cover any portion of the time range specified in the
command.
Action: Change the time range or use an events log that covers the range specified.
ADVM-05088: replicated file system size is below the minimum of stringG
Action: Resize the file system to at least the minimum size specified.
ADVM-05089: replication statistics cannot be queried on the standby site
Cause: An attempt was made to query the replication statistics on the standby site.
Action: Query the replication statistics from the primary site.
ADVM-05090: interval is greater than string years
Cause: The interval specified was greater than the maximum allowed.
Action: Retry the command with a lower interval value.
ADVM-05091: The mount path specified exceeds the maximum length allowed on
this platform.
Cause: The specified mount path exceeded the maximum length on this platform.
Action: Use a valid mount path.
ADVM-05092: replicated file system free space is near the minimum threshold of
stringGB per active node, continuing with initialization
Cause: Initialization of replication was issued on a file system that is near the
minimum threshold of free space.
ADVM-00501 to ADVM-11111 4-41
Action: Consider resizing the file system to allow for optimal replication performance.
ADVM-05093: could not retrieve active node count on file system: string, error:
string
Cause: Could not get the number of nodes active on the specified file system.
Action: Verify at least one cluster node has the file system mounted, or address the
specified operating system dependent error code provided. If the solution is not clear,
ADVM-05094: replicated file system free space is below the minimum of stringGB
per active node, actual free space left: stringGB
Action: Resize the file system such that free space is at least the minimum size
specified.
ADVM-05159: Last sync time with primary: string
Action: None
ADVM-05170: Cannot initialize replication while the cluster is in rolling migration
Cause: An attempt to initialize replication was rejected because the cluster was in
rolling migration. Replication initialization is not allowed during rolling migration.
Action: Complete the rolling migration and then initialize replication.
ADVM-05171: Cannot terminate replication while the cluster is in rolling migration
Cause: An attempt to terminate replication was rejected because the cluster was in
rolling migration and the file system was mounted on more than one node.
Action: Either complete the rolling migration and then terminate replication, or
unmount this file system on the other nodes and then terminate replication.
ADVM-05172: Replication cannot be terminated because background processes are
not running.
Cause: Replication background processes were stopped and cannot finish processing
replication data.
Action: Run 'acfsutil repl bg start mountpoint' to restart replication background
processes and complete the apply of existing replication data, or run 'acfsutil repl
terminate standby immediate mountpoint' to terminate replication immediately
without applying the remaining replication data.
ADVM-05200: Stopping ACFS replication daemons on string
Action: None
ADVM-05201: Starting ACFS replication daemons on string
Action: None
ADVM-05202: ACFS replication daemons started successfully on string
Action: None
4-42 Error Messages
ADVM-05203: ACFS replication daemons stopped successfully on string

Action: None
ADVM-05204: Attempting to restart replication daemons on string
Action: None
ADVM-05205: Failed to initialize replication because ACFS Security is in use on
Security was in use on the file system.
the standby file system and retry the command.
ADVM-05206: Failed to initialize replication on ACFS Security enabled file system
Cause: Replication initialization failed on ACFS Security enabled primary file system
the below mentioned steps in sequence: a. Terminate replication on standby file
system by executing 'acfsutil repl terminate' command. b. Remove ACFS Security on
primary file system by using 'acfsutil sec prepare' command. c. Reinitialize replication
on standby file system by executing 'acfsutil repl init' command. d. Retry 'acfsutil repl
ADVM-05207: A request to initialize replication failed because the primary
replication file system is enabled for ACFS Security and standby site is not
initialized for ACFS Security.
Cause: A request to initialize replication failed because the primary replication file
system was enabled for ACFS Security and standby site was not initialized for ACFS
Security.
below mentioned steps in sequence: a. Terminate replication on standby file system
by executing 'acfsutil repl terminate' command. b. Remove ACFS Security on primary
file system by using 'acfsutil sec prepare' command. c. Reinitialize replication on
standby file system by executing 'acfsutil repl init' command. d. Retry 'acfsutil repl
ADVM-00501 to ADVM-11111 4-43

replication file system is enabled for ACFS Encryption and standby site has PKCS
wallet.
replication file system is enabled for ACFS Encryption and an error occurred in
accessing OCR at standby site.
ADVM-05210: Failed to initialize replication because ACFS Encryption is in use on
Encryption was in use on the file system.
the standby file system to remove encryption and retry the command.
ADVM-05211: Failed to initialize replication on ACFS Encryption enabled file
system 'string' because PKCS wallet existed on standby site.
ADVM-05212: Failed to initialize replication on ACFS Encryption enabled file
system 'string' because an error occurred in accessing the OCR at standby site.
4-44 Error Messages
ADVM-05214: Failed to prepare ACFS Security on replication enabled file system

Cause: An attempt to prepare ACFS Security on replication enabled file system failed
Action: Initialize ACFS Security on the standby site by executing the 'acfsutil sec init'
ADVM-05216: Failed to set ACFS encryption on a replication enabled file system
'string' because PKCS wallet is not supported as ACFS encryption key store on
standby site.
Cause: An attempt to set ACFS encryption on replication enabled file system failed
because the standby site was having a PKCS wallet as ACFS encryption key store.
Action: If ACFS encryption is desired on primary and standby file systems follow the
steps mentioned below in sequence: a. Convert the PKCS wallet to SSO wallet on
standby site by executing the 'acfsutil keystore migrate' command. b. Retry the
'acfsutil encr set' command.
ADVM-05217: Failed to set ACFS Encryption on replication enabled file system
ADVM-05218: Cannot proceed because another conflicting 'acfsutil' command is in
progress.
Cause: The command could not proceed because one of the following 'acfsutil'
commands was in progress in the cluster. a. 'acfsutil repl init' b. 'acfsutil sec prepare'
c. 'acfsutil encr set' d. 'acfsutil audit enable'
ADVM-05219: Cannot proceed because CRS stack is not up.
Cause: The command could not proceed because CRS stack was not up.
Action: Verify that Cluster Ready Services (CRS) stack is up by executing 'crsctl check
crs' and Cluster Synchronization Services (CSS) is running by executing 'crsctl check
css'. If the CRS stack is not up or the CSS is not running, check with the CRS
administrator to bring it up. If it does not resolve the problem, contact Oracle Support
Services.
ADVM-05220: Cannot proceed because ACFS replication initialization is in
progress.
Cause: The command could not proceed because ACFS replication initialization was
in progress.
Action: Verify that the ACFS replication initialization is complete by executing
'acfsutil repl info' and retry.
ADVM-05221: Failed to prepare ACFS Security on a replication enabled file system
Cause: An attempt to prepare ACFS Security on a replication enabled file system
failed because ACFS Audit was not initialized on the standby site.
ADVM-00501 to ADVM-11111 4-45
ADVM-05222: Failed to initialize replication on ACFS Audit prepared filesystem

string because ACFS Audit is not initialized on the standby site.
Cause: Replication initialization failed on an ACFS Audit prepared primary file
system because ACFS Audit was not initialized on the standby site.
Action: If ACFS Audit is desired on primary and the standby file systems, follow the
steps mentioned below in sequence: a. Terminate replication on the standby file
system by executing 'acfsutil repl terminate' command. b. Initialize ACFS Audit on
the standby site by executing 'acfsutil audit init' command. c. Reinitialize replication
on the standby file system by executing 'acfsutil repl init' command. d. Retry 'acfsutil
repl init' command on the primary file system.
ADVM-05223: Failed to prepare ACFS Audit on replication enabled file system
Cause: An attempt to prepare ACFS Audit on a replication enabled file system failed
ADVM-05224: Failed to prepare ACFS Audit on replication enabled file system
ADVM-05226: Failed to set ACFS Encryption on a replication enabled file system
'string' because ACFS audit is not initialized on the standby site; moreover, PKCS
wallet is not supported as ACFS Encryption key store on the standby site.
Cause: In ACFS Audit initialized cluster, an attempt to set ACFS Encryption on
replication enabled filesystem failed because standby site is not ACFS audit initailized
and PKCS wallet is not supported as ACFS Encryption key store on the standby site.
standby site by executing 'acfsutil audit init' command. b. Convert the PKCS wallet to
SSO wallet on standby by executing 'acfsutil keystore migrate' command. c. Retry
command 'acfsutil repl init' on the primary site.
ADVM-05227: Failed to set ACFS Security on a replication enabled file system
'string' because ACFS Security is not initialized on the standby site; moreover,
ACFS Audit is not initialized on standby site.
Cause: In an ACFS Audit initialized cluster, an attempt to prepare ACFS Security on a
replication enabled filesystem failed because the standby site was neither Audit
initialized nor Security initialized.
standby site by executing 'acfsutil audit init' command. b. Initialize ACFS Security on
the standby site by executing 'acfsutil sec init' command. c. Retry command 'acfsutil
repl init' on the primary site.
ADVM-05228: Failed to set ACFS Encryption on a replication enabled file system
Cause: An attempt to set ACFS Encryption on a replication enabled file system failed
4-46 Error Messages
ADVM-05229: Failed to prepare ACFS Security on replication enabled file system

'string' because an error occurred accessing the OCR at the standby site.
ADVM-05230: Failed to get standby site's encryption state.
Cause: An attempt to get standby site's encryption status failed because standby site
was unreachable.
ADVM-05231: Failed to get standby site's security state.
Cause: An attempt to get standby site's security status failed because standby site was
unreachable.
ADVM-05232: Failed to get standby site's audit state.
Cause: An attempt to get standby site's audit status failed because standby site was
unreachable.
ADVM-05233: Cannot prepare a file system for ACFS Security while the cluster is
in rolling migration.
Cause: An attempt to prepare a file system for ACFS Security was rejected because
the cluster was in rolling migration. ACFS Security prepare operation is not allowed
ADVM-05234: Cannot set ACFS Encryption parameters while the cluster is in
rolling migration.
Cause: An attempt to set ACFS Encryption parameters was rejected because the
cluster was in rolling migration. ACFS Encryption set operation is not allowed during
rolling migration.
ADVM-05235: Cannot enable ACFS Audit while the cluster is in rolling migration.
Cause: An attempt to enable ACFS Audit was rejected because the cluster was in
rolling migration. ACFS Audit enable operation is not allowed during rolling
migration.
ADVM-05354: Clock difference detected between primary and standby replication
sites.
Cause: A difference in the system clocks has been detected between the primary and
standby replication sites.
Action: Update the time on the primary and standby replication sites to match, and
reissue the 'acfsutil repl info -s' command with a new time interval.
ADVM-05356: The Oracle Local Registry, OLR, cannot be accessed to query the
software version.
Cause: The OLR is not accessible or is not configured correctly.
Action: Run 'ocrcheck -local' to verify the OLR is accessible and working properly.
ADVM-00501 to ADVM-11111 4-47
ADVM-05500: ACFS replication error. Contact Oracle Support Services. string

Cause: An ACFS replication operation failed.
ADVM-05501: ACFS replication error. Customer action required. string
error.
Action: Correct the problem indicated by the other message(s) immediately. If the
ADVM-05502: ACFS replication error. System administration needed. string
error.
Action: The replication daemon(s) will try to correct this situation by moving to
another node in the cluster, if available. The problem indicated by the other
message(s) should be addressed as soon as possible for replication to continue
without further error. If the cause of the problem is unclear, contact Oracle Support
Services.
ADVM-05503: ACFS replication string daemon shutting down. string
error.
ADVM-05505: The standby replication file system is full.
Cause: The standby replication file system is out of space.
Action: Resize the standby file system or delete snapshots from the standby file
system if any exist; otherwise, replication may not proceed.
ADVM-05506: The primary replication file system is full.
Cause: The primary replication file system is out of space.
ADVM-05507: The standby replication site failed number times to transport
Cause: The replication transport mechanism failed to transport files from the standby
replication site.
ADVM-05508: The primary replication site failed number times to transport
Cause: The replication transport daemon failed to transfer files from the primary
replication site.
4-48 Error Messages
ADVM-05511: The standby replication site host, string, is experiencing number I/O
errors.
Cause: I/O on the standby replication site failed.
ADVM-05512: The primary replication site host, string, has experienced number I/O
errors.
Cause: I/O on the primary replication site failed.
ADVM-05513: replication monitor daemon has detected a problem
Cause: An error log file was received.
Action: Check the ACFS alert logs and 'acfsutil repl info' to determine the cause.
ADVM-05514: The replication monitor daemon has not received receipt or error
files within the set threshold.
Cause: The time allowed for receiving receipt or error files has surpassed.
Action: Make sure all replication resources are running using 'acfsutil repl bg info' on
both the primary and standby replication sites.
ADVM-05515: The replication monitor received an invalid receipt file and will not
process it.
Cause: The receipt file that the replication monitor process received is not valid.
Action: Make sure proper permissions are set on the replication directories and that
I/O requests can be processed.
ADVM-05516: The apply daemon failed to regenerate an apply file.
Cause: The apply daemon has requested more than the allowed number of
regnerations on an apply file.
Action: Restart the file system replication resource using 'acfsutil repl bg start'.
ADVM-05517: ACFS replication on string: string
Action: None
ADVM-05518: string is not an ACFS mount point
Cause: The command required an ACFS mount point for execution.
Action: Retry the command using an ACFS mount point.
ADVM-05519: must provide an Oracle Net alias to the standby replication site
Cause: The Oracle Net alias, which is used to connect to the standby replication site,
was not specified.
Action: Provide the Oracle Net alias to connect to the standby replication site.
ADVM-05520: cannot update replication configuration
ADVM-00501 to ADVM-11111 4-49
ADVM-05521: cannot initialize replication configuration

ADVM-05522: Cannot terminate replication. Pending operations are unable to
complete because the replication standby file system is full.
Cause: The standby replication file system is full and replication could not complete
applying data before terminating.
Action: Resize the standby file system, delete snapshots from the standby file system
if any exist, or use 'acfsutil repl terminate immediate' to force a terminate on the
standby without applying any outstanding replication data. Any outstanding
replication data will be lost if 'acfsutil repl terminate immediate' is issued.
05600-05604 reserved for replication exceptions
ADVM-05605: ACFS replication daemon string is exiting due to replication
termination. string
Action: None 05606-05625 reserved for replication exceptions
ADVM-05700: All the tag names specified during the "acfsutil repl init" operation
must exactly match those specified on the command line.
Cause: Either at least one tag name was not specified during replication initialization
or a specified tag name does not match that used during the "acfsutil repl init"
operation.
Action: Use the exact tag names specified during the "acfsutil repl init" operation.
ADVM-05701: Comparing primary mount point (<<<) to standby mount point
(>>>):
Action: None
ADVM-05702: Testing for extra files on standby.\nStandby mount point (<<<) to
primary mount point (>>>):
Action: None
ADVM-05703: Results for file comparison of primary to standby mount points:
Action: None
ADVM-05704: Files successfully compared = number
Action: None
ADVM-05705: Files which failed comparison = number
Action: None
ADVM-05706: Results for extra files on standby test:
Action: None
4-50 Error Messages
ADVM-05707: Total files checked = number

Action: None
ADVM-05708: Extra files found = number
Action: None
ADVM-05709: A status check on a file failed. Skipping file: string
Cause: Either the primary file system is actively being modified or an internal error
occurred.
Action: If possible, ensure the primary file system is not changing while the tool is
running.
ADVM-05710: ACFS tags do not support character devices. Skipping file: string
Action: None
ADVM-05711: ACFS tags do not support block devices. Skipping file: string
Action: None
ADVM-05712: ACFS tags do not support FIFOs. Skipping file: string
Action: None
ADVM-05713: ACFS tags do not support sockets. Skipping file: string
Action: None
ADVM-05714: <<< string\n>>> File missing!
Cause: The specified file was not replicated to the standby file system.
Action: None
ADVM-05715: Found: string
Cause: The specified file is an extra file on the standby file system.
Action: None
ADVM-05716: <<< Tag names exist on file string\n>>> No tag names exist on file
string
Cause: The file on the primary file system has tag names but the file on the standby
file system has no tag names.
Action: Tag names on files can be displayed with the "acfsutil tag info" command.
ADVM-05717: <<< Extended attribute mismatch for string\n>>> Extended
attribute mismatch for string
Action: None
ADVM-00501 to ADVM-11111 4-51
ADVM-05718: An unexpected result occurred during primary to standby

comparison. Continuing. Affected files: string string
Cause: An unexpected result occurred when comparing the primary to the standby.
ADVM-05719: An unexpected result occurred during standby to primary
comparison. Continuing. Affected files: string string
Cause: An unexpected result occurred when comparing the standby to the primary.
ADVM-05720: File type was not recognized. Continuing. Affected files "string" and
"string"
Cause: An unrecognized file type was encountered which will be ignored.
Action: Informational
ADVM-05721: Could not open the file specified for a checksum operation: string
tool.
ADVM-05722: A file read failed during a checksum operation: string
tool.
ADVM-05723: Unable to obtain security attributes on file "string"
Cause: Check the access rights on the indicated file.
Action: Ensure the files security attributes can be read using a file manager.
ADVM-05724: Unable to convert a security descriptor to a string on file "string"
Cause: The Windows security identifier (SID) may not be available on this system.
Action: Check the Windows SID is available on this host.
ADVM-05728: Failed to retrieve file system status information from a system call
for mount point "string."
Cause: A system call for the status of the file system failed.
Action: Ensure the file system is accessible via "acfsutil info fs".
ADVM-05730: Mount point "string" does not support Oracle ACFS tagging.
Cause: The "-a" option was passed on the command line to compare ACFS tags. A file
system being checked did not support ACFS tagging.
Action: Disable ACFS tag name comparison by omitting the "-a" option.
ADVM-05731: Mount point "string" does not support extended attributes, therefore,
the ACFS tag name portion of the comparisons will not be performed.
Action: None
ADVM-05732: The specified standby mount point does not exist: "string" .
Cause: Failed to access the specified standby mount point.
4-52 Error Messages
Action: Use a networked file system to provide access to the standby file system on
the primary node where the 'acfsutil repl compare' will be preformed.
ADVM-05733: Successfully compared: string string
Action: None
ADVM-05734: Successfully verified existence: string string
Action: None
ADVM-05737: string file attribute comparison failed: permissions=string,
links=number, uid=number, gid=number, bytes=number, file: string
Action: None
ADVM-05738: string file size or file contents comparison failed, file: string
Action: None
ADVM-05739: string security descriptor comparison failed, file: string
Action: None
ADVM-05740: string file type comparison failed, file: string
Action: None
ADVM-05741: string file type comparison failed, directory: string
Action: None
ADVM-05742: string file type comparison failed, soft link: string
Action: None
ADVM-05743: string file type comparison failed, socket: string
Action: None
ADVM-05744: string file type comparison failed, character device: string
Action: None
ADVM-05745: string file type comparison failed, block device: string
Action: None
ADVM-05746: string file type comparison failed, FIFO: string
Action: None
ADVM-00501 to ADVM-11111 4-53
ADVM-05747: Directory 'string' is a nested ACFS reparse point and was not
included in the file system comparison.
Action: None
ADVM-05748: The 'strings' option requires either the 'stringa' option or 'stringt'
option.
Cause: An incorrect combination of options was specified.
Action: Combine the 's' option with either the 'a' option or 't' option.
ADVM-05749: The specified primary and standby mount points are the same path
and will not be compared.
Cause: The provided primary and standby mount point paths resolved to the same
location.
Action: Rerun the command specifying the unique mount point paths for the primary
file system and the standby file system.
ADVM-05801: The primary replication file system string is at least number%% full.
Cause: Free space in the primary replication file system fell below a monitored
threshold.
ADVM-05802: The primary replication file system string has numberGB or less
space available per active node.
Cause: The primary replication file system was found to be running low on space.
ADVM-05803: The primary replication file system string has 2GB or less space
available per active node. Replication is being terminated.
Cause: The primary replication file system was found to be too low on space in order
to run efficiently.
Action: Restart replication with a larger primary file system that has free space equal
to at least 4GB per active node.
ADVM-05804: The standby replication file system string is out of sync with the
primary by at least number minutes.
Cause: The time period to process changes on the standby file system was exceeded.
ADVM-05805: The standby replication file system string is out of sync with the
primary by at least 60 minutes.
Cause: The standby replication file system finished applying changes from the
primary that were made more than 60 minutes ago. The standby is at least 60 minutes
out of sync with the primary.
4-54 Error Messages
ADVM-05806: The primary replication file system string has reached an

appropriate free space level.
Cause: A previously-reported free space shortage in the primary replication file
system was relieved.
Action: None
ADVM-05807: The standby file system string is less than 15 minutes out of sync
now.
Cause: A previously-reported out of sync time difference between the standby
replication file system and the primary reached an appropriate out of sync time for
replication to run efficiently.
Action: None
ADVM-05808: The primary replication file system string had an unrecoverable
error and replication has been terminated for that file system.
Cause: The primary file system encountered an unrecoverable error in the kernel that
has caused replication for this file system to be terminated. The cause will be in the
OKS persistent log.
Action: Replication must be restarted. To do this, terminate replication on the standby
file system, run mkfs (Unix or Linux) or acfsformat.exe (Windows) on the volume for
the standby file system, remount that volume, and then restart replication for both file
systems.
ADVM-05809: invalid query of replication apply events on the standby site
Cause: An attempt was made to query the replication apply events on the standby site
which failed because the information is available only on the primary site.
Action: Query the replication apply events from the primary site.
ADVM-05810: invalid query of replication transport events on the standby site
Cause: An attempt was made to query the replication transport events on the standby
site which failed because the information is available only on the primary site.
Action: Query the replication transport events from the primary site.
ADVM-05811: ACFS replication initialization failed in Oracle Restart environment.
Cause: Initialization failed because the system was configured with Oracle Restart.
ACFS replication is not supported for Oracle Restart configurations.
Action: Initialize ACFS replication in an environment that is configured with single or
multi-node RAC.
ADVM-07016: metadata read failed at disk offset: string size: number bytes
Cause: An attempt to read metadata at the indicated disk offset failed. Refer to the
ADVM-07017: metadata read failed at disk offset: string\n bytes requested: number
Cause: A metadata read at the indicated offset was incomplete. The amount of data
ADVM-00501 to ADVM-11111 4-55
ADVM-07018: metadata write failed at disk offset: string size: number bytes
Cause: An attempt to write metadata at the indicated disk offset failed. Refer to the
ADVM-07019: metadata write failed at disk offset: string\n bytes requested:
number bytes written: number bytes
Cause: A metadata write at the indicated offset was incomplete. The amount of data
ADVM-07021: The File_Entry_Table is corrupt and many of the files in the file
system may \nnot be recoverable. It is strongly recommended that the file system
be restored \nfrom a backup copy.
Cause: The ACFS Checker/Fixer found an inconsistency with the File_Entry_Table
metadata. The File_Entry_Table is a critical system structure that is necessary for a
functioning file system.
ADVM-07022: I/O request for (disk offset + size): string exceeds file system size:
Cause: An I/O request was made for data that exceeded the size of the file system."
ADVM-07023: read failed for metadata structure at disk offset: string size: number
bytes\nstructure type: string \nfor structure:\nstring
Cause: An attempt to read a metadata structure from disk failed. Refer to
ADVM-07024: File_Entry_Table entry: string exceeds the maximum value for this
file system: string
Cause: An entry was referenced that exceeded the File_Entry_Table limit.
ADVM-07025: File_Entry_Table entry: string already processed for structure:
\nstring
Cause: File_Entry_Table entries must be unique within a file system, but there were
multiple references for this specific entry.
4-56 Error Messages
ADVM-07026: file extent exceeds file system size: string\nextent: _FileOffset:

string _Length: string _PhysicalDiskOffset: string\nfor file:\nstring
Cause: The extent values of the indicated file referenced data beyond the size of the
file system. There are two possible causes: 1. The extent _Length and/or
_PhysicalDiskOffset property were incorrect. 2. The file system size value was
incorrect.
ADVM-07027: metadata structure at disk offset: string contains incorrect or invalid
type\n found: string, but expected to find: string or string\nfor structure:\nstring
Cause: The type property of the indicated metadata structure was not valid. The type
must be a DATA extent or a HEADER extent.
ADVM-07028: DATA extent structure has incorrect _granularity value\n found:
Cause: The _granularity property of the indicated DATA extent structure was invalid.
Its value must be -1.
ADVM-07029: HEADER extent structure has incorrect _granularity value\n found:
number, but expected to find: >= 0\nfor structure:\nstring
Cause: The _granularity property of the indicated HEADER extent structure was
invalid. Its value must be greater than or equal to zero.
ADVM-07030: file has invalid _FE_OsdSecurity value\nfor file:\nstring
Cause: The _FE_OsdSecurity property of the indicated file was invalid.
ADVM-07031: extent structure has incorrect _ExtentOffset value\n found: string,
Cause: The _ExtentOffset property of the indicated extent structure did not match its
disk offset.
ADVM-00501 to ADVM-11111 4-57
ADVM-07032: extent structure has incorrect _UpHeaderNodePtr value\n found:

Cause: The _UpHeaderNodePtr property of the indicated extent structure was
incorrect. There are two possible causes: 1. The _UpHeaderNodePtr property did not
match its parent. 2. The parent identifier property was incorrect.
ADVM-07033: extent structure has incorrect _granularity value\n found: number,
Cause: The _granularity property of the indicated extent structure did not match its
calculated depth.
ADVM-07034: extent structure has incorrect _NextFreeExtent value\n found:
Cause: The _NextFreeExtent property of the indicated extent structure was incorrect.
ADVM-07035: extent[number] appears to be uninitialized\nfor structure:\nstring
Cause: An extent of the indicated extent structure appeared to be in use, but all of its
values were zero.
ADVM-07036: extent[number] has invalid _Length value\n found: 0, but expected
to find: > 0\nfor structure:\nstring
Cause: The _Length property of an extent of the indicated extent structure had a value
of zero. _Length values must be greater than zero.
ADVM-07037: extent[number] has incorrect _SnapIncarnationNumber value\n
Cause: The _SnapIncarnationNumber property of the indicated extent structure
ADVM-07038: extent[number] has a non-contiguous _FileOffset value\n found:
Cause: The _FileOffset property of an extent of the indicated extent structure was not
contiguous with the _FileOffset of the previous extent.
4-58 Error Messages
ADVM-07039: extent[number] is not in use but it contains non-zero values:\n
Cause: An extent of the indicated extent structure was not in use, but it contained
non-zero values. There are two possible causes: 1. The extent values were not reset to
zero when the extent was freed. 2. The _NextFreeExtent property of the extent
ADVM-07040: calculated extent structure allocation size (sum of data sizes) does
not match expected value\n calculated: string, but expected to find:string\nfor
structure:\nstring
Cause: The sum of all valid extents within the indicated extent structure did not
match the value of the corresponding extent in the parent extent structure.
ADVM-07041: DATA extent list not found\nfor file:\nstring
Cause: The list of DATA extent structures of the indicated file did not include the
initial DATA extent structure. There are two possible causes: 1. The
the _LastExtentPointer value was not a DATA extent structure.
ADVM-07042: DATA extent node list missing entry for extent structure:\nstring
Cause: The list of DATA extent structures of the indicated file was incomplete. One or
more DATA extent structures was missing. There are three possible causes: 1. The
the _LastExtentPointer value was not a valid DATA extent structure. 3. The
ADVM-07043: metadata structure has invalid or incorrect type:\n found: string, but
Cause: The type property of the indicated metadata structure did not match the type
expected for this structure.
ADVM-00501 to ADVM-11111 4-59
ADVM-07044: DATA extent list has more nodes than expected\n found: number,
but expected to find: number\nfor file:\nstring
Cause: The list of DATA extent structures of the indicated file contained more nodes
than expected. The _NextDataExtent property of one or more DATA extent structures
was incorrect.
ADVM-07045: DATA extent list has fewer nodes than expected\n found: number,
but expected to find: number\nfor file:\nstring
Cause: The list of DATA extent structures of the indicated file contained fewer nodes
than expected. There are two possible causes: 1. One or more of the DATA extent
structures did not have a valid structure header. 2. The _NextDataExtent property of
one or more DATA extent structures was incorrect.
ADVM-07046: file has _LastExtentPointer that does not match calculated value\n
calculated: string, but expected to find: string\nfor file:\nstring
Cause: The _LastExtentPointer property of the indicated file did not match the file's
last DATA extent structure. There are three possible causes: 1. The _LastExtentPointer
value was incorrect. 2. The last DATA extent structure was not found because the The
ADVM-07047: extent node list missing entry for extent structure:\nstring
Cause: The list of extent structures of the indicated file was incomplete. One or more
extent structures was missing. There are three possible causes: 1. The
_LastExtentPointer property of the file was incorrect. 2. One or more extent structures
did not have a valid structure header. 3. The _LastExtentPointer property of one or
more extent structures was incorrect.
ADVM-07048: metadata structure has invalid _generation_number value\n found:
Cause: The _generation_number property of the indicated metadata structure was
incorrect.
ADVM-07049: extent list has more nodes than expected\n found: number, but
Cause: The list extent structures of the indicated file contained more nodes than
expected. The _LastExtentPointer property of one or more extent structures was
incorrect.
4-60 Error Messages
ADVM-07050: extent list has fewer nodes than expected\n found: number, but
Cause: The list of extent structures of the indicated file contained fewer nodes than
expected. There are two possible causes: 1. One or more of the extent structures did
not have a valid structure header. 2. The _LastExtentPointer property of one or more
extent structures was incorrect.
ADVM-07051: file has incorrect _LinkCount value\n found: number, but expected
Cause: The _LinkCount property of the indicated file did not match the number of
hard links found for the file. There are four possible causes: 1. The _LinkCount
property was incorrect. 2. One or more directory entries for this file was invalid or
was not found. 3. A Directory_Entry structure for this file had an incorrect file
identifier. 4. The _LinkCount property of an ACFS Internal File was not equal to one.
ADVM-07052: file has invalid _ProtectionBits value\n found: number, but expected
Cause: The _ProtectionBits property of the indicated files was incorrect.
ADVM-07053: file has invalid _ParentID value\n found: string, but expected to
Cause: The _ParentID property of the indicated file was not correct. There are two
possible causes: 1. The _ParentID value did not match the file's parent directory. 2.
The _ParentID value did not match any valid directory.
ADVM-07054: file has invalid _WindowsAttributes value(s)\n found: string\n, but
Cause: The _WindowsAttributes property of the indicated file was invalid. The
_WindowsAttributes value must be zero since file was not created on a Windows
system.
ADVM-00501 to ADVM-11111 4-61

_FileOffset: string\n _Length: string\n _PhysicalDiskOffset: string\nfor file:
\nstring
ADVM-07057: extent[number] has incorrect _FileOffset\n found: string, but
Cause: The _FileOffset property of the initial extent of the indicated file was not zero.
The _FileOffset for a file's initial extent must be zero as it identifies the beginning of
the file.
ADVM-07058: file with local extents has invalid _LastExtentPointer value\n found:
Cause: The _LastExtentPointer property of the indicated file was not zero which is
required for files with local extents.
ADVM-07060: extent[number] appears to be uninitialized\nfor file:\nstring
Cause: An extent of the indicated file appeared to be in use, but all of its values were
zero.
ADVM-07061: extent[number] has invalid _Length value\n found: 0, but expected
to find: > 0\nfor file:\nstring
Cause: The _Length property of an extent of the indicated file had a value of zero.
_Length values must be greater than zero.
ADVM-07062: extent[number] has incorrect _SnapIncarnationNumber value\n
found: number maximum: number\nfor file:\nstring
maximum value for the file system.
4-62 Error Messages
ADVM-07063: extent[number] has a non-contiguous _FileOffset value\n found:

Cause: The _FileOffset property of an extent of the indicated file was not contiguous
with the _FileOffset of the previous extent.
ADVM-07064: file _AllocationSize value not equal to sum of extents\n found:
Cause: The _AllocationSize property of the indicated file was not equal to the sum of
the _Length properties of the file's extents. There are three possible causes: 1. The
_AllocationSize value was incorrect. 2. The _Length property of one or more of the
file's extents was incorrect. 3. The _NextFreeExtent property of the file was incorrect.
ADVM-07065: File_Entry_Table calculated allocation size (sum of data extents)
does not match its _FileSize value\n found: string calculated: string\nfor file:
\nstring
Cause: The _FileSize property of File_Entry_Table did not match the sum of the file's
extent _Length values. There are two possible causes: 1. The _Length property of one
or more extents of the File_Entry_Table was incorrect. 2. The _FileSize property of the
File_Entry_Table was incorrect.
_SnapIncarnationNumber: number\nfor file:\nstring
ADVM-07073: file has _FileEntry structure with incorrect or invalid _FileEntryType
value\n found: string, but expected to find: string\nfor file:\nstring
Cause: The _FileEntryType property of the indicated file did not match its expected
value. There are two possible causes: 1. The _FileEntryType value was incorrect for
this particular file. 2. The _FileEntryType value was not on the list of valid values.
ADVM-07074: file has _FileEntry structure with incorrect file identifier\n found:
Cause: The file identifier property of the indicated file did not match its position
within the File_Entry_Table entry.
ADVM-00501 to ADVM-11111 4-63
ADVM-07075: file has incorrect _FileSize value\n found: string minimum: string
\nfor file:\nstring
ADVM-07076: file has invalid _AllocationSize value\n found: string minimum:
Cause: The _AllocationSize property of the indicated file was invalid. The
_AllocationSize value for this file cannot be less than the value described in the
message.
ADVM-07077: Local_Bitmap has incorrect _FileOffset value for Extent[1]\n found:
Cause: The _FileOffset property in Extent[1] of the indicated Local_Bitmap was not
zero.
ADVM-07078: Local_Bitmap has incorrect _Length value in Extent[1]\n found:
Cause: The _Length property in Extent[1] of the indicated Local_Bitmap did not
match the file system's allocation unit size.
ADVM-07079: Local_Bitmap has invalid _PhysicalDiskOffset value for Extent[1]\n
was equal to zero. This _PhysicalDiskOffset value must be greater than zero.
ADVM-07080: Local_Bitmap has incorrect _PhysicalDiskOffset value for
Extent[1]\n found: string maximum: string\nfor file:\nstring
exceeded the size of the file system.
Action: n/a
4-64 Error Messages
ADVM-07081: file has invalid _granularity value\n found: number, but expected to
Cause: The _granularity property of the indicated system file was incorrect. Many
system files require local extents which is indicated by a _granularity value of -1.
ADVM-07082: Global_BitMap space requirement exceeds _AllocationSize value.
Bitmap requires string bytes, allocated space: string bytes\nfor file:\nstring
Cause: The _AllocationSize property of the Global_BitMap was not large enough to
store the Global_BitMap data. There are two possible causes: 1. The _AllocationSize
value was incorrect. 2. The value used to indicate the number of bits needed to map
file system storage was incorrect.
ADVM-07083: Global_BitMap has invalid _granularity value\n found: number, but
Cause: The _granularity property of the indicated Global_BitMap was incorrect. The
Global_BitMap file must have a _granularity value of -1 which indicates that the file
has local extents.
ADVM-07084: Snap_Map has mismatch between _FileSize and _AllocationSize
values\n _FileSize: string _AllocationSize: string\nfor file:\nstring
Cause: The _FileSize and _AllocationSize properties of the indicated Snap_Map file
did not match. The values for these properties must match for a Snap_Map file. One
or both values was incorrect.
ADVM-07085: file has _FileSize value that exceeds _AllocationSize value\n
_FileSize: string _AllocationSize: string\nfor file:\nstring
Cause: The _FileSize property of the indicated file exceeded the amount of storage
allocated to the file. The _AllocationSize property describes the amount of storage
available for the file. One of of these properties was incorrect.
ADVM-07086: file has _AllocationSize value that is invalid for the file system\n
found: string, but expected to find: multiple of string\nfor file:\nstring
Cause: The _AllocationSize property of the indicated file was incorrect. Its value must
be a multiple of the file system allocation unit size.
ADVM-00501 to ADVM-11111 4-65
ADVM-07087: file has _AllocationSize value but no extent information\n

_AllocationSize: string\nfor file:\nstring
Cause: The _AllocationSize property of the indicated file was greater than 0, but there
was no corresponding extent information. There are two possible causes: 1. The
_AllocationSize should have been zero. 2. The _NextFreeExtent value was incorrect.
ADVM-07088: Map_File has incorrect _FileSize value\n found: string, but expected
to find: multiple of number\nfor file:\nstring
Cause: The _FileSize property of the indicated Map_File was incorrect. The _FileSize
value for a Map_File must be a multiple of the META_MAP_ENTRY size.
ADVM-07089: Volume_Log has invalid _FileSize value\n found: string, but
Cause: The _FileSize property of the indicated Volume_Log file was not equal to zero.
The _FileSize value for a Volume_Log must be zero.
ADVM-07090: Volume_Log has invalid _granularity value\n found: number, but
Cause: The _granularity property of the indicated Volume_Log file was incorrect.
Volume_Log files must have a _granularity value of -1 which indicates that the file
has local extents.
ADVM-07091: Volume_Log has incorrect _NextFreeExtent value\n found: number,
but expected to find: 0 or 1\nfor file:\nstring
Cause: The _NextFreeExtent property of the indicated Volume_Log file was incorrect.
A Volume_Log file can have at most one extent.
ADVM-07092: file has invalid _security_data_offset value\nfor file:\nstring
Cause: The _security_data_offset property of the indicated file did not have a
corresponding entry in any Security_Metadata file. There are three possible causes: 1.
The _security_data value was incorrect. 2. The Security_Metadata file had incorrect
data at the corresponding offset. 3. The Security_Metadata file was not found.
4-66 Error Messages
ADVM-07094: file has invalid _SnapMetaIncarnationNumber value\n found:

number maximum: number\nfor file:\nstring
maximum _SnapIncarnationNumber value for the file system.
ADVM-07095: CHARACTER special file has invalid major_device_number value
\n found: 0, but expected to find: > 0\nfor file:\nstring
Cause: The major_device_number property of the indicated CHARACTER special file
was invalid. major_device_number values must be greater than zero.
ADVM-07096: file has incorrect _EAOffset value\n found: string, but expected to
Cause: The _EAOffset property of the indicated file was incorrect.
ADVM-07097: file has invalid _TimeofCreation value\n found: string, but expected
Cause: The _TimeofCreation property of the indicated file was incorrect.
ADVM-07098: file has invalid _TimeLastAccessed value\n found: string, but
Cause: The _TimeLastAccessed property of the indicated file was incorrect.
ADVM-07099: file has invalid _TimeLastModified value\n found: string, but
Cause: The _TimeLastModified property of the indicated file was incorrect.
ADVM-07100: file has invalid _FileSize value\n found: string minimum: string
\nfor file:\nstring
Cause: The _FileSize property of the indicated file was invalid. The _FileSize value for
this file cannot be less than the value described in the message.
ADVM-00501 to ADVM-11111 4-67
ADVM-07101: file has invalid _TimeLastChanged value\n found: string, but

Cause: The _TimeLastChanged property of the indicated file was incorrect.
ADVM-07102: file has invalid _TimeofCreation value\n found: 0\nfor file:\nstring
Cause: The _TimeofCreation property of the indicated file was invalid. The
_TimeofCreation value must be non-zero.
ADVM-07103: file has invalid _TimeLastAccessed value\n found: 0\nfor file:
\nstring
Cause: The _TimeLastAccessed property of the indicated file was invalid. The
_TimeLastAccessed value must be non-zero.
ADVM-07104: file has invalid _TimeLastModified value\n found: 0\nfor file:
\nstring
Cause: The _TimeLastModified property of the indicated file was invalid. The
_TimeLastModified value must be non-zero.
ADVM-07105: file has invalid _TimeLastChanged value\n found: 0\nfor file:
\nstring
Cause: The _TimeLastChanged property of the indicated file was invalid. The
_TimeLastChanged value must be non-zero.
ADVM-07106: file has invalid _WindowsAttributes value(s)\n found: string\n
valid values: string\nfor file:\nstring
Cause: The _WindowsAttributes property of the indicated file was invalid. One or
more of the _WindowsAttributes values were not within the range of valid values.
Refer to the corresponding messages for a list of valid values.
ADVM-07107: file has incorrect _rep_incarnation value\n found: number, but
Cause: The _repFE_incarnation_number property of the indicated file was incorrect.
4-68 Error Messages
ADVM-07108: file has incorrect _rep_VFN value\n found: string, but expected to
Cause: The _rep_VFN property of the indicated file was incorrect.
ADVM-07109: file has incorrect _rep_SCN value\n found: string, but expected to
Cause: The _rep_SCN property of the indicated file was incorrect.
ADVM-07110: file has incorrect _EncrMetaOffset value\n found: string, but
Cause: The _EncrMetaOffset property of the indicated file was incorrect.
ADVM-07111: file has incorrect _Vault_MetaOffset value\n found: string, but
Cause: The _Vault_MetaOffset property of the indicated file was incorrect.
ADVM-07112: file has incorrect _EncrSecFlags value\n found: string, but expected
Cause: The _EncrSecFlags property of the indicated file was incorrect.
ADVM-07113: file has incorrect _EA_ContainerUnits value\n found: number, but
Cause: The _EA_ContainerUnits property of the indicated file was incorrect.
ADVM-07115: Local_Bitmap has incorrect _FileSize value\n found: string, but
Cause: The _FileSize property of the indicated Local_Bitmap was invalid. The
_FileSize value for a Local_Bitmap must be zero.
ADVM-00501 to ADVM-11111 4-69
ADVM-07116: BLOCK special file has invalid major_device_number value\n

Cause: The major_device_number property of the indicated BLOCK special file was
invalid. major_device_number values must be greater than zero.
ADVM-07117: Directory_Entry structure has invalid file identifier value:\n found:
string maximum: string\nfor structure:\nstring
Cause: The file identifier property of the indicated Directory_Entry structure
exceeded the maximum file identifier for the file system.
ADVM-07118: System metadata file is corrupt and cannot be repaired\nfor file:
\nstring
Cause: The ACFS Checker/Fixer found an inconsistency with the indicated system
metadata file. This metadata file cannot be repaired due to the nature of the
corruption.
ADVM-07119: _Locator structure has incorrect _global_dir_blk value\n found:
Cause: The _global_dir_blk property of the indicated structure was incorrect.
ADVM-07120: _Locator structure has invalid node identifier for entry number in
_node_number array\n found: number maximum: number\nfor structure:\nstring
Cause: A node identifier in the _node_number array of the indicated structure that
ADVM-07121: _Locator structure has invalid file identifier for entry number in
_local_dir_blk array\n found: string maximum: string\nfor structure:\nstring
Cause: A file identifier for a Local_Metadata_Directory in the _local_dir_blk array of
the indicated _Locator structure exceeded the maximum file identifier for the file
system.
ADVM-07122: _Locator structure has incorrect _local_dir_blk_disk_offset for entry
number in _local_dir_blk_disk_offset array\n found: string, but expected to find:
Cause: The disk offset for a Local_Metadata_Directory in the
_local_dir_blk_disk_offset array of the indicated _Locator structure was incorrect.
4-70 Error Messages
There are two possible causes: 1. The _local_dir_blk_disk_offset value was incorrect.
2. The structure at the _local_dir_blk_disk_offset was not a Local_Metadata_Directory
structure.
ADVM-07123: _Locator structure has duplicate entries for node number\nfor
structure:\nstring
Cause: There was more than one entry for the same node within the _Locator
structure(s). Node identifies must be unique.
ADVM-07124: _Locator structure has duplicate entries for
Local_Metadata_Directory: string\nfor structure:\nstring
Cause: There was more than one entry for the same Local_Metadata_Directory within
the _Locator structure(s). Local_Metadata_Directory file identifiers must be unique.
ADVM-07125: _Locator structure has incorrect _node_count value\n found:
Cause: The _node_count property of the indicated _Locator structure did not match
the number of valid nodes found.
ADVM-07126: _Locator structure has incorrect _next_locator_blk_disk_offset value
\n found: string\nfor structure:\nstring
Cause: The _next_locator_blk_disk_offset property of the indicated _Locator structure
was incorrect. There are two possible causes: 1. The _next_locator_blk_disk_offset
was incorrect. 2. The structure at the _next_locator_blk_disk_offset was not a _Locator
structure.
ADVM-07127: Global_Virtual_FileID_Pool structure has incorrect
_repFreeVFNGroup value\n found: string, but expected to find: string\nfor
structure:\nstring
Cause: The _repFreeVFNGroup property of the indicated Global_Virtual_FileID_Pool
ADVM-00501 to ADVM-11111 4-71
ADVM-07128: Global_Virtual_FileID_Pool structure has incorrect

_repFreeVFNIncarnNum value\n found: string, but expected to find: string\nfor
structure:\nstring
Cause: The _repFreeVFNIncarnNum property of the indicated
Global_Virtual_FileID_Pool structure was incorrect.
ADVM-07129: Replication_Log_Initiator structure has incorrect _initiator_node_id
Cause: The _initiator_node_id property of the indicated Replication_Log_Initiator
ADVM-07130: Replication_Log_Initiator structure has incorrect
_new_rlog_recovered value\n found: number, but expected to find: number\nfor
structure:\nstring
Cause: The _it_rep_logs_processed property of the indicated
Replication_Log_Initiator structure was incorrect.
ADVM-07131: Replication_Log_Initiator structure has incorrect _next_cord_id
Cause: The _next_cord_id property of the indicated Replication_Log_Initiator
ADVM-07132: Replication_Log_Initiator structure has incorrect _next_segment_id
Cause: The _next_segment_id property of the indicated Replication_Log_Initiator
ADVM-07133: Local_Bitmap has incorrect _AllocationSize value\n found: string,
Cause: The _AllocationSize property of the indicated Local_Bitmap did not match the
_Length value of its first extent.
4-72 Error Messages
ADVM-07134: invalid global_dir_fileid value\n found: string, but expected to find:

string
ADVM-07135: Global_Metadata_Directory structure has incorrect _node_number
Cause: The _node_number property of the indicated Global_Metadata_Directory
ADVM-07136: Global_Metadata_Directory structure has incorrect
_global_free_blk_list value\n found: string, but expected to find: string\nfor
structure:\nstring
Cause: The _global_free_blk_list property of the indicated
_global_bitmap_fileid value\n found: string, but expected to find: string\nfor
structure:\nstring
Cause: The _global_bitmap_fileid property of the indicated
_SuperBlock_fileid value\n found: string, but expected to find: string\nfor
structure:\nstring
Cause: The _SuperBlock_fileid property of the indicated Global_Metadata_Directory
ADVM-07139: Global_Metadata_Directory structure has incorrect _gdrfl_fileid
Cause: The _gdrfl_fileid property of the indicated Global_Metadata_Directory
ADVM-00501 to ADVM-11111 4-73

_dotofs_dir_fileid value\n found: string, but expected to find: string\nfor
structure:\nstring
Cause: The _dotofs_dir_fileid property of the indicated Global_Metadata_Directory
ADVM-07141: Global_Metadata_Directory structure has incorrect _ready_dir_fileid
Cause: The _ready_dir_fileid property of the indicated Global_Metadata_Directory
_repl_config_fileid value\n found: string, but expected to find: string\nfor
structure:\nstring
Cause: The _repl_config_fileid property of the indicated Global_Metadata_Directory
_mmap_log_fileid value\n found: string, but expected to find: string\nfor
structure:\nstring
Cause: The _mmap_log_fileid property of the indicated Global_Metadata_Directory
_repGlobalVFNPool_fileid value\n found: string, but expected to find: string\nfor
structure:\nstring
Cause: The _repGlobalVFNPool_fileid property of the indicated
_repl_config_tbl_fileid value\n found: string, but expected to find: string\nfor
structure:\nstring
Cause: The _repl_config_tbl_fileid property of the indicated
4-74 Error Messages

_repLogCutInitiatorBlock_fileid value\n found: string, but expected to find: string
Cause: The _repLogCutInitiatorBlock_fileid property of the indicated
_repLogCutInitiatorBlock_offset value\n found: string, but expected to find: string
Cause: The _repLogCutInitiatorBlock_offset property of the indicated
_snap_map_fileid value\n found: string, but expected to find: string\nfor
structure:\nstring
Cause: The _snap_map_fileid property of the indicated Global_Metadata_Directory
ADVM-07149: Global_Metadata_Directory structure has incorrect _snaps_dir_fileid
Cause: The _snaps_dir_fileid property of the indicated Global_Metadata_Directory
_global_tagdir_fileid value\n found: string, but expected to find: string\nfor
structure:\nstring
Cause: The _global_tagdir_fileid property of the indicated
_ea_change_fileid\n found: string, but expected to find: string\nfor structure:
\nstring
Cause: The _ea_change_fileid property of the indicated Global_Metadata_Directory
ADVM-00501 to ADVM-11111 4-75
ADVM-07152: orphan directory 'string' (file identifier: string) \nadded to 'lost

+found' directory
Cause: The indicated directory did not have a valid entry in any parent directory. The
ACFS Fixer move the file to the 'lost+found' directory.
ADVM-07154: An attempt to create a low-fragmentation memory heap failed.
of memory.
Cause: A call to the Windows HeapCreate function failed. Refer to the accompanying
message(s) for more information on the error.
Action: No further action is required unless there is an error using the standard
memory heap. If there is an error using the standard memory heap then refer to the
accompanying message(s) for information to resolve the problem.
ADVM-07155: An attempt to initialize a low-fragmentation memory heap failed.
of memory.
Cause: A call to the Windows HeapSetInformation function failed. Refer to the
Action: The program will automatically attempt to continue with the standard
memory heap but could run out of memory. No further action is required unless there
is an error using the standard memory heap. To use low-fragmentation heaps, refer to
Microsoft documentation on GlobalFlags values for executables that are not
compatible with low-fragmentation heaps. Then use the regedit utility to unset those
flags on the executable.
ADVM-07156: Local_Metadata_Directory structure has incorrect
_map_file_disk_offset value\n found: string, but expected to find: string\nfor
structure:\nstring
Cause: The _map_file_disk_offset property of the indicated
_vol_log_disk_offset value\n found: string, but expected to find: string\nfor
structure:\nstring
Cause: The _vol_log_disk_offset property of the indicated Local_Metadata_Directory
ADVM-07158: unable to create Security_Metadata file offset list\nfor file:\nstring
Cause: The ACFS Checker could not create the Security_Metadata file offset list. Refer
4-76 Error Messages
ADVM-07159: Local_Metadata_Directory structure has incorrect _smf_fileid value

Cause: The _smf_fileid property of the indicated Local_Metadata_Directory structure
was incorrect.
ADVM-07160: Local_Metadata_Directory structure has incorrect _it_rlog_fileid
Cause: The _it_rlog_fileid property of the indicated Local_Metadata_Directory
ADVM-07161: Local_Metadata_Directory structure has incorrect _rlog_fileid value
Cause: The _rlog_fileid property of the indicated Local_Metadata_Directory structure
was incorrect.
_it_rmap_file_fileid value\n found: string, but expected to find: string\nfor
structure:\nstring
Cause: The _it_rmap_file_fileid property of the indicated Local_Metadata_Directory
ADVM-07163: Local_Metadata_Directory structure has incorrect _rmap_file_fileid
Cause: The _rmap_file_fileid property of the indicated Local_Metadata_Directory
_repLocalVFNPool_fileid value\n found: string, but expected to find: string\nfor
structure:\nstring
Cause: The _repLocalVFNPool_fileid property of the indicated
ADVM-00501 to ADVM-11111 4-77
ADVM-07165: invalid file identifier: string

Cause: The file identifier enetered must be a valid numeric value, greater than or
equal to 0, and less than the maximum file identifier value for the file system.
Action: Re-enter a valid file identifier value.
ADVM-07168: Global_BitMap has incorrect value for bitmap size\n found: string,
Cause: The bitmap size property of the indicated Global_BitMap file was incorrect. Its
value did not the bitmap size that was calculated for the file system.
ADVM-07169: Global_BitMap has incorrect _AllocationSize value\n found: string,
Cause: The _AllocationSize property of the indicated Global_BitMap file was
incorrect. The _AllocationSize value was not large enough to store the Global_BitMap
data as determined by the ACFS Checker.
ADVM-07170: Global_BitMap has incorrect values for Extent[0]\n found:
_FileOffset: string _Length: string _PhysicalDiskOffset: string\n, but expected to
find: _FileOffset: string _Length: string _PhysicalDiskOffset: string\nfor file:
\nstring
Cause: The _PhysicalDiskOffset property of the first extent of the indicated
Global_BitMap file was incorrect. The Global_BitMap data must begin at the disk
offset described in the message.
ADVM-07171: attempt to read SuperBlock FileEntry failed\nfor file:\nstring
Cause: An attempt to read SuperBlock metadata failed. Refer to the accompanying
ADVM-07172: file has incorrect values for Extent[number] \n found: _FileOffset:
string _Length: string _PhysicalDiskOffset: string \n, but expected to find:
_FileOffset: string _Length: string _PhysicalDiskOffset: string \nfor file:\nstring
ADVM-07175: file has incorrect values for Extent[number]\n found: _FileOffset:
string _Length: string \n, but expected to find: _FileOffset: string _Length: string
\nfor file: \nstring
4-78 Error Messages
ADVM-07176: file has invalid _AllocationSize value\n found: string, but expected
Cause: The _AllocationSize property of the indicated file was incorrect.
ADVM-07177: file has incorrect _FileSize value\n found: string, but expected to
ADVM-07178: file has incorrect _granularity value\n found: number, but expected
Cause: The _granularity property of the indicated file was incorrect. Some ACFS
internal files must have a _granularity value equal to -1 which indicates that the file
has local extents.
ADVM-07179: file has incorrect _NextFreeExtent value\n found: number, but
ADVM-07180: There is an inconsistency between the ACFS Map_File and the
ACFS Log_File.
ADVM-07184: Log_File not processed for node number\nfor file:\nstring
Cause: A Log_File was found but not processed. Unprocessed Log_Files could result
in false errors being reported because transaction data was not applied to the file
system.
Action: There are two actions possible: 1. Run the ACFS Fixer which will
automatically process all valid Log_Files. 2. Run the ACFS Checker and respond yes
to any question pertaining to Log_File processing.
ADVM-07185: The ACFS Map _FileSize: number indicates that there is transaction
data \nto be processed, but the ACFS Log _AllocationSize: number indicates that
ADVM-00501 to ADVM-11111 4-79
\nthere is no data available. \nACFS Map_File:\nstring \nACFS Log_File: \nfor

file: \nstring
ADVM-07188: Map_File has entry with incorrect _Length value\n found: number
\nfor file:\nstring
Cause: There are two possible causes: 1. The Map_File entry's _Length was equal to
zero. 2. The Map_File entry's _Length was not a multiple of the volume's sector size as
detailed in the message.
ADVM-07189: Map_File has entry with incorrect _ActualDiskOffset value\n
found: string minimum: string\nfor file:\nstring
incorrect. The _ActualDiskOffset value in a Map_File entry must be greater than the
previous entry's _ActualDiskOffset.
ADVM-07190: Map_File has an entry with invalid _LogDiskOffset value\n found:
string minimum: string maximum: string\nfor file:\nstring
Cause: The _LogDiskOffset property for an entry in the indicated Map_File was
incorrect. The _LogDiskOffset value in a Map_File entry must be within the
corresponding Log_File data.
ADVM-07191: Map_File has duplicate entries for _ActualDiskOffset:string\nfor
file:\nstring
Cause: The indicated Map_File contained more than one entry for the same disk
offset. _ActualDiskOffset values must be unique within a Map File.
ADVM-07192: Map_File has incorrect Map_Entry _Length for the
Volume_Disk_Header\n found: number, but expected to find: number\nfor file:
\nstring
Cause: The _Length property for an entry in the indicated Map_File was incorrect.
The entry was for a Volume_Disk_Header structure, but its _Length value did not
match the size of a Volume_Disk_Header structure.
4-80 Error Messages
ADVM-07193: Map_File entry with an invalid _ActualDiskOffset value\n found:

incorrect. The _ActualDiskOffset value that exceeded the size of this file system.
ADVM-07195: metadata write failed while processing Volume_Log transaction data
Cause: An error occurred while writing Volume_Log transaction data to the file
system. Refer to the accompanying message(s) for more information.
ADVM-07196: write failed for Map_File metadata structure at disk offset: string
Cause: An attempt to write a metadata structure to disk failed. Refer to accompanying
ADVM-07197: discarding Volume_Log and Map_File contents on node number due
to processing error
Cause: An error occurred while processing file system transaction data. Refer to the
ADVM-07199: write failed for Volume_Log metadata structure at disk offset: string
Cause: An attempt to update a metadata structure of the indicated Volume_Log file
ADVM-07200: duplicate _SnapFetaFenum: string found for the following
snapshots:\n
Cause: The _SnapFetaFenum property of the indicated snapshots had the same value.
_SnapFetaFenum values must be unique.
Support Services.
ADVM-00501 to ADVM-11111 4-81
ADVM-07201: Global_Free_Block list is corrupt

Cause: A metadata inconsistency was found within the Global_Free_Block list for the
file system.
ADVM-07202: Free_Block_List has incorrect _free_blk_count value\n found: string,
Cause: The _free_blk_count property of the indicated Free_Block_List was incorrect.
ADVM-07203: results for Snap_Map data may be limited or incorrect due to
Services.
ADVM-07204: write failed for Global_BitMap metadata structure at disk offset:
string size: number bytes\nstructure type: string \nfor file:\nstring
Cause: An attempt to update a metadata structure of the indicated Global_BitMap file
ADVM-07205: functionality may be limited due to File_Entry_Table metadata
inconsistency
Services.
ADVM-07206: read failed for Local_BitMap metadata structure at disk offset: string
Cause: An attempt to read a metadata structure of the indicated Local_BitMap file
ADVM-07207: functionality related to snapshots disabled due to problems
accessing Snap_Map file
4-82 Error Messages
Services.
ADVM-07208: Local_BitMap (file identifier: string) has incorrect size\n found:
string, but expected to find: string \nfor file:\nstring
Cause: The size property of the indicated Local_BitMap was incorrect.
ADVM-07209: Local_BitMap (file identifier: string) has incorrect Global_BitMap
file offset: string or incorrect disk offset: string \nfor file:\nstring
Cause: The Global_BitMap offset property of the indicated Local_BitMap was
incorrect.
ADVM-07211: mismatch between Local_BitMap (file identifier: string) and
temporary Global_BitMap for disk offset: string
Cause: The bitmap data of the indicated Local_BitMap did not match the
corresponding bitmap data of the temporary Global_BitMap for the described disk
offset.
ADVM-07212: temporary Global_BitMap bit set for disk offset: string exceeds
maximum offset: string
Cause: The bitmap data of the temporary Global_BitMap referenced storage that is
beyond the size of this file system.
ADVM-07215: Volume_Disk_Header has invalid _VolSignature value\n found:
'string'\n, but expected to find: string, string, string, or string\nfor structure:
\nstring
Cause: The _VolSignature property of the indicated Volume_Disk_Header was not a
valid ACFS volume signature.
ADVM-07216: Volume_Disk_Header has incorrect _Checksum value\n found:
Cause: The _Checksum property of the indicated Volume_Disk_Header did not
match its calculated value.
ADVM-00501 to ADVM-11111 4-83
ADVM-07217: Volume_Disk_Header version does not match string version\n

found: number.number, but expected to find: number.number\nfor structure:
\nstring
Cause: The _MajorVersionNumber and _MinorVersionNumber properties of the
indicated Volume_Disk_Header did not match the version of the ACFS Checker/
Fixer or ACFS debug utility that was being used. The ACFS Checker/Fixer or ACFS
debug utility was not compatible with this file system. There are two possible causes:
1. The version information in the Volume_Disk_Header structure was not correct. 2.
The ACFS Checker/Fixer or ACFS debug utility was not the correct version for the
file system.
Action: There are two possible actions: 1. If the file system version displayed in the
message is valid then run a compatible version of the ACFS Checker/Fixer or ACFS
debug utility. 2. If the file system version displayed in the message is not valid then
restore the file system from backup.
ADVM-07218: Volume_Disk_Header has incorrect _VolVolumeSize value\n
found: string maximum: string\n- temporarily assuming Volume Size: string\nfor
structure:\nstring
exceeded the size of the volume. The ACFS Checker temporarily assumed the
maximum volume size during processing.
found: string minimum: string\n- temporarily assuming Volume Size: string\nfor
structure:\nstring
Cause: The _VolVolumeSize property of the indicated Volume_Disk_Header was less
than the minimum supported volume size as detailed in the message. The ACFS
Checker temporarily assumed the maximum volume size during processing.
ADVM-07220: Volume_Disk_Header has incorrect _VolClusterSize value\n found:
string, but expected to find: string\n- assuming default size: string\nfor structure:
\nstring
Cause: The _VolClusterSize property of the indicated Volume_Disk_Header was
incorrect. The ACFS Checker temporarily assumed the default value during
processing.
ADVM-07221: Volume_Disk_Header has incorrect _VolFETALPosition value\n
found: string, but expected to find: string\n- assuming default File_Entry_Table
offset: string\nfor structure:\nstring
Cause: The _VolFETALPosition property of the indicated Volume_Disk_Header was
incorrect. The ACFS Checker temporarily assumed the default File_Entry_Table offset
during processing.
4-84 Error Messages
ADVM-07222: Volume_Disk_Header has incorrect _VolOrigVolumeSize value\n
found: string must be aligned on a string byte boundary\nfor structure:\nstring
ADVM-07223: Volume_Disk_Header has incorrect _VolExtentHeaderSize value\n
found: string, but expected to find: string\n- assuming default value: string\nfor
structure:\nstring
Cause: The _VolExtentHeaderSize property of the indicated Volume_Disk_Header
was incorrect. The ACFS Checker temporarily assumed the default value during
processing.
ADVM-07224: cannot process command due to Snap_Map File metadata
inconsistency
Cause: An acfsdbg command was not executed due to a metadata inconsistency.
Services.
ADVM-07225: Volume_Disk_Header has invalid _VolFileSystemEndian value\n
found: character, but expected to find: string or string\nfor structure:\nstring
Cause: The _VolFileSystemEndian property of the indicated Volume_Disk_Header
was invalid.
ADVM-07226: Volume_Disk_Header has invalid _VolStateFlag values.\n found:
ADVM-07227: missing snapshot name or identifier
Cause: A snapshot name or identifier was not entered as required for this command.
Action: Re-enter the command with a valid snapshot name or snapshot identifier.
ADVM-07228: cannot determine disk geometry for volume: string
Cause: The program was unable to determine the geometry of the indicated volume.
ADVM-00501 to ADVM-11111 4-85
ADVM-07229: volume: string has invalid sector size\n found: number, but expected
to find: number\n- assuming default value: number
Cause: The sector size of the indicated volume was invalid. The ACFS Checker
temporarily assumed the default sector size during processing.
ADVM-07230: cannot determine size for volume: string
Cause: The program was unable to determine the size of the indicated volume. Refer
ADVM-07231: seek to end of volume failed for volume: string offset: string
Cause: The program was unable to seek to the end of the indicated volume. Refer to
ADVM-07232: seek to end of volume failed for volume: string\n requested offset:
string returned offset: string
Cause: The request to seek to the end of the indicated volume failed. The offset set
returned did not match the offset requested. Refer to the accompanying message(s)
ADVM-07233: read failed for Primary Volume_Disk_Header at disk offset: string
Cause: An attempt to read the Primary Volume_Disk_Header at the indicated disk
problem.
ADVM-07234: read failed for Alternate Volume_Disk_Header at disk offset: string
Cause: An attempt to read the Alternate Volume_Disk_Header at the indicated disk
problem. problem.
ADVM-07235: extent[number] has invalid _PhysicalDiskOffset value\n found: 0,
but expected to find: greater than 0\nfor file:\nstring
4-86 Error Messages
ADVM-07236: extent[number] has invalid _PhysicalDiskOffset value\n found: 0,

but expected to find: greater than 0\nfor structure:\nstring
ADVM-07237: read failed for File_Entry_Table extent metadata structure at disk
Cause: An attempt to read an extent metadata structure of the indicated file failed.
ADVM-07239: File_Entry_Table count incorrect\n found: number, but expected to
Cause: The number of entries found in the File_Entry_Table file did not match the
expected number of entries. One or more of the extent structures was invalid.
ADVM-07240: Invalid Security_Metadata_File
message.
Support Services.
ADVM-07241: Security_Metadata file has invalid _security_descriptor record\nfor
file:\nstring
Cause: A _security_descriptor record of the indicated Security_Metadata file was
invalid.
ADVM-07243: Security_Metadata file has no valid _security_data records\nfor file:
\nstring
Cause: The indicated Security_Metadata file did not contain any valid valid
_security_data records.
ADVM-00501 to ADVM-11111 4-87
ADVM-07245: Security_Metadata file contains invalid _security_descriptor data

\nfor file:\nstring
Cause: The indicated Security_Metadata file contained at least one invalid
_security_data record. Refer to the accompanying message(s) for more information on
the problem.
ADVM-07246: Security_Metadata file _Private structure is invalid for:\nfor file:
\nstring
Cause: The _Private structure of the indicated Security_Metadata file was invalid.
ADVM-07247: Security_Metadata file has invalid Hash_Table data\nfor file:
\nstring
Cause: The Hash_Table of the indicated Security_Metadata file contained inconsistent
ADVM-07250: Security_Metadata file _Private structure has invalid _maxFree value
incorrect.
ADVM-07251: Security_Metadata file _Private structure has invalid
\nstring
was incorrect.
ADVM-07252: Security_Metadata file node not on _freeDataList\nfor file:\nstring
Cause: One or more of the _security_data nodes of the indicated Security_Metadata
file was not found on the free data node list. The _next property for one or more of the
4-88 Error Messages
ADVM-07254: Security_Metadata file has invalid _security_record for

ADVM-07256: file has unexpected _ProtectionBits value\n found: number, but
Cause: The _ProtectionBits property of the indicated files was not expected.
Action: No action is needed if the protection bits were intentionally set differently
from the default.
ADVM-07257: unable to process request for volume string; volume is not open
Cause: An attempt to read metadata failed because the volume was not open. Refer to
the accompanying messages for more information on the problem.
rerun the acfsdbg utility.
ADVM-07258: unable to reset context to snapshot string due to File_Entry_Table
Services. Services.
ADVM-07259: file system does not contain a valid Local_Metadata_Directory
Cause: There was no valid Local_Metadata_Directory in the file system. At least one
Local_Metadata_Directory is required.
ADVM-07260: Volume_Disk_Header has incorrect _VolNumOFSNodes value\n
Cause: The _VolNumOFSNodes property of the indicated Volume_Disk_Header
structure was incorrect. Its value did not match the number of valid ACFS nodes
found.
ADVM-07261: unable to reset context to snapshot string due to Snap_Map file
Services.
ADVM-00501 to ADVM-11111 4-89
ADVM-07262: unable to reset context to snapshot %(1) because it no longer exists

Cause: The identified snapshot no longer exists due to on-disk metadata changes that
are allowed whenever the acfsdbg utility is operating in read-only mode.
ADVM-07263: Free_Block_List has incorrect _first_free_group value\n found:
Cause: The _first_free_group property of the indicated Free_Block_List structure was
incorrect.
ADVM-07264: Free_Block_List has incorrect _last_free_blk value\n found: number,
Cause: The _last_free_blk property of the indicated Free_Block_List structure was
incorrect.
ADVM-07265: write failed for Free_Block metadata structure at disk offset: string
size: number bytes\nfor structure:\nstring
Cause: An attempt to write a Free_Block metadata structure to disk failed. Refer to
ADVM-07266: write failed for Free_Block_List metadata structure at disk offset:
string size: number bytes\nfor structure:\nstring
Cause: An attempt to write a Free_Block_List metadata structure to disk failed. Refer
ADVM-07267: file marked for deletion (file identifier: string, disk offset: string)
cannot be removed due to inconsistent file metadata
Cause: Inconsistent metadata was found for the indicated file that was marked for
deletion. The file could not be deleted.
ADVM-07268: file marked for deletion (file identifier: string, disk offset: string) has
invalid _LinkCount value\n found: number, but expected to find: 0
Cause: The indicated file was marked for deletion, but its _LinkCount property was
not zero. Files to be deleted must have a _LinkCount value of zero. The file could not
be deleted.
4-90 Error Messages
ADVM-07269: file marked for deletion (file identifier: string, disk offset: string) has
invalid _SynchFlag value\n found: string\n, but expected to find: string
Cause: The _SynchFlag property of the indicated file was incorrect. The file was
marked for deletion but its _SynchFlag did not have the appropriate value. The file
could not be deleted.
ADVM-07271: orphan file : string (file identifier: string) added to 'lost+found'
directory
Cause: The indicated file did not have a valid entry in any parent directory. The ACFS
Fixer move the file to the 'lost+found' directory.
ADVM-07272: read failed for extent metadata structure at disk offset: string\nfor
file:\nstring
Cause: An attempt to read an extent metadata structure for the indicated file failed.
ADVM-07274: missing or invalid snapshot name
Cause: No snapshot name was provided or the name entered was not valid.
Action: Re-enter the command with a valid snapshot name.
ADVM-07275: cannot read File_Entry_Table _FileEntry metadata structure\n- file
Cause: An attempt to read the _FileEntry metadata structure of the File_Entry_Table
failed. The File_Entry_Table is a critical ACFS metadata structure that is required for
file system validation or repairs. The ACFS Checker/Fixer could not process the file
system. NOTE: It is also possible that there was no ACFS file system on this volume.
Action: Correct the problem indicated by the accompanying messages if possible and
rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows). If the problem cannot be
resolved then restore the file system from a backup copy.
ADVM-07276: File_Entry_Table _FileEntry metadata structure is invalid\n- file
Cause: The File_Entry_Table's _FileEntry metadata structure is either corrupt or is
missing critical information. NOTE: It is also possible that there is no ACFS file
system on the volume.
ADVM-07280: checking File_Entry_Table entry: string at disk offset: string
Cause: The ACFS Checker found a File_Entry_Table entry that has not been
processed. This entry was an orphan file or an orphan internal metadata structure.
ADVM-00501 to ADVM-11111 4-91
ADVM-07282: read failed for File_Entry_Table entry: string at disk offset string
Cause: An attempt to read a File_Entry_Table entry failed. Refer to the accompanying
ADVM-07283: orphan File_Entry_Table metadata structure found for\n identifier:
string at disk offset: string\n structure type: string
Cause: A File_Entry_Table entry was found that had not been processed. This entry
was an orphan file or an invalid internal metadata structure.
ADVM-07284: orphan system file found for file identifier: string at disk
offset:string
Cause: The indicated system file did not have a valid parent directory.
ADVM-07285: snapshot: string (identifier: number) has invalid File_Entry_Table
identifier: string that exceeds the maximum value for this file system: string
Services.
ADVM-07286: orphan file found for file identifier: string at disk offset: string
Cause: The indicated file did not have a valid parent directory.
ADVM-07287: orphan Free_Block metadata structure found for file identifier:
Cause: The indicated Free_Block metadata structure was not found on any free block
list.
ADVM-07288: orphan file 'string' (file identifier: string) \nadded to 'lost+found'
directory
Cause: The indicated file did not have a valid entry in any directory which meant that
the file did not have a valid file name. The file was given the generic name described
in the message and moved to the 'lost+found' directory.
4-92 Error Messages
ADVM-07289: orphan Local_Metadata_Directory metadata structure found for file

Cause: The indicated Local_Metadata_Directory metadata structure was not found on
any _Locator list for Local_Metadata_Directory structures.
ADVM-07290: orphan Free_List_Header metadata structure found for file
Cause: The indicated Free_List_Header metadata structure was not found on any
valid Local_Metadata_Directory structure.
ADVM-07291: orphan _Locator metadata structure found for file identifier: string at
disk offset: string
Cause: The indicated _Locator metadata structure was not found in any list of valid
_Locator structures.
ADVM-07292: orphan Global_Metadata_Directory metadata structure found for
file identifier: string at disk offset: string
Cause: The File_Entry_Table contained a duplicate Global_Metadata_Directory
metadata structure. Global_Metadata_Directory structures must be unique.
ADVM-07294: orphan Global_Virtual_FileID_Pool metadata structure found for
Cause: The File_Entry_Table contained a duplicate entry for the
Global_Virtual_FileID_Pool metadata structure. Global_Virtual_FileID_Pool
structures must be unique.
ADVM-07295: orphan Local_Virtual_FileID_Pool metadata structure found for
Cause: The indicated Local_Virtual_FileID_Pool metadata structure was not found on
any valid Local_Metadata_Directory structure.
ADVM-00501 to ADVM-11111 4-93
ADVM-07296: orphan Replication_Log_Initiator metadata structure found for

Cause: The File_Entry_Table contained a duplicate entry for a
Replication_Log_Initiator metadata structure. Replication_Log_Initiator structures
must be unique.
ADVM-07297: File_Entry_Table entry: string at disk offset: string is not a valid
metadata structure
Cause: The indicated entry in the File_Entry_Table was not a metadata structure
recognized by ACFS.
ADVM-07298: cannot convert file identifier: 'string' to numeric value
Cause: The format entered for the file identifier was invalid.
ADVM-07300: directory Hash_Table contains duplicate entries for offset: string
\nfor file:\nstring
Cause: The Hash_Table of the indicated directory file had duplicate entries for the
offset described in the message. Hash_Table entries must map to unique offsets.
ADVM-07301: directory _hash_key: string for offset: string has no corresponding
file entry\nfor file:\nstring
Cause: The _hash_key property of the indicated directory file was invalid. Its value
did not reference a valid file entry.
ADVM-07302: directory _hash_key for offset: string is incorrect\n found: string,
Cause: The _hash_key property of the indicated directory file was incorrect. Its value
did not match the hash value calculated for the corresponding file entry.
ADVM-07303: Security_Metadata file Hash_Table contains multiple entries for
Cause: The Hash_Table of the indicated Security_Metadata file had duplicate entries
for the offset described in the message. Hash_Table entries must map to unique
offsets.
4-94 Error Messages
ADVM-07304: Security_Metadata file _hash_key: string for offset: string has no
corresponding entry\nfor file:\nstring
Cause: The _hash_key property of the indicated Security_Metadata file was invalid.
Its value did not reference a valid entry.
ADVM-07305: Security_Metadata file _hash_key for offset: string is incorrect\n
Cause: The _hash_key property of the indicated Security_Metadata file was incorrect.
Its value did not match the hash value calculated for the corresponding entry.
ADVM-07306: Hash_Table _hash_key order is incorrect\nfor file:\nstring
Cause: The _hash_key properties of the Hash_Table of the indicated file were not
ordered correctly.
ADVM-07308: Hash_File_Index structure for block number at disk offset: string
Cause: The Hash_File node list of the indicated file was invalid. One or more of the
Hash_File structures had an invalid _next property.
ADVM-07309: cannot access Hash_File_Index node metadata structure at disk
Cause: An attempt to access the indicated Hash_File_Index metadata structure failed.
ADVM-07310: Hash_File_Index node has incorrect _next value\n found: string, but
Cause: The _next property of the indicated Hash_File_Index structure was incorrect.
ADVM-00501 to ADVM-11111 4-95
ADVM-07311: Hash_Bucket for block number at disk offset: string already

processed\nfor structure:\nstring
Cause: The Hash_Bucket structure of the indicated file has already been processed.
One or more of the Hash_File structures had an invalid _next property.
ADVM-07312: cannot access Hash_Bucket metadata structure at disk offset: string
\nfor file:\nstring
Cause: An attempt to access the indicated Hash_Bucket metadata structure failed.
ADVM-07313: Hash_Bucket has incorrect _controlling_bkt value\n found: number,
incorrect.
ADVM-07314: Hash_Bucket has incorrect _split_count value\n found: number, but
Cause: The _split_count property of the indicated Hash_Bucket structure was
incorrect.
ADVM-07315: Hash_Bucket has incorrect _next value\n found: number, but
Cause: The _next property of the indicated Hash_Bucket structure was incorrect.
ADVM-07316: cannot access Hash_File_Master_Block metadata structure at disk
Cause: An attempt to access the indicated Hash_File_Master_Block metadata
structure failed. Refer to the accompanying message(s) for more information on the
problem.
ADVM-07317: Hash_File metadata structure for block:number at disk offset: string
Cause: The list of nodes of the indicated Hash_File file was invalid. One or more of
the Hash_File structures had an invalid _next property.
4-96 Error Messages
ADVM-07318: Hash_File_Master_Block structure has incorrect _initial_bkt_count
Cause: The _initial_bkt_count property of the indicated Hash_File_Master_Block
ADVM-07319: Hash_File_Master_Block structure has incorrect _double_count
Cause: The _double_count property of the indicated Hash_File_Master_Block
ADVM-07320: Hash_File_Master_Block structure has incorrect value for entry
number in _hash_bucket_group array\n found: number, but expected to find:
number\nfor structure:\nstring
Hash_File_Master_Block was incorrect.
ADVM-07321: _hash_entry number has no corresponding entry\nfor file:\nstring
Cause: The _hash_entry property in the Hash_Table of the indicated file did not have
a valid entry associated with it.
ADVM-07322: metadata read failed at disk offset: string size: number bytes\nfor
file:\nstring
Cause: An attempt to read metadata of the indicated file failed. Refer to the
bytes returned: number\nfor file:\nstring
Cause: An attempt to read metadata of the indicated file failed. The amount of data
ADVM-00501 to ADVM-11111 4-97
ADVM-07327: metadata write failed at disk offset: string size: number bytes\nfor
file:\nstring
Cause: An attempt to write metadata of the indicated file failed. Refer to
ADVM-07331: metadata write failed at disk offset: string\n bytes requested:
number bytes written: number\nfor file:\nstring
Cause: An attempt to write metadata of the indicated file failed. The amount of data
ADVM-07332: cannot convert snapshot identifier: 'string' to numeric value
Cause: The format entered for the snapshot identifier was invalid.
ADVM-07333: invalid snapshot identifier entered: string\n minimum: 1 maximum:
number
Cause: The snapshot identifier entered was not within the valid range for this file
system.
Action: Re-enter the command with a snapshot identifier that is within the valid
range described in the message.
ADVM-07334: invalid snapshot name 'string' entered
Cause: The snapshot name entered did not exist.
Action: Re-enter the command with the name or identifier of a valid snapshot.
ADVM-07335: Directory_Node has invalid _dir_entry_free_list_tail value\n found:
Cause: The _dir_entry_free_list_tail property of the indicated Directory_Node
ADVM-07336: Directory_Node structure has invalid _next_free_dirnode value\n
Cause: The _next_free_dirnode property of the indicated Directory_Node structure
was incorrect.
ADVM-07337: Directory_Entry structure has incorrect file identifier for file
'string'\n found: string, but expected to find: string\nfor structure:\nstring
Cause: The file identifier property of the indicated Directory_Entry structure did not
match the file identifier of the corresponding file.
4-98 Error Messages
ADVM-07338: Directory_Entry structure has incorrect _rec_len value for file
Cause: The _rec_len property of the indicated Directory_Entry structure was
incorrect.
ADVM-07339: Directory_Entry structure has incorrect _name_len value for file
incorrect.
ADVM-07340: Directory_Entry structure has invalid or incorrect _attributes for file
'string'\n found: string\n, but expected to find: string\nfor structure:\nstring
Cause: The _attributes property of the indicated Directory_Entry structure did not
match the _attributes property of the corresponding file.
ADVM-07341: starting disk offset string exceeds ending disk offset string
Cause: The starting storage map offset was greater than the ending offset.
Action: Re-enter the command with valid disk offsets.
ADVM-07342: Directory_Entry structure has incorrect filename for file\n found:
'string', but expected to find: 'string'\nfor structure:\nstring
Cause: The filename property of the indicated Directory_Entry structure did not
match the name of the file.
ADVM-07343: unused Directory_Entry structure has incorrect _name_len value\n
incorrect.
'string'\n found: number maximum: number\nfor structure:\nstring
Cause: The _rec_len property of the indicated Directory_Entry structure was greater
than the maximum value.
ADVM-00501 to ADVM-11111 4-99
'string'\n found: number minimum: number\nfor structure:\nstring
Cause: The _rec_len property of the indicated Directory_Entry structure was less than
the minimum value.
ADVM-07346: Directory_Entry structure has invalid _name_len value\n found:
number operating system maximum: number\nfor structure:\nstring
greater than the maximum value for this operating system.
ADVM-07347: Directory_Entry structure has incorrect _name_len value\n found:
greater than the maximum value for this entry.
ADVM-07350: command disabled due to lack of File_Entry_Table context; enter
'primary' or 'snap' to set context
Cause: The acfsdbg utility could not process the request because the File_Entry_Table
context was not set. The acfsdbg utility requires a valid File_Entry_Table context to
locate on-disk metadata structures.
Action: Enter 'primary' or 'snap snapshot name' command to set context.
ADVM-07351: requested Snap_Info_Entry structure not available due to
Services.
ADVM-07352: snapshot directory contains files with incorrect attributes;
attempting to continue processing
Cause: The _attributes property for a file in the indicated snapshot directory was
incorrect. The _attributes value indicated that the file was not a directory. All files in a
snapshot directory must be directories.
ADVM-07354: file has incorrect or invalid _attributes value\n found: string\n, but
Cause: The _attributes property of the indicated file was incorrect.
ADVM-07355: Cannot fix orphaned files because the lost+found directory is
damaged.
Cause: Fsck could not move the orphan files because there was an inconsistency with
the lost+found directory. Files that do not have a valid parent directory are
considered to be orphan files and are moved to the lost+found directory.
ADVM-07356: file is a symbolic link but has no storage for the target name \nfor
file:\nstring
Cause: The indicated file was a symbolic link but did have a target. The target of a
symbolic link must have storage.
ADVM-07360: deleting file due to invalid _attributes: string\nfile:\nstring
Cause: The _attributes property of the indicated file was invalid. The file must be
deleted in order to preserve the integrity of the file system.
ADVM-07361: truncating file 'string' to number bytes\nfor file:\nstring
Cause: The indicated file was truncated in order to preserve file system integrity.
ADVM-07363: Volume_Disk_Header has invalid _VolFeatureFlag values.\n found:
message.
Support Services.
ADVM-07364: file has incorrect values for Extent[number]\n found: _Length: string
_PhysicalDiskOffset: string\n, but expected to find: _Length: string
Cause: One or more or the extent properties of the indicated file was incorrect.
ADVM-00501 to ADVM-11111 4-101
ADVM-07365: extent metadata structure has incorrect values for Extent[number]\n
found: _FileOffset: string _Length: string _PhysicalDiskOffset: string \n, but
expected to find: _FileOffset: string _Length: string _PhysicalDiskOffset: string
Cause: One or more properties of the indicated extent metadata structure was
incorrect.
ADVM-07366: directory has incorrect _attributes value\n found: string\n, but
ADVM-07369: directory has invalid _FileSize value\n found: number minimum:
ADVM-07370: directory has invalid _FileSize: string _AllocationSize: string values
\nfor file:\nstring
Cause: The _FileSize and _AllocationSize properties of the indicated directory file
were incorrect.
ADVM-07374: cannot access directory _Private structure for block number at disk
Cause: An attempt to access the indicated directory _Private metadata structure
failed. Refer to the accompanying message(s) for more information on the problem.
ADVM-07375: directory _Private structure at disk offset: string contains invalid
data\nfor file:\nstring
Cause: The _Private structure of the indicated directory file contained invalid data.
ADVM-07376: directory _Private structure has incorrect header type at disk offset:
string, this file may not be a directory\n found: string, but expected to find: string
\nfor file:\nstring
Cause: The indicated file did not contain a _Private directory metadata structure as
required for directory files. It appeared that the file was incorrectly identified as being
a directory.
ADVM-07377: directory has invalid node list\nfor file:\nstring
Cause: The node list of the indicated directory file was invalid. There are three
structure header. 2. The _next_dirnode property of one or more of the file's directory
structures was incorrect. 3. The _first_dirnode property of the _Private directory
ADVM-07378: directory _Private structure has incorrect _last_dirnode value\n
found: number, but expected to find: number\nfor file:\nstring
incorrect.
ADVM-07379: directory has invalid free block list\nfor file:\nstring
Cause: The free block list of the indicated directory file was invalid. There are three
structure header. 2. The _next_free_dirnode property of one or more of the file's
directory structures was incorrect. 3. The _dir_entry_free_list_head property of the
_Private directory structure was incorrect.
ADVM-07381: directory _Private structure has incorrect _dir_entry_free_list_tail
Cause: The _ dir_entry_free_list_tail property of the indicated _Private directory
ADVM-07382: directory has invalid hash block free list; invalid reference for free
hash block\n found: number maximum: number\nfor file:\nstring
Cause: The hash block free list of the indicated directory file was invalid. There are
two possible causes: 1. The _hash_blk_free_list property of the _Private directory
structure referenced a block that exceeded the directory's size. 2. The _next_free_blk
property of a directory free block referenced a block that exceeded the directory's size.
ADVM-00501 to ADVM-11111 4-103
ADVM-07383: directory has invalid hash block free list\nfor file:\nstring
Cause: The free hash block list of the indicated directory file was invalid. There are
three possible causes: 1. One or more of the file's directory structures had an invalid
structure header. 2. The next_free_blk property of one or more of the file's directory
structures was incorrect. 3. The hash_blk_free_list property of the _Private directory
ADVM-07384: snapshot: string (identifier: number) has invalid
_SnapIncarnationNumber\n found: 0, but expected to find: > 0\nfor structure:
\nstring
message.
Support Services.
ADVM-07385: directory has orphan Directory_Node metadata structure for block
Cause: The indicated directory file had a Directory_Node metadata structure that was
not found on any directory node list.
ADVM-07386: directory has incorrect _FileSize value\n found: string, but expected
ADVM-07388: directory contains invalid _Private structure for block number at disk
Cause: A _Private metadata structure of the indicated directory file was found in the
wrong block. _Private metadata structures must be located at block one of a
directory's metadata.
ADVM-07389: directory has orphan free block number at disk offset: string\nfor
file:\nstring
Cause: The indicated directory file had a free block that was not found on the
directory's free list.
ADVM-07391: directory has invalid metadata structure string type for block number
Cause: The structure found at the block of the indicated directory file was not a valid
directory metadata structure.
ADVM-07392: Directory_Entry has incorrect or invalid _attributes value\n found:
string\n, but expected to find: string\nfor file:\nstring
Cause: The _attributes property of the indicated Directory_Entry was incorrect.
ADVM-07395: directory has incorrect or invalid _attributes values\n found: string
\n, but expected to find: string\nfor file:\nstring
ADVM-07396: directory has incorrect Hash_Table data\nfor file:\nstring
Cause: The Hash_Table of the indicated directory file contained inconsistent data.
ADVM-07399: directory has incorrect _LinkCount value\n found: number, but
Cause: The _LinkCount property of the indicated directory file was incorrect.
ADVM-07400: mismatch between _NOLSTXPTR feature and _NOUPHDRPTR
feature\n _NOLSTXPTR: string _NOUPHDRPTR: string\nfor file:\nstring
message.
Support Services.
ADVM-07401: write failed for Deferred_Remove_File_List metadata structure at
disk offset: string size: number bytes\nstructure type: string \nfor file:\nstring
Cause: An attempt to write metadata on the indicated file failed. Refer to
ADVM-00501 to ADVM-11111 4-105
ADVM-07402: Deferred_Delete_Storage_List structure has invalid delete list
pointers: _PrevDeferredListLink: string _NextDeferredListLink: string\nfor
structure:\nstring
Cause: The _PrevDeferredListLink or _NextDeferredListLink property of of the
indicated structure were incorrect. Both values must be zero or non-zero.
ADVM-07403: write failed for Deferred_Remove_Storage_List metadata structure
at disk offset: string size: number bytes\nstructure type: string \nfor file: \nstring
Cause: An attempt to write metadata of the indicated failed. Refer to accompanying
ADVM-07407: Snap_Map_Header contains invalid _SnapCreatePending field
Services.
ADVM-07408: Snap_Map_Header contains invalid _SnapDeletePending field
Services.
ADVM-07411: snapshot metadata checking will be limited due to an error reading
snapshot metadata
Cause: An attempt to read snapshot metadata failed. Snapshot validation was limited
since not all snapshot metadata was not available.
ADVM-07413: unable to create internal structure needed for processing
Cause: Refer to the accompanying message(s) for more information on the problem.
ADVM-07414: snapshot: string (identifier: number) has invalid snap_map_tuples

for file:\nstring
message.
Support Services.
ADVM-07415: invalid snap_map_tuple: ( string, string ) for disk offset: string
message.
Support Services.
ADVM-07416: file has invalid _FileSize value\n found: string minimum: string
\nfor file:\nstring
Cause: The _FileSize property of the indicated file was invalid.
ADVM-07417: Snap_Map_Header structure has invalid _snap_incarnation values;
_SnapHighestActiveIncarnNumber: number must be less than
_SnapNextIncarnationNumber: number\nfor structure:\nstring
Cause: One or both of the _SnapHighestActiveIncarnNumber and
_SnapNextIncarnationNumber properties of the indicated Snap_Map_Header
ADVM-07418: Snap_Map_Header structure has invalid _SnapCreatePending value
Cause: The _SnapCreatePending property of the indicated Snap_Map_Header
metadata structure was incorrect. The _SnapCreatePending value must be zero or less
ADVM-07419: Snap_Map_Header structure has invalid _SnapDeletePending value
Cause: The _SnapDeletePending property of the indicated Snap_Map_Header
metadata structure was incorrect. The _SnapDeletePending value must be zero or less
ADVM-00501 to ADVM-11111 4-107
ADVM-07420: found partially created snapshot for snapshot: 'string'
the system.
ADVM-07421: found partially deleted snapshot
system.
ADVM-07423: snapshot 'string' has invalid file identifier\n found: string
maximum: string\nfor structure:\nstring
ADVM-07424: snapshot 'string' has invalid _SnapIncarnationNumber value\n
Cause: The _SnapIncarnationNumber property of the indicated snapshot was invalid.
ADVM-07425: snapshot (_snapid value: string) has invalid name: 'string'\nfor
structure:\nstring
ADVM-07426: snapshot 'string' has invalid _SnapVisibility value\n found: number,
but expected to find: number or number\nfor structure:\nstring
ADVM-07427: duplicate _SnapIncarnationNumber: number found for snapshots

'string' and 'string'
same value. _SnapIncarnationNumber values must be unique across all snapshots.
ACFS Fixer to resolve the problem. The ACFS Fixer will delete the second snapshot.
ADVM-07429: Snap_Map_Header structure has incorrect _SnapCount value\n
Cause: The _SnapCount property of the indicated Snap_Map_Header metadata
structure was incorrect. The _SnapCount value did not match the number of valid
snapshots found.
ADVM-07430: cannot determine free space for volume associated with directory
'string'; attempting to continue with current directory 'string'
was targeted for the indicated directory. The ACFS Checker was unable to determine
Action: No further action is needed. The ACFS Checker/Fixer will attempt to
continue processing with the current directory.
ADVM-07431: cannot determine free space for volume associated with current
directory 'string'
was targeted for the current directory. The ACFS Checker was unable to determine
ADVM-07432: insufficient space available to store temporary file in\ndirectory
'string' or directory 'string'\nspace needed: number bytes\n- unable to continue
Cause: A temporary file is needed to store information during processing but there
was not enough space to store the file in either of the The size of this file is dependent
on the size of the file system. indicated directories.
Action: Provide sufficient space as described in the message to store the the
temporary file in either of the indicated directories. Rerun the ACFS Checker/Fixer
once there is sufficient storage to store the temporary file.
ADVM-07435: invalid path name length for temporary file\n length: number
minimum: number maximum: number
Cause: The path name for a temporary file does not exist or its length exceeds the
maximum for this system. Refer to the accompanying message(s) for more
ADVM-00501 to ADVM-11111 4-109
ADVM-07436: string has encountered an internal error: invalid parameter passed to

fb_create
ADVM-07437: string has encountered an internal error: invalid parameter passed to
fb_ref\n disk offset: string size: string fbSize: string fbCacheSize: string
ADVM-07438: file has storage allocated to it that is also allocated to another file
\nfor file:\nstring
Cause: Storage allocated to the indicated file was also allocated to at least one other
file. Storage can only be allocated to a single file. Storage can never be allocated to
multiple files.
ADVM-07439: Snapshot_BitMap conflicts with the Global_BitMap for disk offset:
string
Cause: One or more snapshot bitmaps claimed storage that was also claimed by the
Global_BitMap.
ACFS Fixer to resolve the problem. The ACFS Fixer will remove all snapshots whose
bitmap conflicts with the Global_BitMap.
ADVM-07440: Snapshot_BitMap has bit set for non-existing snapshot for disk
offset: string
Cause: One or more bitmaps reserved for unused snapshot incorrectly claimed
storage. Bitmaps for snapshots that are not in use cannot claim any storage.
ADVM-07441: Snapshot_BitMap has bits set for storage at disk offset: string that is
beyond the file system size
Cause: One or more snapshot bitmaps incorrectly claimed storage that exceeded the
ADVM-07443: Global_BitMap has invalid value for number of bits set\n found:
Cause: The Global_BitMap property that indicates the number of bits set exceeded the
size of the bitmap.
ADVM-07444: Global_BitMap has invalid value for number of bits set.\n found:
Cause: The Global_BitMap property that indicates the number of bits set did not
match the amount of storage allocated to all valid files.
ADVM-07445: Global_BitMap has invalid value for next offset to search\n found:
Cause: The Global_BitMap property that indicates the next offset to search for
available bits to allocate exceeded the size of the bitmap.
ADVM-07446: mismatch between temporary Global_BitMap and on-disk
Global_BitMap
Cause: The temporary Global_BitMap that was populated by traversing all valid file
system data did not match the on-disk copy of the Global_BitMap.
ADVM-07447: invalid snap_map_tuple for disk offset: string\n found: ( 0, 0 ), but
expected non-zero values\nfor file:\nstring
message.
Support Services.
ADVM-07448: invalid snap_map_tuple for disk offset: string\n found: ( 0, 0 ), but
expected non-zero values
message.
Support Services.
ADVM-07449: snapshot 'string' storage bitmap is incorrectly set for disk offset:
string
Cause: The bitmap of the indicated snapshot claimed storage that was allocated to
allocated file. Storage can only be allocated to a single file. Storage can never be
allocated to multiple files.
ADVM-00501 to ADVM-11111 4-111
ADVM-07450: snapshot 'string' storage bitmap is not set for disk offset: string
Cause: The bitmap of the indicated snapshot did not claim storage that was allocated
to one of its files. A snapshot's bitmap must claim all storage allocated to its files.
ADVM-07451: snapshot 'string' storage bitmap is incorrectly set for disk offset:
string with no corresponding file data
Cause: The bitmap of the indicated snapshot claimed storage but the storage was not
allocated to any file.
ADVM-07452: unable to locate directory for snapshot 'string' (id: number)\n
processing will continue for other snapshots
Cause: The directory of the indicated snapshot was not found. This snapshot could
not be processed.
ADVM-07453: Snap_Root_Directory file identifier for snapshot 'string' was
incorrect\n found: string, but expected to find: string\nfor structure:\nstring
Cause: The Snap_Root_Directory file identifier property of the indicated snapshot
was incorrect.
ADVM-07455: unable to open file: string
Cause: An attempt to open a file failed. Refer to the accompanying message(s) for
ADVM-07458: The request to cancel string was incomplete because volume string
was not accessible. The file system cannot be mounted in this state.\nRerun string
once the volume is accessible to enable file system mounts.
Cause: The ACFS Checker/Fixer could not reset the volume to allow for file system
mounts because the volume was not accessible. Refer to the accompanying message(s)
for more information on the error.
Action: Rerun the ACFS Checker/Fixer once the volume is accessible to enable file
system mounts.
ADVM-07459: Volume_Label metadata structure has invalid _VolLabelLength

Cause: The _VolLabelLength property of the indicated Volume_Label metadata
ADVM-07460: Volume_Label metadata structure has invalid _VolIDLength value
Cause: The _VolIDLength property of the indicated Volume_Label metadata structure
exceeded the maximum value.
ADVM-07461: Volume_Label metadata structure has invalid _ClusterNameLength
Cause: The _ClusterNameLength property of the indicated Volume_Label metadata
ADVM-07462: file has incorrect or invalid _attributes values\n found: string\n
valid values: string\nfor file:\nstring
Cause: The _attributes property of the indicated file contained invalid and/or
incorrect values.
ADVM-07464: file has invalid _attributes value\n found: string\nfor file:\nstring
Cause: The _attributes property of the indicated file contained invalid values. These
values are not supported on Windows systems.
ADVM-07465: file has _attributes set that are mutually exclusive\n found: string
\nfor file:\nstring
Cause: The _attributes property of the indicated file describe more than one type of
file. File types are mutually exclusive.
ADVM-07466: file has no _attributes value\nfor file:\nstring
Cause: The _attributes property of the indicated file did not describe a file type. The
_attributes property must describe a valid file type.
ADVM-00501 to ADVM-11111 4-113
ADVM-07467: metadata structure has a non-zero value for field: string\nfor
structure:\nstring
Cause: The indicated ACFS metadata structure had a reserved or unused field that
contained a non-zero value. The field was overwritten or was not initialized correctly.
ADVM-07468: file has invalid _SynchFlags value\n found: string\nfor file:
\nstring
Cause: The _SynchFlags property of the indicated file contained values that were not
within the range of valid values.
ADVM-07469: file cannot be modified; _SynchFlag value:\n found: string\nfor
file:\nstring
modified.
ADVM-07470: file cannot be accessed; _SynchFlag value:\n found: string\nfor file:
\nstring
accessed.
ADVM-07471: file incorrectly marked for deletion with _SynchFlag value:\n
found: string\nfor file:\nstring
Cause: The _SynchFlag property of the indicated file incorrectly identified the file as
marked for deletion while it was still part of a valid directory.
ADVM-07474: invalid program name\n found: string, but expected to find: string
or string
Cause: The ACFS Checker/Fixer or Debug utility has been renamed to a value that is
not recognized.
Action: Rename the program to the corresponding value listed in the message and
rerun the program.
ADVM-07481: An I/O error occurred while reading ACFS metadata, some snapshot
metadata checks will not be performed.
Cause: The I/O error prevented full snapshot checking because required ACFS
metadata was not available. Refer to the accompanying message(s) for more
ADVM-07482: snapshot string with _snapid value: string has invalid parent
snapshot with _snapid value: string
ADVM-07483: snapshot with _snapid value: string has invalid ancestor snapshot
ADVM-07484: valid ACFS volume path name required
Cause: A valid volume path name was not entered.
Action: Rerun the ACFS Checker/Fixer or Debug utility with a valid ACFS volume
path name as the final argument.
ADVM-07485: unable to determine temporary directory
Cause: An attempt to determine the system's temporary directory failed. For UNIX
systems this directory is either "/usr/tmp" or "/tmp". For Windows systems this
directory is the system's temporary folder. Refer to the accompanying message(s) for
ADVM-07486: unable to determine current directory
Cause: An attempt to determine the current directory failed. Refer to the
ADVM-07487: unable to open volume: string
Cause: An attempt to open a volume failed. Refer to the accompanying message(s) for
ADVM-07488: This volume is now in a mountable state. \nThe file system was not
checked before changing the volume's state. \nUse of this file system may
encounter serious errors since it has \nnot been checked.
Cause: The volume was forced into a mountable state without checking the integrity
of the file system. The file system may contain incorrect or invalid data.
Action: Run the ACFS Checker/Fixer before attempting to mount the file system.
ADVM-00501 to ADVM-11111 4-115
ADVM-07489: maximum number of passes: number exceeded, program terminating

Cause: There are two possible causes: 1. There is a problem with the file system that
the ACFS Fixer cannot repair. 2. The ACFS Fixer has encountered an internal
problem.
ADVM-07498: extent[number] has invalid _Length value\n found: string, but
Cause: The _Length property of an extent structure of the indicated file was invalid.
_Length values must be a multiple of the file system allocation unit size.
ADVM-07499: extent[number] has invalid _Length value\n found: string, but
Cause: The _Length property of an extent of the indicated extent structure was
invalid. _Length values must be a multiple of the file system allocation unit size.
ADVM-07500: extent[number] has invalid _FileOffset value\n found: string, but
Cause: The _FileOffset property of an extent structure of the indicated file was
ADVM-07501: extent[number] has invalid _FileOffset value\n found: string, but
Cause: The _FileOffset property of an extent of the indicated extent structure was
ADVM-07502: extent[number] has invalid _PhysicalDiskOffset value\n found:
string, but expected to find multiple of: string\nfor file:\nstring
ADVM-07503: extent[number] has invalid _PhysicalDiskOffset value\n found:
string, but expected to find multiple of: string\nfor structure:\nstring
ADVM-07504: snapshot with _snapid value: string has invalid ancestor snapshot
(_cycle)
ADVM-07505: metadata structure read failed at disk offset: string for structure:
string
Cause: An attempt to read the indicated metadata structure at the described disk
problem.
rerun the program.
ADVM-07519: Snap_Map_Header structure has invalid _SnapConvertPending
value\n found: number, but expected to find: less than number\nfor structure:
\nstring
Cause: The _SnapConvertPending property of the indicated Snap_Map_Header
metadata structure was incorrect. The _SnapConvertPending value must be zero or
less than the value indicated in the message.
ADVM-07520: Snap_Map_Info structure has invalid _SnapInfoFlags value\n
Cause: The _SnapInfoFlags property of the indicated Snap_Map_Info metadata
ADVM-07521: Snap_Map_Info structure has invalid _SnapAncestorIncarn value\n
ADVM-07522: snapshot: string (identifier: number) has invalid _SnapParentId:
number, parent snapshot does not exist
message.
ADVM-00501 to ADVM-11111 4-117
Support Services.
ADVM-07523: snapshot: string (identifier: number) has invalid _SnapParentId
value\n found: number, but expected to find: 0\nfor structure:\nstring
message.
Support Services.
_SnapAncestorIncarn value\n found: number, but expected to find: 0\nfor
structure:\nstring
message.
Support Services.
_SnapAncestorIncarn value\n found: number, must be less than
ADVM-07526: Volume_Disk_Header has invalid _VolStateFlag values.\n found:
string,\n but expected to find: string \nfor structure:\nstring
ADVM-07527: Volume Disk Header has invalid VolFeatureFlag values \n found:
string \n string \n but expected to find: string \n string \n for structure:\nstring
message.
Support Services.
ADVM-07528: found partially created snapshot: string (identifier: number)

the system.
ADVM-07529: found partially deleted snapshot: string (identifier: number)
system.
Action: n/a
ADVM-07530: snapshot: string (identifier: number) has invalid file identifier\n
found: string maximum: string\nfor structure:\nstring
ADVM-07531: snapshot: (identifier: number) has invalid name: 'string'\nfor
structure:\nstring
ADVM-07532: snapshot: string (identifier: number) has invalid _SnapVisibility
value found: number, but expected to find: number, number or number\for structure:
\nstring
ADVM-07533: duplicate _SnapIncarnationNumber: number found for the following
snapshots:\n
same value. _SnapIncarnationNumber values must be unique.
Support Services.
ADVM-00501 to ADVM-11111 4-119
ADVM-07534: request for disk offset: string exceeds the size for this file system:
string
Cause: A request was made for a disk offset that exceeded the size of the file system.
Action: Reenter the command with a disk offset that is within the limits of the file
system.
ADVM-07536: snapshot: string (identifier: number) has invalid parent snapshot
identifier: number, maximum: number\nstructure:\nstring
ADVM-07537: snapshot: string (identifier: number) has invalid ancestor snapshot:
string (identifier: number)
ADVM-07538: snapshot: string (identifier: number) has invalid ancestor snapshot
(_cycle)
ADVM-07539: Snap_Map_Info structure has invalid _SnapAncestorIncarn value\n
found: number\nfor structure:\nstring
ADVM-07540: deleting snapshot: string (identifier: number) to maintain file system
integrity
ADVM-07541: Snap_Map_header has invalid value for SnapMapFlags\n found:
string\n string\n but expected to find: string\n string\nfor structure: string
message.
Support Services.
ADVM-07570: snap_map_tuple for disk offset: string conflicts with primary file
system\n found: ( string, string )\n expected: ( 0, 0 )
message.
Support Services.
ADVM-07571: snap_map_tuple for disk offset: string not set in Global BitMap\n
message.
Support Services.
ADVM-07572: invalid snap_map_tuple found for for disk offset string,\nfirst value
must be less than or equal to second value\n snap_map_tuple: ( string, string )
message.
Support Services.
ADVM-07573: orphan snap_map_tuple found for for disk offset string\n
message.
Support Services.
ADVM-07575: command takes no arguments
Cause: The command entered does not take any arguments.
Action: Reenter the command with no arguments.
ADVM-07585: unable to set File_Entry_Table context
Cause: The ACFS Debug utility was not able to set the File_Entry_Table context.
Lookups by file identifier were disabled. Refer to the accompanying message(s) for
more information on the problem.
Action: Correct the problem described in the accompanying messages if possible by
rerunning the ACFS Fixer.
ADVM-00501 to ADVM-11111 4-121
ADVM-07586: Do you want to continue [y|n] ?

Cause: The ACFS Checker/Fixer or Debug utility detected a situation that could leave
the file system in an inconsistent or unusable state. Refer to the corresponding error
message for more information.
ADVM-07588: metadata read failed at disk offset: string size: string bytes \ncannot read beyond file system size: string
Cause: An attempt to read metadata failed because the data requested was beyond
the size of the file system.
ADVM-07590: metadata write failed at disk offset: string size: string bytes\ncannot write beyond file system size: string
Cause: An attempt to write metadata failed because the write location was beyond the
Action: The ACFS Fixer will resolve the problem. No further action is needed.
ADVM-07592: metadata structure has incorrect header for:\nstring
Cause: One or more properties of the header of the indicated metadata structure
contained invalid or incorrect values. Refer to accompanying messages for more
ADVM-07601: unable to determine size of file: string
Cause: An attempt to determine the size of the indicated file failed. Refer to the
ADVM-07602: failed to create temporary paging file 'string'
Cause: An attempt to create the indicated temporary paging file failed. Refer to the
ADVM-07603: write failed at position: string for temporary paging file 'string'
Cause: An attempt to write to the indicated temporary paging file failed. Refer to the
ADVM-07604: seek failed at position: string for temporary paging file 'string'
Cause: An attempt to seek within the indicated temporary paging file failed. Refer to
ADVM-07606: read failed at position: string for temporary paging file 'string'
Cause: An attempt to read the indicated temporary paging file failed. Refer to the
Cause: An attempt to read metadata at the indicated offset was incomplete. The
amount of data read did not match the amount requested. Refer to the accompanying
ADVM-07611: Global_BitMap has bits incorrectly set for storage beyond the file
system size\nfor file:\nstring
Cause: The Global_BitMap had bits set in an area reserved for future expansion. All of
these storage bits must be zero. There is no valid storage associated with these bits.
ADVM-07612: file has invalid _NextFreeExtent value:\n found: number minimum:
ADVM-07613: file has invalid _NextFreeExtent value:\n found: number maximum:
ADVM-07614: Global_BitMap's first extent is not located at the expected disk
offset\n found: string, but expected to find: string\nfor file:\nstring
Cause: The first extent of the indicated Global_BitMap was not located at the correct
disk offset. The Global_BitMap's first extent must be located at the disk offset
described in the message.
ADVM-00501 to ADVM-11111 4-123
ADVM-07615: Global_BitMap file has extents that overlap\n Extent[number]

_Length: string _PhysicalDiskOffset: string\n Extent[number] _Length: string
Cause: The extents of the indicated Global_BitMap mapped some or all of the same
storage. All extents within a file must map storage that is mutually exclusive.
ADVM-07616: string has encountered an internal error: could not post error to
ACFS Fixer
unexpected, internal error. Refer to the accompanying message(s) for more
ADVM-07619: truncating file from number bytes to number bytes to ensure
metadata consistency; file content following file offset: number has been lost\nfor
file:\nstring
Cause: The ACFS Fixer was not able to fully repair the indicated file due to an
inconsistency within its metadata. The file had to be truncated to maintain the
integrity of the file system.
ADVM-07622: resetting _security_descriptor to administrator default value for:
\nfor file:\nstring
Cause: The _security_descriptor the indicated file was invalid or incorrect. It was reset
to the default administrator value.
ACFS Fixer will reset the _security_descriptor to the administrator default value for
the file.
ADVM-07623: unable to repair problem with file _attributes; deleting file to
maintain file system integrity\nfor file:\nstring
Cause: The ACFS Fixer was not able to resolve a problem with the _attributes
property of the indicated file. The file had to be deleted to maintain the integrity of
the file system.
ADVM-07624: file cannot be repaired; deleting file to maintain file system integrity
\nfor file:\nstring
Cause: The ACFS Fixer was not able to repair a problem with the indicated file. The
file had to be deleted to maintain file system integrity.
ADVM-07625: failed to create system directory\nfor file:\nstring
Cause: The ACFS Fixer was not able to create a directory for the indicated internal
system file. Refer to the accompanying message(s) for more information on the
problem.
ADVM-07628: invalid snapshot name 'string' entered

Cause: The snapshot entered did not exist.
Action: Enter the name of a valid snapshot to continue.
ADVM-07629: numeric argument too large: number
Cause: The numeric value entered as an argument exceeded the largest possible value
for this type of argument.
Action: Enter a value that is within the valid range of values for the type of argument.
ADVM-07647: local extent limit reached for extending files; indirect extents not
supported for extending files\nfor file:\nstring
Cause: The ACFS Fixer was not able to create an indirect extent to extend the
indicated file.
ADVM-07648: cannot set Global_BitMap bits for offset: string for number bytes
\nfor file:\nstring
Cause: The ACFS Fixer was unable to set the range of bits described in the message.
ADVM-07649: deleting snapshot to maintain file system integrity
ADVM-07650: unable to repair _VolStateFlag value in Volume_Disk_Header
Cause: The ACFS Fixer was unable to update the _VolStateFlag in the
Volume_Disk_Header. Refer to the accompanying message(s) for more information
on the problem.
ADVM-07652: Volume_Disk_Header has invalid _VolOSCreatedOn value\n
found: number, but expected to find: 1 (Windows_XP), 2 (Linux), 3 (Solaris), or 4
(AIX)\nfor structure:\nstring
Cause: The _VolOSCreatedOn property of the indicated Volume_Disk_Header was
incorrect. Its value must be one of the values listed in the message.
ADVM-07653: Security_Metadata file _Private structure has invalid
_freeDataListTail value\n found: 0, but expected to find: > 0\nfor structure:
\nstring
Cause: The _freeDataListTail property of the indicated Security_Metadata _Private
metadata structure was invalid. The value must be greater than zero.
ADVM-00501 to ADVM-11111 4-125
ADVM-07655: This file system had been removed. It has now been restored.
Cause: This file system was removed via the acfsutil rmfs utility. It has now been
restored by the ACFS Fixer.
Action: The ACFS Fixer has restored the file system. No further action is required.
ADVM-07656: unable to continue
Cause: The ACFS Checker/Fixer or Debug utility has encountered a fatal error and
cannot continue. Refer to the accompanying message(s) for more information on the
error.
ADVM-07658: Ensure that volume string is not mounted on this node. \nNote that
data displayed may not be current if volume string is mounted on any other node
due to file system caching
Cause: The volume cannot be mounted on this node while running the acfsdbg utility
in read-only mode. This restriction is limited to Windows systems. The acfsdbg utility
reads metadata directly from disk and data may not be current if the file system is
mount on any other nodes due file system caching.
Action: Check to determine if the volume is mounted on any node. The volume must
be unmounted on this node before continuing. The volume should also be
unmounted on all others node if possible. If the volume cannot be unmounted on
other nodes, then reenter any request if the metadata values displayed appear to be
stale. Note: You may have to reenter the request several times to retrieve the latest
metadata.
ADVM-07659: command is disabled in read-only mode
Cause: The command entered attempted to modify file system metadata while
running in read-only mode. Modifications to file system metadata are not allowed
when running the ACFS Debug utility in read-only mode.
Action: Rerun the acfsdbg utility in write mode to modify metadata.
ADVM-07660: unable to modify metadata for volume string; volume is not open
Cause: An attempt to modify metadata failed because the volume was not open. Refer
ADVM-07661: metadata lookup by file identifier is disabled due to lack of
File_Entry_Table context; enter 'primary' or 'snap snapshot name' to set the context
Cause: The acfsdbg utility could not process the request because there was no
File_Entry_Table context. The acfsdbg utility requires a valid File_Entry_Table
context for lookups by file identifier since the same file identifier may appear in
multiple snapshots.
ADVM-07662: unable to set snapshot context due to Snap_Map file metadata

inconsistency
Cause: An attempt to set the metadata lookup context to a snapshot failed because
there was a problem accessing the SnapMap metadata. Refer to the accompanying
ADVM-07663: disk offset request: string is not aligned on a sector: number bytes;
results may be inconsistent
Cause: The disk offset entered was not sector aligned. All ACFS metadata structures
are sector aligned.
Action: Reenter the offset so that is properly aligned as described in the
corresponding message.
ADVM-07664: read failed for metadata structure at disk offset: string for number
bytes
Cause: An attempt to read a metadata structure at the indicted disk offset failed. Refer
ADVM-07666: unrecognized metadata found at disk offset: string
Cause: The data found at the indicated disk offset did not contain a valid ACFS
metadata structure type. There are two possible causes: 1. The data at the disk offset
was not an ACFS metadata structure. 2. The metadata structure at the disk offset was
Action: If the data at the disk offset should be an ACFS metadata structure, then run
the ACFS Fixer to resolve the problem.
ADVM-07667: request for file identifier: string exceeds the maximum value for this
file system: string
Cause: A request was made for a file identifier that exceeded the maximum for the file
system.
Action: Reenter the command with a file identifier that is within the limits of the file
system.
ADVM-07669: metadata lookup by file identifier is disabled due to
File_Entry_Table metadata inconsistency
Services.
ADVM-07685: string is unable to detect the ACFS driver on this system.
\nProceeding could leave the file system in an inconsistent and possibly
\nunusable state if the file system is mounted or being fixed on another system.
ADVM-00501 to ADVM-11111 4-127
system is not mounted or being fixed on any node. Rerun the ACFS Checker/Fixer or
Debug utility once these steps are complete.
ADVM-07690: data displayed may not be current if volume string is mounted on
any node due to file system caching
Cause: The acfsdbg utility reads metadata directly from disk. Metadata updates to
disk may be delayed due standard file system caching.
Action: Check to determine if the volume is mounted on any node. Unmount the
volume on all nodes if possible. If the volume cannot be unmounted from all nodes,
then reenter any request if the metadata values displayed appear to be stale. Note:
You may have to reenter a request several times to retrieve the latest metadata.
ADVM-07691: command entered: 'string' is invalid or not unique
Cause: There are two possible causes: 1. The command entered was not recognized by
the acfsdbg utility. 2. A partial command name was entered and there was more than
one command that matched the characters entered.
Action: Use the acfsdbg utility help (-h) option for a list of valid commands. Renter
the command, ensuring that enough of the command name is entered to make it
unique.
ADVM-07692: cannot convert disk offset as specified: string
Cause: The format entered for the disk offset was invalid.
ADVM-07693: Volume_Disk_Header has invalid _VolVolumeSize value\n found:
string must be aligned on a number byte boundary\nfor structure:\nstring
Cause: The _VolVolumeSize property of the Volume_Disk_Header was invalid. Its
value must be aligned on the byte boundary described in the message.
ADVM-07694: too many arguments for string
Cause: Too many arguments were supplied for the string option. The string option
takes one argument.
Action: Reenter the command with only one argument for the string option.
ADVM-07695: The ACFS driver should be loaded on all nodes for a safe check of
this file system.
system is not mounted or being checked on any node. Rerun the ACFS Checker/Fixer
or Debug utility once these steps are complete.
ADVM-07696: The file system on volume string is currently in the string state. This
state indicates that a file system check is currently in progress.
Cause: There are two possible causes: 1. The file system on this volume was being
checked on this system or another system in the cluster. 2. The ACFS Checker/Fixer
was unexpectedly terminated leaving the file system state incorrectly set.
Action: Verify that the file system is not being checked on any node. There are a two
possible options if the file system is not being checked on any node: 1. Respond Y(yes)
when prompted to run the ACFS Checker/Fixer. 2. Run the ACFS Fixer with the [f]
option to reset the file system state to allow the file system to be mounted. NOTE: Use
caution with this option as file system repairs from a previous run of the ACFS
Checker/Fixer may be incomplete.
ADVM-07697: unable to determine program name
Cause: The ACFS Checker/Fixer or Debug utility was invoked in a non-standard way
such that the program name could not be determined.
Action: Run the ACFS Checker/Fixer or Debug utility using a standard method.
ADVM-07698: orphan directory found for file identifier: string at disk offset: string
Cause: No parent directory entry was found for the indicated directory file. 1. The
directory file had no corresponding parent directory entry. 2. The directory file had a
parent directory entry, but there was a problem with corresponding parent directory
file.
directory file that does not have a valid parent directory entry following directory
repairs will be moved to the 'lost+found' directory with all of its files.
ADVM-07701: There are metadata transaction log file(s) that have not been
processed. Failure \nto process these transaction logs may result in metadata
inconsistencies. \nDo you want to process the transaction log(s)? [y|n]
Cause: Transaction Log files contain updates to the file system's metadata. The ACFS
Checker found at least one transaction log that was not completely processed. This
indicates that metadata updates were not completed which could leave the file system
Action: Respond yes to process metadata transaction log(s).
ADVM-07705: There are files marked for deletion that have not been removed from
the \nfile system. Failure to remove these files could result in false errors \nbeing
reported. \nDo you want to remove files that are marked for deletion? [y|n]
Cause: The ACFS Checker found files that were marked for deletion but had not been
removed from the file system. False errors may be reported due to the presence of
there files.
Action: Respond yes to remove these files.
ADVM-07708: unable to read File_Entry_Table entry: string at disk offset: string
Cause: An attempt to read the File_Entry_Table for the indicated entry failed. Refer to
ADVM-07709: orphan file (file identifier: string, disk offset: string) marked for
deletion not on delete list
Cause: The indicated file was marked for deletion but it was not found on any of the
delete file lists.
ADVM-00501 to ADVM-11111 4-129
ADVM-07710: orphan file found for file identifier: string at disk offset: string
Cause: No directory entry was found for the indicated file. There are two possible
causes: 1. The file had no corresponding directory entry. 2. The file had a directory
entry, but there was a problem with corresponding directory file.
file that does not have a valid directory entry following directory repairs will be
moved to the 'lost+found' directory.
ADVM-07711: orphan metadata structure (type: string) found for file identifier:
Cause: The indicated metadata structure was found but had no corresponding parent
metadata structure.
ACFS Fixer will move the structure to the free list. If the ACFS Checker is running,
then run the ACFS Fixer to resolve the problem.
ADVM-07720: new allocation size is invalid\n found: number, but expected to find
multiple of: number\nfor file:\nstring
Cause: The new allocation size property of the indicated file was incorrect. Its value
must be a multiple of the file system allocation unit size.
ADVM-07721: file has invalid _NextFreeExtent value\n found: number maximum:
ADVM-07722: file has invalid _NextFreeExtent value:\n found: number minimum:
1\nfor file:\nstring
ADVM-07723: could not clear temporary Global_BitMap bits at offset: string for
number bits
Cause: The ACFS Fixer was unable to free the indicated storage on the temporary
Global_BitMap.
ADVM-07724: unable to set temporary Global_BitMap bits at offset: string for
number bits
Cause: The ACFS Fixer was unable to reserve the indicated storage on the temporary
Global_BitMap.
ADVM-07725: unable to allocate storage; file system has no free space

Cause: The ACFS Fixer was unable to allocate storage because there was no free
storage available.
command.
ADVM-07726: could not find sufficient free storage to rebuild Global_BitMap
extent\n found: string requested: string\nfor file:\nstring
Cause: The ACFS Fixer could not find enough contiguous storage to rebuild the
Global_BitMap file's extent map.
command.
ADVM-07727: could not rewrite Global_Bitmap data for file:\nstring
Cause: The ACFS Fixer could not update the file system's storage bitmap. Refer to the
rerun the ACFS Fixer.
ADVM-07728: The Global_BitMap file has reached the maximum number of
extents (number). The file system can no longer be expanded. Running string in
fixer mode will attempt to consolidate the storage bitmap into fewer extents which
would allow for file system expansion via the 'acfsutil size' command.
Cause: The ACFS Checker found the file system's storage bitmap was using its
maximum number of extents.
Action: Running the ACFS Checker/Fixer in Fixer mode will attempt to consolidate
the file system's storage bitmap into two extents allowing future file system
expansion using 'acfsutil size', assuming additional storage is available.
ADVM-07729: The Global_Bitmap file has been\n consolidated into number
extents.\nThis may allow for file system expansion via the 'acfsutil size' command.
Cause: The Global_Bitmap file was using the maximum number of extents supported.
The ACFS Fixer has consolidated the Global_Bitmap file into fewer extents thus
allowing future file system growth using the 'acfsutil size' command if unused
storage is available.
Action: No Action Needed.
ADVM-07733: directory _Private structure has invalid _first_dirnode value\n
Cause: The _first_dirnode property of the indicated _Private directory structure was
ADVM-07734: directory _Private structure has invalid _last_dirnode value\n
ADVM-00501 to ADVM-11111 4-131
ADVM-07735: directory _Private structure has invalid _hash_blk_free_list value\n
Cause: The _hash_blk_free_list property of the indicated _Private directory structure
ADVM-07736: directory _Private structure has invalid _dir_entry_free_list_head
Cause: The _dir_entry_free_list_head property of the indicated _Private directory
ADVM-07737: directory _Private structure has invalid _dir_entry_free_list_tail
Cause: The _dir_entry_free_list_tail property of the indicated _Private directory
ADVM-07740: Could not consolidate the file system's temporary\n storage bitmap
to less than number extents. Need\n at least number bytes free contiguous storage.
Cause: The file system's internal storage bitmap could not be consolidated to less than
five extents because there was insufficient free contiguous storage.
ADVM-07741: could not rebuild file system storage bitmap\n free contiguous
bytes found: number\n contiguous bytes requested: number\nfor file: string
Cause: The ACFS Fixer could not find enough contiguous free storage to rebuild the
file system's storage bitmap.
ADVM-07742: _ustEAContainerEntry property has an invalid value\n found:
Cause: The _ustEAContainerEntry property of the indicated _ustEAContainer
structure was not within the range of valid offset values.
information.
ADVM-07743: _ustEAEntryHdrFlags property has an invalid value\n found: string
for _ustEAContainerEntry at offset: string for structure:\nstring
Cause: The _ustEAEntryHdrFlags property of the indicated _ustEAContainer
structure contained one or more invalid values.
ADVM-07744: _ustEAEntryHdrNextFreeOffset property has an invalid value\n
found: number, but expected to find: number for _ustEAContainerEntry at offset:
Cause: The _ustEAEntryHdrNextFreeOffset property of the indicated
_ustEAContainer structure was incorrect.
ADVM-07745: _ustEAEntryHdrNameLen property has an invalid value\n found:
number, but expected to find no greater than: number\n for _ustEAContainerEntry
at offset: string for structure:\nstring
structure was invalid. Its value exceeded the maximum length for an extended
attribute name or ACFS tag name.
ADVM-07746: ACFS tag name contains invalid syntax\n found: string for
_ustEAContainerEntry at offset: string for structure:\nstring
Cause: The _ustEAEntryName property of the indicated _ustEAContainerEntry
property in the _ustEAContainer structure contained invalid syntax for an ACFS tag
name.
ADVM-07747: _ustEAEntryValueLen property has an invalid value\n found:
number, but expected to find: number\n for _ustEAEntry offset: string for structure:
\nstring
the _ustEAEntryContainer structure contained an invalid value length.
ADVM-00501 to ADVM-11111 4-133

ADVM-07748: _ustEAEntryValue property has an invalid value\n found: string,
but expected to find: string\n for _ustEAEntry offset: string for structure:\nstring
Cause: The _ustEAEntryValue property of the indicated _ustEAEntry property in the
_ustEAEntryContainer structure contained an invalid value string for an ACFS tag
name.
ADVM-07749: _ustEAContainerHdrNextContainer property has an invalid value\n
found: string for structure:\nstring
Cause: The _ustEAContainerHdrNextContainer property of the indicated
_ustEAContainer structure contained an invalid offset value.
ADVM-07750: _ustEAContainerHdrNumEAEntries property has an invalid value
\n found: number, but expected to find: number for structure:\nstring
Cause: The _ustEAContainerHdrNumEAEntries property of the indicated
_ustEAContainer structure contained an incorrect count of valid entries.
ADVM-07751: Inconsistent amount of available space\n found: number, but
expected to find: number\n for structure:\nstring
ADVM-07752: _LocalTags property has invalid characters for _FileEntry:\nstring
Cause: The _LocalTags property of the indicted _FileEntry structure contained invalid
characters for ACFS tag names.
ADVM-07753: _ustEAEntry property offset: number is marked free\n but is missing
from the free list for structure:\nstring
ADVM-07754: _ustEAContainer property has inconsistent\n total free and
assigned _ustEAContainerEntry property space\n found: number, but expected to
find: number for structure:\nstring
Cause: The _ustEAContainer structure contained free and active
_ustEAContainerEntry property entries that indicate its total space exceeded the size
of a _ustEAContainer structure.
ADVM-07755: _ustEAContainerHdrNextFreeOffset property has an invalid value
\n found: number, but expected to find less than: number for structure:\nstring
Cause: The ustEAContainerHdrNextFreeOffset property of the indicated
information.
ADVM-07756: _ustEAEntryHeader.ustEAEntryHdrNextFreeEAOffset property has
an invalid value\n found: number, but expected to find less than: number for
_ustEAContainerEntry at offset: number for structure:\nstring
Cause: The _ustEAEntryHeader.ustEAEntryHdrNextFreeEAOffset property of the
indicated _ustEAContainerEntry property for the _ustEAContainer structure was not
within the range of valid offset values.
information.
ADVM-07757: file extended attribute container structure exceeds file system size:
string\n _Length: string\nfor structure:\nstring
Cause: The extended attribute container structure of the indicated file referenced meta
data beyond the size of the file system. There are two possible causes: 1. The extended
attribute container structure disk offset was incorrect. 2. The file system size value
was incorrect.
ADVM-00501 to ADVM-11111 4-135
ADVM-07758: _ustEAEntryHdrNameLen property has an invalid value\n found:

number, but expected non-zero value\n for _ustEAContainerEntry at offset: string
structure was invalid. Its value was zero but must be non-zero for an extended
attribute name entry.
ADVM-07759: _ustEAEntryValueLen property has an invalid value\n found:
number, but expected to find less than: number\n for _ustEAEntry offset: string for
structure:\nstring
the _ustEAEntryContainer structure contained an invalid value length that was larger
than expected for this structure.
ADVM-07760: _ustEAContainerHdrNextFreeOffset property has an invalid value
\n found: number, but expected to find: number for structure:\nstring
Cause: The _ustEAContainerHdrNextFreeOffset property of the indicated
information.
ADVM-07761: directory _Private structure has invalid _dir_bitmap_start value\n
Cause: The _dir_bitmap_start property of the indicated _Private directory structure
ADVM-07762: Directory contains invalid bitmap block number at disk offset: string
\nfor file:\nstring
Cause: A bitmap block of the indicated directory file was found in the wrong location.
Directory bitmap blocks must be located contiguously after the first bitmap block.
ADVM-07763: Directory bitmap is not contiguous from block number to block

Cause: A discontinuity was seen in the directory bitmap. Directory bitmap blocks
must be located contiguously after the first bitmap block.
ADVM-07764: Directory bitmap has incorrect last block\n found: number expected:
Cause: The directory bitmap does not end where expected.
ADVM-07765: Version 11.2.0.3 or earlier directory contains bitmap block number at
disk offset: string\nfor file:\nstring
Cause: The directory _Private structure indicates that the directory does not have a
bitmap, yet a bitmap block was found in the directory.
ADVM-07766: Directory bitmap does not match state of block number\n bitmap:
string block: string\nfor file:\nstring
Cause: The directory bitmap indicates an incorrect state for the directory block.
ADVM-07767: Directory bitmap contains non-zero value for bit number mapping
beyond end of directory:\nstring
Cause: The directory bitmap contains a non-zero bit in the range mapping blocks
beyond the end of the directory.
ADVM-07768: Directory _Private structure has invalid _dir_bitmap_size value\n
found: string minimum: string\nfor structure:\nstring
Cause: The _dir_bitmap_size property of the indicated _Private directory structure
was invalid. Its value did not meet the minimum value for the directory.
ADVM-07769: Number of bitmap blocks found does not match value of
_dir_bitmap_size in directory _Private structure\n found: number expected: number
Cause: The number of bitmap blocks in the directory does not match the number of
blocks that were expected.
ADVM-00501 to ADVM-11111 4-137
ADVM-07770: System directory _Private structure has invalid on-disk version\n
found: string expected: string\nfor structure:\nstring
Cause: The on-disk version of the indicated _Private directory structure was invalid.
ADVM-07771: directory _Private structure has invalid directory bitmap end value
Cause: The calculated end of the directory bitmap of the indicated _Private directory
ADVM-07864: A request to cancel string was made \nwhile the file system was
being repaired. This could leave the file system \nin an inconsistent state. It is
strongly recommended that string \nbe rerun to complete file system repairs.
Cause: The ACFS fixer was cancelled before all file system repairs were completed.
Action: Rerun the ACFS fixer to complete file system repairs.
ADVM-07900: Security_Metadata file _Private structure has invalid _freeDataList
Cause: The _freeDataList property of the _Private structure of the indicated
Security_Metadata file was incorrect. The _freeDataList value exceeded the maximum
value for this Security_Metadata file.
ADVM-07901: Hash_Bucket metadata structure has incorrect _controlling_bkt
value\n found: string maximum: string\nfor structure:\nstring
incorrect. Its value exceeded the maximum value for the hash table.
ADVM-07902: Hash_File_Master_Block metadata structure has incorrect value for
entry number in _hash_bucket_group array\n found: number minimum: number
Hash_File_Master_Block structure was incorrect.
ADVM-07903: Hash_Bucket metadata structure has invalid data; expected all zeros
ADVM-07907: directory file has no storage allocated to it\nfor file:\nstring
ADVM-07908: Root_Directory cannot be repaired\nfile:\nstring
Cause: The ACFS Checker/Fixer found an inconsistency with the Root_Directory
metadata.
Action: The Root_Directory is a critical system file that is necessary for a functioning
file system. Restore the file system from a backup copy.
ADVM-07909: System metadata was truncated, possibly resulting in the deletion of
files.
ADVM-07924: Snap_Map_header has invalid value for RW snap storage not in map
Cause: The Snap_Map_header property that indicates the amount of RW snap storage
not recorded in the Snap_Map file is incorrect.
ADVM-07925: Snap_Map_header has invalid value for snap storage in map\n
Cause: The Snap_Map_header property that indicates the amount of snap storage
recorded in the Snap_Map file is incorrect.
ADVM-07926: Snap_Map_header has invalid value for snap map flags\n found:
Cause: The Snap_Map_header flags field is invalid.
ADVM-00501 to ADVM-11111 4-139
ADVM-07928: Plug-in configuration file has invalid _FileSize value\n found:

Cause: The _FileSize property of the indicated plug-in configuration file was
incorrect.
ADVM-07929: The string command is unable to open the storage accelerator
volume string that is associated with this file system.
Action: Verify that the ASM disk group containing the storage accelerator volume is
mounted. Then rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ADVM-07930: Continuing will result in the storage accelerator volume being
removed from the file system, which could leave the file system in an inconsistent
and possibly unusable state if critical system metadata is stored on the storage
accelerator volume.
Action: If the accelerator volume has no known problems, verify that the ASM disk
group containing the storage accelerator volume is mounted. Then rerun fsck (Unix or
Linux) or acfschkdsk.exe (Windows). Or, if the accelerator volume is known to have
problems such as disk corruption and you wish to have fsck (Unix of Linux) or
acfschkdsk.exe (Windows) disassociate the accelerator volume from the file system,
allow it to continue.
ADVM-07932: Volume string does not contain a valid ACFS storage accelerator.
message.
Support Services.
ADVM-07933: Accelerator volume string is associated with a different file system.
message.
Support Services.
ADVM-07934: The file identifier for the accelerator volume storage bitmap is
invalid.\n found: string maximum: string
message.
Support Services.
ADVM-07935: The _FileEntry metadata structure for the accelerator volume storage
bitmap is invalid.
message.
Support Services.
ADVM-07936: Extent structure has incorrect _VolId value.\n found: string\nfor
structure:\nstring
message.
Support Services.
ADVM-07937: File extent exceeds accelerator volume size.\n string\nextent:
_FileOffset: string _Length: string _PhysicalDiskOffset: string\nfor file:\nstring
message.
Support Services.
ADVM-07938: Accelerator Global_BitMap has invalid value for number of bits set.
message.
Support Services.
ADVM-07939: Accelerator Global_BitMap has invalid value for number of bits set.
message.
ADVM-00501 to ADVM-11111 4-141
Support Services.
ADVM-07940: Accelerator Global_BitMap has invalid value for next offset to
search.\n found: string maximum: string\nfor file:\nstring
message.
Support Services.
ADVM-07941: mismatch between temporary Global_BitMap and on-disk
accelerator Global_BitMap
message.
Support Services.
ADVM-07942: Accelerator Global_BitMap has bits incorrectly set for storage
beyond the file system size for file:\nstring
message.
Support Services.
ADVM-07943: The specified volume is an accelerator volume. Cannot proceed.
Cause: The volume specified on the command line was an accelerator volume. The
command requires the primary file system volume.
Action: Rerun the command specifying the primary file system volume.
ADVM-09025: Failed to update the Windows Registry for volume string.
Cause: An attempt to store data in the Windows registry failed. This message is
accompanied by other message(s) that provide details as to the exact cause of the
failure.
Action: Correct the problem indicated by the accompanying messages and retry the
operation.
ADVM-09100: Creating volume 'string' in diskgroup 'string'.
Action: None
ADVM-09101: Failed to create volume 'string' in diskgroup 'string'.
Cause: The volume was unable to be created in the diskgroup. Possible Causes: 1)
ASM is not running. 2) User is not part of the ASMADMIN group. 3) An ASM specific
error occurred.
Action: 1) Verify that ASM is running ('srvctl status asm') 2) Verify that the user is
part of the ASMADMIN group. 3) Check the ASM logs and output for an ASM
specific error.
ADVM-09102: Unable to verify creation of ACFS Oracle database Home.
Cause: A command was given to ASM to create the specified volume and no errors
were detected. However, post creation checks failed to find that the volume that was
created and/or enabled.
Action: Run sqlplus (or asmcmd) to manually create the volume.
ADVM-09103: Enabling volume 'string' on diskgroup 'string'.
Action: None
ADVM-09104: Enable of volume 'string' failed.
Cause: ASM was instructed to enable the specified volume and failed.
Action: Attempt a manual enable via sqlplus or asmcmd.
ADVM-09105: Volume 'string' not found in 'string'.
Cause: The specified volume does not exist.
Action: Create volume via sqlplus or asmcmd.
ADVM-09106: Diskgroup 'string' not found.
Cause: The specified diskgroup does not exist.
Action: Create diskgroup via sqlplus or asmcmd.
ADVM-09107: ASM mounting diskgroup 'string'.
Action: None
ADVM-09108: ASM mount of diskgroup 'string' failed.
Cause: ASM found the specified diskgroup but could not mount it.
Action: Try mounting the diskgroup manually via sqlplus. If the mount fails, check
ASM logs for errors related to the diskgroup, clear errors, and try again.
ADVM-09109: string driver failed to load.
Cause: The driver failed to load.
Action: View the system specific OS kernel log (for instance, /var/log/messages on
Linux, Event Log on Windows). If the drivers have not previously been unloaded
('crsctl stop crs', 'acfsload stop', 'acfsroot uninstall'), it is not possible to reload them. If
a specific error has occurred, than clear the error condition and try again. If the OS
and\or architecture is not supported by the drivers, than contact Oracle Support
Services for an updated driver package.
ADVM-09110: Offline mount point 'string' was dismounted for recovery.
Cause: Informational. The mount point referenced was fenced due to an underlying
volume failure. In this case, the mount point was successfully dismounted for
recovery.
Action: None
ADVM-00501 to ADVM-11111 4-143
ADVM-09111: Offline mount point 'string' was recovered.

Cause: Informational - the mount point referenced was fenced due to an underlying
volume failure. In this case, the mount point was successfully remounted, which has
renabled IO to the file system.
Action: None
ADVM-09112: The following process IDs have open references on mount point
'string':
Cause: During shutdown of the CRS stack, it was determined that a process had files
open on the mount point in the process of being dismounted. This prevents the
dismount from succeeding.
Action: Terminate any process\applications that are using files on the mount point
that is being dismounted before stopping the CRS stack.
ADVM-09113: These processes will now be terminated.
Action: None
ADVM-09114: completed
Action: None
ADVM-09115: The command 'string' returned an unexpected value.
Action: An internal error occurred during the installation process. Restart the
installation process.
ADVM-09116: Offline mount point 'string' was not recovered.
Cause: An inaccessible mount point could not be restored to working condition.
Action: Manual intervention is required to clear the offline mount point. Dismount
the mount point and remount it manually to restore access to the mount point.
ADVM-09117: Manual intervention is required.
Cause: Informational, from previous errors.
Action: Clear previous errors and retry.
ADVM-09118: string driver in use - cannot unload.
Cause: This may be seen during 'crsctl stop crs', 'acfsload stop', or 'acfsroot uninstall'.
Applications (possibly ASM) have open references on the driver.
Action: Terminate applications, including ASM, that may be using the driver and
retry.
ADVM-09119: string driver failed to unload.
Cause: An unknown error has occurred when trying to unload the driver.
Action: Check system specific logs (/var/adm/messages on Linux, Event Log on
Windows) and clear any error conditions that are preventing the unload.
ADVM-09120: The 'string' machine architecture not supported.
Cause: ADVM/ACFS device drivers have not yet been ported to this CPU type or OS.
This occurs when the customer manually tries to load the drivers on an architecture
or system OS type that ACFS is not supported, such as VMS.
Action: Contact Oracle Support Services to determine if an updated driver is available

for this OS and architecture, or install ACFS on a supported architecture and OS.
ADVM-09121: Failed to detect control device 'string'.
Cause: ADVM/ACFS device drivers have been started but the devices that should
have been created have not been.
Action: Try 'acfsload stop' followed by 'acfsload start' or restarting the crs stack 'crsctl stop crs', 'crsctl start crs'. If the control devices still do not exist, contact Oracle
Support Services.
ADVM-09122: ADVM device not determined from mount point 'string'.
ADVM-09123: 'string' command not found.
Cause: A required component of ACFS is missing. This could be an incomplete install,
removal of files from the system after install, or an unknown cause.
Action: Re-install by running 'acfsroot install'. If that does not work, than contact
Oracle Support Services. In the event that handle.exe // is not found, than please
install handle from sysinternals.com or another site, and make sure that the PATH
environment variable contains the install location. Retry the operation.
ADVM-09124: string driver failed to detach from the system driver stack.
Cause: The ACFS driver is being used by one or more mounted file systems.
Action: Unmount all ACFS file systems and retry the operation.
ADVM-09125: ADVM/ACFS is not supported on this OS: 'string'
Cause: ADVM/ACFS device drivers have not been ported to this OS.
Action: None
ADVM-09126: Attempting to terminate the program 'string' with OS process ID
'string'.
Cause: The process was using an ACFS file system, which was being forcibly
unmounted. A kill signal was sent to allow the unmount to proceed.
ADVM-09127: Not all ADVM/ACFS drivers have been loaded.
Cause: ADVM/ACFS device drivers have been started but not all of them are
detected as running.
Action: Try 'acfsload stop' followed by 'acfsload start'. If that does not start all drivers,
than contact Oracle Support Services.
ADVM-09128: unknown query type 'string'
ADVM-09129: ADVM/ACFS not installed
Cause: No ADVM/ACFS drivers or commands have been found on the system. All
ADVM and ACFS actions will be disabled.
Action: Install components using 'acfsroot install options'. No ACFS file systems or
ADVM volume devices will be available until ADVM/ACFS has been installed.
ADVM-00501 to ADVM-11111 4-145
ADVM-09130: Root access required

Cause: The user this command is executing as does not have sufficient privileges to
run this command.
Action: Run this command as a user with administrative privileges.
ADVM-09135: string installation aborted.
ADVM-09136: PID string could not be killed.
Cause: Failed to kill a Process ID during a force unmount of a file system.
Action: Manually kill the process and retry the unmount.
ADVM-09137: Failed to set group on directory 'string'.
ADVM-09138: command 'string' completed with an error: string
Cause: 'acfsutil' did not successfully run.
Action: Correct the problem described in the accompanying error message from
'acfsutil'. If this error was returned within the context of a CRS resource execution,
retry the CRS action after the problem is resolved.
ADVM-09139: Attempting recovery of offline mount point 'string'
Cause: An ACFS mount point reported by the 'acfsutil' command was not accessible.
Action: This message is informational. CRS will attempt to recover the mount point.
ADVM-09140: Unable to determine the correct drivers for this version of Windows:
ID:string Major:string Minor:string Product Type:string
Cause: Error. ACFS is not supported on this Windows Version.
Action: Report this message to Oracle Support Services to determine if an update to
ACFS is available.
ADVM-09149: unable to determine device mount status - unsupported OS name
'string'
Cause: The standard method to determine mount state of a device was unavailable. It
is possible that ADVM/ACFS is not supported on the OS.
Action: Report the value of OS to Oracle Support Services.
ADVM-09150: Unexpected output from 'acfsutil info fs': 'string'.
Action: None
ADVM-09151: Ignoring request to mount due to existence of "oracle_nomounts"
file: string
Cause: "An "oracle_nomounts" file was present, causing file system mount processing
to be skipped during a CRS resource operation."
Action: Normal mount operations can be resumed by removing the
"oracle_nomounts" file.
ADVM-09152: Program 'string' with OS process ID 'string' will not be terminated.

Cause: The process is using an ACFS file system which is being forcibly unmounted
but it will not be terminated because it is a system critical process.
Action: Manual intervention may be required.
ADVM-09153: Program 'string' with OS process ID 'string' is using mount point
'string'.
Cause: The process is using the mount point.
ADVM-09154: Loading 'string' driver.
Action: None
ADVM-09155: Checking for existing 'string' driver installation.
Action: None
ADVM-09156: Detecting control device 'string'.
Action: None
ADVM-09157: Detecting driver 'string'.
Action: None
ADVM-09158: Configuration file 'string' in the /boot directory is not accessible.
Cause: A populated /boot directory, which contains static files required to install
kernel modules, was not detected on the system.
Action: After restoring the /boot directory and the kernel configuration files, re-run
"acfsroot install".
ADVM-09160: Can not use the silent and verbose options at the same time.
Cause: The -s and -v options were used in the command. These options are mutually
exclusive.
Action: Re-execute the command with one of the options or neither.
ADVM-09161: acfsroot install: Install ADVM/ACFS components.
Action: None
ADVM-09162: acfsroot uninstall: Uninstall ADVM/ACFS components.
Action: None
ADVM-09163: acfsroot version_check: Check ADVM/ACFS version.
Action: None
ADVM-00501 to ADVM-11111 4-147
ADVM-09164: acfsroot enable: Enable ADVM/ACFS CRS resources.

Action: None
ADVM-09165: acfsroot disable: Disable ADVM/ACFS CRS resources.
Action: None
ADVM-09166: string [-h] [-s | -v]
ADVM-09167: ADVM/ACFS is not installed or loaded. Run 'acfsroot install'.
Cause: An operation was requested that requires ADVM/ACFS to be running.
Action: Run 'acfsroot install' and then run the requested operation.
ADVM-09168: The CRS query "string" cannot be parsed.
ADVM-09169: The CRS attribute value specification "string" is invalid.
ADVM-09170: The file system's CRS resource name "string" is invalid.
ADVM-09171: The CRS resource for the file system on device string cannot be
retrieved
ADVM-09172: The CRS resource for the file system on device string cannot be
registered
ADVM-09173: The srvctl command line "string" failed to execute. (number)
ADVM-09174: unable to communicate with CRS
ADVM-09175: Invalid trace level. Valid values for trace level are 0, 1 or 2.
Cause: An invalid trace level was provided.
Action: Use a supported trace level: 0, 1, or 2.
ADVM-09176: Entering 'string'

Action: None
ADVM-09177: Return from 'string'
Action: None
ADVM-09178: Return code = string
Action: None
ADVM-09179: Command executed: 'string', output = 'string'
Action: None
ADVM-09180: Sub-command is 'string'
Action: None
ADVM-09181: Kernel version is 'string'
Action: None
ADVM-09182: Variable 'string' has value 'string'
Action: None
ADVM-09183: Query = 'string'
Action: None
ADVM-09184: string [-h] [-s | -v | -t <0,1,2>]
was specified.
ADVM-09185: string [-h] [-s | -v | -t <0,1,2>] [-l directory]
was specified.
ADVM-09186: Usage: acfsroot uninstall [-h] [-s | -v | -t <0,1,2>]
was specified.
ADVM-09187: Usage: acfsroot version_check [-h] [-t <0,1,2>] [-l location]
was specified.
ADVM-00501 to ADVM-11111 4-149

ADVM-09188: cannot use the trace option with the silent or verbose options
Cause: Conflicting options were specified.
Action: Specify only one of -s, -v, and -t.
ADVM-09189: [-t <0,1,2> ] - trace level
was specified.
ADVM-09190: User group 'string' does not exist.
Cause: The group name is required to create ADVM/ACFS devices with the correct
attributes. The group name could not be found in the /etc/group file nor in the
various remote services like LDAP, AD, NIS/Yellow Pages, DNS, etc.
Action: Ensure that the required group exists, then re-run the command.
ADVM-09191: Usage: acfsroot version_check [-h] [-t <0,1,2>]
was specified.
ADVM-09200: Supported
Cause: ADVM/ACFS device drivers have been ported to this OS or CPU type.
ADVM-09201: Not Supported
Cause: ADVM/ACFS device drivers have not yet been ported to this OS or CPU type.
Action: None
ADVM-09203: true
Cause: ADVM/ACFS device drivers were installed/loaded.
Action: None
ADVM-09204: false
Cause: ADVM/ACFS device drivers were not installed/loaded.
Action: None
ADVM-09205: usage: string [-h] [-orahome <home_path>] {installed | loaded |
version | supported | validate} [-s]
ADVM-09206: usage: string [-orahome <ORACLE_HOME>] {installed | loaded |
ADVM-09207: The user this command is executing as does not have permission to
execute Perl in 'string'.
ADVM-09208: Enter the location of the db home for this database to '-orahome'.
ADVM-09210: The ADVM/ACFS drivers are supported but have not been verified
on this Operating System version.
Cause: The drivers have not been explicitly tested on this operating system version
but are expected to work properly.
ADVM-09211: usage: string [-h] [-orahome <home_path>] {installed | loaded |
ADVM-09225: Failed to start OKS persistent logging.
Cause: The drivers were successfully loaded but OKS persistent logging failed to
start.
Action: run "acfsutil plogconfig -d GridHome" to perform a manual start.
ADVM-09226: ADVM/ACFS drivers not correct for this OS - cannot load.
Cause: The device drivers installed are not compatible with the currently running
operating system
Action: run "acfsroot install options" to install the correct drivers.
ADVM-09250: Unable to get the ASM administrator user name from the ASM
process.
Cause: ASM processes have not been found running on this system. This will prevent
the requested action from being completed.
Action: Start ASM ('srvctl start asm') and retry the operation.
ADVM-09251: Mount point 'string' unmounted.
Action: None
ADVM-09252: The following process IDs have open references on mount point
'string':
Action: None
ADVM-09253: Failed to unmount mount point 'string'. Mount point likely in use.
Cause: Other processes have outstanding open references on the mount point.
ADVM-00501 to ADVM-11111 4-151
Action: Terminate applications using files on the mountpoint than retry the //
operation (' crsctl stop crs' ).
ADVM-09254: Manual intervention is required.
Cause: Follow up message to ACFS-9253.
ADVM-09255: Creating 'string' mount point.
Action: None
ADVM-09256: Failed to create mountpoint 'string'.
Cause: The mount point may already exist, the user executing the command may
have insufficient permission, or a system specific error may have occurred.
Action: Choose another mount point, execute the action from an account with the
required permissions, or resolve the specified error shown before this message.
ADVM-09257: Mounting device 'string' on mount point 'string'.
Action: None
ADVM-09258: Failed to mount device 'string' on mount point 'string'.
Cause: The mount point may be in use, the user executing this command may have
insufficient permissions, or another system specific error may have occurred.
Action: Make sure that the mount point is available, ensure the user executing the
command has the correct permissions, or resolve any system error shown before this
message.
ADVM-09259: Mount point 'string' already has a device mounted on it.
Cause: There is already a device mounted on this mount point.
Action: If the new device is meant to replace the old device on this mount point,
unmount the old one first and retry the operation. Otherwise this error may be
ignored.
ADVM-09260: Failed to connect to the ASM instance.
Cause: ASM connection attempt failed.
Action: Ensure that the ORACLE_SID environment variable is correctly set to // the
value of the ASM instance. In addition, verify that ASM is running ('srvctl status
asm').
ADVM-09261: Invalid _ORA_NAME format.
ADVM-09262: Invalid sub-command 'string'.
Cause: This is an internal error or the user attempted to run the script manually with
an incorrect sub-command.
Action: Contact Oracle Support Services or use a correct sub-command.
ADVM-09263: Valid sub-commands are 'start', 'stop', 'check', and 'clean'.
Cause: This results in an incorrect usage of the command.
Action: Run the command with an option (command) that is supported, such as
'start', 'stop', 'check', or 'clean'.
ADVM-09264: Mount point 'string' is not mounted.
Action: None
ADVM-09274: Resource 'string' is not online.
Action: None
ADVM-09275: The clean failed to unmount the required mountpoint(s) - re-trying.
Cause: Informational. A file system could not be unmounted. This could be due to
new process being started just before the unmount.
Action: None. 9276 - 9288 UNUSED
ADVM-09289: string not set in environment.
Cause: The referenced environment variable was not set. This makes it impossible to
continue with the requested action.
Action: Ensure that the referenced variable is set and retry the operation.
ADVM-09290: Waiting for ASM to shutdown.
Cause: The resource cannot be terminated while ASM is running.
Action: Wait for ASM to stop. Stop it manually if that does not happen.
ADVM-09291: Waiting for the Windows 'sc stop string' command to complete.
Cause: Informational. System activity is preventing the driver from stopping.
Action: If the driver does not unload, a node reboot may be necessary
ADVM-09300: ADVM/ACFS distribution files found.
Action: None
ADVM-09301: ADVM/ACFS installation cannot proceed:
Cause: Previous errors have caused the installation to reach a point where it cannot
continue.
Action: Fix previous errors.
ADVM-09303: No installation files found for OS kernel version string.
Cause: If '-l' (distribution directory) was specified, the directory may not be valid.
Action: Choose a proper distribution location version.
ADVM-09304: Installation cannot proceed: Failed to unload ADVM/ACFS drivers.
Cause: Applications (possibly ASM) have open references on the drivers.
Action: Terminate applications and ASM that may be using the drivers, and retry the
installation.
ADVM-09305: ADVM/ACFS installation cannot proceed:
Action: Clear previous error and retry.
ADVM-00501 to ADVM-11111 4-153
ADVM-09306: Failed to uninstall previous installation.

Cause: Could not remove ADVM/ACFS commands and or drivers.
Action: Commands and/or drivers are likely in use. Wait for operations to finish,
unload the drivers, and retry the installation.
ADVM-09307: Installing requested ADVM/ACFS software.
Action: None
ADVM-09308: Loading installed ADVM/ACFS drivers.
Action: None
ADVM-09309: ADVM/ACFS installation correctness verified.
Action: None
ADVM-09310: ADVM/ACFS installation failed.
Cause: A previous error caused this installation to fail.
Action: Correct previous error and retry the installation.
ADVM-09311: not all components were detected after the installation.
Cause: ADVM/ACFS commands and drivers were found in the installation area but
did not get placed in their assigned locations.
Action: Re-install using 'acfsroot install -l options'. If necessary, contact Oracle Support
Services.
ADVM-09312: Existing ADVM/ACFS installation detected.
Action: None
ADVM-09313: No ADVM/ACFS installation detected.
Cause: An attempt was made to un-install ADVM/ACFS components that did not
exist on the system.
Action: None - there is no problem.
ADVM-09314: Removing previous ADVM/ACFS installation.
Action: None
ADVM-09315: Previous ADVM/ACFS components successfully removed.
Action: None
ADVM-09316: Valid ADVM/ACFS distribution media detected at: 'string'
Action: None
ADVM-09317: No ADVM/ACFS distribution media detected at location: 'string'
Cause: If -l (location) is used, the directory specified may be invalid.
Action: Use the correct directory.

ADVM-09318: ORACLE_HOME is not set.
ADVM-09319: Unknown OS kernel version 'string' detected.
ADVM-09320: Missing file: 'string'.
Cause: A required command or driver is not found on the installation media (pre
install) or system (post install).
Action: If post install, try running acfsroot again. Otherwise, contact Oracle Support
Services.
ADVM-09321: Creating udev for ADVM/ACFS.
Action: None
ADVM-09322: completed
Action: None
ADVM-09323: Creating module dependencies - this may take some time.
Action: None
ADVM-09324: Alternate drivers installed.
Action: None
ADVM-09327: Verifying ADVM/ACFS devices.
Action: None
ADVM-09328: unknown query type 'string'.
ADVM-09329: Failed to uninstall driver: 'string'.
Cause: Acfsinstall failed to uninstall the driver.
Action: Drivers may be in use. Correct previously reported errors and retry uninstall.
If that fails, contact Oracle Support Services.
ADVM-09330: Binary 'string' not installed.
Cause: A component that should have been installed was not installed.
Action: Rerun 'acfsroot install'.
ADVM-09339: The environment variable ORACLE_HOME is not set.
ADVM-00501 to ADVM-11111 4-155

ADVM-09340: failed to install string driver.
Cause: Acfsinstall failed to install the driver.
Action: Run acfsinstall manually to see reported errors, resolve them, and retry.
ADVM-09341: Binary 'string' not found.
Cause: One of the binaries that make up the ACFS package is missing.
Action: Reinstall the ACFS package and retry the operation.
ADVM-09343: Unable to retrieve OS kernel version from module string.
Cause: Running modinfo against the usm driver failed.
Action: None - the current OS kernel version will be used instead.
ADVM-09344: Missing directory: 'string'.
Cause: A required directory is not found on the system.
ADVM-09345: Unable to create directory: 'string'.
Cause: Creation of a required directory failed.
ADVM-09346: Unable to install file: 'string'.
Cause: Copying to the given destination failed.
ADVM-09347: Unable to set permission bits (string) on: 'string'.
Cause: Setting the given permission bits failed.
Action: Manually set the permissions to the required level.
ADVM-09348: Unable to remove 'string'.
Cause: A previously installed file was unable to be removed.
Action: Attempt to manually remove the file.
ADVM-09349: Unable to configure driver 'string'.
Cause: A driver was installed but add_drv failed to write a configuration file.
Action: Correct the OS error and re-run acfsroot install.
ADVM-09350: Failed to create a symbolic link from 'string' to 'string'.
Cause: Creating a symbolic link failed.
ADVM-09351: Unable to remove devlink entry for 'string'.
Cause: An entry for the driver was found in /etc/devlink.tab but it was not possible
to remove the entry.
Action: Manually remove the entry from /etc/devlink.tab and re-run acfsroot
uninstall
ADVM-09352: Unable to write to 'string'.
Cause: A file required modifications but it was not possible to write to it.
Action: Check the file permissions.
ADVM-09353: Unable to unconfigure string.

Cause: A call to rem_drv failed.
Action: Correct the OS error and re-run acfsroot uninstall.
ADVM-09354: Unable to create symlink: 'string'.
Cause: Ensure that a file with the same name does not already exist and the user has
permission.
Action: Remove the existing file and make sure the user has the required permission.
ADVM-09355: Performing AIX setup failed with error code 'string'.
Cause: Running AIX initial setup has failed.
ADVM-09356: Saving the AIX ODM changes for 'string' failed with error code
'string'.
Cause: Running the AIX savebase command failed.
ADVM-09357: Getting the ASMADMIN group failed with error code 'string'.
Cause: Previous installation steps may have failed.
Action: Correct the preceding error and re-run the root install script.
ADVM-09358: Adding the AIX ODM entry for 'string' failed with error code
'string'.
Cause: Running the AIX odmadd command failed.
ADVM-09360: The command aixsetup failed with error code 'string'.
Cause: Running the aixsetup script failed.
ADVM-09361: Removing device 'string' failed with error code 'string'.
Cause: Running the device's undefine method failed.
Action: Correct the error and re-run the root uninstall script.
ADVM-09362: Warning: deleting the AIX ODM entry for 'string' failed with error
code 'string'.
Cause: Running the odmdelete command failed.
Action: Manually remove the entry or ignore the message.
ADVM-09363: Opening the file /etc/vfs for read failed.
Cause: The /etc/vfs file is not readable.
Action: Check the permission of the file and ensure it has read permission.
ADVM-09364: Opening the file /etc/vfs for append failed.
Cause: The /etc/vfs file is not writable.
Action: Check the permission of the file and ensure it has write permission.
ADVM-00501 to ADVM-11111 4-157
ADVM-09365: The directory 'string' is not being removed.

Cause: The directory was scheduled to be uninstalled, but it contained files that were
not installed by acfsroot.
Action: Manually remove the directory.
ADVM-09366: Relative path for mount point 'string' is not supported.
Cause: Mount point was provided as a relative path.
Action: Specify the mount point in the form of an absolute path.
ADVM-09381: Modification of ADVM/ACFS drivers resource failed.
Cause: An attempt to modify the ACFS drivers resource resulted in an error.
ADVM-09382: Modification of ADVM/ACFS drivers resource succeeded.
Action: None
ADVM-09383: ADVM/ACFS uninstall cannot proceed
Cause: ADVM/ACFS uninstall cannot proceed due to an error. This message is
Action: Correct the problem indicated in the other messages.
ADVM-09384: Invalid OS kernel variation 'string'.
Cause: The command found an OS kernel variation (e.g., "el5", etc) that it did not
recognize as a valid ADVM/ACFS supported kernel.
Action: Boot a supported kernel
ADVM-09385: Usage: acfsroot version_check [-h] [-l location]
ADVM-09388: An absolute path name must be specified for the alternate location.
Cause: A relative path name to the distribution files was specified.
Action: Enter the absolute path name instead.
ADVM-09389: ORACLE_HOME is not set to the location of the Grid Infrastructure
home.
Cause: The ORACLE_HOME environment variable was not set correctly.
Action: Make sure that the ORACLE_HOME environment variable is set to the
location of the Grid Infrastructure home and that it is properly exported.
ADVM-09390: The command 'string' returned unexpected output that may be
important for system configuration:
Cause: One of the operating system commands used to configure the system returned
an unexpected error. This message is accompanied by other message(s) providing
details of the error.
Action: See the operating system documentation for the specific command for more
information on this error.
ADVM-09391: Checking for existing ADVM/ACFS installation.
Action: None
ADVM-09392: Validating ADVM/ACFS installation files for operating system.
Action: None
ADVM-09393: Verifying ASM Administrator setup.
Action: None
ADVM-09394: The installed driver string has a build date of string which does not
match the loaded kernel module build date of string.
Cause: The most likely cause is that an upgrade or patch procedure failed to unload
the kernel module.
Action: Reboot the system before attempting to use ACFS.
ADVM-09395: Environment variable ODMDIR is not set, unable to proceed with
system configuration.
Cause: Environment variable ODMDIR was not set.
ADVM-09396: Environment variable ODMDIR specifies a nonexistent path,
unable to proceed with system configuration.
Cause: Environment variable ODMDIR specified a nonexistent path.
ADVM-09397: Modification of ADVM/ACFS registry resource failed.
Cause: An attempt to modify the ACFS registry resource resulted in an error.
ADVM-09398: Modification of ADVM/ACFS registry resource succeeded.
Action: None
ADVM-09399: Calling 'acfsroot install' to install compatible ADVM/ACFS drivers.
Action: None
ADVM-09400: Could not open the Service Control Manager.
Cause: You do not have administrator access.
Action: Log onto a user account with administrator privileges and retry.
ADVM-09401: Failed to install the driver.
Cause: The specified driver could not be installed.
Action: Respond based on the accompanying error message.
ADVM-09402: The driver file path is too long.
Cause: The path to the driver exceeded system limits.
Action: Move the driver to a shorter path or create a shorter link.
ADVM-00501 to ADVM-11111 4-159
ADVM-09403: The driver can be either installed or removed, not both.

Cause: The /i and the /u switches are mutually exclusive.
Action: Use either /i to install or /u to uninstall the driver.
ADVM-09404: Specify either /i (install) or /u (uninstall).
Cause: Either /i to install or /u to uninstall the driver is required.
Action: The /i or the /u switch must be specified.
ADVM-09405: Only one driver can be installed at a time.
Cause: Multiple drivers were specified with the /i option.
Action: Enter only one driver on the command line.
ADVM-09406: Specify either /a (ADVM) or /o (ACFS) or /l (OKS).
Cause: The driver to be installed or uninstalled was not specified.
Action: Enter the driver option on the command line.
ADVM-09407: Could not find driver "string" in the current directory.
Cause: The driver could not be found in the directory specified.
Action: Verify and enter the correct driver path name.
ADVM-09408: The current directory is %"s".
Action: None
ADVM-09409: CreateService failed (ERROR_SERVICE_EXISTS).
Cause: The driver service already exists.
Action: None. The service is active.
ADVM-09410: CreateService failed.
Cause: The driver service could not be created.
the operation.
ADVM-09411: CreateService succeeded.
Action: None
ADVM-09412: The driver was installed successfully.
Action: None
ADVM-09413: RegCreateKeyEx failed.
Cause: Failed to create a Windows registry key.
the operation.
ADVM-09414: RegSetValueEx (TypesSupported) failed.
the operation.
ADVM-09415: RegSetValueEx (EventMessageFile) failed.

the operation.
ADVM-09416: OpenService failed.
Cause: Could not start the driver.
the operation.
ADVM-09417: The driver was started successfully.
Action: None
ADVM-09418: StartService failed (SERVICE_ALREADY_RUNNING).
Action: None. The driver is already running.
ADVM-09419: StartService failed.
Cause: The driver failed to start.
the operation.
ADVM-09420: The driver is not currently installed on this node.
Cause: The driver is not installed to start.
Action: Install the driver using the '/i' option.
ADVM-09421: The driver is already installed on this node.
Cause: An attempt was made to install a driver that is already installed.
Action: None
ADVM-09422: The driver was removed successfully.
Action: None
ADVM-09423: Failure trying to remove the driver, DeleteService failed.\n The
driver service is pending deletion or is in an invalid state.
Cause: The driver could not be removed.
Action: Make sure that all references to the driver have been removed and, if the
driver is "oracleacfs.sys", that "acfsutil detach" has been run. Verify that the driver is
in the STOPPED state and then retry the operation. If the driver removal still fails,
you probably need to reboot the node."
ADVM-09424: The driver was stopped successfully.
Action: None
ADVM-09425: The driver could not be stopped: StopService failed.
Cause: The driver could not be stopped.
the operation.
ADVM-00501 to ADVM-11111 4-161
ADVM-09426: Unable to set the file attributes for file string.

Cause: The file attributes for the oject file could not be set.
Action: Reset the attributes with "attrib -r <file_name>" and then retry the operation.
ADVM-09427: Failed to unload ADVM/ACFS drivers. A system reboot is
recommended.
ADVM-09428: Failed to load ADVM/ACFS drivers. A system reboot is
recommended.
ADVM-09429: Failed to install ADVM/ACFS files.
Cause: An unexpected condition has been detected. The files were previously verified
to exist.
Action: Check the file permissions. Contact Oracle Support if the problem cannot be
resolved.
ADVM-09441: /i Install the driver
ADVM-09442: /u Uninstall the driver
ADVM-09443: /a Perform the operation for the ADVM driver
ADVM-09444: /o Perform the operation for the ACFS driver
ADVM-09445: /l Perform the operation for the OKS driver
ADVM-09446: path Path to the driver. If not specified,\n defaults to
oracleadvm.sys, oracleacfs.sys, or\n oracleoks.sys in the current directory\n
ADVM-09450: Examples:
Action: None
ADVM-09451: string /i /a (Install the ADVM driver from the current directory)
Action: None
ADVM-09452: string /u /o (Uninstall the ACFS driver)
Action: None
ADVM-09453: string /i /o c:\drivers\oracleacfs.sys (Install ACFS with the specified
file)
Action: None
ADVM-09454: Unable to delete the driver file string after stopping driver.
Cause: A call to the Windows DeleteFile function to delete the driver file failed.
Action: Manually delete the specified driver file using Windows Explorer. If you were
installing the driver please retry after deletion.
ADVM-09455: Unable to copy driver file string to the path string.
Cause: Could not copy the driver file to the specified directory because the Windows
CopyFile function failed.
Action: Manually delete any previous driver file from the specified directory using
Windows Explorer and retry the install.
ADVM-09456: An attempt to stop the driver string failed.
Cause: The driver could not be properly stopped; it is in an invalid state.
Action: Reboot system.
ADVM-09457: The driver file does not match the driver chosen to install.
Cause: The driver file is not consistent with the driver option used.
Action: Specify a path to oracleoks.sys when using the /l option. path to
oracleacfs.sys with the /o option and path to oracleadvm.sys with the /a option.
ADVM-09458: The Windows 'string' service is in an invalid state. The new driver
cannot be installed.
Cause: An attempt to install the new driver failed because the existing service could
not be stopped properly.
Action: Reboot system and then retry the install.
ADVM-09459: ADVM/ACFS is not supported on this OS version: 'string'
Cause: ADVM/ACFS device drivers have not been ported to this OS version.
Action: None
ADVM-09500: Location of Oracle Home is 'string' as determined from the internal
configuration data
Action: None
ADVM-00501 to ADVM-11111 4-163
ADVM-09501: Location of Oracle Home is 'string' as determined from the

ORACLE_HOME environment variable
Action: None
ADVM-09502: Location of Oracle Home is 'string' as determined from the location
of the Oracle library files
Action: None
ADVM-09503: ADVM and ACFS driver media location is 'string'
Action: None
ADVM-09504: Copying file 'string' to the path 'string'
Action: None
ADVM-09505: Using acfsutil executable from location: 'string'
Action: None
ADVM-09506: The files 'string' and 'string' are the same, not copying.
Cause: Informational. The file was not copied because the target and source point to
the same file.
Action: None
ADVM-09507: Searching the alternative location: 'string'
Cause: Informational. The installation files were not found in the specified location. A
likely path containing that location will be searched.
Action: None
ADVM-09508: ACFS installation aborted (component string).
Cause: Installation was aborted due to an error.
ADVM-10101: Authentication failed.
Cause: The specified ACFS Security administrator password was wrong.
Action: Re execute the command and provide the correct ACFS Security
administrator password at the prompt.
ADVM-10120: ACFS Encryption not initialized.
Cause: ACFS Encryption was not initialized.
Action: Run 'acfsutil encr init [-p]' as system administrator to initialize encryption.
ADVM-10149: Realm description cannot exceed number characters
Cause: Realm description cannot exceed 1023 characters
ADVM-10150: Realm description not specified within double quotation marks

Cause: Invalid description specified for realm.
Action: Enclose the realm description within double quotation marks.
ADVM-10151: Unmatched single quote or double quote.
Cause: Matching quote was not found.
Action: Add a matching quote and retry.
ADVM-10152: Realm name cannot exceed number characters.
Cause: Realm name length exceeded 255 characters.
ADVM-10153: Realm 'string' not found on mount point 'string'.
Cause: Realm was not found on mount point.
<mount_point> -n'.
ADVM-10154: Failed to create realm 'string' on mount point 'string'.
ADVM-10155: Realm 'string' created.
Cause: Realm was created.
Action: None
ADVM-10156: Failed to destroy realm 'string' on mount point 'string'.
ADVM-10157: Realm 'string' destroyed.
Cause: Realm was destroyed.
Action: None
ADVM-10158: Improper value specified for -l option.
Cause: Invalid argument format was specified for -l option.
Action: Specify the argument in the format 'commandrule:ruleset'. A comma
separated list can also be specified as 'cmd1:rs1,cmd2:rs2,cmd2:rs3'. For example: * acfsutil sec realm add r1 -m /mnt -l READ:rs1 * - acfsutil sec realm add r1 -m /mnt -l
READ:rs1,MKDIR:rs2
ADVM-10159: The command requires at least one of the options -u, -G, -l, -f, or -e.
Cause: None of the options -u, -G, -l, -f, or -e were specified with this command.
Action: Specify at least one of the options -u, -G, -l, -f, or -e with this command.
ADVM-10160: Failed to add user 'string' to the realm 'string'.
ADVM-00501 to ADVM-11111 4-165
ADVM-10161: Added user 'string' to realm 'string'.

Cause: User was added to realm.
Action: None
ADVM-10162: Failed to add group 'string' to realm 'string'.
ADVM-10163: Added group 'string' to the realm 'string'.
Cause: Group was added to the realm.
Action: None
ADVM-10164: Failed to add filter 'string:string' to the realm 'string'.
ADVM-10165: Added filter 'string:string' to the realm 'string'.
Cause: Filter was added to the realm.
Action: None
ADVM-10166: Failed to add 'string' to the realm 'string'.
ADVM-10167: Added 'string' to the realm 'string'.
Cause: Pathname was added to the realm.
Action: None
ADVM-10168: Failed to turn encryption ON for realm 'string'.
ADVM-10169: Encryption turned ON for realm 'string'.
Cause: Encryption was turned ON for realm.
Action: None
ADVM-10170: Failed to delete user 'string' from realm 'string'.
ADVM-10171: Deleted user 'string' from realm 'string'.
Cause: User was deleted from realm.
Action: None
ADVM-10172: Failed to delete group 'string' from the realm 'string'.

ADVM-10173: Deleted group 'string' from realm 'string'.
Cause: Group was deleted from realm.
Action: None
ADVM-10174: Failed to delete filter 'string:string' from the realm 'string'.
ADVM-10175: Deleted filter 'string:string' from realm 'string'.
Cause: Filter was deleted from realm.
Action: None
ADVM-10176: Failed to delete 'string' from realm 'string'.
ADVM-10177: Deleted 'string' from realm 'string'.
Cause: Pathname was deleted from realm.
Action: None
ADVM-10178: Failed to turn encryption OFF for realm 'string'.
ADVM-10179: Encryption turned OFF for realm 'string'.
Cause: Encryption was turned OFF for realm.
Action: None
ADVM-10180: Failed to get realm files or directories for realm 'string'.
ADVM-10181: Failed to get groups for realm 'string'.
ADVM-10182: Failed to get users for realm 'string'.
ADVM-00501 to ADVM-11111 4-167
ADVM-10183: Failed to get filters for realm 'string'.

ADVM-10184: Failed to get realm encryption attributes of realm 'string'.
ADVM-10185: '-e' requires both '-a' and '-k'.
Cause: At least one of the options -a or -k is missing with -e option.
Action: Specify both '-a' and '-k' with '-e' and retry.
ADVM-10186: Realm 'string' already exists on mount point 'string'.
Cause: Realm was already found on mount point.
Action: Specify another realm name and retry.
ADVM-10187: Failed to get all realms on mount point 'string'.
ADVM-10188: Attributes of realm 'string' retrieved.
Cause: Realm attributes were retrieved.
Action: None
ADVM-10189: Failed to update attributes of realm 'string'.
ADVM-10190: Updated attributes of realm 'string'.
Cause: Updated realm attributes.
Action: None
ADVM-10206: File or directory 'string' does not belong to an ACFS file system
Cause: A File or directory specified in 'acfsutil sec realm add/delete' command did
not belong to an ACFS file system.
Action: Specify only ACFS file or directory in the command 'acfsutil sec realm add/
delete'.
ADVM-10221: Rule name cannot exceed number characters.
Cause: Rule name length exceeded 255 characters.
Action: Select a rule name that is smaller than 255 characters and retry.
ADVM-10223: Invalid rule type is specified.
Cause: Invalid rule type was provided on the command line with '-t'.
Action: Provide one of the following with '-t': * - username <user_name> * application <application_name> * - time <start_time>,<end_time> * - hostname
<host_name>
ADVM-10224: Rule type 'username', 'application' or 'hostname' must have only one
rule value.
Cause: An incorrect number of arguments were provided with rule type 'username',
'application' or 'hostname'.
Action: Provide only one argument after the rule type 'username', 'application' or
'hostname'. * For example, '-t username alice' * '-t application 'c:\programs
\mozilla.exe' * '-t application '/sbin/cat' * '-t hostname myhost.domain.com'
ADVM-10225: Rule type 'time' must have both start time and end time separated by
a comma.
Cause: Either the start time or end time was not provided.
Action: Specify both start time and end time (comma separated) after rule type time. *
For example, '-t time 10:10:40,23:01:12'
ADVM-10226: '-o' requires either 'ALLOW' or 'DENY'.
Cause: A valid rule option was not provided.
Action: Specify either 'ALLOW' or 'DENY' as rule the option.
ADVM-10227: Failed to perform rule create operation on 'string'.
ADVM-10228: Rule 'string' is created.
Cause: Rule was created.
Action: None
ADVM-10229: Rule 'string' not found.
Cause: Rule was not found.
Action: Ensure that the rule exists by executing 'acfsutil sec info -m mnt -l rule-name'.
ADVM-10230: Failed to perform rule edit operation on 'string'.
ADVM-10231: Rule 'string' updated.
Cause: Rule was updated.
Action: None
ADVM-10232: Failed to destroy rule 'string'.
ADVM-10233: Rule 'string' destroyed.
Cause: Rule was destroyed.
Action: None
ADVM-10234: Failed to get rule 'string' information.
ADVM-00501 to ADVM-11111 4-169

ADVM-10235: Rule 'string' already exists.
Cause: Rule was already found on mount point.
Action: Specify another rule name and retry.
ADVM-10236: Time format string must be HH:MM:SS.
Cause: The time format provided was not formatted as 'HH:MM: SS', where HH
translates to hours, MM to minutes and SS to seconds.
Action: Specify the time in correct format and retry.
ADVM-10237: Rule type 'string' specified does not match the actual type 'string' of
rule 'string'
Cause: The rule type specified did not match the actual rule typed.
Action: Specify the actual rule type to update the rule value and retry.
ADVM-10238: Failed to get all rules on mount point 'string'.
ADVM-10239: Failed to get information for rule 'string'.
ADVM-10240: Cannot destroy rule 'string'. The rule is in use by one or more rule
sets.
Cause: The rule was being used in one or more rule set(s) in the file system.
Action: Remove the rule from the rule set(s) and retry.
ADVM-10241: Rule set name cannot exceed number characters.
Cause: Rule set name length exceeded 255 characters.
Action: Select a shorter rule set name and retry.
ADVM-10242: '-o' requires either ALL_TRUE or ANY_TRUE.
Cause: The rule set option was not set to either ALL_TRUE or ANY_TRUE.
Action: Specify either ALL_TRUE or ANY_TRUE with the rule set option '-o'.
ADVM-10243: Failed to create rule set 'string' on mount point 'string'.
ADVM-10244: Rule set 'string' is created.
Cause: Rule set was created.
Action: None
ADVM-10245: Rule set 'string' not found on mount point 'string'.
Cause: Rule set was not found on mount point.
Action: None
ADVM-10246: Failed to add rule 'string' to the rule set 'string'.
ADVM-10247: Added rule 'string' to the rule set 'string'.
Cause: Rule was added to the rule set.
Action: None
ADVM-10248: Failed to delete rule 'string' from the rule set 'string'.
ADVM-10249: Deleted rule 'string' from rule set 'string'.
Cause: Rule was deleted from the rule set.
Action: None
ADVM-10250: Failed to destroy rule set 'string' on mount point 'string'.
ADVM-10251: Rule set 'string' destroyed.
Cause: Rule set was destroyed.
Action: None
ADVM-10252: Failed to get rules for rule set 'string'.
ADVM-10253: Failed to get list of command rules.
ADVM-10254: Rule set 'string' already exists.
Cause: Rule set was already found on mount point.
Action: Specify another rule set name and retry.
ADVM-10255: Rule 'string' already exists in rule set 'string'.
Cause: Rule was already part of rule set.
Action: None
ADVM-10256: Rule 'string' is not found in rule set 'string'.
Cause: Rule was not found in the rule set.
Action: Ensure that the realm exists using the command 'acfsutil sec info -m -s rulesetname'.
ADVM-00501 to ADVM-11111 4-171
ADVM-10257: Failed to get all rule sets on mount point 'string'.

ADVM-10258: Failed to get information for rule set 'string'.
ADVM-10259: Invalid command rule 'string'.
Cause: Invalid command rule was specified.
Action: Execute 'acfsutil sec info -m <mount_point> -c' to get all the valid command
rules. * Re-execute the command with valid command rule.
ADVM-10260: File object 'string' and the realm 'string' should be in the same file
system.
Cause: File object was not in the same file system as that of the realm.
Action: Specify file objects from the same file system as that of the realm.
ADVM-10261: Cannot destroy rule set 'string'. The rule set is in use by one or more
realms.
Cause: The rule set is being used in filter(s) that are part of one or more realms in the
file system.
Action: Remove the filter(s) from the realms that are using this rule set and retry.
ADVM-10262: Application path name for rule type 'application' cannot exceed
'number' characters.
Cause: Application path name for rule type 'application' exceeded 511 characters
Action: Select a shorter application path name for rule type 'application' and retry.
ADVM-10263: Host name for rule type 'hostname' cannot exceed 'number'
characters.
Cause: Host name for rule type 'hostname' exceeded 255 characters.
Action: Select a shorter host name for rule type 'hostname' and retry.
ADVM-10264: Invalid value for rule type 'string' as the given path name 'string' is a
symbolic link
Cause: Path name provided for rule type 'application' was a symbolic link. Symbolic
links are not supported for rule type 'application'.
Action: Specify a path name which is not a symbolic link and re-execute the
command.
ADVM-10271: Encryption algorithm can be only 'AES'.
Cause: The encryption algorithm provided was not 'AES'.
Action: Specify 'AES' as the algorithm with '-a' and retry.
ADVM-10272: Key length must be either 128, 192, or 256.
Cause: The key length specified with '-k' was not 128, 192 or 256.
Action: Specify either 128, 192, or 256 with '-k' and retry.
ADVM-10273: Failed to set the encryption parameter on realm 'string'.

ADVM-10274: Failed to update rule set option.
ADVM-10275: Failed to get rule sets for mount point 'string'.
ADVM-10276: Rule set 'string' option updated to 'string'.
Cause: Rule set option updated.
Action: None
ADVM-10277: '-e' requires either ON or OFF.
Cause: The realm encryption status specified with '-e' was not 'on' or 'off'
Action: Specify either 'on' or 'off' with -e and retry.
ADVM-10278: Encryption parameters are not set on the file system, realm
encryption is unavailable.
Cause: The encryption parameters were not set on the file system.
Action: A system administrator must execute an 'encr set' command
ADVM-10284: Failed to get security information for 'string'.
ADVM-10285: Pathname 'string' does not exist.
Cause: Specified pathname was not found.
Action: Specify a valid pathname.
ADVM-10286: User 'string' does not exist.
Cause: User was not found.
Action: Specify a valid user.
ADVM-10287: Group 'string' does not exist.
Cause: Group was not found
Action: Specify a valid group.
ADVM-10288: User 'string' already added to the realm 'string'.
Cause: User was already added to the realm.
Action: None
ADVM-00501 to ADVM-11111 4-173
ADVM-10289: Group 'string' already added to the realm 'string'.

Cause: Group was already added to the realm
Action: None
ADVM-10290: Realm filter 'string' already added to the realm 'string'.
Cause: Filter was already added to the realm.
Action: None
ADVM-10291: Pathname 'string' already added to the realm 'string'.
Cause: Pathname was already added to the realm.
Action: None
ADVM-10292: User 'string' is not part of the realm 'string'.
Cause: User was not part of the realm.
Action: None
ADVM-10293: Group 'string' is not part of the realm 'string'.
Cause: Group was not part of the realm.
Action: None
ADVM-10294: Pathname 'string' is not part of the realm 'string'.
Cause: Pathname was not part of the realm.
Action: None
ADVM-10295: Realm filter 'string' is not part of the realm 'string'.
Cause: Filter was not part of the realm.
Action: None
ADVM-10296: Realm filter 'string:string' could not be added to the realm 'string'.
Cause: The filter was not added because the filter with command rule 'ALL' was
already part of the realm.
command rules are desired. Individual command rules cannot be added when 'ALL'
is already present.
ADVM-10297: Realm filter 'ALL' could not be added since another filter exists in
realm 'string'.
Cause: Filter 'ALL' was not added because another filter existed in the realm .
command rules are desired. 'ALL' command rule cannot be added when individual
command rules are already present.
ADVM-10298: User name cannot exceed number characters.
Cause: User name length exceeded 64 characters.
Action: Select a shorter user name and retry.
ADVM-10299: Group name cannot exceed number characters.
Cause: Group name length exceeded 64 characters.
Action: Select a shorter group name and retry.
ADVM-10322: System realm 'SYSTEM_SecurityMetadata' created.

Cause: System realm 'SYSTEM_SecurityMetadata' was created.
Action: None
ADVM-10323: System realm 'SYSTEM_Logs' created.
Cause: System realm 'SYSTEM_Logs' was created.
Action: None
ADVM-10324: Rulesets cannot be cloned before cloning rules on mount point
'string'.
Cause: Rule sets were not cloned because some rules were not present on mount
point.
Action: Clone rules first using command 'acfsutil sec rule clone' and then clone rule
sets.
ADVM-10342: System realm 'SYSTEM_BackupOperators' created.
Cause: System realm 'SYSTEM_BackupOperators' was created.
Action: None
ADVM-10350: Incorrect password was entered in all attempts to open the
encryption key store. Encrypted files will not be available.
Cause: Incorrect password was entered in all attempts to open the encryption key
store during the mount command.
Action: Unmount the file system and remount it, providing the correct password.
Encrypted files will not be available until the file system is unmounted and
remounted with the correct password.
ADVM-10355: System realm 'SYSTEM_Antivirus' created.
Cause: System realm 'SYSTEM_Antivirus' was created.
Action: None
ADVM-10356: waiting for the operation to complete...
Action: None
ADVM-10357: System realm 'SYSTEM_Audit' created.
Action: None
ADVM-10400: Encryption is set on mount point 'string'.
Cause: Encryption was set on mount point.
Action: None
ADVM-10401: Failed to set encryption parameters on mount point 'string'.
ADVM-10402: Encryption turned 'string' on 'string'.
Cause: Encryption was turned either ON or OFF on the pathname.
Action: None
ADVM-00501 to ADVM-11111 4-175
ADVM-10403: Failed to turn encryption 'string' on 'string'.

ADVM-10405: Failed to get encryption information on 'string'.
ADVM-10406: Re-key operation is complete on 'string'.
Cause: Re-key operation was complete on the pathname.
Action: None
ADVM-10407: Failed to perform re-key operation on 'string'.
ADVM-10410: encryption is already disabled on the file system
Cause: Encryption was already disabled on the file system.
Action: None, encryption is already disabled.
ADVM-10411: encryption is already enabled on the file system
Cause: Encryption was already enabled on the file system.
Action: None, encryption is already enabled.
ADVM-10412: Encryption parameters were not provided, using default algorithm
(string) and key length (number).
Cause: Encryption parameters were not provided.
Action: None, default values have been used.
version 11.2.0.2.0 to allow the acfsutil encryption and security commands.
or beyond.
ADVM-10414: Encryption has been initialized for the cluster.
Cause: An administrator initialized encryption for the cluster.
Action: None
ADVM-10415: File system level encryption is on, file level encryption operations
are not allowed
Cause: A file level encryption operation was attempted while file system level
encryption was enabled. File level encryption operations are not allowed when file
system level encryption is turned on.
Action: None
ADVM-10416: File is realm secured\n

Cause: An encryption operation was attempted on a realm secured file and no action
was performed. A realm secured file can only be encrypted and decrypted by
changing the encryption parameters of containing realm(s) or by deleting the file from
all realms.
Action: If changing the encryption status of this file is required, contact a Security
Administrator to modify the encryption parameters of the containing realm(s).
ADVM-10419: Skipping directory 'string' because it does not belong to the file
system mounted on 'string'
Cause: The directory does not belong to the specified mounted ACFS file system.
Action: None
ADVM-10420: Encryption parameters specified for realm 'string' match existing
settings.
Cause: An attempt to set encryption parameters for a realm specified values the same
as those already set.
Action: None
version 'string' to allow acfsutil encryption commands.
Cause: An adminstrator attempted an encryption set or volume level rekey operation,
but the ADVM compatibility attribute had not been upgraded to a supported version.
version 'string' to allow 'acfsutil sec' commands.
Cause: A security adminstrator attempted an ACFS Security operation, but the
ADVM compatibility attribute had not been upgraded to a supported version.
COMPATIBLE.ADVM attribute and retry the operation.
ADVM-10423: This encryption operation is not allowed on a standby file system.
Cause: An encryption operation that is not allowed on a standby file system was
attempted. The following acfsutil encryption commands are not allowed on a standby
file system: 'encr set', 'encr on', 'encr off', and 'encr rekey'.
Action: None
ADVM-10424: This ACFS Security operation is not allowed on a standby file
system.
Cause: An ACFS Security operation that is not allowed on a standby file system was
attempted. The following acfsutil security commands are not allowed on a standby
file system: 'sec prepare', 'sec save/load/enable/disable', 'sec realm create/destroy/
clone/add/delete', 'sec rule create/destroy/clone/edit', and 'sec ruleset create/
destroy/clone/edit'
Action: None
ADVM-10450: Unauthorized encryption operation attempted on 'string'.
Cause: A user attempted an encryption operation on the given file and the operation
was denied.
Action: None
ADVM-00501 to ADVM-11111 4-177
ADVM-10451: File level encryption operation attempted on realm secured file

'string'.
Cause: A user attempted to perform a file level encryption command on a realm
secured file and the operation was denied.
Action: None
ADVM-10452: Failed to decrypt 'string'.
ADVM-10453: Unable to get encryption parameters for the file system mounted on
'string'.
ADVM-10454: File system level encryption turned on for mount point 'string'.
Cause: A system administrator enabled file system level encryption.
Action: None
ADVM-10455: New volume encryption key generated for mount point 'string'.
Cause: A system administrator updated the volume encryption key for the mount
point. The file encryption keys for all encrypted files on the file system were reencrypted using the new volume encryption key.
Action: None
ADVM-10456: New file encryption key generated for file 'string'.
Cause: A system administrator updated the volume encryption key for the file. The
data in the file was re-encrypted using the new key.
Action: None
ADVM-10457: New file encryption keys generated for all files in directory 'string'.
Cause: A system administrator updated the volume encryption key for the files in the
given directory. The file contents were re-encrypted using the new key.
Action: None
ADVM-10458: Encryption turned off for path 'string'.
Cause: A user successfully decrypted a file or directory.
Action: None
ADVM-10459: Encryption turned off for directory 'string' and its contents.
Cause: A user successfully decrypted a directory and its contents.
Action: None
ADVM-10460: File system level encryption turned off for mount point 'string'.
Cause: A system administrator disabled file system level encryption.
Action: None
ADVM-10461: Encryption turned on for path 'string'.
Cause: A user successfully encrypted a file or directory.
Action: None
ADVM-10462: Encryption turned on for directory 'string' and its contents.

Cause: A user successfully encrypted a directory and its contents.
Action: None
ADVM-10463: Skipping file 'string' because it does not belong to the file system
mounted on 'string'
Cause: The file does not belong to the specified mounted ACFS file system.
Action: None
ADVM-10464: ACFS Encryption operations are not allowed on files of this type.
Cause: An attempt was made to encrypt, decrypt, or rekey a file of one of the
following Oracle file types: data, control, online redo log, archive log, backup,
incremental backup, or flashback.
Action: None
ADVM-10500: Pathname cannot exceed number characters.
Cause: Pathname length exceeds 255 characters.
Action: Select a name that is smaller than %d characters and retry.
ADVM-10550: Security wallet created.
Cause: Security wallet was created.
Action: None
ADVM-10551: Security wallet creation failed.
ADVM-10564: Incorrect password for encryption key store.
Cause: An incorrect password was entered while opening the encryption key store.
Action: Retry the command and enter the correct password.
ADVM-10565: Encryption key store created.
Cause: Encryption key store was created.
Action: None
ADVM-10566: Encryption key store creation failed.
ADVM-10573: Encryption key store not found.
Cause: Encryption key store did not exist.
Action: Run 'acfsutil encr init' command and retry.
ADVM-10574: ACFS encryption already initialized, cannot reinitialize.
Cause: 'acfsutil encr init'can has already been executed and the encryption key store
already existed.
Action: None
ADVM-00501 to ADVM-11111 4-179
ADVM-10575: Incorrect encryption key store.

ADVM-10576: Incorrect encryption key, new volume encryption key not created.
ADVM-10577: Encryption parameters not set.
Cause: A command that requires encryption parameters to be set first was run before
encryption parameters were set on the file system.
Action: Run 'acfsutil encr set' and retry.
ADVM-10578: Unable to communicate new encryption settings to cluster members.
ADVM-10579: Key store is not valid for encryption.
Cause: The encryption key store was either not created using 'acfsutil encr init' or it
was corrupted.
Action: Restore the encryption key store from a backup and retry.
ADVM-10586: Internal error.
ADVM-10588: Internal error : WLT number.
ADVM-10589: Internal error : BSF number.
ADVM-10590: Internal error : XML number.
ADVM-10591: Internal error : TSP number.
ADVM-10592: Internal error : IOC number.
ADVM-10593: Internal error : UGP number.
ADVM-10594: Internal error : OCR number : string.

ADVM-10596: Unable to get the hostname for the current node.
Cause: The current user does not have access to the requested information.
ADVM-10597: The user 'string' and the group 'string' do not belong to the same
domain.
Cause: The user and the group were not part of the same domain.
Action: Use 'net user' command to verify and retry with user and group that belong to
the same domain.
ADVM-10598: Unable to retrieve domain name information for 'string'.
Cause: Unable to retrieve domain name information.
Action: Make sure the node is part of proper domain.
ADVM-10599: Current user does not have system administrative privileges to
initialize ACFS security.
Action: Run 'acfsutil sec init' with administrative privileges.
ADVM-10600: Failed to store first security administrator 'string' in wallet.
ADVM-10601: Failed to update first security administrator 'string' information.
ADVM-10602: Passwords do not match.
Cause: Verification of the password did not succeed.
Action: Re-execute and provide the same password on both the prompts.
ADVM-10603: Security administrator group already set in wallet.
Cause: Security administrator group was already set in wallet.
Action: None
ADVM-10604: Security administrator group not set in wallet.
ADVM-10606: User 'string' is not a security administrator.
Action: Only a security administrator has privilege to execute the security commands.
Add the user to security administrator list by executing 'acfsutil sec admin add' and
retry.
ADVM-00501 to ADVM-11111 4-181
ADVM-10607: User 'string' is not member of security administrator group.

Cause: User was not a member of security administrator's group.
Action: Add the user to the security administrator's group.
ADVM-10609: Administrator update in driver failed.
ADVM-10610: Failed to get current user information.
ADVM-10611: Failed to assign user 'string' as security administrator.
ADVM-10612: Failed to remove user 'string' from security administrator(s) list.
ADVM-10613: Failed to change ACFS Security administrator password for current
user.
ADVM-10614: Security administrator 'string' already added.
Cause: User was already a security administrator.
Action: None
ADVM-10615: User 'string' is not a security administrator.
Action: None
ADVM-10616: Incorrect ACFS Security administrator password.
Cause: The password supplied was incorrect.
Action: Re-execute and provide the correct ACFS Security administrator password for
the current user.
ADVM-10617: Password cannot exceed number characters.
Cause: The password entered exceeded the maximum allowed characters.
Action: Enter the password within the specified number of characters.
ADVM-10618: Security administrator 'string' could not be added.
Cause: Security administrator was not added.
ADVM-10619: Security administrator 'string' added.

Cause: Security administrator was added.
Action: None
ADVM-10620: Security administrator 'string' could not be removed.
Cause: Security administrator was not removed.
ADVM-10621: Removal of the last security administrator 'string' is not allowed.
Cause: The security administrator was not removed being the only security
administrator in this system.
Action: Add another security administrator to remove the intended security
administrator.
ADVM-10622: Security administrator 'string' removed.
Cause: Security administrator was removed.
Action: None
ADVM-10623: ACFS security already initialized, cannot reinitialize.
Cause: ACFS security was already initialized and could not be reinitialized.
Action: None
ADVM-10624: User 'string' is not member of the group 'string'.
Cause: The user was not member of the group.
Action: Add the user to the group and retry.
ADVM-10625: Failed to prepare file system for security operations on mount point
'string'.
ADVM-10626: Mount point 'string' is already prepared for security.
Cause: Mount point was already prepared for security. Prepare should be executed
only once for an ACFS formatted file system that is mounted.
Action: None
ADVM-10627: Mount point 'string' is now prepared for security operations.
Cause: " Mount point was prepared for security operations.
Action: None
ADVM-10629: Failed to enable security on mount point 'string'.
ADVM-10630: Security is already enabled on mount point 'string'.
Cause: Security was already enabled on mount point.
Action: None
ADVM-00501 to ADVM-11111 4-183
ADVM-10631: Security is now enabled on mount point 'string'.

Cause: Security was enabled on mount point.
Action: None
ADVM-10632: Security is already disabled on mount point 'string'.
Cause: Security was already disabled on mount point.
Action: None
ADVM-10633: Security is now disabled on mount point 'string'.
Cause: Security was disabled on mount point.
Action: None
ADVM-10634: Failed to disable security on mount point 'string'.
ADVM-10635: Failed to get security administrator group.
ADVM-10636: Security administrator group retrieved.
Cause: Security administrators group was retrieved.
Action: None
ADVM-10637: File system is not prepared for ACFS security on mount point
'string'.
Cause: File system was not prepared for security operations on mount point.
Action: Execute 'acfsutil sec prepare' to prepare security operation on mount point.
ADVM-10638: Backup and log directories created.
Cause: Backup and log directories were created.
Action: None
ADVM-10639: Failed to create directory 'string' on mount point 'string'.
ADVM-10640: Failed to create log directory on mount point 'string'.
ADVM-10641: Failed to create backup directory on mount point 'string'.
ADVM-10643: Security is already enabled on realm 'string'.

Cause: Security was already enabled on realm.
Action: None
ADVM-10644: Security is already disabled on realm 'string'.
Cause: Security was already disabled on realm.
Action: None
ADVM-10645: Failed to set owner of file 'string' to 'string'.
Cause: Current user is not owner of the file.
Action: Login as the file owner and re-run the command.
ADVM-10646: Failed to create secbackup.xml file on mount point 'string'.
initialize ACFS encryption.
Action: Run 'acfsutil encr init' with administrative privileges.
ADVM-10648: ACFS security already initialized, recovery failed.
Cause: Previous execution of 'acfsutil sec init' had failed. Recovery actions also failed
in the subsequent execution of 'acfsutil sec init'.
ADVM-10649: ACFS encryption already initialized, recovery failed.
Cause: Previous execution of 'acfsutil encr init' had failed. Recovery actions also failed
in the subsequent execution of 'acfsutil encr init'.
ADVM-10650: Invalid file name 'string' for ACFS security metadata.
Cause: The file was invalid for saving or loading ACFS security metadata.
Action: Specify a valid file.
ADVM-10651: Failed to save ACFS security metadata of mount point 'string'.
ADVM-10652: Saved ACFS security metadata of mount point 'string'.
Cause: ACFS security metadata of mount point '%s' was saved.
Action: None
ADVM-10653: Failed to save ACFS security string metadata of mount point 'string'.
ADVM-10654: Directory '.Security' does not exist on mount point 'string'.
Cause: Mount point was not prepared for ACFS security.
Action: Execute 'acfsutil sec prepare' on the mount point.
ADVM-00501 to ADVM-11111 4-185
ADVM-10655: Failed to get hostname.

ADVM-10656: Failed to get timestamp.
ADVM-10657: Absolute and relative pathnames are not allowed with '-p' option.
Cause: Filename was provided with absolute or relative path.
Action: Specify only name of the file with '-p' option and retry.
ADVM-10658: ACFS Security has been initialized on the cluster with user 'string'
as the initial Security Administrator and 'string' as the Security Administrator
group.
Cause: An administrator initialized ACFS Security on the cluster.
Action: None
ADVM-10659: Cannot destroy realm 'string' because it is a system-created realm.
Cause: A request to destroy a system-created realm was denied because that
operation is not allowed.
Action: None
ADVM-10660: Current user does not have required OS privileges to set ACFS
encr set'.
Action: Run 'acfsutil encr set' as a user who has root or administrator privileges.
ADVM-10661: Current user does not have required OS privileges to rekey the
ACFS encryption parameters.
encr rekey'.
Action: Run 'acfsutil encr rekey' as a user who has root or administrator privileges.
ADVM-10662: Current user 'string' does not have security administrator privileges.
Cause: A command requiring Security Administrator privileges was issued but the
user is not in the Security Administrators group.
Action: Add current user to the Security Administrators group or log on as a user
who has the required privileges, then retry the command.
ADVM-10663: User name 'string' is not a fully qualified name.
Cause: Fully qualified name was not specified. The supplied user name was not
ADVM-10664: Group name 'string' is not a fully qualified name.

Cause: Fully qualified name was not specified.The supplied group name was not
Action: Specify domain group name prefixed with Windows Server Domain name.
For example: HOSPITAL-ADMIN\Doctors where HOSPITAL-ADMIN is a Windows
ADVM-10665: Group 'string' is a local group and not a Windows Server Domain
group.
Cause: Specified group was not a Windows Server Domain group.
Action: Specify a domain group name prefixed with Windows Server Domain name.
For example, HOSPITAL-ADMIN\Doctors, where HOSPITAL-ADMIN is a Windows
ADVM-10666: User 'string' is a local user and not a Windows Server Domain user.
Cause: Specified user was not a Windows Server Domain user.
ADVM-10667: Windows Server Domain 'string' does not exist.
Cause: Failed to get Windows Server Domain controller for the domain either because
of not access to domain or domain does not exist.
Action: Specify the name of an existing Windows Server Domain.
ADVM-10675: Failed to load ACFS security metadata on mount point 'string'.
ADVM-10676: Loaded ACFS security metadata on mount point 'string'.
Cause: ACFS security metadata was loaded on mount point.
Action: None
ADVM-10677: Failed to load string on mount point 'string'.
ADVM-10679: Unable to resolve the user id 'string'.
Cause: The user was not found on the system.
Action: None
ADVM-10680: XDK version not compatible.
Cause: Oracle XDK version was incompatible.
Action: Install the correct Oracle XDK version and retry.
ADVM-10681: ACFS kernel version is not compatible. The kernel version on the
system is 'string' while the expected kernel version is 'string' or above.
Cause: ACFS kernel version was incompatible.
ADVM-00501 to ADVM-11111 4-187
ADVM-10682: Kernel major version is not compatible.

Cause: Kernel major version was incompatible.
ADVM-10683: Kernel release version is not compatible.
Cause: Kernel release version was incompatible.
ADVM-10684: Kernel update version is not compatible.
Cause: Kernel update version was incompatible.
ADVM-10685: Kernel port update version is not compatible.
Cause: Kernel port version was incompatible.
ADVM-10686: Kernel patch version is not compatible.
Cause: Kernel patch version was incompatible.
ADVM-10687: Kernel one off version is not compatible.
Cause: Kernel one off version was incompatible.
ADVM-10688: Unable to resolve the group id 'string'.
Cause: The OS group ID could not be resolved to a name. Usually this occurs because
the OS group has been removed.
Action: None
ADVM-10689: Failed to update security administrators information in the driver,
some of the subsequent commands may fail.
Cause: Updating driver security administrator data failed during mount. The mount
completes, but subsequent security commands may be affected. This is an internal
error.
ADVM-10690: Cannot edit groups in realm 'string'.
Cause: No changes were made to the groups in the realm as the operation is not
allowed.
Action: None
ADVM-10691: Changed ACFS Security administrator password for current user.
Action: None
ADVM-10700: Failed to store volume encryption key.
ADVM-10701: Failed to get volume encryption key.

ADVM-10702: Snapshots exist for the file system mounted on 'string'. New
encryption parameters will not apply to files in these snapshots.
operation was done. The new encryption parameters set by this command will apply
only to new files created in the file system and not to existing files in any snapshots.
Note that none of the encryption commands affect files in any snapshots. Any
snapshots created after the command was run will use the new encryption
parameters.
Action: None
ADVM-10703: Snapshots exist for the file system mounted on 'string'. Encryption
status of files in these snapshots will not change.
operation was done. The operation did not modify file data in any snapshots on the
file system, so this data may still be available on disk unencrypted. Note that none of
the encryption commands affect files in any snapshots.
Action: If you plan to use snapshots and encryption together, it is recommended that
any snapshots be created after encrypting data on the file system. If the data on the
file system was encrypted when some snapshots already existed, you may delete
existing snapshots to ensure that data is not available in unencrypted form via any
files in these snapshots.
ADVM-10704: Snapshots exist for the file system mounted on 'string'. Encryption
keys of files in these snapshots will not be rekeyed.
operation was done. The operation did not rekey FEKs of files in any snapshots of the
file system, so the FEKs of these files will continue to remain encrypted with the old
parameters. Note that none of the encryption commands affect files in any snapshots.
Action: To ensure that all FEKs, including those of files in any snapshots, are
encrypted with the new encryption parameters, this command should be run when
the file system has no snapshots. If the command was run when some snapshots
existed you may delete these snapshots. Any snapshots created after the command
was run will use the new encryption parameters.
ADVM-10705: Cannot perform encryption operation because volume encryption
keys for the file system mounted at 'string' are not available.
Cause: The encryption operation failed because the required volume encryption keys
for the file system were not available to the ACFS file system driver. This could
happen because an incorrect key store password was supplied during mount or
because of some other error during mount.
Action: Remount the file system, providing the correct password during the mount
operation if required. Address any other errors reported during mount. If the issue
ADVM-00501 to ADVM-11111 4-189
ADVM-10706: Cannot perform encryption operation because an encryption undo

operation is in progress.
Cause: The encryption operation failed because the system administrator was running
encryption undo ('acfsutil encr set -u') on the file system. It is also possible that a
previous encryption undo operation had not completed cleanly.
Action: There is no action to be taken by users who are not system administrators. If
this message is seen by a system administrator and an encryption undo operation is
not in progress, then a previous encryption operation did not complete properly. Run
the 'acfsutil encr set -u' command again to complete the operation.
ADVM-10707: Cannot perform encryption undo operation because file system level
encryption is on.
Cause: The encryption undo operation failed because file system level encryption was
on.
Action: Turn file system level encryption off and retry the operation.
ADVM-10708: An earlier key store migrate operation did not complete. Provide the
same password as the one used in the previous attempt.
Cause: An earlier run of 'acfsutil keystore migrate' command did not complete.
Action: When prompted for a password (ACFS-10349), provide the same password as
the one used in the previous attempt.
ADVM-10709: Existing ACFS encryption key store is already password-protected.
Action: None
ADVM-10710: Existing ACFS encryption key store is already not passwordprotected.
Action: None
ADVM-10711: Recovery of ACFS encryption key store completed successfully.
Action: None
ADVM-10712: ACFS encryption key store migration to password-protected key
store completed successfully.
Action: None
ADVM-10713: ACFS encryption key store migration to password-free key store
Action: None
ADVM-10714: The environment variable OKV_HOME is not set.
encryption keys failed because the OKV_HOME environment variable was not set.
Action: Set the environment variable OKV_HOME and retry the command.
ADVM-10715: failed to find the PKCS library in path 'string'

encryption keys failed because the PKCS library was not found in '$OKV_HOME/lib'.
ADVM-10716: failed to load the PKCS library
encryption keys failed because the OKV PKCS library could not be loaded from
'$OKV_HOME/lib'.
ADVM-10717: failed to find Oracle Key Vault (OKV) client configuration file
encryption keys failed because the OKV client configuration file, okvclient.ora, was
not found in '$OKV_HOME/conf'.
that contains OKV client data, including the OKV client configuration file,
okvclient.ora. If not, set OKV_HOME and retry the command. If the problem persists,
ADVM-10718: failed to login to OKV server
Cause: A login attempt to Oracle Key Vault (OKV) server failed.
Action: Ensure that correct password is provided, verify okvclient.ora file entries for
servers, verify both the servers are still running, and then retry. If the problem
ADVM-10719: failed to store encryption keys in file system wallet
ADVM-10720: Key store must be either SSO, PKCS, or OKV.
Cause: An attempt to store an encryption key was rejected because the specified key
store was not one of: SSO, PKCS or OKV.
Action: Retry the command specifying either SSO, PKCS, or OKV as the key store.
ADVM-10721: failed to save encryption keys, file system wallet already exists in
directory 'string'
Cause: An attempt to create a new wallet and save encryption keys in it failed because
the wallet already existed in the said location.
Action: Delete or move the wallet and retry the command.
ADVM-10725: Failed to start encryption logging on mount point 'string'.
ADVM-10726: Failed to start security logging on mount point 'string'.
ADVM-00501 to ADVM-11111 4-191

ADVM-10727: Failed to start global security and encryption logging.
Cause: Global security and encryption logging services could not be started. The log
file for this node will not be updated.
Action: n/a
ADVM-10728: ACFS encryption logging directory not found on mount point
'string'.
Cause: The ACFS encryption logging directory '<mount_point>/.Security/
encryption/logs/' could not be opened.
ADVM-10729: ACFS security logging directory not found on mount point 'string'.
Cause: The ACFS security logging directory '<mount_point>/.Security/realm/logs/'
could not be opened.
Action: Ensure the logging directory exists and the security administrator can open
ADVM-10730: ACFS security and encryption logging directory not found in
CRS_HOME.
Cause: The ACFS security and encryption logging directory '<CRS_HOME>/log/
<host_name>/acfssec' could not be opened.
and create files in this directory.
ADVM-10731: Could not get local host name, ACFS encryption logging will not be
Cause: The local host name could not be determined, ACFS encryption logs for this
host in '<mount_point>/.Security/encryption/logs/' will not be written.
ADVM-10732: Could not get local host name, ACFS security logging will not be
Cause: The local host name could not be determined, ACFS security logs for this host
in '<mount_point>/.Security/realm/logs/' will not be written.
Action: Ensure the operating system host name is set correctly and the security
ADVM-10733: Could not get local host name, ACFS security and encryption
logging will not be available for this host
Cause: The local host name could not be determined, ACFS security and encryption
logs for this host in '<CRS_HOME>/log/<host_name>/acfssec' will not be written.
administrator can read this value.
ADVM-10751: Realm_Metadata file has invalid realm record\nfor file:\nstring

Cause: A realm record of the indicated Realm_Metadata file was invalid.
ADVM-10753: Realm_Metadata file has no valid realm records\nfor file:\nstring
Cause: The indicated Realm_Metadata file did not contain any valid valid realm
records.
ADVM-10755: Realm_Metadata file contains invalid realm record data\nfor file:
\nstring
Cause: The indicated Realm_Metadata file contained at least one invalid realm record.
ADVM-10756: Realm_Metadata file _Private structure is invalid for:\nfor file:
\nstring
Cause: The _Private structure of the indicated Realm_Metadata file was invalid. Refer
ADVM-10757: Realm_Metadata file has invalid Hash_Table data\nfor file:\nstring
Cause: The Hash_Table of the indicated Realm_Metadata file contained inconsistent
ADVM-10760: Realm_Metadata file _Private structure has invalid _maxFree value
incorrect.
ADVM-10761: Realm_Metadata file _Private structure has invalid
\nstring
was incorrect.
ADVM-00501 to ADVM-11111 4-193
ADVM-10762: Realm_Metadata file node not on _freeDataList\nfor file:\nstring

Cause: One or more of the _security_data nodes of the indicated Realm_Metadata file
was not found on the free data node list. The _next property for one or more of the
ADVM-10764: Realm_Metadata file has invalid _security_record for
ADVM-10766: Realm_Metadata file has no valid realm data records\nfor file:
\nstring
Cause: The indicated Realm_Metadata file did not contain any valid valid realm data
records.
ADVM-10768: Number of realms created on mount point 'string' has reached the
limit number.
Cause: A request to create a realm was denied because the number of realms created
on the mount point has reached the limit.
Action: Destroy any of the unused realms and retry the command.
ADVM-10769: Number of rulesets created on mount point 'string' has reached the
limit number.
Cause: A request to create a ruleset was denied because the number of rulesets
created on the mount point has reached the limit.
Action: Destroy any of the unused rulesets and retry the command.
ADVM-10770: Number of rules created on mount point 'string' has reached the
limit number.
Cause: A request to create a rule was denied because the number of rules created on
the mount point has reached the limit.
Action: Destroy any of the unused rules and retry the command.
ADVM-10771: Number of realms that file 'string' is part of has reached the limit
number.
Cause: A request to add the file to a realm was denied because the number of realms
that the file is part of has reached the limit.
Action: Remove the file from one or more realms and retry the command.
ADVM-10772: Security at the realm level will not be in effect until file system-level
security is enabled.
Cause: Security is disabled at the file system level. When file system-level security is
disabled, enabling realm-level security does not enable the authorization checks
provided by the realm.
Action: Enable Security at file system level.
ADVM-10773: Unable to lock ACFS Security wallet.
Cause: The ACFS Security wallet lock was not acquired.
ADVM-10774: Unable to unlock ACFS Security wallet.
Cause: The ACFS Security wallet lock was not released.
ADVM-10775: Cannot proceed as another instance of 'acfsutil' command is
updating the security administrator information.
Cause: ACFS Security wallet is locked by another instance of 'acfsutil' command.
ADVM-10776: Invalid 'acfsutil' version 'string'
ADVM-10777: Unable to lock ACFS encryption key store.
Cause: The ACFS encryption key store lock could not be acquired.
ADVM-10778: Unable to unlock ACFS encryption key store.
Cause: The ACFS encryption key store lock was not released.
ADVM-10779: Cannot proceed as another instance of 'acfsutil' command is
updating the encryption key store.
Cause: An acfsutil encryption request found the ACFS encryption key store locked by
another instance of the acfsutil command.
ADVM-00501 to ADVM-11111 4-195
ADVM-10780: The file system mounted on 'string' has been prepared for ACFS
Security, undo ACFS Security first.
Cause: ACFS Encryption cannot be undone when the file system has been prepared
for ACFS Security.
Action: Undo ACFS Security prepare on the mount point by executing 'acfsutil sec
prepare -m <mount_point> -u' as security administrator and retry.
ADVM-10781: existing snapshots preclude undoing ACFS security or encryption
for the file system mounted on 'string'
Cause: An attempt to undo ACFS security or encryption for the indicated file system
failed because there were existing snapshots for the file system. ACFS security and
encryption can only be undone for a file system with no snapshots. This message may
be displayed before or after all files have been decrypted by the 'acfsutil encr set -u'
command. In both cases, the file system retains its encryption 'prepared' state and
files can be encrypted without running 'acfsutil encr set' again.
Action: Remove all snapshots by executing 'acfsutil snap delete' and retry.
ADVM-10782: The file system mounted on 'string' has not been prepared for ACFS
Security, nothing to be undone.
Cause: The file system was not prepared for ACFS Security.
Action: None
ADVM-10783: ACFS Encryption is not set on the file system mounted on 'string',
nothing to be undone.
Cause: ACFS Encryption was not set on the file system.
Action: None
ADVM-10784: Could not destroy all realms, unable to undo ACFS Security.
Cause: All realms were not destroyed.
ADVM-10785: Could not destroy all rules, unable to undo ACFS Security.
Cause: All rules were not destroyed.
ADVM-10786: Could not destroy all rulesets, unable to undo ACFS Security.
Cause: All rulesets were not destroyed
ADVM-10787: Failed to prepare ACFS Security on mount point 'string' as
replication is active on this mount point.
Security cannot co-exist on the same mount point.
ADVM-10788: ACFS Security undo operation on mount point 'string' completed.
Cause: ACFS Security undo operation on the mount point was completed.
Action: None
ADVM-10789: Failed to undo ACFS Security on mount point 'string'.

ADVM-10790: Failed to set ACFS Encryption on mount point 'string' as replication
is active on this mount point.
Encryption cannot co-exist on the same mount point.
ADVM-10791: Failed to undo ACFS encryption on mount point 'string'.
ADVM-10792: Cannot add filter 'string:string' to the cloned realm as the rule set
'string' does not exist on the mount point 'string'.
Cause: Filters could not be added to cloned realm because rule sets were not present
on mount point.
Action: Clone rules and rule sets first and then add command rules to the cloned
realm using 'sec realm add' command.
ADVM-10793: File objects cannot be added to cloned realm as file objects do not
exist on destination mount point.
Cause: File objects could not be added to cloned realm because file objects were not
present on destination mount point.
Action: Copy File objects to destination mount point and then add file objects to the
cloned realm using 'sec realm add' command.
ADVM-10794: File 'string' does not exist on mount point 'string'.
Cause: Information of file could not be obtained, because either file name specified is
not correct or file does not exist on given mount point.
Action: Specify the correct file name or specify the mount point where the file exists.
ADVM-10795: Cannot load ACFS security meta data because the destination mount
point 'string' already has some user-created rules, rule sets or realms.
Cause: ACFS security load was not done as the destination mount point had some
user created rules, rule sets or realms.
Action: Run 'acfsutil sec prepare -u' followed by 'acfsutil sec prepare' on the
destination mount point and then retry the command, or use a file system with no
security objects (like realms, rules and rule sets) except system realms.
ADVM-10796: A prior failed encryption initialization cannot be recovered for this
request because the prior initialization specified a password-protected key store.
because the prior initialization specified a password-protected key store.
Action: Execute the command 'acfsutil encr init' with option 'p'.
ADVM-10797: A prior failed encryption initialization cannot be recovered for this
request because the prior initialization specified a non-password-protected key
store.
because the prior initialization specified a non-password-protected key store.
Action: Execute the command "acfsutil encr init' without option 'p'.
ADVM-00501 to ADVM-11111 4-197
ADVM-10798: ACFS Encryption undo operation on mount point 'string' completed.

Cause: ACFS Encryption undo operation on the mount point was completed.
Action: None
ADVM-10799: For cloning realms with 'string' option, destination mount point
must be same as source mount point.
Cause: Cloning of file system objects is not supported if destination mount point is
different from source mount point.
Action: Run 'acfsutil sec realm clone' without -f option, copy file objects to the
destination mount point, and then add files using 'acfsutil sec realm add' command.
ADVM-10800: Failed to complete ACFS Security undo operation on mount point
'string'.
Cause: ACFS Security undo operation did not complete because some rules, rulesets,
or realms exist for the given file system.
Action: Retry the operation after making sure that no other 'acfsutil sec' commands
are running for the given file system.
ADVM-10801: failed to acquire a lock on ACFS security wallet
Cause: The ACFS security wallet could not be initialized because the lock on the
wallet could not be obtained.
ADVM-10802: unable to release the lock being held on the ACFS security wallet
Cause: After security initialization, the lock on ACFS security wallet could not be
released.
ADVM-10803: cannot proceed because another instance of 'acfsutil' command is
updating the ACFS security wallet
Cause: An attempt to update the ACFS security wallet failed because the ACFS
security wallet was locked by another instance of the acfsutil command.
Action: Retry the command later.
ADVM-10850: Password must have at least number characters.
Cause: The password was not long enough.
Action: Provide the password with number of characters greater than minimum
required length.
ADVM-10851: Password must have at least one digit and letter in it.
Cause: The password did not have either a digit or a letter in it.
Action: Provide a password containing at least one digit and letter.
ADVM-10901: Failed to add the read-only snapshot file 'string' to realm 'string'.
Cause: A file specified for addition to a security realm was a read-only snapshot file.
Action: None
ADVM-10902: Failed to add the read-write snapshot file 'string' to realm 'string'.
Cause: A file specified for addition to a security realm was a read-write snapshot file.
Action: None
ADVM-10903: Snapshot 'string' of mount point 'string' is not prepared for ACFS
Security.
Cause: Snapshot was not prepared for security operations on mount point.
Action: None
ADVM-10914: Security is already enabled in snapshot 'string' of mount point
'string'.
Cause: Security was already enabled in snasphot of mount point.
Action: None
ADVM-10915: Security is already enabled on realm 'string' in snapshot 'string' of
mount point 'string'
Cause: Security was already enabled on realm in snapshot.
Action: None
ADVM-10916: Security is now enabled in snapshot 'string' of mount point 'string'.
Cause: Security was enabled in snapshot of mount point.
Action: None
ADVM-10917: Failed to enable security in snapshot 'string' of mount point 'string'.
ADVM-10918: Security is already disabled in snapshot 'string' of mount point
'string'.
Cause: Security was already disabled in snapshot of mount point.
Action: None
ADVM-10919: Security is already disabled on realm 'string' in snapshot 'string' of
Cause: Security was already disabled on realm in snapshot.
Action: None
ADVM-10920: Failed to disable security in snapshot 'string' of mount point 'string'.
ADVM-10921: Realm 'string' not found in snapshot 'string' of mount point 'string'.
Cause: Realm was not found in snapshot of mount point.
<mount_point> -S <snapshot_name> -n'.
ADVM-10922: Failed to get security related information of snapshot 'string' of
ADVM-00501 to ADVM-11111 4-199

ADVM-10923: Failed to get users for realm 'string' in snapshot 'string' of mount
point 'string'.
ADVM-10924: Failed to get groups for realm 'string' in snapshot 'string' of mount
point 'string'.
ADVM-10925: Failed to get realm encryption attributes of realm 'string' in snapshot
'string' of mount point 'string'.
ADVM-10926: Attributes of realm 'string' in snapshot 'string' of mount point 'string'
retrieved.
Cause: Attributes of realm in snapshot were retrieved.
Action: None
ADVM-10927: Failed to get all rules in snapshot 'string' of mount point 'string'.
ADVM-10928: Failed to get information of rule 'string' in snapshot 'string' of mount
point 'string'.
ADVM-10929: Rule 'string' not found in snapshot 'string' of mount point 'string'.
Cause: Rule was not found in the snapshot.
Action: Ensure that the rule exists by executing 'acfsutil sec info -m <mount_point> -S
<snapshot_name> -l'.
ADVM-10930: Failed to get all rule sets in snapshot 'string' of mount point 'string'.
ADVM-10931: Failed to get rules for rule set 'string' in snapshot 'string' of mount
point 'string'.
ADVM-10932: Rule set 'string' not found in snapshot 'string' of mount point 'string'.
Cause: Rule set was not found in snapshot of mount point.
Action: Ensure that the rule set exists by executing 'acfsutil sec info -m
<mount_point> -S <snapshot_name> -s'.
ADVM-10933: Failed to delete the read-only snapshot file 'string' from realm
'string'.
Cause: Security operations cannot be performed on a read-only snapshot file.
Action: None
ADVM-10934: Failed to delete the read-write snapshot file 'string' from realm
'string'.
Cause: Security operations cannot be performed on a read-write snapshot file.
Action: None
ADVM-10935: ACFS Security cannot be enabled or disabled because 'string' is a
read-only snapshot
Cause: A request to enable or disable ACFS Security specified a read-only snapshot.
Action: None
ADVM-10936: ACFS Security is now disabled in snapshot 'string' of mount point
'string'.
Action: None
ADVM-10937: ACFS Security is now enabled on realm 'string' in snapshot 'string'
of mount point 'string'.
Action: None
ADVM-10938: ACFS Security is now disabled on realm 'string' in snapshot 'string'
of mount point 'string'.
Action: None
ADVM-10939: ACFS Security is now enabled on realm 'string' in mount point
'string'.
Action: None
ADVM-10940: ACFS Security is now disabled on realm 'string' in mount point
'string'.
Action: None
ADVM-10941: Failed to create 'string' file on mount point 'string'
Cause: An attempt to create a file on the indicated mount point failed, most likely
because the user lacked the requisite permission.
Action: Ensure that the user has the required permission and retry. Otherwise, contact
ADVM-10942: Insufficient disk space on mount point 'string'
Cause: The requested operation failed because the file system was full.
Action: Resize the file system and retry.
ADVM-00501 to ADVM-11111 4-201
ADVM-10945: ACFS Auditing source 'string' is already enabled on mount point

'string'.
Action: None
ADVM-10946: ACFS Auditing source 'string' is already disabled on mount point
'string'.
Action: None
ADVM-10947: Audit trail on mount point 'string' is marked as read.
Action: None
ADVM-10948: Audit trail on mount point 'string' is archived.
Action: None
ADVM-10949: ACFS Auditing has been initialized on the cluster with 'string' as the
Oracle ACFS auditor OS group and 'string' as the Oracle ACFS audit manager OS
group.
Action: None
ADVM-10950: Audit trail archive for mount point 'string' is purged.
Action: None
initialize auditing.
Action: Run 'acfsutil audit init' as an OS user with administrative privileges.
ADVM-10952: Auditing already initialized; cannot reinitialize.
Cause: An attempt was made to initialize auditing after it was already initialized.
Action: None
ADVM-10953: Auditing is not initialized.
Cause: A command was issued which requires auditing to be intialized for the cluster,
but auditing has not been initialized.
Action: Initialize auditing by reissuing 'acfsutil audit init' command.
ADVM-10954: Failed to enable auditing on mount point 'string'.
ADVM-10955: Failed to disable auditing on mount point 'string'.
ADVM-10956: Failed to enable auditing for realm 'string' on mount point 'string'.
ADVM-10957: Failed to disable auditing for realm 'string' on mount point 'string'.
ADVM-10958: Current user does not have privileges to run audit commands.
Cause: Command was executed as user who is not part of audit manager OS group or
auditors OS group.
Action: Run command as user who is part of audit manager OS group or auditors OS
group.
ADVM-10960: Failed to get audit information for the mount point 'string'.
ADVM-10961: Failed to get audit manager OS group.
ADVM-10962: Failed to get auditor OS group.
ADVM-10963: Auditing is not enabled on mount point 'string'.
Cause: A command was issued that requires auditing to be enabled at the file system
level, but it is not enabled.
Action: Run 'acfsutil audit enable', and retry the command.
ADVM-10964: Failed to archive audit trail on mount point 'string'.
ADVM-10965: Failed to mark audit trail on mount point 'string' as read
ADVM-10966: Audit trail on mount point 'string' is already marked as read.
Cause: Audit trail was already marked as read on mount point.
Action: None
ADVM-10967: Audit trail on mount point 'string' not found.
Cause: An 'acfsutil audit' command was issued but auditing has not been initialized.
Action: Run 'acfsutil audit init' as an OS user with administrative privileges, then
ADVM-10968: Failed to create audit trail XML file 'string' for mount point string.
ADVM-00501 to ADVM-11111 4-203

ADVM-10969: Failed to purge audit trail archive file for mount point 'string'.
ADVM-10970: Failed to purge audit trail archive because it is not marked 'read' for
Cause: Audit trail was not yet marked as 'read' on mount point.
Action: Run 'acfsutil audit read' and retry the command.
ADVM-10971: Current user does not have privileges to run this audit command.
Cause: Command was executed as user who is not part of audit manager OS group.
Action: Run command as user who is part of audit manager OS group.
ADVM-10972: Failed to update audit managers and auditors group information in
the driver; some of the subsequent audit related commands may fail.
Cause: Audit Managers and Auditors information was not communicated to the
ACFS driver during mount. The mount command was successful but the subsequent
audit commands will not work on this host until the problem is corrected.
version 'string' to enable auditing on mount point 'string'.
Cause: A security adminstrator or audit manager or administrator attempted to
enable auditing, but the 'COMPATIBLE.ADVM' attribute for the disk group had not
been upgraded to a supported version.
enable' command.
ADVM-10974: Auditing cannot be enabled on mount point 'string', because ADVM
compatibility is lower than 'string'.
Cause: A security adminstrator or system administrator attempted to enable auditing
as part of 'acfsutil sec prepare' or 'acfsutil encr set' which was successful, but auditing
could not be enabled because the 'compatible.advm attribute had not been upgraded
to a supported version.
enable' command.
ADVM-10975: Failed to get audit information for realm 'string' on mount point
'string'.
ADVM-10976: Failed to create audit trail XML file because the old audit trail XML
file exists for mount point 'string'.
Cause: A request to archive the audit trail found an existing audit trail XML file.
Action: Run 'acfsutil audit purge' and retry the command.
ADVM-10977: Auditing is enabled for realm 'string' on mount point 'string'.

Action: None
ADVM-10978: Auditing is disabled for realm 'string' on mount point 'string'.
Action: None
ADVM-10979: Cannot proceed because file system is not prepared for ACFS
Security.
Cause: An attempt to enable or disable audit on Security source failed because the file
system was not prepare for ACFS Security.
Action: Execute 'acfsutil sec prepare' to prepare ACFS Security on the file system and
retry 'acfsutil audit' command.
ADVM-10980: Cannot proceed because file system is not set for ACFS Encryption.
Cause: An attempt to enable or disable audit on Encryption source failed because the
file system was not set for ACFS Encryption.
Action: Execute 'acfsutil encr set' to set ACFS Encryption on the file system and retry
'acfsutil audit' command.
ADVM-10998: ACFS Audit not initialized
Cause: ACFS Audit was not initilized.
Action: Run 'acfsutil audit init' command.
ADVM-10999: Audit trail archive file on mount point 'string' was not found.
Cause: An 'acfsutil audit read' command was issued but the audit trail backup file did
not exist.
Action: Run 'acfsutil audit archive' as an OS user with Audit Manager privileges, then
ADVM-11000: ACFS Auditing is already initialized with different Audit Managers
and Auditors group.
Cause: Values provided on the command line did not match those with which ACFS
Auditing was initialized earlier.
Action: Run 'acfsutil audit init' command with the Audit Managers and Auditors
group provided for the previous initialization.
ADVM-11001: Error in parsing command line arguments.
Cause: There was a syntax error is the command line arguments.
Action: Check the command line syntax and re-run the command again.
ADVM-11002: Error: a device name must be supplied with the -l option.
Cause: Either the -l option was not present in the command line or it had no
argument.
Action: Make sure you run the command with the '-l device-name' option.
ADVM-11003: AIX ODM initialization failed, odmerr number
ADVM-00501 to ADVM-11111 4-205
ADVM-11004: failed to lock AIX ODM database, odmerr number

Cause: The method could not lock the AIX ODM database.
Action: Check to see what other method has locked it.
ADVM-11005: failed to look up AIX ODM PdDv object class, odmerr number
ADVM-11006: failed to open AIX ODM CuDv object class, odmerr number
ADVM-11007: failed to add to AIX ODM CuDv object class, odmerr number
Cause: An attempt to add the device's entry to the ODM CuDv object class failed.
Action: Ensure the user has the required permission.
ADVM-11008: failed to close the AIX ODM CuDv object class, odmerr number
ADVM-11010: failed to look up AIX ODM CuDv object class, odmerr number
ADVM-11015: failed to load kernel extension string, errno number (string)
Cause: Loading the kernel extension into the kernel failed.
Action: Check the error message and resolve the error.
ADVM-11017: failed to configure kernel extension string, errno number (string)
Cause: Could not configure the device's driver in the kernel.
ADVM-11018: failed to get a major number for device string
Cause: The method could not get a major number for the device.
ADVM-11019: failed to get a minor number for device string
Cause: The method could not get a minor number for the device.
ADVM-11022: failed to configure device string, errno number (string)
Cause: Attempt to configure the device's driver in the kernel got an error.
ADVM-11024: failed to remove the old device file string, errno number (string)
Cause: The method failed to remove the device file.
Action: Ensure that the user has permission and no other application is still using the
device.
ADVM-11026: failed to create new device file string, errno number (string)
Cause: The user may not have permission or a file with the same name already exists.
Action: Ensure that the file does not already exist and that the user has the required
permission to create it.
ADVM-11028: failed to set permission of the new device file string, errno number
(string)
Cause: The method failed to set permission of the device special file.
ADVM-11030: failed to set group of the new device file string, errno number (string)
Cause: The method failed to set the owning group of the device special file.
ADVM-11031: failed to open the ASMADMIN group file, errno number (string)
Cause: The method could not open the file containing the group to own the device.
ADVM-11032: failed to read from the ASMADMIN group file, errno number
(string)
Cause: The method could not read the file containing the group to own the device.
ADVM-11034: failed to set device state to AVAILABLE, odmerr number
Cause: The method could not change the device's state.
ADVM-11036: No operation was performed because device state is string instead of
DEFINED.
Cause: The method expected a DEFINED device state.
ADVM-11038: failed to unconfigure kernel extension string, errno number (string)
Cause: The method could not unconfigure the kernel extension.
ADVM-11040: failed to unload kernel extension string, errno number (string)
Cause: The method could not unload the extension from kernel.
ADVM-11044: no minor number was returned for device string
Cause: The operating system did not return a device minor number as requested.
ADVM-11046: failed to set device state to DEFINED, odmerr number
Cause: The method failed to change the device's state.
ADVM-00501 to ADVM-11111 4-207
ADVM-11050: failed to delete attributes of device string, odmerr number

Cause: The method failed to remove the device's attributes from the AIX ODM CuAt
object class.
ADVM-11052: failed to delete customized object of device string, odmerr number
Cause: The method failed to remove the device's entry from the AIX ODM CuDv
object class.
ADVM-11053: failed to release major number for device string
Cause: The method failed to release the device's major number.
ADVM-11055: failed to remove device special file string, errno number (string)
Cause: The method failed to remove the device special file.
Action: Check the error message and resolve it.
ADVM-11060: failed to unload kernel extension string
Cause: Could not unload the extension from kernel.
ADVM-11061: failed to look up the group id for group string
Cause: The named group probably does not exist.
Action: Make sure the group exists in the /etc/group file.
ADVM-11062: failed to create directory string, errno number (string)
Cause: The directory could not be created.
Action: Check the permission of the base directory to make sure it is writeable.
ADVM-11063: failed to set permission on directory string, errno number (string)
Cause: The permission of the directory could not be changed.
ADVM-11064: failed to set group on directory string, errno number (string)
ADVM-11065: invalid device minor number number
Cause: The device minor number being used is out of range.
ADVM-11066: the ADVM driver is not loaded
Cause: The ADVM driver is expected to exist in the kernel but it does not.
ADVM-11067: directory /dev/asm does not exist or is not accessible, errno number
(string)
Cause: The ADVM driver probably has not been successfully loaded.
ADVM-11068: The state of device string is unknown. No operation was performed.

Cause: Unknown.
ADVM-11069: Error: device name is too long, exceeding 255 characters.
Cause: The chosen device name exceeds the limit of 255 characters.
Action: Use a device name that is shorter than the limit.
ADVM-11111: string
Cause: None
Action: None
ADVM-00501 to ADVM-11111 4-209
5
ADVMK-00001 to ADVMK-00028
ADVMK-00001: Module load succeeded. Build information: %2 %3 %4 built on %5.
Cause: The ADVM driver was started.
Action: None, this is informational.
ADVMK-00002: Module load failed with status %2. Build information: %3 %4 %5
built on %6.
Cause: There was a problem the prevented the ADVM driver from loading.
Action: Reboot the system.If this happens again please report this error to Oracle
Support Services.
ADVMK-00003: Module unloaded.
Cause: The ADVM driver was unloaded.
ADVMK-00004: Volume %2 in diskgroup %3 created.
Cause: An ADVM volume was created.
ADVMK-00005: The attempt to create volume %2 in diskgroup %3 failed.
Action: None
ADVMK-00006: Volume %2 in diskgroup %3 disabled.
Cause: The ADVM volume was disabled or deleted.
ADVMK-00007: The attempt to disable volume %2 in diskgroup %3 failed.
Action: None
ADVMK-00008: The attempt to open/mount volume %2 in diskgroup %3 failed.
Action: None
ADVMK-00009: Volume %2 in diskgroup %3 resized, new size is %4 MB.
Cause: An ADVM volume was resized.
ADVMK-00010: Mirror recovery for volume %2 in diskgroup %3 started.
Cause: A volume needing recovery was mounted.
ADVMK-00001 to ADVMK-00028 5-1

ADVMK-00011: Mirror recovery for volume %2 in diskgroup %3 completed.
Cause: Mirror recovery finished successfully.
ADVMK-00012: Mirror recovery for volume %2 in diskgroup %3 failed.
Cause: Volume mirror recovery failed.
ADVMK-00013: Cluster reconfiguration started.
Action: None
ADVMK-00014: Cluster reconfiguration completed.
Action: None
ADVMK-00015: Cluster reconfiguration failed.
Cause: Informational. .
Action: None
ADVMK-00016: The ASM instance was shutdown.
Cause: ASM was shutdown.
ADVMK-00017: The ASM instance terminated unexpectedly. All ADVM volumes
will be taken offline.
Cause: ASM aborted or was shutdown with the 'abort' keyword.
Action: Close all applications using these volumes and unmount the file systems.
After restarting the instance, you may need to re-enable the volumes for use.
ADVMK-00018: Diskgroup %2 was dismounted with the force option. All ADVM
volumes in this diskgroup will be taken offline.
Cause: The diskgroup was force dismounted.
Action: Close all applications using these volumes and unmount the file systems.
After re-mounting the diskgroup, you may need to re-enable the volumes for use.
ADVMK-00019: Volume %2 in disk group %3 was taken offline, all attempts to
read or write to this volume will fail.
Cause: The volume was in use when either ASM aborted, or the diskgroup containing
the volume was force dismounted.
Action: The volume must be dismounted.
ADVMK-00020: A read error was reported to the ASM instance for volume %2 in
diskgroup %3.
Cause: A I/O read request returned failure from one of the disks hosting the volume.
5-2 Error Messages
ADVMK-00021: A write error was reported to the ASM instance for volume %2 in
disk group %3.
Cause: A I/O write request return failure from one of the disks hosting the volume.
ADVMK-00022: An internal error occurred.
Cause: An internal ADVM error occurred.
ADVMK-00023: Volume name collision between %2 and %3.
Cause: Volume name collision occurred.
ADVMK-00024: WARNING: the OKS and ADVM drivers have different build
information.
Cause: Warning - The ADVM label version should match the OKS label version.
Action: None
ADVMK-00025: ADVM build %2.
Action: None
ADVMK-00026: ADVM contains fixes '%2'.
Action: None
ADVMK-00027: OKS build %2.
Action: None
ADVMK-00028: OKS contains fixes '%2'.
Action: None
ADVMK-00001 to ADVMK-00028 5-3
5-4 Error Messages
6
AMDU-00200 to AMDU-00503
AMDU-00200: Unable to read [number] bytes from Disk Nnumber at offset [number]
Cause: A read operation failed for the reported disk.
Action: Ensure that the disk is functioning properly.
AMDU-00201: Disk Nnumber: 'string'
Cause: An error occurred with the reported disk. This message indicates the disk path
name for the AMDU reported disk number.
Action: Refer to additional message(s) for details.
AMDU-00202: Cannot reopen disk Nnumber
Cause: Attempt to reopen disk failed.
AMDU-00203: File Deleted. Cannot extract file string.
Cause: Specified ASM file does not exist.
Action: Correct the ASM file number or name specified for extract.
AMDU-00204: Disk Nnumber is in currently mounted diskgroup string.
Cause: Specified ASM file does not exist.
Action: Ensure that the ASM file number or name is specified correctly.
AMDU-00205: Disk Nnumber open failed during deep discovery.
Cause: Attempt to open disk failed during discovery.
AMDU-00206: Shallow discovery failed for string with asmlib string.
Cause: Attempt to discover ASMLIB disks failed.
AMDU-00207: Shallow discovery failed for string.
Cause: Attempt to discover disks failed.
AMDU-00208: File directory block not found. Cannot extract file string.
Cause: File directory block for specified file is out of bounds.
Action: Correct the ASM file number or name specified for extract.
AMDU-00209: Corrupt block found: Disk Nnumber AU [number] block [number]
type [number]
Cause: Block validation failed for reported block
AMDU-00200 to AMDU-00503 6-1

AMDU-00210: No disks found in diskgroup string
Cause: No disks were discovered for the specified disk group.
Action: Ensure that the disk group name is entered correctly and that the member
disks are discoverable.
AMDU-00211: Inconsistent disks in diskgroup string.
Cause: Disk discovery discovered disks with identical names in multiple disk groups.
Action: Specify the disk discovery string so as to avoid doscovery of disks with
nonunique names.
AMDU-00212: Scan of diskgroup string does not appear in report.
Cause: AMDU cannot locate information about the specified disk group in the report
file.
Action: Ensure that the -directory option points to a directory with a report file and
dump for the specified disk group.
AMDU-00213: Disk Nnumber not found for group string
Cause: AMDU encountered a map file entry for a disk that does not exist in the the
report file. The mapfile may have been corrupted.
Action: Re-create the original dump. If the operation still fails, contact Oracle Support
Services.
AMDU-00214: Image files were not created for diskgroup string.
Cause: The original AMDU dump request specified -noimage.
Action: Re-create the AMDU dump including image files.
AMDU-00215: Mirror miscompares on number blocks of file string
Cause: Comparison of mirrored blocks revealed mismatches.
AMDU-00216: 0xbadfda7a written to number blocks of file string
Cause: AMDU was unable to read a number of blocks from the disk. It has written
"0xbadfda7a" in place of these blocks.
AMDU-00218: Voting file not found. Cannot extract file string.
Cause: Voting file is not present in specified disk group.
Action: Ensure that the disk group name is specified correctly.
AMDU-00500: Operating system dependent operation:string failed with status:
string
Cause: There was an operating system call error.
AMDU-00501: Operating system failure message: string
6-2 Error Messages
AMDU-00502: failure occurred at: string

AMDU-00503: additional information: string
AMDU-00200 to AMDU-00503 6-3
6-4 Error Messages
7
ASMCMD-08001 to ASMCMD-09529
ASMCMD-08001: diskgroup 'string' does not exist or is not mounted
Cause: An operation failed because the diskgroup specified did not exist or was not
mounted by the current Oracle Automatic Storage Management (Oracle ASM)
instance.
Action: Verify that the diskgroup name specified is valid, that the diskgroup exists,
and that the diskgroup is mounted by the current Oracle ASM instance.
ASMCMD-08002: entry 'string' does not exist in directory 'string'
Cause: The specified path contained elements that did not exist.
Action: Specify an existing Oracle ASM file path.
ASMCMD-08003: command disallowed by current instance type
Cause: ASMCMD was connected to an instance with an instance type other than
Oracle Automatic Storage Management (Oracle ASM).
Action: Ensure you are connecting to an instance whose INSTANCE_TYPE parameter
is Oracle ASM.
ASMCMD-08004: Oracle ASM file path 'string' contains an invalid alias name
Cause: The path specified contained an invalid alias name.
Action: Specify a valid path.
ASMCMD-08005: directory 'string' is ambiguous
Cause: The directory on which the 'cd' command was executed translated to multiple
matches.
Action: Specify a unique directory string.
ASMCMD-08006: entry 'string' does not refer to an existing directory
Cause: The 'cd' command failed as the specified path did not exist.
Action: Specify an existing Oracle ASM file path.
ASMCMD-08007: unclosed single quotation mark
Cause: The input did not contain a closing single quotation mark.
Action: Close the single quotation mark properly.
ASMCMD-08008: both source 'string' and target 'string' cannot be from remote
instances
Cause: The 'copy' command specified both source and target files that were on remote
instances.
Action: Either the source file or the target file can be on the remote instance, but not
both.
ASMCMD-08001 to ASMCMD-09529 7-1
ASMCMD-08009: more than one source file specified, one of which is remote
Cause: The 'copy' command specified multiple source files, at least one of which was
remote.
Action: When there are multiple source files, all of them must be on the local node
only.
ASMCMD-08010: user name is not specified in remote instance connect string
'string'
Cause: The user name was not specified in the remote instance connect string.
Action: Specify the user name in the remote instance connect string.
ASMCMD-08011: instance identifier is not specified in the remote instance connect
string 'string'
Cause: An instance identifier was not specified in the remote instance connect string.
Action: Specify an instance identifier in the remote instance connect string.
ASMCMD-08012: cannot determine file type for file
Cause: The file type was incompatible with the copy operation.
Action: Specify file types which are supported by Oracle Automatic Storage
Management (Oracle ASM) such as CONTROLFILE, DATAFILE, etc.
ASMCMD-08013: cannot determine logical block size for file 'string'
Cause: During the copy operation, the logical block size of the indicated file could not
be determined. The file is corrupted or it is an internal error.
Action: Ensure that the source and destination files are valid and retry. If the source
and destination files are valid, contact Oracle Support Services.
ASMCMD-08014: file 'string' does not exist
Cause: The file specified did not exist.
Action: Specify a file that exists.
ASMCMD-08016: copy source 'string' and target 'string' failed
Cause: The 'copy' command was not successful.
Action: Examine the accompanying error messages for details.
ASMCMD-08020: could not write into trace file
Cause: Writing to the trace file failed.
ASMCMD-08021: password cannot contain the following characters $%%^&*()'" or
tab
Cause: Invalid characters were found in the specified password.
Action: Supply a password which does not contain $%%^&*()'" or tab.
ASMCMD-08022: unknown command 'string' specified
Cause: An unknown command was specified.
Action: Enter a valid command; 'asmcmd help' will list valid commands.
7-2 Error Messages
ASMCMD-08023: copying password file using Oracle ASM requires software

version 'string' or later on host 'string'
Cause: A request to copy a password file was issued to an Oracle Automatic Storage
Management (Oracle ASM) instance whose version did not support that operation.
Action: Upgrade Oracle ASM to version 12.1 or later.
ASMCMD-08024: file number could not be determined for alias name 'string'
Cause: The attempt to determine the file number for the specified alias was
unsuccessful.
Action: Ensure that the discovery string corresponds to disks for the specified disk
group.
ASMCMD-08025: Invalid file name specified. Absolute path name is required
when there is no connection to Oracle ASM instance.
Cause: The specified file name did not begin with '+'. It is therefore treated as a
relative path name which requires a connection to Oracle Automatic Storage
Management.
Action: Specify an absolute path name for the file you wish to extract. Absolute path
names begin with '+diskgroup'.
ASMCMD-08102: no connection to Oracle ASM; command requires Oracle ASM to
run
Cause: A command that requires Oracle Automatic Storage Management (Oracle
ASM) processing was issued but there was no connection to an Oracle ASM instance.
Action: Start the Oracle ASM instance and retry the command.
ASMCMD-08201: Oracle ASM not available\n string
Cause: During a copy operation, connection to the Oracle Automatic Storage
Management (Oracle ASM) instance on the remote node failed.
Action: Check ASMCMD alert log for more information.
ASMCMD-08202: internal error: string
Cause: There was an internal error.
ASMCMD-08303: invalid SPFILE 'string'
Cause: The specified server parameter file did not have a valid file type, a valid file
size, or a valid block size.
Action: Specify a valid server parameter file.
ASMCMD-08305: GPNPTOOL executable not found at 'string'
Cause: The GPNPTOOL executable was not found at the indicated location.
ASMCMD-08306: could not edit the GPnP profile
Cause: A 'gpnptool edit' command failed.
ASMCMD-08307: could not sign the GPnP profile
Cause: A 'gpnptool sign' command failed.
ASMCMD-08308: -f option cannot be used when Oracle Clusterware stack is up

Cause: The force option was supplied when the Oracle Clusterware stack was up.
Action: Remove the force option and retry.
ASMCMD-08309: could not check the status of cluster
Cause: The command 'crsctl check css' failed.
ASMCMD-08310: could not get the GPnP profile sequence number
Cause: An error occurred while retrieving the sequence number of the GPnP profile.
ASMCMD-08313: CRSCTL executable not found at 'string'
Cause: The CRSCTL executable was not found at the indicated location.
ASMCMD-08314: could not set the disk string
Cause: The command 'srvctl modify asm -d diskstring' failed.
ASMCMD-08315: could not determine the mode in which Oracle Clusterware is
running
Cause: The command 'crsctl status resource ora.crsd -init -g' failed.
ASMCMD-08316: SRVCTL executable not found at 'string'
Cause: The SRVCTL executable was not found at the indicated location.
ASMCMD-08317: could not get the Oracle ASM disk string
Cause: The command 'srvctl config asm' to get the Oracle Automatic Storage
Management (Oracle ASM) disk string failed.
ASMCMD-08318: environment variable 'string' not set
Cause: The environment variable HOSTNAME was not set before running this
command.
Action: Set the variable HOSTNAME and retry.
ASMCMD-08319: could not locate the GPnP profile
Cause: The Grid Plug and Play (GPnP) profile did not exist.
ASMCMD-08402: operation was not performed on the file string
Cause: Altering the diskgroup to change the owner, group, or permissions failed.
ASMCMD-08406: cannot accept null password
Cause: A null password was passed.
Action: A non-null password must be entered.
7-4 Error Messages
ASMCMD-08409: 'chmod' operation not allowed for string

Cause: A 'chmod' command specified the write-only permission.
Action: Specify a permission other than write-only and retry the command.
ASMCMD-08552: invalid diskgroup name 'string'
Cause: An invalid diskgroup name was specified.
Action: Ensure that the command's -G option has a non-null value passed and has
only alphanumeric characters.
ASMCMD-08554: invalid volume name 'string'
Cause: An invalid volume name was specified.
Action: Ensure that the volume name is a non-null value and has only alphanumeric
characters.
ASMCMD-08557: diskgroup 'string' volume 'string' not found
Cause: The specified diskgroup or volume was not found.
Action: Specify a valid diskgroup and volume.
ASMCMD-08558: invalid size multiplier specified
Cause: An invalid size multiplier was specified.
Action: Specify a numeric volume size terminating in 'K', 'k', 'M', 'm', 'G', 'g', T',or 't'.
ASMCMD-08559: invalid size specified
Cause: The size specified contained a valid size multiplier but contained other nonnumeric characters.
Action: Specify a numeric volume size terminating in 'K', 'k', 'M', 'm', 'G', 'g', T',or 't'.
ASMCMD-08601: could not create the analyze directory
Cause: An internally issued 'mkdir' command failed to create the analyze directory.
ASMCMD-08602: time stamp format is not recognized
Cause: The format for time stamp was invalid.
Action: Specify a time stamp in the following format: Mon Sep 19 19:56:15 2011.
ASMCMD-08603: invalid value specified for 'tracedirectory'
Cause: The specified trace directory did not exist.
Action: Supply a valid trace directory which contains the set of logs and trace files
that need to be analyzed.
ASMCMD-08604: Start time is later than end time. Please specify end time later
than start time.
Cause: Inconsistent values for --startime and --endtime options.
Action: Please specify the value of --endtime option later than the value of --starttime
option
ASMCMD-08605: cannot read the event list file.\n
Cause: The event list file did not exist or could not be read
Action: Check if the file asmevents.xml exists under $ORACLE_HOME/lib and you
have read permissions.
ASMCMD-08606: invalid value for --width option: string.\n

Cause: The provided value is not an integer more than 80.
Action: Provide a valid value for --width option.
ASMCMD-08607: invalid separator for string option: string.\n
Cause: Split pattern is not a comma.
Action: The list of values must be comma separated only.
ASMCMD-09345: could not open intermediate file 'string'\n
Cause: During Oracle Automatic Storage Management (Oracle ASM) metadata
backup operation, an attempt to open the intermediate file failed.
Action: Supply an existing file that can be read and written to by the current user.
ASMCMD-09347: invalid intermediate file 'string'
Cause: The intermediate file did not begin with string '@diskgroup_set' or there was
an error while evaluating the file contents.
Action: Ensure that the intermediate file begins with '@diskgroup_set' or contact
ASMCMD-09349: diskgroup 'string' not discovered by Oracle ASM instance;
skipping...
Cause: A non-existent diskgroup was specified during execution of the 'md_backup'
command.
Action: Specify a valid diskgroup and retry the command.
ASMCMD-09350: diskgroup 'string' not mounted by Oracle ASM instance;
skipping...
Cause: The diskgroup specified was not mounted in an Oracle Automatic Storage
Management (Oracle ASM) instance.
Action: Mount the diskgroup in the Oracle ASM instance and retry the command.
ASMCMD-09351: Oracle ASM instance has no diskgroup mounted
Cause: Oracle Automatic Storage Management (Oracle ASM) instance had no
diskgroups mounted.
Action: Mount the diskgroups to be backed up and retry the command.
ASMCMD-09352: CREATE DISKGROUP failed\nstring
Cause: SQL command execution failed.
Action: Fix the error in the SQL command and retry the command.
ASMCMD-09353: ADD or ALTER TEMPLATE failed\nstring
ASMCMD-09354: ADD ALIAS failed\nstring
ASMCMD-09355: could not find information for diskgroup 'string' in backup file
Cause: Information about the diskgroup specified was not present in the backup file.
7-6 Error Messages
Action: Check that the correct diskgroup name and the backup file are specified and
retry the command.
ASMCMD-09356: backup file 'string' is either empty or cannot be interpreted
Cause: Incorrect backup file was specified.
Action: Specify a non-empty backup file.
ASMCMD-09357: file with name 'string' already exists
Cause: The specified file already exists.
Action: Change the file name and retry the command.
ASMCMD-09358: source and target files are the same - 'string'
Cause: The source and target file were the same.
Action: Make sure the source and target files are different.
ASMCMD-09359: invalid diskgroup name 'string' specified in override options
Cause: The old diskgroup name specified in the override options was not found in the
backup file.
Action: Correct the diskgroup name and retry the command.
ASMCMD-09360: ADD or ALTER ATTRIBUTE failed\nstring
ASMCMD-09361: backup version not supported\nstring
Cause: The COMPATIBLE.ASM value of the diskgroup in the backup file was greater
than the Oracle Automatic Storage Management (Oracle ASM) instance version
executing the command.
Action: Upgrade the Oracle ASM instance and retry the command.
ASMCMD-09371: disk 'string' does not exist in diskgroup 'string'
Cause: The disk specified was not part of the diskgroup.
Action: Correct the disk name and retry the command. The disk name must match the
NAME column in the V$ASM_DISK view.
ASMCMD-09372: physical blocks string-string do not map to a valid Oracle ASM
file
Cause: The physical blocks specified were not part of any Oracle Automatic Storage
Management (Oracle ASM) file.
Action: Correct the range of the physical block numbers and retry the command.
ASMCMD-09373: not all physical blocks submitted for remapping
Cause: An attempt to submit all of the physical blocks for remapping failed.
ASMCMD-09374: KFED executable not found at 'string'
Cause: The KFED executable was not found at the indicated location.
Action: Run these commmands if using Oracle 10.2 or later: cd $ORACLE_HOME/
rdbms/lib make -f ins_rdbms.mk ikfed Run these commmands if using Oracle 10.1:
cd $ORACLE_HOME/rdbms/lib mv ssskfeded.o sskfeded.o make -f ins_rdbms.mk
$ORACLE_HOME/rdbms/lib/kfed mv kfed ../../bin/ Verify that
$ORACLE_HOME/bin/kfed exists and has the execute permission bit set.
ASMCMD-09375: error occurred when executing\n string\n\nstring

Cause: The 'lsdsk' command was not successful.
Action: Fix the error indicated in the accompanying messages and retry the
command.
ASMCMD-09378: scanning of disk headers is supported on UNIX platforms only
Cause: The 'lsdsk' command failed because scanning of disk headers is supported on
UNIX platforms only.
Action: Start the Oracle Automatic Storage Management instance and retry the
command without the -I option.
ASMCMD-09381: 'remap' command requires Oracle ASM software version string
or later.
Cause: The Oracle Automatic Storage Management (Oracle ASM) instance did not
support the 'remap' command.
ASMCMD-09382: physical blocks string-string map to an unmirrored file
Cause: Oracle Automatic Storage Management (Oracle ASM) couldnot remap an
unmirrored file.
Action: Specify physical blocks which map to a mirrored file.
ASMCMD-09383: 'mapextent' command requires Oracle ASM software version
string or later
Cause: The Oracle Automatic Storage Management (Oracle ASM) instance did not
support the 'mapextent' command.
ASMCMD-09384: 'mapau' command requires Oracle ASM software version string
or later
Cause: The current Oracle Automatic Storage Management (Oracle ASM) version did
not support this command.
Action: Upgrade to 11g Release 2 or a later version.
ASMCMD-09390: invalid XML tag 'string'
Cause: An invalid XML tag was specified.
Action: Check the value of the tag to ensure it is valid and retry.
ASMCMD-09391: invalid XML file
Cause: Certain parameters were not defined or had invalid values in the file.
Action: Check whether the required parameters are defined in the file and retry.
ASMCMD-09395: error parsing XML file: string
Cause: An error occurred while parsing the XML file.
ASMCMD-09398: element string is empty
Cause: No disks were found in the element.
Action: Add disks to this element and retry.
7-8 Error Messages
ASMCMD-09399: argument 'string' is not a valid number

Cause: A numeric value was expected in the argument.
Action: Change the argument to a numeric value.
ASMCMD-09401: command syntax error
Cause: Incorrect command syntax was specified.
Action: Refer to the command line help or to the documentation to determine the
correct syntax and options.
ASMCMD-09412: Invalid option: string
Cause: An invalid option was specified.
Action: Refer to the command line help or to the documentation to determine the
correct syntax and options.
ASMCMD-09450: missing '--dbuniquename' or '--asm' option for password file
located on a diskgroup
Cause: When trying to update the CRSD resource for a password file located on a
diskgroup, the '--dbuniquename' parameter or the '--asm' option was not specified.
Action: Execute the command again with the '--dbuniquename' parameter if the
password file is a database password file. If the password file is an ASM password
file, then execute the command with '--asm' option.
ASMCMD-09451: 'orapwd' executable was not found at 'string'
Cause: 'orapwd' executable was not found at the location.
Action: Ensure that the executable is present at the location and executable
permissions are set.
ASMCMD-09452: The password file was not found at 'string' or the path specified
does not exist.
Cause: The password file could not be located at the specified path or the path to the
password file did not exist.
Action: Ensure that the path specified is valid and that the password file is present at
that location.
ASMCMD-09453: failed to register password file as a CRS resource
Cause: An internally issued 'srvctl' command to register the password file as a CRS
resource failed.
Action: Respond based on the accompanying error messages.
ASMCMD-09454: could not create new password file
Cause: An internally issued 'orapwd' command to create the password file failed.
ASMCMD-09455: location for the new password file was not valid
Cause: An invalid path was specified to create the password file. ASMCMD can be
used to create password files only on disk groups.
Action: Specify a location on a disk group for the password file and make sure the
disk group is mounted.
ASMCMD-09456: password file should be located on an ASM disk group

Cause: An invalid path for the password file was specified. The password file should
be located on an ASM disk group.
Action: Specify a valid location on a disk group for the password file and make sure
the disk group is mounted.
ASMCMD-09457: an internally issued srvctl command failed with errors
Cause: An internally issued 'srvctl' command failed. The location of the password file
could not be retrieved from the Cluster Ready Services (CRS) resource.
ASMCMD-09458: user tried to move a password file within Operating System file
system
Cause: ASMCMD 'pwmove' or 'pwcopy' was used to move a password file to a
different location on an Operating Systen file system. This action is not supported by
the command.
Action: Ensure that ASMCMD pwmove and pwcopy commands are not used to move
password files within OS filesystems.
ASMCMD-09459: user tried to move or copy a password file within the same disk
group
Cause: ASMCMD 'pwmove' or 'pwcopy' command was used to move or copy a
password file within the same disk group. This action is not supported by the
command.
Action: Ensure that ASMCMD pwmove and pwcopy commands are not used to move
or copy password files within the disk group.
ASMCMD-09460: ASMCMD 'string' command was used on a file which is not a
password file
Cause: This particular ASMCMD command was used on a file which is not a
password file. This command supports only operations on password files.
Action: Ensure that the file specified is a password file.
ASMCMD-09461: invalid password file 'string'
Cause: The specified password file did not have a valid file type, a valid file size, or a
valid block size.
Action: Specify a valid password file.
ASMCMD-09462: could not delete password file
Cause: An internally issued 'orapwd' command to delete the password file failed.
ASMCMD-09463: operation failed due to lack of write permissions
Cause: An ASMCMD command failed because the user lacks write permissions
necessary for the operation. Either the target directory or file does not have write
permissions or the target already exists and cannot be overwritten.
Action: Specify a different target or modify the permissions for the target.
ASMCMD-09470: ASM proxy instance unavailable
Cause: An ASM proxy instance was detected but was not ONLINE.
Action: Start the 'ora.proxy_asm' resource.
7-10 Error Messages
ASMCMD-09471: cannot enable or disable volumes

Cause: Could not communicate with the ASM proxy.
ASMCMD-09472: failed to connect to the ASM proxy
Cause: An ONLINE ASM proxy was detected but the connection failed.
ASMCMD-09473: volume STATE will show as REMOTE
Cause: An ASM proxy instance was detected but was not ONLINE. An Oracle Flex
ASM instance cannot display the volume state.
Action: This error is informational only.
ASMCMD-09474: volume statistics cannot be queried
Cause: An ASM proxy instance was detected but was not ONLINE. An Oracle Flex
ASM instance cannot display the volume statistics.
ASMCMD-09475: ASM proxy SID not found
Cause: An ONLINE ASM proxy was found but the SID could not be determined.
ASMCMD-09476: failed to create the credential file for Client Cluster 'string'
Cause: Creation of the credential file for the Client Cluster failed.
Action: Enable Oracle Flex ASM. Refer to Oracle Automatic Storage Management
Administrator's Guide for configuring Oracle Flex ASM. Ensure that the user has
write access permission on the credential file. Retry the command.
ASMCMD-09477: delete Client Cluster 'string' failed
Cause: Deletion of the Client Cluster failed.
Action: Deinstall the Client Cluster using the procedure documented in the Oracle
Clusterware documentation. Retry the command.
ASMCMD-09480: There are too many connection strings for Oracle Flex ASM.
Cause: While fetching connection strings for Oracle Flex ASM, there were too many
connection strings.
Action: Run the 'lsnrctl' command to see all are valid ASM end points, or try again
later.
ASMCMD-09481: There are no connection strings available for Oracle Flex ASM.
Cause: While fetching connection strings for Oracle Flex ASM, there were no
connection strings available.
Action: Make sure ASM is running and is registered.
ASMCMD-09482: Unknown error happened while fetching connection strings for
FlexASM
Cause: While fetching connection string for FlexASM, unknown error reported.
Action: Check ASM is running and is registered and retry.
ASMCMD-09485: Operations on the ASM SPFILE require the SYSASM privilege.

Cause: An attempt to modify the ASM SPFILE was made without the SYSASM
privilege.
Action: Retry the operation as SYSASM.
ASMCMD-09487: 'string' cannot be run with 'string' privilege
Cause: Command was executed with lower privilege
Action: Retry with appropriate privilege.
ASMCMD-09488: operations on Client Cluster require SYSASM privilege
Cause: An attempt was made to create or delete a Client Cluster without the SYSASM
privilege.
Action: Retry the operation as SYSASM.
ASMCMD-09501: Clear timestamp for OS trail type requires RAC instance number
Cause: There was no RAC instance number specified to clear timestamp for OS
trailtype
Action: Specify the RAC Instance number for OS trail type.
ASMCMD-09502: Set timestamp for OS trail type requires RAC instance number
Cause: RAC instance number was not specified while OS trail type was specified.
Action: Provide a RAC instance number for OS trail type for set timestamp operation.
ASMCMD-09511: failed to obtain required AFD disk string from Oracle Local
Repository
Cause: The AFD disk string required for this operation could not be retrieved from
the Oracle Local Repository (OLR).
Action: Check that Oracle Clusterware is properly configured using 'ocrcheck -local'.
ASMCMD-09512: failed to update AFD disk string in Oracle Local Repository.
Cause: An error occurred while setting AFD disk string.
Action: Check that Oracle Clusterware is properly configured using 'ocrcheck -local'.
ASMCMD-09513: ASM disk label set operation failed.\nstring
Cause: An error occurred while setting the ASM label.
Action: Examine the accompanying error messages and correct the problem indicated,
then retry the afd_label operation.
ASMCMD-09514: ASM disk label clear operation failed.\nstring
Cause: An error occurred while clearing the ASM label.
Action: Examine the accompanying error messages and correct the problem indicated,
then retry the afd_unlabel operation.
ASMCMD-09515: KFOD executable not found at 'string'
Cause: The KFOD executable was not found at the indicated location.
ASMCMD-09516: AFDTOOL executable not found at 'string'
Cause: The AFDTOOL executable was not found at the indicated location.
7-12 Error Messages
ASMCMD-09517: AFDROOT executable not found at 'string'

Cause: The AFDROOT executable was not found at the indicated location.
ASMCMD-09518: AFDDRIVERSTATE executable not found at 'string'
Cause: The AFDDRIVERSTATE executable was not found at the indicated location.
ASMCMD-09519: ASMLib is present with ASM disk string 'string'; command
requires default ASM disk string
Cause: An attempt was made to configure AFD when ASMLib was present. To
configure AFD when ASMLib is present, the ASM disk string needs to be a default
string. Otherwise, when the Oracle Clusterware stack is restarted, the AFD devices
cannot be discovered.
Action: Use a SQL command or ASMCMD command to set the ASM disk string to be
default empty string. Refer to the product documentation and follow the procedure to
configure AFD.
ASMCMD-09520: AFD is not 'string'
Cause: AFD was either not supported, not installed, or not loaded.
ASMCMD-09521: AFD is already configured
Cause: AFD was already configured and loaded on the node.
Action: Run the command when AFD is not configured. Refer to the product
documentation and follow the procedure to configure AFD.
ASMCMD-09522: Insufficient permission to execute the command. Require
privileged user
Cause: A non-privileged user attempted to execute a command requiring privileges.
Action: Issue the command again as a privileged user.
ASMCMD-09523: command cannot be used when Oracle Clusterware stack is up
Cause: The command was executed when the Oracle Clusterware stack was up.
Action: Stop Oracle Clusterware using 'crsctl stop crs' command and retry.
ASMCMD-09524: AFD configuration failed 'string'
Cause: The afd_configure command was not successful.
Action: Examine the accompanying error messages, correct the problem indicated and
then retry the command. Check ASMCMD alert log for more information.
ASMCMD-09525: AFD deconfiguration failed 'string'
Cause: The afd_deconfigure command was not successful.
Action: Examine the accompanying error messages, correct the problem indicated and
then retry the command. Check ASMCMD alert log for more information.
ASMCMD-09526: The AFD state is 'string' and filtering is 'string' on host 'string'
Cause: User requested to retrieve the status of AFD on the node.
Action: Note the status of AFD and its filtering mode.
ASMCMD-09527: AFD is loaded, but resource ora.driver.afd does not exist

Cause: The command was executed with AFD loaded on the node but its OHASD
resource ora.driver.afd did not exist.
Action: Forcibly configure AFD using the 'ASMCMD afd_configure -f' command.
ASMCMD-09528: disk 'string' does not exist
Cause: The disk specified did not exist.
Action: Specify a disk that exists.
ASMCMD-09529: The executable 'string' is either not found or non-executable in
the\nlocation(s) string
Cause: The executable file is either not found or non executable in the specified
location(s). It must be available in any one of the specified location(s).
7-14 Error Messages
8
AUD-00611 to AUD-00809
AUD-00611: unable to access the BLOB for reading
Cause: The BLOB could not be opened for reading.
AUD-00612: unable to open export destination file
Cause: The file could not be created or opened.
Action: Check that the file does not refer to an existing directory. Check that the file is
not locked by another application.
AUD-00613: export destination access denied
Cause: Permission to write to destination file was denied.
Action: Refer to the Oracle Multimedia documentation for information on granting
privileges for the export() method.
AUD-00614: I/O error during export
Cause: The export operation failed because of an I/O error.
Action: Check OS logs and contact Oracle Support Services.
AUD-00702: unable to initialize audio processing environment
Cause: The initalization of the audio processing procedure failed.
Action: See the database administrator to make sure that enough memory has been
allocated to JServer. If JServer does have enough memory, contact Oracle Support
Services.
AUD-00703: unable to read audio data
Cause: An error occurred while accessing the audio source.
Action: Make sure the audio source is valid. For external sources, make sure all access
priviliges are granted.
AUD-00704: invalid input format or corrupted input data
Cause: The audio data in the source was not in the format specified by the format
field of the audio object. In some unusual cases, the audio data is actually corrupted.
Action: Provide a correct value in the format field. If the correct value is unknown,
put NULL in the format field to invoke the DEFAULT format plug-in.
AUD-00705: unsupported input format
Cause: The file format of the audio data was not supported. This error can only occur
in the DEFAULT format plug-in package.
Action: Refer to the Oracle Multimedia documentation for supported formats.
AUD-00611 to AUD-00809 8-1
AUD-00706: unsupported or corrupted input format

Cause: The audio data was either corrupted or the file format was not supported.
Action: Refer to the Oracle Multimedia documentation for supported formats. If the
audio data is not corrupted and is in a supported file format, contact Oracle Support
Services.
AUD-00707: unable to read empty audio data
Cause: There is no data in the audio object.
Action: Refer to the Oracle Multimedia documentation for information on how to
populate the audio object with audio data.
AUD-00713: internal error while parsing audio data
Cause: An internal error occurred during parsing.
AUD-00714: internal error
Cause: An internal error occurred.
AUD-00721: unable to find format plug-in package
ORDPLUGINS.ORDX_string_AUDIO
Cause: Custom audio plug-in for user-specified format was not found.
Action: Ensure correct audio format is specified or proper custom audio plug-in
package is installed.
AUD-00802: name of index is limited to 22 characters
Cause: The user specified an index name that is more than 22 characters long.
Action: Drop this index, and issue the CREATE INDEX statement again with a name
that is at most 22 characters long.
AUD-00803: internal error while processing WHERE clause
Cause: The WHERE clause could not be properly processed.
AUD-00806: first argument to SpeechContains must be a column
Cause: The first argument to SpeechContains is not a column. This is not allowed.
Action: Make sure that the first argument to SpeechContains is a column in a database
table.
AUD-00807: SpeechContains: index of indextype ORDSpeechIndex is required
Cause: SpeechContains was used without an associated index of indextype
ORDSpeechIndex.
Action: Make sure that SpeechContains is used in the context of an index of indextype
ORDSpeechIndex. See the Oracle Multimedia documentation for sample usage
scenarios.
AUD-00808: ORDSpeechIndex: unable to CREATE internal Text index
Cause: CREATE INDEX for ORDSpeechIndex failed when trying to create internal
Text index.
Action: Make sure that you are supplying a valid parameter string. See
SpeechIndexing and Oracle Text documentation for descriptions of a valid parameter
8-2 Error Messages
string for CREATE INDEX. To return to a consistent state, issue a DROP INDEX
command.
AUD-00809: ORDSpeechIndex: unable to ALTER REBUILD internal Text index
Cause: ALTER INDEX REBUILD for ORDSpeechIndex failed when trying to alter
rebuild internal Text index.
Action: Make sure that you are supplying a valid parameter string. See
SpeechIndexing and Oracle Text documentation for descriptions of a valid parameter
string for ALTER INDEX REBUILD. To return to a consistent state, issue a ALTER
INDEX REBUILD PARAMETERS('optimize full') command.
AUD-00611 to AUD-00809 8-3
8-4 Error Messages
9
CLSCH-01001 to CLSCH-03718
CLSCH-01001: Oracle Cluster Health Analysis Service (OCHAD) started on host
{0}.
Cause: The Oracle Cluster Health Analysis Service (OCHAD) was successfully
started.
Action: None
CLSCH-01002: Oracle Cluster Health Analysis Service (OCHAD) aborted on host
{0}. Details in {1}.
Cause: The Oracle Cluster Health Analysis Service (OCHAD) aborted due to an
internal error. Check the OCHAD log file to determine the cause.
Action: Determine whether the Oracle Cluster Health Analysis Service (OCHAD) is
online on the node listed in the message using the 'srvctl status cha -node node name'
command. If OCHAD is offline, restart OCHAD using the 'srvctl stop cha -node node
name -f' command followed by the 'srvctl start cha -node node name' command. If the
problem persists, contact Oracle Support Services.
CLSCH-01003: Oracle Cluster Health Analysis Service (OCHAD) failed to calibrate
on host {0}. Details in {1}.
Cause: The Oracle Cluster Health Analysis Service (OCHAD) failed to calibrate due to
an internal error.
Action: Check the OCHAD calibration log file to determine the cause. If the problem
CLSCH-02001: Oracle Cluster Health Analysis Service (OCHAD) failed to calibrate.
CLSCH-02002: There is no calibration data. Calibration failed.
Cause: There was no calibration data available in the specified time range.
Action: Reissue the 'oclumon calibrate' command with a valid time range. Refer to the
product documentation or to the online help for information about the command.
CLSCH-02003: There is not enough calibration data. Calibration failed.
Cause: There was not enough calibration data available in the specified time range.
Action: Reissue the 'oclumon calibrate' command with a valid time range. Refer to the
product documentation or to the online help for information about the command.
CLSCH-02004: Oracle Cluster Health Analysis Service (OCHAD) failed to retrieve
calibration data from the local instance "{0}".
Cause: An error occurred while connecting to or while retrieving data from the local
database instance.
CLSCH-01001 to CLSCH-03718 9-1
Action: Take the following steps: 1) Examine the accompanying error messages. If
possible, correct the issue reported. 2) Check the status of the local instance of the
target database using the 'srvctl status database' command. If the target database is
offline, issue the 'srvctl start database' command. Reissue the 'oclumon calibrate'
command from a node where an instance of the target database is running. 3) If you
are unable to determine or correct the problem, contact Oracle Support Services.
CLSCH-02005: Oracle Cluster Health Analysis Service (OCHAD) failed due to a
Grid Infrastructure Management Repository error.
Cause: A Grid Infrastructure Management Repository error occurred.
Action: Take the following steps: 1) Examine the accompanying error messages. If
possible, correct the issue reported. 2) Issue a 'srvctl status mgmtdb' command to
determine the status of the Grid Infrastructure Management Repository. If the Grid
Infrastructure Management Repository is offline, issue the 'srvctl start mgmtdb'
command to start it. If it fails to start, examine the database instance alert log to
determine what happened. 3) If you are unable to determine or correct the problem,
CLSCH-02401: An invalid target type "{0}" was specified to the Oracle Cluster
Health Analysis Service (OCHAD).
Cause: A request was made to the Oracle Cluster Health Analysis Service (OCHAD)
with an invalid target type. This is an internal error.
CLSCH-02402: The target name "{0}" specified to the Oracle Cluster Health Analysis
Service (OCHAD) will be ignored on this node.
with a target that was not available on this node. OCHAD took no action.
Action: No action required.
CLSCH-02403: The Oracle Cluster Health Analysis Service (OCHAD) is already
monitoring target "{0}".
to monitor a target that was already being monitored. OCHAD took no action.
CLSCH-02404: The Oracle Cluster Health Analysis Service (OCHAD) is not
to stop monitoring a target that was not being monitored. OCHAD took no action.
CLSCH-02405: The Oracle Cluster Health Analysis Service (OCHAD) failed to start
CLSCH-02406: The Oracle Cluster Health Analysis Service (OCHAD) failed to stop
9-2 Error Messages
CLSCH-02407: The model '{0}' does not exist.

Cause: The specified model did not exist.
Action: Issue the 'chactl config' command to list the available models. Retry the chactl
command using one of the available models.
CLSCH-02408: The model '{0}' is configured to be used for monitoring.
Cause: An attempt to remove or rename a model specified one that is configured to be
used for monitoring.
Action: Issue the 'chactl query model -verbose' command to determine by which
target the model is currently being used. Do not remove or rename the model while
the model is configured to be used by any target.
CLSCH-02409: Cannot specify both '-node' and '-model' when server pools are
configured.
Cause: A single model is used by all nodes in a server pool for a given target. The
request was rejected because it tried to change the model for a target for a subset of
nodes in the server pool.
Action: Issue the 'srvctl monitor' command again without specifying both '-node' and
'-model' option for a give target.
CLSCH-02410: server pool name specified in a cluster without user-defined server
pools
Cause: An attempt was made to start or stop monitoring a target using the 'serverpool' option in a cluster without user-defined server pools.
Action: Reissue the command without a server pool name. Refer to the product
documentation or to the online help for information about the command.
CLSCH-02411: The Oracle Cluster Health Analysis Service (OCHAD) failed to
determine status of target "{0}".
CLSCH-02412: Monitoring is enabled and will start when the database starts up.
Cause: Status message.
Action: None
CLSCH-03601: missing mandatory option: {0}
Cause: The specified mandatory command option was missing.
Action: Use chactl with the -help option to display option details for the command
and ensure that all of the mandatory options are specified.
CLSCH-03602: invalid command line option: {0}
Cause: An invalid command line option was specified.
Action: Review the command inline help or documentation, and specify appropriate
options.
CLSCH-03603: failed to start monitoring database {0}
Cause: An attempt to start monitoring the specified database failed.
CLSCH-03604: failed to start monitoring database {0} on node {1}

Cause: An attempt to start monitoring an instance of the specified database on the
specified node failed.
CLSCH-03605: failed to start monitoring host {0}
Cause: An attempt to start monitoring the specified host failed.
CLSCH-03606: failed to stop monitoring database {0}
Cause: An attempt to stop monitoring the specified database failed.
CLSCH-03607: failed to stop monitoring database {0} on node {1}
Cause: An attempt to stop monitoring an instance of the specified database on the
specified node failed.
CLSCH-03608: failed to stop monitoring host {0}
Cause: An attempt to stop monitoring the specified host failed.
CLSCH-03609: failed to start or stop monitoring due to an internal error
Cause: An internal error occurred during an attempt to start or stop monitoring.
CLSCH-03610: An unexpected error occurred in Cluster Health Advisor control
utility.
Cause: An unexpected error occurred in the Cluster Health Advisor control utility.
CLSCH-03611: Database name to start monitoring is missing.
Cause: An attempt to start monitoring a database failed because the name of the
database to start monitoring was not specified.
CLSCH-03612: Database name to stop monitoring is missing.
Cause: An attempt to stop monitoring a database failed because the name of the
database to stop monitoring was not specified.
CLSCH-03613: failed to retrieve the status of Oracle Cluster Health Analysis
Service
Cause: An attempt to get the status of Oracle Cluster Health Analysis Service failed.
Service for nodes {0}
Cause: An attempt to retrieve the status of Oracle Cluster Health Analysis Service for
the specified nodes failed.
9-4 Error Messages
Action: Examine the accompanying error messages for details, rectify the problems
reported and retry. Otherwise, contact Oracle Support Services.
CLSCH-03616: failed to start monitoring hosts
Cause: An attempt to start monitoring hosts failed.
CLSCH-03617: failed to start monitoring hosts in server pool {0}
Cause: An attempt to start monitoring hosts in the specified server pool failed.
CLSCH-03618: failed to start monitoring database {0} on server pool {1}
Cause: An attempt to start monitoring the specified database on the specified server
pool failed.
CLSCH-03619: failed to stop monitoring hosts
Cause: An attempt to stop monitoring hosts failed.
CLSCH-03620: failed to stop monitoring hosts in server pool {0}
Cause: An attempt to stop monitoring hosts in the specified server pool failed.
CLSCH-03621: failed to stop monitoring database {0} on server pool {1}
Cause: An attempt to stop monitoring the specified database on the specified server
pool failed.
Service for server pool {0}
Cause: An attempt to retrieve the status of Oracle Cluster Health Analysis Service for
the specified server pool failed.
CLSCH-03623: failed to request action on Oracle Cluster Health Analysis Service
Cause: An attempt to request action on Oracle Cluster Health Analysis Service failed.
CLSCH-03624: failed to start monitoring database {0} using model {1}
Cause: An attempt to start monitoring the specified database using the specified
model failed.
CLSCH-03625: failed to start monitoring database {0} on node {1} using model {2}
Cause: An attempt to start monitoring an instance of the specified database on the
specified node using the specified model failed.
CLSCH-03626: failed to start monitoring host {0} using model {1}

Cause: An attempt to start monitoring the specified host using the specified model
failed.
CLSCH-03627: failed to start monitoring hosts using model {0}
Cause: An attempt to start monitoring hosts using the specified model failed.
CLSCH-03628: failed to start monitoring hosts in server pool {0} using model {1}
Cause: An attempt to start monitoring hosts in the specified server pool using the
specified model failed.
CLSCH-03629: failed to start monitoring database {0} on server pool {1} using model
{2}
Cause: An attempt to start monitoring the specified database on the specified server
pool using the specified model failed.
CLSCH-03630: Hosts are already being monitored using model {0}.
Cause: A request to monitor hosts was rejected because the hosts were already being
monitored using the specified model.
CLSCH-03631: Hosts are already being monitored.
Cause: A request to monitor hosts was rejected because the hosts were already being
monitored.
CLSCH-03632: Hosts in server pool {0} are already being monitored using model {1}.
Cause: A request to monitor hosts in the specified server pool was rejected because
the hosts were already being monitored using the specified model.
CLSCH-03633: Hosts in server pool {0} are already being monitored.
Cause: A request to monitor hosts in the specified server pool was rejected because
the hosts were already being monitored.
CLSCH-03634: Host {0} is already being monitored using model {1}.
Cause: A request to monitor the specified host was rejected because the host was
already being monitored using the specified model.
CLSCH-03635: Host {0} is already being monitored.
Cause: A request to monitor the specified host was rejected because the host was
already being monitored.
9-6 Error Messages
CLSCH-03636: Database {0} is already being monitored using model {1}.

Cause: A request to monitor the specified database was rejected because the database
was already being monitored using the specified model.
CLSCH-03637: Database {0} is already being monitored.
Cause: A request to monitor the specified database was rejected because the database
was already being monitored.
CLSCH-03638: Database {0} is already being monitored in server pool {1} using
model {2}.
Cause: A request to monitor the specified database in the specified server pool was
rejected because the database was already being monitored using the specified model.
CLSCH-03639: Database {0} is already being monitored in server pool {1}.
Cause: A request to monitor the specified database in the specified server pool was
rejected because the database was already being monitored.
CLSCH-03640: Database {0} is already being monitored on host {1} using model {2}.
Cause: A request to monitor the specified database on the specified node was rejected
because the database was already being monitored using the specified model.
CLSCH-03641: Database {0} is already being monitored on host {1}.
Cause: A request to monitor the specified database on the specified node was rejected
because the database was already being monitored.
CLSCH-03642: Hosts are not being monitored.
Cause: A request to stop monitoring hosts was rejected because the hosts were
already not being monitored.
CLSCH-03643: Hosts in server pool {0} are not being monitored.
Cause: A request to stop monitoring hosts in the specified server pool was rejected
because the hosts were already not being monitored.
CLSCH-03644: Host {0} is not being monitored.
Cause: A request to stop monitoring the specified host was rejected because the host
was already not being monitored.
CLSCH-03645: Database {0} is not being monitored.
Cause: A request to stop monitoring the specified database was rejected because the
database was already not being monitored.
CLSCH-03646: Database {0} is not being monitored in server pool {1}.

Cause: A request to stop monitoring the specified database in the specified server
pool was rejected because the database was already not being monitored.
CLSCH-03647: Database {0} is not being monitored on node {1}.
Cause: A request to stop monitoring the specified database on the specified node was
rejected because the database was already not being monitored.
CLSCH-03648: failed to start monitoring the target because server pool {0} is a builtin server pool
Cause: A request to start monitoring the target was rejected because the specified
server pool was a built-in server pool.
Action: Omit the server pool, or specify a server pool that is not built-in.
CLSCH-03649: failed to stop monitoring the target because server pool {0} is a builtin server pool
Cause: A request to stop monitoring the target was rejected because the specified
CLSCH-03650: failed to retrieve the status of the target because server pool {0} is a
built-in server pool
Cause: A request to retrieve the status of the target was rejected because the specified
CLSCH-03651: invalid empty model name specified
Cause: A request to start monitoring the target was rejected because the specified
model name was an empty string.
Action: Reissue the command without a model name if the user wants the target to be
monitored with the current model in use, or reissue the command with an existing
model name that is different from the current model in use.
CLSCH-03652: The specified option combination, -node with -model, is not
permitted when server pools are configured.
Cause: An attempt to start monitoring the target was rejected because the specified
option combination, -node with -model, is not permitted when server pools are
configured.
Action: Check the specified option combination.
CLSCH-03653: The specified option, -serverpool, is not permitted when server
pools are not configured.
Cause: An attempt to start or stop monitoring the target was rejected because the
specified option, -serverpool, is not permitted when server pools are not configured.
Action: Check the specified option.
CLSCH-03654: An internal error occurred in Cluster Health Advisor model
calibration.
Cause: An internal error occurred during Cluster Health Advisor model calibration.
9-8 Error Messages
CLSCH-03655: Database {0} does not exist.

Cause: The specified database did not exist.
Action: Specify a database that exists.
CLSCH-03656: invalid node name: {0}
Cause: An attempt to calibrate the model was rejected because an invalid node name
was provided.
Action: Specify a valid node name.
CLSCH-03657: Database {0} has no instance configured on node {1}.
Cause: The specified database had no instance configured on the specified node.
Action: Omit the node, or specify a node on which the database has a configured
instance.
CLSCH-03658: Server pool {0} does not exist.
Cause: An attempt to calibrate the model was rejected because the specified server
pool did not exist.
Action: Specify a server pool that exists.
CLSCH-03659: invalid command line syntax
Cause: The syntax of the command was incorrect.
Action: Examine the usage provided for this command and use the correct syntax.
CLSCH-03660: The model "{0}" already exists.
Cause: An attempt to create the model was rejected because the model already
existed.
Action: Specify a new model name or use the -force option to overwrite the model.
CLSCH-03661: The model "{0}" is currently used for monitoring.
Cause: An attempt to calibrate the model was rejected because the model is currently
used for monitoring.
Action: Stop monitoring by issuing the 'chactl unmonitor' command before
calibrating.
CLSCH-03664: Oracle Cluster Health Analysis Service encountered errors: {0}
Cause: An attempt to get the status of Oracle Cluster Health Analysis Service failed.
CLSCH-03685: Option '-node' cannot be used with option '-db' or '-serverpool'.
Cause: A 'chactl config' command specified conflicting options.
Action: Reissue the command with the correct options.
CLSCH-03686: failed to retrieve server pool {0} configuration for the database {1}
Cause: An attempt to retrieve Oracle Cluster Health Analysis Service configuration
for the specified database on the server pool failed.
CLSCH-03687: failed to retrieve Oracle Cluster Health Analysis Service
configuration for the specified database {0}
Cause: An attempt to retrieve Oracle Cluster Health Analysis Service configuration
for the specified database failed.

CLSCH-03688: failed to retrieve Oracle Cluster Health Analysis Service
configuration for the specified server pool {0}
Cause: An attempt to retrieve Oracle Cluster Health Analysis Service configuraiton
details for the specified serverpool failed.
CLSCH-03689: failed to retrieve the cluster configuration for Oracle Cluster Health
Analysis Service
Cause: An attempt to retrieve the cluster configuration for Oracle Cluster Health
Analysis Service failed.
CLSCH-03690: A SQL error occurred while retrieving information from Grid
Infrastructure Management Repository.
Cause: An SQL error occurred while connecting to or reading from Grid
CLSCH-03704: no model found
Cause: An attempt to query models failed because no models existed in the database.
This is an internal error.
CLSCH-03708: invalid attempt to remove or rename a base model
Cause: An attempt to remove or rename a base model was rejected.
Action: Reconsider the need for the request, or specify a model that is not a base
model.
CLSCH-03709: successfully dumped the CHA statistics to location "{0}"
Action: None
CLSCH-03710: conflicting start and end times for dump
Cause: The specified end date and time for a CHA dump was not later than the start
date and time.
Action: Specify a dump end date and time later than the start date and time.
CLSCH-03711: No data exists between start time {0} and end time {1}.
Cause: A query calibration command specified a time range in which no data existed
in the database.
Action: Specify a time range with existing data.
CLSCH-03712: 'dataset' {0} not found
Cause: A query calibration command specified an unknown 'dataset' name.
Action: Specify a known 'dataset' name.
CLSCH-03713: invalid command line syntax at '{0}'
Cause: The syntax of the command was incorrect.
Action: Examine the usage provided for this command and retry using correct syntax.
9-10 Error Messages
CLSCH-03714: Start time {0} is not earlier than end time {1}.
Cause: Specified end time was earlier than the start time.
Action: Retry, specifying an end time that is later than the start time.
CLSCH-03715: No monitored data exists in the database.
Cause: A query calibration command was executed when there was no monitored
data in the database.
Action: Monitor the target for some time and then retry the command.
CLSCH-03716: Specified time is smaller than the allowed minimum {0} hours.
Cause: An attempt to modify the retention time for targets failed because the specified
time was not greater than the allowed minimum retention time.
Action: Retry, specifying a retention time that is greater than the minimum retention
time.
CLSCH-03717: target retention successfully set to {0} hours
Action: None
CLSCH-03718: repository successfully resized for {0} targets
Action: None
CLSCH-01001 to CLSCH-03718 9-11
9-12 Error Messages
10
CLSDNSSD-00000 to CLSDNSSD-03999
CLSDNSSD-00000: no error.
Cause: Operation was successful.
Action: No action needed.
CLSDNSSD-00001: unknown error has occurred.
Cause: an unknown error has occurred.
Action: This error should not be visible to the user. If it occurs, please contact Oracle
Customer Support.
CLSDNSSD-00002: no such name.
Customer Support.
CLSDNSSD-00003: memory allocation failed.
Cause: The DNS service discovery component was unable to allocate enough
memory.
Action: If memory is low on the system, terminate other processes and/or threads
and try the operation again. Otherwise, this is an internal error and Oracle Customer
Support should be contacted.
CLSDNSSD-00004: invalid parameter.
Cause: An parameter which had an invalid value was passed by the caller to the DNS
service discovery library. This is an internal error.
Customer Support.
CLSDNSSD-00005: invalid reference.
Cause: An unknown DNS record reference was encountered.
Customer Support.
CLSDNSSD-00006: invalid state.
Customer Support.
CLSDNSSD-00007: invalid flags.
Customer Support.
CLSDNSSD-00000 to CLSDNSSD-03999 10-1
CLSDNSSD-00008: unsupported operation.

Cause: The DNS service discovery component attempted to perform an operation not
supported by the library.
Customer Support.
CLSDNSSD-00009: uninitialized.
Customer Support.
CLSDNSSD-00010: service already registered.
Cause: The user attempted to register a service that was already registered.
Action: A service should only be registered once.
CLSDNSSD-00011: service name conflict.
Cause: The user attempted to register a service whose name already exists.
Action: A different service name needs to be used.
CLSDNSSD-00012: invalid data in record.
Cause: The DNS service discovery component attempted to use a record with invalid
data. This is an internal error.
Customer Support.
CLSDNSSD-00013: firewall.
Customer Support.
CLSDNSSD-00014: client software incompatible with server.
Cause: The version of the client software used by the DNS service discovery interface
is not compatible with the version of the server software.
Customer Support.
CLSDNSSD-00015: bad interface index.
Customer Support.
CLSDNSSD-00016: update refused.
Customer Support.
CLSDNSSD-00017: no such record.
Customer Support.
10-2 Error Messages
CLSDNSSD-00018: no auth.
Customer Support.
CLSDNSSD-00019: no such key.
Customer Support.
CLSDNSSD-00020: NAT Traversal.
Customer Support.
CLSDNSSD-00021: Double NAT traversal.
Customer Support.
CLSDNSSD-00022: invalid time stamp in record
Cause: A DNS record contained an invalid time stamp. This is an internal error.
Customer Support.
CLSDNSSD-00023: invalid service type: "string".
Cause: The user specified a service type which does not conform to the standard
specifed by RFC's 1034 and RFC 1123. The service type must be one or more
characters and must start and end with a letter or digit. The interior characters may be
letters, digits, or hyphens.
Action: Specify a service type which conforms to the RFC.
CLSDNSSD-03999: unknown error: number.
Cause: A DNS error code was returned that is not known to the system. This is an
internal error.
Customer Support.
CLSDNSSD-00000 to CLSDNSSD-03999 10-3
10-4 Error Messages
11
CLSGN-00000 to CLSGN-32767
CLSGN-00000: no error\n
CLSGN-00003: unknown command: "string"\n
Cause: The command entered was invalid.
Action: Specify a valid command.
CLSGN-00018: parameter has no default value.
Cause: An attempt was made to reset the value of a parameter for which there is no
default value.
Action: Specify a parameter which has a default value.
CLSGN-00023: "string" is only available in interactive mode.\n
Cause: An attempt was made to run or get help for a command from the command
line which is available only in interactive mode.
Action: Change to interactive mode to run the command.
CLSGN-00024: Oracle Grid Naming Service Daemon (GNSD) aborted on node
string.
Cause: The server aborted on the specified node.
CLSGN-00025: Creation of name object for configuration file "string" failed.\n
Cause: It was not possible to create a name object for the configuration file.
Action: Examine the rest of the stack for the exact reason.
CLSGN-00028: Open of configuration file "string" failed.\n
Cause: The open of the configuration file failed.
Action: Examine the rest of the error stack for the exact reason.
CLSGN-00029: Read of configuration file "string" failed.\n
Cause: A read of the configuration file failed.
CLSGN-00030: Close of configuration file "string" failed.\n
Cause: It was not possible to close the configuration file.
CLSGN-00000 to CLSGN-32767 11-1
CLSGN-00031: Server failed to start:\nstring

Cause: The GNS server failed to start due to an error encountered by the server.
Action: Examine the message that accompanies this one for details. Also, take a look
at the server log files for more information.
CLSGN-00032: Unexpected end of line found in record "string".\n
Cause: The line ended unexpectedly. For example, the line might have ended before
the end of a quoted string was found.
Action: Specify a correctly formatted line.
CLSGN-00033: Too few arguments for value of parameter "string" Minimum:
number\n
Cause: Not enough arguments were specified for a parameter.
Action: Specify the required number of arguments.
CLSGN-00034: Too many arguments for value of parameter "string" Maximum:
number\n
Cause: The number of arguments specified for a parameter was greater than
maximum allowed.
CLSGN-00035: Record "string" contains too few fields. Minimum: number.
Specified: number.\n
Cause: The entry for a parameter in the configuration file does not contain the
required number of fields.
Action: Correct the entry to have the required number of fields.
CLSGN-00036: Record "string" contains too many fields. Maximum: number.
Specified: number.\n
Cause: The entry for a parameter in the configuration file contains more than the
maximum number of fields.
Action: Correct the entry to have the required number of fields.
CLSGN-00040: invalid value for integer parameter: "string": "string"\n
Cause: The value specified for an integer parameter was not an integer.
Action: Specify a correct value, either decimal or hexadecimal. Hexadecimal values
start with the string "0x".
CLSGN-00041: invalid value for boolean parameter "string": "string"\n
Cause: The value specified for a boolean parameter was not a boolean value.
Action: Specify a correct value. Correct values include: TRUE/FALSE, YES/NO, ON/
OFF, and 1/0.
CLSGN-00043: invalid configuration method: "string"\n
Cause: An unknown type was specified for the method used to store configuration
information.
Action: Specify a valid type.
CLSGN-00044: no file name specified.\n
Cause: No name was specified for a configuration method which uses a file as the
repository.
11-2 Error Messages
Action: Specify a file name.

CLSGN-00045: initialization failed: string\n
Cause: The initialization of GNS failed.
Action: Please examine the accompanying message for the exact reason.
CLSGN-00046: no value found for parameter "string".\n
Cause: A value was not specified for the parameter.
Action: Specify a parameter.
CLSGN-00051: unsupported query type: "string"
Cause: The query type passed in is not supported by GNS.
Action: Specify a supported query type.
CLSGN-00052: Initialization of OCR at level number failed.\n string\n
Cause: Initialization of OCR to the specified level failed.
Action: Examine the error message to determine what occurred.
CLSGN-00054: Invalid IP address: string
Cause: The IP address specified is neither in the v4 or v6 format.
Action: Specify a correct address.
CLSGN-00058: Invalid number of arguments specified: number.\n
Cause: The client program sent the wrong number of arguments over for a command.
Action: This error should not ordinarily be seen. Contact Oracle Support Services.
CLSGN-00059: Unknown command: number.\n
Cause: The server received an unknown command from the client.
Action: This error should never happen. If it does, contact Oracle Support Services.
CLSGN-00060: Conversion of string value "string" failed with error number.\n
Cause: The value of a parameter sent over from the client to number failed.
Action: Specify a valid parameter value.
CLSGN-00061: Internal error.\n
Cause: An unexpected error occurred. The rest of the error stack contains details
about the error.
Action: This error should never happen. If it does, contact Oracle Support Services.
CLSGN-00062: Server spawn failed: could not access subdirectory string under
string.\n
Cause: The server process could not be spawned because the directory where the
program resides could not be located or accessed.
Action: Make sure that the server directory exists and can be accessed by the user
starting the program.
CLSGN-00063: Server spawn failed: executable not accessible: directory: string file:
string\n
Cause: The server program could not be accessed.
Action: Make sure the server executable exists and can be accessed by the user
starting the program.
CLSGN-00000 to CLSGN-32767 11-3
CLSGN-00064: spawn of server string failed.\n

Cause: The client was unable to start the server process.
Action: More details about the failure can be found in messages that follow.
CLSGN-00065: Unable to create backup for configuration file string
Cause: The GNS server was unable to create a backup configuration file.
Action: Check the permissions in the configuration directory. Make sure that the GNS
process is permitted to create files there.
CLSGN-00068: Service advertisement stop failed.\n
Cause: GNS encountered an error when it tried to stop the advertisement of its
service.
Action: Examine the message following this one. It will indicate the cause. If it is a
number, consult rdret.h.
CLSGN-00069: Service registration failed.\n
Cause: GNS was unable to register itself with Resource Discovery.
CLSGN-00070: Service location failed.\n
Cause: The client program was not able to locate a GNS server.
Action: Examine the message following this one for a possible cause.
CLSGN-00071: Transport initialization failed.\n
Cause: GNS was unable to initialize the transport that it uses to communicate
between the client and server.
Action: Examine the messages following this one for the cause of the error.
CLSGN-00072: Connection to server failed.\n
Cause: GNS was unable to initialize the transport that it was used to communicate
between the client and server.
Action: The message following indicates the exact error that occurred.
CLSGN-00073: Send failed\n
Cause: GNS was unable to send data either from the client to the server or from the
server to the client.
CLSGN-00074: Wait for client connection failed\n
Cause: An error occurred while the server was waiting for a connection from the
client.
CLSGN-00075: Receive failed.\n
Cause: GNS was unable to receive data from its peer process.
CLSGN-00076: string Packet ignored: string.\n
Cause: The packet was ignored by the server because it was invalid. This may be
caused by another process sending malformed packets.
11-4 Error Messages
Action: Use system tools to determine if a non-GNS process is sending data to the
server.
CLSGN-00077: Invalid DNS message received.\n
Cause: The GNS server received a message from the master DNS server which was
not of the correct format. This could be due to an error by the server or because a
malicious process is sending the GNS server invalid packets.
Action: The error is informational and should not ordinarily be visible to a user. If it is
seen, contact Oracle Support Services.
CLSGN-00078: No space in left in buffer. Buffer size: number.
Cause: The buffer provided was too small to fit a piece of data.
Action: This error should ordinarily not be visible to users. If it appears, contact
CLSGN-00079: Bonjour initialization failed.\n
Cause: The function called to initialize Bonjour for use by GNS failed.
Action: Examine the accompanying Bonjour error and take corrective action.
CLSGN-00080: Wait failed.
Cause: The wait for data to be received from another process failed.
Action: This error should ordinarily not be visible to users. If it appears, contact
CLSGN-00081: The GNS service is not running.\n
Cause: The GNS service could not be contacted because it is not running.
Action: Start the GNS service.
CLSGN-00082: The GNS service is already running.\n
Cause: An attempt was made to start the GNS service, but it was already running.
Action: Shut down the GNS service before trying to start it.
CLSGN-00083: Invalid option: "string"\n
Cause: An unknown option was specified either to a client program or the server.
Action: Specify a supported option.
CLSGN-00086: Service location initialization failed.\n
Cause: The GNS client failed when it tried to initialize the Resource Discovery
subsystem.
CLSGN-00087: Listen on endpoint "string" failed.\n
Cause: The server was unable to listen for requests on the specified endpoint.
Action: The accompanying GIPC error should be examined for the exact error.
CLSGN-00088: Listen on string port number failed due to a lack of privileges.\n
Cause: The server was unable to listen on the specified port because it does not have
privilege to do so. On Linux and Unix systems, this can occur because the server is
not running as the root user.
Action: Run the server as a user with the needed privileges.
CLSGN-00000 to CLSGN-32767 11-5
CLSGN-00089: Not enough arguments specified for the "string" option. Number
specified: number. Minimum number: number.\n
Cause: Enough arguments were not specified for a command.
Action: Specify the minimum number of arguments.
CLSGN-00090: Too many arguments specified for the "string" option. Number
specified: number Maximum number: number.\n
Cause: Too many arguments arguments specified for a command.
CLSGN-00099: Multicast DNS server not running.\n
Cause: GNS was unable to send a query to the multicast DNS server because it is not
running.
Action: Start the multicast DNS server.
CLSGN-00100: The alias "string" already exists.
Cause: The specified alias already exists.
Action: Specify an alias which does not exist.
CLSGN-00101: The alias "string" does not exist.
Cause: An alias for a name could not be found.
Action: Specify an alias which exists.
CLSGN-00102: The name "string" does not exist.
Cause: The specified name could not be found.
Action: Specify a name which exists.
CLSGN-00109: No interfaces available.
Cause: GNS was unable to find any interfaces on which it can listen for requests. This
error is likely caused by the incorrect specification of the list of interfaces on which
GNS is not to listen. Alternatively, it may be caused by an error in system
configuration.
Action: Correct the list of prohibited interfaces if it was set incorrectly. If this is not
the case, check the system configuration.
CLSGN-00110: One or threads failed - check log.\n
Cause: One or more GNS failed unexpectedly.
Action: Check the log file to determine the exact reasons.
CLSGN-00111: Acquisition of privileges needed to perform operation failed.
Cause: An attempt to acquire the privileges needed failed.
Action: Examine the attached message for more details.
CLSGN-00112: Platform initialization failed.\n
Cause: GNS was unable to initialize the layer the provides system-specific services.
Action: Examine the accompanying message for details.
CLSGN-00120: Creation of configuration file "string" failed.\n
Cause: The creation of the new version of the configuration file failed.
11-6 Error Messages
CLSGN-00121: Trace level set to number.

Cause: This is an information message to indicate that the trace level was set.
Action: No action is needed.
CLSGN-00122: Dynamic messaging initalization failed - error number
Cause: The facility used to control the GNS server dynamically failed.
Action: This error should not be seen in normal use. Contact Oracle Support Services
if it appears.
CLSGN-00127: Privileged user "string" does not exist.
Cause: The user which GNS is to run as in order to run operations which require
special privileges does not exist.
Action: Specify a user which does exist on the host. This user must have the ability to
listen for requests from the DNS server.
CLSGN-00128: Unprivileged user "string" does not exist.
Cause: The user which GNS is to run as in order to perform operations which do not
require special privileges does not exist.
Action: Specify a user which exists.
CLSGN-00129: Privileged group "string" does not exist.
Cause: The group to which a user must belong in order to perform administrative
operations does not exist.
Action: Specify a group which exists on the host.
CLSGN-00130: no privileges to access OCR key "string".
Cause: It was not possible to retrieve the specified key from OCR because the user
does not have the required privileges.
Action: Either run the command as a user which has the required privileges or
configure OCR to allow retrieval of the key.
CLSGN-00131: no privileges to get value for OCR key "string".
Cause: It was not possible to retrieve the specified value from OCR because the user
does not have the required privileges.
Action: Either run the command as a user which has the required privileges or
configure OCR to allow retrieval of the key.
CLSGN-00132: user "string" not authorized to run command.
Cause: A user tried to run a command but has no permission to do so.
Action: Run the command as a user which has the proper privileges.
CLSGN-00133: Exception received:\nstring
Cause: An exception occurred on the server process.
Action: Examine the exception for details.
CLSGN-00134: Invalid name: "string".
Cause: The name to be used for a GNS operation was not valid. The name may have
no domain or be qualified with the name of subdomain serviced by GNS.
Action: Specify a correct name.
CLSGN-00000 to CLSGN-32767 11-7
CLSGN-00135: Mandatory parameter "string" is not configured.

Cause: A value was not configured for a mandatory parameter.
Action: Configure a value in the parameter repository.
CLSGN-00136: Query for network address for name "string" failed.
Cause: The query for network addresses for the given name failed.
Action: Examine the accompanying errors for for more information. If the errors
indicate that the name does not exist, register it using srvctl.
CLSGN-00138: No thread names specified.
Cause: The command requires at least one thread name to be specified.
Action: Specify at least one thread name.
CLSGN-00139: Invalid thread name "string"
Cause: The name of the thread was unknown to GNS.
Action: Specify a valid thread name.
CLSGN-00140: OCR key "string" does not exist.
Cause: The specified key cannot be found in the Oracle Cluster Registry.
Action: Specify a key that exists This exception often happens when trying to retrieve
a configuration parameter.
CLSGN-00141: The address "string" already exists.
Cause: A mapping for a address to a name already exists.
Action: Specify an address which does not exist.
CLSGN-00142: Open of OCR key "string" failed.
Cause: An error occurred while trying to open the root OCR used by GNS.
Action: Examine the accompanying exceptions for more information about the error.
This error may be caused by mis-configuration.
CLSGN-00143: Subdomain "string" already exists.
Cause: An attempt was made to create a GNS subdomain which already exists.
Action: Specify a subdomain which does not exist.
CLSGN-00144: Subdomain "string" does not exist.
Cause: The specified GNS subdomain does not exist.
Action: Specify a subdomain which exists.
CLSGN-00147: Address "string" for name "string" is not serviced by GNS.
Cause: The specified address is not served by GNS.
Action: Specify a different address or change the subnet mask used by GNS.
CLSGN-00149: Address "string" does not exist.
Cause: The specified address is not known to GNS.
Action: Specify a valid address.
CLSGN-00150: Alias "string" is invalid.
Cause: The name of the alias to be advertised was not valid. The name may have no
domain or be qualified with the name of subdomain serviced by GNS.
11-8 Error Messages
Action: Specify a correct alias.

CLSGN-00151: Name domain "string" does not match GNS subdomain "string"
Cause: The domain specified for the name does not specify the subdomain served by
GNS.
Action: Either specify the correct domain or just specify the name of the host.
CLSGN-00152: Self-check failed.
Cause: The self-check performed by GNS failed.
Action: Verify that DNS has been configured so that it forwards queries for the GNS
domain to the IP address on which the GNS server is listening. Otherwise contact
CLSGN-00153: Length of subdomain "string": string exceeds the maximum: string.
Cause: The name specified for the subdomain to be served by GNS is longer than the
maximum.
Action: Specify a shorter subdomain name.
CLSGN-00154: Invalid subdomain: "string"
Cause: The name of the subdomain does not conform to Internet standards. It must
meet the following requirments: 1. Only alphanumeric characters, periods are
hyphens are allowed; 2. It must start and end with an alphanumeric character; 3.
Consecutive periods are not allowed. In addition, the subdomain must not end with
with ".local" as it is reserved for multicast DNS.
Action: Specify a subdomain in the correct format.
CLSGN-00155: trace level number is less than the minimum number - ignoring.
Cause: The trace level specified is lower than the minimum supported.
Action: Specify a valid trace level.
CLSGN-00156: trace level number is greater than the maximum number. Using the
maximum value instead.
Cause: The trace level specified is greater than the maximum supported.
Action: Specify a valid trace level.
CLSGN-00158: Initialization or shut down in progress.
Cause: GNS was unable to process a command because it is either starting up or
shutting down.
Action: If the server is starting up, try the command again in a few seconds. The
server is shutting down, try the command again after the server has restarted.
CLSGN-00161: Failed to set GNS trace level: string.
Cause: The call to set the trace level on the GNS server failed.
Action: Examine the accompanying error message for details.
CLSGN-00162: Name "string" and address "string" will not be advertised due to
configuration change.
Cause: When GNS attempted to advertise a name and address upon re-start, it failed
because the address can no longer be serviced. This can happen if the subnet used by
GNS was changed between the time that GNS was stopped and it was started.
Action: If this result was expected, the error can be ignored. Otherwise, the subnet
needs to be changed in OCR and GNS needs to be stopped and re-started.
CLSGN-00000 to CLSGN-32767 11-9
CLSGN-00163: connection with Cluster Synchronization Services failed. Error:

number.\n
Cause: GNS was unable to contact Cluster Synchronization Services in order to
retrieve the name of the cluster.
Action: This error is most probably caused by the Cluster Synchronization Services
daemon being down. If the daemon is running, contact Oracle Support Services and
provide them with the error code.
CLSGN-00164: Failed to retrieve cluster name: Error: number.
Cause: GNS was unable to get the name of the cluster from Cluster Synchronization
Services.
Action: This error is most probably caused by the Cluster Synchronization Services
daemon being down. If the daemon is running, contact Oracle Support Services and
provide them with the error code.
CLSGN-00165: Running as user "string" which is not privileged.
Cause: GNS is not running as a privileged user e.g. root.
Action: Start GNS as a privileged user.
CLSGN-00166: Creation of OCR key "string" failed.\n string
Cause: GNS was unable to create the specified OCR key.
Action: Examine the accompanying error for details about what occurred. This error
may be caused by mis-configuration.
CLSGN-00167: Operation is unsupported.
Cause: An operation was attempted which is not currently supported by GNS.
Action: Do not attempt the operation.
CLSGN-00168: Name advertisement or alias re-creation failed.
Cause: When GNS starts, it re-creates the advertisements and aliases that existed
when it was shut down. The attempt to re-create an advertisement or alias failed.
Action: This error should not occur in normal use. Contact Oracle Support Services.
CLSGN-00169: Spawn of thread "string" failed.
Cause: GNS was unable to spawn a thread. This may be due to low system resources.
Action: If the memory or processes in use on the system are too high, reduce one or
both and restart GNS. If this is not the case, contact Oracle Support Services.
CLSGN-00170: Thread "string" failed on startup.
Cause: A GNS thread failed when it tried to start.
Action: Examine the alert log and and trace file (if any) for details about the error.
CLSGN-00171: Invalid alias "string" specified for name "string"
Cause: The name of the alias to be advertised was not valid. The name must have no
domain or be qualified with the name of subdomain serviced by GNS.
Action: Specify an alias whose name is in the correct format.
CLSGN-00172: Domain given in alias "string" for name "string" does not match
GNS domain "string".
Cause: The domain specified for an alias does not match the domain serviced by GNS.
Action: Either specify the correct domain or do not specify a domain and GNS will
use its domain as the default.
CLSGN-00173: GNS has not been configured.
Cause: An operation on GNS failed because GNS has not configured.
Action: Configure GNS and retry the operation.
CLSGN-00174: Packet replay detected - dropping connection.
Cause: GNS received a duplicate packet from a client. The connection was dropped as
a consequence.
Action: Examine the trace file for details. It is possible that a malicious user is
attempting to send an invalid packet to GNS.
CLSGN-00175: Invalid packet received - dropping connection.
Cause: The packet was ignored by the server because it was invalid. This may be
caused by another process sending malformed packets. This error is usually
accompanied by another error which describes the exact error that occurred.
Action: Use system tools to determine if a non-GNS process is sending data to the
server.
CLSGN-00176: Packet security check failed.
Cause: The check of the security attributes of a packet failed.
Action: Check the trace file for details about the failure. It is possible that a malicious
user is attempting to send an invalid packet to GNS.
CLSGN-00177: Invalid packet type received.
Cause: GNS received a packet whose type is unknown.
Action: Check the trace file for details about the failure. It is possible that a malicious
user is attempting to send an invalid packet to GNS.
CLSGN-00178: Resolution of name "string" failed.
Cause: GNS failed to retrieve the address of the specified name.
Action: Check to make sure that an address for the name has been registered with
GNS. If it is configured, check to make sure that DNS has been properly configured.
CLSGN-00179: No forwarded query received from DNS for name in "string"
domain, check DNS configuration
Cause: A query was not forwarded from DNS to GNS for a name in the subdomain
that it services.
Action: Check the configuration of DNS. Make sure that it contains the required
forwarding directive contained in the following message.
CLSGN-00180: If BIND is being used and the zone is being forwarded, the entry
will likely look like the following:
Cause: This message is displayed when the GNS self-check fails.
Action: Ensure that the configuration of DNS has the entry listed in the message that
follows this one.
CLSGN-00182: string Unable to resolve self-check name.
Cause: This is an informational message which accompanies other messages
describing a self-check failure.
CLSGN-00000 to CLSGN-32767 11-11
Action: Examine the accompanying error messages for more information as to the
cause of the problem.
CLSGN-00183: Number of retries exceeded maximum: number.
Cause: An operation failed after the maximum number of retries.
Action: Examine the accompanying message(s) for the reasons to why this error
occurred.
CLSGN-00184: Operation has to be retried.
Cause: An operation failed because it could not be performed at this time and should
be tried again later`.
Action: Examine the accompanying message(s) for details about the operation that
was performed.
CLSGN-00185: Invalid argument.
Cause: An argument was passed to a function which was incorrect. In the case of a
string, for example, a string will be invalid if it is null or has a zero length.
Action: Supply a valid argument.
CLSGN-00186: Insufficient privileges.
Cause: The user attempted an operation for which he or she does not have sufficient
privileges.
Action: Either have the system administrator grant the needed privileges or re-try the
operation as a user which has the needed privileges.
CLSGN-00187: Listening address "string" is not on the public network.
Cause: The address specified as the address on which GNS is to listen is not on the
public network.
Action: Specify a different address which is on the public network.
CLSGN-00188: The value for parameter "string": number may only be from number
to number.
Cause: The value for a parameter is outside the range of permitted values.
Action: Specify a value within the range.
CLSGN-00190: No records found for "string".
Cause: No records could be found for the specified name in GNS.
Action: Specify a name which exists in GNS.
CLSGN-00191: No records registered.
Cause: A query was made for the names registered in GNS but none were found.
Action: Re-run the query after names have been advertised.
CLSGN-00192: string Open of OCR key "string" failed.\n string
Cause: GNS was unable to open the specified OCR key.
Action: Examine the accompanying error for details about what occurred.
CLSGN-00193: Deletion of OCR key "string" failed.\n string
Cause: GNS was unable to delete the specified OCR key.
Action: Examine the accompanying error for details about what occurred.
CLSGN-00194: Time needed for resolution of name "string": string ms exceeded

threshold of string ms
Cause: Name resolution took longer than the expected time.
Action: This may indicate a problem in the network or DNS configuration and should
be investigated by each administrator.
CLSGN-00197: Self-check failed due to failure in name resolution.
Cause: The self-check failed because it was not possible to resolve the self-check name
into the address used for reference.
Action: Examine the errors that follow the message for further information as to the
cause.
CLSGN-00201: first self-check name resolution failed.
Cause: GNS was unable to resolve the name that it uses for the self-check the first
time after it started.
Action: Examine the logs for more information about the error.
CLSGN-00202: first self-check failed.
Cause: GNS was unable run the self-check the first time after it started.
Action: Examine the logs for more information about the error.
CLSGN-00205: self-check failed while in "recovery" state.
Cause: The self-check had previously succeeded after a failure but has failed again.
Action: Examine the logs for more information about the failure.
CLSGN-00206: Creation of a network endpoint failed.
Cause: The creation of a listening endpoint failed.
Action: Examine the accompanying error stack for more information about the error.
CLSGN-00207: Creation of a network endpoint failed due to lack of permissions.
Cause: The creation of a listening endpoint failed because the server did not have the
needed permissions.
CLSGN-00208: Network endpoint "string" already in use.
Cause: The creation of an endpoint failed because another process is using it.
Action: If another GNS instance is running, this error is expected. Otherwise,
terminate the process using the address or start GNS on another node.
CLSGN-00209: Listen for DNS requests failed. IP address string port number is in
use.
Cause: Listening for requests from the DNS server(s) failed because another process is
using the address.
Action: If another GNS instance is running, this error is expected. Otherwise,
terminate the process using the address or start GNS on another node.
CLSGN-00210: failed to get value for OCR key "string".\n string
Cause: It was not possible to retrieve the specified value from OCR.
CLSGN-00000 to CLSGN-32767 11-13
CLSGN-00211: OCR batch operation failed.\n string

Cause: Setting a set of OCR key values failed.
CLSGN-00215: no service specified
Cause: The service was required in an SRV record, bug not specified.
Action: Specify a the service.
CLSGN-00216: invalid SRV service: "string"
Cause: The service specified was not valid.
Action: Specify a valid service.
CLSGN-00217: no target specified in SRV record
Cause: The target was required in an SRV record, but not specified.
Action: Specify a target for the SRV record.
CLSGN-00218: invalid SRV record target: "string"
Cause: The target in the SRV record specified was not a valid DNS name.
Action: Specify a valid SRV record target. It must be a valid DNS name.
CLSGN-00219: SRV record for service: "string" does not exist
Cause: An SRV record for the specified service did not exist.
Action: Specify a service which exists.
CLSGN-00220: SRV record for service "string" already exists
Cause: An SRV record for the specified service already existed.
Action: Specify a service which does not exist.
CLSGN-00221: invalid SRV record port number: number. Maximum port number is
number
Cause: The value specified for the port number of an SRV record was invalid.
Action: Specify a value which less than or equal to the maximum value.
CLSGN-00222: invalid SRV record priority: number. Maximum priority is number
Cause: The value specified for the priority of an SRV record was invalid.
CLSGN-00223: invalid SRV record weight: number. Maximum weight is number
Cause: The value specified for the weight of an SRV record was invalid.
CLSGN-00224: No SRV record name specified
Cause: The name of the SRV record was not specified.
Action: Specify a name.
CLSGN-00225: Invalid SRV record name: "string"
Cause: The name specified for the SRV record was not a valid DNS name.
Action: Specify a valid DNS name. See RFC 1034 for details.
CLSGN-00226: Invalid SRV record protocol: "string"

Cause: The protocol specified for the SRV record was not valid.
Action: Specify a valid protocol or nothing to get the default.
CLSGN-00229: No SRV record protocol specified
Cause: The protocol for the SRV record was not specified.
Action: Specify a protocol.
CLSGN-00234: No PTR records found for "string"
Cause: No PTR records could be found for the specified name.
Action: Either add PTR records for the name or specify another name.
CLSGN-00235: PTR record already exists for "string"
Cause: An attempt was made to add a PTR record which already exists.
Action: Specify a PTR record which does not exist.
CLSGN-00236: TXT record already exists for "string"
Cause: An attempt was made to add a TXT record which already exists.
Action: Specify a TXT record which does not exist.
CLSGN-00237: No TXT records found for "string"
Cause: No TXT records could be found for the specified name.
Action: Either add TXT records for the name or specify another name.
CLSGN-00238: Length of TXT record (string bytes) exceeds maximum length
(number)
Cause: The TXT record was longer than the maximum.
Action: Specify a shorter record.
CLSGN-00239: Invalid TXT record
Cause: The TXT record specified does not conform with the standard (RFC 1035).
Action: Specify a record which conforms with the standard.
CLSGN-00240: Invalid PTR record: "string"
Cause: The PTR record specified does not conform with the standard (RFC 1035).
Action: Specify a record which conforms with the standard.
CLSGN-00243: Length of name "string" (number) exceeds maximum allowed number
Cause: The length of a name specified exceeds the allowed limit.
Action: Specify a shorter name.
CLSGN-00244: Length of qualfied name "string.string" (number) exceeds maximum
allowed number
Cause: The length of a name plus the GNS subdomain specified exceeded the allowed
limit.
Action: Specify a shorter name.
CLSGN-00246: No name specified for a PTR record.
Cause: A name was not specified for a Pointer Resource (PTR) record.
CLSGN-00000 to CLSGN-32767 11-15
Action: Specify a name which complies with the syntax described in RFC 1034 issued
by the Internet Engineering Task Force (www.ietf.org).
CLSGN-00247: No target specified for a PTR record.
Cause: A name was not specified as the target of the Pointer Resource (PTR) record.
CLSGN-00248: No name specified for TXT record.
Cause: A name was not specified for a text (TXT) record.
CLSGN-00249: No value specified for a TXT record.
Cause: A value was not specified for a text (TXT) record.
Action: The value of a TXT record is a set of keyword and value pairs separated by
commas. The values must comply with the syntax described in RFC 1464 issued by
the Internet Engineering Task Force (www.ietf.org).
CLSGN-00250: No name specified for refresh.
Cause: A name was not specified for a refresh operation.
by the Internet Engineering Task Force (www.ietf.org). The name must correspond to
a record which exists in Grid Naming Service (GNS).
CLSGN-00251: GNS attempt to re-bind listening endpoints failed.
Cause: GNS rebind failed.
Action: Examine the accompanying error messages for details about the error.
CLSGN-00253: Invalid key
Cause: A key supplied for an operation is invalid.
Action: Supply a valid key.
CLSGN-00254: Open of credentials file "string" failed.
Cause: Opening the specified credentials file failed.
Action: Specify a file which exists and has the proper permissions. The file must be
readable by the user performing the operation.
CLSGN-00255: Credentials file "string" does not exist.
Cause: The credentials file specifed could not be found.
Action: Specify a file that exists.
CLSGN-00256: Initialization of credentials import failed.
Cause: The steps required to initialize the import of credentials failed.
Action: Examine the accompanying errors for details about the failure.
CLSGN-00257: Credentials file "string" already exists.
Cause: The credentials file specified already exists.
Action: Specify a file that does not exist.
CLSGN-00258: Credentials file "string" could not be created.

Cause: The credentials file specified could not be created.
Action: Specify a file which does not exist or is writable to the user performing the
export.
CLSGN-00259: Initialization of credentials export failed.
Cause: The steps required to initialize the export of credentials failed.
Action: Examine the accompanying errors for details about the failure.
CLSGN-00260: Credential verification failed.
Cause: GNS was unable to verify the contents of a credentials file.
Action: Examine the accompanying errors for the cause.
CLSGN-00261: Import of credentials failed.
Cause: An error occurred while importing credentials used to contact the GNS server.
Action: Examine the accompanying errors for more information.
CLSGN-00262: Export of credentials failed.
Cause: An error occurred while exporting credentials used to contact the GNS server.
CLSGN-00263: Length of service instance "string": string exceeds maximum:
number.
Cause: The length of the specified service instance exceeded the maximum allowed.
Action: Specify a shorter service instance.
CLSGN-00264: Invalid service instance: "string".
Cause: The service instance contained characters which are not allowed under the
draft standard for DNS-based service discovery (see http://files.dns-sd.org/draftcheshire-dnsext-dns-sd.txt)
Action: Specify a service instance which complies with the standard.
CLSGN-00265: The number of discovery addresses found exceeds the maximum of
two.
Cause: More than two discovery addresses were found in the cluster configuration.
Action: Use 'srvctl modify gns' to correct the discovery addresses. If this does not
resolve the problem, contact Oracle Support Services.
CLSGN-00266: Both of the discovery addresses are of the same type.
Cause: The Grid Naming Service (GNS) configuration was found to have two IPv4 or
two IPv6 discovery addresses.
CLSGN-00267: Discovery address "string" is invalid.
Cause: The configuration was found to have an IP address that is in not in the IPV4 or
IPV6 format.
CLSGN-00000 to CLSGN-32767 11-17
CLSGN-00268: Initialization of GPnP failed.

Cause: An attempt to initialize Grid Plug and Play (GPnP) while modifying the Grid
Naming Service (GNS) configuration failed.
CLSGN-00269: Failed to get GPnP profile or profile value.
Cause: An attempt to access the Grid Plug and Play (GPnP) profile or a value within
the profile failed while modifying Grid Naming Service (GNS) configuration.
CLSGN-00270: Failed to set discovery address.
Cause: An attempt to modify Grid Naming Service (GNS) discovery address failed.
CLSGN-00272: Thread has been stopped.
Cause: This error is used internally by GNS to indicate that a thread has been
stopped.
CLSGN-00500: credentials extraction failed
Cause: The attempt to validate the provided Grid Naming Service (GNS) credentials
failed.
CLSGN-00501: credentials initialization failed
Cause: Initialization of the subsystem used for credentials validation failed.
Action: Generally, this error should not be visible. If it occurs, contact Oracle Support
Services.
CLSGN-00502: CRS initialization failed: string
Cause: Grid Naming Service (GNS) was unable to initialize Cluster Ready Services
(CRS) for its use.
Action: Examine the accompanying errors for more information about the error.
CLSGN-00503: CRS operation "string" failed with error: number
Cause: A Cluster Ready Services (CRS) operation failed.
CLSGN-00504: unsupported version: string
Cause: The version of an object or operation was not supported by Grid Naming
Service (GNS).
CLSGN-00508: OCR is not available
Cause: The Oracle Cluster Registry (OCR) was not available yet for use by Grid
Naming Service (GNS).
CLSGN-00509: Import of GNS key failed.
Cause: An error occurred while importing GNS key.
Action: Examine the accompanying error messages.
CLSGN-00510: CRS is not running

Cause: An operation which attempted to access the Oracle Cluster Registry failed
because the Cluster Ready Services (CRS) was not running.
Action: Run the 'crsctl check crs' command to determine if CRS is running. If it is
running, contact Oracle Support Services. Otherwise, restart CRS.
CLSGN-00511: GNS client cluster data already exists.
Cause: An attempt to import client data failed because client data has already been
imported.
Action: Use 'srvctl modify gns -clientdata' to modify existing client data.
CLSGN-00512: Unsupported record type: string
Cause: The record type specified was unsupported.
Action: Specify a supported record type.
CLSGN-00513: Empty or corrupt import file: string
Cause: Credential import failed because the import file was empty or corrupt.
Action: Specify a valid import file and try again.
CLSGN-00514: Removal of GNS credentials failed.
Cause: An error occurred while removing the GNS credentials from client cluster.
Action: Examine the accompanying error messages.
CLSGN-00515: string failed to set the ownership for OCR key "string".\n string
Cause: GNS was unable to set the ownership for OCR key.
Action: Examine the accompanying error message for details about what occurred.
CLSGN-00516: Import file "string" is not a valid file.
Cause: Operation failed because the import file is not a valid file.
Action: Specify a valid file and retry.
CLSGN-00517: length of component "string": string exceeds the maximum: number
Cause: The length of a component of a name exceeded the maximum allowed.
Action: Specify a shorter component.
CLSGN-00518: Thread group "string" failed to stop.
Cause: A group of threads belonging to the Grid Naming Service (GNS) process failed
to stop. This can happen if one or more threads in the group becomes unresponsive
because of a system problem.
Action: This error can be ignored if the GNS process stops despite this error. If the
GNS process does not stop, contact Oracle Support Services.
CLSGN-00519: Thread "string" failed to stop.
Cause: A thread belonging to the Grid Naming Service (GNS) process failed to stop.
This can happen if the thread becomes unresponsive because of a system problem.
Action: This error can be ignored if the GNS process stops despite this error. If the
GNS process does not stop, contact Oracle Support Services.
CLSGN-00520: invalid PTR target: "string"
Cause: An invalid string was specified for the target of a PTR record. The target must
be a valid DNS name.
CLSGN-00000 to CLSGN-32767 11-19
Action: Specify a target which complies with the syntax described in RFC 1034 issued
by the Internet Engineering Task Force (www.ietf.org). The target must correspond to
a record which exists in Grid Naming Service (GNS).
CLSGN-00521: No port available.
Cause: The Grid Naming Service (GNS) was unable to find a port to listen on.
Action: This error should not generally occur. Contact Oracle Support Services.
CLSGN-32767: Internal error
Cause: An unexpected error occurred.
Action: Examine the message(s) that accompany this one for details about the error
and contact Oracle Support Services.
12
CLSMDNS-00000 to CLSMDNS-02255
CLSMDNS-00000: no error
Cause: A command completely successfully.
Action: No action is needed.
CLSMDNS-00001: GIPC endpoint creation failed.
Cause: An attempt to create a GIPC endpoint for use multicast operations failed.
Action: Examine the accompanying error (if any) and the log file for details as to why
the operation failed.
CLSMDNS-00002: bind failed.
Cause: An attempt to bind an address to a GIPC endpoint failed.
CLSMDNS-00003: address creation failed.
Cause: An attempt to create a GIPC address failed.
CLSMDNS-00004: attribute setting failed.
Cause: An attempt to set an attribute on a GIPC endpoint or address failed.
CLSMDNS-00005: interface registration failed.
Cause: The registration of an interface with mDNS failed.
CLSMDNS-00006: failed to get name server list.
Cause: An attempt to get the list of available name servers failed.
CLSMDNS-00007: mDNS initialization failed.
Cause: The initialization of the mDNS subsystem failed.
CLSMDNS-00000 to CLSMDNS-02255 12-1
CLSMDNS-00008: start of host query failed.

Cause: The query for hosts from mDNS failed to start.
CLSMDNS-00009: stop of host query failed.
Cause: Termination of the query for hosts from mDNS failed.
CLSMDNS-00010: Initialization of name server name retrieval failed.
Cause: The initialization of the retrieval of the names of the name servers used by
multicast DNS failed.
Action: Examine the accompanying messages(s) that detail the platform error(s) for
details about the exception.
CLSMDNS-00011: retrieval of name server name failed.
Cause: The retrieval of the name of a name server to be used by multicast DNS failed.
Action: Examine the accompanying messages(s) that detail the platform error(s) for
details about the exception.
CLSMDNS-00012: no name servers found.
Cause: No name servers were found that could be used by multicast DNS.
Action: Check the system configuration and ensure that or more DNS name servers
are configured, operating and accessible.
CLSMDNS-00013: Send of response to DNS server failed.
Cause: An attempt to send a response to a query from the DNS server failed.
Action: Examine accompanying exceptions for details about the exact error.
CLSMDNS-00015: invalid record type: number
Cause: The DNS server sent a record whose type is unknown.
Action: This is a warning message which can be ignored because the error should
occur very infrequently. If the error occurs frequently, Oracle Customer Support
should be contacted.
CLSMDNS-02000: unknown error.
Cause: An unknown error occurred. This error can occur when the multicast DNS
server is not running.
Action: If the multicast server is not running, start it and try the operation again. If it
is running, this is an internal error and Oracle Customer Support should be contacted
with details about how and when the error occurred.
CLSMDNS-02001: no such name exists.
Cause: This error is internal and should not ordinarily be seen by the user.
CLSMDNS-02002: memory allocation failure.
Cause: The allocation of process memory failed.
12-2 Error Messages
CLSMDNS-02003: invalid parameter.
CLSMDNS-02004: invalid reference.
CLSMDNS-02005: invalid state.
CLSMDNS-02006: invalid flags.
CLSMDNS-02007: operation is unsupported.
CLSMDNS-02008: uninitialized.
CLSMDNS-02009: no cache.
CLSMDNS-02010: record or service is already registered.
CLSMDNS-02011: name conflict found.
CLSMDNS-02012: Invalid.
CLSMDNS-02013: Firewall.
CLSMDNS-02014: Incompatible.
CLSMDNS-02015: invalid interface.

CLSMDNS-02016: Refused.
CLSMDNS-02017: no such record.
CLSMDNS-02018: no authentication.
CLSMDNS-02019: no such key.
CLSMDNS-02020: error occurred while passing through NAT.
CLSMDNS-02021: double NAT encountered.
CLSMDNS-02022: invalid time.
CLSMDNS-02023: invalid signature.
CLSMDNS-02024: invalid key.
CLSMDNS-02025: transient error.
CLSMDNS-02250: connection pending.
CLSMDNS-02251: connection failed.
12-4 Error Messages

CLSMDNS-02252: connection established.
CLSMDNS-02253: more memory needed for cache.
CLSMDNS-02254: configuration changed.
CLSMDNS-02255: memory free needed.
12-6 Error Messages
13
CLSNS-00000 to CLSNS-00035
CLSNS-00000: no error
CLSNS-00001: unspecified error
Cause: An unknown error occurred. This is an internal error.
Action: Contact Oracle Customer Support and provide details about how and when
the error occurred.
CLSNS-00002: memory allocation of number bytes failed
Cause: An operation failed because it was not possible to allocate enough process
memory.
CLSNS-00003: string buffer too small. required: number provided: number
the error occurred.
CLSNS-00004: length of value "string": number exceeds maximum: number
Cause: The value specified exceeds the maximum allowed.
Action: Specify a shorter value. This error can occur when creating a TXT record. If it
occurs in another context, it is an internal error. In that case, contact Oracle Customer
Support and provide details about how and when the error occurred
CLSNS-00005: operation timed out
Cause: A name resolution operation took too long to complete.
Action: This can happen on a heavily loaded system, for example. Retry the operation
a few more times. If it still does not succeed, contact Oracle Customer Support and
provide details about how and when the error occurred.
CLSNS-00006: duplicate object
the error occurred.
CLSNS-00007: object not found
CLSNS-00000 to CLSNS-00035 13-1
the error occurred.
CLSNS-00008: invalid argument: string
the error occurred.
CLSNS-00009: invalid context
the error occurred.
CLSNS-00010: invalid DNS message received
the error occurred.
CLSNS-00011: corrupt list
the error occurred.
CLSNS-00012: corrupt record
the error occurred.
CLSNS-00013: invalid property
the error occurred.
CLSNS-00014: invalid operation code
the error occurred.
CLSNS-00015: invalid record type: number
the error occurred.
CLSNS-00016: invalid flag
the error occurred.
CLSNS-00017: invalid status
the error occurred.
13-2 Error Messages
CLSNS-00018: invalid section: number

the error occurred.
CLSNS-00019: communications failure
Cause: It was not possible to contact a naming service.
Action: Examine the accompanying errors to determine what the cause may be.
CLSNS-00020: DNS configuration retrieval failed
Cause: Retrieval of configuration information failed.
Action: Examine any accompanying errors and logs for more information.
CLSNS-00021: permission denied
Cause: An operation failed because the user did not have the necessary permissions.
CLSNS-00022: credential retrieval failure
Cause: An operation failed because the user did not have the necessary credentials.
CLSNS-00023: connection to GNS failed
Cause: The connection to the GNS server failed.
Action: Examine the accompanying errors for more information about the error.
CLSNS-00024: unable to initialize GNS
Cause: It was not possible to initialize the GNS server for the cluster.
Action: Determine if GNS is running. If it is not, ask the administrator to start it. If
GNS is running, it is an error and Oracle Customer Support should be contacted with
the details of the error.
CLSNS-00025: unable to locate GNS
Cause: It was not possible to locate the GNS server for the cluster.
Action: Determine if GNS is running. If it is not, ask the administrator to start it. If
GNS is running, it is an error and Oracle Customer Support should be contacted with
the details of the error.
CLSNS-00026: failed to resolve name with GNS
Cause: It was not possible to resolve a name with GNS.
Action: Examine the accompanying errors for details. If the name is indeed advertised
with GNS, please contact Oracle Customer Support.
CLSNS-00027: operation is unsupported
Cause: The specified operation is not supported.
Action: This is an internally-visible error and should not ordinarily be seen by users.
Contact Oracle Customer Support and provide details about how and when the error
occurred.
CLSNS-00028: no space for record in message
Cause: Not enough space exists in a DNS message for a record.
CLSNS-00000 to CLSNS-00035 13-3
Action: This is an internally-visible error and should not ordinarily be seen by users.
Contact Oracle Customer Support and provide details about how and when the error
occurred.
CLSNS-00029: advertisement of name "string" failed
Cause: Advertisement of the records attached to specified name failed.
Action: Examine the accompanying error messages for more information.
CLSNS-00030: deletion of name "string" failed
Cause: Deletion of the records attached to the pecified name failed.
CLSNS-00031: refresh of name "string" failed
Cause: Refresh of the records attached to the specified name failed.
CLSNS-00032: retrieval of GPnP profile failed
Cause: The retrieval of the Grid Plug and Play profile failed.
Action: See the accompanying error messages for more information.
CLSNS-00033: initialization of GPnP failed
Cause: The initialization of Grid Plug and Play failed.
CLSNS-00034: number of retries exceeeded maximum: number
Cause: The retries allotted for an operation exceeded the maximum.
Action: Check to see if the name service being used is functioning correctly.
CLSNS-00035: Invalid IP address: string
Cause: GNS discovery address was not in IPv4 nor IPv6 format.
Action: Specify an address using IPv4 or IPv6 format.
13-4 Error Messages
14
CLSR-00001 to CLSR-06507
CLSR-00001: Oracle error number encountered
Cause: Oracle-related error is encountered.
Action: Check alert log and trace file for more detail.
CLSR-00002: Oracle error encountered while executing string
Cause: Oracle-related error is encountered while executing a request.
Action: Check alert log for more detail.
CLSR-00003: ORACLE_HOME environment variable not set
Cause: ORACLE_HOME environment variable is not set.
Action: Make sure that the ORACLE_HOME environment variable has been properly
set and exported.
CLSR-00004: Error encountered at string, category=number, operation=string, OS
error=number
Cause: Operating system error occurred.
Action: Check for the error message for more detail.
CLSR-00005: Error encountered during memory allocation
Cause: System memory is insufficient.
Action: Check the availability of memory in the system before retrying.
CLSR-00006: Error encountered when writing file string
Cause: Error when writing file.
Action: Check the permission of the file and the existence of its path.
CLSR-00007: Error encountered when reading file string
Cause: Error when reading file.
Action: Check the permission and existence of the file.
CLSR-00501: Error number encountered when connecting to EVM daemon
Cause: Error encountered when connecting to EVM daemon.
Action: Check status of EVM daemon and log file for detail.
CLSR-00502: Error number encountered when subscribing an EVM event
Cause: Error encountered when subscribing an EVM event.
Action: Contact customer support.
CLSR-00503: Error number encountered when creating an EVM event
Cause: Error encountered when creating an EVM event.
CLSR-00001 to CLSR-06507 14-1

CLSR-00504: Error number encountered when posting an EVM event
Cause: Error encountered when posting an EVM event.
CLSR-00505: Empty event type is specified
Cause: Empty event type is specified.
Action: Try again with a valid event type.
CLSR-00506: Unmatched resource name prefix string is specified
Cause: Specified resource name prefix does not match as required.
Action: Try again with a valid resource name prefix.
CLSR-00507: The length of the facility name string exceeds the limit (number)
Cause: The given facility name is too long.
Action: Try again with a short facility name.
CLSR-00508: Invalid message number number
Cause: An incorrect message number is specified.
Action: Try again with a correct message number.
CLSR-00509: Unable to initialize NLS
Cause: Failed to initialize callback structure for NLS.
CLSR-00510: Unable to load NLS data
Cause: Failed to initialize NLS data loading.
Action: Not action required as default data loading will be used.
CLSR-00511: Error number encountered when handling incoming EVM message
Cause: Error encountered when handling incoming EVM message.
Action: Check log file for detail.
CLSR-00512: Invalid CAA trigger event type [string]
Cause: Invalid CAA trigger event type is specified.
Action: Try again with a valid type.
CLSR-00513: Message file is not found
Cause: The requested OCI message file is not found.
Action: Check if the message file is properly installed.
CLSR-00514: Unable to locate PMON [pid=string]
Cause: Cannot find PMON with this pid.
Action: Check the existence of PMON.
CLSR-00515: A service member is already running on this node
Cause: There is a service member of the same service running on this node.
Action: No action required as the service member will try to start on another node.
14-2 Error Messages
CLSR-00516: No service provider found at this node

Cause: No suitable service provider is found on this node.
Action: No action required as the service member will try to start on another node.
CLSR-00517: Failed to register a service name
Cause: The requested service name cannot be registered.
CLSR-00518: Failed to register a preconnect service name
Cause: The requested preconnect service name cannot be registered.
CLSR-00519: No instance found
Cause: No instance is found running for the database resource.
Action: No action required as the database resource will fail itself.
CLSR-00520: No service member found
Cause: No service member is found running for the composite service resource.
Action: No action required as the composite service resource will fail itself.
CLSR-00521: Event string is rejected by EVM daemon
Cause: No template has been registered for the event or caller is not authorized to
post the event.
Action: Check if there is a template registered for this event and the authority of
posting this event.
CLSR-00522: Resource string is not registered
Cause: CRS resource is not registered.
Action: Register the CRS resource.
CLSR-00523: Resource string is not enabled
Cause: CRS resource is not enabled.
Action: Enable the CRS resource.
CLSR-00524: Resource string is stopping, resource string cannot start
Cause: Resource cannot start because its composite resource is stopping.
Action: Retry to start the resource when its composite resource is not stopping.
CLSR-00525: prsr initialization failed
Cause: See the related error message.
Action: Run crs_stat to make sure CSS and OCR working properly.
CLSR-00526: Failed to retrieve database configuration in OCR
Cause: See the related error message.
Action: Run crs_stat to make sure CSS and OCR working properly and database
configuration in ocr is initialized.
CLSR-00527: OCR operation failed
Cause: See related error messages about the OCR operation.
Action: Fix the related error. Then try again.
CLSR-00001 to CLSR-06507 14-3
CLSR-00528: RACGONS: host and port number already configured in OCR

Cause: host and port number already configured in OCR.
Action: None
CLSR-00529: RACGONS: host and port number to be removed does not exist
Cause: host and port number to be removed is not configured in OCR.
Action: None
CLSR-00530: Can not get user name
Cause: Error caused by OSD layer.
Action: Contact Oracle support.
CLSR-00531: Can not get primary group name
Cause: There is no primary group for this OS.
Action: Not faital. None.
CLSR-01001: Unsupported open mode number is specified
Cause: Unsupported open mode is specified for mounting database.
Action: Retry again with a valid open mode.
CLSR-01002: Unable to process instance startup
Cause: ORACLE_HOME environment variable not set.
set and exported.
CLSR-01003: Error number encountered during mounting database
Cause: Unexpected error occurs when mounting database.
Action: Check current status of database before retrying.
CLSR-01004: Failed to mount database
Cause: Database cannot be mounted by an instance.
Action: Check alert log for error detail.
CLSR-01005: Error number encountered during altering database open mode
Cause: Unexpected error occurs when altering database open mode.
Action: Check current database status.
CLSR-01006: Unable to process instance shutdown
set and exported.
CLSR-01007: Connection to database was not established
Cause: Connection to database is failed to establish.
Action: Make sure connection and environment are properly set up.
CLSR-01008: Error number encountered during querying for PMON status
Cause: Unexpected error encountered when querying v$process for PMON.
Action: Check alert log and connection to database.
14-4 Error Messages
CLSR-01009: database management module failed to start

Cause: Error encountered during initializing database management module.
Action: Check previous error message for detail.
CLSR-01010: Unable to record PMON pid to string
Cause: Failed to write os pid for PMON to file.
Action: Check file system for disk space and access privilege.
CLSR-01011: Invalid instance startup mode [string] is specified
Cause: Invalid startup mode is specified.
Action: Retry again with a valid startup mode.
CLSR-01012: Invalid instance stop mode [string] is specified
Cause: Invalid stop mode is specified.
Action: Retry again with a vaild stop mode.
CLSR-06500: Invalid input arguments
Cause: Invalid input arguments are specified.
Action: Retry again with a valid argument.
CLSR-06501: Exceeds maximum number of arguments
Cause: Too many input arguments are specified.
Action: Retry again with correct number of arguments.
CLSR-06502: Failed to connect to database 'string' as user 'string'
Cause: Failed to connect to database.
Action: Check database and log file for details.
CLSR-06503: Service name already registered
Cause: Requested service name has been registered by another service.
Action: Choose another service name and retry registration again.
CLSR-06504: Service name not in SERVICE_NAMES
Cause: Requested service name is not registered.
Action: Make sure the correct service name is specified in the request.
CLSR-06505: SERVICE_NAMES found null and fixed
Cause: SERVICE_NAMES parameter becomes null after the delete operation.
Action: Not action required as SERVICE_NAMES is set to default value.
CLSR-06506: Error number encountered when executing string
Cause: Error occurred when executing the SQL statement.
Action: Check alert log for more detail.
CLSR-06507: Cannot add to SERVICE_NAMES, SERVICE_NAMES will be too
long
Cause: Adding the service name will exceed the limit of SERVICE_NAMES.
Action: Change the configuration to avoid SERVICE_NAMES becomes too long.
CLSR-00001 to CLSR-06507 14-5
14-6 Error Messages
15
CLSRSC-00001 to CLSRSC-04015
CLSRSC-00001: Insufficient privileges to execute this script
Cause: The script was invoked by a non-root or a non-administrator user.
Action: Run the script as the root or administrative user.
CLSRSC-00003: No value set for the required parameter 'string'
Cause: The required parameter file is missing, or no value is set for the parameter yet.
Action: Use the correct parameter file and provide each paramter with a valid value.
CLSRSC-00004: No value passed as Oracle CRS home
Cause: No value was passed as Oracle CRS home.
Action: None
CLSRSC-00005: The Oracle CRS home 'string' does not exist
Cause: The Oracle CRS home does not exist.
Action: Make sure that the Oracle Grid Infrastructure software is properly installed.
CLSRSC-00006: No value passed as Oracle Clusterware name
Cause: No value was passed as Oracle Clusterware name.
Action: None
CLSRSC-00007: The OCR location file '/etc/oracle/ocr.loc' is corrupted
Cause: The OCR location file '/etc/oracle/ocr.loc' is corrupted.
Action: Make sure that the '/etc/oracle' directory is empty if this is a fresh install.
CLSRSC-00008: No value passed as OCR locations
Cause: No value was passed as OCR locations.
Action: None
CLSRSC-00009: No value passed as OLR locations
Cause: No value was passed as OLR locations.
Action: None
CLSRSC-00010: The VIP resource was not created due to VIP address not available.
Cause: There was an error in obtaining a VIP address from the DHCP server.
Action: Run the command 'cluvfy comp dhcp' to check the DHCP server.
CLSRSC-00011: No value passed for OLR locations
Cause: No value was passed as OLR locations.
Action: None
CLSRSC-00001 to CLSRSC-04015 15-1
CLSRSC-00012: The ASM resource ora.asm did not start

Cause: There was an error in starting the ASM resource.
Action: Check the accompanying messages and contact Oracle Support Services.
CLSRSC-00013: The file 'string' does not exist
Cause: The specified file does not exist.
Action: None
CLSRSC-00014: CSS is configured for single instance Oracle databases
Cause: The current configuraiton is for previous installation.
Action: Delete this configuration using the command 'localconfig delete' before
proceeding with Oracle RAC configuration.
CLSRSC-00015: No value passed for host name
Cause: No value was passed as the host name.
Action: None
CLSRSC-00016: No value passed for Oracle CRS user
Cause: No value was passed as Oracle crs user.
Action: None
CLSRSC-00017: Invalid GPnP setup
Cause: GPnP directories do not exist.
Action: Make sure that GPnP directories must exist.
CLSRSC-00018: The GPnP peer wallet file 'string' does not exist or is not readable
Cause: The GPnP peer wallet file does not exist or is not readable.
Action: None
CLSRSC-00019: 9i GSD is running on the Cluster nodes (string)
Cause: 9i GSD is running on the Cluster nodes.
Action: Stop the GSD and re-run 'root.sh' on UNIX platforms or 'gridconfig.bat' on
Windows.
CLSRSC-00020: Invalid network type in the network specification string 'string'.
Only 'public' and 'cluster_interconnect' are allowed
Action: If the problem persists, contact Oracle Support Services.
CLSRSC-00021: No value passed for the directory name
CLSRSC-00022: The directory 'string' does not exist
Cause: The specified directory does not exist.
CLSRSC-00023: No value passed for the file name
15-2 Error Messages
CLSRSC-00024: No value passed for the host name.

CLSRSC-00025: Unable to find the command 'string' to stop Clusterware
Cause: Cannot stop Clusterware because the required executable file does not exist.
CLSRSC-00026: The file system of 'string' is invalid
Cause: The root is not able to perform any operations on this file system.
Action: Check export options on NAS filer and make sure that the file system is not
corrupted.
CLSRSC-00027: The GPnP configuration reader wallet in given directory 'string' is
missing
Cause: The setup in GPnP configuration directory is incomplete.
CLSRSC-00028: The GPnP configuration reader wallet in given directory 'string' is
invalid
Cause: The setup in GPnP configuration directory is invalid.
CLSRSC-00029: Invalid GPnP configuration directories. The cluster-wide 'string'
and node-specific 'string' must be different
Cause: Invalid configuration was found while verifying the GPnP local and clusterwide setup.
Action: None
CLSRSC-00030: No parameters specified to query from GPnP profile 'string'
Cause: The required parameters were not supplied while querying from GPnP
profile.
Action: None
CLSRSC-00031: GPnP profile signature verification failed
Cause: The signature status string was not found in the output of 'gpnptool'
execution.
Action: If error persists, contact Oracle Support Services.
CLSRSC-00032: The 'string' file is not readable
Cause: No read access to the specified file.
Action: Check the permissons on this file and make sure it is readable.
CLSRSC-00033: The OLR from version 'string' is missing or unusable for upgrade
Cause: Invalid OLR file was found during upgrade.
CLSRSC-00034: IPv6 is currently not supported
Cause: Attempt was made to use IPv6.
Action: None
CLSRSC-00035: The value set for the parameter 'CRS_NODEVIPS' is null

Cause: No value set for the parameter 'CRS_NODEVIPS'.
Action: Set 'CRS_NODEVIPS' parameter in 'crsconfig_params' and re-run
'rootupgrade.sh'. The format is as follows: CRS_NODEVIPS='node1-vip/node1netmask/node1-interface,node2-vip/node2-netmask/node2-interface'.
CLSRSC-00036: The file 'string' does not exist to proceed with deconfiguration
Cause: Some files are missing in the Grid Infrastructure Home.
CLSRSC-00037: Run the deconfiguration script with a -force option.
Cause: The deconfiguration failed due to a missing file.
Action: Perform the deconfiguration using the -force option and manually stop any
processes running from the GI home.
CLSRSC-00038: Oracle Clusterware stack is not active on this node
Cause: Oracle Clusterware is not running on this node.
Action: Restart the Clusterware stack using 'crsctl start crs' and retry.
CLSRSC-00039: Oracle Restart stack is not active on this node
Cause: Oracle SIHA stack is not running on this node.
Action: Restart the SIHA stack using 'crsctl start has' and retry.
CLSRSC-00040: No value passed for owner name
CLSRSC-00041: No value passed for group name
CLSRSC-00042: No value passed for the file or directory name
CLSRSC-00043: No value passed for permissions
CLSRSC-00044: The init script file name passed is null
CLSRSC-00045: The init script file 'string' does not exist
CLSRSC-00046: Error: 'string' does not exist
Cause: The specified file or directory does not exist.
Action: None
15-4 Error Messages
CLSRSC-00101: Could not copy OCR locations

CLSRSC-00102: Could not delete the OLR file 'string' (error: string)
CLSRSC-00103: An error occured while accessing the file 'string'
Cause: The specified file does not exist or is not readable.
Action: Make sure the file exists and it has read and execute access.
CLSRSC-00104: Could not execute 'string -g' and read output (error: string)
Cause: Unable to execute the specified command.
CLSRSC-00105: Failed to copy 'string' to 'string' (error: string)
Cause: An error occurred while copying the specified file.
CLSRSC-00106: Copy of older local-only OCR failed
Cause: An error occurred while copying over older local-only OCR to SIHA home.
Action: None
CLSRSC-00107: Start of GNS failed
Cause: This is a status message.
Action: None
CLSRSC-00108: Failed to start VIP on node 'string'
Action: None
CLSRSC-00109: Start of ASM diskgroup failed
Action: None
CLSRSC-00110: Failed to start the specified SCAN VIP
Action: None
CLSRSC-00111: Failed to start the specified SCAN listener
Action: None
CLSRSC-00112: Start of the CVU resource failed
Action: None
CLSRSC-00113: Start of ASM instance failed
Action: None
CLSRSC-00114: Force stop of ASM instance failed
Action: None
CLSRSC-00115: Start of resource 'string' failed
Action: None
CLSRSC-00116: Stop of resource 'string' failed
Action: None
CLSRSC-00117: Failed to start Oracle Clusterware stack
Cause: An error occurred while starting Oracle Clusterware stack.
CLSRSC-00119: Start of the exclusive mode cluster failed
Action: If the problem persists, Contact Oracle Support Services
CLSRSC-00120: Timed out waiting for the CRS stack to start
Action: If the problem persists,contact Oracle Support Services.
CLSRSC-00121: Timed out waiting for the GPNPD to start
CLSRSC-00122: Failed to create a root wallet for Oracle Cluster GPnP (error code
string)
Action: Check accompanying messages and contact Oracle Support Services.
CLSRSC-00123: Failed to create a root certificate for Oracle Cluster GPnP (error
code string)
CLSRSC-00124: Failed to export root certificate for Oracle Cluster GPnP (error code
string)
CLSRSC-00125: Failed to create a peer wallet for Oracle Cluster GPnP (error code
string)
15-6 Error Messages
CLSRSC-00126: Failed to create a profile reader wallet for Oracle Cluster GPnP
(error code string)
CLSRSC-00127: Failed to create a provisioning authority wallet for Oracle Cluster
GPnP (error code string)
CLSRSC-00128: Failed to make a peer wallet for Oracle Cluster GPnP (error code
string). Could not add private key to a wallet
CLSRSC-00129: Failed to make a provisioning authority wallet for Oracle Cluster
GPnP (error code string). Could not add private key to a wallet.
string). Could not export a certificate request from a wallet.
GPnP (error code string). Could not export a certificate request from a wallet.
string). Could not create a peer certificate.
GPnP (error code string). Could not create a PA certificate.
string). Could not add a root TP certificate.
CLSRSC-00135: Failed to make a profile reader wallet for Oracle Cluster GPnP
(error code string). Could not add a root TP certificate.

GPnP (error code string). Could not add a root TP certificate.
string). Could not add a PA TP certificate.
Cause: Internal Error.
GPnP (error code string). Could not add a peer TP certificate.
(error code string). Could not add a PA TP certificate.
(error code string). Could not add a peer TP certificate.
string). Could not add a PA TP certificate.
GPnP (error code string). Could not add a peer TP certificate.
CLSRSC-00143: Failed to string a peer profile for Oracle Cluster GPnP using
'gpnptool' (error code string)
CLSRSC-00144: Failed to sign a peer profile for Oracle Cluster GPnP using
CLSRSC-00145: Failed to verify a peer profile 'string' with WRL='string' using
15-8 Error Messages
CLSRSC-00146: Failed to take cluster-wide GPnP setup as local

CLSRSC-00147: Failed to get parameter values from GPnP profile 'string'
CLSRSC-00148: Errors occurred while setting GPnP wallets ownership/permissions
Cause: Failed to set GPnP wallets ownership/permissions.
Action: None
CLSRSC-00149: Creation of Oracle GPnP wallets failed for host 'string'
Cause: Failed to create Oracle GPnP wallets for the specified host.
CLSRSC-00150: Creation of Oracle GPnP peer profile failed for host 'string'
Cause: Failed to create Oracle GPnP peer profile for the specified host.
CLSRSC-00151: Failed to promote local GPnP setup to other cluster nodes
CLSRSC-00152: Could not set ownership on 'string'
Cause: Failed to set ownership on the specified file or directory.
Action: None
CLSRSC-00153: Could not set permissions on 'string'
Cause: Failed to set permissions on the specified file or directory.
Action: None
CLSRSC-00154: Check of resource "string" failed
CLSRSC-00155: Replace of older local-only OCR failed
CLSRSC-00156: Error creating local-only OCR
CLSRSC-00157: Failed to create Oracle Cluster Registry configuration
CLSRSC-00158: Failed to reset the OCR location in 'srvconfig.loc' file

CLSRSC-00159: Failed to initialize Oracle Cluster Registry for cluster
CLSRSC-00160: Failed to create local-only OCR using the command 'string'
CLSRSC-00161: Pin node using the command 'string' failed
CLSRSC-00162: Upgrade of ASM Windows Service failed
CLSRSC-00163: ASM rolling upgrade action failed
CLSRSC-00164: ASM upgrade failed
CLSRSC-00165: Backup of file 'string' failed
Cause: The copy of the file to a backup file failed.
CLSRSC-00166: Failed to stop or deconfigure older version Cluster Support
Services daemon.
Cause: There was an error during the operation.
CLSRSC-00167: Restore of file 'string' failed
Cause: The copy of the file from a backup file failed.
CLSRSC-00168: Could not delete the file 'string' (error: string)
Cause: Unable to delete the specified file.
Action: None
CLSRSC-00169: Failed to create or upgrade OLR
Cause: The 'ocrconfig -local -upgrade' command failed.
CLSRSC-00170: Failed to deconfigure Oracle ASM (error code string)
CLSRSC-00171: Failed to get a list of CSS nodes from OCR

CLSRSC-00172: Failed to get a list of interfaces from OCR
CLSRSC-00173: Error: string \nError getting networks interface information using
'oifcfg'
CLSRSC-00174: Error: string \nAn error occurred while executing the command
'olsnodes'
CLSRSC-00175: Failed to write the checkpoint 'string' with status 'string' (error code
string)
CLSRSC-00176: Failed to write contents of pfile 'string' for checkpoint 'string' (error
code string)
CLSRSC-00177: Failed to add (property/value):('string'/'string') for checkpoint
'string' (error code string)
CLSRSC-00178: Failed to get property value for property 'string' for checkpoint
'string' (error code string)
CLSRSC-00179: Failed to get value of 'string' for checkpoint 'string' (error code
string)
CLSRSC-00180: An error occurred while executing the command 'string' (error code
string)
Cause: Failed to execute the specified command.
Action: Correct the problem indicated in the accompanying messages and retry.
CLSRSC-00181: Failed to find earlier version database home
CLSRSC-00182: Failed to add the resource for ASM diskgroup 'string'

Cause: An internal error occurred while creating the ASM diskgroup resource.
CLSRSC-00183: OCR manual backup operation failed (error code string)
CLSRSC-00184: Configuration of ASM failed
Cause: Errors occurred while configuring ASM via 'asmca'.
Action: See 'asmca' logs for details. If the problem persists, contact Oracle Support
Services.
CLSRSC-00185: Could not open file string (error: string)
Cause: An error occured while attempting to open a specified file.
CLSRSC-00186: Failed to copy file from local path 'string' to remote path 'string' for
given list of nodes 'string' (error code string)
CLSRSC-00187: Failure with signal 'string' from command 'string'
CLSRSC-00188: Failed to create keys in Oracle Local Registry
CLSRSC-00189: Failed to add type 'ora.registry.acfs.type'
CLSRSC-00190: Failed to add resource 'ora.registry.acfs'
CLSRSC-00191: Failed to stop Oracle Clusterware stack
Cause: An error occurred while stopping Oracle Clusterware stack.
CLSRSC-00192: Unable to stop Oracle Restart
CLSRSC-00193: Platform-specific setup failed
CLSRSC-00195: Failed to create OHASD resources for cluster and ASM

Cause: An error occurred while adding OHASD resource types and resources.
CLSRSC-00196: ACFS driver install actions failed
Cause: An error occurred while installing ACFS drivers using the 'acfsroot install'
command.
Action: Examine the accompanying messages from the 'acfsroot install' command,
correct the problem and retry.
CLSRSC-00197: Cluster configuration upgrade failed
CLSRSC-00198: Initial cluster configuration failed
CLSRSC-00199: Timed out waiting for OHASD to start
CLSRSC-00200: Failed to create HA resources for HAS daemon and ASM
CLSRSC-00201: Failed to start CSS daemon
CLSRSC-00202: Failed to start EVM daemon
CLSRSC-00203: Failed to stop resources from database home 'string'
CLSRSC-00204: Failed to downgrade OCR to version 'string'
CLSRSC-00205: Failed to uninstall ADVM/ACFS
CLSRSC-00206: Could not open file string for reading (error: string)
Cause: An error occurred while attempting to open a specified file for reading.
Action: Check that the file exists and has the proper permissions.
CLSRSC-00207: Could not open file string for writing (error: string)
Cause: An error occurred while attempting to open a specified file for writing.
CLSRSC-00208: Could not open file string for appending (error: string)
Cause: An error occurred while attempting to open a specified file for appending.
CLSRSC-00209: Could not move 'string' to 'string' (error: string)
Cause: An error occurred while moving the specified file.
CLSRSC-00210: Current Oracle Cluster Registry location 'string' in file 'string' and
file 'string' do not match
CLSRSC-00211: Current Oracle Cluster Registry mirror location 'string' in file
'string' and file 'string' do not match
CLSRSC-00212: Update either file 'string' to use location 'string' or variable
OCR_LOCATIONS property set in file 'string' with location 'string' then re-run this
script
CLSRSC-00213: Failure in reading file 'string' (error: string)
CLSRSC-00214: Failed to start the resource 'string'
CLSRSC-00215: Could not open file 'string' to read permisisons (error: string)
CLSRSC-00216: Insufficient free space available in Cluster Health Monitor
repository 'string'
Cause: The available space was less than the minimum space required (1024 MB).
Action: Run the command 'oclumon manage -repos reploc <new_path>' to change
Cluster Health Monitor repository and make sure its free space meets the minimum
requirement.
CLSRSC-00217: Could not open file 'string' to write permisisons (error: string)
CLSRSC-00218: Failed to install the OHASD startup script (error: string)

CLSRSC-00219: Unable to get Oracle owner for the home 'string'
CLSRSC-00220: Unable to retrieve database home information
CLSRSC-00221: The patch 'string' apply failed for home 'string'
CLSRSC-00222: The patch 'string' apply successful for home 'string'
Action: None
CLSRSC-00223: The patch 'string' rollback failed for home 'string'
CLSRSC-00224: The patch 'string' rollback successful for home 'string'
Action: None
CLSRSC-00225: The prepatch execution for database home failed
CLSRSC-00226: The postpatch execution for database home failed
CLSRSC-00227: Patch information file 'string' does not exist. Not a valid GI Bundle
patch.
CLSRSC-00228: Timed out waiting for server assignments
CLSRSC-00242: Failed to start Oracle Grid Plug and Play (GPnP) component
CLSRSC-00243: Failed to upgrade the voting disks for Cluster Synchronization

Service
CLSRSC-00244: Failed to start Cluster Synchronization Service in clustered mode
CLSRSC-00245: Failed to start Cluster Time Synchronization Service (CTSS)
CLSRSC-00246: HAIP startup failure considered fatal, terminating ...
CLSRSC-00247: Failed to start ASM
CLSRSC-00248: Failed to upgrade Oracle Clusterware Repository
CLSRSC-00249: Failed to start Cluster Ready Services
CLSRSC-00250: Failed to start Event Manager
CLSRSC-00251: Oracle Clusterware stack start initiated but failed to complete
CLSRSC-00252: Old CRS Home directory is invalid
CLSRSC-00253: Failed to call 'gethostbyname' with the argument 'string' (error:
string)
CLSRSC-00254: Could not create the directory 'string' (error: string)
CLSRSC-00255: Could not create the file 'string' (error: string)

CLSRSC-00256: Could not eval string: string
CLSRSC-00257: Cluster Time Synchronization Service start in exclusive mode
failed
CLSRSC-00258: Failed to configure and start ASM
CLSRSC-00259: Oracle Clusterware Repository configuration failed
CLSRSC-00260: Clusterware exclusive mode start of Cluster Ready Services failed
CLSRSC-00261: Failed to add voting disks
Cause: An attempt to add voting disks failed.
CLSRSC-00262: Failed to promote local GPnP setup to other cluster nodes
CLSRSC-00267: CSS could not exit exclusive mode
Cause: An attempt to stop running OHASD resources failed.
CLSRSC-00268: ORACLE_HOME is not set in the environment
CLSRSC-00269: Failed to add base type cluster_resource
CLSRSC-00270: Failed to register Clusterware type 'string'
CLSRSC-00271: Failed to add resource 'string'

CLSRSC-00272: Could not close file 'string' (error: string)
CLSRSC-00273: Failed to register the resource 'string' with the OHASD
CLSRSC-00274: Mismatching host to VIP IPs specified
CLSRSC-00275: No more elements in crs_nodevip_list
CLSRSC-00276: Unable to get VIP info for new node
CLSRSC-00277: Failed to perform new node configuration
CLSRSC-00278: Failed to perform last node configuration for upgrade
CLSRSC-00279: Failed to perform first node non rolling asm upgrade tasks for
cluster
CLSRSC-00280: Failed to perform first node tasks for cluster modeling upgrade
CLSRSC-00281: Failed to set active version of Oracle Clusterware
Cause: An error occurred while executing the 'crsctl set crs activeversion' command.
Action: Correct the problem indicated in the accompanying messages, and then retry.
CLSRSC-00284: Failed to perform last node tasks for cluster modeling upgrade
CLSRSC-00285: Failed to perform upgrade configuration from old 11.2 install

CLSRSC-00286: Failed to add Grid Infrastructure node applications
CLSRSC-00287: FirstNode configuration failed
CLSRSC-00288: Failed to start Grid Infrastructure node applications
CLSRSC-00289: Could not get existing VIP information
CLSRSC-00290: Error: validation of Single Instance CSS failed
CLSRSC-00291: Error: validation of 9i GSD failed
CLSRSC-00292: Error: validation of OLR config failed
CLSRSC-00293: Error: validation of OCR location 'string' failed
CLSRSC-00294: CSS cannot be run in realtime mode
CLSRSC-00296: No configuration parameter file was specified
CLSRSC-00297: Configuration parameter file 'string' could not be found
CLSRSC-00298: The Oracle CRS home path not found in the configuration
parameters
CLSRSC-00299: The configuration parameter file 'string' is not valid
CLSRSC-00300: Parameter 'string' not defined
CLSRSC-00301: Error in validate_ocrconfig
CLSRSC-00302: Unable to delete old services
CLSRSC-00303: Cannot complete the upgrade without the voting file list
CLSRSC-00304: Failed to upgrade ASM for Oracle Restart configuration
CLSRSC-00305: Failed to upgrade ASM in a rolling fashion for Oracle Clusterware
configuration
CLSRSC-00306: Failed to upgrade ASM in a nonrolling fashion for Oracle
Clusterware configuration
CLSRSC-00307: Failed to upgrade ASM service a rolling fashion for Oracle
clusterware configuration
CLSRSC-00308: Failed to get non-FQDN host name
CLSRSC-00309: Failed to get node network interfaces, error: (string)

CLSRSC-00310: Could not open log file string for append (error: string)
CLSRSC-00311: Failed to verify resources
CLSRSC-00312: Failed to verify HA resources
CLSRSC-00313: Error: 'string' is an unknown Operating System
CLSRSC-00314: Failed to call 'tolower_host' (error: string)
CLSRSC-00315: Clusterware configuration check failed
CLSRSC-00316: OLR configuration failed
CLSRSC-00317: Failed to register Oracle OHASD service
CLSRSC-00318: Failed to start Oracle OHASD service
CLSRSC-00319: Unable to stop running CSS
CLSRSC-00320: Migration of older version local_only to SIHA failed
CLSRSC-00323: Error: readlink failed (error: string)
CLSRSC-00324: Could not open old init.cssd

CLSRSC-00325: Configure Oracle Grid Infrastructure for a Cluster ... succeeded
Action: None
CLSRSC-00326: Configure Oracle Grid Infrastructure for a Cluster ... failed
CLSRSC-00327: Successfully configured Oracle Restart for a standalone server
Action: None
CLSRSC-00328: Removing Clusterware entries in file 'string'
Action: None
CLSRSC-00329: Replacing Clusterware entries in file 'string'
Action: None
CLSRSC-00330: Adding Clusterware entries to file 'string'
Action: None
CLSRSC-00331: Failure initializing entries in file 'string'
CLSRSC-00332: CRS resources for listeners are still configured
CLSRSC-00333: Failed to remove database listener
CLSRSC-00334: Failed to remove database listener, but continuing to deconfigure
with force option
CLSRSC-00335: Successfully downgraded Oracle Clusterware stack on this node
Action: None
CLSRSC-00336: Successfully deconfigured Oracle Clusterware stack on this node

Action: None
CLSRSC-00337: Successfully deconfigured Oracle Restart stack
Action: None
CLSRSC-00338: Successfully downgraded OCR to version string
Action: None
CLSRSC-00348: The Oracle Restart stack failed to stop
Cause: There was a failure in stopping the Oracle Restart stack.
Action: Stop the stack with 'crsctl stop has -f' and rerun the root script.
CLSRSC-00349: The Oracle Clusterware stack failed to stop
Cause: There was a failure in stopping the Oracle Clusterware stack.
Action: Stop the stack with 'crsctl stop crs -f' and rerun the root script.
CLSRSC-00350: Cannot configure two CRS instances on the same cluster
Cause: CRS is already configured on this node.
Action: Must deconfigure before proceeding with the configuration of new home.
CLSRSC-00351: Improper Oracle Clusterware configuration found on this host
Cause: There was an existing configuration found.
Action: Deconfigure the existing cluster configuration before starting to configure a
new Clusterware.
CLSRSC-00352: CRS is already configured on this node for the CRS home location
string
Cause: There was an attempt to configure the cluster when the cluster is already
configured.
Action: None
CLSRSC-00353: Run 'string/crs/install/string -deconfig' to deconfigure existing
failed configuration and then re-run 'string'
Cause: There was an attempt to configure the cluster when a prior failed
configuration was not cleaned up.
Action: Perform the action specified in the message.
CLSRSC-00354: Error: invalid interface
CLSRSC-00355: Error: Cannot change directory to 'string', invalid Berkeley
Database path
CLSRSC-00356: Error in opening directory 'string'

CLSRSC-00357: Failed to stop current Oracle Clusterware stack during upgrade
Cause: An error occurred while executing the 'crsctl stop crs -f' command from the
current CRS home.
Action: Either manually stop the current Oracle Clusterware stack or reboot the local
node to properly clean up the processes started by Oracle Clusterware, and then
rerun rootupgrade.sh.
CLSRSC-00359: Unable to get owner information for the executable string
CLSRSC-00360: Owner 'string' of the old CRS home differs from owner 'string' of
the new CRS home
Cause: The new CRS home was installed as the wrong OS user.
Action: Install the new CRS home as the owner of the old CRS home.
CLSRSC-00361: The Oracle Cluster Repository (OCR) check failed
CLSRSC-00362: The pre-upgrade checks failed, aborting the upgrade
Cause: One or more pre-upgrade checks failed. This message is accompanied by
others providing details of the error.
Action: Correct the problem indicated by the accompanying messages and retry.
CLSRSC-00363: User ignored prerequisites during installation
Cause: Informational message.
Action: None
CLSRSC-00364: Failed to propagate ASM credentials to the other nodes
Cause: An attempt to copy the ASM credentials to all remote cluster nodes failed
CLSRSC-00365: Failed to create credentials for ASM on the local node
Cause: Internal Error
CLSRSC-00366: Failed to import credentials for ASM
Cause: Internal Error
CLSRSC-00367: The value set for the parameter 'GNS_ADDR_LIST' is null
Cause: No GNS address was found while configuring the big cluster discovery
address.
CLSRSC-00368: Failed to set the node role 'string' for the local node
Cause: An error occurred while executing the 'crsctl set node role' command.
Action: Examine the accompanying messages from the 'crsctl set node role' command,
CLSRSC-00369: Failed to set maximum number of Hub nodes to string
Cause: An error occurred while executing the 'crsctl set cluster hubsize' command.
Action: Examine the accompanying messages from the 'crsctl set cluster hubmax'
command, correct the problem and retry.
CLSRSC-00370: Cloud Cluster requires Cloud ASM Server
Cause: Cloud ASM Server was not configured in the cluster.
CLSRSC-00371: Failed to add ASM remote configuration
Cause: An error occurred while executing the 'srvctl add asm -remote' command.
CLSRSC-00372: Failed to add ASM proxy configuration
Cause: An error occurred while executing the 'srvctl add asm -proxy' command.
CLSRSC-00375: Failed to copy ASM credentials to the GPnP directory
Cause: An error occurred while processing a copy operation.
CLSRSC-00376: Failed to get the configured node role for the node string
Cause: An error occurred while executing the 'crsctl get node role config -node
nodename' command.
Action: Examine the accompanying messages from the 'crsctl get node role config node nodename' command, correct the problem and retry.
CLSRSC-00377: Failed to create ASM credential domains
Cause: An error occurred while executing the 'crsctl add credmaint -path -ASM [local]' command.
CLSRSC-00378: Failed to get the configured node role for the local node
Cause: An error occurred while executing the 'crsctl get node role config' command.
Action: Examine the accompanying messages from the 'crsctl get node role config'
command, correct the problem and retry.
CLSRSC-00379: Invalid path for the password file used by ASM
Cause: The path for the password file used by ASM was not properly set in ASM
configuration.
CLSRSC-00380: Failed to create the Rapid Home Provisioning Server credential
domain
Cause: An error occurred while executing the 'crsctl add credmaint -path
GRIDHOME' command.

CLSRSC-00398: Failed to retrieve old Grid Infrastructure home location during
upgrade
Cause: An attempt to locate the previous version Oracle Clusterware home location
failed during upgrade, possibly because its configuration was corrupt or removed.
CLSRSC-00399: Failed to retrieve the network configuration during upgrade
Cause: Private interconnect configuration could not be retrieved from the previous
version Oracle Clusterware, possibly because its configuration was corrupt or
removed.
CLSRSC-00400: A system reboot is required to continue installing.
Cause: The installation of new drivers requires a node reboot to continue the install.
Action: Reboot the node and rerun the install or patch configuration step.
CLSRSC-00404: Failed to upgrade Cluster Health Monitor service in rolling fashion
for Oracle Clusterware configuration.
CLSRSC-00405: Unable to access old configuration file string of Cluster Health
Monitor.
Cause: Old Cluster Health Monitor configuration file was absent.
Action: None
CLSRSC-00406: Failed to find new administrative directory string of Cluster Health
Monitor.
CLSRSC-00408: Failed to create new configuration file string of Cluster Health
Monitor.
Cause: New configuration file of Cluster Health Monitor could not be created.
Action: Ensure that you have the required OS authority or permissions for creating
the indicated file.
CLSRSC-00409: Failed to patch Cluster Health Monitor service for Oracle
Clusterware configuration.
CLSRSC-00410: Cannot change directory to 'string'.
Cause: During OCFS upgrade, an attempt to change to the indicated file system
directory failed.
Action: Ensure that the directory ORACLE_HOME\cfs exists
CLSRSC-00411: A system reboot is required before using OCFS.
Cause: The existing OCFS driver could not be unloaded.
Action: Reboot the local node.
CLSRSC-00412: Failed to enable CRS after successfully installing the ACFS drivers.
Cause: After successfully configuring ACFS during an install, upgrade, or patch, the
root script failed to enable CRS again, using the command 'crsctl enable crs'.
Action: Correct the errors accompanying the failure of the enable command and rerun
the install configuration step.
CLSRSC-00413: Failed to disable CRS in preparation for a node reboot.
Cause: After a failure to install ACFS drivers, CRS is disabled. This allows the user to
reboot and install the drivers for the new version successfully.
Action: Correct the errors accompanying the failure of the disable command, run
'crsctl disable crs', reboot, and continue the install configuration step.
CLSRSC-00414: The OCR backup 'string' was not found on this node to perform
the last node downgrade
Cause: The node where the downgrade command was issued with the '-lastnode'
option was not the first node that was upgraded. The OCR backup is located on that
node.
Action: If this is the last node to be downgraded, copy the OCR backup to the location
mentioned in the error and downgrade with the '-lastnode' option. If this is not the
last node, re-run the downgrade command without the '-lastnode' option on this
node.
CLSRSC-00415: Failed to delete voting disks
Cause: An attempt to delete voting disks failed.
CLSRSC-00416: Failed to retrieve old Grid Infrastructure configuration data during
downgrade
Cause: An attempt to collect the older version Oracle Clusterware configuration data
failed during downgrade, possibly because its configuration was corrupt or removed.
CLSRSC-00417: Backup of olr.loc not found for downgrade
Cause: This cluster was not one successfully upgraded from an old version.
Action: Ensure that this is an upgraded cluster; then re-run the downgrade command.
CLSRSC-00418: Failed to create the ADVM volume resource for device string.
Cause: An error occurred while executing the 'srvctl add volume' command.
CLSRSC-00419: An error occurred attempting to query the volume resource.
Cause: An error occurred while executing the 'srvctl status volume' command.
CLSRSC-00420: The ACFS registration for device 'string' on mount path 'string'
could not be registered with CRS.
Cause: An error occurred while executing the 'acfsutil registry -a' command.
CLSRSC-00421: An error occurred attempting to query the file system resource.
Cause: An error occurred while executing the 'srvctl status // filesystem' command.
CLSRSC-00422: Failed to perform ACFS registry upgrade.
Cause: An error occurred while performing the ACFS registry upgrade.
CLSRSC-00423: Failed to stop database listener
Cause: An error occured while stopping the database listener.
Action: Try to stop the database listener manually using 'srvctl stop listener'
command.
CLSRSC-00424: Failed to stop database listener, but continuing to deconfigure with
force option
Cause: An error occured while stopping the database listener.
Action: None
CLSRSC-00425: Failed to create the ACFS drivers resource but continuing with the
installation
Cause: An error occured while creating the ACFS drivers resource.
Action: Check if your OS kernel is supported and run 'acfsroot enable' to create and
start the ACFS drivers resource.
CLSRSC-00426: Failed to create and start the ACFS drivers resource but continuing
with the patching
Cause: An error occured while creating and starting the ACFS drivers resource.
Action: Check if your OS kernel is supported and run 'acfsroot enable' to create and
start the ACFS drivers resource.
CLSRSC-00427: Failed to remove OCR file string on ASM using command string ...
output: string
Cause: Command failed.
CLSRSC-00428: Existing OCR configuration found, aborting the configuration.
Rerun configuration setup after deinstall.
Cause: While configuring a new cluster, OCR was found to be already configured.
Action: Deinstall and rerun configuration setup.
CLSRSC-00429: The Oracle Clusterware force upgrade was aborted
Cause: One or more pre-upgrade checks failed.
Action: Address the issues reported by accompanying messages and follow the
suggested action.
CLSRSC-00430: Failed to start rolling patch mode
Cause: An error occurred while executing the 'crsctl start rollingpatch' command.
Action: Examine the accompanying messages, correct the problem and retry.
CLSRSC-00431: Failed to stop rolling patch mode
Cause: An error occurred while executing the 'crsctl stop rollingpatch' command.
CLSRSC-00432: Invalid destination CRS home

Cause: The CRS home specified by '-dstcrshome' was identical to the current CRS
home.
Action: Remove '-dstcrshome path to CRS home' from the command line or specify a
different CRS home.
CLSRSC-00433: This command is deprecated and has been replaced by 'rootcrs.pl postpatch'
Cause: A deprecated command was issued.
Action: Use 'rootcrs.pl -postpatch'. See usage for complete command line options.
CLSRSC-00434: An operating system reboot is required to continue the
deconfiguration.
Cause: The uninstall of the ACFS drivers failed. An operating system reboot is
required to continue the deconfiguration.
Action: Reboot the node and restart the deconfiguration step.
CLSRSC-00435: Failed to enable CRS after successfully uninstalling the ACFS
drivers.
Cause: After successfully deconfiguring ACFS during an downgrade, the root script
failed to re-enable CRS using the command 'crsctl enable crs'.
the deconfiguration step.
Cause: An attempt to disable CRS in preparation for a system reboot failed. The
reboot is associated with a failed removal of ACFS drivers.
'crsctl disable crs', reboot, and continue the deconfiguration step.
CLSRSC-00437: Failed to add the management database listener
Cause: An error occurred while adding the management database listener.
Action: Rerun the root.sh script after resolving the problem indicated by the
accompanying messages.
CLSRSC-00438: There is a mismatch between the node list and node role list in
'string/crs/install/crsconfig_addparams'
CLSRSC-00439: Unable to configure a Leaf node first. Run root.sh on a Hub node
first.
Cause: root.sh was run on a Leaf node first.
Action: Run root.sh in a Hub node first.
CLSRSC-00440: Failed to copy GPnP setup from a remote node string that belongs
to an upgraded cluster
Cause: The remote node was unreachable or has not completed upgrade processing.
Action: Make sure the given node can be reached and it has been successfully
upgraded, and then rerun the 'rootupgrade.sh -join -existingNode node name'
command.
CLSRSC-00442: Failed to copy Oracle Clusterware configuration files from existing

nodes
Cause: During the operation of adding nodes, an attempt to copy configuration files
from an existing node failed because no node was unreachable or user equivalence
did not work.
Action: Ensure that at least one node can be reached and user equivalence is properly
configured between the local node and existing nodes, and then rerun the 'root.sh'
command. Contact Oracle Support Services if the problem persists.
CLSRSC-00443: An active CSS daemon was found during CSS exclusive mode
startup
CLSRSC-00444: The 'root.sh' command must first be run on node 'string' where the
OUI session was invoked
Cause: The node where the 'root.sh' command was running was not the node on
which the OUI session was invoked.
Action: Run the 'root.sh' command on the node where the OUI was invoked.
CLSRSC-00445: The Oracle Grid Infrastructure has already been upgraded to
[string]
Cause: The rootupgrade.sh was successfully executed on all cluster nodes.
Action: No further action is required.
CLSRSC-00446: The upgrade has not yet been performed on this node
Cause: The rootupgrade.sh was not yet executed on the local node, and the force
option was specified.
Action: Rerun rootupgrade.sh without the force option on the local node.
CLSRSC-00447: The upgrade has not yet been performed on node string
Cause: The force option was supplied when some nodes in the cluster have not yet
been upgraded. The upgrade cannot be forced to complete while some nodes running
Oracle Clusterware have not yet been upgraded.
Action: Rerun rootupgrade.sh without force option on the specified node.
CLSRSC-00448: Cluster-wide Grid Plug and Play profile not found on this node
Cause: The Grid Plug and Play profile was not found on this node. The node may
have been unreachable when the profile was created and distributed during an earlier
upgrade operation.
Action: First, force completion of the earlier upgrade on the other nodes using
'rootupgrade.sh -force'. Then issue 'rootupgrade.sh -join -existingNode <node_name>'
on the local node to rejoin this node to the cluster. Alternatively, remove this node
from the cluster and then add it back.
CLSRSC-00449: Failed to retrieve the value of attribute 'check_interval' for CVU
resource during upgrade
Cause: An attempt to retrieve the value of attribute 'check_interval' for CVU resource
failed during upgrade, possibly because its configuration was corrupt or removed.
CLSRSC-00450: Failed to determine if the CVU resource was configured

Cause: During upgrade, an attempt to determine if CVU resource was configured
failed, possibly because its configuration was corrupt or removed.
CLSRSC-00451: The last Hub node cannot be deconfigured while the Flex Cluster
still has Leaf nodes
Cause: An attempt to deconfigure the last Hub node in the cluster found one or more
Leaf nodes still active.
Action: Deconfigure all other nodes before deconfiguring the local node.
CLSRSC-00452: Failed to upgrade ASM on the current node during attempt to join
an upgraded cluster
Cause: The ASM upgrade invoked during node join failed.
Action: Examine the accompanying messages, correct the problem and rerun the
'rootupgrade.sh -join -existingNode node name' command.
CLSRSC-00453: An operating system reboot is required to continue the downgrade
Cause: The reinstall of the older version of Oracle ASM Cluster file system (ACFS)
drivers failed. An operating system reboot is required to continue the downgrade.
Action: Reboot the node before running 'crsctl start crs' from the older version of CRS
home.
CLSRSC-00454: Failed to initiate the upgrade of Oracle Clusterware
Cause: An error occurred while executing the 'crsctl startupgrade' command.
Action: Rerun the rootupgrade.sh script and contact Oracle Support Services if the
problem persists.
CLSRSC-00455: Failed attempt to initiate patch on a Leaf node
Cause: Pre-patch failed because of an attempt to execute 'rootcrs.pl -prepatch' on a
Leaf node before any Hub node being patched.
Action: Run the 'rootcrs.pl -prepatch' command on a Hub node first, before running it
on the current node.
CLSRSC-00456: The Oracle Grid Infrastructure has already been configured.
Cause: An attempt to run the configuration script was aborted because it had already
been successfully executed on this node.
CLSRSC-00457: Oracle Restart is currently configured and cannot be deconfigured
using this Oracle Clusterware deconfiguration command.
Cause: A request to deconfigure Oracle Clusterware was rejected because the existing
configuration was Oracle Restart.
Action: Run the command 'roothas.pl -deconfig' to deconfigure Oracle Restart.
CLSRSC-00458: Failed to restore the ASM diagnostic destination during
downgrade
Cause: An attempt to downgrade using the 'asmca -downgrade' command failed,
because the ASM diagnostic destination could not be restored.
Action: Correct the problem indicated in the accompanying messages.
CLSRSC-00459: The '-lastnode' option is not specified on the downgrade command.

Cause: An attempt to downgrade the last node failed because the '-lastnode' option
was missing from the downgrade command line.
Action: Reissue the downgrade command on this node with the '-lastnode' option
specified after downgrading all other nodes.
CLSRSC-00460: failed to start Oracle Restart stack
Cause: An error occurred when the Oracle Restart stack was automatically restarted
during installation or configuration processing.
Action: Retry the configuration script root.sh. If the problem persists, contact Oracle
Support Services
CLSRSC-00461: Failed to retrieve OCR locations
Cause: An error occurred while executing the 'ocrcheck -config -details' command.
CLSRSC-00462: Failed to copy OCR location configuration file to remote nodes
Cause: An attempt to copy configuration file to remote nodes failed because the target
node was unreachable or user equivalence did not work.
Action: Ensure that the remote nodes can be reached and user equivalence is properly
configured across the cluster nodes, and then rerun the 'root.sh' command. Contact
Oracle Support Services if the problem persists.
CLSRSC-00463: The deconfiguration or downgrade script could not stop current
Oracle Clusterware stack.
Cause: An error occurred while executing the 'crsctl stop crs -f' command from the
current CRS home.
Action: After deconfiguration or downgrade completes, either manually stop the
current Oracle Clusterware stack or reboot the local node to properly clean up the
processes started by Oracle Clusterware.
CLSRSC-00464: Starting retrieval of the cluster configuration data
Cause: Retrieval of the cluster configuration data from the older version of Oracle
Grid Infrastructure stack has started.
Action: None
CLSRSC-00465: Retrieval of the cluster configuration data has successfully
completed.
Cause: Retrieval of the cluster configuration data from the older version of Oracle
Grid Infrastructure stack has successfully completed.
Action: None
CLSRSC-00466: Starting shutdown of the current Oracle Grid Infrastructure stack
Cause: Shutdown of the older version of Oracle Grid Infrastructure stack has started.
Action: None
CLSRSC-00467: Shutdown of the current Oracle Grid Infrastructure stack has
successfully completed.
Cause: Shutdown of the older version of Oracle Grid Infrastructure stack has
successfully completed.
Action: None
CLSRSC-00468: Setting Oracle Clusterware and ASM to rolling migration mode

Cause: An attempt has been made to set Oracle Clusterware and ASM to rolling
migration mode.
Action: None
CLSRSC-00469: Successfully set Oracle Clusterware and ASM to rolling migration
mode
Cause: An operation to set Oracle ASM to rolling migration mode has successfully
completed.
Action: None
CLSRSC-00470: Starting non-rolling migration of Oracle ASM
Cause: An attempt has been made to initiate non-rolling migration of Oracle ASM.
Action: None
CLSRSC-00471: Successfully initiated non-rolling migration of Oracle ASM
Cause: An operation to initiate non-rolling migration of Oracle ASM has successfully
completed.
Action: None
CLSRSC-00472: Attempting to export the OCR
Cause: An attempt has been made to export the OCR.
Action: None
CLSRSC-00473: Successfully exported the OCR
Cause: The OCR has successfully been exported.
Action: None
CLSRSC-00474: Initiating upgrade of resource types
Cause: An attempt has been made to initiate upgrade of resource types.
Action: None
CLSRSC-00475: Upgrade of resource types successfully initiated.
Cause: Upgrade of resource types has successfully started.
Action: None
CLSRSC-00476: Finishing upgrade of resource types
Cause: An attempt has been made to finish upgrade of resource types.
Action: None
CLSRSC-00477: Successfully completed upgrade of resource types
Cause: Upgrade of resource types has successfully completed.
Action: None
CLSRSC-00478: Setting Oracle Clusterware active version on the last node to be
upgraded
Cause: An attempt has been made on the last node to be upgraded to set the Oracle
Clusterware active version.
Action: None
CLSRSC-00479: Successfully set Oracle Clusterware active version

Cause: An operation initiated on the last node to be upgraded to set Oracle
Clusterware active version has successfully completed.
Action: None
CLSRSC-00480: Starting the process of upgrading local listeners
Cause: The process of upgrading local listeners has started.
Action: None
CLSRSC-00481: Successfully completed the process of upgrading local listeners
Cause: The process of upgrading local listeners has successfully completed.
Action: None
CLSRSC-00482: Running command: 'string'
Cause: An attempt has been made to run the command mentioned in the message.
Action: None
CLSRSC-00483: unable to run 'rootcrs.pl -prepatch' to perform rolling, in-place
patching for shared Grid Infrastructure home
Cause: In the course of patching a shared Grid Infrastructure home, an attempt to
execute the 'rootcrs.pl -prepatch' command failed because rolling in-place patching of
a shared home is not allowed.
Action: Reissue the 'rootcrs.pl -prepatch' command with the '-nonrolling' or 'dstcrshome' option specified .
CLSRSC-00484: error querying CRS software version on node 'string'
Cause: An error occurred while executing the 'crsctl query crs softwareversion'
command.
Action: Correct the problem indicated in the accompanying messages and then rerun
rootupgrade.sh. Contact Oracle Support Services if the problem persists.
CLSRSC-00485: Local port=string and remote port=string should not be same.
Cause: The rootupgrade script was aborted because the specified local and remote
ports were the same.
Action: Rerun the rootupgrade.sh script after changing the port numbers.
CLSRSC-00487: Check for ASM compatibility version failed during downgrade.
Cause: An attempt to downgrade the current node failed because the ASM
compatibility version was already advanced after upgrade.
Action: Downgrade is not allowed in this case. Contact Oracle Support Services for
further action.
CLSRSC-00488: Patching the Grid Infrastructure Management Repository database
failed.
Cause: An error occured when executing the 'sqlpatch -db -MGMTDB' command' to
patch the Grid Infrastructure Management Repository database.
Action: Address the issues reported by accompanying messages and rerun the
'rootcrs.pl -postpatch' command. If the problem persists, contact Oracle Support
Services.
CLSRSC-00489: Stopping the Grid Infrastructure Management Repository database

failed.
Cause: An error occurred while executing the 'srvctl stop mgmtdb' command.
'rootcrs.pl -postpatch' command.
CLSRSC-00490: Starting the Grid Infrastructure Management Repository database
failed.
Cause: An error occurred while executing the 'srvctl start mgmtdb' command.
CLSRSC-00491: Failed to disable the Grid Infrastructure Management Repository
database
Cause: An error occurred while executing the 'srvctl disable mgmtdb' command.
CLSRSC-00492: Failed to enable the Grid Infrastructure Management Repository
database
Cause: An error occurred while executing the 'srvctl enable mgmtdb' command.
CLSRSC-00493: failed to initiate rolling patch on the current node because there is
only one active HUB node
Cause: An attempt to execute the 'rootcrs.pl -prepatch' command failed because there
was only one active HUB node.
Action: Reissue the 'rootcrs.pl -prepatch' command with the '-nonrolling' option
specified or configure more than one active HUB node in the cluster.
CLSRSC-00494: Failed to execute this command. Current directory is under an
ACFS mount point.
Cause: An attempt to execute a command that would result in a forced / shutdown of
ACFS was rejected because the current directory is on an ACFS file system.
Consequently, the forced shutdown of ACFS would terminate the execution of the
attempted command.
Action: Ensure that the current shell has no dependencies on ACFS file systems (i.e.
current directory not on ACFS and not a sub-shell of a process whose working
directory is on ACFS) and retry the command.
CLSRSC-00495: failed to get active role for the node string
Cause: An error occurred while executing the command 'crsctl get node role status node nodename'.
CLSRSC-00496: failed to get active role for the local node
Cause: An error occurred while executing the command 'crsctl get node role status'.
CLSRSC-00497: failed to retrieve the configured cluster mode

Cause: An error occurred while executing the command 'crsctl get cluster mode
config'.
CLSRSC-00498: invalid cluster mode
Cause: An internal error. The cluster mode returned by the command 'crsctl get
cluster mode config' was neither 'standard' nor 'flex'.
CLSRSC-00499: Stopping the Grid Infrastructure Management Repository database
failed.
Cause: An error occurred while executing the 'srvctl stop mgmtdb' command.
Action: Examine the accompanying messages, correct the problem and rerun
rootupgrade.sh.
CLSRSC-00500: Starting the Grid Infrastructure Management Repository database
failed.
Cause: An error occurred while executing the 'srvctl start mgmtdb' command.
rootupgrade.sh.
CLSRSC-00501: failed to disable the Grid Infrastructure Management Repository
database
Cause: An error occurred while executing the 'srvctl disable mgmtdb' command.
rootupgrade.sh.
CLSRSC-00502: failed to enable the Grid Infrastructure Management Repository
database
Cause: An error occurred while executing the 'srvctl enable mgmtdb' command.
rootupgrade.sh.
CLSRSC-00503: Deleting the Grid Infrastructure Management Repository database
failed.
Cause: An attempt to connect to the GI Management Repository database failed or an
error occurred while executing the SQL statement 'drop database'.
rootupgrade.sh.
CLSRSC-00504: The root script cannot proceed on this node string until the current
first-node operations have finished on the first node string.
Cause: An attempt to run the root script on this node failed because the root script
was still running on the first node and had not yet completed.
Action: Allow the root script to complete execution on the first node and then restart
the root script on this node.
CLSRSC-00505: The root script cannot proceed on this node string because the root
script encountered errors during execution on the first node string.
Cause: An attempt to run the root script on this node failed because the root script
encountered errors during execution on the first node.
Action: Correct the problems indicated by the root script on the first node and rerun
the script on that node. Following successful completion on the first node, restart the
root script on this node.
CLSRSC-00506: The root script cannot proceed on this node string because the firstnode operations have not completed and the first node string has crashed or gone
offline.
Cause: An attempt to run the root script on this node failed because the root script did
not completed successfully on the first node, and the first node has crashed or gone
offline.
Action: Rerun the root script on any of the remaining nodes supplying the -force
option to cause it to act as the first node.
CLSRSC-00507: The root script cannot proceed on this node string because either
the first-node operations have not completed on node string or there was an error
in obtaining the status of the first-node operations.
Cause: An attempt to run the root script on this node failed because the root script has
not completed and may not yet have started on the first node or there was an error in
obtaining the status of the first node.
Action: Start the root script on the first node if necessary, and after it has completed
successfully on the first node, restart the root script on this node.
CLSRSC-00508: The root script cannot be started with the -first -force option on this
node string, while the original first node string is still online.
Cause: An attempt to run the root script supplying the -first -force option on this node
failed because the first node was still online.
Action: Run the root script on the first node. Following successful completion on the
first node, restart the root script on this node.
CLSRSC-00509: invalid ASM mode
Cause: This is an internal error. The ASM mode was an undefined value at this point.
CLSRSC-00510: failed to delete the voting file on diskgroup 'string' during
deconfiguration
Cause: The attempt to remove a voting file failed because an error occurred while
executing the command 'crsctl delete css votedisk +diskgroup'.
Action: Retry the above command manually. If the problem persists, contact Oracle
Support Services.
CLSRSC-00511: failed to set Oracle Clusterware and ASM to rolling migration
mode
Cause: An error occurred while executing the command 'crsctl start rollingupgrade'.
Action: Correct the problem indicated in the accompanying messages and rerun
rootupgrade.sh.
CLSRSC-00512: failed to force node string as the first node because it is not a hub
node
Cause: An attempt to run the root script supplying the -force option on this node has
failed because it is not a hub node.
Action: Run the root script with the -force option on a hub node.
CLSRSC-00514: failed to reset cardinality of Flex ASM to original value
Cause: An error occurred while attempting to reset Flex ASM cardinality, either in
retrieving the previously stored value using 'crsctl status resource' or in restoring the
previous value using 'srvctl modify asm'.
rootupgrade.sh.
CLSRSC-00515: Starting OCR manual backup.
Cause: An attempt has been made to generate OCR manual backup.
Action: None
CLSRSC-00516: OCR manual backup successful.
Cause: OCR manual backup completed normally.
Action: None
CLSRSC-00517: The root script cannot run with the '-lastnode' option on this node
string because the OCR backup file is on node string.
Cause: An attempt to run the root script supplying the '-lastnode' option on this node
has failed because the OCR backup file is not on this node.
Action: Run the root script on this node without '-lastnode' option.
CLSRSC-00518: cannot open directory 'string'
Cause: An attempt to open the specified directory has failed.
Action: Ensure that the user running root script has read permission on the directory.
CLSRSC-00519: cannot move directory string to directory string
Cause: An attempt to move the source directory has failed.
Action: Ensure that the user running root script has read permission on the source
directory and write permission on destination directory.
CLSRSC-00520: Clusterware version on this node too old to join target cluster
Cause: An attempt to join the current node to an upgraded cluster failed because the
join is not supported for nodes with Oracle Clusterware older than version 11.2.0.1.
Action: Delete this node and then add this node back into Clusterware using the 'add
node' operation.
CLSRSC-00522: The root script cannot downgrade this node string with the 'lastnode' option because there is at least one other node that has not finished
downgrade.
Cause: An attempt to run the root script with the '-lastnode' option on this node failed
because there was at least one other node that had not finished downgrade.
Action: Run the root script on this node with the '-lastnode' option after all other
nodes have completed downgrade.
CLSRSC-00523: The root script cannot downgrade this node string because there is
at least one other node that has not finished downgrade and this node should
downgrade with the '-lastnode' option.
Cause: An attempt to run the root script on this node failed because there was at least
one other node that had not finished downgrade and this node should downgrade
with the '-lastnode' option.
Action: Run the root script on this node with the '-lastnode' option after all other
nodes have completed downgrade.
CLSRSC-00524: Setting Oracle Clusterware to rolling migration mode
Cause: The command 'crsctl start rollingupgrade version' to initiate rolling migration
of Oracle Clusterware was issued.
Action: None
CLSRSC-00525: Successfully set Oracle Clusterware to rolling migration mode
Cause: The command 'crsctl start rollingupgrade version' to initiate a rolling migration
of Oracle Clusterware completed successfully.
Action: None
CLSRSC-00526: The root script cannot run with the '-first -force' options to force
current node string as the first node.
Cause: An attempt to run the root script with options '-first -force' on this node failed
because first-node operations had already been done.
Action: Run the root script on this node without the options '-first -force'.
CLSRSC-00527: The root script cannot run with the '-force' option to force current
node string as the last node during fresh install (case: first-node operations
complete).
Cause: An attempt to run the root script with option '-force' on this node failed
because there are no last-node operations for a fresh install, and the first-node
operations had been done.
Action: Run the root script on this node without the option '-force'.
CLSRSC-00528: The root script cannot run with the '-force' options to force current
node string which is the installer node as the last node during upgrade before firstnode operations have been done.
Cause: An attempt to run the root script with option '-force' on installer node failed
because the first-node operations had not been done.
Action: Run the root script on this node without the option '-force'.
node string as the last node during fresh install (case: first-node operations not
complete).
Cause: An attempt to run the root script with option '-force' on this node failed
because there are no last-node operations for a fresh install, and the first-node
operations had not been done.
Action: Run the root script on this node with the options '-first -force'.
node string which is a non-installer node as the last node during upgrade before
first-node operations have been done.
Cause: An attempt to run the root script with option '-force' on a non- installer node
failed because the first-node operations had not been done.
Action: Run the root script on this node with the options '-first -force'.
CLSRSC-00531: The root script does not need the '-first -force' options to force
current node string as the first node.
Cause: An attempt to run the root script with options '-first -force' on this node failed
because the '-first -force' options were not needed on installer node.
Action: Run the root script on this node without the options '-first -force'.
CLSRSC-00532: Clusterware version string does not support downgrade for nodes
that have not been upgraded.
Cause: An attempt to downgrade this node failed because Oracle Clusterware
versions older than 11.2.0.3 do not support downgrade for nodes that have not been
upgraded.
Action: Leave this node unupgraded as it is.
CLSRSC-00533: failed to get the OCR backup information: string
Cause: An attempt to downgrade this node failed because the 'ocrdump' command
failed to retrieve the OCR backup information.
Action: Correct the problem indicated in the accompanying messages and then retry
downgrade.
CLSRSC-00534: Current node string cannot be the last node to downgrade because
the OCR backup file is on node string.
Cause: An attempt to downgrade this node supplying the '-lastnode' option failed
because the OCR backup file was not on this node.
Action: Supply the '-downgrade -lastnode' option on the node where the OCR backup
file is located.
CLSRSC-00535: There is nothing to be downgraded on this node.
Cause: An attempt to downgrade this node failed because this node has never been
upgraded.
CLSRSC-00537: The root script failed to copy the OCR backup file from node string
to shared storage.
Cause: An error occurred while copying the OCR backup file to shared storage.
Action: Examine the accompanying messages, correct the problem indicated and
CLSRSC-00538: The root script failed to get the name of the OCR backup file on
the ASM diskgroup, and local node string does not have the OCR backup file on
local storage.
Cause: An error occurred while getting the OMF name of the OCR backup file using
the 'asmcmd find' command.
Action: Examine the accompanying messages from the 'asmcmd find' command, and
correct the problem indicated.
CLSRSC-00539: There is at least one expired OCR backup on the ASM diskgroup,
and the root script failed to remove it from the ASM diskgroup.
Cause: An error occurred while removing the expired OCR backup file using the
'asmcmd rm' command.
Action: Examine the accompanying messages from the 'asmcmd rm' command, and
correct the problem indicated.
CLSRSC-00540: The root script failed to get a unique name of the OCR backup file
on the ASM diskgroup using string, and local node string does not have the OCR
backup file on local storage.
Cause: There are more than one OMF names corresponding to the given OCR backup
file name.
Action: Remove the expired OCR backup file from the ASM diskgroup using
'asmcmd rm' command.
CLSRSC-00544: If the cluster is downgraded after a partial upgrade, the downgrade
command must be run on the node string with the '-lastnode' option to restore
global configuration data.
Cause: The OCR backup is located on that node.
Action: The downgrade command must be run on the specified node with the 'lastnode' option.
CLSRSC-00545: Voting files are not found.
Cause: The voting files are either removed by an earlier operation or the query for the
voting files failed.
Action: Run 'crsctl query css votedisk' to check if the voting files are configured.
CLSRSC-00546: The Grid Infrastructure processes identified by the following PIDs
(string) are still active.
Cause: There were still some of Grid Infrastructure processes running after shutting
down the Grid Infrastructure stack.
Action: Run the 'crsctl stop crs -force' command again, or 'rootcrs.pl -prepatch cleanpids' to terminate active processes before continuing the patch process.
CLSRSC-00549: The root script cannot downgrade this node string with the 'lastnode' option because the Grid Infrastructure stack is up on at least one other
cluster node.
Cause: An attempt to run the root script with the '-lastnode' option on this node failed
because there was at least one other cluster node with its Grid Infrastructure stack up.
Action: Run the root script on this node with the '-lastnode' option after the Grid
Infrastructure stack on all other cluster nodes is down.
CLSRSC-00550: Local node string failed to check the status of the Grid
Infrastructure stack of other cluster nodes.
Cause: An attempt to downgrade this node with the '-lastnode' option failed because
the root script failed to check the status of the Grid Infrastructure stack of other
cluster nodes by starting CSS in exclusive mode.
Action: Correct the problem indicated in the accompanying messages and then retry
downgrade.
CLSRSC-00551: unable to start rolling mode upgrade due to nodes running or to

prior non-rolling upgrade
Cause: The cluster was either previously upgraded in non-rolling mode or the Oracle
Grid Infrastructure stack has been started on some nodes after the non-rolling
upgrade installer interview.
Action: Shutdown the Oracle Grid Infrastructure stack on all other nodes and then
CLSRSC-00552: unable to proceed with downgrade due to missing option 'lastnode' or '-online'
Cause: An attempt to downgrade a node failed because a required option was
missing from the downgrade command line. Either '-lastnode' or '-online' must be
specified.
Action: To perform a downgrade offline, shutdown the Oracle Grid Infrastructure
stack on all other nodes and then reissue the downgrade command on this node
specifying the '-lastnode' option. Otherwise, reissue the downgrade command on this
node specifying the '-online' option.
CLSRSC-00553: unable to proceed with downgrade because both '-lastnode' and 'online' were specified
Cause: An attempt to downgrade a node failed because both '-lastnode' and '-online'
were specified in the downgrade command line.
Action: To perform a downgrade offline, shutdown the Oracle Grid Infrastructure
stack on all other nodes and then reissue the downgrade command on this node
specifying the '-lastnode' option. Otherwise, reissue the downgrade command on this
node specifying the '-online' option.
CLSRSC-00554: unable to perform an online downgrade after the cluster was
upgraded completely
Cause: An attempt to downgrade a node failed because the option '-online' was
specified in the downgrade command after the cluster had been upgraded
completely.
Action: Reissue the downgrade command on this node without '-online' option.
CLSRSC-00555: unable to downgrade node string with '-lastnode' option because
OCR backup information was not available
Cause: An error occurred while downgrading this node with '-lastnode' option
because the OCR backup information was not available.
Action: Run the root script on this node without '-lastnode' option.
CLSRSC-00556: Oracle Clusterware stack on this node has been successfully
downgraded. There were some errors which can be ignored.
Cause: The downgrade was successful, but stopping the Oracle Clusterware
afterwards failed.
Action: Retry the stop operation by running 'crsctl stop crs -f' from the higher version
home.
CLSRSC-00557: Oracle Clusterware stack on this node has been successfully
deconfigured. There were some errors which can be ignored.
Cause: The deconfiguration was successful, but stopping the Oracle Clusterware
afterwards failed.
Action: Retry the stop operation by running 'crsctl stop crs -f' from the higher version
home.
CLSRSC-00558: failed to deconfigure ASM
Cause: There was an error in deconfiguring ASM.
Action: Examine the accompanying messages and correct the problem.
CLSRSC-01001: Failed to add resource OC4J
Cause: An error occurred while executing the 'srvctl add oc4j' command.
CLSRSC-01002: Failed to create or update the wallet APPQOSADMIN
Cause: An error occurred while creating the wallet.
CLSRSC-01003: Failed to start resource OC4J
Cause: An error occurred while executing the 'srvctl start oc4j' command.
CLSRSC-01004: Failed to enable resource OC4J
Cause: An error occurred while executing the 'srvctl enable oc4j' command.
CLSRSC-01005: Failed to disable resource OC4J
Cause: An error occurred while executing the 'srvctl disable oc4j' command.
CLSRSC-01006: Failed to create the wallet APPQOSADMIN or associated users
during upgrade.
Cause: An error occurred while creating the wallet APPQOSADMIN or the users
oc4jamin and qosadmin during the upgrade.
Action: Respond as follows: 1 - Correct the problem indicated in the accompanying
messages. 2 - Rerun rootupgrade.sh.
CLSRSC-01007: Failed to start OC4J resource
Cause: An error occurred while executing the 'srvctl start oc4j' command.
Action: Respond as follows: 1 - Correct the problem indicated in the accompanying
messages. 2 - Rerun rootupgrade.sh.
CLSRSC-01008: The script string either does not exist or is not executable.
Cause: The specified script did not exist or was not executable.
Action: Make sure the script exists and it has execute access.
CLSRSC-01009: failed to stop resource OC4J
Cause: An error occurred while executing the 'srvctl stop oc4j' command.
Action: Correct the problems indicated in the accompanying messages and rerun
rootupgrade.sh
CLSRSC-02000: Failed to enable CRS after successfully installing the OKA drivers.
Cause: After successfully configuring OKA during an install, upgrade, or patch, the
root script failed to enable CRS again, using the command 'crsctl enable crs'.
the install configuration step.
Cause: After failure to install OKA drivers, an attemmpt to disable CRS in
preparation for a node reboot was unsuccessful.
'crsctl disable crs', reboot, and resume the install configuration step.
CLSRSC-02002: Failed to enable CRS after successfully uninstalling the OKA
drivers.
Cause: After successfully deconfiguring OKA during a downgrade, the root script
failed to re-enable CRS using the command 'crsctl enable crs'.
the deconfiguration step.
CLSRSC-02003: An operating system reboot is required to continue the
deconfiguration.
Cause: The uninstall of the OKA drivers failed. An operating system reboot is
required to continue the deconfiguration.
Action: Reboot the node and restart the deconfiguration step.
Cause: An attempt to disable CRS in preparation for a system reboot failed. The
reboot is associated with a failed removal of OKA drivers.
'crsctl disable crs', reboot, and continue the deconfiguration step.
CLSRSC-02006: Failed to create the OKA drivers resource but continuing with the
installation
Cause: An error occured while creating the OKA drivers resource.
CLSRSC-02007: OKA driver install actions failed
Cause: An error occurred while installing OKA drivers using the 'okaroot install'
command.
Action: Examine the accompanying messages from the 'okaroot install' command,
Cause: The installation of new OKA drivers requires a node reboot to continue the
install.
Action: Reboot the node and rerun the install configuration step.
CLSRSC-02009: Failed to create and start the OKA drivers resource but continuing
with patching
Cause: An error occured while creating and starting the OKA drivers resource.
Action: Check if your OS kernel is supported and run 'okaroot enable' to create and
start the OKA drivers resource.
CLSRSC-02501: The AFD driver install actions failed.

Cause: An error occurred while installing the AFD driver using the 'afdroot install'
command.
Action: Examine the accompanying messages from the 'afdroot install' command,
Cause: Installation of the new AFD driver requires a reboot to continue.
Action: Reboot the node and rerun the install configuration step.
CLSRSC-02503: Failed to add resource 'string'
Cause: An error occurred while attempting to add AFD resource.
Action: Correct the problem indicated in the accompanying messages and retry the
command.
CLSRSC-02504: Failed to rescan devices with 'afdtool -rescan'
Cause: An error occurred while executing the 'afdtool -rescan' command.
command.
CLSRSC-02505: An operating system reboot is required to continue the operation.
Cause: The uninstall of the AFD driver failed. An operating system reboot is required
to continue the upgrade or deconfiguration.
Action: Reboot the node and restart the operation.
CLSRSC-02506: An operating system reboot is required at the end of the deinstall.
Cause: The uninstall of the AFD driver failed. An operating system reboot is required
to complete the deinstall.
Action: Reboot the node after deinstall.
CLSRSC-02601: Failed to add Oracle Cluster Health Analysis resource
Cause: An error occurred while executing the 'srvctl add cha' command.
command.
CLSRSC-02602: Failed to forcibly add Oracle Cluster Health Analysis resource
Cause: An error occurred while executing the 'srvctl add cha -force' command.
command.
CLSRSC-02603: Failed to start Oracle Cluster Health Analysis resource
Cause: An error occurred while executing the 'srvctl start cha' command.
command.
CLSRSC-02604: Failed to set the TARGET to ONLINE for Oracle Cluster Health
Analysis resource
Cause: An error occurred while executing the 'srvctl start cha' command.
command.
CLSRSC-03000: Invalid object 'string' specified on command line.

Cause: The object specified on the command line was not recognized.
Action: Use appcluster.pl with the --help option to display valid options. Ensure that
a valid option is specified.
CLSRSC-03002: Oracle Clusterware has already been configured for non-database
applications.
Cause: A request to configure Oracle Clusterware for non-database applications was
rejected because Clusterware is already configured for non-database applications.
Action: If this is the expected state then this is not an error. If it is not then Oracle
Clusterware can be de-configured and configured.
CLSRSC-03003: Cannot configure Oracle Restart for non-database applications
(Clusterware is only for clusters).
Cause: A request configure Oracle Clusterware for non-database applications was
rejected because Oracle Grid Infrastructure for a stand-alone server (Oracle Restart)
was configured.
Action: De-configure Oracle Restart and configure Oracle Clusterware.
CLSRSC-03004: Failed to gather the configuration information for the node
applications.
Cause: An error occurred while gathering the configuration information for the node
applications.
CLSRSC-04000: Oracle Trace File Analyzer (TFA) Collector is not supported on this
platform.
Action: None
CLSRSC-04001: Installing Oracle Trace File Analyzer (TFA) Collector.
Action: None
CLSRSC-04002: Successfully installed Oracle Trace File Analyzer (TFA) Collector.
Action: None
CLSRSC-04003: Successfully patched Oracle Trace File Analyzer (TFA) Collector.
Action: None
CLSRSC-04004: Failed to install Oracle Trace File Analyzer (TFA) Collector. Grid
Infrastructure operations will continue.
Cause: The Installation of Oracle Trace File Analyzer (TFA) Collector failed with the
accompanying errors.
Action: The Oracle Trace File Analyzer (TFA) Collector will not be available, but Grid
Infrastructure operation is unaffected. Address the issues reported by accompanying
messages and retry using the command '<GI_Home>/crs/install/tfa_setup -crshome
<GI_Home>'. If the problem persists, contact Oracle Support Services for further
action.
CLSRSC-04005: Failed to patch Oracle Trace File Analyzer (TFA) Collector. Grid
Cause: An attempt to patch Oracle Trace File Analyzer (TFA) Collector failed with the
Action: The Oracle Trace File Analyzer (TFA) Collector may not be available, but Grid
messages and retry using the command '<GI_Home>/crs/install/tfa_setup -crshome
<GI_Home>'. If the problem persists, contact Oracle Support Services for further
action.
CLSRSC-04006: Removing Oracle Trace File Analyzer (TFA) Collector.
Action: None
CLSRSC-04007: Successfully removed Oracle Trace File Analyzer (TFA) Collector.
Action: None
CLSRSC-04008: Failed to remove Oracle Trace File Analyzer (TFA) Collector from
home location 'string'. Grid Infrastructure operations will continue.
Cause: The accompanying errors occurred while running the Oracle Trace File
Analyzer (TFA) Collector uninstall script.
Action: The Oracle Trace File Analyzer (TFA) Collector may not be available, but Grid
messages and retry using the command '<GI_Home>/tfa/bin/tfactl uninstall'. If the
problem persists, contact Oracle Support Services for further action.
CLSRSC-04009: Starting Oracle Trace File Analyzer (TFA) Collector.
Action: None
CLSRSC-04010: Successfully started Oracle Trace File Analyzer (TFA) Collector.
Action: None
CLSRSC-04011: Failed to start Oracle Trace File Analyzer (TFA) Collector. Grid
Cause: The Oracle Trace File Analyzer (TFA) Collector failed to start with the
Action: The Oracle Trace File Analyzer (TFA) Collector failing to start, but Grid
messages and retry using the command '<GI_Home>/tfa/bin/tfactl start'. If the
problem persists, contact Oracle Support Services for further action.
CLSRSC-04012: Shutting down Oracle Trace File Analyzer (TFA) Collector.
Action: None
CLSRSC-04013: Successfully shut down Oracle Trace File Analyzer (TFA)
Collector.
Action: None
CLSRSC-04014: Failed to shut down Oracle Trace File Analyzer (TFA) Collector.
Grid Infrastructure operations will continue.
Cause: The Oracle Trace File Analyzer (TFA) Collector did not shut down for
patching with the accompanying errors.
Action: A forcible stop will be issued so that patching can proceed, so no action is
required.
CLSRSC-04015: Performing install or upgrade action for Oracle Trace File Analyzer
(TFA) Collector.
Action: None
16
CLSS-00001 to CLSS-03202
CLSS-00001: skgxn not active
Cause: The skgxn service is required, but is not active
Action: Verify that the clusterware skgxn is active and restart it if necessary
CLSS-00002: unable to determine local node number. type string
Cause: Either the skgxn service is unavailable, or the OCR configuration is
incomplete/inaccurate.
Action: Verify that the clusterware skgxn is active and restart it if necessary.
Additionally validate that the clusterware installation was successful, and that the
local node was entered in the node listings.
CLSS-00003: unable to determine cluster name. type string
Cause: Name of the cluster cannot be determined from configuration.
Action: Verify that the clusterware installation was successful and that the OCR
registry is available.
CLSS-00004: unable to allocate memory resources
Cause: Memory allocation routines failed.
Action: Validate that the system has sufficient memory resources to use the product.
CLSS-00099: logfile open failed for string, err string
Cause: The log file could not be opened, with error type err
Action: Verify that the log directory specified during installation exists and that the
ocssd executable has permission to create a file in that directory
CLSS-00100: configuration data access failed for key string
Cause: Access of the configuration data indicated by key failed with error code error
Action: Verify that the clusterware installation was successful and that the OCR
registry is accessible
CLSS-00101: Oracle Cluster Repository mismatch with node string. (string != string)
Cause: A remote node is accessing a different set of configuration. This situation can
be caused by attempting to reinstall while there are active cluster nodes.
Action: Verify that the local and remote nodes are accessing the same Oracle Cluster
Repository.
CLSS-00102: initialization failure: [string] [string] [string] [string] [string] [string]
Cause: A general initialization failure occurred.
Action: Contact Oracle Customer Service for more information.
CLSS-00001 to CLSS-03202 16-1
CLSS-00103: unable to read configuration information for node string

Cause: Incomplete configuration information for the specified node was found.
Action: Validate the integrity of the Oracle Cluster Repository, restoring it from
backup if necessary.
CLSS-00200: local node string not listed in configuration
Cause: The OCR configuration information does not list this node as a member of the
cluster
Action: Verify that the clusterware installation was successful and that the node has
not been added since installation
CLSS-01200: skgxn errror: category string, operation string, loc string
Cause: The skgxn service encountered an error, the information in the error message
is vendor supplied diagnostic information
Action: Report this error to the vendor who supplied the skgxn
CLSS-02000: reconfiguration successful, incarnation string with string nodes
Cause: A rconfiguration has completed successfully
Action: None
CLSS-02001: local node number string, master node number string
Cause: Informational message regarding this incarnation
Action: None
CLSS-02200: Received node deletion request for active node string.
Cause: User attempted to delete a node from the configuration before shutting it
down.
Action: Shut down the specified node and retry the node deletion.
CLSS-02201: endpoint already in use: string
Cause: The specified endpoint is already in use. Another process is using the
endpoint.
Action: Shut down the other process, and retry the startup attempt.
CLSS-02202: voting device access took an excessive amount of time. (string sec)
Cause: A read or write to the voting device took an unacceptable amount of time.
Action: Contact the disk hardware vendor for information on improving the
availability of the disk.
CLSS-02203: unable to access voting device: string
Cause: The CSS daemon received a failure using the voting device.
Action: Examine the permissions on the voting device. If this failure occurred later
than boot time, then access to the voting device was lost.
CLSS-02204: voting device not configured. [string] [string]
Cause: A voting device was not supplied during configuration.
Action: The voting device assists in ensuring data integrity and is required by the CSS
daemon. Configure a voting device and restart the cluster.
16-2 Error Messages
CLSS-02205: remote node string signaled our eviction via voting device: cause
string
Cause: A remote node of the cluster evicted the local node due to network failure or
due to software failure in the local CSS daemon.
Action: Verify the stability of the private network between the local node and the
specified remote node.
CLSS-02206: local node evicted by vendor node monitor
Cause: The Operating System vendor's node monitor evicted the local node.
Action: Examine the vendor node monitor's logs for relevant information.
CLSS-02207: error string getting status from vendor node monitor
Cause: The CSS daemon received a failure interacting with the vendor node monitor.
The local node may have been evicted or the vendor node monitor may have been
shut down.
Action: Examine the vendor node monitor's logs for relevant information.
CLSS-03000: reconfiguration successful, incarnation string with string nodes
Cause: A rconfiguration has completed successfully
Action: None
CLSS-03001: local node number string, master node number string
Cause: Informational message regarding this incarnation
Action: None
CLSS-03200: timed out waiting on nested reconfiguration
Cause: The current reconfiguration hung. A network failure may have \ occurred.
Action: The local node will terminate itself to cause remote nodes to enter a nested
reconfiguration. This may allow the cluster to continue operation.
CLSS-03201: An attempt to begin a nested reconfiguration failed.
Cause: unable to cancel previous reconfiguration to begin a new one
Action: None
CLSS-03202: out of sync with master: [string] [string] [string] [string]
Cause: Consistency checks between the local node and the master failed.
Action: The local daemon will terminate itself to ensure that the surviving cluster is
all properly coordinated.
CLSS-00001 to CLSS-03202 16-3
16-4 Error Messages
17
CLST-01101 to CLST-03203
CLST-01101: assigning default private interconnect name string for node string
Cause: A private interconnect name was not specified. The node name was used as a
default instead.
Action: Verify that the node name refers to IP addresses on the private interconnect.
Using a non-private network can cause performance and stability issues.
CLST-01102: assigning default host name string for node string
Cause: A host name for the node was not specified. The node name was used as a
default instead.
Action: If the node name is not equal to the host name, the host name must be
supplied to clscfg. Failure to do so will cause the Cluster Ready Services daemons not
to function.
CLST-01103: existing configuration version (string) detected
Cause: An existing configuration was detected.
Action: Informational message only. No action is required. clscfg will not modify the
existing configuration unless explicitly requested with the -force flag.
CLST-01104: successfully determined required configuration for all components
Cause: clscfg was able to determine the proper configuration requirements.
Action: Informational message only. No action is required. clscfg will attempt to write
the configuration next.
CLST-01105: An existing configuration was detected. It was not overwritten.
Cause: An existing configuration was detected, and clscfg chose not to overwrite it.
Action: This message may be ignored if it is seen as part of starting any node other
than the first one. The -force option can be used to override this decision, but if it is
used when there are active cluster members, failure CLSS-0101 and data integrity
issues are likely.
CLST-01301: successfully deleted string of string configuration values
Cause: clscfg completed a portion of the delete operation.
Action: Informational message only. No action is required. If some of the values were
not deleted, another error message should be visible with more information.
CLST-01302: successfully deleted string of string configuration keys
Cause: clscfg completed a portion of the delete operation.
Action: Informational message only. No action is required. If some of the keys were
not deleted, another error message should be visible with more information.
CLST-01101 to CLST-03203 17-1
CLST-01303: successfully rolled back delete operation

Cause: The delete node operation failed, but the configuration was properly restored
to its original state.
Action: Informational message only. No action is required.
CLST-01304: node deletion successful
Cause: The delete node operation succeeded.
CLST-01401: formatting voting device: string
Cause: clscfg started formatting the voting device.
CLST-01501: tried to delete key string but it was not there
Cause: clscfg attempted to delete a key as part of a delete operation, but it had already
been deleted.
Action: Informational message only. No action is required. This might be an
indication of corrupted configuration, or a previous delete operation that did not
complete.
CLST-01901: configuring TCP ports string, string, string, and string
Cause: The specified ports were configured for use with the Cluster Ready Services
Daemons.
Action: Informational message only. No action is required. To change the ports used,
specify 4 alternate ports with "-t". Example: -t 1001,1002,1003,1004
CLST-01902: configuring node: node number string, node name string
Cause: This node configuration was requested.
Action: Informational message only. No action is required. To alter the list of nodes
re-run the install and specify a different set of nodes, or make use of the add and
delete node install options after the current install is complete.
CLST-01903: configuring node: host name string, private interconnect name string
Cause: This node configuration was requested.
Action: Informational message only. No action is required. To alter the list of nodes
re-run the install and specify a different set of nodes, or make use of the add and
delete node install options after the current install is complete.
CLST-01904: creating configuration with user (string) and group (string)
Cause: The configuration was set up with the specified user and group.
Action: Informational message only. No action is required. Some configuration
information will only be accessible to members of the specified group. Note: On
Windows platforms the group may be blank.
CLST-01999: Warning: -force specified. Overwriting existing configuration.
Cause: The -force parameter was supplied.
Action: The -force parameter will cause clscfg to overwrite the existing configuration.
If used while a Cluster Ready Services cluster is actively running, this can cause
instability and data integrity exposures.
17-2 Error Messages
CLST-02101: Too many nodes were specified. limit is string

Cause: Too many nodes were specified on command line.
Action: Retry the operation with a smaller number of simultaneous changes.
CLST-02102: Node string specified is out of range. Maximum node number is
string.
Cause: A node was specified with node number out of range.
Action: Retry the operation with a smaller node number.
CLST-02103: Unable to parse TCP port options specified.
Cause: Arguments to the -t flag were not valid port numbers, or some number other
than 4 ports were supplied.
Action: Correct the arguments to the -t flag and rerun the operation.
CLST-02104: TCP port string is out of bounds.
Cause: The TCP port specified was not a valid port number.
Action: Specify an another port. Usually TCP ports need to be between 1001 and
65,535.
CLST-02105: missing required parameter -l with language ID information
Cause: The -l parameter was required for the requested operation.
Action: Supply the -l parameter with the proper language ID.
CLST-02106: missing required parameter -o with path to ORA_CRS_HOME
Cause: The -o parameter was required for the requested operation.
Action: Supply the -o parameter with the proper path.
CLST-02107: failure configuring component string
Cause: The Oracle Cluster Repository configuration for the specified component was
unsuccessful.
Action: Look for other error information and contact Oracle support.
CLST-02108: missing required parameter -q with path to the voting device
Cause: The -q parameter was required for the requested operation.
Action: Supply the -q parameter with a valid path for the voting device.
CLST-02109: missing required parameter -c with a cluster name
Cause: The -c parameter was required for the requested operation.
Action: Supply the -c parameter with a name for the cluster.
CLST-02110: missing required parameter -nn with the list of nodenames
Cause: The -nn parameter was required for the requested operation.
Action: Supply a list of node names with the format:
nodenameA,nodenumA,nodenameB,nodenumB,...
CLST-02201: node string already exists in the configuration with node number
string
Cause: A node name specified for the add node operation conflicted with the existing
configuration.
Action: Choose an alternate node to add to the cluster, or give the new node a unique
name, or delete the previous node, then retry.
CLST-01101 to CLST-03203 17-3
CLST-02202: private interconnect name string is already assigned to node number

string
Cause: The private interconnect name specified for the add node operation conflicted
with the existing configuration.
CLST-02203: Host name string is already assigned to node number string.
Cause: The host name specified for the add node operation conflicted with the
existing configuration.
CLST-02204: Node number string is already assigned to node string.
Cause: The node number specified for the add node operation conflicted with the
existing configuration.
Action: Chose an alternate node to add to the cluster, or give the new node a unique
node number, or delete the previous node, then retry.
CLST-02301: failure string validating configuration of node string
Cause: clscfg was unable to validate existing configuration of the specified node.
Action: Validate the integrity of the Cluster Ready Services install on the local node,
or choose another node to delete.
CLST-02302: failure string validating configuration of private interconnect name
string
CLST-02303: failure string validating configuration of node with host name string
CLST-02304: node name string for node string does not match existing node name
string
Cause: The node name specified in a delete operation did not match the existing
configuration.
Action: Specify the correct information describing the node you intend to delete, then
retry.
CLST-02305: node number string for node string does not match existing node
number string
Cause: The node number specified in a delete operation did not match the existing
configuration.
retry.
17-4 Error Messages
CLST-02306: private interconnect name string for node string does not match string
Cause: The private interconnect name specified in a delete operation did not match
the existing configuration.
retry.
CLST-02307: host name string for node string does not match existing host name
string
Cause: The host name specified in a delete operation did not match the existing
configuration.
retry.
CLST-02308: concurrent node deletion suspected when deleting key string
Cause: A key being deleted by the current operation was deleted by another process
during the small amount of time between opening it for deletion and actually deleting
it. An attempt to execute multiple separate delete operations may have occurred, and
may have corrupted the configuration.
Action: Verify the integrity of the Oracle Cluster Repository, and restore from backup
if necessary. If only one clscfg process was active on the cluster this may be ignored.
CLST-02309: failure updating the configuration in node deletion
Cause: clscfg was unable to modify the existing configuration for node deletion. The
existing configuration was probably not harmed.
Action: Verify the integrity of the Cluster Ready Services install on the local node, and
retry.
CLST-02310: CSS daemon refused node deletion, status string. attempting rollback
Cause: Cluster Synchronization Services daemon refused the node deletion.
Action: One or more of the designated nodes may still be active. clscfg will now
attempt to roll back the deletion process. The Cluster Ready Services daemons must
be shut down on a node before any attempt to remove them from the configuration.
More information on why the attempt was refused may be available in the Cluster
Synchronization Service logfile.
CLST-02311: failure rolling back node deletion. configuration irrecoverable
Cause: clscfg attempted to roll back the deletion process after a failure and was
unable to do so. Configuration was partially deleted and left in an inconsistent state.
Action: Shut down the cluster and restore the Oracle Cluster Repository from backup.
CLST-02312: failed to completely delete node configuration
Cause: The node deletion was mostly successful, and should be functional in this
state. Some portions of the configuration were not successfully deleted.
Action: This can be ignored. The safer choice is to restore the Oracle Cluster
Repository from backup, and attempt the delete again. Adding any of the deleted
nodes back to the configuration in the future may fail if this is ignored.
CLST-02401: failure string querying maximum configurable node number
Cause: clscfg was unable to determine the legitimate range of node numbers.
Action: Verify the integrity of the Cluster Ready Services install on the local node.
CLST-01101 to CLST-03203 17-5
CLST-02402: failure string querying existing configured node list

Cause: clscfg was unable to retrieve the list of currently configured nodes.
CLST-02403: failure string querying the maximum node name size
Cause: clscfg was unable to determine the size of the largest node name.
CLST-02404: failure string querying the cluster name
Cause: clscfg was unable to determine the existing cluster name.
CLST-02405: failure formatting voting device (string) at [string] [string] [string]
Cause: clscfg failed to format the voting device.
Action: Verify the path and permissions set on the voting device.
CLST-02501: failure string opening configuration for write operation
Cause: clscfg was attempting to open the current configuration for write access.
Action: Verify the integrity of the Oracle Cluster Repository. Shut down the cluster
and restore OCR from backup if necessary.
CLST-02502: failure string writing new configuration
Cause: clscfg was attempting to write new configuration data.
CLST-02503: failure string opening configuration for delete operation
Cause: clscfg received an error while attempting to delete part of the existing
configuration.
CLST-02504: failure string writing configuration to disk
Cause: clscfg received a failure writing information to the Oracle Cluster Repository.
Action: Verify the settings for the Oracle Cluster Repository and retry.
CLST-02901: The number of Oracle Cluster Repository keys exceeds limit of string.
Cause: clscfg ran out of internal space for keys during install.
Action: Re-run the install and specify a smaller list of nodes. When that completes,
use the add node option to add the remaining nodes.
CLST-02902: The number of Oracle Cluster Repository keys exceeds limit of string.
Cause: clscfg ran out of internal space for keys during delete node.
Action: Re-run the delete node operation and delete fewer nodes at once.
CLST-02903: unable to allocate string bytes of memory at location: string
Cause: clscfg was unable to allocate enough memory to service the request.
Action: Ensure that the specified amount of memory will be available and retry the
operation.
17-6 Error Messages
CLST-02904: failure string in SCLS API at string

Cause: clscfg was unable to query for information about the system setup.
Action: Contact Oracle support with the additional information printed just after this
message.
CLST-02905: add, install, delete, concepts, and local are mutually exclusive
Cause: clscfg was run with two different mode flags. All mode flags are mutually
exclusive.
Action: Correct the command line and try again.
CLST-02906: Clustername should be between 1 and string letters.
Cause: cluster name supplied with -c argument was the wrong size.
Action: Supply an alternate cluster name of an appropriate length.
CLST-02907: unknown parameter string supplied
Cause: An unknown parameter was passed to clscfg.
Action: Use "clscfg -help" or "clscfg -concepts" for more information.
CLST-02908: unable to determine local hostname
Cause: clscfg was unable to determine the local hostname.
Action: Verify the operating system host name configuration.
CLST-02909: The requested operation requires High Availability privileges.
Cause: The current user did not have High Availability privileges.
Action: Log in as a different user and retry the operation.
CLST-02910: Failure string contacting the CRS daemon.
Cause: clscfg was unable to communicate with the CRS daemon.
Action: The requested operation must be performed from an active cluster node.
Validate the pre-existing installation on the local machine, or perform the operation
from another node.
CLST-02911: failure string contacting the CSS daemon
Cause: clscfg was unable to communicate with the CSS daemon.
Action: The requested operation must be performed from an active cluster node.
Validate the pre-existing installation on the local machine, or perform the operation
from another node.
CLST-02999: Untranslated failure: [string] [string] [string] [string] [string] [string]
Cause: A failure with no translation occurred.
Action: Contact Oracle Customer Support for more information.
CLST-03100: See the documentation for usage information.
Cause: Incorrect or insufficient arguments were passed to crsuser.
Action: Read documentation for instructions on how to use this tool.
CLST-03101: Enter the password for user string.
Cause: crsuser requires the password to register the user.
Action: Enter the requested password.
CLST-01101 to CLST-03203 17-7
CLST-03102: Operation successful.

Cause: The operation succeeded.
Action: None
CLST-03200: internal error: [string] [string] [string] [string] [string]
Cause: A failure with no translation occurred.
Action: Contact Oracle Customer support for more information.
CLST-03201: unexpected argument: string
Cause: crsuser failed to parse the arguments, or an unknown argument was passed.
Action: Supply the correct arguments and try again.
CLST-03202: Memory allocation failure for string bytes.
Cause: crsuser was unable to allocate memory.
Action: Free up some system memory and try again.
CLST-03203: insufficient privileges for action: string
Cause: The current user did not have sufficient privileges.
Action: Log in as another user and try again.
17-8 Error Messages
18
CLSU-00100 to CLSU-00912
CLSU-00100: operating system function: string failed with error data: string
Cause: A call to an Operating System dependent service or function returned an error
indication. The message includes the name of the function and the returned error
data. The latter varies by platform but typically is numeric; on most platforms it is the
value of C "errno" after the failing call.
Action: This error normally is accompanied by other (higher-level) messages
describing the operation that is affected by the failure. It may also include one or
more of messages 101, 103, and 104 providing additional error details. All of the
messages should be examined to assess the error, which may have a very ordinary
cause and correction, such as an input file failing to open because the supplied name
was misspelled.
CLSU-00101: operating system error message: string
Cause: This message accompanies message 100 above when the Operating System
dependent error data can be converted into a text message. On most Oracle platforms
the message is a text representation of the C "errno" value reported in message 100.
Action: See message 100.
CLSU-00102: operating system interface detected an error
Cause: This message is issued instead of messages 100-101 when a "logical" error
condition (rather than failure of an Operating System function call) is detected at an
Operating System specific interface. The error condition is further described by
accompanying message(s), including 103 and 104.
Action: This error normally is accompanied by other (higher-level) messages
describing the operation that is affected by the failure. In most cases it will also
include messages 103 and 104, providing additional details about the error. All of the
messages should be examined to assess the error, which may have a very ordinary
cause and correction, such as a missing required environment variable.
CLSU-00103: error location: string
Cause: This message accompanies message 100, 102, or 105 and identifies a location in
Oracle program code that encountered the error.
Action: See message 100, 102, or 105. This information normally is useful only when
reporting the error condition to Oracle as a potential code bug.
CLSU-00104: additional error information: string
Cause: This message accompanies message 100, 102, or 105 and supplies additional
information related to the error condition. A single error may include multiple lines
of additional information.
Action: See message 100, 102, or 105.
CLSU-00100 to CLSU-00912 18-1
CLSU-00105: operating system interface has reported an internal failure

Cause: This message indicates that an Operating System dependent interface within
Oracle code has detected internal corruption or some other evidence of internal
program failure.
Action: This message may be accompanied by other (higher-level) messages
indicating the product operation that was affected by the failure. It may also be
accompanied by either or both of messages 103 and 104. All situations reporting this
condition should be referred to Oracle Support for resolution.
CLSU-00106: An improper operating system error display was attempted
Cause: During processing of an error condition, an attempt was made to format or
display Operating System dependent error data, but the error data structure was
found to indicate "no error".
Action: This error should be reported to Oracle Support for resolution.
CLSU-00200: **** Error stack contains number records, newest first:\n
Cause: The collection of errors about to be presented contains this many following
records.
Action: This and the following data should be reported to Oracle Support for
resolution.
CLSU-00201: **** Error stack end ****\n
Cause: This marks the end of a collection of errors
Action: The preceding data should be reported to Oracle Support for resolution.
CLSU-00220: clsem FATAL exception: string
Cause: Something unrecoverable happened in CLSEM.
Action: Report to Oracle Support.
CLSU-00221: ERROR printed by clsecho: string
Cause: An error printed by clsecho
CLSU-00222: WARNING printed by clsecho: string
Cause: A warning
Action: Note the text
CLSU-00223: Info printed by clsecho: string
Cause: Information printed by clsecho
CLSU-00910: Named exception string string string string
Cause: Program raised an exception that does not have its own message
CLSU-00911: Signal string received
Cause: Program received on OS signal reported as an exception
Action: Report to Oracle Support
CLSU-00912: Operating system error: string
Cause: One or more operating system-specific errors were noticed
18-2 Error Messages
Action: Examine the message(s) for more information.
CLSU-00100 to CLSU-00912 18-3
18-4 Error Messages
19
CLSW-00001 to CLSW-01000
CLSW-00001: Cluster Wallet operation failed
Cause: This is generic internal error for Cluster Wallet.
CLSW-00002: Out of heap memory.
Cause: The program ran out of heap memory.
Action: Retry the operation when more memory is available.
CLSW-00003: Error in the cluster registry (OCR) layer. [number] [string]
Cause: An error occurred in the cluster registry layer while performing a cluster
wallet operation.
Action: Ensure correct operation of cluster registry by inspecting ocr error (oerr proc
ocrerror), by using ocrcheck and ocrdump, and retry the operation.
CLSW-00004: Error in the network security layer. [number] [string]
Cause: An error occurred in the network security layer while performing a cluster
wallet operation.
Action: Inspect the network security error (oerr ora nzerr), and take corrective action
to ensure correct operation.
CLSW-00005: Cannot perform cluster wallet operation because one of the
parameters is NULL.
Cause: Program tried a cluster wallet operation using a NULL parameter.
Action: Check the parameters, and retry the operation.
CLSW-00006: Cannot perform cluster wallet operation because the context is
invalid.
Cause: The cluster wallet context passed was invalid.
Action: Intialize the cluster wallet and retry the operation.
CLSW-00007: Cannot perform cluster wallet operation because one of the
parameters is invalid. [number] [string]
Cause: Program tried a cluster wallet operation using an invalid parameter.
Action: Check the parameters, and retry the operation.
CLSW-00008: The cluster wallet to be created already exists.
Cause: The program tried to create a cluster wallet that already exists.
Action: Retry the operation after unsetting the CLSW_FLAGS_WALLET_CREATE
CLSW-00001 to CLSW-01000 19-1
CLSW-00009: The cluster wallet to be operated on does not exist.

Cause: Program tried to access a cluster wallet which does not exist.
Action: Check to see if the cluster wallet exists and try the operation
CLSW-00010: Error in the NLS services.
Cause: An error occurred in the NLS services while performing a cluster wallet
operation.
Action: Check to see if the message file exists in $ORACLE_HOME/has/mesg/
clsw*.msb
CLSW-00011: Cannot perform cluster wallet operation because data stored in the
registry is invalid.
Cause: The data stored in the registry cannot be converted to a wallet.
Action: Delete the registry key associated with the wallet and recreate the wallet.
CLSW-00012: User is not authorized to perform the cluster wallet operation.
[number] [string]
Cause: Program tried an operation on a cluster wallet for which it does not have
permission.
Action: Check to see if program is run as the correct user.
CLSW-00013: Error in the clusterware operating system (SCLS) services. [string]
Cause: An error occurred in the SCLS services while performing a cluster wallet
operation.
Action: Check to see if NIS/LDAP on Unix and Active Directory Service on Windows
has been correctly configured.
CLSW-00014: Wallet type 'string' is not supported on this operating system.
Cause: The program tried a cluster wallet operation using a wallet type that is not
supported on current operating system.
Action: This is an internal error. Contact oracle support services.
CLSW-00015: Alias 'string' already exists in wallet type 'string'.
Cause: A request to add the specified alias to the wallet failed because the alias
already existed in the wallet.
Action: Add an alias that does not already exist in the wallet. The password for an
alias that already exists can be modified using the command 'crsctl modify wallet'.
CLSW-00016: Alias 'string' was not found in wallet type 'string'.
Cause: A request to modify the specified alias in the wallet failed because the alias did
not exist in the wallet.
Action: Ensure that the alias exists in the wallet type specified. A new alias can be
added to a wallet type using the command 'crsctl add wallet'.
CLSW-01000: Enter Password:
Cause: This is a prompt to user to enter password.
Action: Enter password.
19-2 Error Messages
20
CRS-00001 to CRS-29006
CRS-00001: Message ID string-number not found.
Cause: The messsage for the given message id is not found in any language.
Action: Make sure the product is setup correctly on the system.
CRS-00002: string:Internal list corruption. trace file: "string"
Cause: An internal error was detected during trace file flush processing.
CRS-00003: An error occurred while attempting to open file "string". Additional
diagnostics: string
Cause: An error was encountered while attempting to open the specified file.
Action: Examine the additional diagnostics, if available, and attempt to correct any
file system environmental problems if indicated. Otherwise, contact Oracle Support
Services.
CRS-00004: logging terminated for the process. log file: "string"
Cause: One or more file system errors were encountered which caused logging to be
terminated for this process.
Action: Examine preceding Alert log messages for details on the error or errors that
occurred. Restart the process to reenable logging.
CRS-00005: file "string" deleted after close failure
Cause: This message is informational. An attempt to close the specified file failed. The
contents of the file after a close error are undefined. The file has been successfully
deleted. Log data are lost.
Action: None
CRS-00006: file rotation processing continues for file: "string"
Cause: This message is informational and indicates only that a preceding error was
not sufficiently severe to terminate file rotation which might otherwise be the case.
Action: None
CRS-00007: failed to open new log file "string\
Cause: The file system encountered an error while attempting to open the specified
file during log file rotation. Log data are lost.
Action: Review the preceding Alert log message CRS-0011 and attempt to resolve any
file system environmental problems indicated. Otherwise, contact Oracle Support
Services.
CRS-00008: opened new file "string" after close failure
Cause: This message is informational. Log data are lost.
CRS-00001 to CRS-29006 20-1
Action: None
CRS-00009: file "string" reopened
Cause: An error was encountered during rotation processing so that file rotation
could not proceed. The original file, which had been closed, was successfully
reopened.
Action: Review Alert log messages that precede this message that identify the file
system error or errors encountered. If the additional diagnostic data in a preceding
alert log message indicate a file system environmental problem, attempt to correct it.
Otherwise contact Oracle Support Services.
CRS-00011: An error occurred while attempting to close file "string" during file
rotation. Additional diagnostics: string
Cause: An error was encountered when attempting to close the specified file.
Action: Examine the additional diagnostics, if any, and attempt to correct any file
system environmental problems if indicated. Otherwise, contact Oracle Support
Services.
CRS-00012: An error occurred while attempting to rename file "string" to "string"
during file rotation. Additional diagnostics: string
Cause: An error was encountered when attempting to rename the source file to the
destination file.
Services.
CRS-00013: An error occurred while attempting to check for the existence of file
"string" during file rotation. Additional diagnostics: string
Cause: An error was encountered while attempting to determine if the specified file
existed.
Services.
CRS-00014: An error occurred while attempting to delete file "string" during file
Cause: An error was encountered while attempting to delete the specified file.
Services.
CRS-00015: An error occurred while attempting to flush file "string" during file
Cause: An error was encountered while an attempting to flush the specified file.
Services.
CRS-00016: An error occurred while attempting to free the file name object for file
Cause: An error was encountered while attempting to free the file name object for the
specified file.
20-2 Error Messages
Services.
CRS-00017: An error occurred while attempting to create a file name object for file
Cause: An error was encountered while attempting to create a file name object for the
specified file.
Services.
CRS-00018: An error occurred while attempting to reopen file "string" during file
Cause: An error was encountered while attempting to reopen the specified file.
Services.
CRS-00019: Log file rotation terminated. log file: "string"
Cause: One or more file system errors were encountered which caused log file
rotation to be terminated for the process. Although log file rotation has been
terminated, logging continues.
Action: Review Alert log messages that precede this alert log message that identify
the file system error or errors encountered. If the additional diagnostic data in a
preceding alert log message indicate a file system environmental problem, attempt to
correct it. Otherwise contact Oracle Support Services. To reenable file rotation the
process must be restarted.
"string" during file open processing. Additional diagnostics: string
specified file.
Services.
CRS-00021: An error occurred while attempting to check for the existence of file
Cause: An error was encountered while attempting to determine if the specified file
existed.
Services.
CRS-00022: An error occurred while attempting to change access permissions and
privileges for file "string" during file open processing. Additional diagnostics:
string
Cause: An error was encountered while attempting to change access permissions and
privileges for the specified file.
Services.
CRS-00001 to CRS-29006 20-3
CRS-00023: An error occurred while attempting to create default permissions for

file "string" during file open processing. Additional diagnostics: string
Cause: An error was encountered while attempting to create default file permissions
for the specified file.
Services.
specified file.
Services.
CRS-00025: An error occurred while attempting to create a file object for file
Cause: An error was encountered while attempting to create a file object for the
specified file.
Services.
CRS-00026: failed to create one or more file name objects to rename "string" to
"string" during file rotation processing
Cause: An error was encountered while attempting to create one of more file name
objects for the specified files.
CRS-00027: An error occurred while attempting to determine the size of file "string"
during file open processing. Additional diagnostics: string
Cause: An error was encountered while attempting to determine the size of the
specified file.
Services.
CRS-00028: An error occurred while attempting to write the banner for file "string".
Additional diagnostics: string
Cause: An error was encountered while attempting to write the banner record to the
specified file.
Services.
CRS-00029: An error occurred while attempting to flush file "string" after the
banner record was written. Additional diagnostics: string
Cause: An error was encountered while attempting to flush the specified file after
writing the banner record.
20-4 Error Messages
Services.
CRS-00030: An invalid file type was encountered while attempting to perform file
synchronization. Additional diagnostics: string ftype: number
Cause: An invalid file type specification was encountered by file synchronization
services.
CRS-00031: An error occurred while attempting to flush file "string" during file
synchronization processing. Additional diagnostics: string
Cause: An error was encountered while attempting to flush the specified file during
file synchronization processing.
Services.
"string" during generate-file-name processing. Additional diagnostics: string
specified file.
Services.
"string" during generate-file-name processing. Additional diagnostics: string
specified file.
Services.
CRS-00034: An error occurred while attempting to open file "string" during
generate-file-name processing. Additional diagnostics: string
Services.
CRS-00035: An invalid pointer to an internal control structure was encountered
while attempting to open a log file. Additional diagnostics: string
Cause: An invalid pointer was encountered when attempting to open a file. Logging
is disabled for the process.
CRS-00036: An error occurred while attempting to open file "string".
Action: Review preceding Alert log messages and attempt to resolve any file system
environmental problems indicated. Otherwise, contact Oracle Support Services
CRS-00001 to CRS-29006 20-5
CRS-00037: An error occurred while attempting to write to file "string". Additional

diagnostics: string
Cause: An error was encountered while attempting to write to the specified file.
Logging is disabled for the process.
CRS-00038: An invalid pointer to an internal control structure was encountered
while attempting to open a trace file. Additional diagnostics: string
Cause: An invalid pointer was encountered when attempting to open a trace file.
Tracing is disabled for the process.
CRS-00039: An error occurred while attempting to open trace file "string".
Cause: An error was encountered while attempting to open the specified file. Tracing
is disabled for the process.
CRS-00040: Trace logging terminated for the process. trace file: "string"
Cause: One or more file system errors were encountered which caused tracing to be
terminated for this process.
Action: Examine preceding Alert log messages for details on the error or errors that
occurred. Restart the process to reenable logging.
CRS-00041: Trace file rotation terminated for the process. Trace file: "string"
Cause: One or more file system errors were encountered which caused trace file
rotation to be terminated for the process. Although trace file rotation has been
terminated, tracing continues.
Action: Review Alert log messages that precede this alert log message that identify
the file system error or errors encountered. If the additional diagnostic data in a
preceding alert log message indicate a file system environmental problem, attempt to
correct it. Otherwise contact Oracle Support Services. To reenable trace file rotation
the process must be restarted.
CRS-00184: Cannot communicate with the CRS daemon.
Cause: The CRS daemon on the local node is either not running or there was an
internal communication error with the CRS daemon.
Action: Check if the CRS daemon process is running on the local node.
CRS-00210: Could not find resource 'string'.
Cause: An attempt was made to operate on a resource that is not registered.
Action: Ensure that the resource name is specified correctly using the command 'crsctl
status resource'.
CRS-00211: Resource 'string' has already been registered.
Cause: An attempt was made to register a resource that is already registered.
Action: Ensure that the resource name is specified correctly and retry the command.
CRS-00213: Could not register resource 'string'.
Cause: There was an internal error while registering the resource.
20-6 Error Messages
Action: Check the CRS daemon log file.

CRS-00214: Could not unregister resource 'string'.
Cause: There was an internal error while unregistering the resource.
CRS-00215: Could not start resource 'string'.
Cause: There was an internal error while starting the resource.
CRS-00216: Could not stop resource 'string'.
Cause: There was an internal error while stopping the resource.
CRS-00217: Could not relocate resource 'string'.
Cause: There was an internal error while relocating the resource.
CRS-00218: Could not restart the resource 'string' on the original node.
Cause: There was an internal error while restarting the resource.
CRS-00219: Could not update resource 'string'.
Cause: There was an internal error while updating the resource.
CRS-00220: Resource 'string' has invalid resource profile.
Cause: Invalid attributes in the resource profile.
Action: Run the command 'crsctl status type' to identify the invalid attributes. Modify
these attributes using the command 'crsctl modify type'.
CRS-00221: Resource 'string''s action script cannot be found.
Cause: The action script has been deleted from the file system.
Action: Run 'crsctl status resource -p' to determine the action script location, and
check for its existence.
CRS-00223: Resource 'string' has placement error.
Cause: Based on the placement policy for the resource, there was no available host to
which the resourse could failover or start.
Action: Check the target host for the resource and restart the resource using the 'crsctl
start resource' command.
CRS-00230: Member 'string' is not in the cluster.
Cause: The hostname was not found in the cluster.
Action: Check the hostnames in the cluster.
CRS-00232: Cluster member is down. Cannot perform operation.
Cause: The node on which CRS is attempting to start the resource is down.
Action: Start the node and retry the operation.
CRS-00001 to CRS-29006 20-7
CRS-00233: Resource or relatives are currently involved with another operation.\n

Cause: Another CRS daemon was operating on the same resource.
Action: Wait for a minute and try the command or operation again.
CRS-00253: CRS configuration error, the CRS default directory is not set in Oracle
Cluster Registry.
Cause: The Oracle Cluster Registry key which contains the user default CRS key is not
initialised.
Action: Check the CRS configuration. If necessary reinstall CRS.
CRS-00254: authorization failure
Cause: The user permissions were insufficient to operate on the resource.
Action: Check the permissions associated with the resource using 'crsctl getperm
resource' and set the appropriate user permissions using 'crsctl setperm resource'.
CRS-00255: CRSD is not running in privileged mode. Insufficient permissions to
run this command.
Cause: The CRS daemon was not running as the privileged user.
Action: Check if the CRS daemon is running as root (UNIX) or Administrator
(Windows).
CRS-00256: Username conflicts with the owner of the resource.
Cause: An attempt was made to give separate user level permissions for the owner of
the resource.
Action: Check the owner of the resource and the user being given permissions.
CRS-00257: Groupname conflicts with the primary group of the resource.
Cause: An attempt was made to give separate group level permissions for the
primary group of the resource.
Action: Check the primary group of the resource and the group being given
permissions.
CRS-00258: Invalid ACL string format.
Cause: An invalid permission string (ACL) was supplied.
Action: Check the syntax of the permission string (ACL).
CRS-00259: Owner of the resource does not belong to the group.
Cause: The owner of the resource does not belong to the expected group.
Action: If this resource is owned by the root user, check if the root user belongs to the
dba group.
CRS-00271: CRSD shutdown is already in progress.\n
Cause: crsctl stop command is issued before waiting for a prior stop command to
finish.
Action: Wait for the currently running shutdown command to complete before
issuing subsequent command.
CRS-00272: This command remains for backward compatibility only
Action: For all new use cases, use the replacement.
20-8 Error Messages
CRS-00273: This command is deprecated and has been replaced by 'string'

CRS-00274: This command is deprecated and its functionality incorporated into
'string'
CRS-00275: This command is not supported in Oracle Restart environment.
Cause: One of the "crs_" commands was issued in an Oracle Restart environment.
Action: Use the corresponding crsctl command.
CRS-00402: Could not make safe directory('string')
Cause: Unable to create safe directory.
Action: Check if you have proper permissions and sufficient space on the disk to
create the directory.
CRS-00403: Could not change working directory to safe directory('string')
Cause: Unable to change directory to safe directory.
Action: Check if safe directory exists and if you have proper permissions.
CRS-00406: Could not create lock directory ('string')
Cause: Unable to create lock directory.
Action: Check if you have proper permissions and sufficient space on the disk to
create the directory.
CRS-00407: Another CRSD may be running, could not obtain lock file 'string'.
Cause: Unable to obtain lock file as another CRSD may be running.
Action: Stop the existing CRSD before attempting to start CRSD again.
CRS-00413: Could not initialize the Cluster Synchronization Services context
Cause: Unable to communicate with the cluster services.
Action: Verify that the Cluster Synchronization Services Daemon is properly
configured and is running.
CRS-00414: Could not establish Event Manager connection
Cause: Unable to communicate with Event Manager daemon.
Action: Run the 'crsctl check evmd' command to determine whether Event Manager
daemon is properly configured and is running.
CRS-00451: CRS configuration error, unable to initialize Oracle Cluster Registry.
Cause: The Oracle Cluster Registry that contains information about the CRS
configuration is unavailable.
Action: Check the OCR configuration using the ocrcheck utility and resolve any
issues it reports. If the problem persists, contact Oracle Support Services.
CRS-00452: CRS configuration error, unable to find CRSD Connection Information
in Oracle Cluster Registry.
Cause: The Oracle Cluster Registry key which contains the user default CRSD
connection is not initialized.
CRS-00001 to CRS-29006 20-9
CRS-00453: CRS configuration error, unable to find Instance Information in Oracle
Cluster Registry.
Cause: The Oracle Cluster Registry key which contains the Instance's information is
not initialized.
CRS-00471: Node number is not found
Cause: Cluster Synchronization Services is unable to retrieve the node name.
Action: Verify your cluster installation, including any vendor cluster ware. If
necessary reinstall the cluster.
CRS-00472: Node name is not found
Cause: Cluster Services is unable to retrieve the node name.
Action: Verify your cluster installation, including any vendor cluster ware. If
necessary reinstall the cluster.
CRS-00602: Encountered operating system error 'string' while authenticating user
'string'. Details at string in string.
Cause: The operating system experienced an error when Clusterware authenticated
the specified user.
Action: Verify that the authentication service in your environment is functioning
correctly. If the problem persists, contact Oracle Support Services.
CRS-00700: Oracle High Availability Service aborted due to failure to allocate
memory. Details at string in string.
Cause: Memory allocation failed.
Action: Restart Cluster Ready Service using 'crsctl stop crs -f' followed by 'crsctl start
crs'. If the problem persists, contact Oracle Support Services.
CRS-00701: Oracle High Availability Service aborted due to failure to obtain
identity of the running process. Details at string in string.
Cause: Failed to retrieve user id.
Action: Check <crs_home> owner and restart Cluster Ready Service using 'crsctl stop
crs -f' followed by 'crsctl start crs'. If the problem persists, contact Oracle Support
Services.
CRS-00702: Oracle High Availability Service aborted due to failure to run as
privileged user. Details at string in string.
Cause: Oracle High Availability Service was not running as privileged user.
Action: On Unix, restart Cluster Ready Service as privileged user using 'crsctl stop crs
-f' followed by 'crsctl start crs'. On Windows, check the privileges of the Oracle High
Availability Service and restart Cluster Ready Service using 'crsctl stop crs -f'
followed by 'crsctl start crs' If the problem persists, contact Oracle Support Services.
CRS-00703: Oracle High Availability Service aborted due to failure to initialize the
communication context. Details at string in string.
Cause: The network layer initialization failed.
CRS-00704: Oracle High Availability Service aborted due to Oracle Local Registry
error [string]. Details at string in string.
Cause: Oracle Local Registry aborted with an error. Look at the associated error
message to determine the underlying issue.
Action: Solve the underlying issue and restart Cluster Ready Service using 'crsctl stop
Services.
CRS-00708: Oracle High Availability Service aborted due to failure to retrieve
ORA_CRS_HOME environment variable. Details at string in string.
Cause: An environment variable required by Oracle High Availability Service failed
to be set at initialization.
Action: Run 'rootcrs.pl -unlock' followed by 'rootcrs.pl -patch' and restart Cluster
Ready Service using 'crsctl stop crs -f' followed by 'crsctl start crs'. If the problem
CRS-00709: Oracle High Availability Service aborted due to failure to initialize
ORA_CRS_HOME path. Details at string in string.
Cause: Oracle High Availability Service ORA_CRS_HOME path could not be
initialized.
Action: Check for execute permissions on the Grid Infrastructure home or
<crs_home> and restart Cluster Ready Service using 'crsctl stop crs -f' followed by
'crsctl start crs'. If the problem persists, contact Oracle Support Services.
CRS-00712: Oracle High Availability Service aborted due to failure to initialize the
network layer with error [number]. Details at string in string.
CRS-00713: An error occurred initializing the Reboot Advisory Monitor: error code
[number]. Details at string in string.
Cause: An error occurred initializing the Reboot Advisory Monitor component of
Oracle High Availability Service. This error is not fatal; Oracle High Availability
Service processing continues.
Action: Examine the Clusterware alert log for messages providing details of the error.
If the error is correctable, do so and then restart Cluster Ready Service using 'crsctl
stop crs -f' followed by 'crsctl start crs'. If no messages are found or you do not
understand how to correct the problem, contact Oracle Support Services.
CRS-00714: Oracle Clusterware Release number.number.number.number.number.
Cause: The Oracle High Availability Services Daemon (OHASD) was started as part
of a general start of the Oracle Clusterware stack on this node.
Action: None
CRS-00715: Oracle High Availability Service has timed out waiting for init.ohasd to
be started.
Cause: The Oracle High Availability Service requires that initd start init.ohasd to
successfully initialize.
CRS-00001 to CRS-29006 20-11
Action: 1. Check the run level to ensure that you are in the correct runlevel using
cluvfy ("cluvfy stage -pre crsinst -n nodelist"); 2. If the run level is correct, diagnose the
reason for init.d not starting init.ohasd.
CRS-00800: Cluster Ready Service aborted due to failure to allocate memory.
Details at string in string.
CRS-00801: Cluster Ready Service aborted due to failure to obtain identity of the
running process. Details at string in string.
Cause: Failed to retrieve user id.
Action: Check <crs_home> owner and restart Cluster Ready Service using 'crsctl stop
Services.
CRS-00802: Cluster Ready Service aborted due to failure to run as privileged user.
Cause: Cluster Ready Service was not running as privileged user.
Action: On Unix, restart Cluster Ready Service as privileged user using 'crsctl stop crs
-f' followed by 'crsctl start crs'. On Windows, check the privileges of the Oracle High
Availability Service and restart Cluster Ready Service using 'crsctl stop crs -f'
followed by 'crsctl start crs' If the problem persists, contact Oracle Support Services.
CRS-00803: Cluster Ready Service aborted due to failure to initialize the
communication context. Details at string in string.
CRS-00804: Cluster Ready Service aborted due to Oracle Cluster Registry error
[string]. Details at string in string.
Cause: Oracle Cluster Registry aborted with an error. Look at the associated error
message to determine the underlying issue.
Action: Solve the underlying issue and restart Cluster Ready Service using 'crsctl stop
Services.
CRS-00805: Cluster Ready Service aborted due to failure to communicate with
Cluster Synchronization Service with error [number]. Details at string in string.
Cause: The Cluster Synchronization Service is unreachable.
CRS-00806: Cluster Ready Service aborted due to failure to retrieve the local node
name. Details at string in string.
Cause: The Cluster Synchronization Service node name is not accessible.
CRS-00807: Cluster Ready Service aborted due to failure to check version

compatibility. Details at string in string.
Cause: Oracle Cluster Registry content is not compatible with this version of Cluster
Ready Service.
Action: Start the correct version of Cluster Ready Service. If the problem persists,
CRS-00808: Cluster Ready Service aborted due to failure to retrieve
ORA_CRS_HOME environment variable. Details at string in string.
Cause: An environment variable required by Cluster Ready Service failed to be set at
initialization.
Action: Run 'rootcrs.pl -unlock' followed by 'rootcrs.pl -patch' and restart Cluster
Ready Service using 'crsctl stop crs -f' followed by 'crsctl start crs'. If the problem
CRS-00809: Cluster Ready Service aborted due to failure to initialize
ORA_CRS_HOME path. Details at string in string.
Cause: Cluster Ready Service ORA_CRS_HOME path could not be initialized.
Action: Check for execute permissions on the Grid Infrastructure home or
<crs_home> and restart Cluster Ready Service using 'crsctl stop crs -f' followed by
'crsctl start crs'. If the problem persists, contact Oracle Support Services.
CRS-00810: Cluster Ready Service aborted due to failure to communicate with
Event Management Service with error [number]. Details at string in string.
Cause: The Event Management Service is unreachable.
CRS-00811: Cluster Ready Service aborted due to failure to build dependency
graph. Details at string in string.
Cause: There exists inconsistencies in the resources dependencies.
Action: Check the resources dependencies and restart Cluster Ready Service using
'crsctl stop crs -f' followed by 'crsctl start crs'. If the problem persists, contact Oracle
Support Services.
CRS-00812: Cluster Ready Service aborted due to failure to initialize the network
layer with error [number]. Details at string in string.
CRS-00813: Cluster Ready Service aborted due to failure to initialize the network
layer with error [string]. Details at string in string.
CRS-00814: Cluster Ready Service aborted due to failure to start thread with error
[number]. Details at string in string.
Cause: Thread creation failed.
CRS-00001 to CRS-29006 20-13
CRS-01001: The OCR was formatted using version number.

Cause: Successfully formatted the OCR location(s).
Action: None
CRS-01002: The OCR was restored from file string.
Cause: The OCR was successfully restored from a backup file as requested by the
user.
Action: None
CRS-01003: The OCR format was downgraded to version number.
Cause: The OCR was successfully downgraded to an earlier block format as requested
by the user.
Action: None
CRS-01004: The OCR was imported from string.
Cause: Successfully imported the OCR contents from a file.
Action: None
CRS-01005: The Oracle Clusterware upgrade was completed. Version has changed
from [number, string] to [number, string]. Details in string.
Cause: The Oracle Clusterware was successfully upgraded to a version.
Action: None
CRS-01006: The OCR location string is inaccessible. Details in string.
Cause: An error occurred while accessing the OCR.
Action: Use the ocrcheck command to validate the accessibility of the device and its
block integrity. Check that the OCR location in question has the correct permissions.
Determine whether this behavior is limited to one node or whether it occurs across all
of the nodes in the cluster. Use the ocrconfig command with the -replace option to
replace the OCR location.
CRS-01007: The OCR/OCR mirror location was replaced by string.
Cause: The OCR location was successfully replaced as requested by the user.
Action: None
CRS-01008: Node string is not responding to OCR requests. Details in string.
Cause: Error in communicating to the OCR server on a peer node. This OCR did not
receive a notification regarding its peer's death within the specified time.
CRS-01009: The OCR configuration is invalid. Details in string.
Cause: The OCR configuration on this node does not match the OCR configuration on
the other nodes in the cluster.
Action: Determine the OCR configuration on the other nodes in the cluster on which
Oracle Clusterware is running by using the ocrcheck command. Run the ocrconfig
command with the -repair option to correct the OCR configuration on this node.
CRS-01010: The OCR mirror location string was removed.
Cause: The OCR location was successfully removed as requested by the user.
Action: None
CRS-01011: OCR cannot determine that the OCR content contains the latest
updates. Details in string.
Cause: The OCR could not be started. The OCR location configured on this node does
not have the necessary votes and might not have the latest updates.
Action: Ensure that the other nodes in the cluster have the same OCR location
configured. If the configuration on the other nodes in the cluster does not match, then
run the ocrconfig command with the -repair option to correct the configuration on
this node. If the configurations on all of the nodes match, use the ocrdump command
to ensure that the existing OCR location has the latest updates. Run the ocrconfig
command with the -overwrite option to correct the problem. If the se procedures do
not correct the problem, then contact Oracle Support Services.
CRS-01012: The OCR service started on node string.
Cause: The OCR was successfully started.
Action: None
CRS-01013: The OCR location in an ASM disk group is inaccessible. Details in
string.
Cause: An error occurred while accessing the OCR file in an ASM disk group.
Action: Use the 'asmcmd' command to verify if the ASM instance is active. If the ASM
instance aborted, it will be restarted automatically. Use 'ocrcheck -config' to discover
the OCR locations configured, and verify using 'asmcmd' that the disk group in
question is mounted. Mount the disk group if it is not mounted. Validate if the
behavior is limited to one node or whether it occurs across all of the nodes in the
cluster. If nothing works, use the 'ocrconfig' command with the '-replace' or '-delete'
option to replace or remove the OCR location.
CRS-01014: Failed to import Oracle Cluster Registry from file string
Cause: Unable to read data from the import file and import to the cluster registry
Action: Check availability of the cluster registry and the details of the failure from the
log file
CRS-01015: A request to terminate the Cluster Ready Service on node string
completed successfully. Details at string in string.
Cause: The Cluster Ready Service on the above listed node did not respond to an
earlier request within the specified time. The Cluster Ready Service will be terminated
to prevent any possible cluster hangs.
Action: Check the Oracle Clusterware alert log on the listed node for any problems.
Check for any reason that might not allow the Cluster Ready Service to run optimally
on the listed node. Verify network accessibility to the listed node from other nodes in
the cluster. If the problem persists, contact Oracle Support Services.
CRS-01016: The Cluster Ready Service on this node terminated because it detected
a failure while upgrading the Oracle Cluster Registry format. Details at string in
string.
Cause: The Cluster Ready Service on the node coordinating the upgrade of the Oracle
Cluster Registry format terminated.
Action: The Oracle Cluster Registry format upgrade will be completed by another
node in the cluster. The Cluster Ready Service on the node listed above will be
automatically restarted, and will be able to function as soon as the upgrade
completes. If the problem persists, contact Oracle Support Services.
CRS-00001 to CRS-29006 20-15
CRS-01017: The Cluster Ready Service on this node terminated because it was
unable to open the import file while upgrading the Oracle Cluster Registry format.
Cause: There was a failure accessing the import file on this node. The Cluster Ready
Service on this node may not have been active during the Oracle Cluster Registry
format upgrade.
Action: The Oracle Cluster Registry format upgrade will be completed by another
node in the cluster. The Cluster Ready Service on this node will be automatically
restarted, and will be able to function as soon as the upgrade completes. If the
CRS-01018: The Cluster Ready Service on this node terminated because the OCR
configuration on this node is invalid. Details at string in string.
Cause: The OCR configuration on this node did not match with the OCR
configuration on the other nodes in the cluster.
Action: The OCR configuration on this node is automatically repaired and the Cluster
Ready Service will be automatically restarted. If the problem persists, contact Oracle
Support Services.
CRS-01019: The OCR Service exited on host string. Details in string
Cause: The OCR Service exited due to an internal error.
Action: Determine whether the service has restarted. Collect Clusterware alert log and
the CRSD log indicated in the message and contact Oracle Support Services.
CRS-01020: The Oracle Cluster Registry has invalid contents. Details at string in
string.
Cause: Some of the Oracle Cluster Registry contents were invalid.
Action: Check the log file indicated in the message for more details. Use the 'ocrcheck'
command to detect errors, and the 'ocrdump' command to review the registry
contents. If problems exist, the registry may need to be recovered or restored. If the
CRS-01021: The Oracle Cluster Registry backup file in an ASM disk group is
inaccessible. Details in string.
Cause: Oracle Cluster Registry backup location did not exists, wasn't mounted
correctly, or did not have the required permissions.
Action: Ensure that the backup location exists, that it is mounted correctly and visible
to all nodes in the cluster, and that its permissions are correct. Check the ASM entries
in the alert log file for more details.
CRS-01022: The Oracle Clusterware was forcibly upgraded without upgrading
nodes string. Version has changed from [number, string] to [number, string]. Details
in string.
Cause: Oracle Clusterware was forcibly upgraded when the above listed nodes were
not upgraded.
Action: Delete the above listed nodes using the procedure documented in the Oracle
Clusterware documentation. If the nodes later become accessible, they can be added
back into the cluster.
CRS-01024: The Cluster Ready Service on this node terminated because the ASM
instance was not active on this node. Details at string in string.
Cause: The Cluster Ready Service on the node terminated because the ASM instance
was no longer active.
Action: The Cluster Ready Services on this node will be automatically restarted. If the
CRS-01025: The Oracle Clusterware was upgraded to [string] on all nodes, but the
cluster operating version is still [string]. Details in [string].
Cause: The cluster upgrade did not complete because the root upgrade script failed
on the last node, the root upgrade script was interrupted by the user, or the cluster
upgrade is ongoing.
Action: Check the Oracle Clusterware alert log on all nodes for any problems. Rerun
the root upgrade script on the last node to completion, and ensure that the cluster
operating version has changed using the 'crsctl query crs activeversion' command. If
the problem persists, run diagcollection.pl and contact Oracle Support Services.
CRS-01026: The Oracle Clusterware patch has completed. The patch level has
changed from [number] to [number]. Details in string.
Cause: The Oracle Clusterware was successfully patched.
Action: None
CRS-01027: The Oracle Cluster Registry (OCR) location in an ASM disk group
[string] does not have sufficient space. Details at string in string.
Cause: Unable to increase the size of OCR file in the above listed disk group as the
disk group was out of space.
Action: Delete unused files from the disk group or add additional disks to the disk
group. Refer to Oracle Clusterware administration documentation to know about the
space requirements for OCR in ASM disk group.
CRS-01028: The Oracle Cluster Registry backup location string is inaccessible from
node string. Details in string.
Cause: The backup location provided did not exist, was not mounted correctly, or did
not have the required permissions.
Action: Ensure that the backup location exists, that it is mounted correctly and visible
to all nodes in the cluster, and that the permissions are correct. If the backup location
is an ASM disk group, check the ASM entries in the alert log file for more details.
CRS-01110: The Oracle Clusterware upgrade is in unknown state [number].\n
Cause: There was an internal error upgrading the Oracle Clusterware.
Action: Retry the 'crsctl set crs activeversion' command. If the problem persists,
CRS-01111: Error upgrading the Oracle Clusterware. Details [string].\n
Action: Verify using the 'crsctl check crs' command that the CRS Service running.
Retry the 'crsctl set crs activeversion' command. If the problem persists, contact
CRS-01112: Failed to set the Oracle Clusterware operating version string
CRS-00001 to CRS-29006 20-17
CRS-01114: Invalid active version [string] passed
Cause: An invalid active version was passed.
Action: Use the 'crsctl query crs softwareversion' command to retrieve a valid active
version.
CRS-01115: Oracle Clusterware has already been upgraded.\n
Cause: Oracle Clusterware is already running in highest possible operating version.
Action: None
CRS-01116: Oracle Clusterware upgrade has been aborted.\n
Cause: One of the Oracle Clusterware components have failed to upgrade within the
expected time.
Action: Check the Oracle Clusterware alert log and the CRS daemon log for
additional information.
CRS-01117: Error upgrading the Oracle Clusterware.\n
Cause: An attempt was made to change the Oracle Clusterware operating version
before all nodes were upgraded.
Action: Run root.sh script on all nodes in the cluster. If the problem persists, contact
CRS-01119: Unable to complete Oracle Clusterware upgrade while nodes string
have not yet upgraded\n
Cause: An attempt was made to change the Oracle Clusterware operating version
before all known nodes had been upgraded. Note that some of the nodes listed in the
message may no longer be current or recent cluster members.
Action: Issue the 'olsnodes' command to list current and recent cluster members. Any
nodes listed in the error message, but not listed by 'olsnodes' have not been active
recently, and should be deleted using the procedure documented in the Oracle
Clusterware documentation. The currently or recently active cluster members listed
by 'olsnodes' should be upgraded, or, if no longer needed, deleted: 1) Run the
rootupgrade.sh script on each node to be retained. 2) Delete nodes no longer desired
using the procedure documented in the Oracle Clusterware documentation. Once all
of the nodes listed in the message have been upgraded or deleted, run the
rootupgrade.sh script on an upgraded node to complete the upgrade. If one or more
nodes could not upgraded or deleted, forcibly upgrade the cluster using the
procedure documented in the Oracle Clusterware documentation.
CRS-01121: Oracle Clusterware was forcibly upgraded without upgrading nodes
string.\n
Cause: Oracle Clusterware was forcibly upgraded when the above listed nodes were
not upgraded.
Action: Delete the above listed nodes using the procedure documented in the Oracle
Clusterware documentation. If the nodes later become accessible, they can be added
back into the cluster.
CRS-01124: Invalid active version [string] retrieved.
Cause: An invalid active version was retrieved from the configuration.
CRS-01129: Rejecting rolling upgrade mode change because Oracle ASM is in an

unexpected state.
Cause: A request to reset rolling upgrade mode was rejected because Oracle ASM was
in an unexpected state.
CRS-01130: Rejecting rolling upgrade mode change because Oracle IOServer is in
an unexpected state.
Cause: A request to reset rolling patch mode was rejected because Oracle IOServer
was in an unexpected state.
CRS-01131: The cluster was successfully set to rolling upgrade mode.\n
Cause: A 'crsctl start rollingupgrade' command completed successfully.
Action: None
CRS-01132: The cluster is in rolling upgrade mode.
Cause: The cluster was already running in rolling upgrade mode.
Action: None
CRS-01133: There was an error setting Oracle Clusterware to rolling upgrade mode.
Cause: There was an error setting Oracle Clusterware to rolling upgrade mode.
Action: Verify using the 'crsctl check crs' command that the Cluster Ready Services
(CRS) is active, and inspect the accompanying Clusterware-specific error messages to
see if there is a correctable problem. If so, correct the problem and retry the 'crsctl
start rollingupgrade' command. If the problem persists, contact Oracle Support
Services.
CRS-01134: There was an error setting Oracle ASM to rolling upgrade mode.
Cause: There was an error setting Oracle ASM to rolling upgrade mode.
Action: Verify using the 'srvctl status asm' command that the Oracle ASM instance is
active, and inspect the accompanying ASM-specific error messages to see if there is a
correctable problem. If so, correct the problem and retry the 'crsctl start
rollingupgrade' command. If the problem persists, contact Oracle Support Services.
CRS-01135: There was an error setting Oracle IOServer to rolling upgrade mode.
Cause: There was an error setting Oracle IOServer to rolling upgrade mode.
Action: Verify using the 'srvctl status ioserver' command that the Oracle IOServer
instance is active, and inspect the accompanying IOServer-specific error messages to
start rollingupgrade' command. If the problem persists, contact Oracle Support
Services.
CRS-01136: Rejecting the rolling upgrade mode change because the cluster is being
patched.
Cause: The rolling upgrade mode change was rejected because the cluster was being
patched.
Action: Complete applying the patch on all nodes in the cluster before retrying the
'crsctl start rollingupgrade' command.
CRS-00001 to CRS-29006 20-19
CRS-01137: Rejecting the rolling upgrade mode change because the cluster was
forcibly upgraded.
Cause: The rolling upgrade mode change was rejected because the cluster was
forcibly upgraded.
Action: Delete the nodes that were not upgraded using the procedure documented in
the Oracle Clusterware documentation. Retry the 'crsctl start rollingupgrade'
command after completing the above steps.
CRS-01138: There was an error setting the cluster to rolling upgrade mode.
Cause: There was an internal error setting the cluster to rolling upgrade mode.
Action: Retry the 'crsctl start rollingupgrade' command. If the problem persists,
CRS-01139: Invalid version [string] passed
Cause: An invalid version was passed.
Action: Use the version returned by the 'crsctl query crs releaseversion' command
issued from the Oracle Grid Infrastructure home to which you are upgrading.
CRS-01140: The passed version [string] cannot be less than or equal to the release
version [string].
Cause: A version was passed that was less than or equal to the release version.
Action: Verify that the version of the Oracle Grid Infrastructure home to be upgraded
to is greater than the current Oracle Grid Infrastructure home.
CRS-01141: The passed version [string] cannot be less than or equal to the cluster
active version [string].
Cause: A version was passed that was less than or equal to the cluster active version.
Action: Verify that the version of the Oracle Grid Infrastructure home to be upgraded
to is greater than the cluster active version.
CRS-01142: The cluster cannot be set to rolling upgrade mode because Oracle
Clusterware is not active on at least one remote node.
Cause: The cluster could not be set to rolling upgrade mode because Oracle
Clusterware was not active on any of the remote nodes.
Action: Start Oracle Clusterware on at least one remote node and retry the 'crsctl start
rollingupgrade' command, or retry upgrade using the non-rolling option.
CRS-01151: The cluster was successfully set to rolling patch mode.\n
Cause: A 'crsctl start rollingpatch' command completed successfully.
Action: None
CRS-01152: The cluster is in rolling patch mode.
Cause: The cluster was already running in rolling patch mode.
Action: None
CRS-01153: There was an error setting Oracle Clusterware to rolling patch mode.
Cause: There was an error setting Oracle Clusterware to rolling patch mode.
start rollingpatch' command. If the problem persists, contact Oracle Support Services.
CRS-01154: There was an error setting Oracle ASM to rolling patch mode.
Cause: There was an error setting Oracle ASM to rolling patch mode.
correctable problem. If so, correct the problem and retry the 'crsctl start rollingpatch'
command. If the problem persists, contact Oracle Support Services.
CRS-01155: There was an error setting Oracle IOServer to rolling patch mode.
Cause: There was an error setting Oracle IOServer to rolling patch mode.
start rollingpatch' command. If the problem persists, contact Oracle Support Services.
CRS-01156: Rejecting the rolling patch mode change because the cluster is in the
middle of an upgrade.
Cause: The rolling patch mode change was rejected because the cluster was
undergoing an upgrade.
Action: None
CRS-01157: Rejecting the rolling patch mode change because the cluster was
forcibly upgraded.
Cause: The rolling patch mode change was rejected because the cluster was forcibly
upgraded.
Action: Delete the nodes that were not upgraded using the procedure documented in
the Oracle Clusterware documentation. Retry the 'crsctl start rollingpatch' or 'crsctl
stop rollingpatch' command after completing the above steps.
CRS-01158: There was an error setting the cluster to rolling patch mode.
Cause: There was an internal error setting the cluster to rolling patch mode.
Action: Retry the 'crsctl start rolling patch' command. If the problem persists, contact
CRS-01159: The cluster cannot be set to rolling patch mode because Oracle
Clusterware is not active on at least one remote node.
Cause: The cluster could not be set to rolling patch mode because Oracle Clusterware
was not active on any of the remote nodes.
Action: Start Oracle Clusterware on at least one remote node and retry the 'crsctl start
rollingpatch' command, or retry patching using the non-rolling option.
CRS-01161: The cluster was successfully patched to patch level [number].\n
Cause: A 'crsctl stop rollingpatch' command completed successfully.
Action: None
CRS-01162: Rejecting rolling patch mode change because the patch level is not
consistent across all nodes in the cluster. The patch level on nodes string is not the
same as the expected patch level [number] found on nodes string.
Cause: The 'crsctl stop rollingpatch' command was rejected because all the nodes in
the cluster were not patched to the same patch level.
Action: Make sure all the nodes in the cluster have been patched to the same patch
level using the 'crsctl query crs softwarepatch host' command. Retry the 'crsctl stop
rollingpatch' command after patching the required nodes.
CRS-00001 to CRS-29006 20-21
CRS-01163: There was an error resetting Oracle Clusterware rolling patch mode.
Cause: There was an error resetting Oracle Clusterware rolling patch mode.
see if there is a correctable problem. If so, correct the problem and retry the 'crsctl stop
rollingpatch' command. If the problem persists, contact Oracle Support Services.
CRS-01164: There was an error resetting Oracle ASM rolling patch mode.
Cause: There was an error resetting Oracle ASM rolling patch mode.
correctable problem. If so, correct the problem and retry the 'crsctl stop rollingpatch'
command. If the problem persists, contact Oracle Support Services.
CRS-01165: There was an error resetting Oracle IOServer rolling patch mode.
Cause: There was an error resetting Oracle IOServer rolling patch mode.
see if there is a correctable problem. If so, correct the problem and retry the 'crsctl stop
rollingpatch' command. If the problem persists, contact Oracle Support Services.
CRS-01166: Rejecting rolling patch mode change because Oracle ASM is in [string]
state.
Cause: A request to reset rolling patch mode was rejected because Oracle ASM was in
an unexpected state.
Action: Retry the 'crsctl stop rollingpatch' command. If the problem persists, contact
CRS-01167: Rejecting rolling patch mode change because Oracle IOServer is in
[string] state.
Cause: A request to reset rolling patch mode was rejected because Oracle IOServer
was in an unexpected state.
Action: Retry the 'crsctl stop rollingpatch' command. If the problem persists, contact
CRS-01168: There was an error resetting the cluster rolling patch mode.
Cause: There was an internal error resetting the cluster rolling patch mode.
Action: Retry the 'crsctl stop rolling patch' command. If the problem persists, contact
CRS-01169: The cluster is consistent and the cluster active patch level is [number].
Cause: The cluster has already completed the rolling patch procedure.
Action: None
CRS-01170: Rejecting rolling patch mode change because the patch has not been
applied yet. The software patch level [number] on this node is not the same as the
expected patch level [number].
Cause: The 'crsctl stop rollingpatch' command was rejected because the patch level
did not match with the configured software patch level.
Action: Complete applying the patch on this node, and verify the patch level using
the 'crsctl query crs softwarepatch host' command. Retry the 'crsctl stop rollingpatch'
command.
CRS-01171: Rejecting rolling patch mode change because the patch level is not
consistent across all nodes in the cluster. The patch level on nodes string is not the
same as the patch level [number] found on nodes string.
Cause: The 'crsctl stop rollingpatch' command was rejected because all the nodes in
the cluster were not patched to the same patch level.
Action: Verify the list of patches applied on a node by issuing the the 'crsctl query crs
releasepatch' command. Apply the requisite patches. Make sure all the nodes in the
cluster have been patched to the same patch level using the 'crsctl query crs
softwarepatch' command. Retry the 'crsctl stop rollingpatch' command after patching
the required nodes.
CRS-01181: There was an error retrieving the Oracle Clusterware release patch
level.
Cause: There was an internal error retrieving the Oracle Clusterware release patch
level.
CRS-01182: Oracle Clusterware release patch level is [number] and the complete list
of patches [string] have been applied on the local node.\n
Cause: None, this is an informational message.
Action: None
CRS-01183: Oracle Clusterware release patch level is [number] and an incomplete
list of patches [string] have been applied on the local node.\n
Cause: There was an error retrieving the complete list of patches.
CRS-01184: Oracle Clusterware release patch level is [number] and no patches have
been applied on the local node.\n
Action: None
CRS-01191: There was an error retrieving the Oracle Clusterware software patch
level.
Cause: There was an internal error retrieving the Oracle Clusterware software patch
level.
CRS-01192: Oracle Clusterware patch level on node string is [number].\n
Action: None
CRS-01201: CRSD started on node string.
Cause: CRSD has started, possibly due to a CRS start, or a node reboot or a CRSD
restart.
Action: None Required. You can run the command 'crsctl check crsd' to validate the
health of the CRSD.
CRS-01202: CRSD aborted on node string. Error [string]. Details in string.
Cause: Fatal Internal Error. Check the CRSD log file to determine the cause.
Action: Determine whether the CRSD gets auto-started.
CRS-00001 to CRS-29006 20-23
CRS-01203: Failover failed for the CRS resource string. Details in string.
Cause: Failover failed due to an internal error. Examine the contents of the CRSD log
file to determine the cause.
Action: None
CRS-01204: Recovering CRS resources for node string.
Cause: CRS resources are being recovered, possibly because the cluster node is
starting up online.
Action: Check the status of the resources using the 'crsctl status resource' command.
CRS-01205: Auto-start failed for the CRS resource string. Details in string.
Cause: This message comes up when the auto-start for the resource has failed during
a reboot of the cluster node.
Action: Start the resources using the 'crsctl start resource' command.
CRS-01206: Resource string is in the UNKNOWN state. Make sure the resource is
completely stopped, then use the 'crsctl stop -f' command.
Cause: Resource went into an unknown state because the check or the stop action on
the resource failed.
Action: Make sure the resource is completely stopped, then use the 'crsctl stop -f'
command.
CRS-01207: There are no more restart attempts left for resource string. Restart the
resource manually using the crsctl command.
Cause: The Oracle Clusterware is no longer attempting to restart the resource because
the resource has failed and the Oracle Clusterware has exhausted the maximum
number of restart attempts.
Action: Use the 'crsctl start' command to restart the resource manually.
CRS-01208: Cluster Ready Service terminating, unable to start successfully. Details
at string in string.
Cause: Cluster Ready Service could not initialize successfully.
Action: Restart Cluster Ready Service using the command 'crsctl start clusterware'. If
the problem persists, contact Oracle Support Services.
CRS-01209: Cluster Ready Service terminating, failed to register with group 'string'.
Cause: Cluster Ready Service could not initialize successfully.
CRS-01210: Cluster Ready Service failed to update group data. Details at string in
string.
Cause: Cluster Ready Service failed to update the group private data with new
master.
CRS-01211: Cluster Ready Service noticed abnormal termination by Cluster

Synchronization Service. Details at string in string.
Cause: Cluster Ready Service terminating due to abnormal termination of Cluster
Synchronization Service layer.
CRS-01212: Cluster Ready Service received invalid update for group private data.
CRS-01213: Cluster Ready Service failed to retrieve user information. Details at
string in string.
CRS-01214: Cluster Ready Service failed to initialize OLR context. Details at string
in string.
Cause: Cluster Ready Service unable to access local registry.
Action: Use the ocrcheck utility to detect errors in the OLR. If problems exist, the
registry may need to be recovered or restored.
CRS-01215: Cluster Ready Service could not get the local node number. Details at
string in string.
Cause: Cluster Ready Service could not retrieve the local node incarnation number.
CRS-01216: Cluster Ready Service could not determine node list. Details at string in
string.
CRS-01217: Cluster Ready Service unable to get node name. Details at string in
string.
Cause: Cluster Ready Service could not determine node name.
CRS-01218: Cluster Ready Service error during initialization. Details at string in
string.
Cause: Cluster Ready Service could not initialize underlying layers successfully.
CRS-01219: Cluster Synchronization Service not available. Details at string in
string.
Cause: Cluster Ready Service was unable to initialize access to CSS, which is required.
CRS-01220: Cluster Ready Service could not retrieve local node number. Details at
string in string.
Cause: Cluster Ready Service could not retrieve node number for local node.
CRS-00001 to CRS-29006 20-25
CRS-01221: Cluster Ready Service failed to retrieve local node name. Details at
string in string.
Cause: Cluster Ready Service could not retrieve node name.
CRS-01222: Cluster Ready Service failed to retrieve maximum group size. Details at
string in string.
Cause: Cluster Ready Service could not retrieve value for maximum group size.
CRS-01223: Cluster Ready Service error while reading cluster active version.
Cause: Could not retrieve cluster active version.
CRS-01224: Server authentication exception encountered, exception text is 'string'.
Cause: Cluster Ready Service encountered error while authenticating user.
Action: This is an internal error. Contact Oracle Support Services.
CRS-01225: Invalid identity exception encountered, exception text is 'string'. Details
Cause: Cluster Ready Service could not verify user identity.
CRS-01226: Failed to create message to send to policy engine. Details at string in
string.
Cause: Cluster Ready Service encountered communication error.
CRS-01227: Error during initialization of communication subsystem. Details at
string in string.
Cause: Cluster Ready Service encountered communication error during initialization.
CRS-01228: Error while setting up user interface server. Details at string in string.
CRS-01229: Error while listening for events. Details at string in string.
CRS-01231: Failed to open key 'string' in OCR. Details at string in string.
CRS-01232: Could not get security attribute for system key 'string' in OCR. Details
Cause: Encountered error while reading system key attributes in OCR.
CRS-01233: Failed to initialize batch handler for OCR. Details at string in string.
Cause: Could not initialize batch handler for multiwrite in OCR.
CRS-01234: Encountered error while setting key value for key 'string' in OCR.
Cause: Encountered an error while executing a batch write in OCR.
CRS-01235: Error while executing batch for multi writes in OCR. Details at string in
string.
Cause: Encountered an error while executing a batch write in OCR.
CRS-01236: Error enumerating subkeys for key 'string' in OCR. Details at string in
string.
Cause: Encountered an error while reading subkey values in OCR.
CRS-01237: Failed to retrieve the maximum value supported in OCR. Details at
string in string.
Cause: Could not read the maximum value size from registry.
CRS-01238: Failed to add a delete key operation for key 'string' to a batch in OCR.
Cause: Encountered internal error while deleting key in OCR.
CRS-01239: Cluster Ready Service aborted due to an unexpected error [string].
Cause: This is an unexpected error. Look at the associated error message to fix the
underlying issue.
CRS-01301: Oracle High Availability Service started on node string.
Cause: Oracle High Availability Service has started, possibly due to a Clusterware
start, or a node reboot.
Action: None Required.
CRS-01302: Oracle High Availability Service aborted on node string. Error [string].
Details in string.
Cause: Fatal Internal Error. Check the Oracle High Availability Service log file to
determine the cause.
Action: Determine whether the Oracle High Availability Service gets auto-started.
CRS-01303: Failover failed for the OHAS resource string. Details in string.
Cause: Failover processing for the specified resource did not complete. Examine the
contents of the Oracle High Availability Service log file to determine the cause.
Action: None
CRS-00001 to CRS-29006 20-27
CRS-01304: Recovering OHAS resources for node string.

Cause: Oracle High Availability Service resources are being recovered, possibly
because the cluster node is starting up online.
Action: Check the status of the resources using the crsctl command.
CRS-01305: Auto-start failed for the OHAS resource string. Details in string.
Cause: This message comes up when the auto-start for the resource has failed during
a reboot of the cluster node.
Action: Start the resources using the 'crsctl start resource' command.
CRS-01306: Resource string is in an unknown state. Make sure the resource is
completely stopped, then use the 'crsctl stop -f' command.
Cause: Resource went into an unknown state because the check or the stop action on
the resource failed.
Action: Make sure the resource is completely stopped, then use the 'crsctl stop -f'
command.
CRS-01307: There are no more restart attempts left for resource string. Restart the
resource manually using the crsctl command.
Cause: The Oracle Clusterware is no longer attempting to restart the resource because
the resource has failed and the Oracle Clusterware has exhausted the maximum
number of restart attempts.
Action: Use the 'crsctl start resource' command to restart the resource manually.
CRS-01308: Oracle High Availability Service terminating, unable to start
successfully. Details at string in string.
Cause: Oracle High Availability Service could not initialize successfully.
Action: Restart your clusterware installation. If the problem persists, contact Oracle
Support Services.
CRS-01309: Oracle High Availability Service terminating, failed to register with
group 'string'. Details at string in string.
Cause: Oracle High Availability Service could not initialize successfully.
Support Services.
CRS-01310: Oracle High Availability Service failed to update group data. Details at
string in string.
Cause: Oracle High Availability Service failed to update the group private data with
new master.
Support Services.
CRS-01311: Oracle High Availability Service noticed abnormal termination by
Cluster Synchronization Service. Details at string in string.
Cause: Oracle High Availability Service terminating due to abnormal termination of
Cluster Synchronization Service layer.
CRS-01312: Oracle High Availability Service received invalid update for group
private data. Details at string in string.
CRS-01313: Oracle High Availability Service failed to retrieve user information.
CRS-01314: Oracle High Availability Service failed to initialize OLR context.
Cause: Oracle High Availability Service unable to access local registry.
Action: Use the ocrcheck utility to detect errors in the OLR. If problems exist, the
registry may need to be recovered or restored.
CRS-01315: Oracle High Availability Service could not get the local node number.
Cause: Oracle High Availability Service could not retrieve the local node incarnation
number.
CRS-01316: Oracle High Availability Service could not determine node list. Details
CRS-01317: Oracle High Availability Service unable to get node name. Details at
string in string.
Cause: Oracle High Availability Service could not determine node name.
CRS-01318: Oracle High Availability Service error during initialization. Details at
string in string.
Cause: Oracle High Availability Service could not initialize underlying layers
successfully.
CRS-01319: Cluster Synchronization Service not available. Details at string in
string.
Cause: Oracle High Availability Service was unable to initialize access to CSS, which
is required.
CRS-01320: Oracle High Availability Service could not retrieve local node number.
Cause: Oracle High Availability Service could not retrieve node number for local
node.
CRS-00001 to CRS-29006 20-29
CRS-01321: Oracle High Availability Service failed to retrieve local node name.
Cause: Oracle High Availability Service could not retrieve node name.
CRS-01322: Oracle High Availability Service failed to retrieve maximum group
size. Details at string in string.
Cause: Oracle High Availability Service could not retrieve value for maximum group
size.
CRS-01323: Oracle High Availability Service error while reading cluster active
version. Details at string in string.
Cause: Could not retrieve cluster active version.
CRS-01324: Server authentication exception encountered, exception text is 'string'.
Cause: Oracle High Availability Service encountered error while authenticating user.
CRS-01325: Invalid identity exception encountered, exception text is 'string'. Details
Cause: Oracle High Availability Service could not verify user identity.
CRS-01326: Failed to create message to send to policy engine. Details at string in
string.
Cause: Oracle High Availability Service encountered communication error.
CRS-01327: Error during initialization of communication subsystem. Details at
string in string.
Cause: Oracle High Availability Service encountered communication error during
initialization.
CRS-01328: Error while setting up user interface server. Details at string in string.
Action: This is an internal error. Contact Oracle Support Services..
CRS-01329: Error while listening for events. Details at string in string.
Action: This is an internal error. Contact Oracle Support Services..
CRS-01330: Oracle High Availability Services aborted due to internal error.
Cause: Fatal Internal Error. Check the Oracle High Availability Service log file to
Action: Determine whether the Oracle High Availability Service gets auto-started.
CRS-01331: Failed to open key 'string' in OLR. Details at string in string.

CRS-01332: Could not get security attribute for system key 'string' in OLR. Details
Cause: Encountered error while reading system key attributes in OLR.
CRS-01333: Failed to initialize batch handler for OLR. Details at string in string.
Cause: Could not initialize batch handler for multiwrite in OLR.
CRS-01334: Encountered error while setting key value for key 'string' in OLR.
Cause: Encountered an error while executing a batch write in OLR.
CRS-01335: Error while executing batch for multi writes in OLR. Details at string in
string.
Cause: Encountered an error while executing a batch write in OLR.
CRS-01336: Error enumerating subkeys for key 'string' in OLR. Details at string in
string.
Cause: Encountered an error while reading subkey values in OLR.
CRS-01337: Failed to retrieve the maximum value supported in OLR. Details at
string in string.
Cause: Could not read the maximum value size from registry.
CRS-01338: Failed to add a delete key operation for key 'string' to a batch in OLR.
Cause: Encountered internal error while deleting key in OLR.
CRS-01339: Oracle High Availability Service aborted due to an unexpected error
[string]. Details at string in string.
Cause: Look at the associated error message to fix the underlying issue.
CRS-01340: Node 'string' has a pending role change; Oracle High Availability
Services needs to be restarted.
Cause: A 'crsctl stop cluster' command was run after a node's role has changed.
Action: Run 'crsctl stop crs' and 'crsctl start crs' on the node for the node role change
to take effect.
CRS-00001 to CRS-29006 20-31
CRS-01401: EVMD started on node string.

Cause: EVMD has started either because of a CRS start, a node reboot, or an EVMD
restart.
Action: None required. You can run the 'crsctl check evmd' command to validate the
health of EVMD.
CRS-01402: EVMD aborted on node string. Error [string]. Details in string.
Cause: EVMD has aborted due to an internal error. Check the EVMD log file to
Action: Determine whether the EVMD is auto-started and contact Oracle Support
Services.
CRS-01403: The Event Management Service terminated on node string. Listening
port number is in use by another application. Details in string.
Cause: The Event Management Service has aborted because the configured listening
port is being used by another application on this node.
Action: Make the listening port listed above available. Restart the Event Management
Service using 'crsctl start crs' or 'crsctl start cluster' command.
CRS-01601: CSSD Reconfiguration complete. Active nodes are string.
Cause: A node joined or left the cluster.
Action: None
CRS-01602: CSSD aborted on node string. Error [string]; details in string.
Cause: The CSS daemon aborted on the listed node with the listed return code.
Action: Collect the CSS daemon logs from all nodes and any CSS daemon core files
and contact Oracle Support.
CRS-01603: CSSD on node string shutdown by user.
Cause: The CSS daemon on the listed node was terminated by a user.
Action: None
CRS-01604: CSSD voting file is offline: string; details at string in string.
Cause: The listed voting file became unusable on the local node.
Action: Verify that the filesystem containing the listed voting file is available on the
local node.
CRS-01605: CSSD voting file is online: string; details in string.
Cause: The CSS daemon has detected a valid configured voting file.
Action: None
CRS-01606: The number of voting files available, number, is less than the minimum
number of voting files required, number, resulting in CSSD termination to ensure
data integrity; details at string in string
Cause: The number of voting files has decreased to a number of files that is
insufficient.
Action: Locate previous 1604, 1613, 1614 and 1615 messages and take action as
indicated by those messages.
CRS-01607: Node string is being evicted in cluster incarnation number; details at

string in string.
Cause: The local node has detected that the indicated node is still active, but not able
to communicate with this node, so is forcibly removing the indicated node from the
cluster.
CRS-01608: This node was evicted by node number, string; details at string in string.
Cause: The local node was evicted by the indicated node.
CRS-01609: This node is unable to communicate with other nodes in the cluster and
is going down to preserve cluster integrity; details at string in string.
Cause: Communication was lost with some nodes of the cluster and this node
detected that another sub-cluster was designated to be the surviving sub-cluster. This
node went down to preserve data integrity.
Action: Verify all network connections between cluster nodes and repair any
problematic connections. If there do not appear to be any network problems, 1. collect
the CSS daemon logs, system messages and any CSS daemon core files from all nodes
and 2. contact Oracle Support.
CRS-01610: Network communication with node string (number) missing for 90%%
of timeout interval. Removal of this node from cluster in number.number seconds
Cause: Did not receive heartbeat messages from the node. This could be due to
network problems or failure of the listed node.
Action: Check if the private interconnect network used by cluster is functioning
properly, including all the cables, network cards, switches/routers etc. between this
node and listed node. Correct any problems discovered.
network problems or failure of the listed node.
network problems or failure of listed node.
CRS-01613: No I/O has completed after 90%% of the maximum interval. Voting file
string will be considered not functional in number milliseconds
Cause: Voting device I/O has not completed for a long time. This could be due some
error with the device the voting file is on or in some element in the path of the I/O to
the device.
CRS-00001 to CRS-29006 20-33
Action: Verify that the device is working properly including all elements in the I/O
path. The voting file listed will be considered inactive in the number of milliseconds
specified. Failure of a majority of devices will result in node reboot.
the device.
the device.
CRS-01616: The BMC device used for IPMI at IP address string is not properly
configured for ADMIN access; details at string in string
Cause: The IPMI BMC is not configured to support the ADMIN access methods
required by Oracle Clusterware.
Action: Consult the clusterware admin manual for proper procedures in configuring
BMC. Use the BMC configuration tool (ipmitool or ipmiutil) command to check and
verify that the current configuration supports either MD5 or password validation for
ADMIN access.
CRS-01617: The information required to do node kill for node string is incomplete;
details at string in string
Cause: Incomplete config information stored in Cluster Registry for node kill.
Action: Make sure all the information pertaining to the node kill method
CRS-01618: The requested node kill information change could not be validated by
node string; details at string in string
Cause: Unable to validate the node kill information for this node.
Action: Additional information can be found in the CRS alert log of the node that
performed the validation.
CRS-01619: The node kill information of node string could not be validated by this
node due to failure in connecting to the IPMI device; details at string in string
Cause: Unable to validate the node kill information for this node.
Action: Additional information can be found in the CSSD logs.
CRS-01620: The node kill information of node string could not be validated by this
node due to invalid authorization information; details at string in string
Cause: Unable to validate the kill information for this node.
CRS-01621: The IPMI configuration data for this node stored in the Oracle registry
is incomplete; details at string in string
Cause: All the necessary information such as IPMI username, password and IP
address are not present.
Action: Make sure all the information(BMC IPMI username, password and IP
address) are present. Use commands 'crsctl set css ipmiaddr' and 'crsctl set css
ipmiadmin' for this.
CRS-01622: The IPMI node kill information could not be validated due to inability
to connect to the IPMI device at BMC IP address provided string; details at string in
string
Cause: Unable to validate the BMC IPMI IP address provided.
CRS-01623: The IPMI node kill information of BMC at IP address string could not
be validated due to invalid authorization information. The BMC username
provided is 'string'; details at string in string
Cause: Unable to validate the BMC IPMI UserName and password provided.
CRS-01624: The requested Node kill information change succeeds vacuously
because there is no other node in cluster to validate.
Cause: Unable to validate the credentials because this is the sole node in the cluster.
Action: To complete the valdidation, shut down the clusterware stack on this node,
start another node and restart the stack on this node.
CRS-01625: Node string, number number, was shut down
Cause: A Clustware stack shutdown command was issued for a node in the cluster
and was observed by this node.
Action: None required.
CRS-01626: A Configuration change request completed successfully
Cause: A Configuration change request completed successfully.
CRS-01627: A Configuration change request failed because another configuration
change is in progress; Details at string in string
Cause: Another configuration change is in still in progress.
Action: Wait until the other command completes and reissue the command if
necessary. Message 1626 would be printed if the command succeeds.
CRS-01628: A Configuration change request failed because read of existing voting
files failed; Details at string in string
Cause: CSSD was not able to read the lease blocks of a majority of Voting files which
is an indication of a problem with the voting files.
Action: Run the command 'crsctl query css votedisk' to get the list of currently
working voting files. User may delete problematic voting file or use a different set.
CRS-00001 to CRS-29006 20-35
CRS-01629: A Configuration change request failed because write to new voting

files failed; Details at string in string
Cause: A voting file write failed, causing the associated configuration change to fail.
This often results from adding a voting file that is not accessible to one or more nodes.
Action: Confirm that voting files added in a configuration change are accessible and
writeable from all cluster nodes. If they are, contact Oracle Customer Support.
CRS-01630: A configuration change request failed because not all the new voting
files were discovered; Details at string in string
Cause: One or more of the voting files being added were not discovered. Message
1638 identifies the unique ID(s) of the file(s) that could not be found.
Action: Verify if the discovery string is adequate to discover the new voting files. If
not, modify discovery string using command 'crsctl replace discoverystring xxxxx'.
CRS-01631: A configuration change request failed because one or more nodes are
not a sufficient Clusterware version level; Details at string in string
Cause: One ore more nodes are not a sufficient version level.
Action: Configuration change would not be successful until all nodes are at at the
latest version. Try after all the nodes are upgraded.
CRS-01632: Node string is being removed from the cluster in cluster incarnation
number
Cause: The local node is removing the indicated node from the cluster because it
appears to be dead.
Action: Verify that the node that was removed, or the Oracle Clusterware on that
node, was down. The CRS alert log of the node that was removed has information
regarding why the node, or clusterware on the node, was no longer active. If the node
was still up and Oracle Clusterware still active on that node, collect the CSS daemon
logs from all nodes and any CSS daemon core files and contact Oracle Support.
CRS-01633: CSSD failed to register group string in vendor clusterware; details at
string in string
Cause: The local node is not able to register the group of vendor clusterware.
Action: Verify that the vendor clusterware is installed and configured correctly.
CRS-01634: CSSD is unable to determine cluster name; details at string in string
Cause: Name of the cluster cannot be determined from configuration.
Action: Verify that Oracle Clusterware installation was successful.
CRS-01635: CSSSD failed to initialize vendor clusterware; details at string in string
Cause: The local node is not able to attach vendor clusterware.
Action: Verify that the vendor clusterware is installed and configured correctly.
CRS-01636: The CSS daemon was started in exclusive mode but found an active
CSS daemon on node string and is terminating; details at string in string
Cause: The CSS daemon was started in exclusive mode, which requires that the
clusterware stack is down on all other nodes to ensure data integrity. A CSS daemon
was detected on another node, so the CSS daemon on this node is terminating.
Action: Stop the Oracle clusterware stack that is running on the indicated node.
CRS-01637: Unable to locate configured voting file with ID string; details at string
in string
Cause: The voting file with unique the ID indicated in the message was not found
during the voting file discovery phase of CSS initialization.
Action: Verify that all configured voting files are accessible on this node. Any voting
files that are not accessible should be removed and replaced with accessible voting
files using the appropriate 'crsctl' commands.
CRS-01638: Unable to locate voting file with ID string that is being added to the list
of configured voting files; details at string in string
Cause: The voting file with the unique ID indicated in the message was not found
during the voting file discovery phase of CSS initialization. This voting file is in the
process of being added to the list of configured voting files.
Action: Verify that all voting files to be added are accessible on this node. Any voting
files that are not accessible should be removed and replaced with accessible voting
files using the appropriate 'crsctl' commands.
CRS-01639: Rejecting configuration change number:number because another
configuration change is already in progress; details at string in string
Cause: A configuration change was requested, but another configuration change is
already in progress and only one configuration change may be processed at a time.
Action: Wait for the current configuration change to complete, then resubmit this
configuration change.
CRS-01640: Rejecting configuration change number:number because one or more
new voting files in the new configuration could not be found; details at string in
string
Cause: A configuration change that involved the addition of voting files is being
rejected because some of the new voting files were not located.
Action: Verify that the voting file name is correct and that it is accessible on this node,
if the voting files are not managed by ASM. Message number 1638 provides greater
detail.
CRS-01641: Rejecting configuration change number:number because only number of
the required number voting files of the new configuration were located; details at
string in string
Cause: A configuration change that involved a change to the list of voting files is
being rejected because a sufficient number of voting files in the new configuration
could not be located.
Action: Verify that all voting files in the new configuration are accessible on this node.
CRS-01642: Node number is using a different CSS configuration from the one used
by this node; this node is terminating to preserve integrity; details at string in
string
Cause: Another node in the cluster is using a different set of CSS configuration values,
such as misscount or voting files. Inconsistency can result in data corruption, so this
node is terminating to avoid data corruption.
Action: Collect Clusterware alert log and the CSSD log indicated in the message as
well as the CSS daemon logs of all other nodes in the cluster and contact Oracle
Support Services.
CRS-00001 to CRS-29006 20-37
CRS-01643: Failed to format the CSS voting disk string

Cause: Problems were encountered attempting to access the voting file.
Action: Verify that the voting file can be accessed, the file exists, has the proper
ownership and permissions, etc.
CRS-01644: The initialization of the EXADATA fencing facility failed in start with
error ORA-number; details at string in string
Cause: The start of the initialization of the EXADATA fencing facility failed with the
error code shown.
Action: See the Action section of the error message shown.
CRS-01645: The initialization of the EXADATA fencing facility failed in
completion with error ORA-number; details at string in string
Cause: The completion of the initialization of the EXADATA fencing facility failed
with the error code shown.
CRS-01646: Creation of a EXADATA fence identifier failed with error ORAnumber; details at string in string
Cause: An attempt to create an identifier for a fence to an EXADATA device failed
with the error code shown.
CRS-01647: Initialization of a EXADATA fence failed with error ORA-number;
Cause: An attempt to initiate a fence to an EXADATA device failed with the error
code shown.
CRS-01648: Completion of queued EXADATA fence requests failed with error
ORA-number; details at string in string
Cause: Previously queued fence requests to an EXADATA device failed with the error
code shown.
CRS-01649: An I/O error occurred for voting file: string; details at string in string.
Cause: The listed voting file became inaccessible.
Action: Verify that the filesystem containing the listed voting file is available on the
local node.
CRS-01650: Configuration change number:number rejected by node number string;
Cause: A new configuration change request from this node was not accepted due to
another node rejecting the change.
Action: Check the CRS alert log of the node rejecting this configuration change for
more details.
CRS-01651: Configuration change number:number rejected because it would make

the active version of node number lower than the current setting string of this node;
Cause: A new configuration change request from another node was not accepted
because the new Active Version in the request is lower than this node's Active
Version.
Action: Ensure that the new Active Version is not lower than the current Active
Version of the nodes in the cluster.
CRS-01652: Starting clean up of CRSD resources.
Cause: Clean up of the resources registered in CRSD started.
Action: None
CRS-01653: The clean up of the CRSD resources failed.
Cause: Clean up of the resources registered in CRSD failed.
Action: Check the CRS alert log.
CRS-01654: Clean up of CRSD resources finished successfully.
Cause: Clean up of the resources registered in CRSD finished.
Action: None
CRS-01655: CSSD on node string detected a problem and started to shutdown.
Cause: The CSS daemon on the listed node detected a problem and started to
shutdown.
Action: Check the CRS alert log.
CRS-01656: The CSS daemon is terminating due to a fatal error; Details at string in
string
Cause: A fatal error occurred during CSS daemon processing.
Action: Check for prior errors logged in the alert log. Correct any errors that can be
corrected. If there are no errors shown, or the errors cannot be resolved, contact
Oracle support
CRS-01657: Unable to obtain the voting file discovery string; Details at string in
string
Cause: An attempt to obtain the voting file discovery string from the profile failed,
causing the CSS daemon to fail.
Action: Collect the Clusterware alert log and the CSSD log of this node as well as all
CSS daemon logs of all other nodes in the cluster and contact Oracle Support Services.
CRS-01658: There is a mismatch of the initial cluster incarnation among the cluster
nodes; Details at string in string
Action: Collect the Clusterware alert log and the CSSD log of this node as well as all
CRS-01659: An attempt to kill node string failed; Details at string in string
Cause: To protect data integrity a node kill was attempted for the indicated node, but
it failed.
Action: Collect the Clusterware alert log and the CSSD log of this node as well as the
CRS-00001 to CRS-29006 20-39
CRS-01660: The CSS daemon shutdown has completed

Cause: A command to shut down the CSS daemon was issued by a user and the
shutdown processing is completed. The CSS daemon is terminated.
Action: No action is required.
CRS-01661: The CSS daemon is not responding. Reboot will occur in number
milliseconds; Details at string in string
Cause: The CSS daemon is failing to respond.
Action: Collect the Clusterware alert log and the CSSD log of this node as well as the
CRS-01662: Member kill requested by node string for member number number,
group string
Cause: A request to kill a member of the indicated group was issued by a process on
the indicated node.
CRS-01663: Member kill issued by PID string for number members, group string.
Cause: A member kill request was issued by the indicated process for the members
belonging to the indicated group.
CRS-01664: No voting files found; switching node role to 'leaf'.
Cause: A node attempting to start as a Hub node was not able to find a voting file.
CRS-01665: maximum number of cluster Hub nodes reached; the CSS daemon is
terminating
Cause: A node attempting to start as a Hub node found the maximum number of Hub
nodes already active.
Action: If the configured node role is 'auto', no action is required for the node to
restart as a Leaf node. If the configured node role is 'hub', then the configured role
must be changed to a Leaf node using 'crsctl set node role leaf' or the Hub size must
be increased using 'crsctl set cluster hubsize'.
CRS-01666: no Hub nodes found; switching node role to 'hub'
Cause: A node attempting to start as a Leaf node was unable to locate any Hub nodes.
CRS-01667: node string not allowed to join because the maximum number of Hub
nodes has been reached
Cause: A node attempting to start as a Hub node found the maximum number of Hub
nodes already active.
CRS-01668: operation is not allowed on a Leaf node\n
Cause: An unsupported operation was requested on a Leaf node.
Action: Retry this operation on a Hub node.
CRS-01669: The number of voting files available number is less than the minimum
number of voting files required number.
Cause: The number of voting files has decreased to a number of files that is
insufficient.
Action: Look in the alert log for related messages such as 1714, 1604, 1613, 1614 and
1615 and act accordingly.
CRS-01670: Leaf node could not find any Hub nodes to connect to; details at string
in string
Cause: A Leaf node attempted to join the cluster but could not find a Hub node to
which to connect.
Action: Verify that the clusterware stack is up and running on at least one Hub node
and, if not, start the stack on one or more Hub nodes. Verify that the Grid Naming
Service (GNS) resource is active on a Hub node. If not, start it on at least one node.
Check if the network connectivity is viable to all Hub nodes that have the clusterware
stack running. If the Leaf node startup has exhausted its retry attempts, it may be
necessary to start the clusterware stack manually on the Leaf node. Contact Oracle
Support Services if all of the above is verified and the Leaf node is not able to find any
Hub nodes to which to to connect.
CRS-01671: The value for parameter string is outside the allowed range of number
to number\n
Cause: An attempt was made to set a parameter with invalid value.
Action: Set the parameter with a value in the indicated range.
CRS-01672: The number of voting files currently available number has fallen to the
minimum number of voting files required number.
Cause: The Cluster Synchronization Service daemon (CSSD) has detected that the
number of voting files currently available is equal to the minimum number of voting
files required on the node. There is risk of node eviction in the case of another voting
disk failure.
Action: Restore access to voting files or configure additional voting disks so that the
number of voting files currently available is more than the minimum number of
voting files required.
CRS-01701: Initialization of the required component GIPC failed; details at string
in string
Cause: The initialization of the communications component GIPC failed, causing the
CSSD startup to fail.
Action: Collect alert log and the CSSD log indicated in the message and contact Oracle
Support Services.
CRS-01702: Initialization of the required component OLR failed; details at string in
string
Cause: The initialization of the local repository component OLR failed, causing the
CSSD startup to fail.
Action: Collect clusterware alert log and daemon logs and contact Oracle Support
Services.
CRS-00001 to CRS-29006 20-41
CRS-01703: Initialization of the required component GPNP failed because the

GPNP server daemon is not up; details at string in string
Cause: The initialization of the configuration profile service failed because the
associated server is not up, causing the CSSD startup to fail.
Services.
CRS-01704: Initialization of the required component string failed; details at string
in string
Cause: The initialization of a component required by the CSS daemon failed, causing
the CSSD startup to fail
Services.
CRS-01705: Found number configured voting files but number voting files are
required, terminating to ensure data integrity; details at string in string
Cause: The voting file discovery was unable to locate a sufficient number of valid
voting files to guarantee data integrity and is terminating to avoid potential data
corruption.
Action: Delete the voting files that are no longer available, as indicated by message
number 1637, using appropriate 'crsctl' commands, run either on another node where
the clusterware stack is active, or by starting the clusterware stack in exclusive mode.
CRS-01706: Found number of number voting files in a pending configuration change
but number voting files are required, terminating to ensure data integrity; details at
string in string
Cause: The voting file discovery was unable to locate a sufficient number of voting
files from the new configuration when a configuration change to add or delete voting
files is in progress. The CSS daemon is terminating to avoid potential data corruption.
the clusterware stack is active, or by starting the clusterware stack in exclusive mode.
CRS-01707: Lease acquisition for node string number number completed
Cause: CSSD acquired a node number through a lease acquisition procedure.
Action: None
CRS-01708: Lease acquisition failed for node string because all lease slots are in
use; Details at string in string
Cause: The node failed to acquire a lease because all the lease slots were found to be
occupied by other nodes.
Action: Using olsnodes command get the list of leased nodes. Delete the unused
nodes using appropriate crsctl command.
CRS-01709: Lease acquisition failed for node string because no voting file has been
configured; Details at string in string
Cause: At least one voting file is required for CSSD to function properly. No voting
files have been configured.
Action: Add at lease one voting file using appropriate crsctl command.
CRS-01710: Lease acquisition failed for node string because CSSD failed to access
majority of voting files; Details at string in string
Cause: A majority of the voting files are not accessible by a node.
the Clusterware stack is active, or by starting the Clusterware stack in exclusive
mode.
CRS-01711: Increasing the number of leases available for new nodes from number
to number
Cause: All the currently available leases are being used. Hence the number of leases
available are increased.
Action: None
CRS-01712: Failed to save the node number acquired for node string; Details at
string in string
Cause: CSSD failed to save the node number acquired during startup. The node
number is saved to speed up the subsequent startup. Hence this is not a real problem
but just a performance degradation on the next startup.
Action: Collect Clusterware alert log, CSSD logs and OHASD logs indicated in the
message and contact Oracle Support Services.
CRS-01713: CSSD daemon is started in string mode
Cause: CSSD has been started on the node.
Action: None
CRS-01714: Unable to discover any voting files, retrying discovery in number
seconds; Details at string in string
Cause: No voting files were discovered. Possible reasons include: - The filesystems
the voting files are on are not available - The voting files have been deleted - The
voting files are corrupted
Action: Verify that the filesystems that the voting files are on are active and that the
voting files have not been damaged. If necessary, start the clusterware stack in
exclusive mode using 'crsctl start crs -excl' and add voting files using 'crsctl add css
votedisk'
CRS-01715: A failure occurred in the CSS daemon during initialization; Details at
string in string
Cause: A fatal error occurred during the initialization of the CSS daemon.
Action: Check for prior errors logged in the alert log. Correct any errors that can be
corrected. If there are no errors shown, or the errors cannot be resolved, contact
Oracle Support Services
CRS-01716: The CSS daemon cannot join the cluster because the software version
string is lower than the active version string; Details at string in string
Cause: The cluster has been upgraded to the active version indicated. in the message,
but this node is at a lower software version, as indicated in the message.
Action: Upgrade this node to the active version indicated in the message
CRS-00001 to CRS-29006 20-43
CRS-01717: The CSS daemon has detected a voting file add during startup and is
waiting for the add to complete; Details at string in string
Cause: A voting file add started on another node is in progress while this CSS
daemon is starting. To avoid the potential for data corruption, the CSS daemon on
this node must wait for the add to complete.
Action: This is normally a temporary condition that is automatically resolved. If the
clusterware stack cannot start on any node, this condition may be corrected by
starting the clusterware stack in exclusive mode using 'crsctl start crs -excl' followed
by 'crsctl stop crs' on one node. This will automatically correct the condition and the
clusterware can be started normally on all nodes.
CRS-01718: The CSS daemon is unable to continue due to a failure in required
component string.
Cause: A component required by the Cluster Synchronization Service (CSS) daemon
has failed. The CSS daemon is unable to continue and is failing.
Action: See the alert log for more detailed messages indicating the nature of the
problem and the location of additional information regarding this error.
CRS-01719: Cluster Synchronization Service daemon (CSSD) string not scheduled
for number msecs.
Cause: Excessive system load has prevented threads in the Cluster Synchronization
Service daemon (CSSD) from being scheduled for execution for the time indicated in
the message. This indicates the system is overloaded.
Action: Take steps to reduce the system load or increase system resources to handle
the load.
CRS-01801: Cluster string configured with nodes string.
Cause: None.
Action: None
CRS-01802: Node string added to cluster.
Cause: None.
Action: None
CRS-01803: Node string deleted from cluster.
Cause: None.
Action: None
CRS-01804: Node string upgraded to version string.
Cause: None.
Action: None
CRS-01805: Unable to connect to the CSS daemon, return code number
Cause: Could not initialize the CSS connection.
Action: Verify that the CSS daemon is running and restart it if it is not up. Retry the
operation.
CRS-01806: An error occurred when obtaining the node number of this host, return
code number
Cause: The request for node number of this node failed.
Action: Verify that the CSS daemon is running and restart it if not Retry the operation
that failed after restart. Look for error messages from the CSS daemon in the alert log
indicating any problems.
CRS-01807: An internal cluster configuration command failed in an OCR/OLR
operation. Details at string in string.
CRS-01808: Node-specific configuration for node string in Oracle Local Registry
was upgraded to version string.
Cause: None.
Action: None
CRS-01809: The cluster configuration command failed to open OCR or OLR key
string. Details at string in string.
Cause: An expected or required piece of configuration is missing from the cluster or
local registry.
Action: Use the ocrcheck utility to detect errors, and the ocrdump utility to review the
registry contents. If problems exist, the registry may need to be recovered or restored.
If the problem persists, contact Oracle Support Services.
CRS-01810: Node-specific configuration for node string in Oracle Local Registry
was patched to patch level number.
Cause: None.
Action: None
CRS-01811: Node string patched to patch level number.
Cause: None.
Action: None
CRS-01901: CRS service setting (string) is changed from [string] to [string].
Cause: None.
Action: None
CRS-02001: memory allocation error when initiating the connection
Cause: failed to allocate memory for the connection with the target process.
Action: None
CRS-02002: connection by user string to string refused
Cause: User command cannot connect to the target process.
Action: The user may not have sufficient privilege to connect.
CRS-02003: error number encountered when connecting to string
Cause: Connection to the target process failed.
Action: Examine whether the connection is made properly. Retry again at a later time
if necessary.
CRS-02004: error number encountered when sending messages to string
Cause: User command cannot communicate with the target process properly.
Action: Retry again at a later time.
CRS-00001 to CRS-29006 20-45
CRS-02005: timed out when waiting for response from string

Cause: the target process does not return acknowledgment in time.
CRS-02006: error number encountered when receiving messages from string
Cause: no meta or response message was received from the target process.
CRS-02007: invalid component key name <string> used
Cause: the given component key name could not be recognized.
Action: re-run the command with a valid component key name.
CRS-02008: invalid message type <number> used
Cause: an unrecognized message type was sent.
Action: Retry with a valid command again.
CRS-02009: unable to get authentication for user string
Cause: current user was not authenticated for connection.
Action: Log in as another user and try again.
CRS-02010: invalid response message from string
Cause: Response message has incorrect format.
CRS-02011: no response at index number in response message from string
Cause: Response message did not contain a response at the specified index.
Action: If this is an unexpected result, retry again at a later time.
CRS-02012: syntax error in command
Cause: The command syntax is not valid.
Action: Issue 'crsctl debug -h' to see command syntax details. Watch out for ',' vs. ';'.
CRS-02013: user string does not have the required privileges
Cause: An attempt to make a diagnostic connection to a Clusterware daemon failed
because the user does not have required privileges.
Action: Use system tools to identify the user of the specified daemon process. Log on
as the same user as the specified daemon process and try again.
CRS-02101: The OLR was formatted using version number.
Cause: Successfully formatted the OLR location(s).
Action: None
CRS-02102: The OLR was restored from file string.
Cause: The OLR was successfully restored from a backup file as requested by the
user.
Action: None
CRS-02103: The OLR format was downgraded to version number.
Cause: The OLR was successfully downgraded to an earlier block format as requested
by the user.
Action: None
CRS-02104: The OLR was imported from string.
Cause: Successfully imported the OLR contents from a file.
Action: None
CRS-02105: The OLR upgrade was completed. Version has changed from number to
number. Details in string.
Cause: The OLR was successfully upgraded to a newer block format.
Action: None
CRS-02106: The OLR location string is inaccessible. Details in string.
Cause: An error occurred while accessing the OLR.
Action: Use the "ocrcheck -local" command to validate the accessibility of the device
and its block integrity. Check that the OLR location in question has the correct
permissions.
CRS-02112: The OLR service started on node string.
Cause: The OLR was successfully started.
Action: None
CRS-02114: Failed to import Oracle Local Registry from file string
Cause: Unable to read data from the import file and import to the local registry
Action: Check availability of the local registry and the details of the failure from the
log file
CRS-02120: The Oracle Local Registry has invalid contents. Details at string in
string.
Cause: Some of the Oracle Local Registry contents were invalid.
Action: Check the log file indicated in the message for more details. Use the 'ocrcheck
-local' command to detect errors, and the 'ocrdump -local' command to review the
registry contents. If problems exist, the registry may need to be recovered or restored.
If the problem persists, contact Oracle Support Services.
CRS-02301: GPnP: string
Cause: This conveys a message from the GPnP layer to the alert log.
Action: Look up the imbedded message and respond accordingly.
CRS-02302: Cannot get GPnP profile. Error string (string).
Cause: Get GPnP profile operation failed.
Action: n/a
CRS-02303: GPNPD is not running on local node.
Cause: GPNPD is not running on local node. GPnP request cannot be completed.
Action: Make sure GPNPD is running and retry the operation.
CRS-02304: GPnP profile signature verification failed. string request aborted.
Cause: GPnP profile used in GPnP request or request result does not have a valid
signature.
CRS-00001 to CRS-29006 20-47
CRS-02305: GPnP resource discovery (MDNSD) is not running on local node.

Cause: GPnP resource discovery failed.
Action: Make sure resource discovery service (MDNSD) runs on local node.
CRS-02306: GPnP service on host "string" not found.
Cause: Remote GPnP service on requested host were not found in resource discovery
results.
Action: Make sure host is up, clusterware GPnP services (MDNSD and GPNPD) are
up and running and network connection is operational.
CRS-02310: Failed to initialize security facility.
Cause: Error occurred while initializing GPnP security component.
CRS-02311: Failed to initialize Resource Discovery. RD error: string. Make sure RD
providers installed properly.
Cause: Error occurred while initializing GPnP Resource Discovery (RD).
CRS-02312: Failed to initialize XML Developer's Kit (XDK). XDK error string.
Cause: Error occurred while initializing XML Developer's Kit component (XDK).
CRS-02313: Failed to initialize GIPC communication layer. GIPC error: string.
Cause: Error occurred while initializing GIPC communication layer.
CRS-02314: Cannot initialize locking subsystem.
Cause: Error occurred while initializing locking subsystem.
CRS-02315: Failed to initialize GPnP certkey providers.
Cause: GPnP certkey provider(s) data was not found or corrupt.
CRS-02316: Cannot initialize GPnP, string (string).
Cause: General GPnP initialization failure.
CRS-02317: Cannot get local GPnP security keys (wallet).
Cause: GPnP wallet(s) directory or files were not found or corrupt.
CRS-02318: GPNPD is not found.
Cause: Local GPnP service is not found.
Action: Make sure GPNPD is running.
CRS-02319: No cluster name found in GPnP profile.
Cause: Profile is invalid - it must specify a mandatory clustername parameter.
CRS-02320: No sequence number found in GPnP profile.

Cause: Profile is invalid - it must specify a mandatory profile sequence parameter.
CRS-02321: Flex Cluster mode configuration not found in Grid Plug and Play
(GPnP) profile.
Cause: The Profile did not have Flex Cluster mode configuration and could not be
used to bring up the stack in Flex Cluster mode.
CRS-02322: Cannot get local GPnP profile. Error initializing GPnP profile cache
providers.
Cause: Local GPnP setup was invalid.
CRS-02323: Error initializing one of the GPnP profile cache providers.
Cause: Local GPnP setup was invalid.
CRS-02324: Errors occurred while trying to push GPnP profile.
Cause: GPnP profile update partially failed.
Action: Try to repeat the update. If the problem persists, contact Oracle Support
Services.
CRS-02325: Unable to get GPnP profile from requested cluster nodes.
Cause: Get GPnP profile from remote nodes failed.
Services.
CRS-02326: GPnP profile is different across cluster nodes. string.
Cause: GPnP profile was different across cluster nodes.
Services.
CRS-02327: GPNPD already running on node string. Terminating.
Cause: GPnP service instance was already running on node.
Action: Bring down existing GPNPD instance first.
CRS-02328: GPNPD started on node string.
Cause: GPnP service started on node.
Action: None
CRS-02329: GPNPD on node string shut down.
Cause: GPnP service was shut down by request.
Action: None
CRS-02330: GPNPD failed to start listening for GPnP peers.
Cause: GPnP service failed to open server endpoint.
Action: Check GPNPD logs for the cause. If the problem persists, contact Oracle
Support Services.
CRS-00001 to CRS-29006 20-49
CRS-02331: Error getting GPnP profile from "string".

Cause: Get remote GPnP profile from remote node operation failed.
Action: Retry request. If the problem persists, contact Oracle Support Services.
CRS-02332: Error pushing GPnP profile to "string".
Cause: Push GPnP profile to remote node operation failed.
Action: Retry request. If the problem persists, contact Oracle Support Services.
CRS-02333: Could not write GPnP profile to local cache.
Cause: GPNPD service cannot save GPnP profile to local cache.
Action: Make sure there is at least 10MB of free disk space in Clusterware home. If the
CRS-02334: Could not delete pending GPnP profile from local cache.
Cause: GPNPD service cannot delete GPnP profile from local cache.
CRS-02335: Could not write pending GPnP profile to local cache.
Cause: GPNPD service cannot save GPnP profile to local cache.
Action: Make sure there is at least 10MB of free disk space in Clusterware home. If the
CRS-02336: GPNPD failed get local GPnP profile and cannot continue. Check
gpnpd/gpnp client logs.
Cause: GPnP service cannot find a profile in local cache, and cannot continue.
CRS-02339: GPNPD advertisement with string failed. This may block some cluster
configuration changes. Advertisement attempts will continue.
Cause: Grid Plug and Play Daemon (GPNPD) failed to advertise itself with a specified
service (for example, Multicast Domain Name Service Daemon (MDNSD) or Oracle
Grid Naming Service (GNS)). Advertisement attempts will continue at regular
intervals, and alerts will periodically be issued.
Action: Make sure the specified service is running and wait for the success message
CRS-2337 before changing the cluster configuration.
CRS-02340: Errors occurred while processing received gpnp message.
Cause: Invalid GPnP message received.
Action: Check gpnp client and GPNPD logs for details. If the problem persists,
CRS-02341: GPNPD on node string shutting down on signal number.
Cause: GPnP service shutting down due to received signal.
Action: Contact your cluster administrator.
CRS-02342: GPnP messaging received error : string (string).
Cause: GPnP message error received.
CRS-02401: The Cluster Time Synchronization Service started on host string.

Cause: The Cluster Time Synchronization Service successfully started on the listed
node.
Action: None
CRS-02402: The Cluster Time Synchronization Service aborted on host string.
Cause: The Cluster Time Synchronization Service aborted due to an internal error.
Check the Cluster Time Synchronization Service log file to determine the cause.
Action: Determine whether the Cluster Time Synchronization Service has autostarted.
CRS-02403: The Cluster Time Synchronization Service on host string is in observer
mode.
Cause: The Cluster Time Synchronization Service detected an active vendor time
synchronization service on at least one node in the cluster.
Action: Oracle Clusterware requires a time synchronization service in active mode.
Oracle Clusterware will work with a vendor service or the Cluster Time
Synchronization Service. If you want to change the Cluster Time Synchronization
Service to active mode, stop and deconfigure the vendor time synchronization service
on all nodes.
CRS-02404: The Cluster Time Synchronization Service detects that the local time is
significantly different from the mean cluster time. Details in string.
Cause: The difference between the local time and the time on the reference node was
too much to be corrected.
Action: Shutdown the Oracle Clusterware on the local node. Adjust the clock via
native platform or OS methods. Restart the Oracle Clusterware on the local node.
CRS-02405: The Cluster Time Synchronization Service on host string is shutdown
by user
Cause: The Cluster Time Synchronization Service on listed node was terminated by a
user.
Action: None
CRS-02406: The Cluster Time Synchronization Service timed out on host string.
Details in string.
Cause: A Cluster Time Synchronization Service action failed. The information from
the reference node was discarded.
problematic connections. If no network problems are found, 1. Run diagcollection.pl.
2. Contact Oracle Support Services.
CRS-02407: The new Cluster Time Synchronization Service reference node is host
string.
Cause: A new Cluster Time Synchronization Service reference node has been elected.
Action: None
CRS-02408: The clock on host string has been updated by the Cluster Time
Synchronization Service to be synchronous with the mean cluster time.
Cause: The clock was updated to be in sync with the mean cluster time.
Action: None
CRS-00001 to CRS-29006 20-51
CRS-02409: The clock on host string is not synchronous with the mean cluster time.
No action has been taken as the Cluster Time Synchronization Service is running
in observer mode.
Cause: The clock was not in sync with the mean cluster time. No action has been
taken as Cluster Time Synchronization Service is running in observer mode.
Action: Verify correct operation of the vendor time synchronization service on the
node.
CRS-02410: The Cluster Time Synchronization Service on host string is in active
mode.
Cause: The Cluster Time Synchronization Service did not detect an active vendor time
synchronization service on any node in the cluster.
Action: None. If a vendor time synchronization service is preferred to the Cluster
Time Synchronization Service, then configure and start the vendor time
synchronization service on all nodes to change the Cluster Time Synchronization
Service to observer mode.
CRS-02411: The Cluster Time Synchronization Service will take a long time to
perform time synchronization as local time is significantly different from mean
cluster time. Details in string.
too much to be synchronized in a short period.
Action: (Optional) Shutdown and restart the Oracle Clusterware on this node to
instantaneously synchronize the time with the reference node.
CRS-02412: The Cluster Time Synchronization Service detects that the local time is
significantly different from the mean cluster time. Details in string.
too large. No action has been taken as the Cluster Time Synchronization Service was
running in observer mode.
Action: Verify correct operation of the vendor time synchronization service on the
node. Alternatively, if you want to change the Cluster Time Synchronization Service
to active mode, stop and deconfigure the vendor time synchronization service on all
nodes.
CRS-02413: The Cluster Time Synchronization Service is unable to perform step
time synchronization due to high network latency with the reference node. The
local time is not significantly different from the mean cluster time. The Cluster
Time Synchronization Service is entering slew time synchronization mode.
Cause: The Cluster Time Synchronization Service experienced high network latency.
The local time was not significantly different from the mean cluster time; therefore,
the Cluster Time Synchronization Service will maintain the system time with slew
time synchronization.
Action: Determine the root cause of high network latency, and perform appropriate
repair if necessary.
CRS-02414: The Cluster Time Synchronization Service is unable to perform step
time synchronization due to high network latency with the reference node. The
local time is significantly different from the mean cluster time. The Cluster Time
Synchronization Service is aborting.
Cause: The Cluster Time Synchronization Service experienced high network latency.
The local time was significantly different from the mean cluster time; therefore, the
Cluster Time Synchronization Service is aborting.
Action: Shut down the Oracle Clusterware on the local node. Determine the root
cause of high network latency. Perform appropriate repair if necessary, then restart
the Oracle Clusterware on the local node.
CRS-02415: Resource 'string' cannot be registered because its owner 'string' is not
the same as the Oracle Restart user 'string'.
Cause: The resource indicated in the message could not be registered because it was
owned by a user other than the Oracle Restart user.
Action: Resubmit as the Oracle Restart user.
CRS-02500: Cannot stop resource 'string' as it is not running
Cause: A request to stop a resource that is not running was received.
Action: Check the current state of the resource, it should no longer be running.
CRS-02501: Resource 'string' is disabled
Cause: The resource is currently disabled and so may not be operated on.
Action: Enable the resource and re-submit your request.
CRS-02502: Resource 'string' has dependency error because of resource 'string'
Cause: The attempted operation has failed because of a dependency on the specified
resource.
Action: Ensure that the intended operation is still desired. If so, the specified resource
and its state need to be evaluated to decide on the corrective action.
CRS-02503: Resource 'string' is in UNKNOWN state and must be stopped first
Cause: The resource cannot be acted upon when it is in the UNKNOWN state.
Action: Stop the resource manually, make sure it is OFFLINE, and then re-submit the
request.
CRS-02504: Resource 'string' cannot be placed on any online servers that satisfy its
placement policy
Cause: The resource cannot be placed because of the constrains imposed by its
placement policy.
Action: Either change the placement policy of the resource or re-evaluate the request.
CRS-02505: Another operation is being performed on 'string'. Retry later
Cause: Another operation is being performed on the specified object.
Action: Typically, waiting and retrying or using a way to queue the request are the
two choices to proceed.
CRS-02506: Operation on 'string' has been cancelled
Cause: A scheduled or running operation has been cancelled.
Action: None
CRS-02507: Unsupported modifier 'string' in dependency 'string'
Cause: The modifier is not a valid one.
CRS-00001 to CRS-29006 20-53
Action: Check the specification of the dependency, fix the problem indicated, and
resubmit the request.
CRS-02508: Incomplete specification of dependency 'string'
Cause: The specification does not have the dependent object specified.
CRS-02509: Resource type 'string' used in dependency 'string' does not exist or is
not registered
Cause: The resource type referenced by the dependency specification is not found.
CRS-02510: Resource 'string' used in dependency 'string' does not exist or is not
registered
Cause: The resource referenced by the dependency specification is not found.
CRS-02511: Attribute 'string' cannot be specified on per-X basis for resource 'string'
Cause: The specified attribute is specified on per-X basis, which is not allowed for this
attribute.
Action: Remove the specification.
CRS-02512: Attribute format for 'string' is invalid in resource 'string'
Cause: The specification does not follow valid format.
Action: Correct the specification and re-submit the request.
CRS-02513: Attribute format for 'string' is invalid
Cause: The specification does not follow valid format.
CRS-02514: Dependency attribute specification 'string' is invalid in resource 'string'
Cause: The specification of relations does not follow valid format.
CRS-02515: Circular dependency found for resource 'string'
Cause: The resource dependency specification has a circular dependency.
Action: Circular dependencies are disallowed. Change the profile and re-submit.
CRS-02516: Server pool is not specified for resource 'string'
Cause: The resource profile does not have server pool specified.
Action: Either specify a an existing server pool or HOSTING_MEMBERS in the profile
and re-submit the request.
CRS-02517: Required attribute 'string' is not specified for resource 'string'
Cause: A required attribute is missing from the resource profile.
Action: Add the attribute to the profile and re-submit the request.
CRS-02519: Either 'string' or 'string' must be specified when 'string' is 'string'

Cause: Neither or both of the parameters was specified.
Action: Specify exactly one of the two and re-submit.
CRS-02520: Invalid value 'string' for attribute 'string'
Cause: The value specified for the attribute is inappropriate or invalid.
Action: Review the value, correct the problem and re-submit the request.
CRS-02521: Read-only attribute 'string' cannot be modified
Cause: An attempt was made to modify a read-only attribute.
Action: None
CRS-02522: No value is specified
Cause: There is nothing specified for the value.
Action: Provide a valid value.
CRS-02523: Invalid characters are used when specifying the value
Cause: 1 or more characters used to specify a value are inappropriate.
Action: Provide a valid value.
CRS-02524: Value specification may only contain
'string'/'string'/'string'/'string'/'string'/'string'
Cause: The value specified is not any of the allowed.
Action: The value must be one of the allowed ones, as specified. Provide a valid one.
CRS-02525: All instances of the resource 'string' are already running; relocate is not
allowed because the force option was not specified
Cause: All instances of the resource are running and the start request does not have
the force option specified.
Action: Either specify the force option or re-evaluate the need for the request.
CRS-02526: There are no available instances of resource 'string' to start on 'string'
Cause: All instances of the resource are already running or otherwise unavailable to
be started on the specified server.
Action: Create more instances or re-evaluate the need for the request.
CRS-02527: Unable to start 'string' because it has a 'string' dependency on 'string'
Cause: Start/relocate of the resource is impossible because it has a dependency on
another entity which prevents it from being able to start.
Action: This message will usually be coupled with another one that details the nature
of the problem with the other resource. Follow up on the action recommended for
that message.
CRS-02528: Unable to place an instance of 'string' as all possible servers are
occupied by the resource
Cause: Out of possible servers to place the resource on, all already host an instance of
the resource.
Action: You need to add more servers or change the resource placement parameters
to allow placement on additional servers.
CRS-00001 to CRS-29006 20-55
CRS-02529: Unable to act on 'string' because that would require stopping or

relocating 'string', but the force option was not specified
Cause: Acting on the resource requires stopping or relocating other resources, which
requires that force option be specified, and it is not.
Action: Re-evaluate the request and if it makes sense, set the force option and resubmit.
CRS-02530: Unable to stop 'string' because 'string' has a stop-time 'string'
dependency on it
Cause: Stopping the resource is impossible because it has a dependency on another
resource and there is a problem with that other resource.
that message.
CRS-02531: Internal error while operating on 'string'
Cause: General-purpose message for highly unexpected internal errors.
Action: This message will usually be preceded by another one with a more specific
problem description. Contact Oracle Support Services.
CRS-02532: OCR write failed for 'string'
Cause: Unknown, but would usually imply corruption or unavailability of the OCR
or a lack of permissions to update keys or a software defect in the OCR code.
Action: Validate that OCR is accessible, validate that key permissions match. Contact
CRS-02533: Server 'string' is down. Unable to perform the operation on 'string'
Cause: The server is down and therefore the operation cannot be performed.
Action: Try using a different server.
CRS-02534: Resource type 'string' is not registered
Cause: The specified resource type is not registered.
Action: Re-evaluate the request.
CRS-02535: Resource type 'string' does not have attribute 'string' and thus it cannot
be updated
Cause: An non-existing attribute cannot be modified.
CRS-02536: Required attribute 'string' is not specified for 'string'
Cause: A required attribute is missing from the entity's profile.
Action: Add the attribute to the profile and re-submit the request.
CRS-02537: Resource type 'string' cannot be extended directly; use its extensions
instead
Cause: The type cannot be extended.
Action: Use a type that extends this one.
CRS-02538: Value for attribute 'string' is of incorrect type (string is expected)
Cause: The type of the value is not correct.
Action: Re-submit the request with the value specified in proper type.
CRS-02539: A resource with the name 'string' is already registered

Cause: A resource with specified name is already registered.
Action: Use a unique name for the new resource.
CRS-02540: Value for attribute 'string' is of incorrect type (integer is expected)
Cause: The type of the value is not correct.
Action: Re-submit the request with the value specified in proper type.
CRS-02541: Server pool 'string' is not registered
Cause: The specified server pool is not registered.
CRS-02542: The tag 'string' is mentioned in both 'string' and 'string' attributes,
which is conflicting
Cause: The same tag is used to specify exclusive as well as overlapping server pools.
These requirements cannot be satisfied simultaneously.
Action: Remove the tag from one of the attributes.
CRS-02543: The type is not specified for attribute 'string'
Cause: Value type specification is missing for the attribute.
Action: Specify a proper type and re-submit.
CRS-02544: The name 'string' is longer than the allowed maximum of 'number'
characters
Cause: The name is too long.
Action: Use a shorter name.
CRS-02545: Cannot operate on 'string'. string
Cause: The entity specified is currently locked as part of another operation.
Action: Re-submit the request later.
CRS-02546: Server 'string' is not online
Cause: Operation is invalid because the specified server is not online.
Action: Provide an online server name.
CRS-02547: Update of an internal or read-only attribute 'string' for resource 'string'
is not allowed
Cause: Internal and read-only attributes may not be updated.
Action: Exclude internal and read-only attributes from your request.
CRS-02548: A cyclical dependency on 'string' is detected from 'string'
Cause: There is a cycle in the dependency graph. Cycles are disallowed.
Action: Re-evaluate the dependency graph.
CRS-02549: Resource 'string' cannot be placed on 'string' as it is not a valid
candidate as per the placement policy
Cause: The resource cannot be placed because of the constrains imposed by its
placement policy.
Action: Either change the placement policy of the resource or re-evaluate the request.
CRS-00001 to CRS-29006 20-57
CRS-02550: Resource 'string' cannot be failed-over because it has other nonOFFLINE instances on the server 'string'
Cause: The resource cannot be failed-over from the specified server because has other
non-OFFLINE instances still available on that server and fail-over can only be done
on all instances of the resource on the server as a whole.
Action: None
CRS-02551: Resource 'string' cannot be failed-over because it is of type 'string',
which cannot relocate
Cause: Local resources cannot be relocated from one server to another.
Action: None
CRS-02552: There are no available instances of resource 'string' to start.
Cause: All instances of the resource are in the ONLINE or UNKNOWN state.
Action: Re-evaluate the need for the request.
CRS-02553: Server pool 'string' cannot be unregistered as it does not exist
Cause: The server pool you are trying to remove does not exist.
Action: Make sure the server pool you are trying to remove exists.
CRS-02554: Server pool 'string' cannot be unregistered as it is referenced by
resource 'string'
Cause: The server pool you are trying to remove has references to it.
Action: Make sure the server pool you are trying to remove is not referenced by other
entities.
CRS-02555: Resource 'string' cannot be relocated as it is a local resource
Cause: The request is impossible to complete as local resources never relocate.
CRS-02556: Resource 'string' cannot be restored to its original state after a failed
relocate attempt
Cause: After an unsuccessful attempt to relocate a resource, crsd was unable to
restore the resource.
Action: Manual intervention may be required. Re-try starting the resource.
CRS-02557: Server pool 'string' cannot be unregistered as it is referenced by server
pool 'string'
Cause: The server pool you are trying to remove has references to it.
Action: Make sure the server pool you are trying to remove is not referenced by other
entities.
CRS-02558: Resource type 'string' may not be unregistered as there are types that
are based on it.
Cause: Types may not be unregistered if they have derived types.
Action: Remove derived types first, then remove this one.
CRS-02559: Resource type 'string' may not be unregistered as it has the following
resources:string
Cause: Types may not be unregistered if they have resources registered.
Action: Remove the specified resources first, then remove the type.
CRS-02560: Resource type 'string' does not exist

Cause: The resource type referenced does not exist.
Action: Specify a correct type.
CRS-02561: Resource type 'string' may not be unregistered as it is referenced by
resource 'string'
Cause: Types may not be unregistered if they are referenced in resource
dependencies.
Action: Make sure there are no existing resources that reference this type in their
dependencies.
CRS-02562: Resource 'string' cannot be relocated as it is not running
Cause: Only currently running resources can be relocated.
Action: Make sure the resource is running before issuing the request.
CRS-02563: Attempt to start resource 'string' on 'string' has failed. Will re-retry on
'string' now.
Cause: Undirected (no target member) start of a resource has failed for the server; a
retry is in progress.
Action: None, this is an informational message.
CRS-02564: Failed to relocate resource 'string'. Will attempt to restore it on 'string'
now.
Cause: Resource relocate operation was unable to relocate the resource to any of the
possible servers.
CRS-02565: Attempt to relocate resource 'string' to 'string' has failed. Will re-retry
on 'string' now.
Cause: Undirected (no target member) relocate of a resource has failed for the server;
a retry is in progress.
CRS-02566: User 'string' does not have sufficient permissions to operate on resource
'string', which is part of the dependency specification.
Cause: User does not have permissions to operate on the resource as it will prevent
the current resource from starting or staying online in future.
Action: The user performing the operation must have access privileges to operate on
the entire resource dependency tree. The user must either be given those privileges by
modifying the dependent resources' access rights or another user having permissions
should perform this operation.
CRS-02567: Error while parsing the default value for attribute 'string'
Cause: The default value specified is not proper.
Action: Make sure the value is proper for its type.
CRS-02568: Base resource type name 'string' does not exist
Cause: The name of a base type used is not valid.
Action: Use an existing type as a base.
CRS-00001 to CRS-29006 20-59
CRS-02569: Unsupported value type is used in attribute 'string'

Cause: An unsupported value type was specified in the attribute's definition.
Action: Use one of the supported types.
CRS-02570: Internal Error: Number of objects 'number' is different from number of
lists 'number'
CRS-02571: Dependency kind 'string' is specified more than once for resource
'string'
Cause: A dependency kind is used more than once in the profile of the resource.
Action: Combine multiple specifications of the same dependency kind into a single
clause.
CRS-02572: 'string' is not a supported Special Value
Cause: The specified identifier is not a valid Special Value.
Action: Check the value for correctness.
CRS-02573: ACL entry for owner field is missing.
Cause: The complete value for the ACL attribute has been provided but it is missing a
mandatory entry specifying permissions for the owner.
Action: Include permissions for the owner in the value of ACL attribute.
CRS-02574: ACL entry for primary group field is missing.
Cause: The complete value for the ACL attribute has been provided but it is missing a
mandatory entry specifying permissions for the primary group.
Action: Include permissions for the primary in the value of ACL attribute.
CRS-02575: ACL entry for users other than the owner and those belonging to
primary group is missing.
Cause: The ACL attribute is missing a mandatory entry specifying permissions for
users other than the owner and those belonging to the primary group.
Action: Include permissions for other users in the value of ACL attribute.
CRS-02576: User 'string' is not a member of group 'string'
Cause: The group that the caller claims to be a member of has no such user by
configuration.
Action: Make sure the group is configured to have the calling user as a member.
CRS-02577: Use of 'string' in attributes and values is not allowed
Cause: A disallowed character was detected.
Action: Retry without the disallowed character.
CRS-02578: Value of 'string' (number) may not be greater than that of 'string'
(number)
Cause: The specified values do not make sense - one may not be less than the other.
Action: Use valid values.
CRS-02579: Value 'number' may not be less than 'number'
Cause: The value is less than the allowed minimum.
Action: Use a proper value.

CRS-02580: Value 'number' is neither 'number' nor 'number'
Cause: The value must be one of the two and it is neither.
CRS-02581: Value 'string' is not any of the following 'string', 'string', 'string'
Cause: The value must be one of the ones specified and it is not.
CRS-02582: Value 'string' does not follow expected format: n[s|d|m|w|h]
Cause: The value specification does not follow required format.
CRS-02583: Value 'number' must be in the 'number' - 'number' range
Cause: The value is not within the allowed range.
CRS-02584: Value 'string' is not allowed here
Cause: The value is not proper in this context.
CRS-02585: Deletion of built-in resource types is not allowed
Cause: An attempt was made to delete a built-in resource type.
Action: Removal of built-in types is not allowed.
CRS-02586: Deletion of a running resource 'string' requires the force option
Cause: An attempt was made to delete a resource that is still running.
Action: Stop the resource first using the 'crsctl stop resource' command. If the
resource cannot be stopped, specify the force option to the 'crsctl delete' command.
CRS-02587: Attribute 'string' is internal and thus may not be overridden in type
'string'
Cause: Attributes defined in built-in resource types that are internal to the subsystem
may never be overridden in user-defined resource types.
Action: Do not specify this attribute in the new user-defined type.
CRS-02588: A cyclical dependency on 'string' is detected from 'string' via type
'string'
Cause: There is a cycle in the dependency graph, via a resource type. Cycles are
disallowed.
Action: Re-evaluate the dependency graph.
CRS-02589: Relation modifier 'string' is invalid for relation kind 'string'
Cause: An unexpected relation modifier is specified.
Action: Use defined modifiers only.
CRS-02590: A resource name may not be empty or contain spaces
Cause: A name must not be empty or contain space character(s).
Action: Specify a valid name.
CRS-00001 to CRS-29006 20-61
CRS-02591: A server pool name may not be empty or contain spaces

CRS-02592: A type name may not be empty or contain spaces
CRS-02593: Comparator value 'string' in the filter specification is not supported
Cause: An unsupported comparator was supplied.
Action: Use a supported value.
CRS-02594: Filter specification 'string' is invalid
Cause: The filter specification invalid or empty.
Action: Provide a valid filter or do not specify you have one.
CRS-02595: Server pool 'string' has already been registered
Cause: A server pool with this name has already been registered.
Action: Provide a name that is not currently in use.
CRS-02596: Modifications to the 'string' attribute of server pools are not supported
Cause: Changes to the value of the attribute are not allowed.
Action: Create a different pool with the desired value and use it.
CRS-02597: Server 'string' may not be moved to pool 'string'
Cause: Because of one or more of configuration-related constrains, the move of the
server is not a valid operation at the time.
Action: Re-evaluate the request's validity in the context of the entire error stack.
CRS-02598: Server pool 'string' is already at its maximum size of 'number'
Cause: The pool is already at the maximum.
Action: The request is impossible to execute.
CRS-02599: Server 'string' is not in a parent pool of 'string'
Cause: The server is not in a parent pool of the pool in question.
CRS-02600: Server 'string' is already in another top-level server pool
Cause: The server is already consumed by a different top-level pool and all such pools
are exclusive as far as server ownership.
CRS-02601: Server 'string' is not explicitly mentioned as a candidate by server pool
'string'
Cause: The server is not in the list of names the pool allows as candidates.
Action: Use a server that is in the specified group.
CRS-02602: Server 'string' is in server pool 'string' which is exclusive with server
pool 'string'
Cause: The server is already in a pool that's configured to be exclusive with the one at
hand.
CRS-02603: Server 'string' cannot be assigned to server pool 'string' because it is not
a top-level pool
Cause: Server movement is only supported between top-level server pools.
Action: The request is impossible to execute as such an action is not supported.
CRS-02604: Server 'string' is already assigned to server pool 'string'
Cause: Server movement makes no sense: the server is already in the target pool.
Action: Check the request validity.
CRS-02605: Server 'string' cannot be relocated from server pool 'string' because the
pool disallows transfers
Cause: The server pool is configured not to allow server transfers.
CRS-02606: Server 'string' may not be relocated from server pool 'string' because it
is not above its minimum size
Cause: Server pools of identical or higher importance may not be used to steal servers
from if they are not above their minimum size.
Action: Update the configuration of server pools by either changing the importance or
the minimum size or both and then re-submit the request.
CRS-02607: Attribute 'string' has not been specified on per-X basis for resource
'string'
Cause: The specified attribute has not been specified on per-X basis for this resource.
Action: Check the per-X attribute for the resource, fix and resubmit.
CRS-02608: Attribute 'string' is not a per-X value and cannot be removed
Cause: The specified attribute is not a per-X value.
Action: Check the per-X attribute for the resource, fix and resubmit.
CRS-02609: Server 'string' may not be relocated to server pool 'string' as the pool
disallows transfers
Cause: The server pool is configured not to allow server transfers.
CRS-02610: Server 'string' is unavailable
Cause: The server is not available at the moment.
Action: Check available servers and rerun the request with an active server.
CRS-02611: Server pool 'string' is built-in and may not be deleted
Cause: Built-in server pools may never be deleted.
Action: None
CRS-00001 to CRS-29006 20-63
CRS-02612: Server pools do not have attribute named 'string'

Cause: An unsupported attribute was provided as part of the register or update
request.
Action: Double check the attributes that are supplied.
CRS-02613: Could not find resource 'string'.
Cause: An attempt was made to operate on a resource that is not registered.
Action: Check if the resource is registered.
CRS-02614: Could not find resource type 'string'.
Cause: An attempt was made to operate on a resource type that is not registered.
Action: Check if the resource type is registered.
CRS-02615: Could not find server pool 'string'.
Cause: An attempt was made to operate on a server pool that is not registered.
Action: Check if the server pool is registered.
CRS-02616: The owner of resource type 'string' does not have sufficient
permissions to operate on resource type 'string', from which it is directly or
indirectly derived.
Cause: Update of a resource type in the current manner is not allowed as it will
severely limit operations on the current resource type and will potentially prevent
resources of derived types from starting or staying online in future.
Action: If access privileges must be changed, then they need to changed bottom-up in
a dependency.
CRS-02617: Incorrect value of attribute flags has been specified for attribute string.
Only READONLY flag can be changed for a type attribute.
Cause: Attempt was made to update the flag on a resource type attribute. The only
change allowed is to the readonly property of the attribute.
Action: Provide correct value of the attribute flag.
CRS-02618: Cannot change data type string of existing attribute string to type
string.
Cause: Attempt was made to update the data type of attribute value.
Action: Data type of the attribute cannot be changed.
CRS-02619: Server pool 'string' may not be edited
Cause: The pool's attributes may not be edited.
Action: None
CRS-02620: Attribute 'string' of server pool 'string' may not be edited
Cause: Editing of the attribute of the server pool is not allowed.
Action: None
CRS-02621: Server 'string' is assigned to 'string' to which you have no permission.
The operation is not authorized.
Cause: The operation requires making the specified server a placement candidate for
the resources owned by the requesting user. However, this is not allowed because the
user is not authorized to utilize the server.
Action: Either specify another server that that's in the pool you are authorized to use
or request that a cluster administrator gives you access to the pool to which the server
is currently assigned.
CRS-02622: Server 'string' is not assigned to any server pool and thus may only be
specified by a cluster administrator
Cause: The operation makes use of the server that's not currently assigned to a server
pool and the requesting user is not a cluster administrator. Because of that use of the
server cannot be authorized at the moment.
Action: Either request a cluster administrator to perform the operation for you or wait
until the server has joined the cluster and is assigned to a pool to which you have an
x-permission.
CRS-02623: Server pool 'string' cannot accept server 'string' because its name is not
specified in 'string'
Cause: Only servers whose names are mentioned in the attribute may be assigned to
the pool.
Action: None
CRS-02624: One of 'string', 'string' must be specified when 'string' is 'string'
Cause: Neither of the parameters was specified.
Action: Specify either of the two and re-submit.
CRS-02625: Owner of resource 'string' does not have execute permission to pool
'string' and may not use it
Cause: Resource profile references a server pool to which the owner of the resource
does not have the X-permission.
Action: Either have the pool's permission changed appropriately or use a different
pool.
CRS-02626: Owner of server pool 'string' does not have execute permission to
parent server pool 'string'
Cause: Parent pool does not have the X-permission for the pool's parent.
Action: Either have the desired parent pool's permission changed appropriately or
use a different pool.
CRS-02627: You must have execute permission on pool 'string' to relocate server
'string'
Cause: The client requesting the operation does not have proper permissions to the
specified pool.
Action: Acquire required permissions or use another server/pool. Permissions can be
added by an authorized user using 'crsctl setperm' command.
CRS-02628: Server pool 'string' may not be a parent of itself
Cause: An attempt was made to make a server pool a parent of itself.
Action: Re-evaluate the server pool dependencies.
CRS-02629: Only cluster administrators are allowed to create top-level server pools
Cause: An attempt was made to create a server pool that has no parent pools.
Creation of such pools is only allowed for cluster administrators.
Action: Either acquire the role of cluster administrator or have one create the pool for
you.
CRS-00001 to CRS-29006 20-65
CRS-02630: Only cluster administrators are allowed to create local resources

Cause: An attempt was made to create a local resource which is only allowed for
cluster administrators.
Action: Either acquire the role of cluster administrator or have one create the resource
for you.
CRS-02631: Only cluster administrators are allowed to create cluster resources that
may run anywhere in the cluster
Cause: An attempt was made to create a cluster resource that may run anywhere in
the cluster which is only for cluster administrators.
Action: Either acquire the role of cluster administrator or have one create the resource
for you.
CRS-02632: There are no more servers to try to place resource 'string' on that would
satisfy its placement policy
Cause: After one or more attempts, the system ran out of servers that can be used to
place the resource and satisfy its placement policy.
Action: None
CRS-02640: Required resource 'string' is missing.
Cause: A resource that's configured as required is not registered.
Action: Register the missing resource or update the dependency specification so as to
the missing resource is not required for start.
CRS-02641: The value of 'string' cannot override that defined in the resource's type:
'string'
Cause: Agent filename cannot be overridden on per-resource basis.
Action: Define a sub-type that uses the agent. Then create a resource of this new type.
CRS-02642: Relocate resource is not a valid command for this configuration
Cause: A relocate command was issued in the configuration where it is not possible in
principle.
Action: None
CRS-02643: The server pool(s) where resource 'string' could run have no servers
Cause: All of the server pools the resource uses (and has permissions to use) have no
servers assigned.
Action: Either make sure there are active servers in the pools or use different pools for
the resource.
CRS-02644: No hosting members of 'string' are either online or are allowed to be
used by the resource
Cause: No server out of the enumerated as hosting members is online or, if it is, may
be used by the resource.
Action: You need to either add more servers into the cluster or request permission to
pools to which currently available servers are assigned.
CRS-02645: Cannot create resources of type 'string'
Cause: The type is abstract.
Action: Only concrete extensions of the type can be created.
CRS-02646: 'string' must have a default value if specified

Cause: This attribute must have a default value if specified.
Action: Modify the type definition so that the attribute is removed or has a valid
default value.
CRS-02647: Attribute 'string' may not be a negative value
Cause: A negative value was provided for an attribute which only accepts nonnegative values.
Action: Specify a non-negative number.
CRS-02648: Configuration of resource 'string' prevents it from starting on any
online servers.
Cause: An attempt was made to start a resource, but the resource configuration
prevented it from starting.
Action: Check resource configuration.
CRS-02649: Attribute 'string' of 'string' is internally managed and may not be
specified
Cause: An internal attribute was specified as part of an add/modify request.
Action: Re-execute the request without any internal attribute.
CRS-02650: Resource 'string' is configured to run only on 'string' and cannot be
started on 'string'
Cause: An attempt was made to start a resource on a server where it cannot run given
its placement configuration.
Action: Make sure you start resources where they are configured to run.
CRS-02651: Resource alias 'string' must use special values to be unique for each
server
Cause: Resource alias name must resolve to a unique identifier for every server in the
cluster. To achieve that, special values that yield different values on for each server
must be used.
Action: You need to special an alias with special variables that will make it unique for
every server.
CRS-02652: string is a resource and only resource instances can be relocated.
Cause: An attempt was made to relocate a resource.
Action: Make sure you supply a resource instance rather than a resource.
CRS-02653: Special value evaluation must be associated with a resource instance
Cause: Because some special values are per-server, each special value evaluation
request must be associated with a resource instance.
Action: Specify a server for the resource using -k or -n.
CRS-02660: Resource 'string' or all of its instances are disabled
Cause: This is an API return code for requests that cannot be performed because the
resource is disabled.
Action: Look at the detailed error messages that should always accompany this error.
CRS-02661: All instances of resource 'string' are disabled
Cause: All instances of the resource instances are disabled.
CRS-00001 to CRS-29006 20-67
Action: In order to change a resource state through CRS, its instances need to be
enabled.
CRS-02662: Resource 'string' is disabled on server 'string'
Cause: The resource was disabled on the specified server.
Action: Either re-enable, or use a different server.
CRS-02663: Resource instance of 'string' with string=number, string=number is
disabled
Cause: The resource instance whose cardinality/degree is specified is disabled.
Action: Either re-enable or use a different resource instance.
CRS-02664: Resource 'string' is already running on 'string'
Cause: The resource is already running everywhere it may run.
Action: None
CRS-02665: Resource 'string' is disabled on 'string'
Cause: The resource is disabled on every server it is configured to start on.
Action: None
CRS-02666: Resource 'string' is disabled on 'string' and is already running on
'string'
Cause: The resource is disabled on every server it is configured to start on.
Action: None
CRS-02667: Resource 'string' with string=string may only run on servers assigned to
string and string, both of which are empty
Cause: The resource's placement policy only allows it to run on servers assigned to
the specified pools, and they are all empty.
Action: Either change the placement policy of the resource, or change the cluster
configuration so that there are servers in those pools.
CRS-02668: The value of attribute 'string' (number) may not not be above 'number'
Cause: Attribute value specified is above the allowed maximum.
Action: Use a value below the specified maximum.
CRS-02669: The value is out of range. Maximum allowed value is 'number'
Cause: Attribute value is out of the valid range.
Action: The value needs to be in a valid range.
CRS-02670: Unable to start/relocate 'string' because 'string' has a stop-time 'string'
dependency on it
Cause: Start/relocate of the resource is impossible because another resource has a
stop-time dependency on it and the action requires stopping that resources.
that message.
CRS-02671: Error processing attribute 'string': string
Cause: The value specified for the attribute is inappropriate or invalid.
Action: Review the value, correct the problem and re-submit the request.
CRS-02672: Attempting to start 'string' on 'string'

Action: None
CRS-02673: Attempting to stop 'string' on 'string'
Action: None
CRS-02674: Start of 'string' on 'string' failed
Action: None
CRS-02675: Stop of 'string' on 'string' failed
Action: None
CRS-02676: Start of 'string' on 'string' succeeded
Action: None
CRS-02677: Stop of 'string' on 'string' succeeded
Action: None
CRS-02678: 'string' on 'string' has experienced an unrecoverable failure
Action: Perform whatever steps necessary to reset the state.
CRS-02679: Attempting to clean 'string' on 'string'
Action: None
CRS-02680: Clean of 'string' on 'string' failed
Action: None
CRS-02681: Clean of 'string' on 'string' succeeded
Action: None
CRS-02682: It is locked by 'string' for command 'string' issued from 'string'
Cause: This message is generated for operations that have a locking conflict.
Action: None
CRS-02683: It is locked by 'string' for command 'string'
Cause: This message is generated for operations that have a locking conflict.
Action: None
CRS-02714: 'string' is specified multiple times in 'string' of 'string'
Cause: The specified value is specified multiple times.
CRS-00001 to CRS-29006 20-69
Action: Remove duplicates and retry.

CRS-02715: Update to attribute AGENT_FILENAME is not currently supported.
Recreate the resource type with new value.
Cause: Attempt was made to update AGENT_FILENAME attribute.
Action: Delete existing resource type and add it back with the new value.
CRS-02716: Failure threshold exhausted for resource 'string'
Cause: The resource instance has failed more times than allowed in the specified time
interval. It will not be restarted automatically.
Action: Identify and fix the problem. Restart the resource manually thereafter.
CRS-02717: Server 'string' is not in any of the server pool(s) hosting resource 'string'
Cause: An attempt was made to start a resource on a server that is not currently an
active server in any of the resource's server pool(s).
Action: Use a server name that is currently an active server of the resource's server
pools(s).
CRS-02718: Server 'string' is not a hosting member of resource 'string'
Cause: An attempt was made to start the resource on a server not listed as a hosting
member of the resource.
Action: Use a server name that is listed as a hosting member.
CRS-02719: Resource 'string' may not be started on server 'string' because the server
is not in either 'string' or 'string' server pools
Cause: The resource's placement policy only allows it to run in the specified server
pools. An attempt was made to start it on a server assigned to a different pool.
Action: Either use a different server or set the value of SERVER_POOLS to *, which
will allow the resource to run on any server.
CRS-02720: 'string' is a resource alias for 'string' and cannot be updated
Cause: An attempt was made to update a resource as if it were a resource.
Action: Update the resource which this alias refers to instead.
CRS-02721: 'string' is a resource alias for 'string' and cannot be unregistered
Cause: An attempt was made to unregister a resource alias as if it were a resource.
Action: Either unregister the resource which this alias refers to or modify its
ALIAS_NAME attribute to not have a resource alias.
CRS-02722: The instance of resource 'string' may only run on 'string'; check on
'string' is unnecessary
Cause: A check was issued on a server for a resource instance that may only run on a
particular server.
Action: Issue a check on the server where the resource instance is supposed to be run.
CRS-02723: No instance of resource 'string' found on 'string'
Cause: A check was issued on a server for a resource which does not have any offline
instances and no running instances on that server.
Action: Issue a check on a server where a resource instance might be running.
CRS-02724: Modifications to the built-in resource type 'string' are not allowed
Cause: An attempt was made to modify a built-in resource type.
Action: Modification of built-in resource types is not allowed.

CRS-02725: User string does not have permission to operate on resource string.
Cause: Access control list on the resource do not permit the user to operate on the
resource.
Action: Access privileges on the resource must be honored or this user must be given
appropriate permissions.
CRS-02726: Invalid permissions specified for access control.
Cause: Access permissions are specifies using 'r', 'w', 'x' and '-' characters to indicate
read, write and execute permissions. '-' indicates no access of any kind.
Action: Check format for the permissions string and re-run the command with the
correct string.
CRS-02727: Acl entry 'string' has been specified more than once.
Cause: Access permissions for the entry have been specified more than once.
Action: Specify permissions for each entry only once and rerun the command.
CRS-02728: A resource type with the name 'string' is already registered
Cause: A resource type with such name is already registered.
Action: Use a unique name for the new resource type.
CRS-02729: Attribute 'string' cannot be overridden for a resource type
Cause: An attribute was specified that is not allowed in a resource type.
Action: Do not use the attribute specified in the error message for a resource type.
CRS-02730: Resource 'string' depends on resource 'string'
Cause: An attempt was made to unregister a resource that is referenced by another
resource in the dependency specification(s).
Action: Either remove the reference to this resource or the other resource first.
Alternatively, the operation can be retried with a force option.
CRS-02731: Resource 'string' is already running on server 'string'
Cause: The resource is already running on the server; relocate is impossible.
Action: Select another server.
CRS-02732: Resource 'string' is already starting on server 'string'
Cause: The resource is currently starting on the server.
Action: Wait for the request to complete.
CRS-02733: Failed to stop all required resources on 'string'; the server will be
restored into the original server pool(s)
Cause: In order to successfully relocate a server, all resources that cannot run in the
new server pool(s) must be stopped. That did not happen and thus the server was
placed back into the its original server pool(s).
Action: Manual intervention in stopping resources is required. The operation can be
retried thereafter. Alternatively, another server can be used.
CRS-02734: Failed to stop all required resources on 'string'; the server will stay in
RECONFIGURING state
new server pool(s) must be stopped. Since that did not happen, the server will be kept
CRS-00001 to CRS-29006 20-71
in the RECONFIGURING state until the resources that did not stop have been
stopped or unregistered.
Action: Manually stop the resources that did not stop or unregister them.
CRS-02735: The operation requires relocating resource 'string' from server 'string'
Cause: The operation would end up relocating the resource and the force option is not
specified.
Action: Add more servers to the cluster, stop or relocate the resource, or use the force
option for the same command.
CRS-02736: The operation requires stopping resource 'string' on server 'string'
Cause: The operation would end up stopping the resource and the force option is not
specified.
Action: Add more servers to the cluster, stop or relocate the resource, or use the force
option for the same command.
CRS-02737: Unable to register server pool 'string' as this will affect running
resources, but the force option was not specified
Cause: One or more running resources would be affected by the operation.
Action: Add more servers to the cluster, stop or relocate the resources mentioned
right before this error, or use the force option for the same command.
CRS-02738: Unable to modify server pool 'string' as this will affect running
resources, but the force option was not specified
CRS-02739: Unable to relocate server 'string' as this will affect running resources,
but the force option was not specified
right before this error, use a different server, or use the force option for the same
command.
CRS-02740: Failed to relocate server 'string' to server pool 'string'. The server has
been restored to original server pool(s).
new server pool(s) must be stopped. That did not happen and thus the server was
placed back into the its original server pool(s).
Action: Manual intervention in stopping or unregistering resources is required. The
operation can be retried thereafter. Alternatively, another server can be used.
CRS-02741: A value must be specified for attribute 'string'
Cause: The attribute was not given a value.
Action: Provide a value and retry.
CRS-02742: The update of resource 'string' would lose track of one or more running
instances
Cause: An attempt was made to modify the configuration of the resource such that
one or more currently running instance will be lost track of (the new configuration
would change the resource to have fewer instances).
Action: Stop the resource and resubmit.

CRS-02743: Unable to register resource 'string' as this will affect running resources,
CRS-02744: Unable to modify resource 'string' as this will affect running resources,
CRS-02745: Unable to relocate server string because it results in violation of a pool
string constraint
Cause: The requested move was rejected because it would cause either the source or
target pool (or both) to violate a pool size constraint, as indicated.
Action: Either change the pool size constraint(s) to accommodate your intent with this
move, or choose a different server to move.
CRS-02746: Cannot act on the instance of resource 'string' which is last known to
have run on 'string' where Cluster Ready Services are not properly functioning
Cause: The resource had been running on the server in the past but currently there's
no way to know if it's still running there because the Cluster Ready Services daemon
does not appear to be running on the server. To prevent possible configuration
violation, any attempt to start the resource instance on another server is rejected.
Action: The underlying problem preventing Cluster Resource Services on the server
from functioning properly must be addressed. Only then the resources that used to
run there can be operated on again. Alternatively, the server may be shut down or the
clusterware stack on it stopped completely.
CRS-02747: Server reconfiguration has failed to stop resources 'string' on server
'string'. Resources that did not stop must be stopped or unregistered manually.
Cause: The specified resources could not be stopped.
Action: Stop the specified resources manually using and retry the last action.
CRS-02748: Failed to stop resource 'string' during server reconfiguration on server
'string'.
Action: Stop the specified resources manually and retry the last action.
CRS-02749: A write of OCR server data 'string' failed. Details at string in string.
Cause: Could not persist data to OCR.
Action: Use the ocrconfig and ocrcheck utilities to detect errors in OCR. If problems
exist, the registry may need to be recovered or restored.
CRS-02750: Cardinality violation detected on server 'string', resource 'string' is in
unexpected state. Details at string in string.
Cause: The specified resource was in an unexpected state.
Action: Manually restart the resource.
CRS-00001 to CRS-29006 20-73
CRS-02751: Cannot create new resource, the resource type 'string' is not supported.
Cause: The specified resource had an incorrect base type.
Action: Check the attributes for the resource and add it using crsctl again.
CRS-02752: Unable to write event sequence number to OCR. Details at string in
string.
Cause: Could not update OCR with event sequence number.
CRS-02753: Timed out waiting for the server pools to be unfrozen.
Cause: Timed out while waiting for a client to unfreeze the pools it froze.
CRS-02754: Unable to change locks for a running operation 'string'. Details at string
in string.
CRS-02755: Error reading type definition for type 'string'. Details at string in string.
CRS-02756: Invalid tag for command 'string'. Details at string in string.
Cause: An invalid command was received by the CRS daemon.
CRS-02757: Command 'string' timed out waiting for response from the resource
Cause: Timeout occurred while waiting for response to specified command.
Action: Check that the server targeted by the command is online and responsive.
CRS-02758: Resource 'string' is in an unknown state.
Cause: Unable to determine the current state of specified resource.
Action: Manually restart the resource.
CRS-02759: Failed to read repository key for NLS language 'string'. Details at string
in string.
Cause: The key for the specified language could not be read from OCR.
CRS-02760: Policy engine failed to initialize internal types. Details at string in
string.
Cause: Error during initialization of internal data.
CRS-02761: Consistency problem in registry while processing resource 'string'.

CRS-02762: Unable to find type 'string' in registry while processing resource
Action: Contact Oracle Support Services
CRS-02763: Error while reading resources. Details at string in string.
CRS-02764: CRSADMIN and CRSUSER keys are not in repository. Details at string
in string.
Cause: Error with repository. Required keys are not present.
CRS-02765: Resource 'string' has failed on server 'string'.
Cause: The specified resource was no longer running.
Action: The resource will be automatically brought back online. Use crsctl to confirm
that it is online.
CRS-02766: Received state change for disabled resource 'string' from server 'string'.
Cause: Received command to change state for a resource that was disabled.
Action: None
CRS-02767: Resource state recovery not attempted for 'string' as its target state is
OFFLINE
Cause: Target state for resource was OFFLINE. Clusterware will not attempt to
recover it.
Action: None
CRS-02768: Failure threshold exhausted by resource 'string'.
Cause: The specified resource failed too many times. No further restart attempts will
be made.
Action: Fix the underlying cause of resource failure and manually restart the resource.
CRS-02769: Unable to failover resource 'string'.
Cause: Could not failover the specified resource.
Action: Restart the resource manually.
CRS-02770: Resource target 'string' is offline; will not restart.
Cause: The target state of the specified resource was offline.
Action: None
CRS-02771: Maximum restart attempts reached for resource 'string'; will not restart.
Cause: Specified resource had been restarted too many times.
Action: Change the maximum restart parameter of the resource, and restart it
manually.
CRS-00001 to CRS-29006 20-75
CRS-02772: Server 'string' has been assigned to pool 'string'.

Cause: The specified server had been assigned to a server pool.
Action: None
CRS-02773: Server 'string' has been removed from pool 'string'.
Cause: The specified server had been removed from a server pool.
Action: None
CRS-02774: Failed to save resource 'string' to the repository. Details at string in
string.
Cause: Could not update repository with resource details.
Action: Use the ocrcheck utility to detect errors in OCR. If problems exist, the registry
may need to be recovered or restored.
CRS-02775: Failed to update resource 'string'. Details at string in string.
CRS-02776: Failed to update server pool 'string'. Details at string in string.
Cause: Could not update repository with server pool details.
CRS-02777: Failed to delete resource 'string' from repository. Details at string in
string.
Cause: Unable to update resource details in repository.
CRS-02778: Failed to delete server pool 'string' from repository. Details at string in
string.
CRS-02779: Failed to delete type 'string' from repository. Details at string in string.
Cause: Failed to update repository.
CRS-02780: Could not find Access Control List for resource 'string'. Details at string
in string.
CRS-02781: Error during registration for resource 'string'. Details at string in string.
Cause: Error occurred during registration callback of new resource.
CRS-02782: Unable to find attributes for resource 'string'. Details at string in string.
CRS-02783: Internal error in local placement policy for resource 'string'. Details at
string in string.
Cause: Internal error in CRS Policy Engine.
CRS-02784: Internal error, invalid server 'string' in local placement policy. Details
Cause: Internal error in CRS Policy Engine.
CRS-02785: Failed to register resource 'string'. Details at string in string.
CRS-02786: Failed to register server pool 'string'. Details at string in string.
CRS-02787: Server pool 'string' has fallen below its minimum size. Details at string
in string.
Cause: The specified server pool has fallen below its minimum size and will be
reconfigured.
Action: None
CRS-02788: Server reconfiguration failed to stop resources 'string'. The server
'string' has been restored into the original pool(s).
Action: Stop the specified resources manually and retry the last action.
CRS-02789: Cannot stop resource 'string' as it is not running on server 'string'
Cause: An request to stop a resource on a server where it is not running was received
Action: Check the current state of the resource; it should no longer be running on that
server.
CRS-02790: Starting shutdown of Cluster Ready Services-managed resources on
'string'
Cause: Shutdown of Cluster Ready Services and the resources it manages has started
on the specified server.
Action: None
CRS-02791: Starting shutdown of Oracle High Availability Services-managed
resources on 'string'
Cause: Shutdown of Oracle High Availability Services and the resources it manages
has started on the indicated server.
Action: None
CRS-00001 to CRS-29006 20-77
CRS-02792: Shutdown of Cluster Ready Services-managed resources on 'string' has

completed
Cause: Shutdown of Cluster Ready Services and the resources it manages on the
indicated server has completed.
Action: None
CRS-02793: Shutdown of Oracle High Availability Services-managed resources on
'string' has completed
Cause: Shutdown of Oracle High Availability Services and the resources it manages
has completed on the indicated server.
Action: None
CRS-02794: Shutdown of Cluster Ready Services-managed resources on 'string' has
failed
Cause: The failure is associated with one or more of the resources affected by this
command on the indicated server."
Action: Error message(s) preceding this one should have the details about the
resources that refused to shut down. Either manually stop those resources or retry
with the force option.
CRS-02795: Shutdown of Oracle High Availability Services-managed resources on
'string' has failed
Cause: The failure is associated with one or more of the resources affected by this
command on the indicated server."
CRS-02796: The command may not proceed when Cluster Ready Services is not
running
Cause: This command must stop Cluster Ready Services-managed resources.
However, Cluster Ready Services is not running, which does not mean its resources
are not running.
Action: The underlying reason for Cluster Ready Services not running needs to be
resolved and the command retried. Alternatively, the command can be retried with
the force option.
CRS-02797: Shutdown is already in progress for 'string', waiting for it to complete
Cause: Another shutdown command was issued for the indicated server in the past
and it is currently in progress. This command will wait until the original command
completes and then complete as well.
Action: None
CRS-02798: State change received for resource 'string' from unexpected server
'string'. Details at 'string' in 'string'.
Cause: A state change was reported for an instance of the resource from a server
where the resource was never started.
Action: Shutdown the resource on the unexpected server
CRS-02799: Failed to shut down resource 'string' on 'string'
Cause: Shut down failed because the listed resource failed to stop.
CRS-02800: Cannot start resource 'string' as it is already in the INTERMEDIATE
state on server 'string'
Cause: An attempt was made to start a resource that is already in the
INTERMEDIATE state.
Action: Determine why the resource is in the INTERMEDIATE state based on the
value of the STATE_DETAILS attribute. If it is due to a check timeout, no action is
needed. Otherwise, manual intervention is required to bring the resource out of the
INTERMEDIATE state.
CRS-02801: No instance of the resource 'string' should be running
Cause: An attempt was made to relocate resource and the resource's instances to be
relocated have TARGET=OFFLINE.
Action: Restart the resource to change the value of the TARGET attribute to ONLINE.
Examining the value of the INTERNAL_STATE attribute can be used to determine if
the instances are being operated on currently.
CRS-02802: Purging events not published within 15 minutes
Cause: The events could not be published to the Event Manager Daemon either
because it is down or there are errors doing the publish.
Action: Check the status of the Event Manager Daemon.
CRS-02803: Attribute 'string' has already been declared in a derived type 'string'
Cause: An attempt was made to add a new attribute definition to a resource type that
has an identically named attribute already defined in one or more derived types.
Attributes declared in base types can be overridden in derived ones, but the opposite
is not allowed.
Action: Pick a different attribute name or delete the derived type(s), resubmit, and
then add derived types back.
CRS-02805: Unable to start 'string' because it has a 'string' dependency on resource
type 'string' and no resource of that type can satisfy the dependency
Cause: Start/relocate of the resource is impossible because it has a dependency on a
resource type no resource of which can currently be used to satisfy the dependency.
Action: This message will normally be coupled with one or more other messages that
detail the nature of the problem for each existing resource of the type.
CRS-02806: Failed to create stop operation for resource 'string'
Cause: Creating the stop operation did not complete successfully.
Action: Error message(s) preceding this one should have more details about the
problem. Try shutting down the resource manually, or retrying with the force option.
CRS-02807: Resource 'string' failed to start automatically.
Cause: This message comes up when the automatic start for the resource has failed
during a reboot of the cluster node or restart of the clusterware stack. See previous
resource specific messages for more details.
Action: Use 'crsctl start resource' to start the resource manually.
CRS-00001 to CRS-29006 20-79
CRS-02809: Failed to update cluster configuration policy set. Details at string in

string.
Cause: Could not update repository with new configuration data.
CRS-02810: Cluster configuration policy set is corrupted. Details at string in string.
Cause: Could not read the configuration data from the repository.
CRS-02814: Server category 'string' does not exist.
Cause: A request was received that referenced a non-existing server category.
Action: Make sure a registered server category is used.
CRS-02815: Server category 'string' is already registered.
Cause: A request to register a server category with a duplicate name was received.
Action: Use a unique name.
CRS-02816: Server category 'string' cannot be unregistered as it is referenced by
resource 'string'.
Cause: The server category you are trying to remove has references to it.
Action: Make sure the server category you are trying to remove is not referenced by
other entities.
server pool 'string'.
Cause: The server category you are trying to remove has references to it.
other entities.
CRS-02818: Failed to delete server category 'string' from repository. Details at string
in string.
Cause: Could not update repository with server category details.
CRS-02819: Failed to save server category 'string'. Details at string in string.
CRS-02820: Required attribute 'string' is missing for configuration policy 'string'.
Cause: A required attribute was not specified.
Action: Make sure the attribute is specified.
CRS-02821: Fatal error while validating configuration policy 'string'.
Cause: There's a problem with the configuration data in the specified policy.
Action: This message always follows the actual error description.
CRS-02822: Server pool 'string' is not declared in the policy set.

Cause: Each configuration policy may only define server pool. configuration for the
pools declared to be a part of the policy set.
Action: Either remove the server pool from the policy, change its name, or extend the
policy set to include the pool's name.
CRS-02823: The new active policy name 'string' was not found.
Cause: An attempt to activate non-existent policy was made.
Action: Use a registered policy's name instead.
CRS-02824: 'string' is reserved for a built-in configuration policy and cannot be
used.
Cause: This name is reserved for a built-in object.
Action: Use a different name.
CRS-02825: Configuration policy 'string' already exists.
Cause: A configuration policy name specified was defined multiple times.
Action: Make sure each policy is only defined once.
CRS-02826: Server pools cannot be removed from the configuration policy set
without activating a new policy at the same time.
Cause: Server pools can be removed from the configuration policy set only if the
command also activates a policy.
Action: To remove the server pools from the system, activate a new policy with the
update. To remove the server pools from the policy control only, resubmit with the ksp option.
CRS-02828: Failed to stop resource while attempting CARDINALITY modification
Cause: An attempt to stop a resource during CARDINALITY modification failed.
Action: Use 'crsctl stop resource' to stop the resource manually and then retry the
update operation.
CRS-02829: Update operation cannot proceed because it would need to stop
resources.
Cause: An update to CARDINALITY would require the operation to stop resources.
Action: Either manually stop enough resources using 'crsctl stop resource' or specify
the force option to have them selected for you.
CRS-02830: A server category name may not be empty or contain spaces.
CRS-02831: Either 'string' or 'string' may be specified, but never both.
Cause: Two mutually exclusive attributes were used at the same time, which is not
allowed.
Action: Use either one or the other.
CRS-02833: Either 'string' or 'string' must be specified, or both.
Cause: At least one of the two attributes must have a value.
Action: Specify a value for either or both.
CRS-00001 to CRS-29006 20-81
CRS-02834: One of 'string', 'string' or 'string' must be specified when 'string' is

'string'.
Cause: One attribute of the three is required for this configuration.
Action: Specify a value for one attribute of the three.
CRS-02835: Resource 'string' cannot start on server 'string' as the server does not
belong to the resource's server category.
Cause: This resource may only run on the servers that belong to the server category of
the resource.
Action: Pick a server that belongs to the category.
CRS-02836: When using a server category, the resource must have 'string' attribute
set to 'string'.
Cause: An attempt was made to register a resorce that uses a server category and yet
is not configured to utlize any available server.
Action: Set the attribute to the required value.
CRS-02837: There are no servers that belong to the server category 'string' of
resource 'string'.
Cause: The resource cannot be started as there are no available servers that belong to
its category.
Action: Add servers to the cluster or change the category to be more inclusive.
CRS-02838: 'string' is not a valid attribute of server categories.
Cause: An attempt was made to set a value for an attribute which does not belong to
server categories.
Action: Use a valid attribute.
CRS-02839: Cluster Ready Services' active version is below required level of
'string'.
Cause: An attempt was made to use functionality that is only available starting from
the specified active version.
Action: Upgrade to the minimum required version.
CRS-02840: Resource instance 'string' does not exist.
Cause: A request was received that referenced a nonexistent resource instance.
Action: Make sure a registered resource instance is used.
CRS-02841: 'string' must be a resource instance.
Cause: This command may only be issued on a resource instance but the supplied
reference was to an object of a different type.
Action: Use a registered resource instance.
CRS-02842: Action 'string' on resource 'string' timed out.
Cause: The action did complete within the allotted time.
Action: None
CRS-02843: Unable to complete processing of the 'string' action for resource 'string'
on server 'string' as Cluster Ready Services is not reachable.
Cause: The processing of the specified action was aborted because Cluster Ready
Services was no longer reachable.
Action: Unless the clusterware stack was stopped or the server was rebooted, Cluster
Ready Services will restart momentarily. The action can be retried thereafter.
CRS-02844: Waiting for resource 'string' to start on server 'string'.
Cause: The resource is now expected to start on the server.
Action: None
CRS-02845: Waiting for resource 'string' to stop on server 'string'.
Cause: The resource is now expected to stop on the server.
Action: None
CRS-02846: There is no active action on resource instance 'string'
Cause: An attempt was made to finish an action on the resource instance while no
corresponding attempt to start the action was found or an attempt to start the action
was timed out before a request to finish the action arrived.
Action: Check the state of the resource and re-do the complete cycle if needed.
CRS-02847: Authorization failure: OS User 'string' does not exist on server 'string'
Cause: The specified operating system user does not exist on the specified server.
Cluster Ready Services requires that all users used by the resource it manages exist on
each server of the cluster.
Action: Add the specified operating user on the specified server.
CRS-02848: Error while reading resources: Resource: string . Error: string Details at
string in string.
CRS-02849: Authorization failure: Resource [ string ]
Cause: A resource operation could not be performed because authorization checking
failed.
Action: Check the ownership, group, and permissions associated with the resource
and ensure that the associated operating system user and group definitions are
consistent on all cluster nodes.
CRS-02850: Start of 'string' on 'string' has been delayed to maintain concurrency
limit of number.
Cause: The configured concurrent start action limit was reached.
Action: The start action will automatically resume as soon as possible.
CRS-02851: Stop of 'string' on 'string' has been delayed to maintain concurrency
limit of number.
Cause: The configured concurrent stop action limit was reached.
Action: The stop action will automatically resume as soon as possible.
CRS-02852: Conflicting specification of server pool and server.
Cause: Server pool name and server name were specified in a start command.
Action: Specify either server pool name or servername, not both.
CRS-02853: Unknown server pool name: 'string' .
Cause: The server pool name given to start/stop command did not exist.
Action: Specify a valid server pool name.
CRS-00001 to CRS-29006 20-83
CRS-02854: Resource 'string' cannot be started in a server pool because it is a local

resource.
Cause: A local resource name was given to start/stop command.
Action: Specify a cluster resource name.
CRS-02855: Resource 'string' is not configured to run in server pool 'string'.
Cause: An attempt was made to start or stop the resource in a server pool where
resource was not configured to run.
Action: Modify resource's attribute to have this server pool or specify a different
resource.
CRS-02856: Unknown names for server pools or for filters.
Cause: An invalid value was supplied for the '-s' or '-w' argument in a start/stop
command or to the API calls.
Action: Provide valid server pool names or filter attributes.
CRS-02857: Cannot stop resource 'string' because it is not running in server pool
'string'.
Cause: A resource stop request specified a server pool on which the resource is not
running.
Action: Check the current state of the resource; it should no longer be running in that
server pool.
CRS-02858: User 'string' does not have permission to run action 'string' on resource
'string'.
Cause: A username and/or group was specified for the action permissions, but the
current user is not included in the specification.
Action: Use 'crsctl modify' to update the ACTIONS attribute for this resource to add
the current user to the permission list for this action, or remove all user and group
specifications to enable universal access.
CRS-02859: Cannot run action 'string' on resource 'string' because the resource is
not online.
Cause: A resource action operation could not be performed because the resource was
not online.
Action: Ensure the resource is online before attempting to run an action.
CRS-02862: Cannot update the ACTIONS attribute, because the input is not valid
Cause: A resource update operation could not be performed, because the input value
is not vvalid.
Action: Ensure the ACTIONS name attribute is specified in 32 or less US7ASCII
characters. Ensure users and groups are prefixed with the appropriate identifier,
either "user:" or "group:"
CRS-02863: Cannot restart resource 'string' because it is not running.
Cause: A resource restart action was not performed because the resource is not
running.
Action: Ensure that the resource which needs to be restarted is up and running.
CRS-02865: Resource 'string' cannot be started on server 'string' because it has an

exclusion dependency with resources of type 'string'.
Cause: An exclusion dependency was configured without the right to preempt a
running resource.
Action: Pick a different server or stop the other resource(s) on this server.
exclusion dependency with resources of type 'string' and the force option was not
specified.
Cause: An exclusion dependency was configured but the force option was not used to
stop the running resource(s).
Action: Either pick a different server or use the force option.
CRS-02867: Server pool 'string' cannot be added to the policy set.
Cause: The Generic server pool as well as its sub-pools cannot be added to the policy
set.
Action: Remove the pool from SERVER_POOL_NAMES attribute.
CRS-02868: 'string' is not a valid attribute of configuration policies.
configuration policies.
CRS-02869: 'string' is not a valid attribute of the policy set.
the policy set.
CRS-02870: An OCR write operation has failed during upgrade of the object
schema.
Cause: While performing CRS upgrade as part of the clusterware upgrade, an OCR
write operation has failed.
Action: Examine the clusterware alert log for more information about OCR failures.
exclusion dependency with resource 'string'.
Cause: An exclusion dependency was configured between the two resources without
the right to preempt a running resource.
Action: Pick a different server or stop the other resource on this server.
exclusion dependency with resource 'string' and the force option is not used.
Cause: An exclusion dependency was configured between the two resources but the
force option was not used to stop the running resource.
Action: Either pick a different server or use the force option.
CRS-02874: Could not restart resource 'string' on server 'string'.
Cause: A required part of restart operation has failed.
Action: Check the preceding errors to see the cause and take appropriate action.
CRS-00001 to CRS-29006 20-85
CRS-02875: Failed to record shutdown information in OLR.

Cause: An attempt to record information during a normal shutdown failed. This will
cause the shutdown to be regarded as unplanned on the next startup, and may lead to
some driver resources being disabled.
CRS-02876: Disabled resource 'string' due to OHASD crashes
Cause: OHASD crashes have exceeded the autostart thresholds set for this resource,
and the resource has been disabled as a result.
Action: Use crsctl config to look up whether a resource has been disabled, and crsctl
enable/disable to manually change the status.
CRS-02877: Owner 'string' of the entity 'string' does not belong to the 'string' group.
Cause: The owner of an entity being configured was not a member of the required
group.
Action: The user, issuing the command, needs to be configured to be in the group.
CRS-02878: Failed to restart resource 'string'
Cause: An attempt to start the resource has failed.
Action: If failover is not enabled, try manually starting the resource on a different
server. If failover is enabled, the resource has been failed over, and any problems are
reported in subsequent messages.
CRS-02879: Cannot update the ALERT_TEMPLATE attribute, because the input is
not valid
Cause: A resource update operation could not be performed, because the input value
is not valid.
Action: Ensure that valid attributes are specified in a space separated list.
CRS-02880: Incorrect specification of dependency 'string', only one modifier may
be specified.
Cause: During resource update, an exclusion dependency specified more than the
maximum of one modifier.
CRS-02881: Additional exclusion dependency discovered on resource 'string' within
the same dependency tree.
Cause: During resource update, a dependency specified more than the maximum of
one exclusion per hard dependency tree.
CRS-02882: Unable to place an instance of resource 'string' due to an exclusion
dependency on 'string'.
Cause: The resource cannot be placed because of the constraints imposed by its start
dependencies.
Action: Either change the resource start dependencies or re-evaluate the request.
CRS-02883: Resource 'string' failed during Clusterware stack start.

Cause: During Clusterware startup, automatic startup of the indicated resource
succeeded but the resource failed before Clusterware startup completed.
Action: Retry starting Clusterware.
CRS-02884: Server 'string' cannot be used for resource placement currently.
Cause: The server is currently configured such that it cannot be used for resource
placement.
Action: Use a different server.
CRS-02890: An administrator-managed database cannot be configured on a nonHub server 'string'.
Cause: An attempt was made to register a database on a server whose role is not 'hub'
or the node is currently down.
Action: Use only online servers configured as Hub servers.
CRS-02891: Policy-managed databases can only be configured in server pools that
use 'string' category.
Cause: An attempt was made to configure a database using a server pool that does
not currently use a category that includes only nodes with the specified role.
Action: Either use an existing server pool that uses such a category or create and use a
server pool with such category.
CRS-02892: In order to use 'string' in resources of 'string' type, 'string' must be set to
'string' and 'string' must be set to 'string'.
Cause: An attempt was made to use an attribute such that other attributes must be set
to specific values.
Action: Resubmit with the mentioned attributes set to the mentioned values.
CRS-02893: Cannot stop ASM instance on server 'string' because it is the only
instance running.
Cause: An attempt was made to stop the last ASM instance in the cluster, which
would lead to a complete cluster outage.
Action: Reissue the request when there are at least two ASM instances running in the
cluster.
CRS-02894: Cannot stop the ASM resource because it will lead to a complete cluster
outage.
Cause: An attempt was made to stop all ASM instances in the cluster, which would
lead to a complete cluster outage.
Action: Reissue the request by specifying a concrete node name.
CRS-02900: User 'string' does not exist on node 'string'.
Cause: An attempt was made to add an unknown username to the CRS Administrator
list.
Action: Reissue the command with a known username. Or create the user on the
node(s) specified, and reissue the command.
CRS-02901: Not authorized to modify the CRS Administrator list.
Cause: An attempt was made to modify the CRS Administrator list by a user not
belonging to the CRS Administrator list.
CRS-00001 to CRS-29006 20-87
Action: Either acquire the role of cluster administrator or have one modify the CRS
Administrator list for you.
CRS-02904: Parameter 'string' for 'relocate' is not a singleton resource.
Cause: A relocate request specified a resource that is not singleton.
Action: Specify a singleton resource or a filter that resolves to an instance of the
resource.
CRS-02905: Server pools in a policy do not have ACL attribute
Cause: A 'crsctl modify serverpool' command specified an ACL attribute with -policy
or -all_policies.
Action: Omit ACL from the attributes.
server pool 'string' in policy 'string'.
Cause: The server category you are trying to remove has references to it in a policy.
other entities in the policy.
CRS-02907: Resource 'string' is not completely configured, and hence cannot be
operated upon.
Cause: A request was made without specifying the PID_FILES or
EXECUTABLE_NAMES.
Action: Specify a value for PID_FILES and/or EXECUTABLE_NAMES attribute, or
specify values for STOP_PROGRAM, CHECK_PROGRAM and CLEAN_PROGRAMS
attributes. 2908 no longer used
CRS-02909: Server 'string' cannot be assigned to server pool 'string' because its
current role is not 'string'.
Cause: An attempt was made to assign a server to the server pool that did not have
the specified role. Only servers with the specified role can be assigned to this server
pool.
Action: Retry using a different server.
CRS-02910: Unable to register server category 'string' as this will affect running
resources, but the force option was not specified.
Cause: One or more running resources were affected by the operation.
CRS-02911: Unable to modify server category 'string' as this will affect running
Cause: One or more running resources were affected by the operation.
CRS-02912: Unable to start resource 'string' on server 'string' because resource
dependencies require stopping it on a different server.
Cause: A start request failed because resource dependencies would require stopping
the resource in order to start it somewhere else.
Action: Manually stop the resource before starting it elsewhere.
CRS-02913: 'autostart delay' value 'string' is invalid.

Cause: The command specified an 'autostart delay' time that was non-numeric or
negative.
Action: Specify a non-negative numeric value for the 'autostart delay' argument.
CRS-02914: 'autostart servercount' value 'string' is invalid.
Cause: The command specified an 'autostart servercount' value that was non-numeric
or negative.
Action: Specify a positive numeric value for the 'autostart servercount' argument.
CRS-02915: Failed to update 'autostart delay' (string) or 'autostart servercount'
(string). Details at string in string.
Cause: A request to update the automatic start details failed because of incorrect
input values.
CRS-02917: The 'string' server pool cannot be removed from the system.
Cause: The command to remove the server pool from the policy set would have
caused it to be removed from the system completely.
Action: Reissue the 'crsctl modify policyset' command with the -ksp option.
CRS-02918: Authorization failure: operating system group 'string' does not exist on
server 'string'
Cause: The specified operating system group does not exist on the specified server.
Cluster Ready Services requires that all groups used by the resources it manages exist
on each server of the cluster.
Action: Add the specified operating system group on the specified server.
CRS-02919: Resource 'string' has no instances to act upon.
Cause: An attempt was made to act on a resource that has no resource instances
because it is configured to run on servers that have never existed in the cluster.
Action: Retry the command when the resource has instances.
CRS-02920: Unable to activate policy 'string' because this will affect running
Cause: An attempt to activate a new policy would have affected one or more running
resources but the force option was not specified.
Action: Reevaluate the request and if it makes sense, set the force option and
resubmit.
CRS-02921: Unable to register policy because attribute 'string' for resource 'string'
does not have the POLICY_CONFIG flag.
Cause: An attempt was made to specify resource attributes in the policy that do not
have the POLICY_CONFIG flag.
Action: Only attributes that can be policy managed and have the POLICY_CONFIG
flag can be specified in a policy definition.
CRS-02922: The attribute 'string' is not supported for resource type 'string'.
Cause: An attempt to update a CRS resource specified an attribute that is not
associated with the resource type.
CRS-00001 to CRS-29006 20-89
Action: Specify only attributes that are associated with the type of resource being
updated.
CRS-02923: The EXPRESSION attribute cannot accept 'string' as a server
configuration attribute.
Cause: An attempt was made to set a server configuration attribute that cannot be
used with the EXPRESSION attribute.
CRS-02924: The EXPRESSION attribute contains invalid value 'string' for server
configuration attribute 'string'.
Cause: An attempt was made to set a value which cannot be assigned to a server
configuration attribute.
Action: Use a valid value.
CRS-02925: The dependency modification 'string' for the targets 'string' has an
unknown dependency or incorrect syntax.
Cause: An attempt was made to modify an existing dependency without providing a
known dependency or the correct modification syntax.
Action: Refer to the Oracle Clusterware documentation for an explanation of
supported dependencies and the resource dependency modification syntax.
CRS-02926: Cannot find a match for target 'string' in the modification list for
dependency 'string'.
Cause: There was no existing dependency that had the same target to be modified.
Action: Supply the correct target for the dependency modification.
CRS-02927: The requested action for the resource 'string' was aborted due to a
timeout.
Cause: The timeout specified for a custom action was reached before the action could
complete.
Action: Revise the timeout setting and retry the action.
CRS-02928: The dependency on type 'string' cannot be accepted because it is
specified multiple times.
Cause: A duplicate type was assigned as a dependency to a resource.
Action: Revise the dependency list to ensure that no duplicate types exist.
CRS-02929: The dependency on resource 'string' cannot be accepted because it is
specified multiple times.
Cause: A duplicate resource was assigned as a dependency to a resource.
Action: Revise the dependency list to ensure that no duplicate resources exist.
CRS-03501: The Cluster Health Analysis service started on host string.
Cause: The Cluster Health Analysis service was successfully started on the listed
node.
Action: None
CRS-03502: The Cluster Health Analysis service aborted on host string. Details at
string in string.
Cause: The Cluster Health Analysis service aborted due to an internal error.
Action: Determine whether the Cluster Health Analysis service has automatically
restarted by checking the Oracle Clusterware alert log. If the problem persists, contact
CRS-03503: The Cluster Health Analysis service on host string is shutting down.
Cause: The Cluster Health Analysis service on the listed node was terminated.
Action: None
CRS-04000: Command string failed, or completed with errors.
Cause: The specified command did not complete successfully. If the command
performs multiple operations internally, one or more of those operations experienced
an error that is reported in a previous message.
Action: Examine the error message(s) preceding this message and correct the
problem(s) they describe.
CRS-04016: Key 'string' is missing in the OCR.
CRS-04017: Failed to get the value for key 'string' from OCR.
CRS-04038: Cannot delete invalid user 'string' from CRS Admin list.
Cause: An attempt was made to delete an invalid username from the CRS Admin list.
Action: Reissue the command with a valid username.
CRS-04040: The value of attribute 'string' contains the following invalid characters:
'string'
Cause: An attribute value with invalid characters was specified.
Action: Reissue the command and provide valid characters for the attribute value.
CRS-04044: CRS Administrator List: string
Cause: Output message, not an error.
Action: None
CRS-04046: Invalid Oracle Clusterware configuration.
Cause: The Oracle Clusterware configuration is invalid.
Action: Configure Oracle Clusterware or Oracle Restart.
CRS-04047: No Oracle Clusterware components configured.
Cause: No Oracle Clusterware components have been configured.
Action: Configure Oracle Clusterware or Oracle Restart.
CRS-04050: Rejecting the command because the cluster active version [string] is
less than the required cluster active version [string]
Cause: The command was rejected because the cluster active version was less than the
required cluster active version.
Action: Reissue the command with a valid cluster active version.
CRS-00001 to CRS-29006 20-91
CRS-04200: Failed to initialize a security context during wallet IPMI credentials

creation.\n
CRS-04201: Hash context initialization failure during wallet IPMI credentials
creation\n
CRS-04202: String hashing failed during wallet credentials creation\n
CRS-04203: Hashing creation error during wallet credentials creation\n
CRS-04204: Failed to initialize the IPMI credentials wallet: string\n
Cause: While trying to initialize the IPMI credentials wallet, the cluster wallet
subsystem returned an unexpected error. The error is included with this message.
Action: See the documentation and follow the directions for the displayed error.
CRS-04205: Failed to open the IPMI credentials wallet. The wallet does not exist.\n
Cause: The wallet does not exist.
Action: Configure the wallet for the IPMI device using 'crsctl set'\n"
CRS-04206: Error reading IPMI credentials wallet: 'string'\n
Cause: While trying to read the IPMI credentials wallet, the cluster wallet subsystem
returned an unexpected error. The error is included with this message.
CRS-04207: Error writing IPMI credentials wallet: 'string'\n
Cause: While trying to write the IPMI credentials wallet, the cluster wallet subsystem
CRS-04208: Unexpected error encountered during lookup of IPMI credentials in the
wallet\n
Cause: Possible corruption in wallet or internal error.
Action: Reconfigure the IPMI wallet using 'crsctl set' and then retry the operation. If
the retry fails call Oracle Support Services.
CRS-04209: IPMI credentials not contained in the wallet\n
Cause: The wallet has not been configured.
Action: Configure the wallet for the IPMI device using 'crsctl set'\n
CRS-04210: Failed to obtain the length of IPMI credentials while accessing the
wallet.\n
Action: Reconfigure the IPMI wallet using "crsctl set" and then retry the operation. If
CRS-04211: Failed to allocate memory\n
Cause: Insufficient system memory resources.
Action: Correct the system memory resources problem and retry.
CRS-04212: Failed to obtain the secret from the wallet.\n
CRS-04213: Secret from wallet has incorrect size\n
CRS-04214: crsctl string and string wallet versions of IPMI do not match.\n
Cause: A mismatch occurred between the IPMI versions of crsctl and the Cluster
Synchronization Services Daemon.
Action: Check proper installation and configuration of crsctl and the Cluster
CRS-04215: Wallet secret encoding error\n
CRS-04216: Unexpected error configuring the wallet contents\n
CRS-04217: Unexpected error saving IPMI credentials wallet: string\n
Cause: While trying to save the IPMI credentials wallet, the cluster wallet subsystem
CRS-04218: Unable to access an IPMI device on this system\n
Cause: A test for the availability of an IPMI device failed. This can occur if: - the IPMI
device driver is not installed, - the installed device driver is not supported by Oracle, IPMI is not supported on this platform or operating system, - no IPMI device is
present, or - an IPMI device is present but not configured.
Action: Verify that IPMI hardware supporting IPMI version 1.5 or greater is present
and supported on this server, that the IPMI device is configured and the device driver
is properly installed.
CRS-04219: Failed to open the wallet. User must be the creator of the wallet: string
\n
Cause: Not the owner/creator of the wallet. The cluster wallet subsystem returned an
error included with this message.
Action: Retry as the owner/creator of the wallet. If necessary, also see the
documentation and follow the directions for the displayed error.
CRS-00001 to CRS-29006 20-93
CRS-04221: Must specify a password\n

Cause: No password entered in response to password prompt.
Action: Specify a password which matches the local servers IPMI BMC password.
CRS-04222: Supplied password was greater than number bytes\n
Cause: The password specified was too long for the IPMI device.
Action: Supply a password with a length no greater than the indicated size while still
matching the password used to configure the IPMI device. Retry.
CRS-04223: Username is greater than number bytes\n
Cause: The username specified was too long for the IPMI device.
Action: Supply a username with a length no greater than the indicated size while still
matching the username used to configure the IPMI device. Retry.
CRS-04224: Unable to communicate with the Cluster Synchronization Services
daemon to update IPMI values.\n
Cause: crsctl modified the IPMI credential wallet but could not notify the Cluster
Action: Retry after assuring the Cluster Synchronization Services Daemon is
functioning by executing csscheck.
CRS-04225: Unexpected authorization error while creating the IPMI credentials
wallet: string\n
Cause: Error creating the IPMI credentials wallet. The cluster wallet subsystem
Action: See the documentation and follow the directions for the displayed error and
retry.
CRS-04226: Unexpected authorization error while saving the IPMI credentials
wallet: string\n
Cause: While attempting to save the IPMI credentials wallet, the cluster wallet subsystem returned an authorization error. The text of the authorization error text is
included with this message. This error was unexpected, and might have been due to
an internal error, because wallet creation should be authorized for anyone, and, if the
wallet was pre-existing, it had already been read after proper authorization checks.
Action: Consult the documentation for the included message to investigate the root
cause of the authorization error, and retry the "set" operation if indicated. If this fails,
CRS-04227: Configuration data stored but IPMI IP address is required to complete
the change. The change cannot be validated until the information is complete.\n
Cause: Not proceeding with Client's IPMI login change request because all
information such as IPMI username, password and IP address need to be present.
Action: Execute 'crsctl set css ipmiaddr' from crsctl.
CRS-04228: Value of attribute 'string' is missing\n
Cause: The user did not provide a value for the attribute.
Action: Provide a value using the format attrName=value, where value may be empty
single quotes.
CRS-04229: The IPMI information change was successful\n

Cause: The IPMI address and authorization information have been validated and the
change completed.
CRS-04230: A device was found where the IPMI device should be, but the device is
not an IPMI device\n
Cause: The IPMI driver may not be configured or supported by this host.
Action: Check the configuration of the IPMI driver and verify the server's support of
an IPMI version 1.5 or greater device.
CRS-04231: IPMI device and/or driver found\n
Cause: An IPMI device and/or device driver was identified on the machine. Detection
mechanisms for IPMI hardware vary by platform.
CRS-04232: Configuration data stored but IPMI authorization information is
required to complete the change. The change cannot be validated until the
information is complete.\n
Cause: Not proceeding with Client's IPMI login change request because all
information (IPMI username, password and IP address) need to be present.
Action: Execute 'crsctl set css ipmiadmin' from crsctl.
CRS-04233: New IPMI configuration data stored, but failed validation by remote
node.\n
Cause: The supplied configuration data was stored in the Oracle registry, but the
resulting configuration could not be used for IPMI access by a remote node. The
stored IP address and/or IPMI admin credentials is/are incorrect.
Action: The validating node is identified in the CRS alert log, and further details can
be found in the alert log on that node. Verify the credentials for the local IPMI device
and reset the configuration using commands 'crsctl set css ipmiadmin' and 'crsctl set
css ipmiaddr'
CRS-04234: IPMI configuration unset and registry entries deleted.\n
Cause: Requested operation successful. However, if the CRS stack was able to access
and use the deleted configuration data, it will continue to do so until it is restarted.
Action: None required. Enter new configuration data or restart the CRS stack if
desired.
CRS-04235: Failed to delete the IPMI configuration from the Oracle Registry:
'string'\n
Cause: An error was encountered in the Oracle registry sub-system while trying to
clear IPMI configuration and delete the IPMI configuration entries. The detailed error
message is included with this message.
CRS-04236: Oracle Clusterware configured to use IPMI\n
Cause: The Oracle Registry contains complete configuration data for IPMI.
CRS-00001 to CRS-29006 20-95
CRS-04237: Oracle Clusterware is not fully configured to use IPMI\n

Cause: The Oracle Registry does not contain complete configuration data for IPMI.
CRS-04251: Failed to change the discovery string\n
Cause: An internal error happened during this operation.
CRS-04252: Failed to update the profile with the new discovery string\n
Cause: An internal error happened when updating the discovery string in the profile.
CRS-04253: The discovery string can not be changed because the voting files are on
ASM\n
Cause: Changing the discovery string is allowed only if the voting files are not on
ASM.
Action: None
CRS-04254: The discovery string has already been set to this value\n
Cause: The value being passed is the same as the current discovery string.
Action: Pass a different discovery string if necessary.
CRS-04255: Not able to find the current configured voting files with the provided
discovery string\n
Cause: The supplied discovery string does not discover the voting files that are
currently configured.
Action: Pass a different discovery string that includes the location of the current
configured voting files.
CRS-04256: Updating the profile\n
Cause: An update to the profile is being performed.
Action: None
CRS-04257: Voting file discovery string successfully replaced\n
Cause: A request to replace a discovery string completed.
Action: None
CRS-04258: Addition and deletion of voting files are not allowed because the
voting files are on ASM\n
Cause: A voting file add or delete request was issued, but voting files have been
configured on ASM storage. Once voting files are configured for ASM, changes in the
configuration can be made only with 'crsctl replace votedisk'.
Action: Use 'crsctl replace votedisk' to modify the voting file configuration.
CRS-04259: Only one ASM diskgroup may be specified\n
Cause: If the voting files will be on ASM, no more than one diskgroup should be
specified.
Action: Specify the correct ASM diskgroup.
CRS-04260: Voting file string is already configured\n
Cause: The location provided is already configured as a voting file.
Action: Specify another location that is not a current voting file.

CRS-04261: Diskgroup string is already configured with voting files\n
Cause: The diskgroup name provided is already configured with voting files.
Action: Specify another location for the voting files.
CRS-04262: Failure when retrieving information from the GPnP profile\n
Cause: An internal error happened when accessing GPnP profile.
CRS-04263: This operation is not allowed\n
Cause: Replacing a list of non-ASM voting files with a different list of voting files is
not supported.
Action: To change the list of non-ASM voting files and add new voting files, use
'crsctl add css votedisk vfile ... vfile'.
CRS-04264: The operation could not be validated\n
Cause: An internal error happened during the validation of the discovery string.
CRS-04265: The operation cannot be performed because the profile is busy with
another operation\n
Cause: Another operation on the profile is taking place.
Action: Let the other operation finish and retry.
CRS-04266: Voting file(s) successfully replaced\n
Cause: A request to replace a voting files(s) completed.
Action: None
CRS-04267: Error while updating the profile with ASM discovery string\n
Cause: An internal error happened while updating the ASM discovery string.
CRS-04268: '-name' option is allowed only with APPQOSDB or CVUDB type
wallets
Cause: The '-name' option was specified in a wallet command for other than
APPQOSDB or CVUDB type wallet.
Action: Use the '-name' option only for actions on APPQOSDB or CVUDB type
wallets.
CRS-04269: Successful get priority number string for Cluster Synchronization
Services.\n
Cause: The 'get' operation was performed successfully.
Action: None
CRS-04271: Voting file creation in other than an ASM disk group prohibited in this
cluster.\n
Cause: An attempt was made to create voting files outside of the ASM disk group in a
client cluster.
Action: Specify an ASM disk group for voting file creation or replacement.
CRS-00001 to CRS-29006 20-97
CRS-04272: error while identifying voting files in use\n

Cause: More than one voting file was identified for the cluster.
CRS-04273: Creation of voting files in an ASM disk group not allowed using the
command 'crsctl add votedisk'.\n
Cause: An attempt was made to create voting file in the ASM disk group with the
command 'crsctl add votedisk'.
Action: Use 'crsctl replace votedisk' to add or replace the voting files in ASM disk
group.
CRS-04274: Command not supported in this cluster.\n
Cause: An attempt was made to add voting file(s) in a client cluster with the
command 'crsctl add votedisk'.
Action: Use 'crsctl replace votedisk' to add or replace the voting file in client clusters.
CRS-04402: The CSS daemon was started in exclusive mode but found an active
CSS daemon on node string, number string, and is terminating
Cause: The CSS daemon was started in exclusive mode, which requires that the
clusterware stack is down on all other nodes to ensure data integrity. A CSS daemon
was detected on another node, so the CSS daemon on this node is terminating.
Action: If this message displays as part of the install process, no action is required,
otherwise stop the Oracle clusterware stack that is running on the indicated node. The
name and number of the active node may be unknown.
CRS-04404: The following nodes did not reply within the allotted time:\nstring
Cause: The clusterized command timed out before the specified nodes responded to
the command.
Action: Check if the nodes are online; also check for communications problems.
Consider issuing the command locally on the specified node(s).
CRS-04405: The following nodes are unknown to Oracle High Availability
Services:\nstring
Cause: The local Oracle High Availability Services is not in contact with Oracle High
Availability Services on the specified nodes.
Action: Check if the nodes are online and Oracle High Availability Services is
running. Check for communications problems and consider issuing the command
locally on the specified node(s).
CRS-04406: Oracle High Availability Services synchronous start failed.
Cause: A start of Oracle High Availability Services with the '-wait' or '-waithas' option
did not complete successfully. This message is preceded by others describing errors
that occurred.
Action: Examine the error messages preceding this message and correct the problems
they describe.
CRS-04407: Values bigger than 10 are not allowed for parameter string.\n
Cause: This parameter does not allow values higher than 10.
Action: Use a value between 0 and 10.
CRS-04408: Node 'string' configured role successfully changed; restart Oracle High
Availability Services for new role to take effect.
Cause: The 'crsctl set node role' command was run to change the role of a node in a
Flex Cluster.
Action: Restart Oracle High Availability Services on the node by running 'crsctl stop
crs' and 'crsctl start crs'.
CRS-04409: Node 'string' is already configured in 'string' role.
Cause: A 'crsctl set node role' command specified the role already configured for the
node."
Action: Specify a different role or a different node, if appropriate.
CRS-04411: The role of node string cannot be converted to 'leaf'.
Cause: An attempt was made to modify the role of the last remaining configured 'hub'
node to 'leaf' node, which is not allowed or the node is already a 'leaf' node."
Action: If role of this node must to be modified to 'leaf', first bring up another node as
a 'hub' node to ensure that there is always at least one 'hub' node.
CRS-04481: Unable to spawn a process.\n
Cause: There was an internal error while spawning a process.
Action: Report the error to Oracle Support.
CRS-04482: A child process terminated abnormally.\n
Cause: A child process exited due to an internal error.
Action: Report the error to Oracle Support.
CRS-04602: Failed number to add voting file string.\n
Cause: An attempt to add a voting file failed. The number following "Failed" is a
return code, which can be: 1 - internal OCSSD server error; 8 - rejected by OCSSD; 15insufficient privileges for this operation; 19- version incompatibility between client
and server;
Action: Respond based on the return code as follows: 15 - adjust privileges or use a
different userid 19 - ensure that compatible versions are installed others - report to
Oracle Support Services
CRS-04608: Failure number with Cluster Synchronization Services while deleting
voting disk.\n
Cause: An attempt to delete a voting disk failed. The number following "Failed" is a
return code, which can be: 1 - internal OCSSD server error; 8 - rejected by OCSSD; 15insufficient privileges for this operation; 16- either the specified voting disk does not
exist or you tried to delete a majority of voting disks; 19- version incompatibility
between client and server;
Action: Respond based on the return code as follows: 15 - adjust privileges or use a
different userid 16 - review the voting disk configuration displayed by 'crsctl query
css votedisk' and correct your request accordingly 19 - ensure that compatible
versions are installed others - report to Oracle Support Services
CRS-04615: Software version query failed for node string\n
CRS-00001 to CRS-29006 20-99
CRS-04625: Failure to allocate number bytes for username.\n

Cause: System is out of memory.
Action: Free up memory on system and retry.
CRS-04626: The requested setting must be between number and number.\n
Cause: An attempt to change a setting to an out of bounds value.
Action: Retry with the setting within the proper limits.
CRS-04627: Unable to lock the configuration before making changes. number\n
Cause: Failure in a CSS API acquiring a lock.
Action: Retry or contact support for information on the error code.
CRS-04628: Change to configuration failed, but was successfully rolled back.\n
Cause: See accompanying messages for explanation of cause.
Action: No action is required. This indicates that no damage was done.
CRS-04629: Unable number to mark unformat information on voting file string\n
Cause: Probably an unreadable / unwritable voting file was being removed.
Action: If cause is correct, this is ignorable, but not ideal.
CRS-04630: Unable to apply correct permissions to new voting file string.\n
Cause: An attempt to set permissions on a new voting file failed. This message is
accompanied by others that provide OS-specific details of the error.
Action: Examine the OS-specific error and correct it if possible; otherwise, specify a
different voting file.
CRS-04631: Unable number to undo initialization of voting file.\n
Cause: Could not roll back format of voting file.
Action: Disk should be cleaned out before an attempt to add again.
CRS-04632: Unable number to roll back OCR settings for voting file.\n
Cause: Could not remove temporary changes to OCR adding voting file.
Action: Shut down the cluster and restart. New voting file must be removed with
"crsctl delete css votedisk".
CRS-04633: This could take several minutes.\n
Cause: CRS daemons is engaged in an activity take could potentially take a long time.
Action: None
CRS-04634: Retrying stop resources.\n
Cause: crsctl command is trying again to stop resources.
Action: None
CRS-04635: Internal error 'number' while attempting to send shutdown request
Action: If retrying does not work, contact Oracle support
CRS-04636: Failure number in clsvrelversion
CRS-04637: Oracle High Availability Services release version on the local node is
[string]\n
Action: None
CRS-04651: No resources found on server 'string'.
Cause: The server has no resources associated with it.
Action: Provide a server with resources running.
CRS-04652: Failure number in clsvswversion for the local node
CRS-04653: Server name 'string' contains invalid characters.
Cause: The name provided contains invalid characters.
Action: Use a server name with only alphanumeric characters.
CRS-04654: Server 'string' could not be found.
Cause: The name provided is not a known server's name.
Action: Use a known server's name.
CRS-04655: Resource 'string' could not be found.
Cause: The name provided is not a known resource's name.
Action: Use a known resource's name.
CRS-04656: Resource 'string' is not running on server 'string'.
Cause: The resource is not on the server the user specified.
Action: User must type a known server.
CRS-04657: Source and destination servers are the same.
Cause: The source and destination servers may not be the same.
Action: Specify a different destination server.
CRS-04658: The clusterware stack on node string is not completely down.\n
Cause: There is indication that the clusterware stack is still up.
Action: Shut down the entire clusterware stack before deleting the node.
CRS-04659: Error while trying to unpin node string.\n
CRS-04660: Could not find node string to delete.\n
Cause: The node to be deleted could not be found because it has not been a member
of this cluster recently.
Action: Check the name provided. If the name is correct, the node has been
automatically deleted because it was inactive for a long time and no further action is
required to delete the node from the cluster.
CRS-04661: Node string successfully deleted.\n
Cause: A request to delete a node completed.
CRS-00001 to CRS-29006 20-101
Action: None
CRS-04662: Error while trying to delete node string.\n
Cause: Some internal error happened during this operation.
CRS-04663: could not find node string to pin\n
Cause: The indicated node was not an active Hub node in the cluster.
Action: Ensure that the node name is correct, is a Hub node, and that Oracle
Clusterware is running on the node.
CRS-04664: Node string successfully pinned.\n
Cause: A request to pin a node completed.
Action: None
CRS-04665: Error while trying to pin node string.\n
CRS-04666: Could not find node string to unpin.\n
Cause: An unpin request specified a node that is not an active hub node in the cluster.
Action: Ensure that the node name is correct, that it is a hub node, and that Oracle
Clusterware is running on the node.
CRS-04667: Node string successfully unpinned.\n
Cause: A request to unpin a node completed.
Action: None
CRS-04668: This ASM diskgroup does not contain voting disks to be deleted\n
Cause: The ASM diskgroup name provided does not contain voting files.
Action: Provide the right ASM diskgroup name.
CRS-04669: Failed to set parameter string to number due to conflicting parameter
string; the new value for string must be less than number.\n
Cause: An attempt was made to set a new value to a configuration parameter which
conflicts with another parameter's current value.
Action: Set the value of this parameter to a lower value than what is indicated in the
message.
CRS-04670: Failed to unset parameter string due to conflicting parameter string
currently set to number.\n
Cause: An attempt was made to unset a configuration parameter which conflicts with
another parameter's current value.
Action: Set the conflicting parameter to a value which can coexist with proposed
parameter change before submitting this parameter change.
CRS-04671: This command is not supported for ASM diskgroups.\n
Cause: The command 'crsctl add css votedisk' contains one or more ASM diskgroups
in the list of voting files. Voting files may be migrated to and from ASM, but
diskgroups cannot be added or deleted.
Action: Use an appropriate 'crsctl set' command to add ASM diskgroups. Use 'crsctl
replace votedisk' command to migrate voting files to ASM.
CRS-04672: Successfully backed up the Voting File for Cluster Synchronization

Service.\n
Cause: The backup of the voting file completed successfully.
Action: None
CRS-04673: Oracle High Availability Services version on the local node is [string]
\n
Action: None
CRS-04674: Cannot add invalid user 'string' to CRS Admin list.
Cause: An attempt was made to add an invalid username to the CRS Admin list.
Action: Reissue the command with a valid username.
CRS-04675: Failed to get logfilesize for Cluster Synchronization Services.\n
Cause: An internal error happened during this operation for Cluster Synchronization
Services.
CRS-04676: Successful get logfilesize number for Cluster Synchronization Services.
\n
Cause: The operation is done successfully for Cluster Synchronization Services.
Action: None
CRS-04677: Failed to get string for Cluster Synchronization Services.\n
Services.
CRS-04678: Successful get string number for Cluster Synchronization Services.\n
Cause: The 'get' operation was performed successfully.
Action: None
CRS-04679: Failed to unset logfilesize for Cluster Synchronization Services.\n
Services.
CRS-04680: Successful unset logfilesize for Cluster Synchronization Services.\n
Cause: The 'unset' operation was performed successfully.
Action: None
CRS-04681: Failed to unset priority for Cluster Synchronization Services.\n
Services.
CRS-04682: Successful unset priority for Cluster Synchronization Services.\n
Cause: The 'unset' operation was performed successfully.
Action: None
CRS-00001 to CRS-29006 20-103
CRS-04683: Failed to set parameter string to number for Cluster Synchronization

Services.\n
Services.
CRS-04684: Successful set of parameter string to number for Cluster
Synchronization Services.\n
Cause: The 'set' operation was performed successfully for Cluster Synchronization
Services.
Action: None
CRS-04685: Failed to set logfilesize number for Cluster Synchronization Services.\n
Services.
CRS-04686: Successful set logfilesize number for Cluster Synchronization Services.
\n
Cause: The 'set' operation was performed successfully for Cluster Synchronization
Services.
Action: None
CRS-04687: Shutdown command has completed with errors.
Cause: Processing of a shutdown command has completed with errors.
Action: Refer to preceding error message(s) for information about the errors that
occurred.
CRS-04688: Oracle Clusterware is already stopped on server 'string'
Cause: Oracle Clusterware is not running on the indicated server.
Action: None
CRS-04689: Oracle Clusterware is already stopped
Cause: Oracle Clusterware is not running.
Action: None
CRS-04690: Oracle Clusterware is already running on 'string'
Cause: Oracle Clusterware is already running on the indicated server.
Action: None
CRS-04691: Oracle Clusterware is already running
Cause: Oracle Clusterware is already running.
Action: None
CRS-04692: Cluster Ready Services is online in exclusive mode
Cause: Cluster Ready Services is limited to providing internal services to other Oracle
Clusterware components. External Cluster Ready Services are not available.
Action: When in exclusive mode, Oracle Clusterware components are dedicated to the
repair or reconfiguration of the Oracle Cluster Registry, voting files or both. Oracle
Clusterware should be down and remain down on every other cluster node. Only
commands that check or stop the stack, interact with Cluster Synchronization Services
or aid in Clusterware repair or reconfiguration should be issued.
CRS-04693: Failed to back up the voting file for Cluster Synchronization Service.\n
CRS-04694: Number of voting files cannot exceed number. Failed to add voting
files.\n
Cause: The request to add voting files would cause the maximum number allowed to
be exceeded.
Action: Specify fewer voting files to add so that the maximum is not exceeded, or
include the -purge option on 'crsctl add css votedisk' to replace the existing set of files
with an allowable number of new files.
CRS-04695: Voting disk addition failed because this disk string is a duplicate of an
existing voting disk with matching File Universal ID string.\n
Cause: This disk is already a part of the current cluster.
Action: None needed.
CRS-04696: Failed to set parameter string to number due to conflicting parameter
string; the new value for string must be greater than number.\n
Cause: An attempt was made to set a new value to a configuration parameter which
conflicts with another parameter's current value.
Action: Set the value of this parameter to a higher value than what is indicated in the
message.
CRS-04697: This command must be executed by Operating System user 'string'.
Cause: A crsctl command was executed by the wrong Operating System user.
Action: The specified Operating System user should execute the command.
CRS-04698: Error code number in retrieving the patch level
CRS-04699: Error code number in retrieving the cluster configuration type
CRS-04700: The Cluster Time Synchronization Service is in Observer mode.\n
Cause: Vendor time synchronization software exists on at least one of the nodes in the
cluster.
Action: None
CRS-04701: The Cluster Time Synchronization Service is in Active mode.\n
Cause: Vendor time synchronization software is not detected on any of the nodes in
the cluster.
Action: None
CRS-04702: Offset (in msec): string\n
Cause: None
Action: None
CRS-00001 to CRS-29006 20-105
CRS-04703: The Cluster Time Synchronization Service is Offline.\n

Cause: The Cluster Time Synchronization Service is not running on the current node.
Action: None
CRS-04704: Shutdown of Clusterware failed on node string.\n
Cause: The shutdown did not complete successfully. One or more of the internal
operations experienced an error that is reported in previous messages.
CRS-04705: Start of Clusterware failed on node string.\n
Cause: The start did not complete successfully. One or more of the internal operations
experienced an error that is reported in previous messages.
CRS-04708: Server name is missing
Cause: The server name provided was empty or no name was provided.
Action: Provide a valid server name.
CRS-04730: Command aborted due to an internal error\n
Cause: An inconsistent internal state was detected.
Action: Call Oracle Support Services.
CRS-04731: Specified file string could not be created.\n
Cause: JAZN configuration file required by the OC4J container could not be created.
Action: Ensure that the directory path exists and that its permissions will allow the
file to be created by oracle owner of clusterware home.
CRS-04732: Could not be open file string.\n
Cause: JAZN configuration file required by the OC4J container could not be opened.
file to be created by oracle owner of clusterware home.
CRS-04733: File string does not exist.\n
Cause: The JAZN configuration file required by the OC4J container does not exist.
file to be created oracle owner of the clusterware home.
CRS-04734: Filename was not specified.\n
Cause: filename was not supplied or was an empty string.
Action: Re-try the command by specifying a valid JAZN configuration filename.
CRS-04735: Expected OCR key does not exist\n
Cause: An infrastructure error occurred because a required OCR key was missing.
Action: Call Oracle Support Services.
CRS-04736: Operation on OCR key failed\n
Cause: Operation on OCR key failed due to an OCR error.
Action: Re-issue the command as oracle owner of clusterware home.
CRS-04737: Failed to allocate number bytes of memory\n

Cause: Could not allocate memory for internal buffers due to insufficient system
memory resources
Action: Correct the system memory resources problem and retry the command
CRS-04738: Size of file string is too large\n
Cause: Specified file size exceeds 65536 bytes.
Action: Re-issue the command after reducing the size of the file.
CRS-04739: Could not close file string \n
Cause: Due to an internal error the specified file could not be closed
Action: Re-issue the command after verifying disk space, permissions and path.
CRS-04740: I/O operation on file string failed.\n
Cause: Due to an internal error an I/O operation on the specified file failed.
Action: Call Oracle Support if the problem persists.
CRS-04741: Insufficient permissions on OCR key\n
Cause: Operation on OCR key failed due to insufficient permissions.
Action: Re-issue the command as oracle owner of clusterware home.
CRS-04742: OCR updated with contents of string (New = number, Old = number
bytes)
Cause: set jazn command was issued and OCR key was updated.
CRS-04743: File string was updated from OCR(Size: number(New), number(Old)
bytes)
Cause: get jazn command was issued and specified file was updated with the contents
from OCR key.
CRS-04839: Required attribute 'string' is missing for 'string'.
Cause: A required attribute was not specified.
Action: Make sure the attribute is specified.
CRS-04840: Attribute 'string' cannot be specified using this command.
Cause: An attribute was specified that cannot be used with this command.
Action: Server pool configuration can be changed or created using 'crsctl modify
policyset' and 'crsctl modify serverpool -policy' commands.
CRS-04843: Policy 'string' does not exist.
Cause: An invalid policy name was specified.
Action: Verify the name.
CRS-04846: Configuration policy set has an invalid profile.
Cause: An invalid policy set definition was specified. Missing elements or duplicate
elements may be present in the profile.
Action: Verify the contents of the policy set profile and resubmit the command.
CRS-00001 to CRS-29006 20-107
CRS-04847: File 'string' does not exist.

Cause: The specified for the comamnd did not exist or could not be opened.
Action: Verify the filename and resubmit the command.
CRS-04848: Policy 'string' appears more than once in a policy set file.
Cause: A policy was defined more than once in the profile.
Action: Verify the contents of the policy and remove the duplicate policy.
CRS-04849: Server pool 'string' appears more than once for policy 'string' in the
policy set file.
Cause: A server pool was defined more than once in the profile for the same policy.
Action: Verify the contents of the policy and remove the duplicate server pool.
CRS-04873: At least one attribute must be specified for this command.
Cause: The 'crsctl eval modify' command was run without specifying any attributes.
Action: Rerun the command with at least one attribute specified.
CRS-04891: Invalid value of level specified.
Cause: An invalid value for output level was specified. Output level can only be 1, 2
or 3.
Action: Rerun the command with a level of 1, 2 or 3.
CRS-04922: Module string: string ignored; module level out of bounds (valid range
number - number)
Cause: An attempt to set a log or trace level supplied a level that is out of range for
the module.
Action: Specify a log or trace level within the valid range.
CRS-04923: string module: string ignored; module level is invalid (range 0 - 65535)
Cause: Module log/trace level was invalid (range 0 - 65535).
Action: Specify a log/trace level within the valid range (0 - 65535).
CRS-04925: 'all' module keyword was specified with other module names
Cause: The module keyword 'all' already refers to all module names.
Action: When referring to all modules, use 'all' without duplicate references to other
module names.
CRS-04932: Failed to get the current cluster mode
Cause: There was an internal error while getting cluster mode.
CRS-04933: Cluster mode set to "flex"; restart Oracle High Availability Services on
all nodes for cluster to run in "flex" mode.
Cause: Cluster mode was changed to "flex", which requires a cluster restart.
Action: Restart Oracle High Availability Services on all nodes for cluster to run in
"flex" mode.
CRS-04934: Failed to set the cluster mode
Cause: There was an internal error while setting cluster mode.
CRS-04937: Unable to set the cluster mode.

Cause: An attempt was made to set the cluster mode to 'flex' but Grid Naming
Service(GNS) was not configured.
Action: Configure GNS and try again to set the cluster mode to 'flex'.
CRS-04940: Cluster must run in standard or flex mode to use this command
Cause: An attempt was made to set the cluster mode but machine is not running as a
cluster.
Action: Cluster must be in standard or flex mode to change the cluster mode.
CRS-04942: Cluster mode set to "standard"
Cause: Cluster mode is changed. Cluster will shut down now.
Action: None
CRS-04953: CSS already running in nonexclusive mode
Cause: An exclusive mode CRS stack start was attempted when CSS was already
running in nonexclusive mode.
Action: Stop the CRS stack first and then start in exclusive mode.
CRS-04954: CRSD already running in nonexclusive mode
Cause: An exclusive mode CRS stack start was attempted when CRSD was already
running in nonexclusive mode.
Action: Stop the CRS stack first and then start in exclusive mode.
CRS-04955: CSS failed to start in exclusive mode
Cause: An exclusive mode CRS stack start was attempted but CSS failed to start in
exclusive mode.
Action: Check the Clusterware alert log for errors. Correct the reported error(s) and
retry.
CRS-04956: CRSD failed to start in exclusive mode
Cause: An exclusive mode CRS stack start was attempted but CRSD failed to start in
exclusive mode.
Action: Check the Clusterware alert log for errors. Correct the reported error(s) and
retry.
CRS-04967: Input values are out of range for parameter string
Cause: A value was provided which was out of range for this parameter.
Action: Specify a value which is appropriate for this parameter.
CRS-04968: Invalid values for parameter string. Specify either 0 or 1.
Cause: A value was provided which was out of range for this parameter.
Action: Specify a value which is appropriate for this parameter.
CRS-04969: Specified server attribute string does not exist
Cause: A nonexistent attribute was specified for get/set command.
Action: Specify an attribute that exists.Run 'crsctl stat res resourcename -p' to list all the
attributes of that resource.
CRS-00001 to CRS-29006 20-109
CRS-04973: Flex ASM must be enabled before switching the cluster mode to 'flex'
Cause: An attempt to change the cluster mode to 'flex' failed because Flex ASM is not
enabled.
Action: Enable Flex ASM before changing the cluster mode. Refer to Oracle
Automatic Storage Management Administrator's Guide for configuring Flex ASM.
CRS-04977: Cluster cannot be converted from 'flex' mode to 'standard' mode
Cause: An attempt was made to set the cluster mode to standard from flex mode.
Action: If a cluster needs to be converted to standard mode, reinstall Clusterware.
CRS-04980: Duplicate value string specified for resource attribute string
Cause: A duplicate value was specified for a resource attribute.
Action: Specify only one value for a resource attribute.
CRS-04981: Duplicate value string specified for type attribute keyword string
Cause: A duplicate value was specified for a type attribute keyword.
Action: Specify only one value for DEFAULT_VALUE, FLAGS and TYPE per type
attribute.
CRS-04982: Valid type attribute keyword string specified outside a type attribute
Cause: A valid type attribute keyword was specified outside a type attribute.
Action: Specify the ATTRIBUTE type attribute keyword before specifying the
DEFAULT_VALUE, FLAGS or TYPE type attribute keywords.
CRS-04983: Invalid type attribute keyword string specified
Cause: An invalid type attribute keyword was specified.
Action: Specify only the valid type attribute keywords ATTRIBUTE,
DEFAULT_VALUE, FLAGS and TYPE.
CRS-04984: Duplicate definition for type attribute string
Cause: The same type attribute was named on more than one ATTRIBUTE keyword.
Action: Define a type attribute only once.
CRS-04985: The value 'string' of FLAGS attribute is invalid.
Cause: An invalid flag value was specified.
Action: Flag values may be combined using the '|' character as a separator.
CRS-04986: This command is for Oracle's internal use only
Cause: A command meant for internal use was specified.
Action: Refer to 'crsctl -h' for list of commands available for use.
CRS-04989: Module string: string ignored; module level out of bounds (valid range
number - number)
Cause: An attempt to set a log or trace level supplied a level that is out of range for
the module.
Action: Specify a log or trace level within the valid range.
CRS-04990: Issued command does not support filter in this version of CRS.
Cause: The command was rejected because a filter (-w) was specified. Filters are not
currently supported for this command.
Action: Reissue the command without the filter.
CRS-04991: Could not delete the resource because it does not exist.
Cause: An attempt to delete a resource failed because the resource specification did
not identify an existing resource. Either there was no resource with the specified
name, or no resource satisfied the specified filter.
Action: Reissue the command specifying the name of an existing resource or a filter
that will select an existing resource.
CRS-04992: Could not delete the server pool because it does not exist.
Cause: An attempt to delete a server pool failed because the server pool specification
did not identify an existing server pool. Either there was no server pool with the
specified name, or no server pool satisfied the specified filter.
Action: Reissue the command specifying the name of an existing server pool or a filter
that will select an existing server pool.
CRS-04993: Could not delete the server category because it does not exist.
Cause: An attempt to delete a server category failed because the server category
specification did not identify an existing server category. Either there was no server
category with the specified name, or no server category satisfied the specified filter.
Action: Reissue the command specifying the name of an existing server category or a
filter that will select an existing server category.
CRS-04994: Could not delete the resource type because it does not exist.
Cause: An attempt to delete a resource type failed because the resource type
specification did not identify an existing resource type. Either there was no resource
type with the specified name, or no resource type satisfied the specified filter.
Action: Reissue the command specifying the name of an existing resource type or a
filter that will select an existing resource type.
CRS-04995: The command 'string' is invalid in crsctl. Use srvctl for this command.
Cause: An attempt was made to use an unsupported command in crsctl.
Action: Use srvctl for the mentioned command.
CRS-04996: Command ('crsctl string policyset') is not supported in this version of
CRS.
Cause: The command was rejected because policy-based management is not a
supported feature in this release.
Action: If this error occurs during rolling upgrade, wait for the upgrade to finish.
Otherwise, upgrade to the required release or higher.
CRS-04997: Command ('crsctl string category') is not supported in this version of
CRS.
Cause: The command was rejected because the server category is not a supported
feature in this release.
CRS-04998: Command ('crsctl eval string' ) is not supported in this version of CRS.
Cause: The command was rejected because What-If is not a supported feature in this
release.
CRS-00001 to CRS-29006 20-111
CRS-04999: Command ('crsctl string policy') is not supported in this version of

CRS.
Cause: The command was rejected because policy-based management is not a
supported feature in this release.
CRS-05000: Expected resource string does not exist in agent process
Cause: The expected resource must have been created by Oracle Configuration tools.
Action: Check that the resource was not manually deleted. If not the case call Oracle
Support.
CRS-05001: Expected dependency in resource string on a resource of type string
does not exist
Cause: The expected resource dependency must have been created by Oracle
Configuration tools.
Action: Check that the resource dependency was not manually removed.
CRS-05002: Agent action was aborted
Cause: Agent action was aborted either due to action timeout expiry or the user
canceled the action.
Action: Retry the operation.
CRS-05003: Invalid attribute value: 'string' for attribute string
Cause: An attribute value passed to the Agent was NULL or invalid.
Action: Give the correct value to the attribute and retry.
CRS-05004: Cannot find listener endpoint for listener string
Cause: listener endpoint not found.
Action: Check listener.ora for that listener.
CRS-05005: IP Address: string is already in use in the network
Cause: The VIP resource attempted to use an IP address already in use in the
network.
Action: Use srvctl to re-create vip or scanvip specifying an IP address which is not
being used in the network and retry the operation.
CRS-05006: Unable to automatically select a network interface which has subnet
mask string and subnet number string
Cause: The subnet mask and subnet number configured for the resource did not
match the subnet mask and subnet number of any network interface on this node.
Action: Provide a subnet mask and subnet number which matches at least one
network interface's subnet mask and subnet number using srvctl remove and add vip
and retry the operation.
CRS-05007: Cannot remove the primary IP string from the network interface
Cause: The primary IP of the network interface was incorrectly configured as the VIP.
Action: Use 'srvctl remove' and 'srvctl add vip' or 'srvctl remove' and 'srvctl add scan'
to provide the correct IP address for the VIP and retry the operation.
CRS-05008: Invalid attribute value: string for the network interface

Cause: The network interface value did not match the subnet mask and subnet
number of any network interface on the node.
Action: Modify the network interface's value such that the subnet mask and subnet
number matches the subnet mask and subnet number of at least one network
interface on the node using 'srvctl remove' and 'srvctl add vip' and retry the
operation.
CRS-05009: The VIP address string does not belong to the subnet string
Cause: The VIP's subnet number and the network interface's subnet number did not
match.
Action: Make the VIP's subnet number match the network interface's subnet number
using 'srvctl remove' and 'srvctl add vip' or 'srvctl remove' and 'srvctl add scan' and
retry the operation.
CRS-05010: Update of configuration file "string" failed: details at "string" in "string"
Cause: An attempt to open the specified file failed. Common causes are that the file
does not exist, or the file permissions prohibit access.
CRS-05011: Check of resource "string" failed: details at "string" in "string"
Cause: The check of the database or Automatic Storage Management instance failed.
Action: Check the database or ASM instance alert log and the referenced Oracle
Clusterware trace file for additional information. Recover the instance if necessary.
CRS-05012: Check of service resource "string" failed: details at "string" in "string"
Cause: The check of the preconnect service failed because it could not run on the same
node as the main service.
Action: Check the referenced Oracle Clusterware trace file for additional information.
Start the preconnect service on a different node.
CRS-05013: Agent "string" failed to start process "string" for action "string": details
at "string" in "string"
Cause: The named agent failed to start the named process for the named action.
Action: Check the referenced Oracle Clusterware trace file for additional operating
system specific information. Refer to operating system documentation to correct the
error.
CRS-05014: Agent "string" timed out starting process "string" for action "string":
details at "string" in "string"
Cause: The named agent aborted the named process because the process failed to
respond within the timeout period.
Action: Check the agent log files for further information
CRS-05015: Agent timed out waiting for a response from the DHCP server
Cause: Agent and the DHCP server were not able to communicate with each other.
Common causes of this failure are due to the DHCP server not running, or improper
DHCP server configuration, or the DHCP server running out of DHCP leases.
Action: Identify the cause of the problem from the DHCP server log files. If the
problem is due to the DHCP server running out of leases, increase the number of
addresses which can be served by the DHCP server.
CRS-00001 to CRS-29006 20-113
CRS-05016: Process "string" spawned by agent "string" for action "string" failed:
details at "string" in "string"
Cause: The named process failed to complete succesfully.
Action: Check details in the agent log for error information from the spawned
process.
CRS-05017: The resource action "string string" encountered the following error:
\nstring. For details refer to "string" in "string".
Cause: An error occurred during the resource action.
Action: Examine the accompanying error messages and respond accordingly.
CRS-05018: Clusterware has disabled an IP route associated with destination
"string" and interface "string". For details, refer to "string" in "string".
Cause: A potentially conflicting route in the same subnet used by the address for the
redundant interconnect was found and removed to prevent routing conflicts.
Action: Validate that the route described was not actually in use.
CRS-05019: All OCR locations are on ASM disk groups [string], and none of these
disk groups are mounted. Details are at "string" in "string".
Cause: OCR was configured on ASM disk groups, and all of the listed disk groups
failed to mount. The possible causes are: 1. A disk was not accessible. 2. A disk in a
normal or high redundancy disk group failed after the most recent dismount. 3. The
ASM_DISKSTRING in the SPFILE or the GPnP profile was incorrect.
Action: Check the ASM alert logs for more information. To correct disk access or
failure issues either: a) restore access to the disks in the disk group and mount the
disk group (via ASMCMD or SQL). or b) Issue a force mount to the disk group to
offline missing disks and mount a normal or high redundancy disk group. To correct
the ASM_DISKSTRING in the SPFILE and propagate the change to the GPnP profile,
in sqlplus, issue the SQL command "ALTER SYSTEM SET ASM_DISKSTRING
<discovery_string> ...", see Setting Oracle ASM Initialization Parameters in the
Automatic Storage Management Administrator's Guide
CRS-05020: Not all endpoints are registered for listener string
Cause: Listener agent failed to register all endpoints to listener.
Action: Check listener log file for that listener.
CRS-05021: Check of storage failed: details at "string" in "string"
Cause: The check of ASM storage failed because the storage was not accessible.
Action: Check Clusterware alert log and the referenced Oracle Clusterware trace file
for additional information.
CRS-05022: Stop of resource "string" failed: current state is "string"
Cause: The named resource failed to stop.
Action: Ensure there are no users of the resource and reissue the stop.
CRS-05023: Failed to unmount file system "string"; details at "string" in "string"
Cause: The named file system resource failed to unmount.
Action: Determine which OS processes are accessing the mount point using an OS
command such as 'fuser' or 'lsof' for Unix based platforms or 'handle' for Windows.
Close, shut down, or terminate applications and processes accessing the mount point,
then retry.
CRS-05024: Unmounting file system "string"

Cause: A 'stop' of the file system resource mounted on the indicated path started.
Action: This is an informational message only.
CRS-05025: File system "string" unmounted
Cause: A 'stop' of the file system resource mounted on the indicated path completed
normally.
CRS-05026: Failed to clean mount point "string"; details at "string" in "string"
Cause: The clean of the volume failed because one or more processes on the system
were accessing the mount point.
Action: Determine which OS processes are accessing the mount point using an OS
command such as 'fuser' or 'lsof' for Unix based platforms or 'handle' for Windows.
Close, shut down, or terminate applications and processes accessing the mount point,
then retry.
CRS-05027: The ASM instance on node "string" cannot be stopped because it is
currently being used by Cluster Ready Services.
Cause: An attempt to stop the ASM instance on the indicated server failed because
Cluster Ready Services was using that ASM instance.
Action: Use 'crsctl stop crs' or 'crsctl stop cluster' to stop the Cluster Ready Services on
the node.
CRS-05028: Cannot start resource "string" because the resource it depends on,
"string", failed to start on the same node
Cause: The resource could not be started because the resource on which it depends
failed to start on the same node.
Action: Manually start the dependency resource and then the resource on the same
node.
CRS-05029: Agent failed to initialize ARP devices required for starting the HAIP
resource
Cause: The resource could not be started because the ARP devices failed to start on
the same node.
Action: Manually check the ARP devices on the same node and then start the
resource.
CRS-05030: The resource action "string string" completed with the following error:
string
Cause: An error occurred during the resource action.
Action: Examine the accompanying error messages and respond accordingly.
CRS-05031: invalid instance open mode: 'string'
Cause: The instance open mode passed to the Agent was invalid.
Action: Provide a correct instance open mode and retry.
CRS-05032: incompatible instance open mode: 'string' with the role of the database
in an Oracle Data Guard configuration: 'string'
Cause: The instance open mode passed to the Agent was invalid for the role of the
database in an Oracle Data Guard configuration.
CRS-00001 to CRS-29006 20-115
Action: Provide a correct instance open mode or change the role of the database in an
Oracle Data Guard configuration and retry.
CRS-05033: Open mode 'string' is incompatible with the current instance state
'string'.
Cause: An attempt to change the instance to the specified open mode failed because
the specified mode was incompatible with the current instance state.
Action: Reissue the command with a correct instance open mode.
CRS-05034: failed to get instance connection
Cause: Agent process failed to get an instance connection. Internal error.
CRS-05100: One or more attributes were not found for the entity.
Cause: The operation failed because the entity lacked one or more attributes.
Action: Provide the required attributes and retry the operation.
CRS-05101: The specified entity was not found in the entity list.
Cause: The Cluster Ready Services daemon was unable to locate the input entity in its
entity list.
Action: Retry the operation after deleting the entity and registering it again.
CRS-05102: The entity is already registered.
Cause: An attempt was made to register an entity that was already registered.
Action: If the specification of the entity was incorrect, retry the operation with the
correct entity specification.
CRS-05103: The entity is not registered.
Cause: An attempt was made to operate on an entity that was not registered.
Action: If the specification of the entity was incorrect, retry specifying the correct
entity otherwise register the entity and retry the operation.
CRS-05104: The registration of the entity failed.
Cause: An attempt to register an entity failed. The preceding error messages provide
additional details.
Action: Correct the issues described in the accompanying error messages and retry
the registration.
CRS-05105: Unregistering the entity failed.
Cause: An attempt to unregister an entity failed. The preceding error messages
provide additional details.
Action: Correct the issues described in the accompanying error messages and try to
unregister the entity again.
CRS-05106: The entity failed to start.
Cause: An attempt to start an entity failed. The preceding error messages provide
additional details.
start the entity again.
CRS-05107: The entity failed to stop.

Cause: An attempt to stop an entity failed. The preceding error messages provide
additional details.
stop the entity again.
CRS-05108: The entity failed to relocate.
Cause: An attempt to relocate an entity failed. The preceding error messages provide
additional details.
relocate the entity again.
CRS-05109: The status code is invalid.
Cause: The status code was not of the type enum CLSCRS_STAT.
Action: Verify that the status code argument is a valid code returned from the
CLSCRS API and retry.
CRS-05110: The entity failed to update.
Cause: An attempt to update an entity failed. The preceding error messages provide
additional details.
update the entity again.
CRS-05111: The entity has an invalid profile.
Cause: There were invalid attributes in the entity profile.
Action: Check the entity profile, remove any invalid attributes and retry the
operation.
CRS-05112: The action script of the entity cannot be found.
Cause: The action script of the entity specified by the attribute ACTION_SCRIPT
could not be located.
Action: Ensure that the attribute ACTION_SCRIPT exists and specifies a valid script
for the entity.
CRS-05113: The entity has a dependency error.
Cause: An attempt to operate on an entity failed because of the resulting effect on one
or more dependent entities. Preceding messages provide details on the nature of the
problem.
Action: Take the corrective action as suggested by the preceding messages and
resubmit the operation.
CRS-05114: A placement error was encountered while attempting to operate on the
entity.
Cause: Based on the placement policy for the entity, there was no available server to
which the entity could failover or start.
Action: Check the target server for the entity and restart the entity using the 'crsctl
start' command.
CRS-05115: The specified server is not in the cluster.
Cause: The specified server name did not designate a server in the cluster.
Action: Check the server names in the cluster and retry the operation specifying a
server that is a member of the cluster.
CRS-00001 to CRS-29006 20-117
CRS-05116: The operation on the entity has been cancelled.

Cause: A scheduled or running operation was cancelled.
Action: None
CRS-05117: An internal error occurred while operating on the entity.
Cause: There was an internal error. This message will be preceded by another
message with a more specific problem description.
Action: Review the accompanying error messages and contact Oracle Support
Services.
CRS-05118: The entity or all of its instances are disabled.
Cause: The attempted request could not be serviced because the entity was disabled.
Action: Enable the entity and retry the operation.
CRS-05119: The active version of Cluster Ready Services is below the required
level.
Cause: An attempt was made to use the functionality that has only been available
beginning with the active version specified in the preceding message.
Action: Upgrade to the minimum required version stated in the preceding message.
CRS-05120: The requested action for the entity was aborted due to a timeout.
complete.
CRS-05121: The operation cannot be completed due to invalid arguments.
Cause: Invalid arguments were specified to execute the CRS command.
Action: Check the arguments and specify only valid arguments to the command.
CRS-05122: The entity could not be registered due to a type mismatch.
Cause: The registration of an entity failed because the input entity type to the API did
not match the type of the entity to be registered.
Action: Specify the correct entity type to register the entity.
CRS-05123: The resource validity check failed due to an invalid resource type.
Cause: The value of the attribute TYPE for the resource was not 'application'.
Action: Specify the value 'application' for the resource attribute TYPE.
CRS-05124: The entity has one or more attributes missing.
Cause: The validity check failed to find one or more of the attributes NAME, TYPE or
ACTION_SCRIPT for the entity.
Action: Update the entity to have the missing attributes.
CRS-05125: The action script does not exist for the entity.
Cause: The validity check on the entity failed to find the file specified in the attribute
ACTION_SCRIPT of the entity.
Action: Provide the full path to an existing file for the attribute ACTION_SCRIPT.
CRS-05126: The entity has invalid hosting servers for the placement policy.
Cause: Either the attribute HOSTMEM_REQ was not set or was empty for the entity.
Action: Either set the attribute HOSTMEM_REQ or set the attribute PLACEMENT to
'balanced'.
CRS-05127: The attribute HOSTING_MEMBERS must not be specified for the
entity.
Cause: The attribute HOSTING_MEMBERS was specified for the entity with the
balanced placement policy.
Action: Either unset the attribute HOSTING_MEMBERS or set the entity's placement
policy to be 'favored' or 'restricted'.
CRS-05128: The value of the attribute HOSTING_MEMBERS for the entity is
invalid.
Cause: The value of the attribute HOSTING_MEMBERS for the entity contained one
or more of the characters: ',', ';' or ':'.
Action: Remove the invalid characters from the value of the attribute
HOSTING_MEMBERS.
CRS-05129: An invalid placement policy was specified for the entity.
Cause: The attribute PLACEMENT for the entity was set to an invalid value.
Action: Set the attribute PLACEMENT to either 'favored','restricted', or 'balanced'.
CRS-05130: An invalid value was specified for the attribute AUTO_START.
Cause: The attribute AUTO_START of the entity was set to an invalid value.
Action: Set the attribute AUTO_START to either 'always', 'never', or 'restore'.
CRS-05131: One or more attribute of the entity are set to invalid values.
Cause: An attempt was made to set the attribute to a value of different type.
Action: Check the attributes and set the value to the appropriate type.
CRS-05132: The entity list is not empty.
Cause: The entity list passed to receive the information for the queried CRS entities
was not empty.
Action: Create an empty list to pass as the output argument and retry.
CRS-05133: The generated connection key is too long.
Cause: The size of the environment variables HOST and HOSTNAME were greater
than 255 characters.
Action: Set the environment variables HOST and HOSTNAME to values whose
length is no more than 255 characters.
CRS-05151: Memory could not be allocated.
Cause: An attempt to allocate memory for an entity failed.
Action: Check the system logs, correct the condition and retry the operation.
CRS-05152: The pointer to the context is invalid.
Cause: A null pointer was passed as a pointer to the context.
Action: Create a valid context and pass its address to the requested operation.
CRS-05153: The entity pointer is invalid.
Cause: A null pointer was passed to the API for the entity name or the entity value."
Action: Allocate memory for the entity name and the entity value and pass in the
valid pointers to the API.
CRS-00001 to CRS-29006 20-119
CRS-05154: The input attribute name not found in the entity's attribute list.
Cause: An attempt was made to modify a nonexistent attribute of an entity.
Action: Provide an existing attribute of the entity and retry the operation.
CRS-05155: The end of the entity list was reached.
Cause: An attempt was made to search beyond the end of the entity list.
Action: None
CRS-05156: The entity has no attributes.
Cause: An attempt was made to get the attribute list for an entity that has no
attributes.
Action: Check the entity name that is being passed. If it's correct then delete the
entity, register it with correct attributes and retry the operation.
CRS-05157: The pointer to the operation status message in the entity structure is
null.
Cause: The message pointer in the entity structure was null. The entity maybe
corrupted.
Action: Delete the entity, register the entity and retry the operation.
CRS-05158: The entity list could not be found.
Cause: An attempt was made to perform an operation on an entity list, but no valid
entity list was passed.
Action: None
CRS-05159: The specified entity already exists.
Cause: An attempt was made to add an entity that already exists.
Action: Check the entity name to be added. If it is correct and the existing entity must
be recreated, then delete the entity and retry the operation.
CRS-05160: The entity list is empty.
Cause: The query failed because the entity list was empty.
Action: Retry the query supplying the intended list of entities.
CRS-05161: The entity name contains invalid characters.
Cause: An attempted operation was rejected because the specified entity name
contained invalid characters.
Action: Retry the operation specifying a valid entity name.
CRS-05162: The name of a resource or a filter contains invalid characters.
Cause: An attempted operation was rejected because the specified resource name or
the filter name contained invalid characters.
Action: Retry the operation specifying a valid resource name or the filter name.
CRS-05164: The attribute name is longer than 255 characters.
Cause: An attempt was made to use an attribute name with a length of more than 255
characters.
Action: Use an attribute name shorter than 255 characters and retry the operation.
CRS-05165: The supplied buffer is too small for the filter to string conversion.
Cause: The buffer supplied to the API was too small to hold the output string.
Action: Increase the buffer size and pass it to the API.

CRS-05166: The specified return code is invalid.
Cause: The return code was not of the type 'enum clscrsret'.
Action: Verify that the return code argument is a valid code returned from the
CLSCRS API and retry.
CRS-05501: Unable to connect to eONS server on port number
Cause: The eONS server may not be active or listening on a different port.
Action: Ensure that the eONS resource is ONLINE and listening on the above port.
CRS-05502: Invalid event template string
Cause: The event template specified is invalid.
Action: The event template format must be <PROPERTY|ELEMENT>(attribute
name=<literal|%resource attribute name%>) ...
CRS-05503: Error creating the eONS subscriber
Cause: The eONS server may not be active.
Action: Ensure that the CRS eONS resource is in ONLINE state.
CRS-05504: Node down event reported for node 'string'.
Cause: The specified node was not responsive.
Action: Restart the specified node.
CRS-05601: MDNS: string
Cause: None, generic bypass mdns message.
Action: None
CRS-05602: mDNS service stopping by request.
Cause: MDNSD stopping by OHASD request.
Action: None
CRS-05705: Failed to get required resources
Cause: There was an internal error while evaluating the required resources for the
subject resource.
CRS-05706: No more members to consider
Cause: There was no host found on which to start the resource based on the
placement policy.
Action: Check the placement policy and the required resources for the subject
resource.
CRS-05707: Failed after successful dependency consideration
Cause: There was no host found on which to start the resource based on the
placement policy.
Action: Check the placement policy and the required resources for the subject
resource.
CRS-00001 to CRS-29006 20-121
CRS-05709: Resource 'string' is already running on member 'string'

Cause: An attempt was made to start a resource on a host while it is already running
on that host.
Action: This is an insignificant error. Check the operation being performed.
CRS-05801: Agent path is null or does not resemble a filesystem path
Cause: Unable to spawn the agent program because of incorrect agent path.
Action: Fix the agent path using 'crsctl modify type'.
CRS-05802: Unable to start the agent process
Cause: An attempt to start the agent process failed.
Action: Ensure that the agent path is correct and has the proper permissions, and
retry the command.
CRS-05805: Missing the required action callback in agent
Cause: Unable to execute resource's command.
Action: Ensure that agent executable or action script contains the missing function.
CRS-05809: Failed to execute 'string' value of 'string' for 'string'. Error information
'string', Category : number, OS error : number
Cause: Unable to spawn the resource action script due to incorrect path value or
incorrect permissions or other OS error.
Action: Correct the action script path and permissions or check and fix the reported
OS error.
CRS-05810: Attempt to add a duplicate resource 'string'. Details at string in string.
Cause: An identical resource was already being monitored.
Action: Rename the resource and retry the operation.
CRS-05811: Failed to read ORA_CRS_HOME from environment. Details at string in
string.
Cause: The ORA_CRS_HOME environment variable was not set correctly.
Action: This variable is set during CRS installation. If necessary, reinstall CRS.
CRS-05812: Could not get local hostname. Details at string in string.
Cause: The hostname could not be read.
Action: Check that the hostname for the local machine is valid. If the problem persists,
CRS-05813: Could not change directory to 'string'. Details at string in string.
Cause: The specified path is inaccessible to the agent process.
Action: Check that the specified path exists.
CRS-05814: Agent 'string' started with invalid arguments. Details at string in string.
Cause: An invalid parameter was supplied to the agent.
CRS-05815: Agent 'string' could not find any base type entry points for type 'string'.
Cause: Action entry points were not defined for this agent.
Action: No action necessary if this is a script agent. If this is not a script agent, define
action points in your agent code.
CRS-05816: Agent 'string' could not start implicit monitoring for resource 'string'.
Cause: The resource was currently disabled and hence could not be monitored.
Action: Enable the resource.
CRS-05817: Caught exception from user code for command 'string'. Details at string
in string.
Cause: An exception was thrown from the user code when an action entry point was
called.
Action: This is due to an error in the agent user code. Modify the agent's code to
resolve this.
CRS-05818: Aborted command 'string' for resource 'string'. Details at string in
string.
Cause: Execution of the specified command was aborted due to a timeout.
Action: Restart the resource manually. If the problem persists, contact Oracle Support
Services.
CRS-05819: Could not abort command 'string' for resource 'string'. Details at string
in string.
Cause: Attempt to abort the specified command failed.
Action: Define an abort action entry point for the agent.
CRS-05820: Agent 'string' failed to initialize server process address. Details at string
in string.
Cause: Agent could not connect to the server process.
CRS-05821: Agent 'string' is started with wrong user 'string'. Details at string in
string.
Cause: An incorrect owner was specified for the agent.
Action: Make sure CRSD has enough privileges to spawn programs as the value
specified as the 'owner' in the ACL attribute.
CRS-05822: Agent 'string' disconnected from server. Details at string in string.
Cause: Agent could not connect to server process.
CRS-05823: Could not initialize agent framework. Details at string in string.
Cause: Initialization of the agent failed.
CRS-05824: Could not initialize server connect string 'string'. Details at string in
string.
Cause: Incorrect server connect string was specified in the environment.
CRS-00001 to CRS-29006 20-123
CRS-05825: Agent 'string' is unresponsive and will be restarted. Details at string in

string.
Cause: The specified agent did not respond and will be restarted automatically.
Action: None
CRS-05826: Agent 'string' could not read environment variable 'string'. Details at
string in string.
Cause: The agent could not read a required environment variable.
CRS-05827: Could not find information for resource 'string'. Details at string in
string.
Cause: The specified resource was not found in the internal list of resources.
Action: Check the agent parameters and restart the resource manually.
CRS-05828: Could not start agent 'string'. Details at string in string.
Cause: Creation of the agent process failed.
CRS-05829: Failed to get definition for resource 'string'. Details at string in string.
Cause: The definition of the resource could not be determined.
Action: Delete the resource and add it again using the crsctl command.
CRS-05830: Invalid path 'string' found for agent filename. Details at string in string.
Cause: The path that was specified for the agent was incorrect.
Action: Check that the path exists and is readable.
CRS-05831: Agent 'string' has exceeded maximum failures and has been disabled.
Cause: The specified agent has failed too many times.
CRS-05832: Agent 'string' was unable to process commands. Details at string in
string.
Cause: Agent was unable to process commands.
CRS-05833: Cleaning resource 'string' failed as part of reboot-less node fencing
Cause: A resource 'clean' action associated with reboot-less node eviction encountered
an error. This is an expected occurence in most cases.
Action: None
CRS-05834: Resource 'string' monitoring disabled due to repeated agent failures.
Cause: A cluster resource was disabled because it was causing repeated agent
failures.
Action: Restart the resource after resolving the problems with the agent.
CRS-05835: Agent version incapable of processing this command
Cause: A request encountered an older agent version that is not capable of processing
that request.
Action: Upgrade the agent to the Clusterware version.

CRS-05836: Agent 'string' version 'string' cannot process command. Details at string
in string.
Cause: A request encountered an older agent version that is not capable of processing
that request.
Action: Upgrade the agent to the Clusterware version.
CRS-05837: Unable to open environment file 'string'.
Cause: The environment file specified could not be opened.
Action: Verify that the filename, its location and its permsissions are correct.
CRS-05838: Syntax error in environment file 'string'.
Cause: The environment file specified did not have key value pairs in the correct
format.
Action: Correct the key value format and retry. Consult the administration document
for the correct format.
CRS-05839: The requested action 'string' for the resource 'string' on server 'string'
was aborted due to a timeout.
complete.
CRS-06001: User does not have permission to start CRSD.
Cause: Unable to start CRSD due to insufficient permissions.
Action: Start CRSD as a privileged user.
CRS-06007: Could not communicate with Event Manager.
CRS-06015: Oracle Clusterware has experienced an internal error. Details at string
in string.
CRS-06016: Resource auto-start has completed for server string
Cause: CRS has completed startup of resources on the specified server.
Action: None
CRS-06017: Processing resource auto-start for servers: string
Cause: The blocking start of Oracle High Availability Services has updated its list of
servers to process.
Action: None
CRS-06021: Could not set system resource limits for Clusterware: "ulimit -string
string".
Cause: A ulimit command issued internally to set system resource limits failed.
Action: Ensure that the correct resource limit values are set in the user profile and
limits.conf.
CRS-00001 to CRS-29006 20-125
CRS-06022: Starting Oracle High Availability Services-managed resources

Cause: Oracle High Availability Services is attempting to start resources for the local
server.
Action: None
CRS-06023: Starting Oracle Cluster Ready Services-managed resources
Cause: Oracle Cluster Ready Services is attempting to start resources for the cluster.
Action: None
CRS-06024: Completed start of Oracle Cluster Ready Services-managed resources
Cause: Oracle Cluster Ready Services has started resources for the cluster.
Action: None
CRS-06504: 'string' cannot be specified as an attribute.
Cause: An effort was made to explicitly specify an attribute that cannot be specified
by the user
Action: Remove the mentioned attribute, and re-issue the command.
CRS-06505: Format of the EXPRESSION attribute 'string' is invalid
Cause: The EXPRESSION attribute is invalid.
Action: Provide a valid value for the EXPRESSION attribute.
CRS-06530: cannot set node role because cluster is not configured in "flex" mode
Cause: An attempt to set a node's role using 'crsctl set node role' was rejected because
the cluster is not running in "flex" mode. Node roles can only be set for nodes in "flex"
clusters.
Action: Reissue the command after the cluster is configured in "flex" mode."
CRS-06531: Issued command is not supported in this version of CRS.
Cause: The command was rejected because related feature is not supported in this
release.
CRS-06602: No password specified.\n
Cause: A password was not entered in response to the password prompt.
Action: Enter a password.
CRS-06603: Cannot modify 'string' policy.
Cause: An attempt was made to modify a read-only policy.
Action: Specify a policy that is not read-only.
CRS-06705: Oracle Clusterware Release Version ('string') does not match Software
Version ('string'). Oracle Clusterware cannot be started.
Cause: Oracle Clusterware was started from an older home that has since been
upgraded.
Action: Start Oracle Clusterware from the upgraded home. Also, check the CRS home
configured in olr.loc and the /etc/init.d/ohasd script to make sure they have not
been accidentally changed.
CRS-06706: Oracle Clusterware Release patch level ('number') does not match
Software patch level ('number'). Oracle Clusterware cannot be started.
Cause: Oracle Clusterware was started from an older home that has since been
patched.
Action: Start Oracle Clusterware from the patched home. Also, check the CRS home
configured in olr.loc and the /etc/init.d/ohasd script to make sure they have not
been accidentally changed.
CRS-06749: unable to get the software version
Cause: The crsctl query failed because the software version could not be retrieved.
Either the clusterware stack was down, or the user was not root (UNIX) or
Administrator (WINDOWS).
Action: Bring up the clusterware stack or run the query as a privileged user.
CRS-06750: unable to get the active version
Cause: The crsctl query failed because the active version could not be retrieved. Either
the clusterware stack was down, or the user was not root (UNIX) or Administrator
(WINDOWS).
CRS-06751: unable to get the software patch version
Cause: The crsctl query failed because the software patch version could not be
retrieved. Either the clusterware stack was down, or the user was not root (UNIX) or
Administrator (WINDOWS).
CRS-06752: Active version query failed.
Cause: The crsctl query failed because the active version could not be retrieved.
Action: See the accompanying error message and respond.
CRS-06753: Software patch query failed.
Cause: The crsctl query failed because the software patch version could not be
retrieved.
CRS-06754: Software version query failed for node string.
Cause: The crsctl query failed to retrieve the software version.
CRS-06761: Invalid value for QoS Management policy management key 'string' in
OCR.
Cause: An invalid value for Quality of Service Management policy management key
was found in the OCR.
CRS-06762: Unable to use CRSCTL for Policy Management because Quality of
Service Management (QoS) is managing the Clusterware policies.
Cause: CRSCTL cannot be used for Policy Management because Quality of Service
Management is configured to manage Clusterware policies.
Action: Use Quality of Service Management for Policy Management.
CRS-00001 to CRS-29006 20-127
CRS-07000: Generic GPnP success

CRS-07001: Generic GPnP error
CRS-07002: Not enough memory
CRS-07003: GPnP facility initialization failed
CRS-07004: This feature is unsupported or not implemented
CRS-07005: Requested item not found
CRS-07006: Insufficient buffer size
CRS-07007: Error in file I/O operation
CRS-07008: Invalid permissions for the operation
CRS-07009: Bad authority id
CRS-07010: Key does not exist
CRS-07011: Bad key
CRS-07012: Hostname not found

CRS-07013: GPNPD daemon is not running
CRS-07014: Attempting to set a bad value
CRS-07015: Bad hostname value
CRS-07016: Bad authority id value
CRS-07025: Duplicate profile
CRS-07026: Profile is not given or not available
CRS-07027: Badly formed profile
CRS-07028: Profile is too big to be valid
CRS-07029: Profile is older than the current
CRS-07030: Profile exists in memory only, not saved
CRS-07031: Request retry message from GPNPD
CRS-07032: Value already set in profile
CRS-00001 to CRS-29006 20-129
CRS-07040: Generic XML error

CRS-07041: GPnP XML profile is not well formed
CRS-07047: Communication timeout
CRS-07053: Resource discovery error
CRS-07056: OCR Init error
CRS-07057: Reinit OCR to a different bootlevel
CRS-07058: OCR error
CRS-07065: GPnP wallet error
CRS-07066: Requested GPnP wallet is not found
CRS-07067: Invalid GPnP wallet password given
CRS-07068: GPnP wallet is too big to be valid
CRS-07069: GPnP wallet is corrupted or invalid
CRS-07070: Bad or missing private key in GPnP wallet

CRS-07071: Bad or missing public key in GPnP wallet
CRS-07076: Failed to init crypto libraries
CRS-07085: GPnP profile unsigned
CRS-07086: GPnP profile signature invalid
CRS-07087: GPnP profile valid peer signature
CRS-07088: GPnP profile valid PA signature
CRS-07089: GPnP profile was signed with a different wallet
CRS-07090: Grid Naming Service (GNS) error
CRS-07095: GPnP tool usage
CRS-07096: GPnP tool version
CRS-08000: unable to obtain local host name for reboot advisory log file scan
Cause: An attempt to retrieve the local host name failed. The scan for reboot advisory
files will not use host name criteria and so may report occurrences for other nodes as
well as this one.
CRS-08001: an error occurred accessing reboot advisory log file location: string
Cause: The scan for reboot advisory log files was unable to access the indicated file
system location. The location was skipped, so any reboot advisory files that it contains
CRS-00001 to CRS-29006 20-131
will not be reported. This message is accompanied by CLSU- messages containing

details of the access error.
Action: Respond based on the error described by the accompanying CLSU- messages.
This may involve re-creating the directory or changing its permissions.
CRS-08002: an error occurred searching reboot advisory log file location: string
Cause: The scan for reboot advisory log files was unable to read the next file name
from the indicated file system location. No further processing of reboot advisory files
from that location occurs. This message is accompanied by CLSU- messages
containing details of the access error.
Action: Respond based on the error described by the accompanying CLSU- messages.
CRS-08003: reboot advisory log file: string is unexpectedly empty
Cause: The scan for reboot advisory log files encountered a file that was empty. This
might happen (rarely) if a component is initializing its use of reboot advisory at the
same time the scan is running. Processing of other files in the location continues.
Action: Frequent occurrence of this message should be reported to Oracle Support
Services.
CRS-08004: an error occurred reading reboot advisory log file: string
Cause: The scan for reboot advisory log files experienced a read error on a reboot
advisory file. No further processing is done for that file, but the scan continues with
other files. This message is accompanied by CLSU- messages containing details of the
read error.
Action: Respond based on the accompanying CLSU- messages.
CRS-08005: an error occurred closing reboot advisory log file: string
Cause: The scan for reboot advisory log files experienced a close error on a reboot
advisory file. The scan continues with other files. This message is accompanied by
CLSU- messages containing details of the close error.
CRS-08006: an error occurred opening reboot advisory log file: string
Cause: The scan for reboot advisory log files experienced an error when it opened a
reboot advisory file. The scan continues with other files. This message is accompanied
by CLSU- messages containing details of the open error.
Action: If the error indicated in the accompanying CLSU- messages is one that can be
corrected, do so. Otherwise, report this error to Oracle Support Services.
CRS-08007: an error occurred closing reboot advisory log file location: string
Cause: The scan for reboot advisory log files experienced an error when it closed the
indicated file system location. Processing of other reboot advisory locations (if any)
continues normally. This message is accompanied by CLSU- messages containing
details of the close error.
CRS-08008: string
Cause: Operating system error data related to reboot advisory file processing was
returned. The error data is packaged in a CLSU- message that follows "CRS-08008:".
One or more of these messages appears after a message announcing the error
condition.
Action: Look up the embedded CLSU- message for an explanation of the operating
system error data. If there is no CLSU- message ID present, contact Oracle Support
Services.
CRS-08009: reboot advisory log file: string contains invalid data (length number,
error code number)
Cause: A reboot advisory log record read from the indicated file contained incorrect
data.
CRS-08010: invalid network reboot advisory message detected (length number,
error code number)
Cause: A reboot advisory record received over the network was improperly formed
or contained incorrect data.
CRS-08011: reboot advisory message from host: string, component: string, with time
stamp: string
Cause: A reboot advisory message was detected. During Oracle Clusterware startup
on a given host, messages recently written to disk on that host before a reset or reboot
are detected and announced. Subsequently, network reboot advisory messages may
be announced as they occur. These are reported by hosts other than the one being
reset or rebooted. This message is accompanied by other messages containing details
on what led to the reset or reboot. The time stamp in this message begins with either
'U' (denoting UTC time) or 'L' (denoting local time as viewed by the issuing host).
Note that a given reset or reboot event can produce multiple occurrences of these
messages on multiple hosts in the cluster.
Action: Use the reboot advisory message(s) to determine why Oracle Clusterware
caused a reset or reboot of the affected host, and respond accordingly. Refer to the
discussion of reboot advisories in the Oracle Clusterware administration
documentation for additional guidance.
CRS-08012: reboot advisory message from a higher Oracle Clusterware version
detected
Cause: A reboot advisory message from a higher version installation of Oracle
Clusterware was detected. This is an expected occurrence with network reboot
advisories when there are nodes with a higher Oracle Clusterware version than this
node (such as during an upgrade). It is an unexpected condition with file reboot
advisories.
Action: The reboot advisory message is displayed in a following CRS-08013 message
in a "raw" text form. In the case of network reboot advisories, the explanatory
message text should be readable and useful to determine the cause of the node reboot.
If the reboot advisory message is from a file, report this message to Oracle Support
Services.
CRS-08013: reboot advisory message text: string
Cause: An explanatory text message associated with a reboot advisory announced in
a preceding CRS-08011 or CRS-08012 message was displayed. These text messages are
always written in US English locale.
Action: Refer to the descriptions of messages CRS-08011 and -08012, and to the Oracle
Clusterware documentation on reboot advisories.
CRS-00001 to CRS-29006 20-133
CRS-08014: reboot advisory binary data (number bytesstring) follows:

Cause: Binary data associated with a reboot advisory message was displayed. It is
followed by one or more lines of CRS-08015 message containing the binary data
formatted in hexadecimal. If an asterisk appears inside the parentheses, an invalid
data length was detected.
Action: Refer to the description of message CRS-08011 and -08012, and to the Oracle
CRS-08015: number string
Cause: Hexadecimal display of binary data included in a reboot advisory log message
was displayed. The first number is an offset and is followed by up to 16 bytes of data.
Action: Refer to the description of message CRS-08011 and -08012, and to the Oracle
CRS-08016: an error occurred determining the location for reboot advisory log files
Cause: The search for reboot advisory log files was unable to determine the file
system location used for those files. Processing of reboot advisory files is skipped.
This message is accompanied by CLSU- messages containing failure details. This is an
internal error.
CRS-08017: location: string has number reboot advisory log files, number were
announced and number errors occurred
Cause: This summary message is written during Oracle Clusterware startup if one or
more reboot advisory log files was found and examined.
Action: This message is informational, but if the error count is nonzero the associated
messages (earlier in the alert log) should be examined.
CRS-08018: warning: missing cluster identity data for reboot advisory message
validation
Cause: During Oracle Clusterware start up, an attempt to obtain the identity of the
cluster failed. Processing continues normally, but network reboot advisories from
nodes in other clusters may be reported in this cluster's alert log.
CRS-08019: warning generated by the initialization of the reboot advisory in the
CSS agent, string
Cause: During initialization of the reboot advisory, a warning was generated
Action: Report this warning to Oracle Support Services.
CRS-08020: error generated by the initialization of the reboot advisory in the CSS
agent, string
Cause: During initialization of the reboot advisory, an error was generated.
CRS-08500: Oracle Clusterware string process is starting with operating system
process ID string
Cause: The indicated service or component of Oracle Clusterware began execution.
Action: None
CRS-08501: Oracle Clusterware string process with operating system process ID

string is ending with return value number
Cause: The indicated service or component of Oracle Clusterware ended execution.
Action: None
string failed in initialization
Cause: The indicated service or component of Oracle Clusterware was unable to
complete initialization.
string experienced fatal signal or exception code number
Cause: The indicated service or component of Oracle Clusterware encountered a fatal
exception.
string is exiting
Cause: The indicated service or component of Oracle Clusterware ended execution
using the operating system 'exit' function.
Action: None
string experienced fatal error string-number
Cause: The indicated service or component of Oracle Clusterware encountered an
internal error, causing an ADR incident to be raised.
CRS-09000: Failed to allocate memory.
Cause: During intialization, memory could not be allocated.
CRS-09001: Internal Error
CRS-09003: Cluster Health Monitor is not supported in this configuration.
Cause: Grid Infrastructure Management Repository was not configured.
Action: Re-Install Grid Infrastructure and ensure that Grid Infrastructure
Management Repository is configured.
CRS-09004: Error reading from standard input
Cause: Could not read commands from the command line.
CRS-09005: Quoted string not ended
Cause: An unmatched " was found in the command entered.
Action: Put in the corresponding quote or remove the unmatched quote.
CRS-00001 to CRS-29006 20-135
CRS-09008: Unknown verb string

Cause: Unknown or invalid verb passed to oclumon.
Action: Use 'oclumon -h' in command line or help command in interactive mode to
see the supported verbs.
CRS-09009: Error string: Parsing error. Invalid arguments specified.
Cause: Invalid or unknown arguments passed.
Action: Refer to product documentation or to command online help for an
explanation of verbs and arguments.
CRS-09010: Error string: mandatory data not supplied
Cause: Mandatory data not supplied to the command.
Action: Refer to product documentation or to command online help for an
explanation of verbs and arguments.
CRS-09011: Error string: Failed to initialize connection to the Cluster Logger Service
Cause: Error occurred while connecting to the Cluster Logger Service.
Action: Ensure that Cluster Logger Service is running and reachable from the client
node by using the 'ping' command for the given node.
CRS-09012: Error string: Error sending query to the Cluster Logger Service
Cause: Error occurred while sending query to the Cluster Logger Service.
Action: Ensure that the Cluster Logger Service is running and reachable from the
client node by using the 'ping' command for the specified node.
CRS-09013: Error string: Invalid data received from the Cluster Logger Service
Cause: Invalid or unknown data received from the Cluster Logger Service.
CRS-09014: Error: Corrupt reply from the Cluster Logger Service
Cause: Invalid or unknown data received from the Cluster Logger Service.
Action: Make sure that the version of both master and client installation is same. Also,
check the connectivity between master and client using the 'ping'.
CRS-09017: Error: Invalid or unknown reply received from the Cluster Logger
Service
Cause: Error occurred in the data received.
Action: Make sure that the version of both master and client installation is same. Also,
check the connectivity between master and client.
CRS-09018: Error string: No arguments supplied
Cause: No argument was supplied with the command.
Action: Some commands need arguments with them. Refer to the product
documentation or to the online help display.
CRS-09019: Error string: No parameter string supported
Cause: A wrong parameter was passed with the command.
Action: Refer to the command help and pass the correct parameters.
CRS-09020: Error string: No master node name specified

Cause: The master node name was not specified in the command.
Action: Pass the appropriate master node name with the command.
CRS-09021: Error string: Invalid or no start time specified
Cause: A start time was not specified or the time was passed in the wrong format.
Action: Pass the correct start time. For correct format, refer to command help.
CRS-09022: Error string: Invalid or no end time specified
Cause: A end time was not specified or the time was passed in the wrong format.
Action: Pass the correct end time. For correct format, refer to command help.
CRS-09023: Error string: Time not specified or in wrong format or invalid
Cause: Time was not specified or was invalid.
Action: Pass the correct and valid time. For correct format, refer to command help.
CRS-09024: Error string: No node name specified
Cause: Node name not specified.
Action: Provide a node name in the command. Refer to the product documentation or
to the command online help for information.
CRS-09025: Error string: No disk ID name specified
Cause: Disk ID was not specified in the command with -diskid.
Action: Pass a valid disk ID with -diskid option.
CRS-09026: Error string: No parameter specified
Cause: The parameter was not specified in the query.
Action: Pass appropriate parameter for query. Refer to the product documentation or
CRS-09027: Error string: Parameter string is not supported with this verb
Cause: Invalid or unknown parameter passed.
Action: Pass the correct parameter. Refer to the product documentation or to the
command online help for information.
CRS-09028: Error string: No NIC ID specified
Cause: NIC ID was not specified in the command with -nicid.
Action: Pass a valid NIC ID with -nic option.
CRS-09029: Error string: No PID specified
Cause: PID was not specified in the command with -pid.
Action: Pass a valid PID with -pid option.
CRS-09030: Error string: No region specified
Cause: Incorrect or no region specified with -c option.
Action: Pass a valid region with -c option. Refer to the product documentation or to
the command online help for information.
CRS-09031: Error string: Argument string not supported with this verb
Cause: Unknown or invalid argument passed with the command.
CRS-00001 to CRS-29006 20-137
Action: Refer to the product documentation or to the command online help for
information on supported arguments.
CRS-09032: Invalid hour specified in the time argument
Cause: Invalid hour in the time string was passed.
Action: Pass a valid time string in accordance with the format. Refer to the product
documentation or to the command online help for information on supported
arguments.
CRS-09033: Invalid minutes specified in the time argument
Cause: Invalid minutes in the time string was passed.
arguments.
CRS-09034: Invalid seconds specified in the time argument
Cause: Invalid seconds in the time string was passed.
arguments.
CRS-09035: Arguments not in proper format, or invalid arguments
Cause: Invalid arguments specified.
Action: Pass a valid verb and correct arguments for it. Refer to the product
arguments.
CRS-09036: Invalid Cluster Health Monitor repository size specified
Cause: Non-numeric value or value out of range specified for Cluster Health Monitor
repository size.
Action: Specify Cluster Health Monitor repository size in the valid range. Refer to the
product documentation or to the command online help for information on supported
arguments.
CRS-09037: string Error: Node name not specified. -disk, -nic or -proc need node
name
Cause: The required node name was not specified for -disk, -nic or -proc.
Action: Provide a node name with -n option. Refer to the product documentation or
to the command online help for information on supported arguments.
CRS-09038: Error: -s and -e need to be specified together
Cause: Either -s or -e is missing.
Action: Start and end time need to be specified together for range queries, which
cannot be unbounded. Refer to the product documentation or to the command online
help for information on supported arguments.
CRS-09039: Error string: -i is not allowed with the range query
Cause: The -i option was specified on a oclumon range query.
Action: Use -i only in continuous mode. Refer to the command inline help or product
documentation for more information.
CRS-09040: Error string: Band value not specified or incorrect

Cause: The band value was not specified with -t option or was invalid.
Action: Provide a valid band value. Refer to the product documentation or to the
command online help for information on supported arguments..
CRS-09041: Error string: The -repos argument was specified without an option.
Cause: -repos was not specified with the option, generating a parsing error.
Action: Provide a valid option to -repos. Refer to the product documentation or to the
command online help for information on supported arguments.
CRS-09042: Error string: No size specified with 'checkretentiontime'
Cause: A valid value was not specified with 'checkretentiontime'.
Action: Provide a valid numerical value with 'checkretentiontime'. Refer to the
arguments.
CRS-09043: Error string: Non-numeric or invalid value for size: string
Cause: An invalid or non-numeric value was specified for size.
Action: Provide a valid numeric size. Refer to the product documentation or to the
CRS-09044: No key specified with -getkey
Cause: An option was not specified with -getkey.
Action: Provide a valid key as an option with -getkey.
CRS-09045: No key specified for -get
Cause: An option was not specified with -get.
Action: Provide a valid option with -get. Refer to the product documentation or to the
CRS-09046: Invalid key specified
Cause: An unknown key was specified with -get.
Action: Provide a supported key with -get. Refer to the product documentation or to
the command online help for information on supported arguments.
CRS-09047: Error string: Error Dumping Log (return code:number ) for node string
Cause: An error occurred while dumping local log.
Action: Report this error to Oracle Support Services. Cluster Health Monitor
repository directory may be unreachable, unreadable or incorrect.
CRS-09048: Error string: No data received from the Cluster Logger Service after
number attempts
Cause: Data was not received from the Cluster Logger Service after the specified
number of attempts or data was not available.
Action: None
CRS-09049: Error string: Cannot get environment variable CRFHOME
CRS-00001 to CRS-29006 20-139
CRS-09050: Error string: Too many host names

Cause: Too many host names were specified.
Action: Provide valid number of host names. Refer to the product documentation or
CRS-09051: Error string: Invalid interval size specified
Cause: Non-numeric or invalid interval specified.
Action: Provide a valid numerical value for interval size. Refer to the product
documentation or to the command online help for information
CRS-09052: Error string: string control not supported
Cause: The specified debug control was not supported.
Action: Provide a supported control. Refer to the product documentation or to the
command online help for information.
CRS-09053: Key:value pair missing
Cause: A required key:value pair was missing.
Action: Provide a valid key:value pair. Refer to the product documentation or to the
command online help for information
CRS-09054: Incomplete or invalid parameters string
Cause: Incomplete or invalid parameters supplied.
Action: Provide the complete and correct parameters. Refer to the product
documentation or to the command online help for information
CRS-09055: module:level specified in invalid format or invalid value
Cause: Invalid format or value specified for module:level.
Action: Provide correct module:level. Refer to the product documentation or to the
command online help for information
CRS-09056: Error string: Invalid Cluster Health Monitor repository location
specified
Cause: Invalid Cluster Health Monitor repository location specified.
Action: Provide a directory with read and write permissions for Cluster Health
Monitor repository location. Refer to the product documentation or to the command
online help for information.
CRS-09057: Error string: No response received from the Cluster Logger Service
Cause: No data received from the Cluster Logger Service for the query.
CRS-09058: Error string: Changing log level failed due to authentication failure
Cause: Log level could not be changed due to authentication failure.
Action: Ensure that this command is run as root.
CRS-09059: Error string: Changing log level failed due to connection failure
Cause: A connection failure occurred while changing the log.
Action: Ensure that the daemons are running and are reachable.
CRS-09060: Error string: Unable to send message due to memory allocation failure
Cause: Memory could not be allocated for debug message.
CRS-09061: Error string: Changing log level failed due to response time-out
Cause: A time out happened while waiting for response.
CRS-09062: Error string: Error in changing log level
Cause: An error occurred while changing log level.
CRS-09063: Given time range is more than 1 hour
Cause: The time range specified with showtrail command was more than one hour.
Action: Provide a range of less than 1 hour for showtrail.
CRS-09064: Error string: Changing log level failed due to connection failure.
Cannot connect to daemon string.
Cause: A connection failure occurred while changing the log level.
Action: Ensure that the specified daemon is running and reachable.
CRS-09065: Disk ID not found
Cause: Given disk ID was not found or not present in the interesting list.
Action: Provide a disk ID which is available at the start of the query range.
CRS-09066: Process ID not found
Cause: Given process ID was not found.
Action: Provide a process ID which is available at the start of the query range.
CRS-09067: NIC ID not found
Cause: Given NIC ID was not found.
Action: Provide a correct NIC ID.
CRS-09068: Error string: -allnodes and -n must not be used together
Cause: Both -allnodes and -n were supplied on a dumpnodeview command.
Action: Specify either -allnodes or -n with specific nodes.
CRS-09069: The new Cluster Health Monitor repository location is string.
Cause: The Cluster Health Monitor repository location was successfully replaced.
Action: None
CRS-09070: The new Cluster Health Monitor repository retention time is number
seconds.
Cause: The Cluster Health Monitor repository retention time was successfully
modified.
Action: None
CRS-09071: Internal error in Cluster Health Analysis during problem analysis
Cause: An internal error occurred during problem analysis.
CRS-00001 to CRS-29006 20-141
CRS-09072: Internal error in Cluster Health Analysis report output

Cause: An internal error occurred while reporting a problem.
CRS-09073: No problems to display
Cause: No problems were found that matched the selection criteria specified to the
'oclumon analyze' command.
Action: None
CRS-09074: No component specified to the component argument
Cause: An 'oclumon analyze' command was issued without a component.
Action: Provide a component to the 'oclumon analyze' command. Refer to the product
documentation or to the command online help for information.
CRS-09075: Invalid component name 'string' specified as the component argument
Cause: An 'oclumon analyze' command was issued with an invalid component.
Action: Pass a valid component to the 'oclumon analyze' command. Refer to the
arguments.
CRS-09076: Error loading the required Cluster Health models
Cause: The required Cluster Health models did not exist, did not have the required
permission, or had an invalid format.
Action: Ensure that the Cluster Health models are present in the 'cdata/model'
subdirectory of the Oracle Grid Infrastructure home, and that their permissions are
correct. If the problem persists, check for entries in the oclumon log file for more
details.
CRS-09077: Invalid path 'string' was specified as the data directory argument
Cause: An 'oclumon analyze' command was issued specifying a data directory that
does not exist or is not accessible to the user.
Action: Pass a valid path to the 'oclumon analyze' command. Look at accompanying
messages for more information.
CRS-09078: Invalid severity value 'string' provided as the severity argument
Cause: An 'oclumon analyze' command was issued with an invalid severity value.
Action: Pass a valid severity value to the 'oclumon analyze' command. Refer to the
product documentation or to the command online help for information.
CRS-09079: No instance name specified for the instance argument
Cause: An 'oclumon' command was issued without an instance name.
Action: Provide an instance name with the 'oclumon' command. Refer to the product
CRS-09080: data for other nodes of cluster cannot be viewed from this node
Cause: An 'oclumon dumpnodeview -n' command was issued for other nodes from a
leaf node.
Action: Refer to the Cluster Health Monitor documentation for more information.
CRS-09081: Internal error in Cluster Health calibration
Cause: An internal error occurred during cluster health model calibration.

CRS-09082: Insufficient permission to execute command. Require privileged user
Cause: A non-privileged user attempted to execute a command requiring privilege.
Action: Issue the command again as a privileged user.
CRS-09083: No database name specified for the database argument
Cause: An 'oclumon' command was issued without a database name.
Action: Provide a database name with the 'oclumon' command. Refer to the product
CRS-09084: Error string: Node name is greater than string bytes
Cause: An 'oclumon' command was issued with a node name that was too long.
Action: Supply a node name no greater than the indicated size with the 'oclumon'
command and retry. Refer to the product documentation or to the command online
help for information.
CRS-09085: Model name missing or invalid for the model argument
Cause: The previous oclumon command was rejected because it did not include a
valid model name.
Action: Reissue the oclumon command providing a valid model name. Refer to the
CRS-09086: Server pool name missing or invalid for the server pool argument
Cause: The previous oclumon command was rejected because it did not include a
valid server pool name.
Action: Reissue the oclumon command providing a valid server pool name. Refer to
the product documentation or to the command online help for information.
CRS-09087: Server pool name specified in a cluster without user-defined server
pools
Cause: The previous oclumon command was rejected because it was issued with a
server pool name on a cluster without user-defined server pools.
Action: Reissue the oclumon command without a server pool name. Refer to the
CRS-09088: Node name specified in a cluster with user-defined server pools
Cause: The previous oclumon command was rejected because it was issued with a
node name on a cluster with user-defined server pools.
Action: Reissue the oclumon command without a node name. Refer to the product
CRS-09089: Parameter 'string' is not supported in combination with parameter
'string'.
Cause: The command was rejected because the combination of parameters passed
was invalid.
Action: Refer to the product documentation or to the online help for the command
and reissue the command with the correct parameters.
CRS-09090: Error string: Parameter 'string' is specified multiple times.
Cause: The previous 'oclumon' command was rejected because the parameter listed in
the message was specified multiple times.
CRS-00001 to CRS-29006 20-143
Action: Refer to the product documentation or to the online help for the command
and reissue the command with the correct parameters.
CRS-09091: database name 'string' is invalid
Cause: An 'oclumon' command was issued with an invalid database name.
Action: Provide a valid database name with the 'oclumon' command. Refer to the
product documentation or to the online help for the command for information.
CRS-09092: No instance of database 'string' is active on this node.
Cause: The 'oclumon calibrate' command was rejected because no instance of the
above listed database was active on the local node.
Action: Issue the 'srvctl start database' command to start the above listed database.
Issue the 'srvctl status database' command to retrieve a list of nodes on which the
database instances are online. Issue the 'oclumon calibrate' command again from a
node on which the database instance is online. Refer to the product documentation or
to the online help for the command for information.
CRS-09093: Database 'string' of type 'string' is not supported in a cluster with userdefined server pools.
Cause: An 'oclumon' command was issued with an administrator-managed database
in a cluster with user-defined server pools.
Action: Reconfigure the database to be policy-managed using the 'srvctl modify
database' command to enable monitoring by the Oracle Cluster Health Analysis
service. Verify the monitoring status using the 'srvctl status cha' command. Re-issue
the 'oclumon calibrate' command. Refer to the product documentation or to the online
help for the command for information.
CRS-09100: Error setting Cluster Health Monitor repository size
Cause: An error occurred while setting Cluster Health Monitor repository size on the
Cluster Logger Service.
CRS-09101: Error updating Cluster Health Monitor repository size in configuration
file.
Cause: An error occurred while writing the Cluster Health Monitor repository size to
configuration files.
CRS-09102: No data for the node at the specified time
Cause: Data was not found for the specified node.
CRS-09103: No data available
Cause: Data was not available for the query.
Action: Make sure the System Monitor Service is running on the specified node.
CRS-09104: No data available for the specified nodes
Cause: Data was not available for specified nodes.
Action: Make sure the System Monitor Service is running on the specified nodes.
CRS-09105: Internal Error on master
Cause: An internal error on master caused this error.

CRS-09106: Data requested was outside Cluster Health Monitor retention time
limits.
Cause: A request for data outside Cluster Health Monitor repository limit caused this
error.
Action: Data needs to be requested in the proper Cluster Health Monitor repository
limits. Refer to the product documentation for more information.
CRS-09107: Start time greater than end time
Cause: A start time greater [or later] than end time caused an error.
Action: Make sure the start time is less than the end time for the specified range
query.
CRS-09108: Threshold out of acceptable range
Cause: A threshold was specified that is outside the allowed range.
Action: Make sure threshold is within the acceptable range. Refer documentation or
online help for more information
CRS-09109: New Cluster Health Monitor repository location same as the old
location on node string
Cause: The new location specified for Cluster Health Monitor repository is same as
the old location.
Action: Provide a different location for Cluster Health Monitor repository. Refer
documentation or online help for more information.
CRS-09110: Cluster Health Monitor repository location not changed as the location
specified does not exist on node string.
Cause: The new location specified for Cluster Health Monitor repository does not
exist.
Action: Provide a different location for Cluster Health Monitor repository. Refer
documentation or online help for more information.
CRS-09111: Error updating Cluster Health Monitor repository location string in
configuration file.
Cause: An error occurred while writing the Cluster Health Monitor repository
location to configuration files.
CRS-09114: Cluster Health Monitor repository location change failed on one or
more nodes. Aborting location change.
Cause: An error occurred while setting Cluster Health Monitor repository location on
the Cluster Logger Service.
Action: Retry specifying a valid location.
CRS-09116: Cluster Health Monitor repository retention change failed on one or
more nodes. Aborting retention change.
Cause: An error occurred while setting Cluster Health Monitor repository size on the
Cluster Logger Service.
Action: Retry specifying a valid location.
CRS-00001 to CRS-29006 20-145
CRS-09117: Grid Infrastructure Management Repository configuration error \n

string
Cause: Grid Infrastructure Management Repository configuration error occurred.
Action: Take the following steps. 1) Examine the accompanying ORA-nnnnn or CRSnnnn error messages. If possible, correct the issue reported. 2) Issue a 'srvctl status
mgmtdb' command to determine the status of the Grid Infrastructure Management
Repository database. If it is not online, examine the database instance alert log to
run 'diagcollection.pl' and contact Oracle Support Services.
CRS-09118: Grid Infrastructure Management Repository connection error \n string
Cause: Grid Infrastructure Management Repository connection error occurred.
CRS-09119: Warning: string option has been deprecated and will be ignored.
Cause: A deprecated option was specified on the command line. The option was
ignored.
Action: Check the documentation for the new syntax of the command.
CRS-09120: oclumon was not able to connect to the Grid Infrastructure
Management Repository because an authorization failure occurred. \nstring
Cause: An authorization failure occurred when connecting to the Grid Infrastructure
Management Repository.
Action: Run the 'srvctl config mgmtdb' command to verify that Grid Infrastructure
Management Repository has been created successfully. If not, run the 'mgmtca'
command to reset the passwords in the wallet. If the problem persists, run
'diagcollection.pl' and contact Oracle Support Services.
Management Repository because no listener was available.
Cause: An attempt to connect to the Grid Infrastructure Management Repository
failed because no Grid Infrastructure Management Repository listener was running.
Action: Use the 'srvctl status mgmtlsnr' command to confirm that Grid Infrastructure
Management Repository listener is running. If it is not, start it using the 'srvctl start
mgmtlsnr' command. If the problem persists, run 'diagcollection.pl' and contact
CRS-09122: oclumon was not able to retrieve the security keys from the wallet.
Cause: An attempt to retrieve the security keys from the wallet failed.
Action: Run the 'crsctl query wallet -type MGMTDB' command to verify that the
wallet exists. If the problem persists, contact Oracle Support Services.
Management Repository because a Cluster Synchronization Services request failed.
failed due to a Cluster Synchronization Services failure.
Action: If the problem persists, run 'diagcollection.pl' and contact Oracle Support
Services.
CRS-09124: Cluster Health Monitor repository retention change failed. Aborting
retention change. Error: string
Cause: An error occurred while setting the Cluster Health Monitor repository size on
the cluster logger service.
CRS-09125: Error string: string is an invalid node name.
Cause: The 'oclumon' command could not be carried out as entered because the node
name cited in the message was invalid. The cited node name was ignored and the
query executed with any remaining names.
Action: Reissue the 'oclumon' command, if desired, supplying a valid name for the
node name cited in the message. Refer to the product documentation or to command
online help for information.
CRS-09500: The System Monitor Service aborted on host string. Details at string in
string.
Cause: The System Monitor Service aborted due to an internal error.
Services.
CRS-09501: The Cluster Logger Service aborted on host string. Details at string in
string.
Cause: The Cluster Logger Service aborted due to an internal error.
Services.
CRS-09502: The Cluster Health Monitor repository location string is inaccessible.
Cause: An error occurred while accessing the Cluster Health repository.
Action: Check that the Cluster Health Monitor repository location in question has the
correct permissions. Determine whether this behavior is limited to one node or
whether it occurs across all of the nodes in the cluster. Use the 'oclumon manage repos reploc location' command to replace the Cluster Health Monitor repository
location.
CRS-09503: The System Monitor Service on this host is unable to communicate
with the Cluster Logger Service on host string, and will log the Cluster Health
Monitor data to the local repository.
Cause: Communication was lost with the Cluster Logger Service node.
problematic connections. If network problems are not found, execute the following
steps: 1. Run diagcollection.pl. 2. Contact Oracle Support Services.
CRS-00001 to CRS-29006 20-147
CRS-09504: The Cluster Logger Service on host string is dropping the Cluster
Health Monitor node view. Details at string in string.
Cause: The Cluster Logger Service was unable to insert Cluster Health Monitor node
view into Cluster Health Monitor repository .
CRS-09505: The Cluster Health Monitor repository is deleted due to corruption and
the Cluster Logger Service is disabled on string. Details at string in string.
Cause: A critical error occurred while operating on Cluster Health Monitor
repository.
CRS-09506: The System Monitor Service local repository is disabled on the host
string. Details at string in string.
Cause: An internal error occurred while writing to the System Monitor Service local
repository.
CRS-09507: The maximum Cluster Health Monitor repository retention time is
reached. Deleting the oldest Cluster Health Monitor node views in age order.
Cause: The maximum time for which the oldest Cluster Health Monitor node view
will be available on Cluster Health Monitor repository was reached.
Action: If necessary, use 'oclumon manage -repos changerepossize size' command to
change the retention time.
CRS-09508: The Cluster Health Monitor repository retention time cannot be
changed due to lack of disk space on node string.
Cause: The Cluster Health Monitor retention time condition could not be fulfilled
because the Cluster Health Monitor repository ran out of disk space at run time at the
repository location.
Action: Use the 'oclumon manage -repos reploc location' command to replace the
Cluster Health Monitor repository with a disk location that has at least 1GB of
available space per cluster node.
CRS-09509: The new Cluster Logger Service master is string.
Cause: A new Cluster Logger Service master node was elected.
Action: None
CRS-09510: The new Cluster Logger Service replica is string.
Cause: A new Cluster Logger Service replica node was elected.
Action: None
CRS-09511: The System Monitor Service was not able to collect disk information on
node string.
Cause: There was a problem in reading the disk-related information.
Action: Confirm that disks are properly configured and usable on the indicated node.
If no issues are found and the problem persists, run 'diagcollection.pl' and contact
CRS-09512: The System Monitor Service was not able to collect network interface
card information on node string.
Cause: There was a problem in reading the network interface card related
information.
Action: Confirm that network interface cards are properly configured and usable on
the indicated node. If no issues are found and the problem persists, run
CRS-09513: The version of the Grid Infrastructure Management Repository [string]
is incompatible with the version of the Oracle Clusterware [string].
Cause: During startup, the Cluster Logger Service found that the version of Grid
Infrastructure Management Repository was older than that of the Oracle Clusterware.
Action: Upgrade the Grid Infrastructure Management Repository to a version which
is at least that of the Oracle Clusterware.
CRS-09514: The Cluster Logger Service encountered an unexpected error during
inserting the data into the Grid Infrastructure Management Repository. \nstring.
Cause: An unexpected Oracle error was returned by the Grid Infrastructure
Action: 1) Examine the accompanying ORA-nnnnn error messages. If possible, correct
the issue reported. 2) Issue a 'srvctl status mgmtdb' command to determine the status
of the Grid Infrastructure Management Repository database. If it is not online,
examine the database instance alert log to determine what happened. 3) If you are
unable to determine or correct the problem, contact Oracle Support Services.
CRS-09515: The Cluster Logger Service encountered an unexpected error during
deleting the data from Grid Infrastructure Management Repository. \nstring.
CRS-09516: Encountered an unexpected error during querying the data from Grid
Infrastructure Management Repository. \nstring.
CRS-09517: An unrecoverable configuration error occurred in the Grid
Infrastructure Management Repository. Details at string in string. \nstring
Cause: An unexpected condition happened in the Grid Infrastructure Management
Repository.
CRS-00001 to CRS-29006 20-149
CRS-09518: The Cluster Logger Service was not able to connect to the Grid
Infrastructure Management Repository because an authorization failure occurred.
\nstring
Cause: An authorization failure occurred when connecting to the Grid Infrastructure
Management Repository has been created successfully. If not, run the 'mgmtca'
command to reset the passwords in the wallet. If the problem persists, run
Infrastructure Management Repository because no listener was available.
failed because no Grid Infrastructure Management Repository listener was running.
Action: Use the 'srvctl status mgmtlsnr' command to confirm that Grid Infrastructure
Management Repository listener is running. If it is not, start it using the 'srvctl start
mgmtlsnr' command. If the problem persists, run 'diagcollection.pl' and contact
CRS-09520: The storage of Grid Infrastructure Management Repository is number%
% full. The storage location is 'string'.
Cause: The storage of Grid Infrastructure Management Repository was close to full.
This storage can be a shared file system or an Oracle ASM disk group.
Action: Make sure there is sufficient free space in repository location.
CRS-09521: Grid Infrastructure Management Repository was not available on the
node string. The System Monitor Service will store the data in its local repository
on all nodes. \nstring
Cause: Grid Infrastructure Management Repository was initializing or was shutting
down when the Cluster Logger Service tried to connect, insert or delete the data.
Action: Check if the Grid Infrastructure Management Repository is online using the
'srvctl status mgmtdb' command. If it is offline, start it using the 'srvctl start mgmtdb'
command.
CRS-09522: The Cluster Logger Service was not able to retrieve the security keys
from the wallet.
Cause: The Cluster Logger Service could not get the security keys due a wallet read
failure.
Action: Run the 'crsctl query wallet -type MGMTDB' command to verify that the
wallet exists. If the problem persists, contact Oracle Support Services.
Infrastructure Management Repository because a Cluster Synchronization Services
request failed.
failed due to a Cluster Synchronization Services failure.
Services.
CRS-09524: The System Monitor Service on this host is unable to communicate

with the Cluster Logger Service on host string, and will log the Cluster Health
Analysis data to the local repository.
Cause: Communication was lost with the Cluster Logger Service node.
problematic connections. If network problems are not found, execute the following
steps: 1. Run diagcollection.pl. 2. Contact Oracle Support Services.
CRS-09525: The Cluster Health Analysis local repository is disabled on host string.
Cause: An internal error occurred while writing to the Cluster Health Analysis local
repository.
CRS-09526: The Cluster Logger Service was unable to reset the password for
Cluster Health Monitor.
Cause: A password reset failure occurred when the Cluster Logger Service tried to
reset the Cluster Health Monitor password after finding that the password had
expired.
Management Repository has been created successfully. If not, run the 'mgmtca
setpasswd -user CHM' command to reset the password for Cluster Health Monitor. If
the problem persists, run 'diagcollection.pl' and contact Oracle Support Services.
CRS-09527: The Cluster Logger Service was unable to reset the password for
Cluster Health Analysis.
Cause: A password reset failure occurred when the Cluster Logger Service tried to
reset the Cluster Health Analysis password after finding that the password had
expired.
Management Repository has been created successfully. If not, run the 'mgmtca
setpasswd -user CHA' command to reset the password for Cluster Health Analysis. If
the problem persists, run 'diagcollection.pl' and contact Oracle Support Services.
CRS-09600: Failed to initialize string daemon
Cause: An error occurred during initialization.
CRS-09603: Failed to read configuration files
Cause: An error encountered while retrieving information from configuration files.
CRS-09607: Cannot spawn thread for string
Cause: An error encountered while spawning thread.
CRS-09608: ASM disk method failed
Cause: An error encountered with ASM disks configuration.
CRS-00001 to CRS-29006 20-151
CRS-09609: Encountered cssd failure. Reinitializing CSSD layer.

Cause: An error was encountered with CSSD layer while retrieving information.
CRS-09610: Encountered a fatal internal error. Daemon string exiting.
Cause: A fatal error occurred with CSSD layer.
CRS-09611: Mark string disks encountered errors
Cause: An error occurred while accessing disk.
CRS-09612: Mark string disks failed
Cause: A fatal error occurred while accessing disk.
CRS-09615: Disk method Failure : string
CRS-09616: Daemon started : string
Cause: A daemon process started successfully.
Action: None
CRS-09617: Invalid message type encountered
Cause: An invalid or corrupted message was received.
CRS-09618: Daemon stopped : string
Cause: A daemon process stopped successfully.
Action: None
CRS-10002: failed to allocate memory\n
Action: Correct the system memory problem and retry.
CRS-10004: unable to reach string address from local node
Cause: An attempt to reach the IP address specified failed.
Action: Make sure that the specified IP address is a valid IP address and is assigned to
an interface. Make sure that there are no firewalls between local node and node on
which specified IP address is hosted.
CRS-10005: unable to determine local hostname
Cause: The hostname could not be determined.
Action: Check that the hostname for the local machine is valid. Look at the
accompanying messages. If the problem persists, contact Oracle Support Services.
CRS-10006: APPVIP type needs a VIP name. Specify a VIP name using -vip
commandline option.
Cause: VIP resource name was missing in the command line for APPVIP type.
Action: Specify a VIP name using -vip option.

CRS-10008: unable to generate client ID for VIP type string, cluster name string,
VIP resource name string
Cause: An attempt to generate client ID for specified cluster name, VIP type and
resource name failed.
Action: Make sure that cluster name and VIP resource name do not exceed 252
characters. Make sure that VIP type is a valid VIP type. Refer to 'crsctl get clientid help' for more information.
CRS-10010: unable to discover DHCP server in the network listening on port
number for client ID string
Cause: An attempt to discover DHCP server listening on port specified failed.
Action: Make sure that DHCP servers exist on the network and are listening on port
specified. If they are listening on a different port then specify that port using the -port
option. For more information refer to help for 'crsctl discover dhcp' command.
CRS-10011: unable to request DHCP lease for client ID string on port number
Cause: An attempt to request DHCP lease for the specified client ID on specified port
failed.
Action: Make sure that there are DHCP servers with IP addresses available on the
network. If other DHCP servers are available which are listening on a different port
specify an alternative port using the -port option. For more information refer to help
for 'crsctl request dhcp' command.
CRS-10013: unable to release DHCP lease for client ID string, on port number
Cause: An attempt to release DHCP lease for the specified client ID on specified port
failed.
Action: Make sure that there are DHCP servers listening on port specified. If the
DHCP server is listening on a different port specify an alternative port using -port
option. For more information refer to help for 'crsctl release dhcp' command.
CRS-10014: HOSTVIP type needs a node name. Specify a node name using -n
option.
Cause: Node name was missing in the command line for HOSTVIP type.
Action: For HOSTVIP type node name needs to be specified via -n option.
CRS-10015: VIP type string is invalid
Cause: An invalid VIP type was specified for DHCP client ID generation.
Action: Make sure that VIP type is a valid VIP type. Refer to 'crsctl get clientid -help'
for more information.
CRS-10016: error obtaining local host DNS resolver configuration
Cause: An attempt to obtain local host DNS configuration failed.
Action: Make sure that the user executing the command has sufficient permission to
read local system configuration.
CRS-10017: the number name servers configured on this system exceeds the number
maximum allowed
Cause: An attempt to obtain local host DNS configuration failed because more name
servers were found then allowed on this operating system.
Action: Reduce the number of name servers configured to the maximum allowed.
CRS-00001 to CRS-29006 20-153
CRS-10023: Domain name look up for name string failed. Operating system error:
string
Cause: An attempt to query DNS servers for name specified failed.
Action: Look at accompanying messages for more information on the failure.
CRS-10029: could not verify if port number at address string is in use
Cause: An attempt to verify if port at address specified is in use failed.
Action: Make sure that the user has permission to create socket at port specified. For
ports < 1024 user should be root. Also look at the accompanying messages for more
information.
CRS-10030: could not verify if port number on local node is in use
Cause: An attempt to verify if port specified on local node is in use failed.
Action: Make sure that the user has permission to create socket at port specified. For
ports < 1024 the user should be root. Also look at the accompanying messages for
more information.
CRS-10033: could not stop the DNS listening daemon running on port number at
address string
Cause: An attempt to stop the DNS listening daemon running on port and address
specified failed.
Action: Make sure that the user has permission to send packets at the port specified.
For ports < 1024 the user should be root. Also look at the accompanying messages for
more information.
CRS-10034: could not stop the DNS listening daemon running on port number on
local node
Cause: An attempt to stop the DNS listening daemon on local node running on port
specified failed.
Action: Make sure that the user has permission to send packets at the port specified.
For ports < 1024 the user should be root. Also look at the accompanying messages for
more information.
CRS-10035: invalid name server 'string' specified in command line
Cause: An invalid IPv4 address was specified on the command line for -dnsserver
option.
Action: Specify a valid IPv4 address on the command line.
CRS-10036: value for command line parameter 'string' is not an integer
Cause: An invalid value was specified for the specified command line parameter.
Action: Re-submit the request with an integer value.
CRS-10038: invalid IP address 'string' specified
Cause: An invalid IPv4 or IPv6 address was supplied on command line.
Action: Supply an IP address that conforms to IETF RFC-791 or IETF RFC-2373.
CRS-10039: invalid subnet 'string' specified
Cause: An invalid IPv4 or IPv6 subnet was supplied to crsctl.
Action: Supply a subnet address that conforms to IETF RFC-950 or IETF RFC-5942.
CRS-10040: unable to get list of network interfaces

Cause: An attempt to get the list of network interfaces failed.
Action: Look at the accompanying messages for more information.
CRS-10041: subnet 'string' is not configured on the node
Cause: The subnet specified did not match subnet of any network interface on this
node.
Action: Specify a subnet that matches at least one network interface's subnet on this
node.
CRS-10043: DNS daemon is not listening on port number at address string
Cause: An attempt to check if the DNS daemon is listening on port and address
specified failed.
Action: Make sure that the address specified is reachable. Make sure that there is no
firewall between the node on which this command was run and the address specified.
Also look at the accompanying messages for more information.
CRS-10044: invalid cluster name 'string' specified
Cause: An invalid cluster name was supplied to the CRSCTL utility.
Action: Specify a cluster name which is at least one character but no more than 15
characters in length. The cluster name must be alphanumeric, it cannot begin with a
numeric character, and it may contain hyphen (-) characters. However, it cannot end
with a hyphen (-) character.
CRS-10045: invalid node name 'string' specified
Cause: An invalid node name was supplied to the CRSCTL utility.
Action: Specify a node name which is at least one character but no more than 63
characters in length. The node name must be alphanumeric, it cannot begin with a
CRS-10046: invalid client ID 'string' specified
Cause: An invalid client ID was supplied to the CRSCTL utility.
Action: The client ID can be obtained by running the command 'crsctl get clientid
dhcp'.
CRS-10051: CVU found following errors with Clusterware setup : string
Cause: A resource-specific error was detected by the Clusterware Verification Utility
(CVU). This message is accompanied by others providing details of the error
condition.
Action: Respond based on the accompanying messages.
CRS-10100: Execution of crswrapexece.pl script with arguments 'string' fails.
Cause: crswrapexece.pl script failed when executed with the specific arguments.
Action: Check system log and crswrapexece.log for more details. Contact Oracle
Support Services.
CRS-10101: Internal Error
Cause: Execution of crswrapexece.pl script failed due to missing argument.
CRS-00001 to CRS-29006 20-155
CRS-10102: Failure to open environment file string.

Cause: The crswrapexece.pl script failed to open the environment file, which might be
caused by hostname change or user edits.
Action: Check for the existence and permission of the environment file.
CRS-10103: Found string syntax errors in environment file string.
Cause: crswrapexece.pl found syntax errors in the provided environment file.
Action: Check and fix syntax error in the indicated environment file. If the problem
CRS-10131: Failure to create named pipe string. Details [string].
Cause: The specified named pipe could not be created. Oracle High Availability
Service would not be able to restart if crashes.
Action: Check for the existence and permission of the parent directory, where the
named pipe was created.
CRS-10132: Oracle High Availability Service was restarted at least string times
within the last string seconds. Stop auto-restarting Oracle High Availability
Service.
Cause: Oracle High Availability Service was restarted too rapidly within a short
period of time.
Action: Check the Oracle High Availability Service log file to determine the cause. If
CRS-10201: Internal error
Cause: An unexpected condition was detected in the cluster event module.
CRS-10202: Failed to allocate process memory
Cause: Insufficient system memory resources.
Action: Correct the system memory resources problem and retry. If this does not
appear to be caused by an operating system issue, contact Oracle Support Services.
CRS-10203: Could not connect to the Event Manager daemon
CRS-10250: Database name is required to access database wallets. Use -name option
to supply a database name.
Cause: The option -name was missing on the command line.
Action: For APPQOSDB wallet types -name is a mandatory parameter. Retry the
command with -name option.
CRS-10251: User name is required to create OSUSER wallets. Use -user option to
supply a username.
Cause: The option -user was missing on the command line.
Action: For OSUSER wallet types -user is a mandatory parameter. Retry the
command with -user option.
CRS-10301: Unable to contact Oracle high availability service on peer nodes for
cluster wide commands. Details at string in string.
Cause: Multicast Domain Name Server (mDNS) or Grid Plug and Play (GPnP) or both
daemons on the local node were not running.
Action: If you are shutting down the Clusterware stack, this is expected. If you had
issued a cluster wide command, reissue the command after the stack has been
restarted. If you are not shutting down the stack, the missing component(s) may have
failed and may restart automatically. Any cluster wide commands can be retried after
a few seconds. However, the failure should be investigated and reported to Oracle
Support Services.
CRS-10302: Oracle high availability service on peer nodes is reachable. Details at
string in string.
Cause: Oracle high availability service on peer nodes was reachable.
Action: None
CRS-10401: Internal error in credentials processing.
Cause: An unexpected condition was detected in the credentials module.
CRS-10402: Failed to allocate process memory.
Cause: There were insufficient system memory resources.
Action: Correct the system memory resources problem and retry. If this does not
appear to be caused by an operating system issue, contact Oracle Support Services.
CRS-10403: Could not connect to credential storage: string.
Cause: An attempt to communicate with Oracle Cluster Registry (OCR) or Oracle
Local Registry (OLR) credential storage failed.
Action: Run the 'crsctl check crs' command to determine whether Cluster Ready
Services or Oracle High Availability Services are online.
CRS-10405: Credential domain already exists.
Cause: The provided credential domain already existed.
Action: Specify another credential domain path.
CRS-10406: Authorization error.
Cause: The user did not have permissions to view or modify the provided credential
information.
Action: Use a different user to view or modify the credential information.
CRS-10407: Credential domain does not exist.
Cause: The provided credential domain did not exist.
Action: Specify another credential domain path or create the credential domain.
CRS-10408: Credential set already exists.
Cause: The provided credential set already existed.
Action: Specify another credential domain path to which the credential set will be
added.
CRS-10409: Credential target already exists.
Cause: The provided credential target already existed.
CRS-00001 to CRS-29006 20-157
Action: Specify another credential target name, or modify the value of the existing
one.
CRS-10410: Credential set member does not exist.
Cause: The provided credential set member did not exist.
Action: Specify another credential set member or create a new member.
CRS-10411: Credential set does not exist.
Cause: The provided credential set did not exist.
Action: Specify another credential set or create a new member.
CRS-10412: Security layer returned failure: string.
Cause: Credential operation failed due to error from security layer.
Action: Depending on the reason, this operation may be retried after correcting the
situation.
CRS-10413: Invalid argument specified for attribute.
Cause: An invalid argument was found for a given attribute.
Action: Rerun the command using correct value.
CRS-10414: User name or group name does not match the owner or group of the
credential object.
Cause: Credential permissions for the owner could not be modified because the user
name did not match the owner of the credential.
Action: Specify the owner's user ID in the argument to change owner's permission.
CRS-10415: ACL string is missing the user or group modifier.
Cause: The access control list (ACL) string did not specify whether user's or group's
permission needs to be changed.
Action: Specify the correct format in the argument and rerun the command.
CRS-10416: Credentials target does not exist.
Cause: The provided credentials target did not exist.
Action: Specify another credentials target.
CRS-10417: The directory 'string' does not exist.
Cause: The specified directory did not exist.
Action: Provide a directory for which the user has read and write permissions.
CRS-10418: The directory 'string' is not accessible.
Cause: An attempt to access the specified directory failed.
Action: Ensure that the user has read and write permissions on the directory.
CRS-10419: Unable to open file 'string' for read access.
Cause: An attempt to open the specified file for read access failed.
Action: Ensure that the user has read access permission on the file.
CRS-10420: Unable to open file 'string' for write access.
Cause: An attempt to open the specified file for write access failed.
Action: Ensure that the user has write access permission on the file.
CRS-10421: Section name does not exist.

Cause: The credentials could not be imported because the provided section name did
not exist in the XML file.
Action: Verify the sections included in the credentials file and retry the import
supplying the correct section name.
CRS-29000: Oracle VM Manager job failed with the following error:\nstring
Cause: The Oracle Virtual Machine (Oracle VM) Manager was unable to complete the
action due to the indicated error.
Action: Consult Oracle Virtual Machine (Oracle VM) documentation if the problem
persists.
CRS-29001: could not find Grid Infrastructure virtual machine 'string'
Cause: The name specified for the Grid Infrastructure virtual machine was not found.
Action: Specify a known virtual machine, or create a new virtual machine with the
specified name and add it to the Oracle Clusterware cluster.
CRS-29002: could not find a virtual machine with the ID 'string'
Cause: The ID specified for the virtual machine was not found.
specified ID.
CRS-29003: could not find a virtual machine with the name or ID 'string'
Cause: Either the name or the ID provided for the virtual machine was not found.
specified name or ID.
CRS-29004: not authorized to perform the Oracle VM Manager operation
Cause: The Oracle Virtual Machine (Oracle VM) user name and password
combination did not work, or the user did not have permission to perform the action
requested.
Action: Update the user's password using the 'srvctl modify ovmm' command, or
specify a different user who has the correct permissions.
CRS-29005: could not connect to the Oracle VM Manager on host string at port
string
Cause: A connection to the Oracle Virtual Machine (Oracle VM) Manager could not be
established or timed out.
Action: Start the Oracle VM Manager on the appropriate host and port, or specify a
different host or port using the 'srvctl modify ovmm' command.
CRS-29006: could not find Oracle VM Manager credentials
Cause: Authentication credentials were not found for the Oracle Virtual Machine
(Oracle VM) Manager.
Action: Create or modify the credentials by using the 'srvctl {add | modify} ovmm'
command.
CRS-00001 to CRS-29006 20-159
21
DBV-00200 to DBV-00201
DBV-00200: Block, DBA number, already marked corrupt
Cause: The block was previously corrupted. It has been marked as corrupt by the
Oracle database server.
Action: If the block is not currently allocated to a database object, then no action is
required. If the block is allocated, then the options and required action depend on the
type and nature of the object which owns the block. To repair an allocated block,
perform block or file media recovery.
DBV-00201: Block, DBA number, marked corrupt for invalid redo application
Cause: The block was marked corrupt by the Oracle database server for invalid redo
application, ex: media recovery of a NOLOGGING object or direct loaded data.
Action: If the block is not currently allocated to a database object, then no action is
required. If the block is allocated, then the object will need to be rebuilt, or data to be
reloaded.
DBV-00200 to DBV-00201 21-1
21-2 Error Messages
22
DGM-16900 to DGM-17032
DGM-16900: Unable to initialize client
Cause: The client could not be initialized.
DGM-16901: Unable to initialize environment
Cause: The database environment could not be allocated and initialized.
DGM-16902: Unable to allocate handle
Cause: The database handle could not be allocated.
DGM-16903: Unable to connect to database using string
Cause: The Data Guard command-line interface (DGMGRL) was unable to connect to
the database using the specified connect identifier.
Action: Check the connect identifier and ensure the instance or host is reachable.
DGM-16904: Unable to set attribute
Cause: The server attributes could not be set.
Action: Check additional error messages.
DGM-16905: Failed.
Cause: The command failed to execute.
DGM-16906: Unable to accept commands: no memory
Cause: No memory was available for the attempted operation.
Action: Check your system and retry the command.
DGM-16909: Fatal error - quitting...
Cause: A fatal error was encountered.
Action: See additional error messages and/or contact Oracle Support Services.
DGM-16910: Unable to issue command to server
Cause: Command could not be issued to the server.
Action: See additional error messages and/or contact Oracle Support Services.
DGM-16912: Unrecognized command "string", try "help"
Cause: An unrecognized command was issued.
Action: Try again using a valid command.
DGM-16900 to DGM-17032 22-1
DGM-16916: Missing site name, try "help"

Cause: The site name is missing from the command.
Action: Try the command again using correct syntax.
DGM-16934: \tstart up instance "string" of database "string"
Cause: The operation completed successfully and requires a restart of the specified
instance. DGMGRL was unable to restart the instance.
Action: Start the specified instance manually.
DGM-16943: \tconnect to instance "string" of database "string"
Cause: The operation required DGMGRL to connect to a specific instance to complete,
but DGMGRL could not automatically connect to the given instance.
Action: Connect to the specified instance and issue the command again.
DGM-16944: Failover succeeded, new primary is "string"
Cause: The failover command completed successfully."
DGM-16945: Syntax error before or at "string"
Cause: The command could not be processed because of a syntax error in the named
token.
Action: Try the command again using valid syntax.
DGM-16948: Unable to switchover, primary database is still "string"
Cause: The switchover operation could not be executed due to the errors reported
with this error message. The primary role has not been changed.
Action: Correct the errors and try the SWITCHOVER command again.
DGM-16949: Object "string" was not found
Cause: The named object was not found.
Action: Try the command again using a valid database name.
DGM-16951: Unable to failover
Cause: The failover operation could not be executed due to the errors reported with
this error message.
Action: Correct the errors and try the FAILOVER command again.
DGM-16952: Configuration details cannot be determined by DGMGRL
Cause: The broker configuration could not be found.
Action: 1) The Data Guard broker process (DMON) could not be contacted. Verify
that the DMON process is running. 2) No broker configuration currently exists. You
must create one. 3) You are connected to a standby database in the broker
configuration that has either been disabled or deleted. While the standby is in this
state, the details of the broker configuration are not available on the standby database.
Connect to the primary database and reissue the command. 4) You are connected to a
database in the broker configuration that must be reinstated or reinstantiated. While
in this state, details of the broker configuration are not available. Either reinstate or
reinstantiate the database and reissue the command, or connect to the primary
database and reissue the command.
22-2 Error Messages
DGM-16953: XML document is too long

Cause: The length of the XML document exceeded the internal limit.
DGM-16954: Unable to open and lock the Observer configuration file
Cause: The Observer configuration file cannot be opened or cannot be locked for
exclusive access.
Action: Make sure the Observer has the correct operating system privileges to write
the file and there is no other Observer that is using the same file. Try the command
again.
DGM-16959: No response from broker server process
Cause: No response was received from the broker server process (DMON).
Action: The Data Guard broker process (DMON) is not available. Verify that the
DMON process is running and retry the command.
DGM-16960: Status not available
Cause: The status could not be retrieved.
Action: The Data Guard broker process (DMON) is not available. Verify that the
DMON process is running and retry the command.
DGM-16979: Unable to log on to the primary or standby database as SYSDBA
Cause: The username/password used by the observer to log on to the primary
database and Fast-Start Failover target standby database does not have valid SYSDBA
credentials.
Action: Make sure the primary database and Fast-start failover target database are
using a remote login password file. Make sure the SYSDBA password is the same at
both databases and that the SYSDBA password is used in the CONNECT command.
Start the observer again.
DGM-16991: Two or more resources have the name "string"
Cause: The named resource exists on more than one site.
Action: Use the ON SITE clause and reissue the command.
DGM-16999: Instance "string" was not found
Cause: The named instance could not be found.
Action: Try the command again using a valid instance name.
DGM-17000: Two or more instances have the name "string"
Cause: The named instance exists on more than one database.
Action: Use the ON DATABASE clause and reissue the command.
DGM-17002: Primary database cannot be removed
Cause: The named database to be removed is the primary database.
Action: Remove the broker configuration instead.
DGM-17007: Unsupported platform, observer cannot start
Cause: The Observer was started on an operating system that does not support multithreading.
Action: Start the Observer on an operating system that supports multi-threading.
DGM-16900 to DGM-17032 22-3
DGM-17009: New primary database "string" is opening...

Cause: The Data Guard broker is opening the specified new primary database. The
new primary database is ready to accept transactions once it is open.
Action: None
DGM-17016: failed to retrieve status for database "string"
Cause: DGMGRL could not retrieve the StatusReport property from the given
database and thus could not report the database status.
Action: See accompanying messages for details.
DGM-17017: unable to determine configuration status
Cause: The Data Guard broker could not execute a health check at the moment, so the
configuration status could not be determined.
DGM-17023: far sync instance "string" was not found
Cause: A far sync instance with the given name was not found in the configuration.
Action: Try the command again using a valid far sync instance name. If the name
refers to a database, use the corresponding database command syntax instead.
DGM-17025: database "string" was not found
Cause: A database with the given name was not found in the configuration.
Action: Try the command again using a valid database name. If the name refers to a
far sync instance, use the corresponding far sync instance command syntax instead.
DGM-17032: Wildcard string not supported for this command
Cause: The wildcard string was specified instead of an object name.
Action: Supply an object name instead of the wildcard string and retry the command.
22-4 Error Messages
23
DIA-48001 to DIA-51705
DIA-48001: internal error code, arguments: [string], [string], [string], [string],
[string], [string], [string], [string]
Cause: This is the generic internal error number for program exceptions. This
indicated that a process encountered an exceptional condition.
Action: Report as a bug - the first argument is the internal error number.
DIA-48002: thread terminated by fatal error
Cause: The thread was in an unrecoverable state.
Action: Examine the thread trace file for more information.
DIA-48003: out of process memory when trying to allocate string bytes
(string,string)
Cause: Operating system process private memory was exhausted.
Action: n/a
DIA-48004: unable to allocate string bytes of shared memory
("string","string","string","string")
Cause: More shared memory is needed than was allocated in the shared pool.
Action: Reduce your use of shared memory or increase the amount of available
shared memory.
DIA-48007: name is already used by an existing product type
Cause: An attempt was made to define a product type with the same name as an
already defined product type.
Action: Use the already existing product type with the specified name, or use a
different name for the product type.
DIA-48008: id is already used by an existing product type
Cause: An attempt was made to define a product type with the same id as an already
defined product type.
Action: Choose a different name for the product type.
DIA-48100: error encountered when attempting to open a file
Cause: There was an error encountered when attempting to open a file with the ADR
file interface.
Action: Check that the specified directory name, file name, and open options are
valid.
DIA-48101: error encountered when attempting to read a file [string] [string] [string]
Cause: There was an error encountered when attempting to read a file with the ADR
file interface.
DIA-48001 to DIA-51705 23-1
Action: Check the specified arguments to the read interface.

DIA-48102: encountered the end-of-file when reading the file
Cause: The ADR file interface encountered the end-of-file when reading the file.
Action: Handle the end of file condition.
DIA-48103: error encountered when attempting to write a file [string] [string]
[string]
Cause: There was an error encountered when attempting to write a file with the ADR
file interface.
Action: Check the specified arguments to the write interface.
DIA-48104: read mismatch on blocks requested and returned, [string], [string]
Cause: There was a mismatch between the number of blocks requested for reading
and the number of blocks actually returned.
Action: Check the file to make sure there are no partial blocks.
DIA-48105: write mismatch on blocks requested and returned, [string], [string]
Cause: There was a mismatch between the number of blocks requested for writing
and the number of blocks actually written.
Action: Check that there is enough space left on the device to write the requested
number of blocks.
DIA-48106: error initializing the ADR string object
Cause: There was an error encountered during the initialization of one of the ADR file
objects.
Action: Check the validity of the specified directory name and file name.
DIA-48107: invalid Bfile input, [string]
Cause: An invalid Bfile was passed into the routine to convert the bfile into a file
handle.
Action: Verify the contents of the specified Bfile.
DIA-48108: invalid value given for the diagnostic_dest init.ora parameter
Cause: The value given for the diagnostic_dest directory is not a valid directory.
Either the directory does not exist or the process does not have read/write privileges
on the directory.
Action: Use a value for diagnostic_dest that is a valid directory with the proper read
and write privileges.
DIA-48109: invalid lock mode for file descriptor, [string]
Cause: The lock mode associated with the file descriptor was invalid in the context of
the routine.
Action: Verify that a file is not trying to obtain multiple locks and that the file is
holding a lock when attempting to release the lock.
DIA-48110: error encountered while attempting to get a file lock [string] [string]
Cause: There was an error encountered while trying to get a file lock.
Action: Check the state of the file and operating system.
DIA-48111: error encountered while attempting to release a file lock [string]
Cause: There was an error encountered while trying to release a file lock.
23-2 Error Messages
Action: Check the state of the file and operating system.

DIA-48112: invalid flags for open file, string
Cause: Invalid flags were passed in to the open file routine.
Action: Check to see if the flags are a valid combination.
DIA-48113: unable to write to stream file because of out of space condition
Cause: The system is unable to write the requested number of bytes to a stream file.
This is due to an out of space condition. The additional information shows how many
bytes were not written.
Action: Check that there is enough space left on the device to write the requested
number of bytes.
DIA-48114: error encountered when attempting to close a file
Cause: There was an error encountered when attempting to close a file with the ADR
file interface.
Action: Check the validity of the file descriptor.
DIA-48115: error encountered while seeking a file position
Cause: There was an error encountered while seeking a position in a file.
Action: Check that the requested file position falls within the file boundaries.
DIA-48116: error enountered when attempting to create a directory [string]
Cause: There was an error encountered when attempting to create a directory.
Action: Check the directory name.
DIA-48117: error encountered when attempting to remove a directory [string]
Cause: There was an error encountered when attempting to remove a directory.
DIA-48118: error encountered with list directory [string]
Cause: There was an error with listing the elements of a directory.
Action: Check the state of the operating system.
DIA-48119: error encountered when attempting to remove a file [string] [string]
Cause: There was an error encountered when attempting to remove a file with the
ADR file interface.
Action: Check the directory name and file name.
DIA-48120: error encountered when attempting to retrieve the file size [string]
[string]
Cause: There was an error encountered when attempting to retrieve the file size with
the ADR file interface.
DIA-48121: error with opening the ADR stream file [string] [string]
Cause: An error was encountered when attempting to open an ADR stream file.
Action: Check the rest of the error stack for details of the actual error that was
encountered.
DIA-48001 to DIA-51705 23-3
DIA-48122: error with opening the ADR block file [string] [string]
Cause: An error was encountered when attempting to open an ADR block file.
Action: Check the rest of the error stack for details of the actual error that was
encountered.
DIA-48123: error encountered when attempting to flush a file
Cause: There was an error encountered when attempting to flush a file with the ADR
file interface.
Action: Check the state of the file.
DIA-48124: device full encountered during write to a file
Cause: The device full error was encountered during the write to a file.
Action: Check the amount of free space on the device.
DIA-48125: illegal identifier length, argn:string, len:string, lim:string
Cause: An input identifier was passed in that has a length that is greater than the max
length.
Action: Make sure the input indentifier has a length that is less than the max length.
DIA-48126: attempting to create a file that already exists
Cause: The client attempted to create a file that already exists.
Action: Either remove the file or check if it is okay if the file already exists.
DIA-48127: attempting to open a file that does not exist
Cause: An attempt was made to open a file that does not exist.
Action: Either create the file or check why the file does not exist.
DIA-48128: opening of a symbolic link is disallowed
Cause: An error was encountered when attempting to open a file that is a symbolic
link. Users are not allowed to open symbolic links.
Action: Check the specified file name.
DIA-48129: invalid input for the full path specification
Cause: Input was incorrectly specified for the full path specification, or the default
extension may have been incorrectly specified. Or an empty string was passed in for
the full path.
Action: Check that the full path string is non-NULL. If you want to specify a relative
path from ADR Home for the full path specification, then use '<ADR_HOME>'
instead of the actual path to ADR Home. For ADR Base, use '<ADR_BASE>'.
DIA-48130: invalid lock parameters for get file lock [string]
Cause: Invalid lock parameters passed in for the get file lock routine. The user must
pass in file as the lock type. Or, there is a lock mode mismatch. Exclusive locks are not
allowed in read-only mode, and shared locks are not allowed in write-only mode.
Action: Check that correct lock type is specified and that the correct lock mode is
requested for the file given its open flags.
DIA-48131: error encountered when attempting to tell the file position
Cause: An error was encountered when attempting to tell the file position using the
ADR file interface.
Action: Check the directory and file name of the file along with the open state.
23-4 Error Messages
DIA-48132: requested file lock is busy, [string] [string]

Cause: The requested file lock is busy because another process is holding the file lock.
Action: Try to get the file lock again at a later time.
DIA-48133: file descriptor has already been opened [string] [string]
Cause: The specified file descriptor has already been opened.
Action: Do not open a file that has previously been opened, or check your code to
make sure you are cleaning up a file descriptor that is being reused correctly.
DIA-48134: invalid file descriptor state for operation, string, string, string
Cause: The state of the file descriptor was invalid for the requested operation. An
example is that a file was opened for read, but a write operation to the file was
requested.
Action: Check the state of the file descriptor and make sure it matches the operation.
DIA-48135: uninitialized file descriptor
Cause: The specified file descriptor is uninitialized.
Action: Make sure the file descriptor is initialized before passing it into the routine.
DIA-48136: directory already exists [string]
Cause: Operation failed because the specified directory already exists.
Action: Remove the directory or ignore this error.
DIA-48137: uninitialized file handle
Cause: The specified file handle is uninitialized.
Action: Make sure the file handle is initialized before passing it into the routine.
DIA-48138: invalid directory name input for client address
Cause: An invalid directory name was specified as part of the address path
specification.
Action: Check that the directory name is non-NULL and that the directory name
length does not exceed the maximum length.
DIA-48139: invalid input to ADR initialization routine
Cause: There was an invalid input to the ADR initialization routine.
Action: Check the length of the ADR base, product ID, and instance ID input
arguments.
DIA-48140: the specified ADR Base directory does not exist [string]
Cause: The specified ADR Base Directory does not exist.
Action: Check that the specified ADR Base Directory is a valid path name and that the
directory exists.
DIA-48141: error creating directory during ADR initialization [string]
Cause: Error encountered when creating a directory during the initialization of the
ADR subsystem.
Action: Check the input arguments to the ADR initialization routine and the state of
the operating system.
DIA-48142: invalid permissions input for change permissions
Cause: Invalid permissions passed into change permissions routine.
DIA-48001 to DIA-51705 23-5
Action: Check the value of the permissions input.

DIA-48143: error changing permissions for a file
Cause: Error encountered while changing the permissions for a file
Action: Check the specified directory and file and the state of the operating system.
DIA-48144: error encounted while performing standard file I/O
Cause: Error encountered while performing standard file I/O
Action: Check the validity of standard in, out, and error.
DIA-48145: invalid seek location, [string], [string]
Cause: Invalid seek location specified for routine.
Action: Check the validity of specified seek location.
DIA-48146: missing read, write, or exec permission on directory during ADR
initialization [string] [string]
Cause: Error encountered when checking if the process has read, write, and exec
privileges on directories needed by the ADR subsystem. This error occurs during the
initialization of the ADR subsystem.
Action: Check the input arguments to the ADR initialization routine and the state of
the operating system. Ensure that the user has the proper permissions on the ADR
directories.
DIA-48147: invalid home location specification for ADR, [string], [string], [string]
Cause: Invalid read or write home location specification for ADR.
Action: An invalid home was specified for the ADR Read or Write Home location.
DIA-48148: error encountered when attempting to move a file
Cause: There was an error encountered when attempting to move a file with the ADR
file interface.
DIA-48149: error encountered when attempting to copy a file
Cause: There was an error encountered when attempting to copy a file with the ADR
file interface.
DIA-48150: error encountered with set current working directory
Cause: There was an error with setting the current working directory.
Action: Check the path used, or the state of the operating system.
DIA-48151: error getting operating system time for a file
Cause: Error encountered while getting the operating system time for a file.
Action: Check the specified directory and file and the state of the operating system.
DIA-48152: lock table is full
Cause: Lock table is full - too many locks granted
Action: Try again later
23-6 Error Messages
DIA-48153: error encountered when getting ADR base directory default

Cause: There was an error encountered when attempting to get the ADR base
directory default value.
Action: Check your environment to see if the $ORACLE_BASE and
$ORACLE_HOME environment variables are set.
DIA-48154: reached end of file for alert log
Cause: The end of file was reached for reading the Alert Log. There are no more
messages to read in the Alert Log.
Action: Do not read from the Alert Log
DIA-48155: error encountered when read alert log [string]
Cause: There was an error encountered when attempting to read a message from the
Alert Log.
Action: Check the error message and the contents of the alert message.
DIA-48156: Alert log purge has occurred - retry operation
Cause: The purge of the alert log has occurred.
DIA-48157: null input to ADR initialization
Cause: There was an null input to the ADR initialization routine.
Action: Check the ADR base, product ID, and instance ID input arguments.
DIA-48158: invalid input for ADR base directory
Cause: An invalid input was passed in for the ADR base directory name. The ADR
base directory name is either NULL or too long of a string.
Action: Check the ADR base directory input argument.
DIA-48159: invalid input for ADR product type
Cause: An invalid input was passed in for the ADR product type. The ADR product
type is out of bounds.
Action: Check the ADR product type input argument.
DIA-48160: invalid input for ADR product id
Cause: An invalid input was passed in for the ADR product id. The ADR product id
is either NULL or too long of a string.
Action: Check the ADR product id input argument.
DIA-48161: invalid input for ADR instance id
Cause: An invalid input was passed in for the ADR instance id. The ADR instance id
is either NULL or too long of a string.
Action: Check the ADR instance id input argument.
DIA-48162: string buffer too small to hold input, [string], [string], [string]
Cause: The string buffer is too small to copy an input string into.
Action: Check the size of the string buffer and the input string. Look in the argument
for the location in the code where the error occurs.
DIA-48163: error concatenating directory onto path, [string], [string], [string]
Cause: Error encountered while concatenating a directory onto a path name.
DIA-48001 to DIA-51705 23-7
Action: Check the error returned by the OS and the size of the input and output
buffers.
DIA-48164: error concatenating file onto path, [string], [string], [string]
Cause: Error encountered while concatenating a directory onto a path name.
Action: Check the error returned by the OS and the size of the input and output
buffers.
DIA-48165: user missing read, write, or exec permission on specified ADR Base
directory [string]
Cause: The specified ADR Base Directory does not have the correct permissions.
Action: Check the read, write, and exec permissions on the specified ADR Base
Directory
DIA-48166: error with opening ADR block file because file does not exist [string]
[string]
Cause: An error was encountered with opening an ADR block file because the file
does not exist.
Action: Check the existence of the ADR Block File.
DIA-48167: invalid argument for checking ADR initialization
Cause: Invalid arguments were specified for the routine to check ADR initialization.
Action: Check the inputs to the ADR initialization routine.
DIA-48168: the ADR sub-system is not initialized
Cause: The ADR subsystem has not been initialized. The requested operation cannot
be performed.
Action: Check the usage of the call to the ADR services. The ADR sub-system must be
initialized for the call to work.
DIA-48169: incorrect arguments to ADR deferred initialization
Cause: There are incorrect arguments to the ADR deferred initialization.
Action: Check the input arguments. It could be possible that the product is not set up
for deferred initialization.
DIA-48170: unable to lock file - already in use
Cause: the file is locked by another process, indicating that it is currently in use by
another process
Action: determine which process legitimately owns this file.
DIA-48171: unable to get share lock - file not readable
Cause: share lock request was made on a file not open for read access.
Action: file must be open read-only or read-write to get a share lock.
DIA-48172: unable to find a valid ADR base
Cause: Unable to find a valid ADR base. We tried the ORACLE_BASE,
ORACLE_HOME, home, and tmp directories, but none of the directories exist for
read/write access.
Action: Check the validity of the ORACLE_BASE, ORACLE_HOME, home, and tmp
directories.
23-8 Error Messages
DIA-48173: error checking directory existence during ADR initialization [string]

Cause: Error encountered when checking directory existence during the initialization
of the ADR subsystem. Either the diag or product type directory does not exist
underneath the ADR base.
Action: The directory in the error message must exist in order for ADR initialization
to succeed. Make sure the directories exist.
DIA-48174: error encountered with get current working directory
Cause: There was an error with getting the current working directory.
Action: Check the state of the operating system or the size of the path buffer.
DIA-48175: the path name must not contain the string '..'.
Cause: The specified path name contains '..'.
Action: Correct the path name and retry the operation.
DIA-48176: error translating a path name into its full path name
Cause: An error was encountered when translating a path name into its full path
name.
Action: Check the inputted path name to make sure it is a valid relative path.
DIA-48177: file name with full path information [string] not allowed
Cause: Input was incorrectly specified for the file name. The inputted file name is
greater than the maximum length, or the file name has path information. In this case,
the file name should not have any path information. The path information should be
specified in a separate argument.
Action: Check that the string for the file name is not too long and does not have path
information.
DIA-48178: error encountered while reading an ADR block file during ADR
initialization [string]
Cause: An error was encountered while reading an ADR block file during the
initialization of the ADR subsystem.
Action: Check the state of the file system.
DIA-48179: OS file synchronization failure
Cause: OS command to synchronize the changes to a file with the operating system
failed.
Action: Check the state of the file system and the amount of free space left on your
device.
DIA-48180: OS open system call failure
Cause: OS open system call failed. The system failed to open or create a file in the
requested mode.
Action: Check the OS error code
DIA-48181: OS write system call failure
Cause: OS write system call failed. The system failed to write to a file.
DIA-48182: OS read system call failure
Cause: OS read system call failed. The system failed to read to a file.
DIA-48001 to DIA-51705 23-9

DIA-48183: OS close system call failure
Cause: OS close system call failed. The system failed to close a file.
DIA-48184: OS seek system call failure
Cause: OS seek system call failed. The system failed to seek to a position in a file.
DIA-48185: OS file size system call failure
Cause: OS file size call failed. The system failed to retrieve the file size for a file.
DIA-48186: OS check file exists system call failure
Cause: OS check file exists system call failed. The system failed to perform the check
file exists command for a file.
DIA-48187: specified directory does not exist
Cause: The specified directory does not exist.
DIA-48188: user missing read, write, or exec permission on specified directory
Cause: The user does not have valid permissions on the specified directory. The user
is missing either the read, write, or execute permission.
Action: Check the permissions of the specified directory.
DIA-48189: OS command to create directory failed
Cause: The OS command to create a directory failed.
Action: Check the error number associated with the create directory failure.
DIA-48190: OS unlink system call failure
Cause: OS unlink system call failed. The system failed to perform unlink on the
specified file.
DIA-48191: user missing read or write permission on specified file
Cause: The user does not have valid permissions on the specified file. The user is
missing either the read or write permission.
Action: Check the permissions of the specified file.
DIA-48192: OS command to move a file failed
Cause: The OS command to move a file failed.
Action: Check the error number associated with the move file.
DIA-48193: OS command to open a directory failed
Cause: The OS command to open a directory failed.
Action: Check the OS error associated with the open directory failure.
DIA-48194: OS command to close a directory failed

Cause: The OS command to close a directory failed.
Action: Check the OS error associated with the close directory failure.
DIA-48195: OS command to remove a directory failed
Cause: The OS command to remove a directory failed.
Action: Check the OS error associated with the remove directory failure.
DIA-48196: OS command to release advisory lock failed
Cause: The OS command to release the advisory lock failed
Action: Check the OS error associated with the release advisory lock failure.
DIA-48197: OS command to get the file status failed
Cause: The OS command to get the file status failed. This could be because the file is
not open or file descriptor is invalid.
Action: Check the OS error associated with the get file status failure.
DIA-48198: OS command to change the file permissions failed
Cause: The OS command to change the file permissions failed.
Action: Check the OS error associated with the failure.
DIA-48199: OS command to copy a file failed
Cause: The OS command to copy a file failed.
Action: Check the error number associated with the copy file.
DIA-48200: Illegal Input Argument [string]
Cause: An illegal argument was passed in.
Action: Fix the call.
DIA-48201: Field Length Exceeds Maximum [string] [string] [string]
Cause: An illegal field length was used.
Action: Fix the call.
DIA-48202: Illegal Identifier [string] [string]
Cause: Illegal identifier specified.
Action: Use a valid identifier.
DIA-48203: Illegal Data Type [string]
Cause: Illegal data type specified.
Action: Use a valid data type.
DIA-48204: Illegal Identifier Length [string] [string] [string]
Cause: The input identifier is too long.
Action: Specify a shorter identifier.
DIA-48205: Record Length too Big [string] [string] [string]
Cause: The sum of the maximum lengths of all fields exceeds the maximum record
length that is supported.
Action: Remove or shorten some of the fields.
DIA-48001 to DIA-51705 23-11
DIA-48206: Ilegal Number of Fields [string] [string] [string]

Cause: The number of fields specified exceeds the supported maximum.
Action: Remove some of the fields in the relation.
DIA-48207: Illegal Field Name [string]
Cause: The field name is invalid.
Action: Specify a valid field name.
DIA-48208: Duplicate Field Names [string]
Cause: The list of fields specified contains a duplicate field.
Action: Remove the duplicate field.
DIA-48209: Relation Already Exists
Cause: The relation already exists.
Action: Remove the relation.
DIA-48210: Relation Not Found
Cause: The relation was not found.
Action: Either specify a valid relation name or create one with that name.
DIA-48211: Illegal Access Mode [string] [string]
Cause: The supplied access mode is not recognized.
Action: Supply a valid mode.
DIA-48212: Open Record Access Not Done
Cause: The open record access call was not performed.
Action: The open record access call is required before attempting this call.
DIA-48213: Incorrect Access Mode for Operation [string] [string]
Cause: The relation was opened in a mode not compatibile with the attempted
operation being done.
Action: Reopen the relation in the correct mode.
DIA-48214: Sequence Overflow [string] [string] [string]
Cause: The sequence number will exceed the system maximum.
Action: Reset the sequence number.
DIA-48215: Sequence Invalid Operation [string] [string]
Cause: The specified sequence operation is not valid.
Action: Specify a valid operation.
DIA-48216: Field Len Exceeds Max Field Length [string] [string] [string] [string]
Cause: The field length specified exceeds the defined maximum for the field.
Action: Supply a smaller field length.
DIA-48217: Out of Space on Device
Cause: The storage subsystem is out of space.
Action: Add more space to the storage subsystem.
DIA-48218: Duplicate Key Name [string] [string]

Cause: The key name already exists.
Action: Specify a different key name.
DIA-48219: Key Name Doesn't Match Any Existing Key
Cause: The key name provided doesn't match an existing key.
Action: Specify a key name that exists.
DIA-48220: Too Many Keys Defined [string] [string]
Cause: A key is trying to be created that exceeds the maximum number of keys
supported.
Action: Drop another key.
DIA-48221: Key Exceeds Maximum Allowed Length [string] [string] [string]
Cause: The sum of the lengths of the fields in the key exceeds the maximum length
supported.
Action: Remove one or more fields from the key.
DIA-48222: Predicates/Order By Not Allowed
Cause: A predicate or order by can not be added after fetch has started.
Action: Put the predicate or order by call before the first fetch.
DIA-48223: Interrupt Requested - Fetch Aborted - Return Code [string] [string]
Cause: User interrupt has occurred.
Action: None
DIA-48224: DDL has occurred since parse - reparse [string] [string] [string]
Cause: Another session has performed a DDL (i.e. add field, create key, drop key) that
prevents this session from being to continue.
Action: Call open record access again.
DIA-48225: No More Space in Order By Buffer
Cause: The order by buffer size is not sufficient for the number of rows.
Action: Increase the order by buffer size specified.
DIA-48226: No Fetch in Progress
Cause: An attempt to perform update or delete has occurred without a fetch.
Action: You must first perform a fetch.
DIA-48227: Invalid Relation File - [string] [string] [string] [string]
Cause: The AMS file is invalid or corrupt.
Action: Do a repair relation
DIA-48228: Missing Define Call [string]
Cause: A call to define was not performed before doing a fetch.
Action: Call the define service before fetch.
DIA-48229: Invalid Relation Handle Provided [string] [string]
Cause: An invalid or corrupt relation handle was used.
Action: Possible memory corruption.
DIA-48001 to DIA-51705 23-13
DIA-48230: Expression arguments must match types

Cause: Incorrect type semantics for fields in the predicate.
Action: Correct the predicate.
DIA-48231: Predicate syntax error
Cause: A syntax error exists in the predicate string.
Action: Correct the predicate.
DIA-48232: Debug command syntax error [string]
Cause: An invalid debug command has been specified.
Action: Correct the debug command.
DIA-48233: Invalid Field Handle [string] [string] [string]
Cause: The field handle is invalid.
DIA-48238: Invalid Surrogate Length Specified [string] [string]
Cause: An invalid length during create field was specified
Action: Specify a correct length
DIA-48239: Invalid Predicate Handle Provided [string] [string]
Cause: An invalid or corrupt relation handle was used.
DIA-48240: Field is NOT NULL but NULL value supplied
Cause: A field [%s] declared to not allow nulls contains a null value.
Action: Specify a correct value
DIA-48242: Fields that are NOT NULL can not use surrogates
Cause: NOT NULL fields can not have surrogates specified.
Action: Either remove the constraint or the surrogate.
DIA-48243: Additional Fields must be declared nulls allowed
Cause: A field can not be added to a relation that is defined NOT NULL
Action: Do not specify NOT NULL
DIA-48244: Purge for Retention can't be called while in an Query
Cause: A query is already running - purge for retention can't be invoked
Action: Fix call sequence
DIA-48245: Attempt to Update/Delete when at EOF
Cause: The fetch operation is positioned at EOF - can not update/delete
Action: Do not call update/delete after fetch has returned EOF
DIA-48246: Illegal Operation on External Relation
Cause: An illegal call was made using an external relation
Action: Do not perform the API Call
DIA-48247: Predicate Conversion Error string
Cause: A time conversion failed
Action: Fix the input

DIA-48248: Function string type check error; ityp = string typ = string arg = string
Cause: Invalid inputs to the specified function
Action: Change the inputs
DIA-48251: Failed to open relation due to following error
Cause: See error below in the error stack
Action: See error below in the error stack
DIA-48252: Relation does not require migration
Cause: Relation on disk is compatible with the current code
Action: Don't run the migration services
DIA-48258: AMS Corrupt Page Found - Rebuild Relation
Cause: A corrupted page has been found.
Action: Do a rebuild of the relation
DIA-48259: AMS Relation not Created Correctly
Cause: Create relation failed
Action: Recreate the relation
DIA-48260: Function string not found
Cause: A reference to a function that is not valid was found
Action: Fix the function name
DIA-48262: Sequence references not allowed in predicates
Cause: References to currval or nextval not allowed
Action: Remove these references
DIA-48263: Currval not set yet - use nextval
Cause: References to currval can't occur until a nextval is done
Action: Remove the reference
DIA-48265: Incorrect number of arguments (string) provided - expected (string)
Cause: Number of arguments to function is incorrect
Action: Specify the correct number of arguments
DIA-48291: Field name string can't be unique resolved
Cause: Field name appears in more than one relation
Action: Prefix the field name with the relation name
DIA-48292: Can't use outer join syntax mixed with inner join syntax
Cause: The join condition was specified using both inner and outer join elements"
Action: Specify the join condition correctly
DIA-48293: Outer join syntax not allowed without a join
Cause: Using outer join syntax in the predicate without doing a join
Action: Fix the predicate
DIA-48001 to DIA-51705 23-15
DIA-48300: Incident Record Already Exists

Cause: trying to create an incident that already exists
Action: retry operation with new incident ID
DIA-48301: An Invalid Incident ID was specified
Cause: the specified incident ID was invalid
Action: retry operation with correct incident ID
DIA-48302: Incident Directory does not exist
Cause: the incident directory was not found
Action: retry operation with a different incident ID
DIA-48303: Exceeded max Incident Sequence Value
Cause: the maximum supported incident sequence value was exceeded
Action: reset incident sequence and retry operation
DIA-48304: incident staging file not found
Cause: the incident staging file is missing
Action: retry with a different incident ID
DIA-48305: incident ID range is too large
Cause: the maximum incident sequence value was exceeded
Action: retry operation with a smaller range
DIA-48309: illegal incident state transition, [string] to [string]
Cause: the incident cannot be moved to the new state
Action: retry operation with a valid incident status
DIA-48310: Incident string staging file not found
Cause: the incident staging file does not exist
Action: retry operation with a valid incident ID
DIA-48311: Invalid field name [string]
Cause: the specified field name is invalid
Action: retry operation with a valid field name
DIA-48312: Sweep incident string staging file failed
Cause: the sweep action of incident staging file failed
Action: check the incident ID and retry
DIA-48313: Updates not allowed on ADR relation [string] of Version=string
Cause: Update operations not supportd on this version of ADR relation
Action: check ADR version and retry
DIA-48314: Invalid ADR Control parameter [string]
Cause: the specified control parameter is invalid
Action: check parameter and reissue command
DIA-48315: ADR unavailable
Cause: the ADR directory is not available
Action: enable ADR and retry operation

DIA-48316: relation [string] unavailable or cannot be created
Cause: the ADR relation is not available
Action: check ADR directory and retry operation
DIA-48317: ADR Relation [string] of version=string is obsolete
Cause: the version of ADR relation is too old and not supported
Action: check the ADR version and retry
DIA-48318: ADR Relation [string] of version=string cannot be supported
Cause: the version of ADR relation is too new and cannot be supported
Action: need to use a newer release to access the ADR
DIA-48319: Update operation on ADR relation [string] not allowed
Cause: updates to foreign ADR relation cannot be supported
Action: verify ADR location and reissue command
DIA-48320: Too many incidents to report
Cause: the result set of incidents is too large to handle
Action: use a predicate to reduce the number of incidents and retry
DIA-48321: ADR Relation [string] not found
Cause: the required ADR relation is missing, ADR may be corrupted
Action: check ADR directory and retry
DIA-48322: Relation [string] of ADR V[string] incompatible with V[string] tool
Cause: the tool version is incompatible with the ADR version
Action: use another version of tool and retry
DIA-48323: Specified pathname [string] must be inside current ADR home
Cause: A file outside of ADR home was not allowed for this type of file.
Action: Check the file name and retry.
DIA-48324: Incompatible staging file encountered
Cause: sweep incident failed because staging file is incompatible
Action: check the incident ID and version of ADR and retry
DIA-48339: view [string] does not exist
Cause: view has not been created
Action: verify view name and reissue command
DIA-48340: operation not supported on view [string]
Cause: unsupported (dml) operation on views
Action: verify relation name and reissue command
DIA-48341: Field [string] not a grouping field
Cause: the field name specified is not a grouping field
Action: verify field names and groupby clause and reissue command
DIA-48001 to DIA-51705 23-17
DIA-48342: Field [string] cannot be mixed with string fields

Cause: the specified field is incompatible with other grouping fields *A8ction: verify
this and other field names and reissue command
Action: n/a
DIA-48343: invalid field [string] reference in string clause
Cause: the specified field in the specified clause is invalid
Action: verify this field name and reissue command
DIA-48344: Invalid Name [string] specified
Cause: Either the name refers to an existing object or violates the reserved namespace
rules.
Action: Pick another name
DIA-48345: Timeout encountered during operation
Cause: The attempted operation conflicted with another operation that was already
being executed.
Action: Retry operation at a later time.
DIA-48400: ADRCI initialization failed
Cause: The ADR Base directory does not exist
Action: Either create an ADR Base directory or point to an existing one
DIA-48401: SET command requires arguments
Cause: No arguments are input for the SET command
Action: Input the arguments
DIA-48402: Variable is not defined
Cause: No substitution value is input.
Action: Input the substitution value following after the variable name.
DIA-48403: DEFINE or UNDEFINE command has no arguments
Cause: DEFINE and UNDEFINE command need users to input the substitution
variable name.
Action: Input the vairable name follow after the DEFINE or UNDEFINE
DIA-48404: RUN or @ command has no arguments
Cause: RUN and @ commands need users to input script filename
Action: Input script filename after RUN and @ commands
DIA-48405: The option in the command is invalid
Cause: The option is not allowed in the command
Action: Check the command syntax
DIA-48406: ECHO or TERMOUT status must be set to ON or OFF
Cause: the status of ECHO ann TERMOUT commands must be ON or OFF
Action: input ON or OFF
DIA-48407: DESCRIBE and QUERY commands need at least relation name

argument
Cause: This is no relation name is input as argument
Action: Need users to input at least the relation name
DIA-48408: The incident number exceeds the maximum number [string]
Cause: The input incident number exceeds the maximum number
Action: Input less incidents
DIA-48409: The ADR homes exceeds the maximum number [string]
Cause: The input ADR homes number exceeds the maximum number
Action: Input less ADR home string
DIA-48410: The trace path exceeds the maximum number [string]
Cause: The input trace path exceeds the maximum number
Action: Input less trace path
DIA-48411: The trace files exceeds the maximum number [string]
Cause: The input trace file path number exceeds the maximum number
Action: Input less trace file path
DIA-48412: The parameters exceeds the maximum number [string]
Cause: The input paramter number exceeds the maximum number
Action: Input less parameter number or increase the upper bound
DIA-48413: The number of orderby fields exceeds maximum number [string]
Cause: The orderby field number exceeds the maximum number
Action: Input less fields
DIA-48414: The string in the execution option exceeds maximum length [string]
Cause: The string length is too long
Action: Divid the commands into two sets or use adrci scripts.
DIA-48415: Syntax error found in string [string] at column [string]
Cause: Parsing error found in the user input string
Action: Validate the input string
DIA-48419: Illegal arguments
Cause: The input argument is illegal
Action: Check the input arguments and make sure it is not null
DIA-48421: Predicate string in the command must be single or double quoted
Cause: The predicate string is not single or double quoted
Action: Put single or double quotes around the predicate string
DIA-48423: IMPORT command must have a filename
Cause: File name is missing from the command
Action: Input the import file name after the IMPORT keyword
DIA-48001 to DIA-51705 23-19
DIA-48424: SHOW TRACE command needs argument

Cause: SHOW TRACE command needs arguments
Action: Input arguments
DIA-48426: The initialization filename is too long
Cause: The initialization filename length exceeds the maximum length
Action: This is really an internal setting parameter of the ADRCI, report it as a bug.
Alternatively move the initialization file to the current working directory
DIA-48428: Input command string exceeds max length [string]
Cause: The current command string is too long and exceeds the limit
Action: Input less characters
DIA-48429: Variable name [string] is an invalid identifier
Cause: The substitution variable name is not a valid identifier
Action: Input the valid identifier defined by ADRCI
DIA-48431: Must specify at least one ADR home path
Cause: The command syntax requires at least one ADR home path to be input
Action: Check the command syntax and input the home path
DIA-48432: The ADR home path [string] is not valid
Cause: The adr home user inputs is not valid, which may due to the path does not
exist.
Action: Check if the input home path exists
DIA-48433: Unknown help topic
Cause: The input topic is unknown
Action: Check if the topic is vaild
DIA-48434: No DDE commands are input
Cause: No DDE commands are input
Action: Input a DDE command
DIA-48435: Input a trace file
Cause: Show trace expects a trace file
Action: Input a trace file
DIA-48436: File [string] does not exist
Cause: the file does not exist
Action: Validate the trace file name
DIA-48437: No IPS commands are input
Cause: No IPS commands are input
Action: Input a IPS command
DIA-48438: [string] is not a valid number
Cause: The input number is not valid
Action: Check the input number
DIA-48439: The input path name exceeds the maximum length [string]
Cause: The input path name is too long
Action: Report as a bug to change the limit
DIA-48440: Variable [string] is already defined
Cause: The variable name is defined previously
Action: Use another variable name
DIA-48441: The function parameter number exceeds the maximum number [string]
Cause: The function parameter number exceeds the maximum number
Action: Report it as bug to change the maximum number
DIA-48442: The control parameter number exceeds the maximum number [string]
Cause: The control parameter number exceeds the maximum number
Action: Report it as bug to change the maximum number
DIA-48443: Trace Record type appears in the middle of the path
Cause: The trace record cannot be in the middle of the path
Action: Validate the input
DIA-48444: The single "." and "*" cannot appear in the middle of the path
Cause: The single "." and "*" appears in the middle of the path
Action: Validate the input
DIA-48445: Path expression only supports one bucket dump type
Cause: The path expression only supports one bucket dump"
Action: Change the path expresison syntax
DIA-48446: The command needs path input
Cause: No path is input as a parameter
Action: Input the path
DIA-48447: The input path [string] does not contain any ADR homes
Cause: The input path does not contain ADR homes
Action: Validate the path
DIA-48448: This command does not support multiple ADR homes
Cause: There are multiple homes in the current adr setting.
Action: Use command SET HOMEPATH to set a single home
DIA-48449: Tail alert can only apply to single ADR home
Cause: There are multiple homes in the current setting
Action: Use command SET HOMEPATH to set a single home
DIA-48457: ADRCI core dumped
Cause: It is adrci internal error.
Action: Report to Oracle
DIA-48458: "show incident" failed due to the following errors
Cause: There could be a bug or users do not have the access permission
DIA-48001 to DIA-51705 23-21
Action: Report to Oracle if the errors are not due to ADR permission settings
DIA-48459: "describe" command only supports one ADR home path
Cause: Multiple ADR home paths in the command
Action: put one ADR home path
DIA-48460: The home path [string] is not valid
Cause: The input home path is not valid home path
Action: Verify the homepath
DIA-48461: "describe" failed due to the following errors
Cause: Underlying code failed
Action: If it is not due to permission issue, report to Oracle
DIA-48462: Fatal error encountered in [string]
Cause: Fatal error encountered
DIA-48463: The value buffer reached the maximum length [string]
Cause: The value buffer is full
DIA-48464: The predicate buffer reached the maximum length [string]
Cause: The predicate buffer is too small
DIA-48465: The specified type [string] is undefined
Cause: The purge type specified is undefined
Action: Check the type name
DIA-48466: Internal failure, the report context is not initialized
Cause: Internal problem failure.
DIA-48467: "string" for the keyword "string" is not a valid number
Cause: The keyword value is not a valid number
Action: Check the value
DIA-48468: "string" is not a valid keyword
Cause: The keyword is not defined for the command
Action: Check the available keywords
DIA-48469: Keyword "string" cannot be duplicated
Cause: The command can only allow one key with the name
Action: Remove one keyword name from the command
DIA-48470: Unknown "string" command
Cause: The command is not valild
Action: Use help manual to check the command syntax
DIA-48472: Invalid product name

Cause: The product name provided does not exist
Action: Specify a product name, see HELP SHOW BASE
DIA-48473: Internal failure, unknown return code [string]
Cause: Internal program failure
DIA-48474: Syntax error specifying product, must not be NULL
Cause: The product clause is being used, but no product name is provided
Action: Supply the product name
DIA-48475: [string] is not a valid timestamp
Cause: The input timstamp string is not in valid format
Action: None
DIA-48476: Cannot write the results out to a file, please check if \nthe environment
variable TMPDIR is set or the current directory is \nnot writable
Cause: The current path may not be writable
Action: If the current path is writable, report to Oracle
DIA-48477: The input path does not contain any valid ADR homes
Cause: The input path does not contain any valid ADR homes
Action: Check the path if it is valid
DIA-48478: No alert messages are created
Cause: No alert messages are created
Action: No action
DIA-48479: No HM runs are created
Cause: There is no hm runs
Action: No action
DIA-48480: No incidents are created
Cause: There is no incident
Action: No action
DIA-48481: Report is not available
Cause: The requested report does not exist"
Action: Check the report ID
DIA-48482: Report is not generated
Cause: The requested report is not ready to be generated
Action: Check the report ID
DIA-48483: Spooling failed, it may be because the spool file cannot be created due
to a permission issue
Cause: The spooling filename may not be valid or the file cannot be created
Action: Check the permissions of the target directory and verify the filename
DIA-48001 to DIA-51705 23-23
DIA-48484: Run script failed, it may be because the script file does not exist
Cause: The script file may not exist
Action: Check if the script file exist
DIA-48485: The file exceeds the maximum length [string]
Cause: The filename is too long
DIA-48486: The file [string] exceeds the maximum length [string]
Cause: The filename is too long
DIA-48487: The internal predicate string exceeds the maximum length [string]
Cause: The predicate string exceeds the maximum length
DIA-48488: The predicate string exceeds the maximum length [string]
Cause: The input predicate string exceeds the maximum length
DIA-48489: The input exceeds the maximum length [string]
Cause: The input exceeds the maximum length
DIA-48490: The field number exceeds the maximum number [string]
Cause: The input field number exceeds the maximum number
Action: Input less field names
DIA-48491: The program name is too long, exceeds the maximum length [string]
Cause: the program name length exceeds the maximum length setting
DIA-48492: The report component name is not defined
Cause: the report component name does not exist
Action: Check the component name to ensure it is registered
DIA-48493: Sweep command needs parameters
Cause: sweep command needs parameter
Action: Check the syntax of the command
DIA-48494: ADR home is not set, the corresponding operation cannot be done
Cause: The adr home is not set in the current adrci session
Action: Set the adr home using the adrci command "set base" and "set homepath"
DIA-48495: Interrupt requested
Cause: User requested to interrupt the current action
Action: No action is needed
DIA-48496: "string" is a mandatory keyword for the command
Cause: The keyword is not specified for the command
Action: Input the keyword

DIA-48497: "string" is an invalid product type
Cause: The product type is not registered
Action: Check the product type
DIA-48499: The value of the keyword "string" exceeds the maximum length string
Cause: The keyword value is too long
Action: Check the limit and input again
DIA-48500: File Write Error [string] [string]
Cause: Number of bytes written differs from number requested. Possibly due to out
of disk space.
Action: Ensure sufficient disk space.
DIA-48501: File Read Error [string] [string]
Cause: Number of bytes read differs from number requested. Possibly due due to
corrupted file.
Action: Recreate the file.
DIA-48502: Invalid Command Line - Missing Required Elements
Cause: Missing required command line arguments.
Action: Review the help message and supply the required arguments.
DIA-48503: Invalid Parameter Specified
Cause: Invalid input parameter supplied.
Action: Review the help message and correct the invalid input parameter.
DIA-48504: Relation Parameter Must be Specified
Cause: Relation parameter must be specified during adrexp.
Action: Supply the relation parameter.
DIA-48505: File Parameter Must be Specified
Cause: File parameter must be specified during adrimp.
Action: Supply the file parameter.
DIA-48506: Existing Relation at different version than export [string] [string]
Cause: Attempting to import into an existing relation and the schema version of that
relation differs from the schema of the relation that was exported.
Action: Drop the existing relation if you still wish to import the relation.
DIA-48507: Predicate Not Allowed during Import
Cause: The predicate option is not allowed during adrimp.
Action: Remove the predicate arguement.
DIA-48508: Export File Version [string] Can Not be Used by Import [string]
Cause: The version of the export file is not able to be read by this version of adrimp.
Action: Rerun the export using the current version of adrexp.
DIA-48509: Error occurred during operation. See the following errors
Cause: An underlying error has occurred.
DIA-48001 to DIA-51705 23-25
Action: Review and correct the underlying error.

DIA-48510: Can not export an in memory relation
Cause: In memory relations can not be exported.
Action: Pick a different relation.
DIA-48600: HM run with name [string] already exists
Cause: The specified run name already existed.
Action: Specify different run name and re-run the check
DIA-48615: Parameter [string] value not specified
Cause: Run was invoked without specifying the parameter and its value
Action: Specify the needed parameter and its value
DIA-48618: Invalid HM run name specified
Cause: An invalid Health Monitor (HM) run name was specified.
Action: Specify a HM run name using only alphanumeric and underscore characters.
DIA-48800: "string" for the keyword "string" is not in the right format of timestamp
Cause: The value format is not right
Action: Check the format ADRCI supports
DIA-48801: The option "string" is duplicated
Cause: The option has been specified more than once
Action: Check the input
DIA-48802: The options "string" and "string" are mutual exclusive
Cause: These two options cannot be specified together
Action: Only specify one of them
DIA-48803: The keyword "string" is not defined for this command
Cause: The keyword is invalid
Action: Check the valid keywords for the command
DIA-48804: The command needs at least one file input
Cause: No files are specified to view
Action: Input the files
DIA-48805: BEGIN BACKUP issued already - must do an END BACKUP first
Cause: A begin backup was already issued.
Action: Issue END BACKUP
DIA-48806: Unknown Function Reference (string)
Cause: The function reference is not a valid function
Action: Change the reference
DIA-48807: The SET subcommand requires at least one additional parameter
Cause: An argument was not specified for the SET subcommand.
Action: Specify additional arguments or precede the command with help.
DIA-48808: malformed SET CONTROL command - see "help SET CONTROL"

Cause: Improper syntax was specified for the SET CONTROL command.
Action: Specify additional arguments or precede the command with help.
DIA-48900: Illegal Input Argument [string]
Cause: The input argument is invalid
Action: Check the input parameter
DIA-48906: Parser context is not valid
Cause: The parser context is not initlialized
Action: Call the initialization routine first before using the context
DIA-48907: The end of file is reached
Cause: The end of file is raeched
Action: Handle the end of file
DIA-48908: No trace files are found
Cause: This is no file in the navigator context, either it is done with parsing, or no file
is pushed
Action: Check if the file is added to the context
DIA-48909: Scan context is not initialized
Cause: The scan context is not initialized
Action: call the initliazation routine of the scan context
DIA-48912: The specified trace filename is too long
Cause: The resulting trace filename length exceeds the maximum length
Action: Use a smaller trace filename suffix or move ADR higher in the directory
hierarchy
DIA-48913: Writing into trace file failed, file size limit [string] reached
Cause: An attempt was made to write into a trace file that exceeds the trace's file size
limit
Action: increase the trace's file size limit.
DIA-48914: File position is not in right format
Cause: The file positon format is not right
Action: Check if the file format string is the right one
DIA-48928: The predicate exceeds the max limit string
Cause: The predicate is too long, exceeds the max limit
Action: Use a shorter predicate
DIA-48929: The trace record size exceeded the max size that can be read [string]
Cause: A trace record is too large to be read by the ADR viewer
DIA-48930: Cannot allocate memory for processing traces
Cause: A memory allocation request failed
DIA-48001 to DIA-51705 23-27
DIA-48934: invalid input for the file name identifier

Cause: An invalid input was given for the file name indentifier. The file name is not
allowed to have slashes ('', '/') and is not allowed to refer to the parent directory using
the '..' characters.
Action: Check the file name and provide a valid input.
DIA-48936: The number of relations exceeds maximum number [string]
Cause: Too many relations listed
Action: Reduce the number
DIA-48937: Feature (string) currently not allowed for SELECT
Cause: Feature is not allowed
Action: Remove feature
DIA-48938: View select column count differs from select alias list
Cause: The view alias list has a different number of fields than the select list"
Action: Change the alias list or view select statement
DIA-48939: Select * not allowed in a CREATE VIEW
Cause: * is currently not allowed for a create view select list
Action: List the fields explicitly
DIA-49315: Invalid incident type specified [string]
Cause: The specified incident type is not defined in this ADR.
Action: Specify an available incident type.
DIA-49404: No such package [string]
Cause: The specified package does not exist.
Action: Specify an existing package.
DIA-49405: Cannot change package name [string] [string]
Cause: Attempted to change package name after package generation.
Action: Use current name, or create a new package with the desired name.
DIA-49406: Undefined configuration parameter specified [string]
Cause: The specified configuration parameter was not found in ADR.
Action: Specify an existing parameter. Re-populate parameters if necessary.
DIA-49407: No unpacking history in this home
Cause: No packages were unpacked into this home.
Action: Verify the current home. Unpack a package if necessary.
DIA-49408: Invalid home specified [string]
Cause: An invalid ADR_HOME was specified.
Action: Verify that the directory exists, and has the correct structure.
DIA-49409: Incremental package provided when complete expected
Cause: No packages were unpacked into this home.
Action: Provide a complete package, or use FORCE option.
DIA-49410: Not an IPS package

Cause: The specified file was not an IPS package.
Action: Verify that the file is a valid zip file with expected contents.
DIA-49412: Package ID does not match existing ID [string] [string]
Cause: The package ID in package file did not match previously unpacked packages.
Action: Use the correct location for unpacking the package.
DIA-49413: Package name does not match existing name [string] [string]
Cause: The package name in package file did not match previously unpacked
packages.
Action: Use the correct location for unpacking the package.
DIA-49414: Package sequence later than expected [string] [string]
Cause: The package sequence in package file was later than expected.
Action: Apply packages in correct order, or use FORCE option.
DIA-49415: Package sequence earlier than expected [string] [string]
Cause: The package sequence in package file was earlier than expected.
Action: Apply packages in correct order, or use FORCE option.
DIA-49416: Earlier package sequence applied with FORCE option [string] [string]
Cause: An earlier package sequence was applied using the FORCE option.
Action: Apply a complete sequence which is later than any already applied, or use
FORCE option to apply an incremental package.
DIA-49417: Cannot modify already generated package
Cause: Attempted to change package attributes after package generation.
Action: Create a new package with the desired name.
DIA-49418: Invalid package name specified
Cause: An invalid Incident Packaging Service (IPS) package name was specified.
Action: Specify a package name using only alphanumeric and underscore characters.
DIA-49420: Package too large [string] [string]
Cause: The package is too large.
Action: Remove some files or incidents from the package, or try using incremental
mode.
DIA-49421: Maximum number of package files generated [string]
Cause: The command generated the maximum number of package files.
Action: Remove some files or incidents from the package, or use incremental mode to
generate additional files.
DIA-49423: File outside ADR not allowed
Cause: The specified file is not within the ADR directory structure.
Action: Specify a file inside ADR.
DIA-49424: Directory outside ADR not allowed
Cause: The specified directory is not within the ADR directory structure.
DIA-48001 to DIA-51705 23-29
Action: Specify a directory inside ADR.

DIA-49425: File inside ADR not allowed
Cause: The specified file is within the ADR directory structure.
Action: Specify a file outside ADR.
DIA-49426: Directory inside ADR not allowed
Cause: The specified directory is within the ADR directory structure.
Action: Specify a directory outside ADR.
DIA-49427: No such file or file not accessible [string]
Cause: The specified file does not exist or cannot be accessed.
Action: Create the file or verify file permissions.
DIA-49428: No such directory or directory not accessible [string]
Cause: The specified directory does not exist or cannot be accessed.
Action: Create the directory or verify directory permissions.
DIA-49429: File already exists and OVERWRITE option not specified [string]
Cause: The client attempted to create a file that already exists.
Action: Either remove the file or use the OVERWRITE option.
DIA-49430: No such problem [string]
Cause: The specified problem does not exist.
Action: Specify a problem that exists in this repository.
DIA-49431: No such incident [string]
Cause: The specified incident does not exist.
Action: Specify an incident that exists in this repository.
DIA-49432: Problem not part of package [string]
Cause: The specified problem is not included in the package.
Action: Specify a problem that is included in the package.
DIA-49433: Incident not part of package [string]
Cause: The specified incident is not included in the package.
Action: Specify an incident that is included in the package.
DIA-49434: Invalid date format
Cause: An invalid format was used to specify a date
Action: Specify the date in a supported format.
DIA-49435: Flood-controlled incident not allowed here [string]
Cause: A flood-controlled incident cannot be included in a package
Action: Specify an incident that is not flood-controlled
DIA-49436: Date conversion error [string]
Cause: An invalid format was used to specify a date
Action: Specify the date in a supported format.
DIA-49440: Warnings while unpacking package, details in file string

Cause: There were some non-fatal errors when unpacking a package
Action: Review the specified unpacking log file
DIA-49441: Warnings while finalizing package, details in file string
Cause: There were some non-fatal errors when finalizing a package
Action: Review the specified finalize log file
DIA-49450: Non-zero return code from archiving utility [string] [string]
Cause: The archiving utility (zip/unzip) returned a warning or error.
Action: Verify that the file and directory exist and are readable, and that the file is a
valid zip file.
DIA-49451: Archive file structure error [string] [string]
Cause: The archiving utility (zip/unzip) returned an error indicating that the archive
file structure is incorrect.
Action: Verify that the file was transferred correctly and that the file is a valid zip file.
DIA-49452: Archiving utility out of memory [string] [string]
Cause: The archiving utility (zip/unzip) returned an error indicating that it was
unable to allocate enough memory.
Action: Check for operating system limitations on process memory usage.
DIA-49453: Invalid command invoking archiving utility [string] [string]
Cause: The archiving utility (zip/unzip) was invoked with an invalid command line,
or with invalid options.
Action: Verify that there are no operating system settings affecting the behavior of the
archiving utility..
DIA-49454: Archive is missing or empty [string] [string]
Cause: The specified archive does not exist, or is empty.
Action: Check if the specified archive exists.
DIA-49455: Archive I/O failed [string] [string]
Cause: An attempt to create, write to or read from an archive failed.
Action: Verify that operating system I/O operations are working correctly.
DIA-49456: Operation failed due to insufficient disk space [string] [string]
Cause: An operation on an archive failed due to insufficient disk space.
Action: Verify that there is sufficient disk space. Check for operating system quotas or
other restrictions.
DIA-49601: syntax error: found "string": expecting one of: "string" etc..
Cause: Syntax error discovered when processing event speciifcation
Action: Enter correct event specification
DIA-49701: Parameter 'string' is NULL.
Cause: NULL was passed to a function that requires a non-NULL parameter.
Action: Pass a valid non-NULL parameter.
DIA-48001 to DIA-51705 23-31
DIA-49702: unable to allocate 'string' bytes of external procedure call memory

Cause: An attempt to allocate memory in a C external procedure failed due to
Action: Try the operation again.
DIA-49703: invalid ADR service name
Cause: A NULL or undefined Automatic Diagnostic Respository (ADR) service name
was specified.
Action: Specify a valid ADR service name.
DIA-49704: invalid incident ID
Cause: A NULL or nonpositive incident ID was specified.
Action: Specify a valid ADR incident ID.
DIA-51001: check [string] not found in HM catalog
Cause: checker name might have been misspelled
Action: retry running check with proper checker name
DIA-51003: run parameters not formatted correctly
Cause: Run parameters were given in a wrong format
Action: Correct the run params text and try again
DIA-51004: Check doesn't take any input params
Cause: run params were passed to the check, which doesn't take any inputs
Action: don't pass any run params and try again
DIA-51006: unexpected delimter ';' in the run params text
Cause: run params were not properly formatted.
Action: correct the run params format and try again
DIA-51007: parameter [string] not registered with this check
Cause: Wrong inputs were given to this check.
Action: correct the run params and try the check again
DIA-51008: parameter [string] value is not a proper number
Cause: the given parameter value is a not a proper number
Action: correct the run params and try again
DIA-51025: check name should be non NULL value
Cause: NULL value was passed for check name
Action: give a proper check name and retry again
DIA-51035: invalid timeout value
Cause: User specified an invalid timeout value
Action: n/a
DIA-51036: check [string] can only be executed in database instance
Cause: An attempt was made to run database-specific check in ASM environment
Action: Don't run the check in ASM environment
DIA-51037: check [string] can only be executed in ASM instance

Cause: An attempt was made to run ASM-specific check in a database environment
Action: Don't run the check in database environment
DIA-51102: cannot change priority of a critical failure string
Cause: An attempt was made to change priority of a failure with CRITICAL priority.
DIA-51103: cannot change priority of a closed failure string
Cause: An attempt was made to change priority of a closed failure.
DIA-51105: cannot change priority of a failure to CRITICAL
Cause: An attempt was made to change priority of a failure to CRITICAL.
DIA-51106: check failed to complete due to an error. See error below
Cause: While executing the check, an unexpected error occured.
Action: Check the errors below and try rerunning the check.
DIA-51107: failures are changing too rapidly - retry command
Cause: Failures were added or closed during a Data Recovery Advisor command.
Action: Retry the command.
DIA-51108: unable to access diagnostic repository - retry command
Cause: A lock or timeout error occurred when trying to read failure or repair data
from the Automatic Diagnostic Repository.
DIA-51109: repair script file is too large
Cause: Data Recovery Advisor generated a repair script file that was too large.
Action: Retry the command with fewer failures selected.
DIA-51110: buffer size [string] is too small - [string] is needed
Cause: An internal buffer was too small.
DIA-51111: failure revalidation timed out
Cause: Data Recovery Manager was unable to revalidate all failures before timing out.
Action: Increase timeout and retry the command.
DIA-51190: Internal error [string], [string] from DBMS_IR
Cause: An unexpected error occurred while executing a routine in the DBMS_IR
package.
DIA-51191: Too many files opened
Cause: Data Recovery Advisor attempted to open too many files using the DBMS_IR
package.
DIA-48001 to DIA-51705 23-33
DIA-51192: File not open

Cause: Data Recovery Advisor attempted to read or write from a file that was not
open.
DIA-51193: invalid parameter value
Cause: An invalid parameter value was supplied in a call to the DBMS_IR package.
Action: Fix the parameter value and retry the call.
DIA-51303: illegal check mask value specified
Cause: An illegal check mask value was specified.
Action: Specify one of the following legal values: COLUMN_CHECKS,
ROW_CHECKS, REFERENTIAL_CHECKS, or ALL.
DIA-51316: No check meta-data found on specified table string
Cause: No check meta-data was found for the object
Action: Table may not exist or no checks currently defined for the table
DIA-51700: Invalid file URL
Cause: A URL with invalid syntax was provided, either directly to the function or
through an XML IMPORT or INCLUDE.
Action: Check the URL.
DIA-51701: Invalid file URL or path prefix
Cause: Either a URL or path prefix with invalid syntax was provided.
DIA-51702: Could not find file at URL provided
Cause: The file requested could not be found in the given location.
Action: Check the URL provided.
DIA-51703: Missing body tag from HTML
Cause: An HTML document was passed to the function missing its body tag.
Action: Check the HTML source.
DIA-51704: Error string received from XPath engine
Cause: An error was received from the XPath library during an XPath operation.
Action: Check xmlerr.h to understand the cause of the error and correct the relevant
client code.
DIA-51705: XML string error: string "string"
Cause: An error was received from an underlying XDK API and is being resignalled.
Action: Check xmlerr.h to understand the cause of the error and correct the relevant
client code.
24
DRG-10000 to DRG-52403
DRG-10000: failed to read column string.string
Cause: Error during read of specified text column
Action: check existence and privs of column
DRG-10001: can not access result table string
Cause: specified table does not exist or server does not have write privileges
Action: check result table
DRG-10002: can not insert into result table
Cause: text server is not privileged to insert, tablespace exhausted
Action: check privileges and tablespace
DRG-10011: invalid object name string
Cause: a table, column or procedure name specified had an invalid format. It is either
too long or contains illegal characters. Probably you are passing in incorrect
parameters.
Action: check parameter values
DRG-10015: id exceeds limit(2147483642) of a number
Cause: the limit of an id is 2147483642
Action: use an id with value 214748364 or under
DRG-10016: you must be the owner to modify this object
Cause: you tried to modify an object which you do not own
Action: have the owner modify the object
DRG-10017: you must be string to do this: string
Cause: you tried to modify an object which you have no privilege
Action: have the owner modify the object
DRG-10100: invalid argument found: string
Cause: invalid command argument was specified
Action: check the documentation for the legal arguments and re-execute the
command
DRG-10101: no value for argument: string
Cause: this argument requires value(s)
Action: re-execute the command with the correct argument value(s)
DRG-10000 to DRG-52403 24-1
DRG-10102: mandatory argument missing: string

Cause: this argument is mandatory
Action: re-execute the command and specify the argument
DRG-10103: illegal value for argument: string
Cause: an illegal value was passed to this argument
Action: check the documentation for the legal values for this argument
DRG-10200: invalid server personality mask: string
Cause: the specification for the server personality mask is invalid
Action: check the documentation and specify the correct mask
DRG-10202: server failed to register
Cause: the server failed to register itself with the data dictionary
Action: look at the next error on the stack
DRG-10203: server named string does not exist
Cause: update was called with the name of a server that does not exist
Action: correct the name of the server
DRG-10204: server update failed
Cause: the attempt to update the server failed
DRG-10205: server deregister failed
Cause: the attempt to deregister the server from the data dictionary failed
DRG-10206: failed to perform recovery for a server or client
Cause: Contact oracle support
Action: Contact oracle support
DRG-10301: timed out waiting for responses from servers
Cause: Not enough servers are running to handle the current system load, and a large
backlog of commands has accumulated; perhaps no servers are running. This
message could also indicate an internal error where one of the servers has crashed
trying to process a given request
Action: Check that enough servers are running, and that they are processing
commands of the correct type. For instance, a DDL command might timeout if all the
servers are setup to exclusively process query commands. Also, check the server log
files.
DRG-10302: interrupted waiting for responses from servers
Cause: User interrupted the request before it was completed
Action: Restart the request
DRG-10303: could not queue given commands to be processed
Cause: The given command or commands could not (all) be queued. This could
indicate an extremely high system load, but it is more likely an internal error.
Action: Check if any servers are running to process the command.
24-2 Error Messages
DRG-10304: unexpected error sending command(s) to Oracle Text server

Cause: There was an unexpected error sending command(s) to server
Action: Call customer support.
DRG-10305: pipe string is full
Cause: Could not send command to pipe, because the pipe was full
Action: Check if any servers are running to process the commands on that pipe
DRG-10306: server terminated unexpectedly while processing command
Cause: The server shutdown during execution of your command. This could be
caused by a shutdown abort, or by an internal error in the server.
Action: If the server terminated had an internal error, contact customer support.
DRG-10307: no servers running
Cause: Could not process command because no servers are running with the correct
personality mask.
Action: Start some servers with correct personality mask.
DRG-10308: no server with the required string personality mask is running
Cause: Could not process command because no servers are running with the correct
personality mask.
Action: Start some servers with correct personality mask.
DRG-10309: not enough job queue processes
Cause: Could not process command because no servers with the correct personality
mask are running.
Action: increase the JOB_QUEUE_PROCESSES initialization parameter or reduce the
parallel degree for this statement.
DRG-10310: servers were shutdown before processing request
Cause: The command could not be completed because the servers were shut down or
terminated before processing the request.
Action: Start another server with the correct personality mask.
DRG-10311: remote send not supported
Cause: You tried to specify a database link in an index specification
Action: Specify only local index names
DRG-10312: logfile name must be specified
Cause: You tried to start logging without specifying a logfile name
Action: Specify a logfile name
DRG-10313: logging has already been started
Cause: You tried to start logging even though logging has already been started
Action: Stop logging first, or ignore
DRG-10314: logging has not been started
Cause: You tried to stop logging even though logging has not been started
Action: Start logging first, or ignore
DRG-10000 to DRG-52403 24-3
DRG-10315: logging is not supported on MTS

Cause: You tried to start logging on MTS
Action: n/a
DRG-10500: CREATE_INDEX failed: column spec string
Cause: failed to create text index on the specified column
Action: See the next errors on stack and take appropriate action
DRG-10501: invalid stopword: string
Cause: The stopword specified cound be lexed into multiple tokens with current lexer
preference
Action: Check lexer preference and Respecifies the stopword
DRG-10502: index string does not exist
Cause: the specified index does not exist or you do not have access to it.
Action: Specify an existing index
DRG-10503: table string cannot be indexed because it has no primary key
Cause: a textkey needs to be a single column unique key whose length does not
exceed 64 bytes. no such key was defined as an unique index or declared as a primary
or unique key constraint
Action: create a suitable textkey for the table or specify it explicitly in this procedure
call
DRG-10504: primary key is required when using the DETAIL_DATASTORE
Cause: you tried to use the detail datastore to index a table with no primary key
constraint
Action: add a primary key constraint on the table
DRG-10506: table does not exist: string
Cause: The table, view, or synonym specified does not exist. There may also be a
permissions problem reading the table.
Action: Reinvoke the operation with the correct table name
DRG-10507: duplicate index name: string
Cause: the specified index already exists in the dictionary
Action: this index can be updated or deleted, however this is only allowed if there is
no text index available on the text column
DRG-10509: invalid text column: string
Cause: the column specified is not valid
Action: check that the followings are valid: a) text column is of supported datatype b)
valid table name, column name in the specification.
DRG-10510: stopword is missing
Cause: The stopword to be added was not specified.
Action: Specify the stopword
DRG-10511: index string does not exist or is incomplete
Cause: index creation is not complete
Action: create index before performing this operation
24-4 Error Messages
DRG-10513: index string metadata is corrupt

Cause: dictionary contains bad preferences for this index
Action: contact you DBA
DRG-10516: failed to perform DDL operation due to an Oracle error
Cause: the ddl operation requested has failed because of an Oracle error
Action: see the Oracle error on the stack and take the appropriate action
DRG-10517: index string is already valid
Cause: The index was in a valid state and did not need the requested operation.
Action: Check the requested operation
DRG-10518: an operation is in progress which conflicts with string request
Cause: another session is operating on this index. it could be: a) DML is requested and
DDL is in progress or b) DDL is requested and DML is in progress operation on the
index
Action: try again later
DRG-10520: failed to drop index: string
Cause: Failed to drop index on the specified index
DRG-10525: missing REBUILD keyword
Cause: all Oracle Text alter index options require the REBUILD keyword
Action: specify alter index with the REBUILD keyword
DRG-10528: primary keys of type string are not allowed
Cause: you tried to create an index on a table with an illegal primary key datatype
Action: change the textkey to one of the followings: VARCHAR2, NUMBER,
VARCHAR, DATE, CHAR, MLSLABEL
DRG-10531: parallel parameter must be > 0
Cause: you called create index with parallel = 0
Action: specify with value > 0
DRG-10532: table is not partitioned
Cause: you called parallel create index on non-partitioned table
Action: recreate the table with partitions or remove the PARALLEL clause
DRG-10533: invalid user name: string
Cause: you specified a user name that is invalid
Action: specify the correct user name
DRG-10535: failed to optimize text index string
Cause: the optimize operation requested has failed because of an Oracle error
DRG-10549: length of the object name string exceeded the limit
Cause: object name has exceeded the maximun length of 30 bytes
Action: Reduce the length of the object name if you want to re-create it
DRG-10000 to DRG-52403 24-5
DRG-10550: illegal syntax for index, preference, source or section name

Cause: name may have additional periods(.)
Action: check the syntax of the name
DRG-10553: illegal syntax for column specification string
Cause: column specification may have additional periods(.)
Action: check the syntax of column specification if you want to re-create it
DRG-10561: index string is not valid for requested operation
Cause: The index was not in a valid state due to some prior error.
Action: Drop index and create index again.
DRG-10562: missing alter index parameter
Cause: The parameter string was missing
Action: Provide correct parameter string with regard to the requested alter index
operation.
DRG-10569: table or column does not exist: string
Cause: The table, view, synonym or column specified does not exist. There may also
be a permissions problem reading the table.
Action: Reinvoke the operation with the correct table name or column name
DRG-10573: index string is obsolete
Cause: you specified an obsolete index
Action: perform upgrade_index on the index
DRG-10574: failed to upgrade text index string
Cause: the upgrade operation has failed because of an Oracle error
DRG-10579: must provide text query criteria
Cause: text query criteria is mandatory
Action: provide text query criteria
DRG-10580: parallel indexing is not supported: string
Cause: attempted to create index with parallel servers
Action: Drop index and set parallel to 1 in create index
DRG-10581: indirect datastores cannot be used with long or lob text columns
Cause: You tried to create an index on a long or lob column using an indirect
datastore such as the file or url datastores
Action: Use direct datastore or a varchar column
DRG-10582: column string does not exist in table string
Cause: you specified an invalid column
Action: specify valid column
DRG-10583: TRUNCATE INDEX failed: string
Cause: Failed to truncate index
24-6 Error Messages
DRG-10584: failed to string string string due to an Oracle error

Cause: a DDL operation on an index object failed due to SQL error
Action: see following error
DRG-10595: ALTER INDEX string failed
Cause: failed to alter index
DRG-10597: invalid rebuild online operation
Cause: REBUILD ONLINE is not supported for requested operation.
Action: Alter index without the online option.
DRG-10598: invalid parallel operation
Cause: PARALLEL is not supported for requested operation.
Action: Alter index without the parallel option
DRG-10599: column is not indexed
Cause: The column specified is not indexed.
Action: Create index on the column before performing this operation
DRG-10601: failed to remove pending DML for this index
Cause: The system could not remove triggers setup to monitor updates to the
requested table
Action: See next error on stack to determine course of action. Call Oracle support if
necessary. Until this error is fixed, updates to all text columns in the given table may
not be indexed.
DRG-10602: failed to queue DML change to column string for primary key string
Cause: The system could not record that a change had been made to the given column
Action: See next error on stack to determine course of action. Call Oracle support if
necessary. Until this error is fixed, updates to all text columns in the given table may
not be indexed.
DRG-10606: server failed to access the DML Queue
Cause: The server was had an error accessing the DML Queue
Action: See next error on stack.
DRG-10607: index meta data is not ready yet for queuing DML
Cause: the meta data for the index has not been created yet
Action: retry the DML operation
DRG-10608: rowid to primary key mapping not available in base table
Cause: Procedural replication is on and no rowid to primary key mapping available
in base table
Action: Modify base table to include a primary key
DRG-10609: cannot encode composite key with more than 16 columns
Cause: Cannot encode composite key with more than 16 columns
Action: Modify base table to have composite key with less than 16 columns
DRG-10000 to DRG-52403 24-7
DRG-10610: Procedure not supported with Procedural replication on: string

Cause: This procedure is not supporeted when Procedural replciation is on
Action: Turn off procedural replication to execute this procedure
DRG-10700: preference does not exist: string
Cause: the preference name specified does not exists
Action: retry with the correct preference name
DRG-10701: preference string.string already exists
Cause: the specified preference already exists
Action: must drop the preference if you want to re-create it.
DRG-10702: cannot create or modify preference in another user's schema
Cause: you tried to create a preference for another user
Action: owner or CTXSYS or a user who has CTXADMIN role should create
preference
DRG-10703: invalid framework object string
Cause: you specified an invalid object type
Action: use a valid framework object
DRG-10704: preference string does not have an attribute named string
Cause: you tried to set value for a invalid attribute (not supported by the object.
Action: specify the correct attribute name
DRG-10705: invalid value string for attribute string
Cause: you tried to set an illegal value for an attribute
Action: specify the correct attribute value for the datatype of the attribute
DRG-10706: length of string exceeds maximum size of string
Cause: Parameter is too many bytes
Action: Correct preference setting and resubmit
DRG-10707: a value is required for attribute string of preference string
Cause: A required attribute was not provided
Action: Correct preference setting and resubmit
DRG-10708: invalid class id string for preference string
Cause: the specified class id is not correct for the specified preference
Action: specify the correct class id
DRG-10709: this preference is referenced by string and cannot be dropped
Cause: the specified preference is used as part of another preference and cannot be
dropped until the referring preference is modified
Action: modify the referring preference
DRG-10710: Invalid value string for string attribute
Cause: Invalid value provided for save_copy attribute It should be one of these:
(PLAINTEXT, FILTERED, NONE)
Action: Provide correct SAVE_COPY attribute value
24-8 Error Messages
DRG-10711: Invalid value for SAVE_COPY attribute: string

Cause: Invalid value provided for SAVE_COPY attribute. It should be a boolean value
Action: Provide boolean value for SAVE_COPY attribute
DRG-10712: preference string already has value for an attribute named string
Cause: Cannot call set_sec_grp_attr for an attribute whose value is already set in a
preference
Action: Call add_sec_grp_attr_val to add an additional value for attribute
DRG-10713: preference string does not have any value for attribute named string
Cause: Cannot call add_sec_grp_attr_val for an attribute without calling
set_sec_grp_attr for the same attribute
Action: Call set_sec_grp_attr to set value for attribute and then call
add_sec_grp_attr_val to add an additional value for attribute
DRG-10714: cannot add or remove value for attribute named string
Cause: Cannot call add_sec_grp_attr_val or rem_sec_grp_attr_val for a boolean
attribute
Action: Do not call add_set_grp_attr_val or rem_sec_grp_attr_val for a boolean
attribute. Use set_sec_grp_attr and unset_sec_grp_attr instead.
DRG-10715: preference string has incompatible values for string and string
Cause: Cannot set related attributes to incompatible values
Action: Set or add a compatible value for related attributes
DRG-10716: invalid prefix_ns_mapping attribute value string
Cause: Value of prefix_ns_mapping is neither of the form xmlns:pfx="ns" nor of the
form xmlns="ns"
Action: Call rem_sec_grp_attr_val to remove this prefix_ns_mapping attribute value.
DRG-10750: unknown parameter string
Cause: Unrecognized parameter
Action: Specify correct parameter
DRG-10751: invalid value for parameter
Cause: Wrong data type or out of range
Action: Specify correct parameter value
DRG-10752: DEFAULT_INDEX_MEMORY cannot be greater than
MAX_INDEX_MEMORY
Cause: You tried to set DEFAULT_INDEX_MEMORY to a value higher than the
maximum set in MAX_INDEX_MEMORY
Action: Specify a lower value
DRG-10753: invalid size (in bytes) string string
Cause: You specified an incorrectly formatted size string
Action: Specify a correctly formatted size string
DRG-10754: Size (in bytes) must be between string and string
Cause: You specified size (in bytes) which is outside the allowed range
Action: Specify size (in bytes) within the allowed range
DRG-10000 to DRG-52403 24-9
DRG-10755: string and string have characters in common

Cause: the join character sets cannot have characters in common
Action: Correct the attribute values and resubmit
DRG-10756: neither text indexing nor theme indexing has been selected
Cause: INDEX_TEXT and INDEX_THEMES preferences both cannot be FALSE.
Action: Set either of INDEX_TEXT or INDEX_THEMES or both to TRUE.
DRG-10757: stoplist cannot have more than 4096 stopwords
Cause: a stoplist cannot have more than 4096 stopwords. This includes stopthemes.
Action: none required
DRG-10758: index owner does not have the privilege to use file or URL datastore
Cause: index owner does not have the role defined in FILE_ACCESS_ROLE
Action: grant index owner the appropriate role
DRG-10759: invalid role
Cause: the role does not exist in the database
Action: check the role name or create the role
DRG-10760: illegal format for procedure name
Cause: the procedure name specified is invalid. For instance, it may have a semicolon
Action: check the procedure name
DRG-10761: procedure string does not exist
Cause: the specified procedure could not be found
Action: check input. Try a fully-specified format such as OWNER.OBJECT
DRG-10762: index owner does not have access to procedure string
Cause: the index owner does not have execute privilege on the specified procedure
Action: grant index owner execute permission on the procedure
DRG-10763: value string is not a valid character set
Cause: the value specified for the filename_charset attribute of the file datastore is not
a valid character set name
Action: specify a valid Oracle character set name
DRG-10764: only SYS can modify FILE_ACCESS_ROLE
Cause: For security reasons, only SYS can modify the FILE_ACCESS_ROLE system
parameter
Action: Connect as SYS before modifying the parameter
DRG-10765: stoplist cannot have more than 250 stopclasses with stoppatterns
Cause: a stoplist cannot have more than 250 stopclasses with stoppatterns. This does
not include NUMBERS stopclass.
Action: none required
DRG-10800: query failed: string string string
Cause: Failed to process the query
Action: Check the errors on stack and take appropriate action
DRG-10801: cannot create an SQE for another user

Cause: You tried to create an SQE for another user
Action: Remove owner from SQE name specification
DRG-10816: display/highlight call failed
Cause: See the next error on the stack.
Action: See the next error on the stack.
DRG-10817: CONTAINS term consists of stopword or phrase of stopwords: string
Cause: One or more terms within a CONTAINS query consist of just a stopword or a
phrase of just stopwords
Action: Replace the stopword or use stopwords within phrases containing nonstopwords.
DRG-10819: could not open contains cursor
Cause: An error occurred while trying to open a contains cursor
Action: See accompanying error messages in the stack
DRG-10820: invalid contains cursor id
Cause: You tried to fetch or close a contains cursor with an id which does not exist.
Action: Review fetch or close invocation
DRG-10821: contains cursor is not open
Cause: You tried to fetch from a contains cursor which was not open.
Action: Open cursor first
DRG-10822: duplicate query name
Cause: You tried to create a stored query with a name already used.
Action: Use different name
DRG-10823: invalid query name
Cause: The query name specified is not valid
Action: Check the query name
DRG-10825: stored query does not exist: string
Cause: The specified stored query does not exist.
Action: Check the query name
DRG-10826: no document with the specified textkey is found
Cause: There is no document with the specified textkey.
Action: Check the textkey
DRG-10827: open_con must be performed before count_last
Cause: last_count returns hit from in-memory query,so an in-memory query must be
run before you can use count_last
Action: execute open_con before run count_last
DRG-10828: token string is longer than maximum length for column string
Cause: A token to be inserted in the feedback table is longer than the maximum
allowed column size.
DRG-10000 to DRG-52403 24-11
Action: Modify the query, or the column size for feedback table, or feedback
procedure arguments accordingly.
DRG-10829: feedback id string is longer than the maximum length of string bytes
Cause: Feedback id is longer than the maximum allowed length for the feedback_id
column.
Action: Use a smaller feedback_id.
DRG-10830: SHARELEVEL is not 0 or 1
Cause: You specified a sharelevel which is not 0 or 1
Action: Use sharelevel equal to 0 or 1 only.
DRG-10831: can not insert into feedback table string
Cause: Not privileged to insert.
Action: Check privileges.
DRG-10832: can not delete from feedback table string
Cause: Not privileged to delete.
Action: Check privileges.
DRG-10833: feedback failed
Cause: Failed to process feedback request
Action: Check the errors on stack and take appropriate action
DRG-10834: upper-case form of section name string too long
Cause: upper-case form of the section name is longer then supported length
Action: reduce length of section name when adding section
DRG-10835: WITHIN operator not supported for theme index
Cause: WITHIN operator used in theme index query
Action: Rewrite query without WITHIN operator
DRG-10836: field section and attribute section can not be nested
Cause: A field section or a attribute section is specified in a nested section search
Action: Rewrite query without nested field sections
DRG-10837: section string does not exist
Cause: The given section name does not exist in USER_SECTIONS
Action: Rewrite query with valid section name
DRG-10838: invalid SPAN argument supplied to NEAR
Cause: An invalid value was supplied for SPAN argument to NEAR
Action: Provide a valid SPAN. Valid values are integers from 0 to 100.
DRG-10839: invalid ORDER argument supplied to NEAR
Cause: An invalid value was supplied for ORDER argument to NEAR
Action: Provide a valid ORDER. Valid values are T, TRUE, F, FALSE (case
insensitive).
DRG-10840: CONTAINS predicate including 0 is not supported by FIRST_ROWS

hint
Cause: User attempts to issue a query with CONTAINS predicate including 0 while
giving FIRST_ROWS hint.
Action: remove FIRST_ROWS hint.
DRG-10841: invalid SCORE argument supplied to FUZZY
Cause: An invalid value was supplied for SCORE argument to FUZZY
Action: Provide a valid SCORE. Valid values are integers from 1 to 80.
DRG-10842: invalid NUMRESULTS argument supplied to FUZZY
Cause: An invalid value was supplied for NUMRESULTS argument to FUZZY
Action: Provide a valid NUMRESULTS. Valid values are integers from 0 to 5000.
DRG-10843: invalid WEIGHT argument supplied to FUZZY
Cause: An invalid value was supplied for WEIGHT argument to FUZZY
Action: Set WEIGHT to WEIGHT or NOWEIGHT.
DRG-10844: index cannot execute this structured predicate efficiently
Cause: You specified a combination of condition and order by columns in a catsearch
query which cannot be executed by the index's index set efficiently
Action: n/a
DRG-10845: column string is not indexed
Cause: You specified a column in a condition or order by which is not part of the
ctxcat index
Action: n/a
DRG-10846: order by columns must be all ascending or all descending
Cause: You specified an order by clause which has some columns ascending and
some descending. This is not currently supported by catsearch
Action: n/a
DRG-10847: catsearch requires prefix index for this type of query
Cause: For efficient execution of this Vgram query, we require presence of a prefix
index.
Action: create a prefix index
DRG-10848: invalid structured clause
Cause: you have specified an invalid structured clause
Action: n/a
DRG-10849: catsearch does not support functional invocation
Cause: the query plan for your query is invoking a catsearch operator functionally
rather than as an index rowsource. The catsearch operator does not support
functional invocation
Action: add optimizer hints so that all catsearch operators are performed through
index scans
DRG-10000 to DRG-52403 24-13
DRG-10850: CTXRULE indextype does not support the operator

Cause: Used an operator not supported by CTXRULE. Currently it only supports
AND, NEAR, phrase, NOT, WITHIN, OR, ABOUT, EQUIVALENCE, STEM and
THESAURUS operators
Action: Rewrite query without this operator
DRG-10851: Invalid grammar string specified for query template
Cause: incorrect grammar specification
Action: Rewrite query specifying valid grammar name
DRG-10852: Invalid scoring type string specified for query template
Cause: incorrect scoring type specification
Action: Rewrite query specifying valid scoring type (integer/float)
DRG-10853: Catsearch does not support this operator
Cause: unsupported operator specified
Action: Rewrite query using valid operators
DRG-10854: Invalid scoring algorithm string specified for query template
Cause: incorrect scoring algorithm specification
Action: Rewrite query specifying valid scoring algorithm (default/count)
DRG-10855: CTXRULE indextype does not support the token type
Cause: Unsupported VGRAM token type 1.
Action: n/a
DRG-10856: SDATA section string does not exist
Cause: The given SDATA section name does not exist in USER_SECTIONS
Action: Rewrite query with valid SDATA section name
DRG-10857: literal is not compatible with the data type of the SDATA section
Cause: The given literal is not compatible with the data type of the specified SDATA
section.
Action: Rewrite query with a compatible literal
DRG-10858: SDATA operator is not allowed in WITHIN
Cause: A field section or a attribute section is specified in a nested section search
Action: Rewrite query without nested field sections
DRG-10859: Only one predefined scoring component can be used in
DEFINESCORE
Cause: More than one predefined scoring component (i.e. RELEVANCE,
OCCURRENCE, etc.) is used in the scoring expression of the DEFINESCORE operator
Action: Rewrite query using only one predefined component
DRG-10860: All expressions under the same WITHIN must use the same
predefined scoring component
Cause: The query side of the same within mixes different types of scoring
components(i.e. RELEVANCE, OCCURRENCE, etc.)
Action: Rewrite query using only one type of predefined component
DRG-10861: COMPLETION score must be used with WITHIN operator

Cause: The completion score is used without using the WITHIN operator
Action: Rewrite query to include a within operator
DRG-10862: string attribute cannot be used with CTXRULE indexes
Cause: Used an attribute not supported by CTXRULE. This restriction is due to lack of
wildcard support for CTXRULE indexes.
Action: Rewrite query without this attribute
DRG-10863: invalid ORDER argument supplied to NDATA
Cause: An invalid value was supplied for ORDER argument to NDATA
Action: Set ORDER to ORDER or NOORDER.
DRG-10864: invalid PROXIMITY argument supplied to NDATA
Cause: An invalid value was supplied for PROXIMITY argument to NDATA
Action: Set PROXIMITY to PROXIMITY or NOPROXIMITY.
DRG-10865: invalid datatype in user scoring expression
Cause: The scoring expression specified in DEFINESCORE or
NORMALIZATION_EXPR in the query template either contains components with
unsupported datatypes or does not return numerical values.
Action: Rewrite the scoring expression.
DRG-10866: The right hand operand of MINUS cannot use IGNORE score
Cause: The IGNORE score is used as the right hand operand of MINUS
DRG-10867: OCCURRENCE and COMPLETION score cannot be used with
ABOUT in DEFINESCORE
Cause: The OCCURRENCE and COMPLETION score cannot be used with ABOUT
queries
DRG-10868: matches does not support functional invocation
Cause: the query plan for your query is invoking a matches operator functionally
rather than as an index rowsource. The matches operator does not support functional
invocation
Action: add optimizer hints so that all matches operators are performed through
index scans
DRG-10869: Invalid span supplied to NEAR2 operator
Cause: Near2 span must be between 0 and 100
Action: Use acceptable span
DRG-10870: Invalid weight supplied to NEAR2 operator
Cause: Near2 weights must be between 0 and 10
Action: Use acceptable weight
DRG-10871: NDATA operator not supported with string
Cause: NDATA operator is not supported in the specified operation
Action: Rewrite the query without NDATA operator
DRG-10000 to DRG-52403 24-15
DRG-10872: Characters cannot be outside string in an XML query

Cause: Charaters outside query element are not valid
Action: Write the characters inside querytextquery
DRG-10873: Invalid characters location in the XML query
Cause: Charaters between certain elements are not allowed
Action: Write the characters in designed places
DRG-10874: Syntax error in XML Query Template
Cause: XML template is wrong. Possible causes include missing closing tag or
receiving invalid attributes or characters.
Action: Check that the query is valid XML
DRG-10875: Missing closing tag in XML Query
Cause: Some tag has been opened and not closed properly.
Action: Close all tags properly
DRG-10876: Invalid ordering of elements in XML Query
Cause: Occurrence of some element that should be only between another element that
was not found
Action: Check the proper ordering of elements
DRG-10877: query should always start an XML Query
Cause: Either query is missing or is wrongly possitioned
Action: Insert query properly
DRG-10878: Invalid ordering in XML Query: string should be string of string
Cause: Invalid ordering of tags as of specs
Action: Rewrite query properly
DRG-10879: Invalid string element repetition in XML Query
Cause: Invalid repetition of XML element
Action: Rewrite query, merging both repeated elements
DRG-10880: Invalid nesting of string in XML Query
Cause: Invalid nesting of same element has been encountered
Action: Either close element properly or avoid nesting
DRG-10881: Invalid setting of savescore in ctxfiltercache
Cause: savescore argument must be true or false
Action: set savescore to true or false
DRG-10882: Invalid setting of topn in ctxfiltercache
Cause: topn argument must be true or false
Action: set topn to true or false
DRG-10883: savescore must be true to use topn in ctxfiltercache
Cause: savescore must be true to use topn in ctxfiltercache
Action: set savescore to true to use topn processing
DRG-10884: invalid use of ctxfiltercache with topn

Cause: ctxfiltercache with topn must be child of AND, THRESHOLD, or WEIGHT
operators
Action: invalid query
DRG-10885: ctxfiltercache operator requires non-zero query_filter_cache_size
Cause: used ctxfiltercache operator with zero query_filter_cache_size
Action: Set a non-zero query_filter_cache_size
DRG-10886: topn must be used with order by score desc in ctxfiltercache
Cause: must order query results by score desc when topn argument is true
Action: Add order by score desc and use oracle hint DOMAIN_INDEX_SORT
DRG-10887: Query cannot be processed, index partition is set to non-readable
mode
Cause: Index partition has been set to non-readable mode
Action: Use 'alter index modify pratition' to set read mode to TRUE
DRG-10891: invalid MINREQD argument supplied to NEAR
Cause: An invalid value was supplied for MINREQD argument to NEAR
Action: Provide a valid MINREQD. Valid values are integers from 0 to 63.
DRG-10900: out of memory
Cause: can not allocate more memory
Action: Contact your system adminstrator
DRG-11000: invalid keyword string
Cause: A keyword was invalid.
Action: Respecify the parameter string with correct keyword
DRG-11001: missing keyword when expecting one of string
Cause: A keyword was missing.
Action: Respecify the parameter string with keyword
DRG-11002: missing value for string
Cause: A value for the argument was missing.
Action: Respecify the parameter string with value
DRG-11003: invalid value string for string
Cause: An invalid value was given for the argument
Action: Specify a valid value
DRG-11004: duplicate or conflicting value for string
Cause: More than one value has been specified for the argument
Action: Check parameter string and correct the problem parameter
DRG-11005: invalid create index parameter string
Cause: the supplied parameter string is not correct
Action: drop index and recreate index with correct parameters
DRG-10000 to DRG-52403 24-17
DRG-11006: invalid alter index parameter string

Cause: The parameter string was invalid.
Action: Reissue the statement with the correct parameter string.
DRG-11007: multiple stopwords specified
Cause: Tried to add more than one stopword
Action: Specify one stopword at a time
DRG-11008: invalid create index partition parameter string
Cause: The parameter string was invalid
Action: drop index and recreate index with correct parameters
DRG-11100: unable to connect to the database
Cause: failed to connect to Oracle database
Action: check the Oracle error and connect string
DRG-11101: failed to open file string
Cause: failed to open a file
Action: check whether the file exist or access permission available
DRG-11102: assigned lexer can not operate on string language setting
Cause: Single byte lexer selected in multibyte language setting
Action: check RDBMS language setting or text columns lexer setting
DRG-11104: Oracle Text error:
Cause: See the next error on stack
Action: See the next error on stack
DRG-11106: user database session has terminated during this operation
Cause: this database session does not exist or has terminated
Action: determine why the user database session terminated while the operation was
still being carried out.
DRG-11107: invalid path specification: string
Cause: the path specified is not valid
Action: check the path specification
DRG-11108: invalid filename specified: string
Cause: the filename specified is not valid
Action: check the filename for beginning or trailing spaces, invalid characters, or
other such problems.
DRG-11109: assigned lexer does not support string query operator
Cause: This lexer does not support this query operator
Action: do not use the operator in your query
DRG-11111: value of string must be between string and string
Cause: You specified a value for the parameter which is out of range
Action: Specify a value which is in the allowed range
DRG-11112: length of string exceeds maximum of string

Cause: You specified a value for the parameter which is too long
Action: Specify a value which is less than or equal to the maximum length
DRG-11113: value of string must be one of string
Cause: You specified a value for the parameter which is invalid
Action: Specify a valid value for the parameter
DRG-11114: result table format is not correct for this operation
Cause: You specified a result table which has the wrong number, type, or names of
columns for this operation.
Action: Check result table. Refer to the documentation for the correct format for each
operation
DRG-11115: a value for string must be specified
Cause: You did not specify a value for the parameter
Action: Specify a value for the parameter
DRG-11116: value of string must be less than or equal to value of string
Cause: You specified values for the two parameters which are invalid
Action: Specify valid values for the parameters
DRG-11117: name is already used by an existing object
Cause: You tried to create an object whose name conflicts with an object of that type
which already exists
Action: Specify a new name
DRG-11118: object string does not exist
Cause: You tried to modify or drop an object which does not exist
Action: Specify correct object name
DRG-11119: operation is not supported by this index type
Cause: You tried to invoke an operation on an index which is not supported by the
index type
Action: n/a
DRG-11120: failed to write to file string
Cause: failed to write to a file
DRG-11121: failed to read from file string
Cause: failed to read from a file
DRG-11122: unsupported section group
Cause: unsupported section group is specified for functional contains
Action: change the section group to NULL_SECTION_GROUP
DRG-11123: theme indexing is not supported
Cause: theme indexing is on in the lexer preference for functional contains
DRG-10000 to DRG-52403 24-19
Action: turn off theme indexing

DRG-11124: invalid value string
Cause: you specified an invalid value
Action: specify a valid value
DRG-11125: invalid format of existing log file string
Cause: the file specified by START_LOG already exists, and is not a previously
written log file
Action: specify a new file, or remove the existing file
DRG-11126: context index is empty
Cause: the training table is empty or the context index of training table is not
populated
Action: populate the training table or context index
DRG-11127: inconsistent index policy with trained rule
Cause: the ctxrule index policy is inconsistent with the policy in which the rule was
trained
Action: change the ctxrule index policy
DRG-11128: invalid format of rule
Cause: the rule format is not valid for this operation
Action: check the rule type and operation type
DRG-11129: the rule table is empty
Cause: the rule table is empty
Action: populate the rule table by training
DRG-11130: no data found in the collection
Cause: feature preparation program can not find any feature in the specified
collection
Action: check the setting for extracting features.
DRG-11131: Error from Oracle XML parser: string
Cause: The Oracle XML parser reported an error
Action: Check the document for the error, and fix if necessary
DRG-11132: Invalid character in logfile name
Cause: The logfile parameter to CTX_OUTPUT.START_LOG or
CTX_OUTPUT.START_QUERY_LOG contains an invalid character (such as a
forward slash)
Action: Remove the invalid character
DRG-11133: failed to convert a datatime value [ora-number]
Cause: Failed to convert the datetime value.
Action: Check the error code
DRG-11134: The file string is currenly being used for logging by another process
Cause: The file is currently being used by another process.
Action: Give a different file name.
DRG-11135: feature not generally available

Cause: You tried to use a feature not generally available.
Action: Contact customer support
DRG-11136: assigned lexer does not support entity extraction
Cause: This lexer does not support entity extraction
Action: Do not use this lexer for entity extraction
DRG-11137: tracing is not supported on MTS
Cause: you tried to use ctx_output tracing in an MTS session
Action: connect using a dedicated session and retry the operation
DRG-11138: trace string is already enabled
Cause: you tried to enable a trace that is already enabled
Action: disable the trace first
DRG-11139: trace string is not enabled
Cause: you tried to disable a trace that is not enabled
Action: enable the trace first
DRG-11140: Section string is not MDATA
Cause: you tried to perform MDATA operation on non-mdata section
Action: provide correct mdata section name
DRG-11141: CTX_DDL.REMOVE_MDATA() and CTX_DDL.ADD_MDATA() not
allowed for MDATA Section string
Cause: you tried to call CTX_DDL.REMOVE_MDATA() or
CTX_DDL.ADD_MDATA() on a MDATA section which is created with
ALLOW_ADD_REM parameter set to FALSE.
Action: do not call CTX_DDL.REMOVE_MDATA() or CTX_DDL.ADD_MDATA() on
a MDATA section that is created with ALLOW_ADD_REM parameter set to FALSE.
DRG-11142: string cannot be string
Cause: The value for the specified parameter cannot be as specified
Action: Specify the correct value
DRG-11143: Only 64 errors can be traced
Cause: You tried to trace more than 64 errors with ctx_output
Action: Trace fewer errors, or use DRG_DUMP_ALL_ERRORS
DRG-11144: Invalid value for radius parameter: string
Cause: You specified invalid value for radius parameter
Action: Provide non-negative/non-decimal value for radius parameter
DRG-11145: Invalid value for max_length parameter: string
Cause: You specified invalid value for max_length parameter
Action: Provide non-negative/non-decimal value for max_length parameter
DRG-11146: Invalid value for use_saved_copy: string
Cause: You specified invalid value for use_saved_copy parameter
DRG-10000 to DRG-52403 24-21
Action: Use one of these: SAVE_COPY_FALLBACK / SAVE_COPY_ERROR /

SAVE_COPY_IGNORE
DRG-11147: Invalid lexer for ctx_doc.policy_stems
Cause: You specified/used a lexer which does not support ctx_doc.policy_stems
Action: Use auto lexer for ctx_doc.policy_stems
DRG-11148: Invalid lexer for ctx_doc.policy_noun_phrases
Cause: You specified/used a lexer which does not support
ctx_doc.policy_noun_phrases
Action: Use auto lexer for ctx_doc.policy_noun_phrases
DRG-11149: Invalid lexer for ctx_doc.policy_part_of_speech
Cause: You specified/used a lexer which does not support
ctx_doc.policy_part_of_speech
Action: Use auto lexer for ctx_doc.policy_part_of_speech
DRG-11150: Reverse Index feature not enabled
Cause: Feature not enabled
Action: Enable Reverse Index feature
DRG-11203: INSO filter not supported on this platform
Cause: You tried to use the INSO filter on a platform which does not support it
Action: Do not use the INSO filter
DRG-11204: user filter command is too long
Cause: The user filter command must be 32 characters or less
Action: Specify a shorted user filter command
DRG-11205: user filter command contains illegal characters
Cause: The user filter command cannot contain special characters such as slashes,
parentheses, semicolons, etc.
Action: Correct command specification
DRG-11206: user filter command string could not be executed
Cause: The user filter command could not be executed.
Action: Check that the command exists in $ORACLE_HOME/ctx/bin, and that it is
executable.
DRG-11207: user filter command exited with status string
Cause: The user filter command exited with the given error status.
Action: See any DRG-11220, DRG-11221, DRG-11222, DRG-11223, DRG-11224,
DRG-11225, or DRG-11227 error message on the error stack otherwise see error status.
DRG-11208: ORACLE_HOME is not set
Cause: ORACLE_HOME is not set
Action: make sure ORACLE_HOME is set when running ctxsrv
DRG-11209: filename for string exceeds maximum length of string
Cause: Value of the file name is too long
Action: Specify a shorter filename
DRG-11210: format column must be a char, varchar, or varchar2 type

Cause: you specified a format column which is not a char, varchar, or varchar2 type.
Action: specify a format column of correct type
DRG-11211: charset column must be a char, varchar, or varchar2 type
Cause: you specified a charset column which is not a char, varchar, or varchar2 type.
Action: specify a charset column of correct type
DRG-11212: procedure filter procedure name contains a semicolon
Cause: the procedure name specified had a semicolon
Action: remove semicolon or rename procedure name. The correct format is
PACKAGENAME.PROCEDURE_NAME
DRG-11213: CTXSYS does not own procedure filter stored procedure: string
Cause: CTXSYS does not have execute privilege to the procedure filter stored
procedure
Action: make sure the package is owned by CTXSYS and the procedure exist
DRG-11214: execution of procedure filter stored procedure has failed
Cause: an error occur while executing the proedure filter stored procedure
Action: check or debug the stored procedure
DRG-11215: index owner does not have access to filter stored procedure: string
Cause: the index owner does not have execute privilege of the procedure
Action: CTXSYS to grant execute privilege of the procedure to index owner
DRG-11216: length of datastore data exceeds limit
Cause: the length of the datastore data passed to the filter stored procedure is longer
than the maximum length (32767 bytes)
Action: check primary key parameter
DRG-11217: INSO safe callout failed
Cause: The INSO safe callout cannot be executed
Action: check the Oracle errpr
DRG-11218: malformed mail line, line string
Cause: The mail message has an error at the indicated line
Action: manually edit mail message, if possible
DRG-11219: malformed mail configuration file, line string
Cause: mail filter configuration file has an error at the indicated line
Action: manually edit mail filter configuration file, if possible
DRG-11220: Third-party filter is out of memory.
Cause: Third-party filter could not filter this document because it was unable to
allocate sufficient virtual memory.
Action: Increase virtual memory provided by the Operating System and reindex this
document.
DRG-10000 to DRG-52403 24-23
DRG-11221: Third-party filter indicates this document is corrupted.

Cause: Third-party filter could not filter this document because this document is
corrupted.
Action: Fix the corruption and reindex this document.
DRG-11222: Third-party filter does not support this known document format.
Cause: Third-party filter was able to recognize the format of this document but could
not filter it because this format is not supported.
Action: Remove this document or specify it to be ignored.
DRG-11223: Third-party filter indicates this document is password protected or
encrypted.
Cause: Third-party filter encountered a password protected or encrypted document
and could not filter it because this level of password protection or encryption is not
supported.
DRG-11224: Third-party filter is unable to create or write to temporary file.
Cause: Third-party filter could not filter this document because it was unable to create
a temporary file or unable to write to a temporary file.
Action: Make sure that the Operating System specified temporary directory has
enough space and that the Operating System Oracle user has the privileges to create
files in this temporary directory.
DRG-11225: Third-party filter timed out.
Cause: Third-party filter could not filter this document because the filter timed out.
Action: Increase the value of the TIMEOUT attribute of INSO_FILTER filter type and
reindex this document. When TIMEOUT attribute is set to 0 and the session hangs
then contact Oracle Support.
DRG-11226: Error initializing third-party filter: string
Cause: There was an error initializing the third-party filter.
Action: Check the following messages for details
DRG-11227: Third-party filter does not support this document format.
Cause: Third-party filter does not support the format of this document.
DRG-11228: Charset filter does not support binary documents.
Cause: The format column specifies a binary document
Action: Do not attempt to filter binary documents using the charset filter
DRG-11229: configuration column must be a char, varchar, or varchar2 type
Cause: you specified a configuration column which is not a char, varchar, or varchar2
type.
Action: specify a configuration column of correct type
DRG-11301: error while indexing document
Cause: An error was encountered while indexing the document. The error may have
occurred during lexing, parsing for sections, or other action during document
tokenization
Action: review document and update with valid data. Note that the document
contents may have been partially indexed, so it may be returned by some queries.
DRG-11303: secondary indexes are not supported by this indextype
Cause: You attempted to create an index on an index-organized table, but the
indextype does not support this action.
Action: n/a
DRG-11304: function-based indexes are not supported by this indextype
Cause: You attempted to create a function-based index but the indextype does not
support this action.
Action: n/a
DRG-11305: create/alter index string is in progress in another session
Cause: you attempted to mark the index from INPROGRESS to FAILURE but create/
alter on the same index is in progress in another session
Action: n/a
DRG-11306: operation cannot be performed on a policy
Cause: you attempted to perform an operation on a policy, but the operation is only
valid for an index.
Action: n/a
DRG-11307: operation cannot be performed on an index
Cause: you attempted to perform an operation on an index, but the operation is only
valid for a policy.
Action: n/a
DRG-11308: unsupported column expression string
Cause: You attempted to create an index with an unsupported column expression.
Action: n/a
DRG-11309: invalid filter by column: string
Action: check that the followings are valid: a) column is of supported datatype b)
DRG-11310: invalid order by column: string
Action: check that the followings are valid: a) column is of supported datatype b)
DRG-11311: string cannot be specified for this optimization mode
Cause: the specified option is not valid for this optimization mode
Action: remove the specified option
DRG-11312: source and new policy must have same owner
Cause: the new policy has a different owner than the source policy
Action: Ensure that both policies are owned by the same user
DRG-10000 to DRG-52403 24-25
DRG-11313: populate index error on index partition string

Cause: failed to polulate the text index on the specified partition
DRG-11314: changing TRANSACTIONAL property on index with rows on
pending queue not allowed
Cause: the index has pending unsynced rows
Action: sync the index before changing the TRANSACTIONAL property
DRG-11316: $S table cannot be created with string
Cause: the $S table cannot be created with the specified storage option
Action: remove the specified option from the index preference and retry the index
creation
DRG-11317: rowid string is not in the index
Cause: you specified an invalid rowid in ctx_ddl.add_mdata
Action: correct the rowid and retry
DRG-11318: error processing dr$sdata_update
Cause: there was an error
Action: check the error stack for more details
DRG-11319: more than 1 index found on $I. OPTIMIZE REBUILD not supported
Cause: OPTIMIZE REBUILD is not supported due to the specified reason
Action: resolve the issue, and retry the operation
DRG-11320: no index found on $I. OPTIMIZE REBUILD not supported
DRG-11321: triggers detected on $I. OPTIMIZE REBUILD not supported
DRG-11322: fast optimize not supported for big_io option
Cause: OPTIMIZE FAST is not supported with big_io option
Action: run optimize full or rebuild instead
DRG-11323: merge optimize requires near_realtime option
Cause: OPTIMIZE MERGE requires near_realtime option
Action: run another optimize mode
DRG-11324: fast optimize not supported for separate_offsets option
Cause: OPTIMIZE FAST is not supported with separate_offsets option
Action: run optimize full or rebuild instead
DRG-11325: stageitab only supported for context index
Cause: STAGEITAB requires context index
Action: don't use stageitab on non context indexes
DRG-11326: separate offsets only supported for context index

Cause: SEPARATE_OFFSETS requires context index
Action: don't use separate_offsets on non context indexes
DRG-11327: big_io only supported for context index
Cause: BIG_IO requires context index
Action: don't use big_io on non context indexes
DRG-11328: optimize validation failed
Cause: optimize validation failed
Action: file a bug
DRG-11332: Index already has STAGE_ITAB set
Cause: Index already has stage_itab set
Action: Do not add stage_itab to this index
DRG-11333: Index does not have STAGE_ITAB set
Cause: Index does not have stage_itab set
Action: Do not remove stage_itab from this index
DRG-11334: Index already has BIG_IO set
Cause: Index already has big_io set
Action: Do not add big_io to this index
DRG-11335: Index does not have BIG_IO set
Cause: Index does not have big_io set
Action: Do not remove big_io from this index
DRG-11336: Index already has SEPARATE_OFFSETS set
Cause: Index already has separate_offsets set
Action: Do not add separate_offsets to this index
DRG-11337: Index does not have SEPARATE_OFFSETS set
Cause: Index does not have separate_offsets set
Action: Do not remove separate_offsets from this index
DRG-11338: policy string does not exist
Cause: the specified policy does not exist or you do not have access to it.
Action: Specify an existing index
DRG-11339: $A table cannot be created with string
Cause: the $A table cannot be created with the specified storage option
creation
DRG-11340: $F table cannot be created with string
Cause: the $F table cannot be created with the specified storage option
creation
DRG-10000 to DRG-52403 24-27
DRG-11341: Index optimization failed for one or more tokens

Cause: Index optimization generated an error for one or more tokens, possibly due to
corruption of the token_info blob.
Action: Check the index optimization log for the detailed error, or retry the optimize
call with logging enabled
DRG-11342: OPTIMIZE REBUILD not supported for partitioned $I and global $X
DRG-11343: OPTIMIZE REBUILD not supported for current $I partitioning scheme
DRG-11344: SPLIT DOLLARI does not allow an empty mapping table input
Cause: SPLIT DOLLARI doesn't generate any output for empty mapping table
Action: populate the mapping table, and retry the operation
DRG-11345: Index optimization was interrupted
Cause: Index optimization was interrupted by ctx_adm.stop_optimize
Action: None
DRG-11346: FORWARD INDEX only supported for context index
Cause: FORWARD INDEX needs context index
Action: Don't use FORWARD INDEX on non context indexes
DRG-11347: FORWARD INDEX does not exist for this index
Cause: FORWARD INDEX does not exist
Action: Enable forward index for the index
DRG-11348: OPTIMIZE REBUILD not supported for $I with character length
semantics columns
DRG-11349: FILTER CACHE only supported for context index
Cause: FILTER CACHE only for context index
Action: Don't use FILTER_CACHE on non context indexes
DRG-11350: SAVE COPY only supported for context index
Cause: SAVE COPY needs context index
Action: Don't use SAVE COPY on non context indexes
DRG-11351: Unable to fetch partition Id for given rowid: string
Cause: Not able to fetch partition id for given rowid
Action: Make sure index tables are partitioned correctly.
DRG-11352: Not able to fetch partition name for given partition position: number
Cause: Not able to fetch partition name for given partition position
Action: Make sure valid parition position has been provided
DRG-11353: xml_enable is not allowed for a local index

Cause: Section group attribute xml_enable set to TRUE for a local index
Action: Set xml_enable to FALSE for a local index.
DRG-11354: stage_itab_target_size need to be set, if stage_itab storage preference is
set
Cause: Storage option stage_itab needs to be accompanied with
stage_target_max_size
Action: Add stage_target_max_size to storage preference
DRG-11355: Not able to fetch partition position from rowid: string
Cause: Not able to fetch partition position for given rowid
Action: Make sure valid rowid has been provided
DRG-11356: Optimize operations are not permitted on partition string
Cause: READ mode for this partition is set to FALSE. No optimize operations are
permitted in this mode.
Action: Set READ mode for this partition to be TRUE.
DRG-11357: FORWARD INDEX must be specified at index, not partition level
string
Cause: forward index was specified at partition level and not at index level
Action: Specify forward index option at index level. All partitions inherit.
DRG-11358: Save Copy must be specified at index, not partition level string
Cause: save copy was specified at partition level and not at index level
Action: Specify save copy option at index level. All partitions inherit.
DRG-11400: failed to parse document with key string
Cause: the document specified for linguistic extraction could not be parsed. This
could indicate that the document is not well-formed English
Action: check the document contents
DRG-11403: primary key value too long
Cause: the primary key value parameter passed to the service request is longer than
the maximum primary key length (64 bytes)
DRG-11404: no primary key value specified
Cause: the primary key value parameter passed to the service request is null
DRG-11410: could not insert into string result table
Cause: an ORACLE error occurred while linguistic output was being inserted into the
result table
Action: take action appropriate to the ORACLE error code.
DRG-11418: insufficient document content for linguistic parser
Cause: the document specified for linguistic extraction was parsed but the document
content was insufficient for linguistic extraction by the specified parser.
Action: check the document contents or try modifying linguistic settings
DRG-10000 to DRG-52403 24-29
DRG-11422: linguistic initialization failed

Cause: linguistic services initialization failed
Action: Check to see if knowledge base files present for the language
DRG-11425: gist level string is invalid
Cause: invalid gist level
Action: Specify a valid gist level
DRG-11427: valid gist level values are string
Cause: Invalid gist level
Action: Specify a valid gist level
DRG-11428: document contains invalid characters
Cause: The document contains invalid characters
Action: Remove invalid characters
DRG-11432: file error while accessing knowledge base
Cause: An oracle error was encountered during knowledge base access
Action: Check to see if knowledge base files present for the language
DRG-11435: primary key value is invalid
Cause: the primary key value parameter passed to the service request is not valid
DRG-11439: index name length exceeds maximum of string bytes
Cause: the length of the index name is longer than the maximum index name size
Action: drop the index and recreate the index with a shorter index name
DRG-11440: operation not supported for the string language
Cause: the requested operation is not supported for the current language
Action: Do not request this operation
DRG-11441: gist numParagraphs string is invalid
Cause: invalid gist numparagraphs
Action: Specify valid gist numparagraphs
DRG-11442: valid gist numParagraphs values are string
Cause: invalid gist numparagraphs
Action: Specify valid gist numparagraphs
DRG-11443: gist maxPercent string is invalid
Cause: invalid gist max percent
Action: Specify valid gist max percent
DRG-11444: valid gist maxPercent values are string
Cause: invalid gist max percent
Action: Specify valid gist max percent
DRG-11445: rowid value is invalid: string
Cause: the rowid value parameter passed to the service request is not valid
Action: check rowid parameter

DRG-11446: supplied knowledge base file string not installed
Cause: Either using Oracle Express edition or supplied Knowledge Base was required
but was not installed.
Action: If using Oracle Express edition then upgrade to Oracle Enterprise or Oracle
Standard edition. Otherwise see post-installation tasks section of the Database
Installation Guide for instructions to install supplied Knowledge Base.
DRG-11480: ctxkbtc memory allocation error: %(1)
Cause: Unable to allocate memory
Action: Contact your system administrator
DRG-11481: linguistic feature not enabled
Cause: linguistic feature not enabled
Action: enable linguistic feature
DRG-11500: column name expected, found string on line string
Cause: possibly miss-spelt column name or keyword
Action: check spellings and punctuation around specified line
DRG-11501: identifier string found in place of column name on line string
Cause: possibly miss-spelt column name
Action: check spellings around specified line
DRG-11502: read of file failed at line string for file string
Cause: bad file name, wrong file_type or file system error
Action: check file name, type and/or file integrity
DRG-11503: insert statement overflows maximum statement size
Cause: total length of statement exceeds database maximum
Action: reduce length of column names or number of columns
DRG-11504: invalid longsize parameter of string specified
Cause: invalid option argument
Action: specify long buffer size in kbytes above 0
DRG-11505: long data on line string not found or invalid
Cause: either bad data or bad data file
Action: check file exists and is accessible, if separate
DRG-11506: record ignored on line string because of error(s)
Cause: an error occured parsing this row's data
Action: move and amend line in error to alternate load file
DRG-11507: file error trying to read file string
Cause: file not found or could not be read
Action: check name and location of file
DRG-11508: bad or missing string token on line string
Cause: token expected was not found
DRG-10000 to DRG-52403 24-31
Action: move and amend record affected to error load file

DRG-11509: value expected on line string
Cause: could not make sense of text where value expected
Action: move and amend record affected to error load file
DRG-11510: encountered unrecoverable error on line string
Cause: see previous messages
Action: see previous errors
DRG-11511: specified table does not contain a LONG RAW column
Cause: text must be inserted into a LONG RAW type column
Action: check table and type of data
DRG-11512: bad syntax for thesaurus load file at line string
Cause: load file must have specific format for loading thesaurus
Action: check documentation for description of correct format
DRG-11513: unable to open or write to file string
Cause: an attempt to open or to write to the given file failed
Action: check with system administrator
DRG-11514: user string does not have UPDATE or SELECT privilege on string
Cause: user has not been granted UPDATE or SELECT privilege
Action: check privilege on the user
DRG-11515: not enough text key values
Cause: number of values provided does not match the number of text keys
Action: provide same number of values as the number of text keys
DRG-11516: user must be at least in role CTXUSER to perform this operation
Cause: user does not have CTXUSER, CXAPP or CTXADMIN role
Action: grant user the proper role
DRG-11517: error when validating text objects
Cause: see accompanying Oracle error
Action: see accompanying Oracle error
DRG-11518: text table string does not have a LONG or LONG RAW column
Cause: table specified does not have a LONG or LONG RAW column
Action: check the table
DRG-11519: encounter error when exporting a LONG or LONG RAW column
Cause: see accompanying error message
Action: see accompanying error message
DRG-11520: error writing to file
Cause: file does not exist
Action: make sure file exists
DRG-11521: encounter error when updating a LONG or LONG RAW column

Cause: see accompanying error message
Action: see accompanying error message
DRG-11522: no row exists for the text key(s) specified
Cause: no row in the table has the text key(s) specified
Action: use a valid text key(s)
DRG-11523: unable to lock the specified row for update
Cause: some other process has a lock on the row
Action: release the lock or wait until the lock is released
DRG-11524: primary key value is missing
Cause: primary key value is not provided
Action: provide the primary key value(s)
DRG-11525: invalid commitafter parameter of string specified
Cause: invalid option argument
Action: specify commitafter above 0
DRG-11526: filename exceeds maximum length
Cause: value of the file name is too long
Action: Specify a shorter file name
DRG-11527: end token not found on line string
Cause: TEXTEND not found at end of record
Action: processing discontinued - amend record
DRG-11528: LONG or LONG RAW column defintion found in structure data
Cause: could be misplaced
Action: remove reference to LONG or LONG RAW column from structure data
DRG-11529: token exceeds maximum length
Cause: value of the column name or value is too long
DRG-11530: token exceeds maximum length
Cause: value of the phrase or relation word is too long
DRG-11531: start token not found on line string
Cause: <TEXTSTART: not found at start of record
DRG-11532: error reading through end of line string for file string
Cause: characters encountered while reading through end of line
Action: remove extraneous characters
DRG-11533: improper value of column string
Cause: value of the column is too long or mismatched quote
DRG-10000 to DRG-52403 24-33

DRG-11534: invalid column string
Cause: column does not exist or it's misspelled
DRG-11535: error writing phrase or qualifier: string on line string to memory
Cause: not enough memory
Action: allocate more memory, contact WorldWide Support if problem persists
DRG-11600: URL store: string has permanently moved
Cause: the document referred to by the URL has permanently moved
Action: find the new address, if any, of the document
DRG-11601: URL store: bad syntax on request for string
Cause: client did not make correct request
Action: contact support
DRG-11602: URL store: access to string requires authentication
Cause: user has to provide password or other authentication
Action: get required access, or check URL
DRG-11603: URL store: payment required to access string
Cause: payment is required before the URL can be accessed
Action: check URL, or pay if required if access necessary
DRG-11604: URL store: access to string is denied
Cause: access to the URL is denied
Action: check URL; if correct, do not try to access URL again
DRG-11605: URL store: document specified by string not found
Cause: the document can not be found on the host specified
Action: check URL
DRG-11606: URL store: access to string timed out waiting for client request
Cause: client did not make response within timeout period
Action: check URL
DRG-11607: URL store: access to string was denied due to garbled response
Cause: Web server identified in URL doesn't obey HTTP protocol
Action: contact the Web administrator of the remote host
DRG-11608: URL store: host portion of string specified incorrectly
Cause: host portion of the URL could not be parsed
Action: check URL
DRG-11609: URL store: unable to open local file specified by string
Cause: attempt to open local file failed
Action: check URL
DRG-11610: URL store: unable to read local file specified by string

Cause: attempt to read local file failed
Action: contact system administrator
DRG-11611: URL store: unknown protocol specified in string
Cause: the protocol parsed is neither http or file
Action: check URL
DRG-11612: URL store: unknown host specified in string
Cause: the address of the host specified could not be resolved
Action: check URL
DRG-11613: URL store: connection refused to host specified by string
Cause: attempt to connect to host was forcibly refused
Action: check URL
DRG-11614: URL store: communication with host specified in string timed out
Cause: a network operation timed out
Action: try again later; network connection may be down to Web server
DRG-11615: URL store: write failed sending to string over network
Cause: unknown error writing request to Web server
Action: check network connection
DRG-11616: URL store: too many redirections trying to access string
Cause: too long a chain of HTTP redirections given the URL
Action: contact the Web administrator of the remote host
DRG-11617: URL store: URL string is too long
Cause: The length of the URL string is longer than URLSIZE
Action: set URLSIZE attribute to a larger value
DRG-11618: URL store: document identified by string is too large
Cause: document larger than user-set maximum size
Action: do not access URL, or increase document size limit
DRG-11619: URL store: row in table is empty
Cause: row deleted or otherwise missing
Action: check table if necessary
DRG-11620: URL store: thread operation error
Cause: thread operation failed
Action: contact system administrator
DRG-11621: URL store: socket open error for string
Cause: socket open failed; probably too many open file descriptors
Action: reduce the maximum number of threads started
DRG-11622: URL store: unknown HTTP error string getting string
Cause: an unexpected HTTP error has occurred
DRG-10000 to DRG-52403 24-35
Action: consult HTTP error codes; if valid, contact support

DRG-11623: URL store: unknown error getting string
Cause: unexpected error
DRG-11624: invalid attribute string for string: proper range string to string
Cause: unexpected error
Action: change attribute value
DRG-11625: MAXURLS * URLSIZE must be less than string
Cause: MAXURLS * URLSIZE cannot be larger than the limit
Action: Lower either MAXURLS or URLSIZE
DRG-11626: URL store: unknown protocol specified during redirect from string
Cause: the URL redirected to a site with neither http nor file protocol
Action: check URL
DRG-11627: URL store: not implemented error getting string
Cause: The remote host returned a 501 not implemented error
Action: Check URL
DRG-11628: URL store: bad gateway error getting string
Cause: The remote host returned a 502 bad gateway error
Action: Check URL
DRG-11629: URL store: service unavailable error getting string
Cause: The remote host returned a 503 service temporarily unavailable error
Action: Check URL
DRG-11630: URL store: gateway timeout error getting string
Cause: The remote host returned a 504 gateway timeout error
Action: Check URL
DRG-11700: thesaurus string already exists
Cause: thesaurus with same name exists
Action: use another name
DRG-11701: thesaurus string does not exist
Cause: thesaurus does not exist
Action: use another thesaurus or create it
DRG-11702: string
Cause: error while parsing thesaurus operator in query term. see error message for
details.
Action: see error message
DRG-11703: user string must have at least CTXAPP role to execute this function
Cause: privilege is not sufficient
Action: grant user CTXAPP role
DRG-11704: phrase 'string' does not exist

Cause: phrase does not exist
Action: use another phrase or create it
DRG-11705: multilevel jump from string to string
Cause: the thesaurus load file has a multilevel jump which could not be parsed.
Action: correct thesaurus file
DRG-11706: invalid relation string
Cause: You specified an invalid relation. The set of valid relations will be displayed.
Additionally, you may be able to specify a translation, which has the syntax
languagename: where languagename can be any string up to 10 bytes
Action: Specify a valid relation
DRG-11707: valid relations: string
Cause: You specified an invalid relation. The set of valid relations will be displayed.
Additionally, you may be able to specify a translation, which has the syntax
languagename: where languagename can be any string up to 10 bytes
Action: Specify a valid relation
DRG-11708: too many thesauri
Cause: ctxkbtc cannot compile more than 16 thesauri
Action: Specify fewer thesauri
DRG-11709: too many terms in thesaurus
Cause: number of thesaurus terms exceeds maximum
Action: Use a thesaurus with fewer terms
DRG-11710: thesaurus term string too long
Cause: knowledge base does not permit terms longer than 80 characters
Action: Correct thesaurus
DRG-11711: too much data for term string
Cause: internal limit on size of data per term
Action: redesign thesaurus
DRG-11712: multiple Broader Terms for term string
Cause: There is a term in the thesaurus with multiple broader terms
Action: make sure each term has only one broader term
DRG-11713: multiple Preferred Terms per synonym ring
Cause: There is a synonym ring in the thesaurus with multiple preferred terms
Action: make sure each synonym ring has only one preferred term
DRG-11714: synonyms have different Broader Terms
Cause: Some synonyms in a synonym ring have different broader terms
Action: make sure all synonyms have the same broader term
DRG-11715: attempt to add a BT relation between 2 KB categories string and string
Cause: BT relation cannot be between two existing knowledge base categories
DRG-10000 to DRG-52403 24-37
Action: redesign the BT hierarchy

DRG-11716: attempt to add Narrower Term string for non-Preferred Term string
Cause: only a PT can have NTs
Action: attach the NT to the preferred term
DRG-11717: attempt to add Related Term string to non-Preferred Term string
Cause: only a PT can have RTs
Action: attach the RT
DRG-11718: multiple Preferred Terms for term string
Cause: There are multiple preferred terms for this term
Action: Correct thesaurus
DRG-11719: Broader Term hierarchy too deep
Cause: The broader term hierarchy in this thesaurus is too deep
Action: flatten the hierarchy for best results
DRG-11720: too many synonyms per synonym ring
Cause: too many synonyms for a single preferred term
Action: introduce further distinctions to deepen the hierarchy
DRG-11721: thesaurus string is empty
Cause: no entries in thesaurus
Action: add some entries or drop the thesaurus
DRG-11722: invalid language specification
Cause: language specification cannot be more than 10 characters
Action: reduce language specification to less or equal to 10 char
DRG-11723: phrase cannot be NULL
Cause: you tried to add a NULL phrase to the thesaurus
Action: specify a valid phrase
DRG-11724: phrase string already exists
Cause: phrase with same name exists
DRG-11725: phrase does not have any synonyms
Cause: you tried to nominate a phrase with no synonyms to be the preferred term, or
you tried to drop SYN from a phrase with no synonyms
Action: None
DRG-11726: phrase is not a preferred term
Cause: you tried to remove the preferred term relation from a phrase which is not a
preferred term.
Action: None
DRG-11727: phrase does not have any related terms
Cause: you tried to drop a relation which does not exist
Action: None
DRG-11728: phrase does not have any broader terms of this type
Action: None
DRG-11729: phrase does not have any narrower terms of this type
Action: None
DRG-11730: relation does not exist
Action: None
DRG-11731: translation does not exist
Cause: you tried to drop a translation which does not exist
Action: None
DRG-11732: phrase does not have any translations
Cause: you tried to drop translations which does not exists
Action: None
DRG-11733: more than one translation for the term in the specified language
Cause: the term has more than one translation in the specified language
Action: specified a translation
DRG-11734: missing homograph
Cause: A term of the form 'homograph(disambiguation)' is missing the the
homograph.
Action: None
DRG-11735: missing disambiguation
Cause: A term of the form 'homograph(disambiguation)' is missing the the
disambiguation (i.e., homograph()).
Action: None
DRG-11736: illegal text after disambiguated homograph
Cause: A term of the form 'homograph(disambiguation)' has text after the
disambiguation (e.g, homograph(disambiguation) extra text".
Action: None
DRG-11801: Continue
Cause: Enquire user to decide if continue is necessary HTTP_ERROR = 100
Action: Upon positive response, continue the original operation
DRG-11802: Switching Protocols
Cause: Telling client a protocol switching just happened HTTP_ERROR = 101
Action: The user agent takes proper actions
DRG-11803: OK
Cause: Telling client things are ok HTTP_ERROR = 200
DRG-10000 to DRG-52403 24-39
DRG-11804: Created
Cause: Telling client things are created HTTP_ERROR = 201
DRG-11805: Accepted
Cause: Telling client things are accepted but not commited HTTP_ERROR = 202
DRG-11806: Non-authoritative Information
Cause: The returned metainformation is not the definitive set HTTP_ERROR = 203
Action: The user agent knows the information is Non-authoritative
DRG-11807: No Content
Cause: request has been fulfilled but no new information found HTTP_ERROR = 204
DRG-11808: Reset Content
Cause: Telling client to reset the document view HTTP_ERROR = 205
DRG-11809: Partial Content
Cause: Telling client document content is a patial content HTTP_ERROR = 206
DRG-11810: Partial Update OK
Cause: Telling client document is partially updated HTTP_ERROR = 207
DRG-11811: Multiple Choices
Cause: Telling client multiple choices of resources is possible HTTP_ERROR = 300
DRG-11812: Moved Permanently
Cause: The URI has been assigned a new permanent URI HTTP_ERROR = 301
DRG-11813: Moved Temporarily
Cause: The URI resides temporarily under a different URI. HTTP_ERROR = 302
DRG-11814: See Other
Cause: The URI can be found using GET METHOD under a different URI
HTTP_ERROR = 303
DRG-11815: Not Modified
Cause: Response to conditional GET, indicating document not modified.
HTTP_ERROR = 304
DRG-11816: Use Proxy

Cause: The client should use specified proxy to repeat the request HTTP_ERROR =
305
DRG-11817: Proxy Redirect
Cause: Proxy redirection. Not used HTTP_ERROR = 306
Action: Outdated due to HTTP evolution
DRG-11818: Temporary Redirect
Cause: The resource is temporarily under a different URI. HTTP_ERROR = 307
Action: The takes proper actions
DRG-11819: Bad Request
Cause: The URL syntax is incorrect. Request rejected by server. HTTP_ERROR = 400
DRG-11820: Unauthorized
Cause: The request requires further authentication. HTTP_ERROR = 401
DRG-11821: Payment Required
Cause: Reserved for future use. HTTP_ERROR = 402
DRG-11822: Forbidden
Cause: The server refuses to fulfil the request from client HTTP_ERROR = 403
DRG-11823: Not Found
Cause: The server can not find the requested URI HTTP_ERROR = 404
DRG-11824: Method Not Allowed
Cause: The user agent specified method not allowed HTTP_ERROR = 405
Action: The user agent reads allow header to decide alternatives.
DRG-11825: Not Acceptable
Cause: Requested resource is not acceptable according to request header
HTTP_ERROR = 406
Action: The user agent should query the user for the next action.
DRG-11826: Proxy Authentication Required
Cause: The client must authenticate itself with the proxy. HTTP_ERROR = 407
DRG-11827: Request Timeout
Cause: The server is tired of waiting for the requst HTTP_ERROR = 408
Action: The user agent repeat the request
DRG-10000 to DRG-52403 24-41
DRG-11828: Conflict
Cause: The request conflicts with the current state of the URI HTTP_ERROR = 409
DRG-11829: Gone
Cause: The resource is no longer available and no forwarding address. HTTP_ERROR
= 410
DRG-11830: Length Required
Cause: The server must receive a content-length header. HTTP_ERROR = 411
DRG-11831: Precondition Failed
Cause: Telling the user agent that the resource failed preconditions HTTP_ERROR =
412
DRG-11832: Request Entity Too Large
Cause: Request rejected because request entity is too large. HTTP_ERROR = 413
Action: If Retry-After header found, the user agent should retry.
DRG-11833: Request-URI Too Big
Cause: The server is refusing to accept the URI which is too big. HTTP_ERROR = 414
DRG-11834: Unsupported Media Type
Cause: The server is refusing the request because of media type HTTP_ERROR = 415
DRG-11835: Requested Range Not Satisfiable
Cause: The byte range request can not be satisfied by the resource extent.
HTTP_ERROR = 416
Action: The user agent reads content-range header in the response.
DRG-11836: Expectation Failed
Cause: Server can not meet the user agent's expectation. HTTP_ERROR = 417
Action: The user agent takes pro
DRG-11837: Reauthorization Required
Cause: Reserved HTTP_ERROR = 418
Action: Reserverd
DRG-11838: Proxy Reauthentication Required
Action: Reserved
DRG-11839: Internal Server Error
Cause: The server encountered internal error in fulfilling the request. HTTP_ERROR
= 500
DRG-11840: Not Implemented

Cause: The server can't support a request feature which has yet to be implemented.
HTTP_ERROR = 501
DRG-11841: Bad Gateway
Cause: In serving the request, the server received invalid response from gateway.
HTTP_ERROR = 502
DRG-11842: Service Unavailable
Cause: Server overloaded or in maintenance mode. HTTP_ERROR = 503
Action: If retry-after header is in the response, retry the request.
DRG-11843: Gateway Timeout
Cause: Upstream server did not timely respond to the gateway server. HTTP_ERROR
= 504
DRG-11844: HTTP Version Not Supported
Cause: The HTTP version in the request header is rejected by the server.
HTTP_ERROR = 505
DRG-11845: No Partial Update
Action: Reserved
DRG-11846: Response Is Stale
Cause: The the user agent knows the returned reponse is stale.
HTTP_CACHE_ERROR = 10
Action: The user agent client takes proper actions.
DRG-11847: Revalidation Failed
Cause: User agent's attempt to revalidate a stale response failed.
Action: The user agent client takes proper actions
DRG-11848: Disconnected Operation
Cause: The cache is intentionally disconnected for a time period.
DRG-11849: Heuristic Expiration
Cause: Cache freshness lifetime and response age both greater than 24 hours.
DRG-11850: Transformation Applied
Cause: Telling cache manager, content encoding/media type has been changed in
cache. HTTP_CACHE_ERROR = 14
DRG-10000 to DRG-52403 24-43

DRG-11851: Cache Related Warning
Cause: Arbitrary information about cache to be presented to logger.
Action: The user agent client must not take any automated action.
DRG-11852: Can't Locate Remote Host
Cause: connection to remote host failed USER_AGENT_ERROR
DRG-11853: No Host Name Found
Cause: The host name is not specicied in URI. USER_AGENT_ERROR
Action: The user agent client takes proper action.
DRG-11854: No File Name Found Or File Not Accessible
Cause: Unable to open the file specified USER_AGENT_ERROR
DRG-11855: FTP Server Replies
Cause: FTP server responds to the agent request USER_AGENT_ERROR
DRG-11856: FTP Server Doesn't Reply
Cause: No response from FTP server during operation. USER_AGENT_ERROR
DRG-11857: Server Timed Out
Cause: Server operation timed out USER_AGENT_ERROR
DRG-11858: Gopher Server Replies
Cause: Gopher server responds to the agent request. USER_AGENT_ERROR
DRG-11859: Data Transfer Interrupted
Cause: Processing of URL request was interrupted USER_AGENT_ERROR
DRG-11860: Connection Establishment Interrupted
Cause: Connection operation was interupped USER_AGENT_ERROR
DRG-11861: CSO-server Replies
Cause: Telling client things are ok USER_AGENT_ERROR
DRG-11862: This Is Probaly A HTTP Server 0.9 Or Less
Cause: A very old web server USER_AGENT_ERROR
DRG-11863: Bad, Incomplete, Or Unknown Response

Cause: The server is mumbering something not understandable
USER_AGENT_ERROR
DRG-11864: Unknown Access Authentication Scheme
Cause: The server is using an unkown access authentication scheme
USER_AGENT_ERROR
DRG-11865: News Server Replies
Cause: News Server is responding USER_AGENT_ERROR
DRG-11866: Please Try `ftp://' Instead Of `file://'
Cause: wrong access scheme is used. USER_AGENT_ERROR
DRG-11867: Method Not Suited For Automatic Redirection
DRG-11868: Too Many Redirections
Cause: The web server setup configured too many redirections
USER_AGENT_ERROR
Action: The user agent client should take proper actions
DRG-11869: Premature End Of File Detected
Cause: Detected end of file is unexpected USER_AGENT_ERROR
DRG-11870: Response From WAIS Server Too Large -- Extra Lines Ignored
Cause: Response from WAIS caused buffer overflow USER_AGENT_ERROR
DRG-11871: WAIS Server Doesn't Return Any Data
Cause: Bad WAIS Server USER_AGENT_ERROR
DRG-11872: Can't Connect To WAIS Server
Cause: Connect to WAIS server failed USER_AGENT_ERROR
DRG-11873: System Call Replies
Cause: register what system call replies USER_AGENT_ERROR
DRG-11874: Wrong Or Unknown Access Scheme
Cause: Protocol class is wrongfully connected to ther server USER_AGENT_ERROR
DRG-10000 to DRG-52403 24-45
DRG-11875: Access Scheme Is Not Allowed

DRG-11876: When Your Are Connected, You Can Log In
Cause: Pass information to telnet agent USER_AGENT_ERROR
DRG-11877: This Cache Version Has Expired And Will Be Automatically Reloaded
Cause: Need to tell user that cache entry has been reloaded USER_AGENT_ERROR
DRG-11878: Loading New Rules Must Be Explicitly Acknowledged
Cause: Let user agent client be aware of new rule loading USER_AGENT_ERROR
DRG-11879: Automatic Proxy Redirection Msut Be Explicitly Acknowledged
Cause: Let user agent client be aware of proxy redirection USER_AGENT_ERROR
DRG-12001: Please enter username:
Cause: Prompt user for name W3CLIB_MSG = 0
DRG-12002: Please enter username for proxy authentication:
DRG-12003: Please enter username for this FTP server:
DRG-12004: Password:
Cause: Prompt user for password W3CLIB_MSG = 3
DRG-12005: Please give name of file to save in:
Cause: Prompt user for file name W3CLIB_MSG = 4
DRG-12006: Plase enter account:
Cause: Prompt user for account W3CLIB_MSG = 5
DRG-12007: You might not be allowed to use this method here, continue?
Cause: Warn user of deny of service. W3CLIB_MSG = 6
DRG-12008: Location has moved, continue?
Cause: Warn user of location changes. W3CLIB_MSG = 7

DRG-12009: A new set of rules is requested to be added to your setup - continue?
Cause: Warn user of rule changes. W3CLIB_MSG = 8
DRG-12010: This file already exists - replace existing file?
Cause: Warn user of pending replacement W3CLIB_MSG = 9
DRG-12011: Authentication failed - retry?
Cause: Warn user of authentication failure W3CLIB_MSG = 10
DRG-12012: Proxy authentication failed - retry?
Cause: Warn user of proxy authentication failure W3CLIB_MSG = 11
DRG-12013: This method has already been performed - repeat operation?
Cause: Warn user the repetition of previous method used W3CLIB_MSG = 12
DRG-12014: This document is very big - continue operation?
Cause: Warn user of big document processing W3CLIB_MSG = 13
DRG-12015: The source document for this operation has moved - continue?
Cause: Warn user of location changes W3CLIB_MSG = 14
DRG-12016: The target document for this operation has moved - continue?
Cause: Warn user of destination document changes W3CLIB_MSG = 15
DRG-12017: A redirection may change the behavior of this method - proceed
anyway?
Cause: Warn user of redirection effects on method W3CLIB_MSG = 16
DRG-12018: Encountered an automatic request for changing proxy - continue?
Cause: Warn user of automatic proxy change W3CLIB_MSG = 17
DRG-12201: section group string already exists
Cause: Section group with the same name already exists
Action: Use another name or delete the existing one first
DRG-12202: error while creating section group
Cause: detect an Oracle error while creating section group
Action: see the accompanying Oracle error and take appropriate action
DRG-10000 to DRG-52403 24-47
DRG-12203: section group string does not exist

Cause: section group provided does not exist
Action: provide an existing section group
DRG-12204: error while dropping section group string
Cause: detect an Oracle error while dropping a section group
DRG-12206: tag string already exists in section group string
Cause: the start tag provided already exists in the same Section
Action: provide another start tag
DRG-12210: error while adding section string
Cause: detect an Oracle error while adding a section
DRG-12211: section or section id string does not exist
Cause: Section name or Section id to be dropped does not exist
Action: provide an existing Section name or Section id
DRG-12212: error while dropping section string
Cause: detect an Oracle error while dropping a Section
DRG-12213: cannot create/drop section group or sections for other user
Cause: You can only create/drop section group objects of your own
Action: have the other user create/drop his/her own objects
DRG-12217: tags cannot be more than 64 bytes
Cause: max limit of start and end tag is 64 bytes
Action: provide a shorter start and end tag
DRG-12218: section group name missing
Cause: must provide section group name
Action: provide a section group name when creating Section or section group
DRG-12219: section name missing
Cause: must provide Section name when creating a Section
Action: provide a Section name
DRG-12220: a valid tag must be provided
Cause: must provide tag when adding a section to a section group
Action: provide a tag
DRG-12223: section name string is a reserved name
Cause: you tried to name a section a reserved name
Action: Specify a different name for the section
DRG-12224: use ctx_ddl.create_section_group to create section groups
Cause: you tried to use ctx_ddl.create_preference to create a section group
Action: use ctx_ddl.create_section_group

DRG-12225: this type of section cannot be added to this section group
Cause: You tried to add sections to the null section group, add a stop section to a nonauto section group, or add a zone or field section to the auto section group
Action: Do not add this type of section to this section group
DRG-12226: a field section named string already exists in this section group
Cause: you tried to name an attribute or zone section the same name as an existing
field section
DRG-12227: a zone section named string already exists in this section group
Cause: you tried to name an attribute or field section the same name as an existing
zone section
DRG-12228: maximum number of field sections (string) exceeded
Cause: a section group has more than the maximum number of unique field sections
Action: no action required
DRG-12229: special section string already exists in this section group
Cause: you tried to add a special section which already exists
DRG-12230: special section name must be one of string
Cause: you tried to add an invalid special section
Action: specify a valid special section
DRG-12231: an attr section named string already exists in this section group
Cause: you tried to name a field or zone section the same name as an existing
attribute section
DRG-12232: invalid attribute tag format
Cause: you specified a tag for use as an attribute tag which did not have the correct
format. An attribute tag must have the form TAG@ATTR
Action: use correct format
DRG-12233: xml sections cannot co-exist with other section types
Cause: you tried to add an xml section to a section group or index which already has
zone, field, attr, or special sections, or you tried to add a zone, field, attr, or special
section to a section group or index which already has xml sections
Action: n/a
DRG-12234: column string already mapped in section group string
Cause: you tried to add a column section which already exists
Action: use correct format
DRG-10000 to DRG-52403 24-49
DRG-12235: an sdata section named string already exists in this section group
Cause: you tried to name a non-sdata section the same name as an existing sdata
section
DRG-12236: an mdata section named string already exists in this section group
Cause: you tried to name a non-mdata section the same name as an existing mdata
section
DRG-12237: a section named string already exists in this section group
Cause: you tried to map a column but the section name is already being used by
another section
DRG-12238: maximum number of mdata sections (string) exceeded
Cause: a section group has more than the maximum number of unique mdata sections
DRG-12239: maximum number of sdata sections (string) exceeded
Cause: a section group has more than the maximum number of unique sdata sections
DRG-12240: ORDER BY column string must be indexed as an SDATA section
Cause: an order by column has been mapped to an MDATA section
Action: adjust section group
DRG-12241: column name string is not a valid section name
Cause: an order by or filter by column cannot be implicitly mapped to an SDATA
section because the name is not valid as a section name
Action: adjust section group to map column name to a valid section name
DRG-12242: value of string is too large for section string
Cause: the value of a filter by or order by column is too large to be indexed
Action: update the row
DRG-12243: invalid datatype
Cause: the datatype specified for a sdata or mdata section is invalid
Action: specify a supported datatype
DRG-12244: data conversion error for sdata section string
Cause: failed to convert data
Action: check the format of the data
DRG-12245: SDATA operator not compatible with the sdata section string
DRG-12246: SDATA operand not compatible with the sdata section string

DRG-12247: maximum number of NDATA sections (string) exceeded
Cause: a section group has more than the maximum number of unique NDATA
sections
DRG-12248: a NDATA section named string already exists in this section group
Cause: you tried to name a non-NDATA section the same name as an existing
NDATA section
DRG-12249: a MVDATA section named string already exists in this section group
Cause: you tried to name a non-MVDATA section the same name as an existing
MVDATA section
DRG-12250: maximum number of mvdata sections (string) exceeded
Cause: a section group has more than the maximum number of unique mvdata
sections
DRG-12251: MVDATA section in XML_SECTION_GROUP is not supported
Cause: you tried to add MVDATA section in XML_SECTION_GROUP
Action: n/a
DRG-12252: No valid rowid provided with MVDATA update procedure
Cause: No valid rowid(s) provided with MVDATA update procedure
Action: Provide at least one valid rowid with this procedure
DRG-12300: an index with this column list already exists in the index set
Cause: You tried to add an index to an index set, but an index with the specified
column list already exists
Action: n/a
DRG-12301: index does not exist in index set
Cause: You tried to remove an index from an index set, but the specified index was
not found
Action: n/a
DRG-12302: invalid column list
Cause: You specified an invalid column list -- it may have a syntax error, duplicate
columns, or invalid column names
Action: n/a
DRG-12303: cannot add more than 99 indexes to an index set
Cause: You tried to add too many indexes to the index set
Action: n/a
DRG-12304: index set string does not exist
Cause: You specified an invalid index set name
DRG-10000 to DRG-52403 24-51
Action: n/a
DRG-12305: column string data type is not supported for index set columns
Cause: You specified a column in the column list of an index of an index set which
does not have a valid datatype
Action: use only DATE, NUMBER, CHAR, or VARCHAR2 columns in index column
lists
DRG-12306: column string is too long for index set columns
Cause: You specified a column in the column list of an index of an index set which is
too long
Action: CHAR and VARCHAR2 columns must be 30 bytes or less max length
DRG-12307: column string is NULL and cannot be indexed
Cause: You tried to index a row where at least one of the meta columns was NULL.
Action: provide a value for the meta column and reindex the row
DRG-12308: use ctx_ddl.create_index_set to create index sets
Cause: you tried to use ctx_ddl.create_preference to create an index set
Action: use ctx_ddl.create_index_set
DRG-12309: not to use compression on attributes lob column
Cause: you tried to use compression on attributes lob column for xml full text index
Action: not to use compression on attributes lob column for xml full text index
DRG-12400: template string is empty
Cause: The template is empty.
Action: Check the template was installed successfully.
DRG-12401: invalid template: query within a loop
Cause: A CTX EXEC tag cannot occur within a CTX REPEAT tag.
Action: Remove the CTX EXEC tag.
DRG-12402: error processing template string, line string
Cause: An error occurred when processing a template.
Action: See other errors on the stack and take the appropriate action.
DRG-12403: template string was not found
Cause: The template does not exist.
Action: Check the name of the template and check that it is installed.
DRG-12404: more than one template string found
Cause: More than one template with the same name was found.
Action: Remove templates as appropriate.
DRG-12405: error occurred processing CTX REDIRECT or CTX LABEL tag
Cause: Error in syntax of a tag.
Action: Correct the syntax of the tag.
DRG-12406: invalid CTX EXEC tag attribute (string)
Cause: The specified attribute is incorrectly specified.
Action: Check the sytax of the specified attribute.

DRG-12407: invalid CTX REPEAT tag attribute (string)
Cause: The specified attribute is incorrectly specified.
Action: Check the sytax of the specified attribute.
DRG-12408: invalid variable reference: string.string
Cause: The variable referenced does not exist.
Action: Check the label and column name.
DRG-12409: syntax error for label in string
Cause: The SQL in a CTX EXEC tag has incorrect syntax for a label or label type.
Action: Check the SQL attribute of the CTX EXEC tag.
DRG-12410: could not process CTX EXEC tag
Cause: An error occurred when processing the SQL attribute of a CTX EXEC tag.
Action: See other errors on the stack and take the appropriate action.
DRG-12411: SQL processing error: string
Cause: Error executing SQL from SQL attribute of CTX EXEC tag.
Action: Check the SQL in the SQL attribute.
DRG-12412: missing or invalid Template Processor attribute (string)
Cause: The specified attribute was missing or invalid in a HTML input field.
Action: Check the Template Processor-specific attributes in the INPUT, SELECT,
RADIO and CHECKBOX tags of the template.
DRG-12422: write to client failed
Cause: See the following messages.
Action: Contact the administrator.
DRG-12430: mandatory argument missing: string
Cause: This argument is mandatory.
Action: Re-submit the URL with this argument supplied.
DRG-12431: configuration section string not found
Cause: Specified conf argument is invalid.
Action: Re-submit the URL with this argument corrected.
DRG-12432: configuration file string not found or unreadable
Cause: An error occurred when processing the configuration file.
DRG-12433: load of string JDBC driver class failed
Cause: Driver class is invalid.
Action: Contact the administrator to modify configuration.
DRG-12434: connection failed using configuration string information
Cause: Configuration information is not correct.
Action: Contact the administrator to modify configuration.
DRG-10000 to DRG-52403 24-53
DRG-12435: highlight table allocation failed

DRG-12436: document table allocation failed
DRG-12437: highlight table release failed
DRG-12438: document table release failed
DRG-12439: highlight table read failed
DRG-12440: document table read failed
DRG-12441: counting the number of highlights failed
DRG-12500: stoplist string already exists
Cause: the specified stop list already exists
Action: must remove the duplicate stop list if you want to re-create it.
DRG-12501: null stoplist is not allowed
Cause: the specified stop list is null
Action: mustspecify a valid stop list
DRG-12502: cannot modify stoplists owned by other users
Cause: You can only create/drop Stop List or Stop Word objects of your own
Action: have the other user create/drop his/her own objects
DRG-12503: error while creating or dropping stoplist
Cause: detect an Oracle error while creating Stop List
DRG-12504: stoplist string does not exist
Cause: the specified stop list does not exist
Action: check that the Stop List is valid
DRG-12505: error while adding or removing a stop word
Cause: detect an Oracle error while adding or removing Stop Word
DRG-12506: stop word string does not exist in stoplist string
Cause: the specified Stop Sord does not exist
Action: check that the Stop Word is valid
DRG-12507: stop word string already exists in this stoplist
Cause: the specified stop word already exists
Action: must remove the duplicate word if you want to re-create it.
DRG-12508: null stop words are not allowed
Cause: the specified stop word is null
Action: must remove the null stop word if you want to re-create it.
DRG-12509: length of the stop word string exceeded the limit of string bytes
Cause: A stop list entry has exceeded the maximun length
Action: Reduce the length of the stop list entry
DRG-12511: use ctx_ddl.create_stoplist to create stoplists
Cause: you tried to use ctx_ddl.create_preference to create a stoplist
Action: use ctx_ddl.create_stoplist
DRG-12512: invalid stop class string
Cause: you specified an invalid stop class
Action: specify a valid stop class
DRG-12513: valid stop classes are: string
Cause: You specified an invalid stop class
Action: Specify a valid stop class
DRG-12514: languages must be specified for stopwords in a MULTI_STOPLIST
Cause: You tried to add a stopword to a multi_stoplist without specifying the
language of the stopword
Action: Specify the language of the stopword
DRG-12515: cannot specify language for stopwords in a BASIC_STOPLIST
Cause: You tried to add a language-specific stopword to a basic stoplist.
Action: Do not specify language for the stopword
DRG-12516: language column must be specified when using the multi stoplist
Cause: you tried to create an index using a multi stoplist but you did not specify a
language column
Action: specify a language column
DRG-12517: cannot add stopthemes to a MULTI_STOPLIST
Cause: you tried to add a stoptheme to a MULTI_STOPLIST. This is not supported in
this version.
Action: n/a
DRG-12518: cannot use this option with MULTI_STOPLIST
Cause: index already has multi_stoplist
DRG-10000 to DRG-52403 24-55
Action: can only be used to migrate from basic to multi stoplist

DRG-12519: LANGUAGE COLUMN missing
Cause: index does not have a language column
Action: specify language column value
DRG-12520: LANGUAGE COLUMN mismatch
Cause: LANGUAGE COLUMN does not match language column of the Index
Action: index language column should match specified one
DRG-12521: cannot add STOP PATTERN to NUMBERS stopclass
Cause: NUMBERS is a predefined stopclass to specify numeric values
Action: use any other alphanumeric word
DRG-12600: user datastore procedure name contains a semicolon
Cause: the procedure name specified had a semicolon
Action: remove semicolon or rename procedure name. The correct format is
PACKAGENAME.PROCEDURE_NAME
DRG-12601: invalid user datastore procedure name: string
Cause: the format of the procedure name is invalid. It should be in the form
PACKAGENAME.PROCEDURENAME or PROCEDURENAME
Action: make sure PROCEDURE attr has the format
PACKAGENAME.PROCEDURENAME or PROCEDURENAME
DRG-12602: index owner does not have access to user datastore procedure: string
Cause: the index owner does not have execute privilege of the procedure
Action: CTXSYS to grant execute privilege of the procedure to index owner
DRG-12603: CTXSYS does not own user datastore procedure: string
Cause: CTXSYS does not have execute privilege to the user datastore procedure
Action: make sure the package is owned by CTXSYS and the procedure exist
DRG-12604: execution of user datastore procedure has failed
Cause: an error occur while executing the user datastore procedure
Action: check or debug the datastore procedure
DRG-12605: datatype of column number in COLUMNS list is not supported
Cause: one or more of the columns in the column list of the multi datastore are of a
type which the multi datastore is unable to process
Action: change the column list of the multi datastore to contain only supported types.
PL/SQL functions can be used in the comlumn list to convert unsupported types to
supported types.
DRG-12606: error encountered while parsing COLUMNS list
Cause: An oracle error was encountered while parsing the columns list of the multi
datastore.
Action: See next error on stack and take appropriate action
DRG-12607: only ctxsys can create MULTI_COLUMN preferences

Cause: In order to create a multi column datastore preference, the effective user must
be ctxsys.
Action: contact your DBA to create the preference as ctxsys
DRG-12700: seed word must be a single word
Cause: seed word is not a single word
Action: use a single-word seed word
DRG-12800: Attribute NESTED_TYPE must have owner name as prefix
Cause: the attribute NESTED_TYPE does not have an owner name prefix
Action: reset the attribute NESTED_TYPE to include owner name prefix
DRG-12801: invalid type: string
Cause: invalid nested_type or
Action: check the owner and the type attribute names
DRG-12802: invalid type column: string
Cause: column specified does not exist in the type table
Action: check the type table
DRG-12803: invalid text datatype
Cause: LONG and LONG RAW are not supported in nested table
Action: change text column to a supported data type
DRG-12900: Operation:string for index: string has already been started
Cause: the specified operation has been started
Action: n/a
DRG-13000: error while adding or removing a sub lexer
Cause: see next error
Action: n/a
DRG-13001: sub lexer and multi lexer must have the same owner
Cause: you specified a sub lexer which is not owned by the owner of the enclosing
multi-lingual lexer preference
Action: specify a sub lexer owned by the owner of the multi-lexer preference
DRG-13002: preference string is not a MULTI_LEXER
Cause: you tried to add a sub lexer to a lexer preference which cannot accept sub
lexers. Only multi-lingual lexers can accept sub lexers.
Action: specify a multi lingual lexer
DRG-13003: preference string cannot be used as a sub lexer
Cause: you specified a preference for sub lexer which is not a lexer, or is a multilingual lexer or is an auto lexer
Action: specify a sub lexer which is not a multi-lingual lexer or an auto lexer
DRG-13004: language is invalid
Cause: you specified an invalid language for the sub lexer or stopword
DRG-10000 to DRG-52403 24-57
Action: specify a valid language -- see NLS Support Guide for a list of valid languages
DRG-13005: alt_value cannot be an NLS language name
Cause: you specified an NLS language name as the alt value
Action: specify a non-NLS value
DRG-13006: sub lexer for this language is not defined
Cause: you tried to remove a sub lexer for a language, but no sub lexer was defined
for that language
Action: None
DRG-13007: cannot define an alternate value for the DEFAULT sub lexer
Cause: you tried to define an alternate value for the DEFAULT sub lexer
Action: None
DRG-13008: cannot remove the DEFAULT sub lexer
Cause: you tried to remove the DEFAULT sub lexer
Action: None
DRG-13009: multi lexer preference does not have a DEFAULT sub lexer
Cause: you tried to use a multi lexer preference which does not have a DEFAULT sub
lexer defined
Action: add a DEFAULT sub lexer to the multi lexer preference and retry
DRG-13010: alt_value is already used by another sub lexer
Cause: you tried to specify an alt value which is already in use by another sub lexer in
the lexer preference
Action: specify a different alt value
DRG-13011: language column must be specified when using the multi lexer
Cause: you tried to create an index using a multi lexer preference, but you did not
specify a language column
Action: specify a language column
DRG-13012: language column must be a char, varchar, or varchar2 type
Cause: you specified a language column which is not a char, varchar, or varchar2
type.
Action: specify a language column of correct type
DRG-13013: cannot have language independent DEFAULT sub lexer
Cause: you tried to define a language independent DEFAULT sub lexer
Action: DEFAULT sub lexer can only be language dependent
DRG-13014: base table has rows with language column value string
Cause: there are documents in the base table with language column value set to
symbol for sublexer or stopword being removed
Action: base table should not have such rows
DRG-13015: sublexer string already exists in the index
Cause: cannot add a sub_lexer more than once
Action: if you want to update sub_lexer preferences, use update sub_lexer parameter
or remove currently used sub_lexer
DRG-13100: index is not partitioned
Cause: you attempted to invoke a partition-level operation on an index which is not
partitioned
Action: invoke appropriate index-level operation
DRG-13101: partition string does not exist in this index
Cause: you specified a partition name which does not exist
Action: specify correct partition name
DRG-13102: index partition name must be specified
Cause: you attempted to invoke a partition-level operation on a partitioned index but
did not specify the partition name
Action: n/a
DRG-13103: index table string is partitioned
Cause: you attempted to perform an exchange partition including indexes, but one or
more of the internal index tables are partitioned.
Action: specify EXCLUDING INDEXES on the exchange partition, then manually
rebuild the indexes.
DRG-13104: indexes do not have equivalent settings for string
Cause: you attempted to perform an exchange partition including indexes, but the
specified metadata setting is not equivalent across the two indexes, so the data cannot
be exchanged
Action: specify EXCLUDING INDEXES on the exchange partition, then manually
rebuild the indexes.
DRG-13200: failed to load dictionary file string
Cause: failed to load a dictionary file
Action: check whether the dictionary file exists in $ORACE_HOME/ctx/data/kolx or
access permission is available
DRG-13201: KOREAN_LEXER is desupported
Cause: Using lexer type KOREAN_LEXER which is desupported.
Action: Use lexer type KOREAN_MORPH_LEXER instead.
DRG-13300: document size bigger than string bytes
Cause: size of the document being indexed is larger than the maximum supported
size for the VARCHAR2 interface of stored procedure
Action: use the CLOB interface for the stored procedure
DRG-13301: syntax error in token data when expecting string, at line string
Cause: token data returned by the user-defined lexer procedure is incorrect
Action: modify user-defined lexer procedure to return expected data
DRG-13302: number of wildcard offsets must be in the range string..string, at line
string
Cause: number of wildcard offsets specified as value for the wildcard attribute does
not meet the supported range
DRG-10000 to DRG-52403 24-59
Action: modify user-defined lexer query procedure to return valid number of

wildcard offsets
DRG-13303: value of wildcard offset must be in the range string..string, at line
string
Cause: value of pre-normalized wildcard offset or post-normalized wildcard offset
specified as value for the wildcard attribute does not meet the supported range
Action: modify user-defined lexer query procedure to return valid value for wildcard
offset
DRG-13304: character referenced by wildcard attribute is not a wildcard character,
at line string
Cause: The wildcard attribute value specified the offset of a wildcard character. The
character at the specified offset is neither the '%' character nor the '_' character.
Action: Modify user-defined lexer query procedure.
DRG-13305: 'off' attribute value must be in the range string..string, at line string
Cause: value of 'off' attribute does not meet the supported range
Action: modify user-defined lexer index procedure to return valid value for 'off'
attribute
DRG-13306: 'len' attribute value must be in the range string..string, at line string
Cause: value of 'len' attribute does not meet the supported range
Action: modify user-defined lexer index procedure to return valid value for 'len'
attribute
DRG-13307: 'off'=string and 'len'=string references character past end-of-file of
string character document, at line string
Cause: value of 'off' attribute plus value of 'len' attribute is greater than the number of
characters in the document
Action: modify user-defined lexer index procedure to return valid values for 'off' and
'len' attributes
DRG-13308: query operator ABOUT not supported by USER_LEXER
Cause: the query contains an ABOUT operator while using USER_LEXER lexer type
Action: remove ABOUT operator from query or use lexer type other than
USER_LEXER
DRG-13309: operation not supported by USER_LEXER
Cause: USER_LEXER does not support this operation
Action: stop the operation or use alternate lexer type
DRG-13310: index owner does not have EXECUTE privilege on USER_LEXER
stored procedure string
Cause: user CTXSYS did not grant EXECUTE privilege on USER_LEXER stored
procedure to the index owner
Action: user CTXSYS grant EXECUTE privilege on USER_LEXER stored procedure to
index owner
DRG-13311: USER_LEXER stored procedure name contains a semicolon
Cause: the procedure name contains a semicolon character
Action: remove semicolon from procedure name or rename stored procedure
DRG-13312: user CTXSYS does not own USER_LEXER stored procedure string
Cause: CTXSYS does not have EXECUTE privilege on the USER_LEXER stored
procedure
Action: make sure the stored procedure exists and is owned by CTXSYS
DRG-13400: Oracle Data Mining was not installed
Cause: The function you used depends on Oracle Data Mining, which has not been
installed yet.
Action: make sure the Oracle Data Mining is installed
DRG-13401: the preference string type is not supported in this API
Cause: the type you have specified is not supported
Action: use a different type
DRG-13500: Parameter_string must start with string
Cause: Wrong syntax for parameter_string.
Action: Make sure the parameter_string has the correct syntax
DRG-13501: Shadow Index Already Exists
Cause: A shadow index was previously created already
Action: Drop the shadow index and try again
DRG-13502: NOPOPULATE is not allowed in recreate_index_online
Cause: Specify NOPOPULATE in parameter_string in recreate_index_online
Action: Don't specify NOPOPULATE.
DRG-13503: POPULATE is not allowed for a local index in create_shadow_index
Cause: Specify POPULATE for a local index during create_shadow_index
Action: Don't specify POPULATE.
DRG-13504: string has no shadow index
Cause: Tried to perform exchange shadow without creating shadow index first
Action: create a shadow index before doing exchanges_shadow_index
DRG-13505: Keyword string is not allowed here in parameter_string
Cause: Wrong syntax for parameter_string
Action: Make sure the parameter_string has the correct syntax
DRG-13506: string has no shadow part
Cause: Tried to perform exchange shadow part without creating shadow part first
Action: create a shadow part before doing exchanges_shadow_index on the partition.
DRG-13507: SWAP and NOPOPULATE is incompatible
Cause: Specified SWAP and NOPOUPLATE in parameter string
Action: Correct the parameter string setting
DRG-13508: Not all partitions for index string are swapped
Cause: try to swap an local partitioned index when not all partitions are swapped
Action: Swap all partitions first, then swap the (local) index.
DRG-10000 to DRG-52403 24-61
DRG-13509: error while swapping shadow index

Cause: an error occurred during the shadow index swap
Action: check error message stack for the actual error
DRG-13510: shadow index does not exist
Cause: Tried to perform exchange shadow without creating shadow index first
Action: create a shadow index before doing exchanges_shadow_index
DRG-13600: Syntax error in the result set descriptor at string
Cause: The result set descriptor has a syntax error
Action: check the syntax of the result set descriptor
DRG-13601: Syntax error in the order attribute
Cause: The order attibute has a syntax error
Action: check the syntax of the order attibute
DRG-13602: Number parsing error in string
Cause: The number string is malformed
Action: check the syntax of the number string
DRG-13603: To many sort keys
Cause: Too many sort keys are specified
Action: reduce the number of sort keys
DRG-13604: To many items to select
Cause: Too many select items are specified
Action: reduce the number of select items
DRG-13605: Too many group tags
Cause: Too many group tags are specified
Action: reduce the number of group tags
DRG-13606: start_hit_num is not specified or out of valid range number..number
Cause: start_hit_num is not specified or out of valid range
Action: set a correct start_hit_num value
DRG-13607: end_hit_num is not specified or out of valid range number..number
Cause: end_hit_num is not specified or out of valid range
Action: set a correct end_hit_num value
DRG-13608: Temporary lob not created for ctx_query.result_set_document
Cause: Temporary lob is not allocated for ctx_query.result_set_document
Action: Create a temporary lob for ctx_query.result_set_document
DRG-13609: Result set Interface should only have group mvdata element in
absence of a query
Cause: No query is specified and result set descriptor has invalid elements
Action: either specify query or change result set descriptor
DRG-13610: Missing group_values in the result set interface

Cause: MVDATA group values not specified in RSI
Action: add group_values element for group counting
DRG-13611: Missing value id for MVDATA group counting in the result set
interface
Cause: MVDATA group values not specified in RSI
Action: add value id element for group counting
DRG-13612: Missing path element in the result set interface
Cause: Path element not specified for the ctx_tree element
Action: add path element for the ctx_tree element
DRG-13613: Missing index name
Cause: index name not specified in the API
Action: specify an index name
DRG-13614: result_set_inteface not supported with security policy
Cause: result set interface not supported with security policies
Action: cannot use result set interface on table with security policy
DRG-13615: Only one snippet element allowed in result set interface
Cause: More than one snippet element specified with result set interface
Action: Specify only one snippet element with result set interface
DRG-13616: Invalid MVDATA group counting topn in result set interface
Cause: Cannot use group values and topn for the same group counting
Action: Use group_values or topn
DRG-13617: Invalid MVDATA value for topn in result set interface
Cause: Cannot use topn less than or equal to zero
Action: Use topn greater than zero
DRG-13618: Error in group counting in result set interface
Cause: Cannot do group count for facets with no data
Action: Check facet name or index needed facet values
DRG-13619: Invalid value for MVDATA sortby in result set interface
Cause: Invalid value provided for sortby criteria in result set interface
Action: Select either count or alpha
DRG-13620: Invalid value for MVDATA order in result set interface
Cause: Invalid value provided for order criteria in result set interface
Action: Select either asc or desc
DRG-13621: Duplicate group count element in result set interface
Cause: Group Count element specified more than once for group
Action: Specify one count element for a group
DRG-10000 to DRG-52403 24-63
DRG-13700: Syntax error in the Extraction Rule Descriptor

Cause: The Extraction Rule descriptor has a syntax error
Action: check the syntax of the Extraction rule descriptor
DRG-13701: Invalid rule_id
Cause: rule_id is NULL or rule_id <= 0
Action: rule_id must be number > 0
DRG-13702: Rule not found
Cause: No rule for given rule_id
Action: Specify a valid rule_id
DRG-13703: Invalid Type Specified: string
Cause: An invalid entity type was specified
Action: Specify a valid entity type
DRG-13704: Invalid Entity Type List
Cause: An invalid entity type list was specified
Action: Check format and types on entity type list
DRG-13705: Must use an Extract Policy
Cause: Using a non-extraction policy
Action: Use a policy created with ctx_entity.create_extract_policy
DRG-13706: Cannot use Entity Extraction Policy here
Cause: Using an entity extraction policy
Action: Use a policy created with ctx_ddl.create_policy
DRG-13707: Rule Engine Loading Failed
Cause: A user rule has an error
Action: Fix the user rule with the error
DRG-13708: Dictionary Loading Failed
Cause: The user dictionary has an error
Action: Fix the user dictionary
DRG-13709: Unsupported Language Specified: string
Cause: Unsupported Language Specified
Action: Specify a supported language
DRG-13710: Syntax Error in Dictionary
Cause: Syntax error in dictionary
Action: Correct syntax error in dictionary
DRG-13711: Stop Entity Not Found
Cause: Tried to remove a non-existent stop entity
Action: Cannot remove non-existent stop entity
DRG-13712: User Dictionary already loaded
Cause: Tried to load a 2nd user dictionary to a policy
Action: Drop the dictionary, and then load

DRG-13713: No User Dictionary loaded
Cause: No user dictionary loaded for this policy
Action: Cannot drop non-existent dictionary
DRG-13714: Duplicate Stop Entity
Cause: Trying to load a duplicate uncompiled stop entity
Action: Stop entity is already present
DRG-13715: Null name and type for Stop entity
Cause: Trying to load a stop entity with null name and type
Action: Stop entity must have at least one parameter non-null
DRG-13716: Entity Extraction not enabled
Cause: Haven't loaded correct event
Action: Must load correct event and level
DRG-13717: Null entry or alternate form in user dict
Cause: A entry or alternate form has null value
Action: Entries or alternate forms must be non-null
DRG-13718: No entity type given in user dict
Cause: An entry was not given an entity type
Action: All entries must have an entity type
DRG-13719: File and Drop are mutually exclusive
Cause: Tried to run ctxload with file and drop
Action: file and drop are mutually exclusive
DRG-13720: Stop entity already marked for deletion
Cause: Tried to re-drop a stop entity
Action: Only drop this stop entity once
DRG-13721: Duplicate Type on Typelist
Cause: Duplicate type on typelist
Action: Typelist must be unique
DRG-13722: Invalid Backreference
Cause: Backreference not between 1 and 10
Action: Backreferences must be between 1 and 10
DRG-13723: Invalid Attribute: string
Cause: Unsupported Attribute
Action: Follow correct syntax for rule or dictionary
DRG-13724: Invalid Attribute Value: string
Cause: Unsupported attribute value
DRG-10000 to DRG-52403 24-65
DRG-13725: Type Name Too Long

Cause: Type name more than 30 bytes
Action: Type must be less than 30 bytes
DRG-13726: Invalid Tag: string
Cause: Unsupported Tag
DRG-13727: Missing Tag: string
Cause: Missing Necessary Tag
Action: Add tag for rule or dictionary
DRG-13728: Missing Attribute: string
Cause: Missing Necessary Attribute
Action: Add attribute for rule or dictionary
DRG-13800: MVDATA section string does not exist
Cause: The given MVDATA section name does not exist in USER_SECTIONS
Action: Rewrite query with valid MVDATA section name
DRG-13801: literal is not compatible with the data type of the MVDATA section
Cause: The given literal is not compatible with the data type of the specified
MVDATA section.
Action: Rewrite query with a compatible literal
DRG-13802: MVDATA operand not compatible with the mvdata section string
DRG-13803: Illegal MVDATA value
DRG-13804: ctx_tree.register_index() not run for index string and mvdata section
string
Cause: failed to create data
Action: create the data (trees) first
DRG-13805: Invalid character in node name string
Cause: failed to create data
DRG-13806: Duplicate path 'string' in CTX_TREE.ADD_NODE()
Cause: The path specified in ctx_tree.add_node() adds the node with the same name
in the same tree at the same level
Action: change path
DRG-13807: Node string does not exist or is deleted
Cause: failed to lookup input node
Action: check if the path exists
DRG-13808: Empty path passed into string

Cause: path is empty
Action: pass in a non-empty and valid path
DRG-13809: Index with MVDATA sections must have big_io turned on
Cause: Big_io option not specified for MVDATA index
Action: turn on big_io for the index
DRG-13810: Index with support_ctx_tree must have atleast one MVDATA section
Cause: MVDATA section not specified for ctx_tree usage
Action: add one MVDATA section for the index
DRG-13811: Invalid path 'string' in CTX_TREE.ADD_NODE()
Cause: The path specified in ctx_tree.add_node() is invalid.
Action: change path
DRG-13812: Partitioned Index with MVDATA must have index-level big_io
Cause: Index-level big_io was not specified
Action: turn on big_io at index level
DRG-13900: Auto_Optimize Process is already started
Cause: Auto_Optimize Process is already started
Action: Can't start auto_optimize when it's already running
DRG-13901: Index must have stage_itab
Cause: Auto_Optimize works on indexes with stage_itab
Action: Use an index with stage_itab for auto_optimize
DRG-13902: Index/Partition already added to auto_optimize list
Cause: Index/Partition already added to auto_optimize list
Action: Can't add index/partition to list twice
DRG-13903: Index/Partition not on the auto_optimize list
Cause: Index/Partition not on the auto_optimize list
Action: Can't remove index/partition from list
DRG-50000: requested size larger than pagesize
Cause: The requested memoery size is larger than page size,
Action: Contact support
DRG-50100: CORE LSF error: string
Cause: detect a CORE LSF error
Action: look up the core error and take appropriate action
DRG-50101: CORE LEM error: string
Cause: detect a CORE LEM error while reading the error stack
DRG-50200: Third-party filter internal error
Cause: Third-party filter could not filter this document because of an internal error.
DRG-10000 to DRG-52403 24-67

DRG-50300: error sending message from server to client
Cause: internal database error or internal Text error
Action: Call customer support
DRG-50301: server error reading request queue
Cause: database error or internal Text error
DRG-50302: server error reading OOB break queue; cannot detect interrupts
Cause: database error or internal Text error
DRG-50303: error in bufout
Cause: This is an internal error
Action: Contact Oracle Support
DRG-50304: error in execute()
DRG-50305: getcmd() called when one of the queue names is NULL
DRG-50400: maximum number of fuzzy match candidates exceeded: string
Cause: Internal error, probably result of large number of indexed words
Action: Contact Oracle support
DRG-50401: failed to retrieve fuzzy match candidates from db: string
DRG-50402: Index validation failed for one or more tokens
Cause: Index validation generated an error for one or more tokens
Action: Check the ctx log for the detailed errors
DRG-50403: Invalid MVDATA entries exist in the index
Cause: Index validation generated an error for one or more tokens
Action: Check the ctx log for the detailed errors
DRG-50500: only RULE_CLASSIFIER is accepted in this API
Cause: you specified an illegal classifier
Action: use RULE_CLASSIFIER
DRG-50501: classifier preference not specified
Cause: the classifier preference is not specified
Action: specify a classifier preference
DRG-50502: cannot use RULE_CLASSIFIER in this API

Cause: you specified RULE_CLASSIFIER
Action: use a different classifier
DRG-50503: unsupported classification method
Cause: you spcified an unsupported classification method
Action: use a different classifier
DRG-50504: invalid column datatype for string table
Cause: the column datatype is invalid
Action: specify a different datatype
DRG-50600: assertion failed
Cause: An internal check-condition has been violated
Action: Contact Oracle support for assistance
DRG-50601: fatal error
Cause: A fatal error has occurred
Action: Contact Oracle support for assistance
DRG-50603: unrecognized operation code string
Cause: Bad operation code was encountered (reached switch default:)
Action: check .h files versions
DRG-50607: failed to obtain column info for cid string
Cause: internal error, probably a bug
Action: call customer support
DRG-50608: unexpected end of data
DRG-50609: pipe internal error
DRG-50610: internal error: string
DRG-50611: Third party lexer internal error: string
Cause: internal error from inxight lexer
DRG-50612: internal error: you need to call bind first for this insertion mode
Cause: internal error
DRG-50613: internal error: model type is not supported in drctrwpf
DRG-10000 to DRG-52403 24-69

DRG-50614: library loading error in string
DRG-50615: Third party lexer timed out
Cause: Third-party auto lexer could not complete tokenization because the lexer
timed out.
Action: Increase the value of the TIMEOUT attribute of the auto_lexer and reindex the
document. If TIMEOUT is set to 0 and the lexer still hangs context Oracle Support.
DRG-50616: Stop-Optimize List not found
Action: calll customer support
DRG-50617: Query string too long: string
Action: Invalid query string provided
DRG-50700: unknown command (args=queue, command)
Cause: this is an internal error
Action: Contact Oracle support to report a bug
DRG-50701: error in listener.get_cmd()
DRG-50702: error in drtlsleep()
Cause: this is an internal error in a testing function
DRG-50703: listener startup error
DRG-50704: Net8 listener is not running or cannot start external procedures
Cause: Oracle Text needs to call external code to complete your request, and could not
start the extproc agent process.
Action: Start listener if it is configured for external procedures and is not running. If
your listener is running, configure it for starting external procedures and restart it.
Consult Oracle documentation for details.
DRG-50800: failed to open cursor
Cause: Too many cursors open for internal queries
Action: implement cursor cleanup routine
DRG-50801: failed to parse cursor
Cause: parse error on an internal query
Action: check versions of code
DRG-50802: failed to bind input

Cause: bind error on an internal query
DRG-50803: failed to define output
Cause: define error on an internal query
DRG-50804: failed to exec cursor
Cause: exec error on an internal query
Action: debug code
DRG-50805: failed to close cursor
Cause: cursor close error on an internal query
DRG-50806: failed to rollback
Cause: transaction rollback error
DRG-50807: failed to commit
DRG-50850: string
Cause: This is an oracle error
Action: See RDBMS documentation
DRG-50851: SQL execute failed
Cause: failed to execute a sql statement
Action: please report this as a bug
DRG-50852: failed to turn SQL trace on
Cause: internal error,
Action: Please contact Oracle support
DRG-50853: fetch error
Cause: fetch error on an internal query
DRG-50855: logoff fail
Cause: Fail to logoff from the database
DRG-50857: oracle error in string
Cause: this is an informational message
Action: See error
DRG-50858: OCI error: string
Cause: a generic OCI error occurred
DRG-10000 to DRG-52403 24-71
Action: Please contact Oracle support

DRG-50859: failed to allocate statement handle
DRG-50860: failed to prepare statement
DRG-50861: failed to obtain type descriptor
DRG-50862: failed to create new Oracle object
DRG-50863: string assignment failed
DRG-50864: number assignment failed
DRG-50865: failed to append to collection
DRG-50866: failed to resize string
DRG-50867: failed to free Oracle object
DRG-50868: failed to free statement handle
DRG-50900: text query parser error on line string, column string
Cause: bad query
Action: fix query
DRG-50901: text query parser syntax error on line string, column string
Cause: bad query
Action: fix query
DRG-50902: unexpected character string

Cause: bad query
Action: fix query
DRG-50903: invalid weight string
Cause: invalid weight
Action: fix query
DRG-50904: weight string outside valid range 0.1 to 10.0
Cause: invalid weight
Action: fix query
DRG-50905: invalid score threshold string
Cause: invalid score threshold
Action: fix query
DRG-50906: score threshold string is not an integer
Action: fix query
DRG-50907: score threshold string outside valid range 1 to 100
Action: fix query
DRG-50908: invalid maximum number of documents string
Cause: invalid maximum number of documents
Action: fix query
DRG-50909: maximum number of documents string is not an integer
Action: fix query
DRG-50910: max documents requested string outside valid range 1 to 65535
Action: fix query
DRG-50911: invalid first document number string
Cause: invalid first document number
Action: fix query
DRG-50912: first document number string is not an integer
Action: fix query
DRG-50913: first document requested string is not a positive number
Action: fix query
DRG-50914: invalid last document number string
Cause: invalid last document number
DRG-10000 to DRG-52403 24-73
Action: fix query

DRG-50915: last document number string is not an integer
Action: fix query
DRG-50916: last document string is less than first document
Action: fix query
DRG-50917: escape on at end of text query string
Cause: unbalanced escape characters
Action: turn escape off
DRG-50918: mismatched close escape character
Cause: no matching open escape character for close escape
Action: match open and close escapes
DRG-50919: NEAR operand not a phrase, equivalence or another NEAR expression
Cause: invalid operand type for NEAR operator
Action: correct operand type
DRG-50920: part of phrase not itself a phrase or equivalence
Cause: invalid type of expression which is part of phrase
Action: fix query
DRG-50921: EQUIV operand not a word or another EQUIV expression
Cause: invalid operand type for EQUIV operator
DRG-50922: PL/SQL execution failed for string
Cause: PL/SQL function may not exist or is returning bad value
Action: PL/SQL may not exist or is returning bad value
DRG-50923: could not rewrite PL/SQL for execution
Cause: parser internal
Action: call support
DRG-50924: PL/SQL inside PL/SQL not supported
Cause: PL/SQL function call returned another PL/SQL call
Action: remove recursive PL/SQL
DRG-50925: could not parse return value of PL/SQL
Cause: string returned by PL/SQL function could not be parsed
Action: fix PL/SQL function being called
DRG-50926: invalid text query string
Cause: query string empty or made up of invalid characters
Action: fix query
DRG-50927: parser failed on line string on column string

Cause: bug
DRG-50928: reserved failure on line string on column string
Cause: bug
DRG-50929: parser internal on line string on column string
Cause: bug
DRG-50930: parser memory failure on line string on column string
Cause: memory allocation or freeing error
DRG-50931: parser not opened
Cause: bug
DRG-50932: parser preference initialization failed
Cause: bug
DRG-50933: parser hash insert failure
Cause: bug
DRG-50934: parser hash create failure
Cause: bug
DRG-50935: parser component failure
Cause: bug
Action: look for other errors
DRG-50936: query word string is too complex for index
Cause: bug
Action: look for other errors
DRG-50937: query too complex
Cause: query is too complex for our query evaluator
Action: make query smaller
DRG-50938: parser already bound
Cause: internal coding mistake
DRG-50939: parser not set
Cause: bug
DRG-10000 to DRG-52403 24-75

DRG-50940: parser not parsed
Cause: bug
DRG-50941: PL/SQL function string cannot be executed
Cause: PL/SQL function may not exist or cannot be executed by user
Action: rewrite PL/SQL function specified in query
DRG-50942: errors: stringstring
Cause: PL/SQL function encountered error -- this is the error message
Action: See error message
DRG-50943: query token too long on line string on column string
Cause: A query token is longer than 256 bytes
Action: Rewrite query
DRG-50944: NEAR operator not supported for theme index
Cause: NEAR operator used in theme index query
Action: Rewrite query without NEAR operator
DRG-50945: Illegal phrase in query for theme index
Cause: Phrase incorrectly defined in theme index query
DRG-50946: Invalid unary operator for theme index
Cause: Stemming, fuzzy match and soundex not allowed for theme index
DRG-50947: ABOUT clause not allowed without a theme index
Cause: The query contains an ABOUT clause, but there is no theme index to support
it
DRG-50948: ABOUT clause required in the absence of a text index
Cause: There is no text index, but the query does not contain any about clause. With
only a theme index present, each query term must belong to an ABOUT clause
DRG-50949: too many SQEs
Cause: Too many SQEs to expand
Action: Rewrite query or SQE
DRG-50950: circular SQE found
Cause: Circular SQE reference is found.
Action: Rewrite query or SQE
DRG-50951: Unable to resolve element name for attribute string
Cause: XPATH expression such as A/*/@B or A//@B is not supported.
DRG-50952: Section is not PATH section group

Cause: XPATH expression has section which is not created using PATH section
group.
Action: Rewrite query not to use XPATH expression or create the index with PATH
section group
DRG-50953: Unable to determine section name
Cause: XPATH expression should not end with . or *
Action: Rewrite the path expression not to use . or * at the end
DRG-50954: Theme index is required for CTXCAT about queries
Cause: There is no theme index, but the catsearch query contains about clause. You
must create a theme index before using ABOUT query against CTXCAT index
Action: create theme index
DRG-50955: Missing comma in transform clause string
Cause: A transform clause in a query template is missing a comma
Action: Add the comma in the appropriate position
DRG-50956: Theme index is required for THEMES transform queries
Cause: There is no theme index, but the operator TRANSFORM is used with
THEMES as its parameter. You must create a theme index before using THEMES in
TRASNFORM operator.
Action: create theme index
DRG-50957: Missing textquery element in query template string
Cause: The textquery tag is missing or misspelled in a query template
Action: Correct the missing tag
DRG-50958: Missing quote in transform clause string
Cause: A transform clause in a query template is missing a quote
Action: Add the quote in the appropriate position
DRG-50959: Query length exceeds string bytes
Cause: the query length exceeds the maximum allowed length
Action: reduce the length of the query
DRG-50960: Mild not operand not a term or phrase
Cause: invalid operand type for MNOT operator
DRG-50961: Missing string for string clause
Cause: the specified tag is missing from the specified complex query clause
Action: Add missing clause
DRG-50962: Query operators are not allowed in transform input string
Cause: You specified an operator (such as wildcard) in the input string for the
transform operator
Action: Remove or escape the query operator
DRG-10000 to DRG-52403 24-77
DRG-51002: unexpected component failure

DRG-51017: unable to open storage buffer for fuzzy match candidates
Cause: Internal error, probably insufficient memory
DRG-51019: unable to open or illegal format for fuzzy match data file: string
Cause: Unable to open OS file containing fuzzy matching information or the file was
not of the correct format
Action: Consult the documentation for correct location of the fuzzy match
information files and check for file damage
DRG-51020: out of memory in fuzzy matcher
Cause: Cannot allocate more memory
Action: Contact your system adminstrator
DRG-51021: undefined error in fuzzy matcher
DRG-51022: undefined error in stemmer
DRG-51023: stemmer file cannot be opened
Cause: Unable to open OS file containing stemmer lexicon, or the file contents were
not correct
Action: Consult documentation for for correct location of the stemmer lexicons and
check for file damage
DRG-51024: out of memory in stemmer
Cause: Cannot allocate more memory
Action: Contact your system administrator
DRG-51025: an invalid character was passed to the stemmer
Cause: Invalid character in word input to the stemmer
Action: Remove invalid character from word to be stemmed
DRG-51028: unexpected error in fuzzy match expansion: %(1)
DRG-51029: unexpected error in stemmer expansion: %(1)
DRG-51030: wildcard query expansion resulted in too many terms
Cause: User error
Action: Make wildcard query narrower

DRG-51100: invalid program argument index
Action: Contact Oracle Support to report a bug
DRG-51101: argument processing callback failed
DRG-51200: open keymap failed for index id = string
Cause: Failed to initialize the keymap for the column id specified.
Action: Check index ID. Contact support if caused by internal errors
DRG-51201: failed to perform DDL operation: database object string
Cause: Textkey mapping service failed on DDL operation
Action: Check Oracle error and take corrective action
DRG-51202: invalid key mapping operation mode : string
Cause: invalid keymap mode value found. This is an internal error
DRG-51203: found doc ids without mappings during get maps
Cause: found doc ids without mappings during get mapping by doc ids, the index
data and keymap service are out of synch.
DRG-51300: error getting dml Queue lock
Cause: a server must have hung while processing the dml Queue, leaving it locked
DRG-51301: error releasing dml Queue lock
Cause: internal database error, or perhaps someone dropped the lock while we were
using it
DRG-51311: DML lock handle previously allocated
DRG-51312: DML lock internal error string
DRG-51313: timeout while waiting for lock
Cause: most likely an internal error
DRG-51314: index is not empty
Cause: you attempted to invoke populate_pending against an index which already
has or has had indexed documents.
DRG-10000 to DRG-52403 24-79
Action: populate pending manually, or recreate the index NOPOPULATE

DRG-51403: New index name not provided by kernel
DRG-51801: failed to seek in file: %(1)
DRG-51802: failed to read from file: %(1)
DRG-51803: failed to open file: %(1)
DRG-51804: failed to write to file: %(1)
DRG-52100: string returned internal error code string
DRG-52101: an invalid session handle was passed to Oracle Text
DRG-52102: an invalid transaction handle was passed to Oracle Text
DRG-52103: the Oracle Text environment could not reset
DRG-52104: the Oracle Text environment could not initialize
DRG-52105: no delete function found
DRG-52106: Oracle Text service results could not be committed
DRG-52107: ctxkbtc internal error

DRG-52108: failed to delete knowledge base user extension
Action: check file permissions or contact Oracle support
DRG-52109: error in reading thesaurus
DRG-52110: error in writing extended knowledge base
DRG-52111: error in knowledge base cache
DRG-52112: improper Chinese string string of length number
Action: n/a
DRG-52113: improper Japanese string string of length number
Action: n/a
DRG-52200: invalid state during export
DRG-52201: imcompatible Oracle Text versions
Cause: attempting to import an incompatible version of Oracle Text data
Action: make sure source and target Oracle Text versions are compatible
DRG-52202: invalid class name: string
Cause: the specified class name is not valid
DRG-52203: invalid object name: string
Cause: the specified object name is not valid
DRG-52204: error while registering index
DRG-52205: class string and object string already exists for this index
Cause: duplicate entry of class and object
DRG-10000 to DRG-52403 24-81

DRG-52206: error while registering index object
DRG-52207: the specified attribute does not exist: string
DRG-52208: the specified attribute already exist: string
DRG-52210: error while registering value for attribute: string
DRG-52211: error while registering partition
DRG-52212: error while registering cdi columns
DRG-52300: Index string.string does not exist
Cause: The given index does not exist for the current user
Action: Give a valid index name
DRG-52301: Query Stats is already enabled for this index
Cause: attempting to enable the query stats for an index for which it is already
enabled
Action: None. No need to enable again
DRG-52302: Query Stats is not enabled for this index
Cause: attempting to disable the query stats for an index for which it is not enabled
Action: None. No need to disable if it is not already enabled
DRG-52303: Option String is full
Cause: Index option string is full
Action: None
DRG-52304: This operation requires Query Stats to be enabled for the index
Cause: attempting to do an operation which required query stats option for the index
to be enabled
Action: Enable query stats option for the index using ctx_output.enable_query_stats()
DRG-52305: Unknown value, string, passed in to stat_type
Cause: An invalid value is passed in to the parameter stat_type
Action: Give a valid value
DRG-52400: Dictionary string already exists

Cause: The specified dictionary already exists
Action: Must drop the dictionary if you want to re-create it.
DRG-52401: Invalid language string specified
Cause: Language specified is invalid
Action: Must specify a valid language
DRG-52402: Dictionary name is invalid
Cause: The specified dictionary name is invalid
Action: Must provide valid dictionary name
DRG-52403: Dictionary string does not exist
Cause: The specified dictionary does not exist
Action: Retry with the correct dictionary name
DRG-10000 to DRG-52403 24-83
25
EVM-00001 to EVM-00901
EVM-00001: Cannot write raw events to a terminal
Cause: Attempted to redirect binary events to a terminal.
Action: Use evmshow to format events for display.
EVM-00002: Use evmshow to format events for display
Cause: Attempted to redirect binary events to a terminal.
Action: Use evmshow instead.
EVM-00003: Failed to open file "string": string
Cause: Filename, path or the permisions were not valid.
Action: Use a valid path and filename, check permissions. Otherwise contact Oracle
Customer Support.
EVM-00004: Failed to open channel config file "string"
Cause: Configuration file name,the path or the permissions were not valid.
Action: Use a vaild path and filename, check permissions. Otherwise contact Oracle
Customer Support.
EVM-00006: Failed to create temporary file
Cause: The file being used as a temporary file for evmsort had one of the following
issues; filename, path or the permisions were not valid.
Customer Support.
EVM-00007: Failed to write to temporary file
Customer Support.
EVM-00008: Failed to read from temporary file
Customer Support.
EVM-00009: Failed to create EVM posting connection
Cause: Error occured while communicating with the EVM daemon.
Action: Check log and status of the EVM daemon.
EVM-00001 to EVM-00901 25-1
EVM-00010: Failed to read from EVM posting connection

EVM-00011: Failed to write to EVM posting connection
EVM-00012: Failed to create EVM listening connection
EVM-00013: Failed to read from EVM listening connection
EVM-00014: Failed to write to EVM listening connection
EVM-00015: Failed to create EVM service connection
EVM-00016: Failed to read from EVM service connection
EVM-00017: Failed to start EVM service "string"
Cause: EVM daemon failed to start.
Action: Check log for the EVM daemon.
EVM-00018: Failed to write to output stream
Cause: Failed to write to standard output.
EVM-00019: Failed to read event from input stream
Cause: Bad input file for evmshow/evmsort EOF missing.
Action: Check the input file.
EVM-00020: Failed to create event subscription
Cause: Bad network connection between subscriber and EVM daemon.
Action: Check the network connection and filter string.
EVM-00021: Failed to create filter
Cause: Used a null filter string or memory allocation failed.
Action: Use a non null filter string.
EVM-00022: Invalid filter string
Cause: Used a null or invalid filter string.
25-2 Error Messages

EVM-00023: Filter test operation failed
Cause: Used a null or invalid filter string.
Action: Use a non null filter string. Otherwise contact Oracle Customer Support.
EVM-00024: Lost connection to EVM daemon
Cause: Evmlogger lost connection to evmdaemon.
Action: Check status of evmlogger,evmd daemons and logs.
EVM-00025: Authorization database error
Cause: Not authorized to post/listen for certain events.
Action: Check evm.auth file to ensure the current user is authorized to post/listen for
specific events.
EVM-00026: Failed to post event "string"
Cause: Evmpost failed to post an event.
Action: Check the status and log for EVM daemon.
EVM-00027: Memory allocation failure
Cause: The system is running low on memory.
Action: Check the availability of memory in the system.
EVM-00029: Event contains invalid values
Cause: Invalid syntax for an event was used.
Action: Use a valid syntax for an event.
EVM-00030: Event name is missing
Cause: Name of the event was missing.
EVM-00031: Event name has too few components
Cause: Invalid syntax for an event was used.
EVM-00032: Failed to write event
Cause: Failed to write event to output file.
Action: Check the permissions of the file. Otherwise contact Oracle Customer
Support.
EVM-00033: Error in input file "string", line number
Cause: Failed to parse input file.
Action: Check input file and the line for possible errors. Otherwise contact Oracle
Customer Support.
EVM-00034: Error: string
Cause: Error Occured.
Action: Look at the error message for details.
EVM-00035: EVM service "string" terminated with exit code number
Cause: EVM daemon died.
EVM-00001 to EVM-00901 25-3
Action: Check the EVM daemon log.

EVM-00036: Host "string" is unknown
Cause: Invalid hostname discovered while trying to create a connection to the EVM
daemon.
Action: Check the hostname, on which EVM daemon is running. Otherwise contact
Oracle Customer Support.
EVM-00037: Failed to connect to EVM daemon on "string"
Cause: EVM daemon is dead or is not responding.
Action: Check the status of EVM daemon and logs.
EVM-00038: Failed to create an EVM event
Cause: Failed to create an EVM event.
Action: Check the EVM daemon log.
EVM-00039: Invalid port number in host name "string"
Cause: Used an invalid port number.
Action: Use a valid or a different port number.
EVM-00040: Error occurred while reading from "string"
Cause: Error occured when evmshow was reading from an input file.
Action: Check the input file.
EVM-00042: Use "string -A" to format events, or pipe output to evmshow
Cause: Invalid use of evmshow command.
Action: Use evmshow command as instructed.
EVM-00043: Attempting to reconnect to the EVM daemon...
Cause: Evmwatch trying to reconnect to the evm daemon.
Action: Not an error message.
EVM-00044: Attempting to reconnect to the EVM daemon on "string"...
Cause: Evmwatch trying to reconnect to the evm daemon on this host.
EVM-00045: EVM connection re-established
Cause: Evmwatch was able to reconnect to the evm daemon.
EVM-00104: End of file reached unexpectedly
Cause: End of event template file reached unexpectedly.
Action: Check the event template file in evm/admin.
EVM-00105: Missing end-of-group character
Cause: end-of-group character missing in event template file.
EVM-00106: Missing end-of-string character
Cause: end-of-string character missing in event template file.
25-4 Error Messages
EVM-00107: Value "string" is not valid

Cause: Invalid value found in the event template file.
EVM-00108: Keyword "string" is not valid
Cause: Invalid keyword found in the event template file.
EVM-00201: Failed to allocate space for application object
EVM-00202: Failed to allocate space for local lock pathname
EVM-00301: Failed to open logger config file "string"
Cause: Configuration file had one of the following problems; filename, path or
permissions were not valid.
Action: Check whether path and permissions are valid. Otherwise contact Oracle
Customer Support.
EVM-00302: Configuration error - using default configuration
Cause: Configuration file had invalid configuration details
Action: Check the configuration file.
EVM-00303: Keyword "string" is invalid in this position
Cause: Valid Keyword was used in an invalid position in configuration file.
Action: Use the correct syntax.
EVM-00304: Configuration error in file string, line number
Cause: Configuration error in configuration file.
EVM-00305: Memory allocation failure for "string"
EVM-00306: Failed to create filter for "string"
Cause: Failed to create a filter for events for evmlogger.
Action: Check the availability of memory.
EVM-00307: Filter string invalid for "string"
Cause: Used a null filter string or memory allocation failed.
Action: Use a non null filter string.
EVM-00308: Failed to open eventlog "string": string
Cause: Eventlog file had one of the following problems; filename, path or permissions
were not valid.
EVM-00001 to EVM-00901 25-5
Customer Support.
EVM-00309: Failed to write to eventlog "string"
Cause: Eventlog had one of the following problems; size or permissions were not
valid.
Action: Check the permissions and the size of the eventlog file. Otherwise contact
EVM-00310: Invalid suppression filter for eventlog "string"
Cause: Invalid filter was used.
Action: Use a non null filter. Otherwise contact Oracle Customer Support.
EVM-00311: Invalid entry in eventlog "string" (number events OK)
Cause: Evmlogger found an invalid entry in eventlog.
Action: Check the eventlog file.
EVM-00312: Eventlog "string" disabled
Cause: Events could not be written to the eventlog file.
Action: Check the permissions,max size of the logfile.
EVM-00313: Eventlog "string" re-enabled
Cause: Events logging is reenabled.
EVM-00314: Forwarder "string" disabled
Cause: Forwarding is disabled by the evmlogger.
EVM-00315: Forwarder "string" re-enabled
Cause: Forwarding is disabled by the evmlogger.
EVM-00316: Suppression disabled for "string"
Cause: Error message filtering supression disabled for this string.
EVM-00317: Suppression re-enabled for "string"
Cause: Error message filtering supression reenabled for this string.
EVM-00318: Failed to open config info file "string"
Cause: Configuration file had one of the following problems; filename, path or
Customer Support.
EVM-00319: Keyword "string" is not allowed in a secondary config file
Cause: Invalid Keyword was used.
Action: Use a valid Keyword.
25-6 Error Messages
EVM-00323: Config file "string" has insecure write permission

Cause: The configuration file had write permissions for the group 'other'.
Action: Change the write permissions for the configuration file
EVM-00324: Config file "string" has incorrect ownership
Cause: Configuration file should be owned by root or bin.
Action: Change the owner of configuration file to root or bin.
EVM-00325: Config file "string" is not a regular file
Cause: Configuration file is not a regular file.
EVM-00401: Failed to open binary event library file
Cause: Binary event file had one of the following problems; filename, path or
Customer Support.
EVM-00601: Data read from the input stream is not a valid EVM event
Cause: evmshow tried to read an invalid EVM event.
Action: Check the logs for the evm daemon.
EVM-00701: Check that the event is registered and you are authorized to post it
Cause: Not authorized to post for certain events.
Action: Check evm.auth file to ensure the current user is authorized to post the
specific event.
EVM-00702: Priority must be an integer in the range 0-number
Cause: Used an integer out of the range for priority.
Action: Use a valid integer.
EVM-00801: Missed number subscribed-to event(s)
Cause: Missed some events during the connection setup phase.
EVM-00802: Failed to reconnect within number seconds - terminating
Cause: Failed to establish a connection with EVM daemon.
Action: Check the logs for EVM daemon.
EVM-00901: Invalid sort specification "string"
Cause: Invalid sort specification used for evmsort.
Action: Use a valid sort specification. Look at documentation for evmsort using
evmsort -h.
EVM-00001 to EVM-00901 25-7
25-8 Error Messages
26
EXP-00000 to EXP-00114
EXP-00000: Export terminated unsuccessfully\n
Cause: Export encountered an Oracle error.
Action: Look up the accompanying Oracle message in the ORA message chapters of
this manual, and take appropriate action.
EXP-00001: data field truncation - column length=number, buffer size=number
actual size=number
Cause: Export could not fit a column in the data buffer.
Action: Record the given size parameters and the accompanying messages and report
this as an Export internal error to customer support. (Part of the table has been
exported. Export will continue with the next table.)
EXP-00002: error in writing to export file
Cause: Export could not write to the export file, probably because of a device error.
This message is usually followed by a device message from the operating system.
Action: Take appropriate action to restore the device.
EXP-00003: no storage definition found for segment(number, number)
Cause: Export could not find the storage definitions for a cluster, index, or table.
Action: Record the accompanying messages and report this as an Export internal
error to customer support.
EXP-00004: invalid username or password
Cause: An invalid username or password was specified.
Action: Retry with a valid username and password.
EXP-00005: all allowable logon attempts failed
Cause: Attempts were repeatedly made to log on with an invalid username or
password.
Action: Shut down the utility, then restart and retry with a valid username and
password.
EXP-00006: internal inconsistency error
Cause: Export's data structure was corrupted.
EXP-00007: dictionary shows no columns for string.string
Cause: Export failed to gather column information from the data dictionary. The table
may have been dropped.
EXP-00000 to EXP-00114 26-1
Action: Retry the export and, if this error recurs, report it as an Export internal error
to customer support.
EXP-00008: ORACLE error number encountered
Cause: Export encountered the referenced Oracle error.
Action: Look up the Oracle message in the ORA message chapters of this manual and
take appropriate action.
EXP-00009: no privilege to export string's table string
Cause: An attempt was made to export another user's table. Only a database
administrator can export another user's tables.
Action: Ask your database administrator to do the export.
EXP-00010: string is not a valid username
Cause: An invalid username was specified.
Action: Shut down the utility, then restart and retry with a valid username.
EXP-00011: string.string does not exist
Cause: Export could not find the specified table.
Action: Retry with the correct table name.
EXP-00012: string is not a valid export mode
Cause: An invalid export mode was specified.
Action: Retry with a valid export mode.
EXP-00013: respond with either 'Y', 'N', RETURN or '.' to quit
Cause: An invalid response was entered.
Action: Enter any of the responses shown in the message.
EXP-00014: error on row number of table string\n
Cause: Export encountered an Oracle error while fetching rows.
this manual and take appropriate action.
EXP-00015: error on row number of table string, column string, datatype number
Cause: Export encountered an error while fetching or writing the column. An
accompanying message gives more information.
Action: Correct the error and try again.
EXP-00016: ORACLE error encountered while reading default auditing options
Cause: Export encountered an Oracle error while reading the default auditing options
(those for updates, deletes, and so on).
EXP-00017: feature "string" is needed, but not present in database
Cause: The command entered requires the specified feature. Either that feature is not
installed, or the row describing the feature is missing from table V$OPTION
Action: Reinstall Oracle with the feature specified in the message.
26-2 Error Messages
EXP-00018: datatype (number) for column string, table string.string is not supported
Cause: Export does not support the referenced datatype.
Action: Retry with an acceptable datatype (CHAR, NUMBER, DATE, LONG, or
RAW).
EXP-00019: failed to process parameters, type 'EXP HELP=Y' for help
Cause: Invalid command-line parameters were specified.
Action: Check the online help screen for the set of valid parameters, then retry.
EXP-00020: failed to allocate memory of size number
Cause: Export failed to allocate the necessary memory.
Action: Decrease the export buffer size so that less memory is required, or increase the
runtime memory size for Export.
EXP-00021: can only perform incremental export in Full Database mode
Cause: USER or TABLE mode was specified when doing an incremental export.
Action: Specify FULL database mode (FULL=Y) and retry.
EXP-00022: must be SYS or SYSTEM to do incremental export
Cause: The privileges needed to do an incremental export do not exist. Only a data
base administrator can do incremental exports.
Action: Ask the database administrator to do the incremental export.
EXP-00023: must be a DBA to do Full Database or Tablespace export
Cause: The privileges needed to do a FULL database export do not exist. Only a
database administrator can do a FULL database export.
Action: Ask the database administrator to do the FULL database export.
EXP-00024: Export views not installed, please notify your DBA
Cause: The necessary Export views were not installed.
Action: Ask the database administrator to install the required Export views.
EXP-00025: dictionary shows no column for constraint string.number
Cause: Export failed to gather column information about the referenced constraint
from the data dictionary. The constraint may have been altered.
Action: Retry the export and, if this error recurs, report it as an Export internal error
to customer support.
EXP-00026: conflicting modes specified
Cause: Conflicting export modes were specified.
Action: Specify only one parameter and retry.
EXP-00027: failed to calculate ORACLE block size
Cause: Export failed to calculate the Oracle block size.
Action: Report this as an Export internal error to customer support.
EXP-00028: failed to open string for write
Cause: Export failed to open the export file for writing. This message is usually
followed by device messages from the operating system.
EXP-00000 to EXP-00114 26-3
EXP-00029: Incremental export mode and consistent mode are not compatible
Cause: Both consistent and incremental exports were specified.
Action: None. Consistent mode is turned off.
EXP-00030: Unexpected End-Of-File encountered while reading input
Cause: Encountered an End-Of-File while reading the user input.
Action: If input to export is being redirected, check the file for errors.
EXP-00031: Arraysize not in valid range. Using arraysize=number
Cause: The arraysize value specified is not in the valid range.
Action: None
EXP-00032: Non-DBAs may not export other users
Cause: Only database administrators can export to other users. A non- database
administrator attempted to specify owner=user where exporter is not the user.
Action: Request that this operation be performed by the database administrator.
EXP-00033: Could not find environment character set
Cause: The environment character set is missing or incorrectly specified.
Action: Ensure that the environment character set is correctly specified and is present.
EXP-00034: error on rowid: file# number block# number slot# number
Cause: Identifies the rowid on which an error occurred.
Action: This is an information message. No action is required.
EXP-00035: QUERY parameter valid only for table mode exports
Cause: You specified the QUERY parameter in an export command, but you are not
performing a table mode export. The QUERY parameter cannot be used for a user
mode export, a full export, nor a point in time recovery export.
Action: If you want to select a subset of rows for a table, you must export the table
independently with a table mode export. Issue a table mode export command that
specifies the table name and the query you want to execute during export.
EXP-00036: Object number non-existent in dictionary
Cause: The specified object could not be found in the dictionary. The object might
have been dropped during the export
Action: The object no longer exists; no action is needed.
EXP-00037: Export views not compatible with database version
Cause: The Export utility is at a higher version than the database version and is
thereby incompatible.
Action: Use the same version of Export utility as the database.
EXP-00038: Bad Hash cluster id in clu$
Cause: The function id in clu$ is not a legal number. Clu$ has become corrupted.
Action: Contact Worldwide Support
EXP-00039: export file string must be on a disk
Cause: On some platforms, export can read files from tape. This message is displayed
if the first file in an export file set was on disk and you specified a tape device for a
second or subsequent file.
26-4 Error Messages
Action: Verify that you have specified the correct file name for the export file.
Remember that all export files can be either on disk or all files can be on tape, but not
mixed both tape and disk.
EXP-00040: Dump file and log file must be different
Cause: The dump file and log file cannot be the same file.
Action: Specify different file names for the dump file and the log file, then retry the
operation.
EXP-00041: INCTYPE parameter is obsolete
Cause: Export encountered the INCTYPE parameter when parsing Export options.
Incremental Exports are no longer supported.
Action: Consult the Oracle Backup and Recovery guide. Export will attempt to
continue.
EXP-00042: Missing NLS_CHARACTERSET/NLS_NCHAR_CHARACTERSET in
props$
Cause: A value for NLS_CHARACTERSET/NLS_NCHAR_CHARACTERSET was
not entered in the props$ table"
Action: internal error.
EXP-00043: Invalid data dictionary information in the row where column "string" is
"string" in table string
Cause: The export utility retrieved invalid data from the data dictionary.
Action: Contact Oracle Worldwide Suport.
EXP-00044: must be connected 'AS SYSDBA' to do Point-in-time Recovery or
Transportable Tablespace import
Cause: The user must log in 'as SYSDBA' to perform transportable tablespace imports
or Point-In-Time Recovery imports.
Action: Ask your database adminstrator to perform the Transportable Tablespace
import or the Tablespace Point-in-time Recovery import.
EXP-00045: Cannot export SYSTEM Tablespace for Point-in-time Recovery or
Transportable Tablespace
Cause: SYSTEM tablespace cannot be part of recovery set or transportable tablespace
set.
Action: Contact Oracle Wordwide Support.
EXP-00046: Tablespace named string does not exist
Cause: The specified tablespace does not exist in dictionary.
EXP-00047: Missing tablespace name(s)
Cause: Tablespace name(s) were not supplied
Action: Provide tablespace name(s)
EXP-00048: Cannot export SYSAUX Tablespace for Point-in-time Recovery or
Transportable Tablespace
Cause: SYSAUX tablespace cannot be part of recovery set or transportable tablespace
set.
EXP-00000 to EXP-00114 26-5
EXP-00049: string option is not compatible with Point-in-time Recovery or

Transportable Tablespace Export
Cause: An option was specified incompatible with Point-in-time Recovery or
Transportable Tablespace Export.
Action: Retry the Export without the displayed option.
EXP-00050: Cannot perform Partition Export "string" on non-partitioned table
"string"
Cause: The table specified in this Partition Export is not a partitioned table.
Action: Use Table mode, or specify a non-partitioned table.
EXP-00051: "string" - given partition or subpartition name is not part of "string"
table
Cause: The specified partition or subpartition name is not in the specified table.
Action: Check if the correct table, partition or subpartition name was specified.
EXP-00052: error on row number of partition string\n
Cause: Export encountered the referenced Oracle error while fetching rows.
EXP-00053: unable to execute QUERY on table string because the table has inner
nested tables
Cause: You specified the QUERY parameter on a table that has one or more inner
nested tables. The QUERY parameter cannot be specified on tables that have inner
nested tables.
Action: Export the entire table by omitting the QUERY parameter.
EXP-00054: error on row number of subpartition string\n
Cause: Export encountered the referenced Oracle error while fetching rows.
EXP-00055: string.string is marked not exportable
Cause: An object was marked as non-exportable in the NOEXP$ table.
Action: Consult your database administrator.
EXP-00057: Failure to initialize parameter manager
Cause: The parameter manager failed in intialization.
Action: Record the messages that follow and report this to Oracle Wordwide Support
as an Export internal bug.
EXP-00058: Password Verify Function for string profile does not exist
Cause: Cannot find the function for the profile.
Action: Check if the profile was created properly.
EXP-00059: error converting an object type's identifier to characters
Cause: An invalid length of an object type identifier prevented its conversion.
Action: Contact Oracle Worldwide Support
26-6 Error Messages
EXP-00060: an object type had multiple TYPE BODYs

Cause: More than one TYPE BODY was found for an object type.
Action: Try dropping the TYPE BODY, if that is not successful, contact Oracle
Worldwide Support
EXP-00061: unable to find the outer table name of a nested table
Cause: While exporting a bitmap index or posttable action on an inner nested table,
the name of the outer table could not be located, using the NTAB$ table.
Action: Verify the table is properly defined.
EXP-00062: invalid source statements for an object type
Cause: TYPE was not found in the statements in SOURCE$ for an Object Type
Action: Contact Oracle Worldwide Support.
EXP-00063: error in changing language handle
Cause: Unable to change language handle.
EXP-00064: string is an inner nested table and cannot be exported.
Cause: An attempt was made to export an inner nested table without its parent table.
Action: Export the parent of the inner nested table.
EXP-00065: Error writing lob to the dump file.
Cause: The current LOB could not be written to the dump file.
Action: Identify the cause of the write failure and fix it.
EXP-00066: Object table string is missing its object identifier index
Cause: All object tables must have an object identifier index, but the specified table
was missing an index on its object identifier column.
Action: Recreate the type table and retry the operation.
EXP-00068: tablespace string is offline
Cause: Export failed to export tablespace (tablespace being offline).
Action: Make tablespace online and re export.
EXP-00070: attempt to free unallocated memory
Cause: An attempt was made to free memory that was not allocated.
EXP-00071: QUERY parameter not compatible with Direct Path export
Cause: You specified a value for the QUERY parameter for a direct path export. The
QUERY parameter cannot be used with a direct path export.
Action: Re-issue the export command with DIRECT=N or omit the DIRECT
parameter from the command line.
EXP-00072: error closing export file string
Cause: An error occurred while trying to close the export file.
EXP-00000 to EXP-00114 26-7
EXP-00073: dump file size too small

Cause: You specified either the FILESIZE parameter or the VOLSIZE parameter (if
your platform supports it), and the value of the parameter is too small to hold the
header information for the export file, plus any data.
Action: Increase the value of the FILESIZE or VOLSIZE parameter.
EXP-00074: rounding VOLSIZE down, new value is string
Cause: The VOLSIZE parameter must be a multiple of the RECORDLENGTH, but the
value you specified for VOLSIZE does not meet this requirement. The value of
VOLSIZE has been rounded down to be a multiple of the RECORDLENGTH used for
the dump file.
Action: No action is required. You can adjust the VOLSIZE or RECORDLENGTH
parameter to avoid this message. When importing this file, you must specify the
VOLSIZE value reported by this message.
EXP-00075: rounding FILESIZE down, new value is string
Cause: The FILESIZE parameter must be a multiple of the RECORDLENGTH, but the
value you specified for FILESIZE does not meet this requirement. The value of
FILESIZE has been rounded down to be a multiple of the RECORDLENGTH used for
the dump file.
Action: No action is required. You can adjust the FILESIZE or RECORDLENGTH
parameter to avoid this message. When importing this file, you must specify the
FILESIZE value reported by this message.
EXP-00076: multiple devices specified for tape output
Cause: You specified multiple file names when doing an export to a tape device.
EXPORT uses the same device for writing all files, of the number of tape volumes
required. For this reason, export will accept only one value for the FILE parameter
when writing to tape.
Action: Reenter the EXPORT command, but specify only one tape device in the FILE
parameter.
EXP-00077: multiple output files specified for unbounded export file
Cause: You specified multiple file names when doing an export and you also
specified a value of 0 for the FILESIZE parameter. Note that 0 is the value used if
FILESIZE is not specified on the command line. Since a value of 0 for FILESIZE means
that only one file will be written and there is no size limit for that file, the other files
you specified in the FILE parameter can never be used.
Action: If you intended to write multiple files, respecify the command but use the
FILESIZE to specify the maximum number of bytes that EXPORT should write to
each file. If you intended to write only one file with no limits on it's size, reissue the
EXPORT command but specify only one file name for the FILE parameter.
EXP-00078: Error exporting metadata for index string. Index creation will be
skipped
Cause: Domain indexes export private metadata via anonymous PL/SQL blocks prior
to the CREATE INDEX statement. Export does this by calling the
ODCIIndexGetMetadata method on the implementation type associated with the
index. A problem occurred inside this routine. Because the metadata is considered an
integral part of the index, the CREATE INDEX statement was not written to the dump
file.
26-8 Error Messages
Action: Contact the developer of the index's implementation type. If this is an Oraclesupplied index (perhaps via a data cartridge), contact Oracle Worldwide Support.
EXP-00079: Data in table "string" is protected. Conventional path may only be
exporting partial table.
Cause: User without the execute privilege on DBMS_RLS, the access control package,
tries to export a table that has access control. Since table owner is also subjected to
access control, the owner may not be able to export all rows in the table, but only the
ones he can see. Also, to preserve integrity of the table, user exporting the table
should have enough privilege to recreate the table with the security policies at import
time. Therefore, it is strongly recommended the database administrator should be
handling exporting of this table. Granting the table owner execute privilege would
also satisfy this security check, though it might have other security implications. If the
table does not have objects, can use direct mode.
Action: Ask the database administrator to export/import this table/view.
EXP-00080: Data in table "string" is protected. Using conventional mode.
Cause: User without the execute privilege on DBMS_RLS, the access control package,
tries to direct export a table that has access control enabled. Using conventional
export mode instead. Note that because of access control, only a partial table may be
exported.
EXP-00081: Exporting access control for table/view "string" as non-DBA.
Cause: A non-DBA user tries to export table/view and the associated fine grain access
control policies. The user may not have enough privilege to recreate the access control
policies when importing the table/view. And such an event may cause inconsistency
in the security model of the table/view.
EXP-00082: Invalid function name passed to procedural object support: string
Cause: Internal inconsistency error: The listed function is not a method on export's
procedural object interface specification.
EXP-00083: The previous problem occurred when calling string.string.string
Cause: The listed package provides export/import support for procedural actions.
The previously listed error occurred while calling the specified function.
Action: Contact Oracle Worldwide Support. Most packages are supplied by Oracle
internal cartridge or server development groups. The package name will help Support
determine the correct owner of the problem.
EXP-00084: Unexpected DbmsJava error number at step number
Cause: The error was returned from a call to a DbmsJava procedure.
EXP-00085: The previous problem occurred when calling string.string.string for
object number
Cause: The listed package provides export/import support for procedural objects, i.e,
those whose DDL is supplied by stored procedures. The previously listed error
occurred while calling the specified function.
EXP-00000 to EXP-00114 26-9
Action: Contact Oracle Worldwide Support. Most packages are supplied by Oracle
internal cartridge or server development groups. The package name will help Support
determine the correct owner of the problem.
EXP-00086: Primary key REFs in table "string"may not be valid on import
Cause: The specified table contains primary key REFs which may not be valid in the
import database.
Action: Do not use Export/Import to move Primary key REFs between databases
having differing character sets.
EXP-00087: Problem with internal hash table of schema/table names
Cause: Most likely a problem with allocating memory for the hash table entries.
EXP-00089: invalid FILE_FORMAT specification
Cause: The FILE_FORMAT specification did not contain an instance of "%s". This
wildcard string must be present.
Action: Correct the error and reenter the EXPORT command.
EXP-00090: cannot pin type "string"."string"
Cause: Export was unable to pin the specified type in the object cache. This is
typically caused because a type could not be made valid (for example because of
authorization violations in accessing subtypes).
Action: Fix the problem with the offending type until the type can be successfully
compiled.
EXP-00091: Exporting questionable statistics.
Cause: Export was able export statistics, but the statistics may not be usuable. The
statistics are questionable because one or more of the following happened during
export: a row error occurred, client character set or NCHARSET does not match with
the server, a query clause was specified on export, only certain partitions or
subpartitions were exported, or a fatal error occurred while processing a table.
Action: To export non-questionable statistics, change the client character set or
NCHARSET to match the server, export with no query clause, export complete tables.
If desired, import parameters can be supplied so that only non-questionable statistics
will be imported, and all questionable statistics will be recalculated.
EXP-00092: Unable to set NLS_NUMERIC_CHARACTERS to required defaults.
Cause: Export was unable to set NLS_NUMERIC_CHARACTERS to '.,'
EXP-00093: Could not convert to server character set's handle
Action: Contact Worldwide support.
EXP-00094: Could not convert to server national character set's handle
EXP-00095: Flashback_time and Flashback_scn are not compatible
Cause: Both flashback_time and flashback_scn paramerers were specified.
Action: Reissue command with only one flashback parameter.

EXP-00097: Object type "string"."string" is not in a valid state, type will not be
exported
Cause: The object type's status is invalid which may be caused by a dependant type's
modification (or removal) without cascading the change.
Action: The type must be recompiled using ALTER TYPE COMPILE.
EXP-00098: Data in table has not been upgraded, table will not be exported
Cause: Export is attempting to process a table containing references to a type which
has evolved. In order for Export to process the table successfully, all data within each
table must be upgraded to the latest revision of each referenced type.
Action: The table must be updated using ALTER TABLE UPGRADE DATA.
EXP-00099: Table "string"."string" is not in a valid state, table will not be exported
Cause: A table or one of its dependant types has modified without cascading the
change. This left the table in an INVALID state.
Action: The table must be updated using ALTER TABLE UPDATE.
EXP-00100: error converting an object type's hashcode to characters
Cause: An invalid length of an object type identifier prevented its conversion.
EXP-00101: Version 1 extensible index "string"."string" can not be included in
Transportable Tablespace Export
Cause: Transporable Tablespace extensible indexes must be at least version 2.
Action: Upgrade extensibile index implementation to version 2 specifications.
EXP-00102: Resumable parameters ignored -- current session not resumable
Cause: Current session is not resumable.
Action: Must specify RESUMABLE=Y to enable resumable session in order for the
RESUMABLE_NAME and RESUMABLE_TIMEOUT parameters to take effect.
EXP-00103: The FLASHBACK_TIME parameter was invalid
Cause: FLASHBACK_TIME did not contain a valid timestamp or an expression that
yields a valid timestamp.
Action: Specify a timestamp value in the format of YYYY-MM-DD HH24:MI:SS or an
expression that evaluates to a valid timestamp.
EXP-00104: datatype (string) of column string in table string.string is not supported,
table will not be exported
Cause: The column is of a datatype which does not contain the required support. The
table will not be exported.
Action: Use the Data Pump version of Export to export this table.
EXP-00105: parameter string is not supported for this user
Cause: The user attempted to specify either CONSISTENT or OBJECT_CONSISTENT
when connected as sysdba.
Action: If a consistent export is needed, then connect as another user.
EXP-00106: Invalid Database Link Passwords
Cause: Invalid Encoded Password for Database Link
EXP-00000 to EXP-00114 26-11
Action: Please drop the Database Link and recreate it after import.
EXP-00107: Feature (string) of column string in table string.string is not supported.
The table will not be exported.
Cause: Export does not contain the required support for this feature. The table will
not be exported.
Action: Use the Data Pump version of Export to export this table.
EXP-00108: NULL lob fetched
EXP-00109: XSL delimiter not found
EXP-00110: Tablespace string is encrypted and will not be exported
Cause: Encrypted Tablespace feature is not supported by classic export
Action: Use DATAPUMP Utility to export this tablespace.
EXP-00111: Table string resides in an Encrypted Tablespace string and will not be
exported
Cause: Encrypted Tablespace feature is not supported by classic export
Action: Use DATAPUMP Utility to export this table.
EXP-00112: Index string is of XMLType and could not be exported
Cause: Export does not contain the required support for this feature. The index could
not be exported.
Action: Use Oracle Data Pump Utility to export this index.
EXP-00113: Feature string is unsupported. string string.string could not be exported
Cause: Export does not contain the required support for this feature.
Action: Use Oracle Data Pump Utility
EXP-00114: Length of string string is exceeding the maximum limit
Cause: Provided length was more than the maximum limit allowed.
Action: Check the input value and provide the correct value.
27
GIPC-00000 to GIPC-00020
GIPC-00000: general success.
Cause: The operation succeeded.
GIPC-00001: general failure.
Cause: A GIPC operation failed.
Action: Examine the trace and log files for the specific cause.
GIPC-00002: GIPC needs to be initialized.
Cause: The application failed to initialize GIPC prior to performing an operation.
Action: Initialize GIPC.
GIPC-00014: buffer not large enough to hold data.
Cause: The buffer provided by the application was not big enough to hold the data
received.
Action: Use a larger buffer.
GIPC-00016: timeout waiting on request.
Cause: A wait call returned because the time expired.
Action: This error happens normally in most cases. If this error was not expected,
examine the trace and log files for the reason.
GIPC-00017: waiting call has been posted.
Cause: A wait was interrupted by another thread posting it.
Action: This error happens normally in most cases. If this error was not expected,
examine the trace and log files for the reason.
GIPC-00020: bind address already in use.
Cause: The application attempt to bind an endpoint to an address which has already
been bound.
Action: Specify another address.
GIPC-00000 to GIPC-00020 27-1
27-2 Error Messages
28
IMG-00001 to IMG-02014
IMG-00001: unable to initialize Oracle Multimedia environment
Cause: The image processing external procedure initialization process failed.
IMG-00002: unrecoverable error
IMG-00003: exhausted memory while processing image
Cause: Oracle Multimedia exhausted available Java memory during processing.
Action: Increase the JAVA_POOL_SIZE initialization parameter setting.
IMG-00201: unsupported metadata type
Cause: The requested metadata type could not be read from or written to this image
format.
Action: Refer to the Oracle Multimedia documentation to select the proper metadata
type for this image.
IMG-00202: unsupported character encoding
Cause: The character encoding was not supported for this image format.
Action: Refer to the Oracle Multimedia documentation to select the proper encoding
for this image.
IMG-00203: xmlData is invalid
Cause: The XML document was NULL or not schema valid.
Action: Create a schema valid document for input.
IMG-00204: input metadata too long
Cause: The metadata was too long to embed in this image format.
Action: Trim the metadata, or use a different image format.
IMG-00205: cannot add a TIFF directory entry
Cause: No new entries could be added to this directory.
Action: Use a different image format.
IMG-00206: unsupported image format for putMetadata
Cause: Metadata could not be written to this image format.
Action: Use a different image format.
IMG-00001 to IMG-02014 28-1
IMG-00207: input parameter is not valid

Cause: The input parameter value contained an invalid value.
Action: Correct the input parameter value.
IMG-00208: metadata format parse error
Cause: The parser detected an error in the embedded metadata.
Action: Verify that the metadata conforms to proper standards.
IMG-00209: error parsing metadata
Cause: There was an internal error while parsing the metadata.
IMG-00210: unable to get metadata from an empty image
Cause: There was no data in the input image.
populate image data into the image object.
IMG-00211: metadataType value "string" is invalid
Cause: The metadataType parameter value was NULL or invalid.
Action: Correct the metadataType parameter value.
IMG-00212: encoding value "string" is invalid
Cause: The encoding parameter value was NULL or invalid.
Action: Correct the encoding parameter value.
IMG-00213: xmlData does not contain an RDF element
Cause: The XML document did not contain an RDF element as a child of xmpMetadata.
Action: Create a schema valid document with an RDF element.
IMG-00502: invalid scale value
Cause: An invalid scale value was found while parsing the parameters for the image
process function.
Action: Correct the statement by using a valid scale value. Refer to the Oracle
Multimedia documentation for a description of the correct usage and syntax for the
image processing command string.
IMG-00505: missing value in CUT rectangle
Cause: An incorrect number of values was used to specify a rectangle.
Action: Use exactly four integer values for the lower-left and upper- right vertices.
IMG-00506: extra value in CUT rectangle
Cause: An incorrect number of values was used to specify a rectangle.
Action: Use exactly four integer values for the lower left and upper right vertices.
IMG-00510: string
Cause: A syntax error was found while parsing the parameters for the image process
function.
Action: Correct the statement by using valid parameter values. Refer to the Oracle
28-2 Error Messages
IMG-00511: string
Cause: An error was found while accessing image data.
IMG-00512: multiple incompatible scaling parameters found
Cause: Multiple incompatible scaling parameters were found in the image process
command string. With the exception of XSCALE and YSCALE, which can be used
together in a process command string, scaling functions are mutually exclusive and
cannot be combined.
Action: Remove scaling functions until only one remains (or two, if they are XSCALE
and YSCALE).
IMG-00513: missing value in scaling operation
Cause: An incorrect number of values was used to specify image dimensions.
fixedScale and maxScale require exactly two integer values for the X and Y
dimensions of the desired image.
Action: Use two values for fixedScale and maxScale.
IMG-00514: extra value in scaling operation
Cause: An incorrect number of values was used to specify image dimensions.
fixedScale and maxScale require exactly two integer values for the X and Y
dimensions of the desired image.
Action: Use two values for fixedScale and maxScale.
IMG-00515: incorrect number of input channels
Cause: An incorrect number of values was used to specify input channels.
InputChannels requires either one or three channels numbers for the gray or red,
green, and blue channel assignments.
Action: Use either one or three values to specify the input channels.
IMG-00516: default channel out of range
Cause: An incorrect value was used to specify the default channel selection.
Action: Use a channel number which is less than or equal to the number of bands and
greater than zero.
IMG-00517: height or width not present in parameter string
Cause: Height and/or width were not specified in the setProperties parameter string.
Action: Specify both the height and width.
IMG-00518: invalid value for height or width
Cause: Height and/or width were not positive integers"
Action: Specify both the height and width as positive integers"
IMG-00519: illegal combination of parameters
Cause: Other than height, width, dataOffset, and userString no other parameters may
be specified in the setProperties parameter string when CCITTG3 or CCITTG4 is used
as the compressionFormat.
Action: Supply only the height and width when compessionFormat is either CCITTG3
or CCITTG4. The dataOffset and userString may optionally be supplied as well.
IMG-00001 to IMG-02014 28-3
IMG-00520: invalid value for numberOfBands

Cause: NumberOfBands was not a positive integer"
Action: Specify numberOfBands as a positive integer"
IMG-00521: invalid value for dataOffset
Cause: DataOffset was not a positive integer"
Action: Specify dataOffset as a positive integer"
IMG-00522: invalid format for parameter value
Cause: A floating point value was specified where an integer is required, or a
character value was specified where a numeric value is required.
Action: Specify the correct type of values for process parameters.
IMG-00523: invalid process verb
Cause: A process verb was specified that is not understood by Oracle Multimedia.
Action: Refer to the Oracle Multimedia documentation for a description of valid
process verbs.
IMG-00524: mismatched quotes
Cause: Quotation marks used within a process command string were not matched.
Action: Ensure that quotation marks occur in pairs.
IMG-00525: locale error
IMG-00526: error parsing foreign image description
Cause: An internal error occurred while processing a foreign image.
IMG-00527: invalid deletePages specified
Cause: The specified value for the deletePages parameter was not valid.
Action: See the Oracle Multimedia documentation for reference information about
valid values for deletePages parameter.
IMG-00528: invalid movePages specified
Cause: The specified value for the movePages parameter was not valid.
valid values for movePages parameter.
IMG-00529: invalid combination of TIFF page operations
Cause: The specified TIFF page operations were not valid.
valid values for TIFF page operations.
IMG-00530: internal error while parsing command
Cause: An internal error occurred while parsing the command passed to the image
processing function or the foreign image setProperties function.
Action: Check the command passed to the function. Refer to the Oracle Multimedia
documentation for a description of the correct usage and syntax for the image
28-4 Error Messages
processing command string or the foreign image setproperties function. If you are
certain that your command is correct, then contact Oracle Support Services.
IMG-00531: empty or null image processing command
Cause: An empty or null image processing command was passed to the image
process function.
Action: Refer to the Oracle Multimedia documentation for a description of the correct
usage and syntax for the image processing command string.
IMG-00540: contentFormat and interleave conflict
Cause: Interleave values were specified using both the contentformat and interleave
verbs.
Action: Specify interleave using either contentformat or interleave, but not both.
IMG-00541: invalid contentFormat specified
Cause: The specified contentFormat was not valid.
contentFormat specifications.
IMG-00542: contentFormat includes invalid extra information
Cause: The specified contentFormat included invalid characters at the end of the
parameter string.
contentFormat specifications.
IMG-00543: invalid compressionFormat specified
Cause: The specified compressionFormat was not valid.
compressionFormat specifications.
IMG-00544: invalid compressionQuality specified
Cause: The specified compressionQuality was not valid.
compressionQuality specifications.
IMG-00545: invalid cut values specified
Cause: An invalid value was found while parsing the parameters for the cut
operation.
Action: Correct the statement by specifying values for the cut operation that are not
negative. Refer to the Oracle Multimedia documentation for a description of the
correct usage and syntax for the image processing command string.
IMG-00546: invalid page number specified
Cause: An invalid page number was specified.
Action: Specify page numbers that are not negative.
IMG-00547: invalid channelOrder specified
Cause: The specified channelOrder was not valid.
channelOrder specifications.
IMG-00001 to IMG-02014 28-5
IMG-00548: invalid interleave specified

Cause: The specified interleave was not valid.
interleave specifications.
IMG-00549: invalid pixelOrder specfied
Cause: The specified pixelOrder was not valid.
pixelOrder specifications.
IMG-00550: invalid scanlineOrder specified
Cause: The specified scanline order was not valid.
scanlineOrder specifications.
IMG-00551: invalid quantize method specified
Cause: The specified quantization method was not valid.
quantization method specifications.
IMG-00552: invalid inputChannels specified
Cause: An invalid value was specified for the inputChannels verb.
Action: Specify non-negative values for inputChannels. Refer to the Oracle
IMG-00553: invalid rotate value
Cause: An invalid value was specified for image rotation. Rotation values must be a
floating point number.
Action: Correct the statement by providing a valid rotation value.
IMG-00554: extra value in rotate operation
Cause: Multiple arguments were used to specify image rotation. The rotate operation
accepts only a single value.
Action: Provide a single value for the rotate operation.
IMG-00555: invalid value for gamma correction
Cause: An invalid value was specified for gamma correction. Gamma values must be
positive.
Action: Correct the statement by providing a positive gamma value.
IMG-00556: incorrect number of gamma values
Cause: An incorrect number of values were used to specify gamma correction.
Gamma correction requires either one or three gamma values.
Action: Provide either one or three values to specify the gamma correction.
IMG-00557: invalid value for contrast enhancement
Cause: An invalid value was used to specify contrast enhancement.
Action: To specify contrast enhancement using percentages, provide values between 0
and 100. To specify contrast enhancement using bounds, provide values greater than
0.
28-6 Error Messages
IMG-00558: incorrect number of contrast values

Cause: An incorrect number of values were used to specify contrast enhancement.
Contrast enhancement requires one, two, three, or six contrast values.
Action: Provide one or three values to specify contrast enhancement using
percentages; provide two or six values to specify contrast enhancement using contrast
bounds.
IMG-00559: invalid frame number
Cause: An incorrect number was used to specify frame in Dicom image. The number
should be greater than 0 and less than total frames in Dicom image.
Action: Provide one number greater than 0 and less than total frames in Dicom image.
IMG-00560: input format does not support page selection
Cause: The page verb was specified for an input format that does not support
selecting pages.
Action: Remove the page selection verb. Refer to the Oracle Multimedia
documentation for a description of which image formats support page selection.
IMG-00561: input format does not support channel selection
Cause: The inputChannels verb was specified for an input format that does not
support selecting channels.
Action: Remove the inputChannels verb. Refer to the Oracle Multimedia
documentation for a description of which image formats support input channel
selection.
IMG-00577: invalid quantize argument
Cause: A quantize value was specified that accepts an argument, but the argument
provided was not valid.
Action: Provide a valid, non-negative argument for the quantize value.
IMG-00578: missing quantize argument
Cause: A quantize value was specified that requires an argument, but no argument
was provided.
Action: Provide an argument for the quantize value.
IMG-00579: extra quantize argument
Cause: An extra argument was provided for a quantize value. Some quantize values
accept no arguments, while others accept a single argument.
Action: Provide an argument only for quantize values that accept an argument.
IMG-00580: specified format does not support output
Cause: The output format specified by fileFormat does support output.
Action: Change the specified fileFormat to one that supports output. Refer to the
Oracle Multimedia documentation for a description of which formats support output.
IMG-00581: output format does not support the specified contentFormat
Cause: The specified contentFormat is not supported by the explicitly or implicitly
specified output format.
Action: Refer to the Oracle Multimedia documentation for a description of which
contentFormat values are supported for each output format.
IMG-00001 to IMG-02014 28-7
IMG-00582: output format does not support the specified interleave

Cause: The specified interleave is not supported by the explicitly or implicitly
interleave values are supported for each output format.
IMG-00583: output format does not support the specified compressionFormat
Cause: The specified compressionFormat is not supported by the explicitly or
implicitly specified output format.
compressionFormat values are supported for each output format.
IMG-00584: output format does not support the specified compressionQuality
Cause: The specified compressionQuality is not supported by the explicitly or
implicitly specified output format.
compressionQuality values are supported for each output format.
IMG-00585: output format does not support the specified channelOrder
Cause: The specified channelOrder is not supported by the explicitly or implicitly
channelOrder values are supported for each output format.
IMG-00586: output format does not support the specified pixelOrder
Cause: The specified pixelOrder is not supported by the explicitly or implicitly
pixelOrder values are supported for each output format.
IMG-00587: output format does not support the specified scanlineOrder
Cause: The specified scanlineOrder is not supported by the explicitly or implicitly
scanlineOrder values are supported for each output format.
IMG-00599: internal error
Cause: An internal error has occurred.
IMG-00601: out of memory while copying image
Cause: Operating system process memory has been exhausted while copying the
image.
Action: See the database administrator or operating system administrator to increase
process memory quota.
IMG-00602: unable to access image data
Cause: An error occurred while reading or writing image data.
Action: Ensure that the source image can be read from and the destination can be
written to.
28-8 Error Messages
IMG-00603: unable to access source image data

Cause: The source image SOURCE attribute is invalid.
Action: Ensure that the SOURCE attribute of the source image is populated with
image data.
IMG-00604: unable to access destination image data
Cause: The destination image SOURCE attribute is invalid.
Action: Ensure that the SOURCE attribute of the destination image is populated with
image data.
Cause: An attempt was made to access an invalid image.
Action: Ensure that the SOURCE attribute of the image is populated with image data.
IMG-00607: unable to write to destination image
Cause: The destination image SOURCE attribute is invalid.
Action: Ensure that the SOURCE attribute of the destination image is initialized
correctly and that you have sufficient tablespace.
IMG-00609: unable to read image stored in a BFILE
Cause: The image stored in a BFILE cannot be opened for reading.
Action: Ensure that the access privileges of the image file and the image file's
directory allow read access.
IMG-00611: unable to access the BLOB for reading
Cause: The BLOB could not be opened for reading.
IMG-00612: unable to open export destination file
Cause: The file could not be created or opened.
Action: Check that the file does not refer to an existing directory. Check that the file is
not locked by another application.
IMG-00613: export destination access denied
Cause: Permission to write to destination file was denied.
Action: Refer to the Oracle Multimedia documentation for information on granting
privileges for the export() method.
IMG-00614: I/O error during export
Cause: The export operation failed because of an I/O error.
Action: Check OS logs and contact Oracle Support Services.
IMG-00701: unable to set the properties of an empty image
Cause: There is no data in the image object.
IMG-00702: unable to initialize image processing environment
Cause: The image processing external procedure initialization process failed.
IMG-00001 to IMG-02014 28-9
IMG-00703: unable to read image data

Cause: There is no image data in the image object.
IMG-00704: unable to read image data
Cause: There is no image data in the image object.
IMG-00705: unsupported or corrupted input format
IMG-00706: unsupported or corrupted output format
Cause: An error occurred while reading or writing image data.
Action: Contact your system administrator.
Cause: The destination image is invalid.
Action: Ensure that the SOURCE attribute of the destination image is initialized and
that you have sufficient tablespace.
IMG-00711: unable to set properties of destination image
Cause: The destination image is invalid.
Action: Ensure that the SOURCE attribute of the destination image is initialized and
that you have sufficient tablespace. Ensure the row containing the destination image
has been locked (this does not apply to temporary BLOBs).
IMG-00713: unsupported destination image format
Cause: A request was made to convert an image to a format that is not supported.
Action: Refer to the Oracle Multimedia Documentation for supported formats.
IMG-00714: internal error
IMG-00715: unable to open image stored in a BFILE
Cause: The image stored in a BFILE could not be opened for reading.
Action: Ensure that the access privileges of the image file and the image file's
directory allow read access.
IMG-00716: source image format does not support process options

Cause: A request was made to apply a processing option not supported by the source
image format.
Action: Refer to the Oracle Multimedia Documentation for a discussion of supported
processing options.
IMG-00717: destination image format does not support process options
Cause: A request was made to apply a processing option not supported by the
destination image format.
Action: Refer to the Oracle Multimedia Documentation for a discussion of supported
processing options.
IMG-00718: the same Temporary LOB cannot be used as both source and
destination
Cause: A call was made to processCopy with the same Temporary LOB being
specified as both the source and destination.
Action: Specify a different LOB for parameter "dest".
IMG-00719: image processing internal error
IMG-00720: image processing internal error
IMG-00721: unable to find source plug-in package
ORDPLUGINS.ORDX_string_SOURCE
Cause: Custom source plug-in for user-specified source type was not found.
Action: Ensure correct source type is specified or proper custom source plug-in
package is installed.
IMG-00722: incorrect value of bitsAllocated, bitsStored or highBit for output
Dicom image
Cause: incorrect value of bitsAllocated, bitsStored or highBit for output Dicom image.
Action: Ensure correct value of bitsAllocated, bitsStored or highBit for output Dicom
image.
IMG-00723: missing value in SHARPEN operation
Cause: An incorrect number of values was used to specify the sharpen parameters.
Action: Use one integer value to specify the kernel type and one float value to specify
the gain factor.
IMG-00724: extra value in SHARPEN operation
Cause: An incorrect number of values was used to specify the sharpen parameters.
Action: Use one integer value to specify the kernel type and one float value to specify
the gain factor.
IMG-00725: output image will be empty
Cause: The processing commands resulted in an empty output image.
Action: Ensure the resulting output image will not be empty.
IMG-00001 to IMG-02014 28-11
IMG-00726: invalid value for the AVI framerate

Cause: An invalid value was used to specify the AVI framerate parameter.
Action: Use a floating-point value to specify the AVI framerate parameter.
IMG-00727: invalid value for the AVI frametime
Cause: An invalid value was used to specify the AVI frametime parameter.
Action: Use a floating-point value to specify the AVI frametime parameter.
IMG-00728: multiple incompatible AVI frame parameters found
Cause: Multiple incompatible AVI frame parameters were found.
Action: Use only one AVI frame parameter.
IMG-00729: output format does not support the specified frame parameters
Cause: The specified frame parameter is not supported by the explicitly or implicitly
Action: Specify AVI as the output format in the process command string.
IMG-00730: unable to process empty image
Cause: There is no data in the input image object.
Action: Refer to the Oracle Multimedia documentation for information on how to put
image data into the image object.
IMG-00731: specified page could be found in input image
Cause: The specified page does not exist in the input image.
Action: Restrict the value of the page parameter to values specifying pages that exist
within the input image object.
IMG-00732: specified inputChannels could not be found in input image
Cause: The specified inputChannel parameter does not exist in the input image.
Action: Restrict the value of the inputChannels parameter to values specifying
channels that exist within the input image object.
IMG-00733: invalid watermark property setting
Cause: The specified watermark property setting is not supported by Oracle
Multimedia.
Action: See the Oracle Multimedia documentation for a description of valid
watermark property settings.
IMG-00734: invalid deflateLevel value
Cause: The specified value for the deflateLevel parameter was not supported by
Oracle Multimedia.
Action: See the Oracle Multimedia documentation for a description of the valid values
for the deflateLevel parameter.
IMG-00735: incorrect transparencyFillColor values
Cause: The specified value for the transparencyFillColor parameter was not
supported by Oracle Multimedia.
Action: See the Oracle Multimedia documentation for a description of the valid values
for the transparencyFillColor parameter.
IMG-00800: internal error while parsing attribute string

Cause: An internal error occurred while parsing the attribute string containing the
weights of the attributes.
Action: Check the command passed to the function. Refer to the Oracle Multimedia
documentation for a description of the correct usage and syntax for the attributes
string for image matching. If you are certain that your command is correct, then
IMG-00801: cannot extract height and width
Cause: Height and width are not set in the image object.
Action: Set the properties of the image object by calling setProperties and then
generate signature.
IMG-00802: empty or null attribute string
Cause: An empty or null attributes string was passed to the image matching
operators.
usage and syntax of the attributes string.
IMG-00803: invalid attribute value
Cause: An invalid value was found while parsing the attribute string for the image
matching operators.
usage and syntax for the attributes string. The weight values should be between 0.0
and 1.0.
IMG-00804: Syntax error in attribute string
Cause: A syntax error was found while parsing the attribute string for the image
matching operators.
usage and syntax of the attributes string.
IMG-00805: SIGNATURE data has been corrupted or is invalid
Cause: The data in the signature is not a valid signature.
Action: Re-create the signature using the generateSignature method.
IMG-00806: invalid input image
Cause: The image data is either corrupt or is in an unsupported format.
Action: Repopulate the image object, set properties of the image, and generate the
signature.
IMG-00807: no weights specified in weight string
Cause: All weights passed were zero. At least one attribute must be weighted.
Action: Specify a non-zero weight for at least one attribute
IMG-00808: unable to read an empty image
Cause: There is no data in the image object.
populate the image object with image data.
IMG-00001 to IMG-02014 28-13
IMG-00809: usage of IMGSimilar is incorrect

Cause: Syntax error while using IMGSimilar
Action: Refer to the Oracle Multimedia documentation for information on how to use
the IMGSimilar operator. Check whether the value returned by IMGSimilar is
compared to the value 1.
IMG-00810: boundary queue initialization failed
Cause: Operating system process memory has been exhausted while initializing the
boundary queue.
IMG-00811: fail queue initialization failed
Cause: Operating system process memory has been exhausted while initializin the fail
queue.
IMG-00812: merged area queue initialization failed
merged area queue.
IMG-00813: boundary queue free failed
Cause: An internal error has occured.
Action: Contact Oracle Support Services with the error number.
IMG-00814: fail queue free failed
IMG-00815: merged area queue free failed
IMG-00820: area 0 queue clear failed
IMG-00821: area N queue clear failed
IMG-00822: area queue reset failed
IMG-00823: boundary queue pop failed
IMG-00824: fail queue pop failed

IMG-00825: merged area queue pop failed
IMG-00830: boundary queue is full
Action: Contact Oracle Support Services with the error number and the image causing
this problem.
IMG-00831: boundary queue size exceeds expected size
this problem.
IMG-00832: fail queue is full
this problem.
IMG-00833: boundary queue size exceeds expected size
this problem.
IMG-00834: merged area queue is full
this problem.
IMG-00835: merged area queue size exceeds expected size
this problem.
IMG-00836: area queue merge failed
this problem.
IMG-00840: image structure allocation failed
image structure.
IMG-00001 to IMG-02014 28-15
IMG-00841: image data allocation failed

image data.
IMG-00842: image index allocation failed
image index.
IMG-00843: internal image structure allocation failed
internal image structure.
IMG-00844: internal image data allocation failed
internal image data.
IMG-00845: internal image index allocation failed
internal image index.
IMG-00846: adjacency matrix allocation failed
adjacency matrix.
IMG-00847: area list allocation failed
area list.
IMG-00850: image structure free failed
IMG-00851: image data free failed
IMG-00852: image index free failed

IMG-00853: internal image structure free failed
IMG-00854: internal image data free failed
IMG-00855: internal image index free failed
IMG-00856: adjacency matrix free failed
IMG-00857: area list free failed
IMG-00860: assert failure, number of region exceeds allocated
this problem.
IMG-00861: assert failure, inconsistency in area merge operation
this problem.
IMG-00862: assert failure, inconsistency in merged area labels
this problem.
IMG-00870: unsupported aspect ratio or image size
Cause: Signature generation was attempted on an image smaller than the supported
size.
Action: Try scaling the image up to have a larger height and width, the suggested size
is greater than 21 pixels each. If signature generation still fails, contact Oracle Support
Services with the error number and the image causing this problem.
IMG-00871: unexpected number of seeds
this problem.
IMG-00001 to IMG-02014 28-17
IMG-00872: unsupported image model

Cause: Signature generation was attempted on an image with an image model that
Oracle Multimedia is unable to support.
Action: Try scaling the image down. If signature generation still fails, contact Oracle
Support Services with the error number and the image causing this problem.
IMG-00899: signature cannot be generated
Cause: generateSignature could not generate the signature.
Action: Verify that the input image is a format supported by Oracle Multimedia.
IMG-00901: VIR signature version mismatch
Cause: Two signatures to be compared have different versions.
Action: Recompute signatures on the same platform and repeat signature comparison.
IMG-00902: VIR signature free failed
IMG-00910: allocation of basic data structure failed
image.
IMG-00911: free basic data structure failed
image.
IMG-00921: threshold out of range
Cause: Threshold is not between 0 and 100
Action: Use a threshold between 0 and 100 and retry query.
IMG-00922: location specified without feature
Cause: only location was specified.
Action: Specify at least one other parameter (color, texture or shape) along with
location. Refer to the Oracle Multimedia documentation for more details.
IMG-00923: signature is empty
Cause: Signature has not been generated.
Action: Generate the signature for the image by calling the generateSignature method.
IMG-00924: Incorrect parameter specification during CREATE INDEX
Cause: There is a spelling error, or duplicate parameter specification, or incorrect
specification of parameters while creating an index of type ORDIMAGEINDEX.
Action: Refer to the Oracle Multimedia documentation for correct specification of
CREATE INDEX parameters.
IMG-00925: unable to write to the ORDImageSignature object

Cause: The signature object was not valid and therefore the write operation failed.
This problem is commonly caused by an attempt to invoke the generateSignature
method on an uninitialized ORDImageSignature object.
Action: Ensure that the ORDImageSignature object has been initialized and inserted
into a table. Also ensure that the row containing the signature object is locked. (The
two previous actions do not apply to signature objects created using temporary
BLOBs). Ensure that there is sufficient tablespace to contain the signature.
IMG-00926: tablespace specified during CREATE INDEX is not valid
Cause: A tablespace specified in the parameter string of a CREATE INDEX operation
did not exist or the current user did not have sufficient privileges on the tablespace.
Action: Create the tablespace, grant appropriate privileges on the tablespace to the
current user, or choose a different tablespace.
IMG-01000: unsupported option string
Cause: The function was invoked with an invalid option string.
Action: Ensure that correct option string is passed to the PL/SQL function. Refer to
the Oracle Multimedia documentation for more information.
IMG-01001: not a DICOM object
Cause: The input was not a valid DICOM standalone object.
Action: Use an object that conforms to the DICOM standard. Refer to the Oracle
Multimedia documentation for more information.
IMG-01002: unsupported DICOM version
Cause: The object header could not be parsed, possibly because the object header did
not conform to the DICOM standard release 2003.
Action: Use an object that conforms to the DICOM standard release 2003. Refer to the
Oracle Multimedia documentation for more information.
IMG-01003: unsupported DICOM object type
Cause: The category of DICOM objects is not supported by Oracle Multimedia.
Action: Use a DICOM image is supported by Oracle Multimedia. Oracle Multimedia
supports image types defined in the DICOM standard release 2003. Refer to the
Oracle Multimedia documentation for more details.
IMG-01004: input DICOM object is not an image
Cause: The DICOM object was not a DICOM image. DICOM object types such as
structured reporting are not allowed by this function.
Action: Invoke this function with a DICOM image. Refer to the Oracle Multimedia
documentation for more details.
IMG-01005: unsupported DICOM transfer syntax
Cause: The operation failed because the transfer syntax in the DICOM object, which
describes the binary encoding of the DICOM object, was not supported by Oracle
Multimedia.
Action: Use a DICOM object with a transfer syntax supported by Oracle Multimedia.
Refer to the Oracle Multimedia documentation for more details.
IMG-00001 to IMG-02014 28-19
IMG-01006: DICOM object cannot be parsed

Cause: The DICOM object could not be parsed by Oracle Multimedia, possibly due to
an incorrect format or corrupted object.
Action: Verify that the DICOM object is not corrupted. If the DICOM object is valid,
IMG-02001: 2FF01 - incorrect image format
Cause: There was a SQL/MM Still Image exception. Either the supplied image BLOB
format did not match the image format or the image format is unsupported.
Action: For supported image formats, specify an input BLOB that has the same format
as the image. For unsupported image formats, this method is not supported. Refer to
the Oracle Multimedia documentation for more information.
IMG-02002: 2FF02 - incorrect average color feature specification
Cause: There was a SQL/MM Still Image exception. The specified average color value
was not a valid SI_Color value.
Action: Specify an average color value that is not null and contains valid SI_Color
values. SI_Color attribute values must be integers from 0 to 255. Refer to the Oracle
Multimedia documentation for more information on constructing valid SI_Color
objects.
IMG-02003: 2FF03 - incorrect color histogram feature specification
Cause: There was a SQL/MM Still Image exception. This exception was caused by
one of the following. - The specified color value was null or invalid. - The specified
frequency value was null or invalid. - The input color and frequency arrays were not
equal in size. - The SI_ColorList array attribute had reached the maximum size.
Action: Ensure that the following are true(as applicable to your case): - The color and
frequency values are not null. - The SI_Color attribute values are integers from 0 to
255. - The frequency value is a double precision number from 0 to 100. - The color and
frequency arrays are equal in size and the size of the arrays is less than the
SI_MaxHistogramLength value listed in the SI_VALUES view in the
SI_INFORMTN_SCHEMA. Refer to the Oracle Multimedia documentation for more
information on constructing SI_ColorHistogram objects.
IMG-02004: 2FF04 - incorrect feature list specification
Cause: There was a SQL/MM Still Image exception. Either the specified feature
values were invalid or the specified feature weights were invalid.
Action: Check the values of feature and featureweight pairs. For a non null feature
value, the corresponding feature weight value must be a double precision number
greater than 0.0. Refer to the Oracle Multimedia documentation for more information
on the SI_FeatureList object type and its methods.
IMG-02005: 2FF05 - incorrect color specification
Cause: There was a SQL/MM Still Image exception. The specified red/green/blue
value was null or invalid.
Action: Specify red, green and blue values as integers from 0 to 255.
IMG-02006: 2FF06 - average color feature cannot be determined
Cause: There was a SQL/MM Still Image exception. Either the specified image was
null, the image data in the specified image was null, or the average color feature was
not supported by the specified image format
Action: Specify an image with non null image data and a supported format. Refer to
the SI_INFORMTN_SCHEMA views and the Oracle Multimedia documentation for a
list of supported image formats and image features.
IMG-02007: 2FF07 - positional color feature cannot be determined
null, the image data in the specified image was null, or the positional color feature
was not supported by the specified image format.
list of supported image features and formats.
IMG-02008: 2FF08 - color histogram feature cannot be determined
null, the image data in the specified image was null, or the color histogram feature
was not supported by the specified image format.
Action: Specify an image with non null image data and a supported format Refer to
IMG-02009: 2FF09 - texture feature cannot be determined
null, the image data in the specified image was null, or the texture feature was not
supported by the specified image format.
IMG-02010: 2FF10 - illegal image format specification
Cause: There was a SQL/MM Still Image exception. The specified format name was
null or invalid.
Action: Specify a format name that is not null. For supported image formats, specify a
format name that matches the image BLOB format. For unsupported image formats,
specify a format name that is not listed as supported image format. Refer to the
SI_INFORMTN_SCHEMA views and the Oracle Multimedia documentation for a list
of supported image formats.
IMG-02011: 2FF11 - unsupported image format conversion specified
Cause: There was a SQL/MM Still Image exception. Either the specified target format
value was null, the specified image had a null format value, or the conversion from
the specified image format to the specified target format was not supported.
Action: Specify an image with a supported image format and specify a target format
value that is supported for conversion. Refer to the SI_INFORMTN_SCHEMA views
and the Oracle Multimedia documentation for a list of supported image format
conversions.
IMG-02012: 2FF12 - illegal specification for thumbnail generation
Cause: There was a SQL/MM Still Image exception. Either the specified image format
did not support thumbnail generation, the specified thumbnail height or width was
greater than the image height or width respectively, or the default thumbnail size 80
X 80 was greater than the image height or width respectively.
Action: Specify an image for which thumbnail generation is supported and specify
thumbnail height and width values that are less than the image height and width
IMG-00001 to IMG-02014 28-21
values. Refer to the SI_INFORMTN_SCHEMA views and the Oracle Multimedia

documentation for a list of supported thumbnail formats.
IMG-02014: 2202D Data exception - Null image value
Cause: There was a SQL/MM Still Image exception. The function was invoked using
a null image value.
Action: Specify an image whose image data is not null. Refer to the Oracle
Multimedia documentation for more information on constructing SI_StillImage
objects.
29
IMP-00000 to IMP-00402
IMP-00000: Import terminated unsuccessfully\n
Cause: Import encountered an Oracle error.
this manual, and take appropriate action.
IMP-00001: respond with either string, string, RETURN or '.' to quit
Cause: An invalid response was entered.
Action: Enter any of the responses shown in the message.
IMP-00002: failed to open string for read
Cause: Import failed to open the export file for reading. This message is usually
followed by a device message from the operating system.
IMP-00003: ORACLE error number encountered
Cause: Import encountered the referenced Oracle error.
Action: Look up the Oracle message in the ORA message chapters of this manual, and
IMP-00004: invalid username or password\n
Cause: An invalid username or password was specified.
Action: Retry with a valid username and password.
IMP-00005: all allowable logon attempts failed
Cause: An attempt was repeatedly made to log on with an invalid username or
password.
Action: Retry with valid username and password.
IMP-00006: failed to allocate memory of size number
Cause: Import failed to allocate the necessary memory.
Action: Decrease the import buffer size so that less memory is required, or increase
the runtime memory size for Import.
IMP-00007: must be a DBA to import objects to another user's account
Cause: The privileges needed to import into another user's account do not exist. Only
a database administrator can import into another user's account.
Action: Ask the database administrator to do the import.
IMP-00000 to IMP-00402 29-1
IMP-00008: unrecognized statement in the export file: \n string

Cause: Import did not recognize a statement in the export file. Either the export file
was corrupted, or an Import internal error has occurred.
Action: If the export file was corrupted, retry with a new export file. Otherwise,
report this as an Import internal error and submit the export file to customer support.
IMP-00009: abnormal end of export file
Cause: The export file is probably from an aborted Export session.
Action: If so, retry the export and import. Otherwise, report this as an Import bug and
submit the export file that caused this error to customer support.
IMP-00010: not a valid export file, header failed verification
Cause: Either the file was not generated by Export or it was corrupted.
Action: If the file was indeed generated by Export, report this an Import bug and
submit the export file to customer support.
IMP-00011: formatted table data not currently supported
Cause: You tried to import an export file that contains formatted table data. Import
only supports export files containing binary table data. wher
Action: Retry using an export file that contains only binary table data.
IMP-00012: invalid export mode (character) in header
Cause: The Export mode specified in the export file header is invalid.
Action: Check the export file to see if it was corrupted. If it was not, report this as an
Import bug and submit the export file to customer support.
IMP-00013: only a DBA can import a file exported by another DBA
Cause: The privileges needed to Import an export file generated by a database
administrator do not exist. Only a database administrator can import such files.
Action: Ask the database administrator to do the import.
IMP-00014: option "string" is needed, but not present in database
Cause: The command entered requires the specified option. Either that option is not
installed, or the row describing the option is missing from table V$OPTION
Action: Reinstall Oracle with the option specified by the message.
IMP-00015: following statement failed because the object already exists:
Cause: Import failed to create an object because it already exists.
Action: Specify IGNORE=Y to ignore such errors and import rows even when tables
are not created because they already exist.
IMP-00016: required character set conversion (type number to number) not
supported
Cause: Import could not convert the character format of the export file into the native
character format.
Action: Change the user character set by setting the NLS_LANG environment
variable to match the character set of the export file.
IMP-00017: following statement failed with ORACLE error number:
Cause: Import failed to execute the statement from the export file because of an
Oracle error.
29-2 Error Messages
IMP-00018: partial import of previous table completed: number rows imported
Cause: A table was only partially imported because of an Oracle error.
IMP-00019: row rejected due to ORACLE error number
Cause: Import encountered the referenced Oracle error while trying to import a row.
IMP-00020: long column too large for column buffer size (number)
Cause: The column buffer is too small. This usually occurs when importing LONG
data.
Action: Increase the insert buffer size 10,000 bytes at a time (for example). Use this
step-by-step approach because a buffer size that is too large may cause a similar
problem.
IMP-00021: INCTYPE parameter is obsolete
Cause: Import encountered the INCTYPE parameter when parsing Import options.
Incremental Imports are no longer supported.
Action: Consult the Oracle Backup and Recovery guide. Import will attempt to
continue.
IMP-00022: failed to process parameters, type 'IMP HELP=Y' for help
Cause: Invalid command-line parameters were specified.
Action: Check the online help screen for the set of valid parameters, then retry.
IMP-00023: Import views not installed, please notify your DBA
Cause: The necessary Import views were not installed.
Action: Ask your database administrator to install the required Import views.
IMP-00024: Only one mode (TABLES, FROMUSER, or FULL) can be specified
Cause: Parameters were specified that conflict with the import specification FULL=Y.
Action: Retry, making sure not to specify FULL=Y.
IMP-00025: for DBA export files, FROMUSER must be specified with TOUSER
option
Cause: When importing a database administrator export file, you specified the
TOUSER parameter but not the FROMUSER parameter.
Action: Specify the FROMUSER parameter so that Import knows which user's objects
to import.
IMP-00027: failed to rollback partial import of previous table
Cause: Import encountered an Oracle error while trying to roll back a partial import.
this manual and take appropriate action. Then, log on to Oracle and check that the
partial import was not committed.
IMP-00000 to IMP-00402 29-3
IMP-00028: partial import of previous table rolled back: number rows rolled back
Cause: Import encountered an Oracle error while trying to import a table.
this manual and take appropriate action. Then, if necessary, re-import the table.
IMP-00029: cannot qualify table name by owner (string), use FROMUSER
parameter
Cause: A table name was qualified with the name of its owner, as shown in the
following example. This is not allowed. IMP SYSTEM/MANAGER
TABLES=(SCOTT.EMP)
Action: Use the FROMUSER parameter to specify the table's owner, as shown in the
following example: IMP SYSTEM/MANAGER FROMUSER=SCOTT TABLES=(EMP,
DEPT)
IMP-00030: failed to create file string for write
Cause: Import was unable to create the specified file with write enabled.
Action: Check the file name and file system for the source of the error.
IMP-00031: Must specify FULL=Y or provide FROMUSER/TOUSER or TABLES
arguments
Cause: The database administrator did not specify full or partial import.
Action: The database administrator must specify FROMUSER/TOUSER or table
arguments if not a full import.
IMP-00032: SQL statement exceeded buffer length
Cause: The buffer was too small for the SQL statement being read.
Action: Rerun with a larger buffer. This can also be an indication of a corruption in
the import datafile.
IMP-00033: Warning: Table "string" not found in export file
Cause: A table name was specified that does not exist in export file.
Action: Correct the table specification.
IMP-00034: Warning: FromUser "string" not found in export file
Cause: The user specified a FROMUSER name that does not exist in export file.
Action: Correct the FROMUSER specification.
IMP-00035: input file string must be on a disk
Cause: On some platforms, import can read files from tape. This message is displayed
if the first file in an export file set was on disk and you specified a tape device for a
second or subsequent file.
Action: Verify that you have specified the correct file name for the import file.
Remember that all input files can be either on disk or all files can be on tape, but not
mixed both tape and disk.
IMP-00036: Could not find environment character set
Cause: An environment character set was specified that was not recognized by the
Import utility.
Action: Ensure that the spelling of the character set specified in the command line
parameter CHARSET (for Release 6 only) or the environment variable NLS_LANG is
correct.
29-4 Error Messages
IMP-00037: Character set marker unknown

Cause: The export file is corrupted.
Action: Try to obtain an uncorrupted version of the export file. If the export file is not
corrupted, report this as an Import internal error and submit the export file to
customer support.
IMP-00038: Could not convert to environment character set's handle
Action: Contact Worldwide Support.
IMP-00039: VOLSIZE does not match the value used for export: string
Cause: The value specified for VOLSIZE does not match the value specified during
the creation of the export file.
Action: If you believe that the specified VOLSIZE value is correct, verify that you
specified the correct file for import. If you specified the correct file but are unsure
about the correct value, re-execute the import command but specify VOLSIZE=0.
IMP-00040: FILESIZE does not match the value used for export: string
Cause: The value specified for FILESIZE does not match the value specified during
the creation of the export file.
Action: If you believe the specified FILESIZE value is correct, verify that you specified
the correct file for import. If you specified the correct file but are unsure about the
correct value, re-execute the import command but specify FILESIZE=0.
IMP-00041: Warning: object created with compilation warnings
Cause: The object in the SQL statement following this error was created with
compilation errors. If this error occurred for a view, it is possible that the base table of
the view was missing.
Action: This is a warning. The object may have to be recompiled before being used.
IMP-00042: CHARSET used, but the export file has specific character set
Cause: The user requested that a specific character set be used to process an export
file that has a specific embedded character set ID. The ID in the export file is accurate
and should be used.
Action: Remove the CHARSET keyword from the command line.
IMP-00043: export file character set inconsistent
Cause: The character set of the export file and the environment character set (or the
character set specified with the CHARSET keyword) are inconsistent. One character
set is ASCII-based while the other is EBCDIC based.
Action: Specify the correct character set with the CHARSET keyword.
IMP-00044: unable to allocate enough memory for statement
Cause: Import was unable to allocate sufficient memory to read in the specified
statement and execute it.
Action: Increase the allocation for database buffers, restart the instance, and reexecute
the Import command.
IMP-00000 to IMP-00402 29-5
IMP-00045: using VOLSIZE value from export file of string

Cause: Either you did not specify the VOLSIZE parameter in your IMPORT
command, or you specified VOLSIZE=0 and the export was created with a non-zero
value for VOLSIZE. Import will use the value specified in the export file.
IMP-00046: using FILESIZE value from export file of string
Cause: Either you did not specify the FILESIZE parameter in your IMPORT
command, or you specified FILESIZE=0 and the export file was created with a nonzero value for FILESIZE. Import will use the value specified in the export file.
IMP-00047: unexpected file sequence number; expected number but found number
Cause: The header in the export file contains a sequence number that is used to track
the order in which multiple export files are written. The first export file is assigned
sequence number one, the second file is assigned sequence number two and so on.
This message is displayed when a number other than the expected sequence number
is found in the file header
Action: Execute the import command again, but specify the files in the order in which
Export wrote them.
IMP-00048: mismatched file header
Cause: During verification of the 2nd or subsequent file in a multi-file export, Import
found header fields in the file that did not match values in the first file.
Action: Check the names of the files created by Export and verify that you specified
them correctly for the import operation.
IMP-00049: Unknown language specified in CHARSET
Cause: An unknown language was listed in the CHARSET option.
Action: Use a known character set.
IMP-00050: Dump file and log file cannot be identical
Cause: Identical names were given to the dump file and log file.
Action: Specify different names for the dump file and log file and retry the operation.
IMP-00051: Direct path exported dump file contains illegal column length
Cause: An invalid column length was encountered while processing column pieces."
Action: Check to make sure the export file is not corrupted, or else report this to
Oracle Worldwide Support as an Import/Export internal bug and submit the export
file.
IMP-00052: Warning: Unable to set event for freelist communication with server
Cause: An event could not be set for current the session.
Action: If Import fails, give the Import user ALTER SESSION PRIV and retry the
operation.
IMP-00053: Import mode incompatible with Export dump file
Cause: The specified import option is incompatible with point-in-time- recovery
dump file.
Action: Generate a proper dump file or use point-in-time-recovery import mode.
29-6 Error Messages
IMP-00054: must be connected 'AS SYSDBA' to do Point-in-time Recovery or

Transportable Tablespace import
Cause: The user must log in 'as SYSDBA' to perform transportable tablespace imports
or Point-In-Time Recovery imports.
Action: Ask your database adminstrator to perform the Transportable Tablespace
import or the Tablespace Point-in-time Recovery import.
IMP-00055: Warning: partition or subpartition "string":"string" not found in export
file
Cause: A partition or subpartition name was specified that does not exist in export
file.
Action: Check to make sure the partition or subpartition name belongs to the table.
IMP-00056: multiple devices specified for tape input
Cause: You specified multiple file names when doing an import from a tape device.
Import uses the same device for reading all tapes, regardless of the number of tape
volumes required. For this reason, export will accept only one value for the FILE
parameter when writing to tape.
Action: Reenter the IMPORT command, but specify only one tape device in the FILE
parameter.
IMP-00057: Warning: Dump file may not contain data of all partitions of this table
Cause: The dump file used for this Table Import might not contain all of the data
belonging to the exported table.
Action: Check to see if the export was done as intended, or try performing a Partition
Import.
IMP-00059: Failure to initialize parameter manager
Cause: Parameter manager failed in initialization.
Action: Report this to Oracle Worldwide Support as an Import internal bug.
IMP-00060: Warning: Skipping table "string"."string" because object type
"string"."string" does not exist or has different identifier
Cause: An object type needed by the table, either does not exist on the * target system
or, if it does exist, it has a different object identifier.
Action: Create the object type on the target system with a valid * identifier.
IMP-00061: Warning: Object type "string"."string" already exists with a different
identifier
Cause: An object type cannot be created because it already exists on the * target
system, but with a different identifier
Action: Drop the object type from the target system and retry the operation.
IMP-00062: Warning: The identifier on the dump file for object type
"string"."string" is invalid
Cause: The character string representing the object type's identifier * could not be
converted to an object identifier.
Action: Internal error.
IMP-00000 to IMP-00402 29-7
IMP-00063: Warning: Skipping table "string"."string" because object type

"string"."string" cannot be created or has different identifier
Cause: An error occurred creating an object type that is used by the * table.
Action: Examine the import log to determine why the object type could not * be
created. If the object type already existed, with a * different object identifier, then drop
the object type and * retry the import.
IMP-00064: Definition of LOB was truncated by export
Cause: While producing the dump file, Export was unable to write the * entire
contents of a LOB. Import is therefore unable to * reconstruct the contents of the LOB.
The remainder of the * import of the current table will be skipped.
Action: Delete the offending row in the exported database and retry the * export.
IMP-00065: Import is unable to recreate lobs within objects.
Cause: An error occurred recreating a LOB within an imported object.
Action: Report this to Oracle Worldwide Support as an Import internal error.
IMP-00066: Missing NLS_CHARACTERSET in props$
Cause: No value for NLS_CHARACTERSET in props$.
IMP-00067: Could not convert to server character set's handle
IMP-00068: Could not find environment national character set
Cause: An environment national character set was specified that was not recognized
by the Import utility.
Action: Ensure that the spelling of the national character set specified in the
environment variable NLS_NCHAR is correct.
IMP-00069: Could not convert to environment national character set's handle
Cause: Internal error..
IMP-00070: Lob definitions in dump file are inconsistent with database.
Cause: The number of LOBS per row in the dump file is different than the * number of
LOBS per row in the table being populated.
Action: Modify the table being imported so that it matches the column * attribute
layout of the table that was exported.
IMP-00071: Object identifier of imported table mismatches object identifier of
existing table
Cause: An attempt was made to import data into a table that was recreated under a
different object identifier than the object identifier used for the exported object table.
Under this situation, REF's to this table that are contained within the dump file will
also be invalid.
Action: Drop the offending object table prior to import.
29-8 Error Messages
IMP-00072: Warning: The object table's object identifier is invalid.

Cause: The character string representing the table's object identifier could not be
converted to an internal object identifier.
IMP-00073: FILE locator "string" "string" is truncated to "string" "string" in server
character set
Cause: The conversion of the specified directory and name strings for a file attribute
or column from the export server's character set into the import server's character set
exceeded the maximum string lengths allowed within FILE descriptors. The strings
will be truncated to the maximum supported lengths.
Action: Rename the directory aliases and external filenames to match the truncated
names in the specified FILE column or attribute.
IMP-00074: The constraints flagged by ALL_CONSTRAINTS.BAD will break in
2000 A.D.
Cause: Constraints exist in the data base that specify date values without fully
specifying the year. These constraints could break in the year 2000 A.D.
Action: Query ALL_CONSTRAINTS and correct those constraints marked as bad.
IMP-00075: Warning: The nested table may contain partial rows or duplicate rows
Cause: An error occurred inserting data into an outer or inner nested table. If the error
occurred in the outer table, rows are still inserted into the inner tables. If the error
occurred in an inner table, data is still inserted into the outer table and other inner
tables. This can result in duplicate inner table rows or partial logical rows.
Action: Examine the data in the tables. Delete the incorrect rows or drop the entire
table and perform the import again.
IMP-00076: Missing NLS_NCHAR_CHARACTERSET in props$
Cause: No value for NLS_NCHAR_CHARACTERSET in props$.
IMP-00077: Could not convert to server national character set's handle
IMP-00078: Cannot translate FILE locator to "string" "string" in server character set
Cause: (1) The current export dump file was generated using Beta-2 of Oracle8.0 AND
(2) there was a File that appeared as an an attribute of an ADT within a table's column
AND (3) the character set of the export server's database was different than the
character set of the import server's database AND (4) when the filename or the
aliasname of the File increased in size when it was translated to the character set of
the import server. When all of these conditions are true, translation of the strings
could yield corruption of the data in the column. Rather than proceeding with the
translation, import will leave the character strings in the File in the old character set.
Action: After import completes, rename the directory aliases and external filenames to
match the real names used for the target database.
IMP-00079: Warning: National character set data in this table may be incorrect
Cause: Due to a problem in 8.0.2 Export, national character data in NCHAR and
NVARCHAR2 columns was incorrectly assumed to be in the export server's data base
character set and was converted to the export client's data base character set. This
IMP-00000 to IMP-00402 29-9
conversion would only be correct if the export server's data base character set was the
same as the export server's national character set and the export client's data base
character set was the same as the export client's national character set. All other
combinations would likely be incorrect. This export dump file was generated by 8.0.2
Export and the export client and server characater sets did not fit that criteria.
Action: Examine the national character data. If incorrect, update the data with correct
data.
IMP-00080: Error during character conversion of long column or long command
Cause: During piecewise character conversion of the data in a long column or of a
long command, a fatal conversion error occurred. Either character truncation
occurred or an invalid character set handle was used.
Action: Retry the import with a different character set.
IMP-00081: attempt to free unallocated memory
Cause: An attempt was made to free memory that was not allocated.
IMP-00082: Error during conversion ROWID from string format to internal
Cause: An error occured while attempting to to convert a ROWID from an export
dump file into an internal format.
Action: Report this to Oracle Worldwide Support as an Import internal error.
IMP-00083: dump file does not contain an incremental export
Cause: An incremental import was requested and the dump file specified for the
import command is either a user or table export.
Action: Reissue the command import command but specify the name of a dump file
containing an incremental export.
IMP-00084: attempt to mix incremental import with user or table import
Cause: An incremental import was requested along with the FROMUSER, TOUSER,
or TABLE qualifier. An incremental import cannot be done if any of these other
qualifiers are also specified.
Action: Determine whether you want to do an incremental import, full import, user
import or table import and reissue the import command with the appropriate
qualifiers.
IMP-00085: multiple input files specified for unbounded export file
Cause: You specified multiple file names for the FILE parameter when doing an
import, but the header in the export file indicates that that the export operation could
create only one file. Specifying multiple file names is valid for an import operation
only if the export files were created by an export operation in which the user specified
a non-zero value for the FILESIZE parameter.
Action: If you believe the export contains multiple files, verify that you have specified
the correct files. If you believe the export should be in only one file then try the
import operation again, but specify only one value for the FILE parameter.
IMP-00086: TOID "string" not found in export file
Cause: Import did not find the type identification specified in the
TOID_NOVALIDATE parameter. The specified type identification does not exist in
export file.
Action: Correct or omit the TOID_NOVALIDATE parameter.
IMP-00087: Problem with internal hash table of schema/table names

Cause: Most likely a problem with allocating memory for the hash table entries.
IMP-00088: Problem importing metadata for index string. Index creation will be
skipped
Cause: Domain indexes import private metadata via anonymous PL/SQL blocks
prior to the CREATE INDEX statement. The execution of one of these PL/SQL blocks
failed. Because the metadata is considered an integral part of the index, the
subsequent CREATE INDEX statement was skipped.
Action: Contact the developer of the index's implementation type. If this is an Oraclesupplied index (perhaps via a data cartridge), contact Oracle Worldwide Support.
IMP-00089: Fine grain policy "string" not recreated on table/view "string"
Cause: Import user fails to recreate fine grained policies of the table/view being
imported. To recreate the policy, the user doing the import needs execute privilege on
the package DBMS_RLS for access policies or DBMS_FGA for audit policies.
Action: Ask the database administrator to perform the export/import of this table/
view.
IMP-00090: Unexpected DbmsJava error number at step number while creating
string
Cause: The error was returned from a call to a DbmsJava procedure.
Action: Record the accompanying messages and report this as an Import internal
IMP-00091: Above error occurred on the following function and object: string.
Remaining PL/SQL blocks for this object will be skipped.
Cause: An error occurred while executing a PL/SQL block that implements the DDL
for the named function and procedural object. A procedural object is one whose DDL
is implemented as stored procedures rather than as standard SQL statements.
Action: Contact Oracle Worldwide Support so they may determine the development
group responsible for the package that failed.
IMP-00092: Java object "string"."string" already exists, cannot be created
Cause: Import failed to create the Java source, class or resource object because it
already exists.
IMP-00093: Inconsistency between dumpfile constraint definition for table string
with columns (string)
Cause: Import failed to locate a base table for a constraint that was defined in the
dump file and statistics were not imported.
Action: Check to see if the table and constraint exist. If the table and constraint exist,
then report this to Oracle Support Services as an Import internal error.
IMP-00094: Warning: The identifier on the dump file for object type
"string"."string" is invalid
converted.
IMP-00000 to IMP-00402 29-11
IMP-00095: Resumable parameters ignored -- current session not resumable

Cause: Current session is not resumable.
Action: Must specify RESUMABLE=Y to enable resumable session in order for the
RESUMABLE_NAME and RESUMABLE_TIMEOUT parameters to take effect.
IMP-00096: Warning: Skipping table "string"."string" because type synonym
"string"."string" cannot be created
Cause: An error occurred creating a synonym for a type that is used by the * table.
Action: Examine the import log to determine why the type synonym could * not be
created. If the synonym already existed, but is not * needed, then drop the synonym
and retry the import. If the * synonym is PUBLIC but the importer does not have the *
CREATE PUBLIC SYNONYM system privilege, then the import must * be done by
someone possessing that privilege, or the importer * must be granted the privilege.
IMP-00097: \nSTREAMS_CONFIGURATION=Y ignored, only valid with FULL=Y
Cause: STREAMS_CONFIGURATION=Y can only be used * when FULL=Y is present
on the command line
Action: Remove conflicting command arguments
IMP-00098: INTERNAL ERROR: string
Cause: An INTERNAL error occurred.
IMP-00099: Warning: The typeid in the dump file for object type "string"."string" is
invalid
converted.
IMP-00400: Warning: Object type "string"."string" already exists with a different
typeid
Cause: An object type could not be created because it already existed on the * target
system, but with a different typeid
IMP-00401: dump file "string" may be an Data Pump export dump file
Cause: A dump file was specified for an import operation which appears to have been
created using the Data Pump export utility. These dump files cannot be processed by
the original import utility.
Action: Try using the Data Pump import utility to process this dump file.
IMP-00402: Invalid parameter "string" with data_only mode
Cause: Parameter provided along data_only is invalid.
Action: Remove the invalid parameter from command line.
30
JMS-00101 to JMS-00256
JMS-00101: Invalid delivery mode {0}
Cause: The delivery mode is not supported
Action: The valid delivery mode is AQjmsConstants.PERSISTENT or
AQjmsConstants.NON_PERSISTENT
JMS-00102: Feature not supported {0}
Cause: This feature is not supported in the current release
Action: n/a
JMS-00104: Message Payload must be specified
Cause: The message payload was null
Action: Specify a non-null payload for the message
JMS-00105: Agent must be specified
Cause: AQjmsAgent object was null
Action: Specify a valid AQjmsAgent representing the remote subscriber
JMS-00106: Cannot have more than one open Session on a JMSConnection
Cause: There is already one open jms session on the connection Cannot have more
than one open session on a connection
Action: Close the open session and then open a new one
JMS-00107: Operation not allowed on {0}
Cause: The specified operation is not allowed on this object
Action: n/a
JMS-00108: Messages of type {0} not allowed with Destinations containing payload
of type {1}
Cause: There was a mismatch between the message type being used and the payload
type specified for the destination
Action: Use the message type that maps to the payload specified for the queue table
that contains this destination
JMS-00109: Class not found: {0}
Cause: The specified class was not found
Action: Make sure your CLASSPATH contains the class
JMS-00110: Property {0} not writeable
Cause: An attempt was made to update a read-only message header field or property
Action: n/a
JMS-00101 to JMS-00256 30-1
JMS-00111: Connection must be specified

Cause: The connection object was null
Action: Specify a non-null jdbc connection
JMS-00112: Connection is invalid
Cause: The jdbc connection is invalid
Action: Specify a non-null oracle jdbc connection
JMS-00113: Connection is in stopped state
Cause: An attempt was made to receive messages on a connection that is in stopped
state
Action: Start the connection
JMS-00114: Connection is closed
Cause: An attempt was made to use a Connection that has been closed
Action: Create a new connection
JMS-00115: Consumer is closed
Cause: An attempt was mode to use a Consumer that has been closed
Action: Create a new Message Consumer
JMS-00116: Subscriber name must be specified
Cause: Subscriber name was null
Action: Specify a non-null subscription name
JMS-00117: Conversion failed - invalid property type
Cause: An error occurred while converting the property to the requested type
Action: Use the method corresponding to the property data type to retrieve it
JMS-00119: Invalid Property value
Cause: The property value specified is invalid
Action: Use an appropriate type of value for the property being set
JMS-00120: Dequeue failed
Cause: An error occurred while receiving the message
Action: See message inside the JMSException and linked SQLException for more
information
JMS-00121: DestinationProperty must be specified
Cause: A null AQjmsDestinationProperty was specified while creating a queue/topic
Action: Specify a non-null AQjmsDestinationProperty for the destination
JMS-00123: Interval must be at least {0} seconds
Cause: An invalid interval was specified
Action: Specify an interval value that is greater than or equal to 1 second
JMS-00124: Invalid Dequeue mode
Cause: Invalid dequeue mode was specified
Action: Valid Dequeue modes are AQConstants.DEQUEUE_BROWSE,
AQConstants.DEQUEUE_REMOVE, AQConstants.DEQUEUE_LOCKED,
AQConstants.DEQUEUE_REMOVE_NODATA
30-2 Error Messages
JMS-00125: Invalid Queue specified

Cause: An invalid Queue object was specified
Action: Specify a valid Queue handle
JMS-00126: Invalid Topic specified
Cause: An invalid Topic object was specified
Action: Specify a valid Topic handle
JMS-00127: Invalid Destination
Cause: An invalid destination object was specified
Action: Specify a valid destination (Queue/Topic) object
JMS-00128: Invalid Navigation mode
Cause: An invalid navigation mode was specified
Action: The valid navigation modes are
AQjmsConstants.NAVIGATION_FIRST_MESSAGE,
AQjmsConstants.NAVIGATION_NEXT_MESSAGE,
AQjmsConstants.NAVIGATION_NEXT_TRANSACTION
JMS-00129: Invalid Payload type
Cause: There was a mismatch between the message type being used and the payload
type specified for the destination
Action: Use the message type that maps to the payload specified for the queue table
that contains this destination. For ADT messages, use the appropriate
CustomDatum/ORAData factory to create the message consumer
JMS-00130: JMS queue cannot be multi-consumer enabled
Cause: An attempt was made to get an AQ multi-consumer queue as a JMS queue
Action: JMS queues cannot be multi-consumer enabled
JMS-00131: Session is closed
Cause: An attempt was made to use a session that has been closed
Action: Open a new session
JMS-00132: Maximum number of properties (100) exceeded, message has {0}
properties
Cause: Maximum number of properties (100), including provider-specific properties,
for the message has been exceeded
Action: Reduce the number of user defined properties
JMS-00133: Message must be specified
Cause: Message specified was null
Action: Specify a non-null message
JMS-00134: Name must be specified
Cause: Queue or Queue table Name specified was null
Action: Specify a non-null name
JMS-00135: Driver {0} not supported
Cause: The specified driver is not supported
JMS-00101 to JMS-00256 30-3
Action: Valid drivers are oci8 and thin. To use the kprb driver get the kprb connection
using getDefaultConnection() and use the static createTopicConnection and
createQueueConnection methods
JMS-00136: Payload factory can only be specified for destinations with ADT
payloads
Cause: A CustomDatumFactory/ORADataFactory was specified for consumers on
destinations not containing ADT payloads
Action: This field must be set to null for destinations containing payloads of type
SYS.AQ$_JMS_TEXT_MESSAGE, SYS.AQ$_JMS_BYTES_MESSAGE , SYS.AQ
$_JMS_MAP_MESSAGE, SYS.AQ$_JMS_OBJECT_MESSAGE, SYS.AQ
$_JMS_STREAM_MESSAGE
JMS-00137: Payload factory must be specified for destinations with ADT payloads
Cause: CustomDatumFactory/ORADataFactory was not specified for destinations
containing ADT payloads
Action: For destinations containing ADT messages, a CustomDatumFactory/
ORADataFactory for a java class that maps to the SQL ADT type of the destination
must be specified
JMS-00138: Producer is closed
Cause: An attempt was made to use a producer that has been closed
Action: Create a new Message Producer
JMS-00139: Property name must be specified
Cause: Property name was null
Action: Specify a non-null property name
JMS-00140: Invalid System property
Cause: Invalid system property name specified.
Action: Specify one of the valid JMS system properties
JMS-00142: JMS topic must be created in multi-consumer enabled queue tables
Cause: An attempt was made to create a JMS topic in a single-consumer queue table
Action: JMS topics can only be created in queue tables that are multi-consumer
enabled
JMS-00143: Queue must be specified
Cause: Null queue was specified
Action: Specify a non-null queue
JMS-00144: JMS queue cannot be created in multi-consumer enabled queue tables
Cause: An attempt was made to create a JMS queue in a multi-consumer queue table
Action: JMS queues can only be created in queue tables that are not multi-consumer
enabled
JMS-00145: Invalid recipient list
Cause: The recipient list specified was empty
Action: Specify a recipient list with at least one recipient
JMS-00146: Registration failed
Cause: An error occurred while registering the type in the type map
30-4 Error Messages
Action: n/a
JMS-00147: Invalid ReplyTo destination type,
Cause: The ReplyTo destination object is invalid
Action: The ReplyTo destination must be of type AQjmsAgent, or AQjmsDestination.
If AQjmsAgent is used, its "name" must not be "JMSReplyTo" (which is considered a
reserved name to be used for AQjmsDestination objects). If AQjmsDestination is
used, it must be serializable into a string (and vice-versa).
JMS-00148: Property name size exceeded
Cause: The property name is greater than the maximum size allowed
Action: Specify a property name that is less than 100 characters
JMS-00149: Subscriber must be specified
Cause: Subscriber specified was null
Action: Specify a non-null subscriber
JMS-00150: Property not supported
Cause: An attempt was made to use a property that is not supported
Action: n/a
JMS-00151: Topics cannot be of type EXCEPTION
Cause: Topics cannot be of type AQjmsConstants.EXCEPTION
Action: Specify topics to be of type AQjmsConstants.NORMAL
JMS-00153: Invalid System property type
Cause: The type of the value specified does not match the type defined for the system
property being set
Action: Use the correct type for the setting the system property
JMS-00154: Invalid value for sequence deviation
Cause: The sequence deviation is invalid
Action: Valid values are AQEnqueueOption.DEVIATION_BEFORE,
AQEnqueueOption.DEVIATION_TOP
JMS-00155: AQ Exception {0}
Cause: An error occurred in the AQ java layer
Action: See the message inside the JMSException and the linked exception for more
information
JMS-00156: Invalid Class {0}
Cause: Class specified is invalid
Action: make sure your CLASSPATH has the specified class
JMS-00157: IO Exception {0}
Cause: IO exception
Action: See message is JMSException for details
JMS-00158: SQL Exception {0}
Cause: SQL Exception
Action: See message inside linked SQLException for details
JMS-00101 to JMS-00256 30-5
JMS-00159: Invalid selector {0}

Cause: The selector specified is either invalid or too long
Action: Check the syntax of the selector
JMS-00160: EOF Exception {0}
Cause: EOF exception occurred while reading the byte stream
Action: n/a
JMS-00161: MessageFormat Exception: {0}
Cause: An error occurred while converting the stream data to specified type
Action: check the type of data expected on the stream and use the appropriate read
method
JMS-00162: Message not Readable
Cause: Message is in write-only mode
Action: Call the reset method to make the message readable
JMS-00163: Message not Writeable
Cause: Message is in read-only mode
Action: Use the clearBody method to make the message writeable
JMS-00164: No such element
Cause: Element with specified name was not found in the map message
Action: n/a
JMS-00165: Maximum size of property value exceeded
Cause: The property value exceeded the maximum length allowed
Action: Value for JMS defined properties can have a maximum length of 100, value
for User defined properties can have a maximum length of 2000
JMS-00166: Topic must be specified
Cause: Topic specified was null
Action: Specify a non-null topic
JMS-00167: Payload factory or Sql_data_class must be specified
Cause: Payload factory or Sql_data_class not specified for queues containing object
payloads
Action: Specify a CustomDatumFactory/ORADataFactory or the SQLData class of the
java object that maps to the ADT type defined for the queue.
JMS-00168: Cannot specify both payload factory and sql_data_class
Cause: Both CustomDatumFactory/ORADataFactory and SQLData class were
specified during dequeue
Action: Specify either the CustomDatumFactory/ORADataFactory or the SQLData
class of the java object that maps to the ADT type defined for the queue.
JMS-00169: Sql_data_class cannot be null
Cause: SQLData class specified is null
Action: Specify the SQLData class that maps to the ADT type defined for the queue
30-6 Error Messages
JMS-00171: Message is not defined to contain {0}

Cause: Invalid payload type in message
Action: Check if the queue is defined to contain RAW or OBJECT payloads and use
the appropriate payload type in the message
JMS-00172: More than one queue table matches query {0}
Cause: More than one queue table matches the query
Action: Specify both owner and queue table name
JMS-00173: Queue Table {0} not found
Cause: The specified queue table was not found
Action: Specify a valid queue table
JMS-00174: Class must be specified for queues with object payloads\n Use
dequeue(deq_option, payload_fact) or dequeue(deq_option, sql_data_cl)
Cause: This dequeue method cannot be used to dequeue from queues with OBJECT
payloads
Action: use the either dequeue(deq_option, payload_fact) or dequeue(deq_option,
sql_data_cl)
JMS-00175: DequeueOption must be specified
Cause: DequeueOption specified is null
Action: Specify a non-null dequeue option
JMS-00176: EnqueueOption must be specified
Cause: EnqueueOption specified is null
Action: Specify a non-null enqueue option
JMS-00177: Invalid payload type: Use dequeue(deq_option) for raw payload
queues
Cause: This method cannot be used to dequeue from queues with RAW payload
Action: use the dequeue(deq_option) method
JMS-00178: Invalid Queue name - {0}
Cause: The queue name specified is null or invalid
Action: Specify a queue name that is not null. The queue name must not be qualified
with the schema name. The schema name must be specified as the value of the owner
parameter
JMS-00179: Invalid Queue Table name - {0}
Cause: The queue table name specified is null or invalid
Action: Specify a queue table name that is not null. The queue table name must not be
qualified with the schema name. The schema name must be specified as the value of
the owner parameter
JMS-00180: Invalid Queue Type
Cause: Queue type is invalid
Action: Valid types are AQConstants.NORMAL or AQConstants.EXCEPTION
JMS-00181: Invalid value for wait_time
Cause: Invalid value for wait type
JMS-00101 to JMS-00256 30-7
Action: Wait time can be AQDequeueOption.WAIT_FOREVER,

AQDequeueOption.WAIT_NONE or any value greater than 0
JMS-00182: More than one queue matches query
Cause: More than one queue matches query
Action: Specify both the owner and name of the queue
JMS-00183: No AQ driver registered
Cause: No AQDriver registered
Action: Make sure that the AQ java driver is registered. Use
Class.forName("oracle.AQ.AQOracleDriver")
JMS-00184: Queue object is invalid
Cause: The queue object is invalid
Action: The underlying JDBC connection may have been closed. Get the queue handle
again
JMS-00185: QueueProperty must be specified
Cause: AQQueueProperty specified is null
Action: Specify a non-null AQQueueProperty
JMS-00186: QueueTableProperty must be specified
Cause: QueueTableProperty specified is null
Action: Specify a non-null AQQueueTableProperty
JMS-00187: Queue Table must be specified
Cause: Queue Table specified is null
Action: Specify a non-null queue table
JMS-00188: QueueTable object is invalid
Cause: The queue table object is invalid
Action: The underlying JDBC connection may have been closed. Get the queue table
handle again
JMS-00189: Byte array too small
Cause: The byte array given is too small to hold the data requested
Action: Specify a byte array that is large enough to hold the data requested or reduce
the length requested
JMS-00190: Queue {0} not found
Cause: The specified queue was not found
Action: Specify a valid queue
JMS-00191: sql_data_cl must be a class that implements SQLData interface
Cause: The class specified does not support the java.sql.SQLData interface
Action: n/a
JMS-00192: Invalid Visibility value
Cause: Visibility value specified is invalid
Action: Valid values areAQConstants.VISIBILITY_ONCOMMIT,
AQConstants.VISIBILITY_IMMEDIATE
30-8 Error Messages
JMS-00193: JMS queues cannot contain payload of type RAW

Cause: An attempt was made to create a JMS queue with RAW payload
Action: JMS queues/topics cannot contain RAW payload
JMS-00194: Session object is invalid
Cause: Session object is invalid
Action: The underlying JDBC connection may have been closed. Create a new session
JMS-00195: Invalid object type: object must implement CustomDatum/ORAData or
SQLData interface
Cause: Invalid object type specified
Action: object must implement CustomDatum/ORAData or SQLData interface
JMS-00196: Cannot have more than one open QueueBrowser for the same
destination on a JMS Session
Cause: There is already one open QueueBrowser for this queue on this session
Action: There cannot be more than one queue browser for the same queue in a
particular session. Close the existing QueueBrowser and then open a new one
JMS-00197: Agent address must be specified for remote subscriber
Cause: Address field is null for remote subscriber
Action: The address field must contain the fully qualified name of the remote topic
JMS-00199: Registration for asynchronous receipt of messages failed
Cause: Registration with the database for asynchronous receipt of messages for the
consumer failed
Action: See error message in linked Exception for details
JMS-00200: Destination must be specified
Cause: Destination is null
Action: Specify a non-null destination
JMS-00201: All Recipients in recipient_list must be specified
Cause: One or more elements in the recipient list are null
Action: All AQjmsAgents in the recipient list must be specified
JMS-00202: Unregister for asynchronous receipt of messages failed
Cause: An error occured while removing the registration of the consumer with the
database for asynchronous receipt
Action: n/a
JMS-00203: Payload Factory must be specified
Cause: Null Payload Factory was specified
Action: n/a
JMS-00204: An error occurred in the AQ JNI layer
Cause: JNI Error
Action: Check error message in linked exception for details
JMS-00205: Naming Exception
Cause: Naming exception
JMS-00101 to JMS-00256 30-9
Action: n/a
JMS-00207: JMS Exception {0}
Cause: An error occured in the JMS layer
Action: See the message inside the linked JMSException for more information
JMS-00208: XML SQL Exception
Cause: An error occured in the XML SQL layer
Action: See the message inside the linked AQxmlException for more information
JMS-00209: XML SAX Exception
Cause: An error occured in the XML SAX layer
JMS-00210: XML Parse Exception
Cause: An error occured in the XML Parser layer
JMS-00220: Connection no longer available
Cause: Connection to the database no longer available.
Action: n/a
JMS-00221: Free physical database connection unavailable in connection pool
Cause: A free physical database connection was not available in the OCI connection
pool in order to perform the specified operation.
Action: Try performing the operation later
JMS-00222: Invalid Payload factory type
Cause: Payload factory should be of CustomDatumFactory or ORADataFactory type.
Action: Use one of CustomDatumFactory/ORADataFactory types.
JMS-00223: Payload factory must be null for destinations with Sys.AnyData
payload - use typemap instead
Cause: A CustomDatumFactory/ORADataFactory was specifed for consumers on
destinations containing SYS.ANYDATA payloads
Action: This field must be set to null for destinations containing payloads of type
SYS.AnyData. The ORADataFactory(s) must be registered in the session's typemap
JMS-00224: Typemap is invalid - must be populated with SQLType/
OraDataFactory mappings to receive messages from Sys.AnyData destinations
Cause: The typemap of the session is null or empty. For destinations of tpye
Sys.AnyData, the typemap must contain OraDataFactory objects for all possible types
that may be stored in the queue/topic
Action: Use the AQjmsSession.getTypeMap() method get the typemap. Then use the
put() method to register SQLType names and their corresponding OraDataFactory
objects
JMS-00225: Invalid JDBC driver - OCI driver must be used for this operation
Cause: Operations on Sys.AnyData queues/topics are not supported using this JDBC
driver
Action: Use the JDBC OCI driver to receive messages from Sys.AnyData queues/
topics
JMS-00226: Header-only Message does not have a body

Cause: Header-only message does not have a body; the body cannot be cleared,
changed, or queried.
Action: Do not access or modify the body of a read-only message.
JMS-00227: Illegal attempt to commit on a non transacted JMS Session
Cause: Illegal attempt to invoke the commit method on a non transacted JMS Session
Action: Remove invocation of the commit method on the current JMS Session
JMS-00228: Illegal attempt to rollback on a non transacted JMS Session
Cause: Illegal attempt to invoke the rollback method on a non transacted JMS Session
Action: Remove invocation of the rollback method on the current JMS Session
JMS-00229: {0} must be specified
Cause: The specified parameter was null
Action: Specify a non-null value for the parameter
JMS-00230: Illegal operation on durable subscription with active TopicSubscriber
Cause: Try to unsubscribe, change or create durable subscription while it has an
active TopicSubscriber.
Action: Close the active TopicSubscriber and try again.
JMS-00231: Consumers on temporary destination must belong to the same
Action: Specify a non-null value for the parameter
JMS-00232: An invalid user/password was specified for the JMS connection
Cause: Invalid user/password specified for connection
Action: Specify valid user/password for connection
JMS-00233: The required subscriber information is not available
Cause: Try to retrieve subscriber information from a subscriber which was obtained
with getDurableSubscriber method and had no corresponding information in the inmemory map.
Action: Do not retrieve subscriber information from such a subscriber
JMS-00234: This operation is not allowed in the current messaging domain
Cause: Perform an operation that is not allowed in the current messaging domain
Action: Do not perform the operation in the current messaging domain
JMS-00235: Can not link the durable subscriber name with a topic in unsubscribe
method.
Cause: OJMS is unable to link the supplied durable subscriber name with a topic. This
causes unsubscribe method to fail.
Action: Use other unsubscribe methods which the user can provide topic name.
JMS-00236: OJMS encountered invalid OCI handles.
Cause: OJMS encountered invalid OCI handles when using JDBC OCI driver .
Action: Make sure the underlying JDBC connection is not closed while OJMS is still
operating.
JMS-00101 to JMS-00256 30-11
JMS-00237: Can not start thread for message listener.

Cause: OJMS is unable to start a new thread for message listener.
Action: Check the thread proxy code if the thread was started by a user provided
thread proxy.
JMS-00238: Illegal attempt to recover on a transacted JMS Session
Cause: Illegal attempt to invoke the recover method on a transacted JMS Session
Action: Use rollback method instead of recover method on transacted JMS session.
JMS-00239: Illegal attempt to call {0} method on a XASession.
Cause: Illegal attempt to invoke the commit or rollback method on a XASession
Action: Use JTA to commit or rollback a distributed transaction
JMS-00240: Illegal attempt to call setClientID after other actions.
Cause: Illegal attempt to call Connection.setClientID method after other actions has
been taken on this Connection
Action: set client ID before any other action on the Connection
JMS-00241: Illegal attempt to delete temporary destination when there are
consumers using it.
Cause: Illegal attempt to delete temporary destination while there are existing
consumers still using it.
Action: close the consumers before deleting the temporary destination
JMS-00242: Illegal attempt to enqueue message with both immediate visibility and
three phase enqueue process.
Cause: Illegal attempt to enqueue message with both immediate visibility and three
phase enqueue process.
Action: turn on the system property oracle.jms.useTemplobsForEnqueue
JMS-00243: Topic {0} not found
Cause: The specified topic was not found
Action: Specify a valid topic
JMS-00244: {0} is an invalid operation with the Sharded Queue.
Cause: The operation is not valid with the Sharded Queue
Action: Specify a valid operation for the Sharded Queue
JMS-00245: JMS Streaming support is available only for Sharded Queues.
Cause: JMS Streaming is supported with Sharded Queues only
Action: Use JMS Streaming APIs with Sharded Queue
JMS-00246: JMS Streaming support is not available for {0} driver.
Cause: JMS Streaming is supported with thin driver only
Action: Use JMS Streaming APIs with thin driver
JMS-00247: NON_PERSISTENT message delivery is not supported with JMS
Streaming.
Cause: The NON_PERSISTENT delivery mode is not supported with JMS Streaming
Action: Specify PERSISTENT message delivery mode
JMS-00248: Illegal attempt to use JMS Streaming API when streaming is disabled.
Cause: Illegal attempt to use JMS Streaming API when streaming is disabled
Action: Turn on the system property oracle.jms.useJmsStreaming
JMS-00249: InputStream representing the message data must be specified.
Cause: InputStream is null
Action: Specify a valid InputStream representing the message data
JMS-00250: OutputStream must be specified to write the message data.
Cause: OutputStream is null
Action: Specify a valid OutputStream to write the data from the received message
JMS-00251: Illegal attempt to set message data using both write method(s) and
Streaming API.
Cause: Illegal attempt to set message data using both write methods and Streaming
API
Action: Specify either an InputStream or write method to set the message data
JMS-00252: Illegal attempt to read the data using {0} when the streaming is used
with dequeue.
Cause: Illegal attempt to read the message data using read methods when the
dequeue used streaming
Action: Call receiveData() to read the message data
JMS-00253: Operation {0} not allowed on a Message with null JMSMessageID.
Cause: The operation is not allowed on a Message with null JMSMessageID
Action: Use this operation on a Message with valid JMSMessageID
JMS-00254: Streaming is not used with dequeue, please use standard JMS API to
read the message data.
Cause: Streaming is not used with dequeue operation
Action: Use standard JMS API to read the message data
JMS-00255: JMS Streaming support is available in a Session with acknowledge
mode +
Cause: Invalid acknowledgement mode used with JMS Streaming
Action: Valid acknowledgement modes are Session.CLIENT_ACKNOWLEDGE and
Session.SESSION_TRANSACTED
JMS-00256: stop() of javax.jms.Connection timed out.
Cause: stop() of javax.jms.Connection timed out
Action: A default timeout of 10 minutes is set to disable the registrations, and allow
the onMessage() to process the message. Set a higher value in milli seconds for this
timeout using the system property oracle.jms.notificationTimeOut
JMS-00101 to JMS-00256 30-13
31
JMS-00400 to JMS-00448
JMS-00400: Destination name must be specified
Cause: A null Destination name was specified
Action: Specify a non-null destination name
JMS-00402: Class not found: {0}
Cause: The specified class was not found
Action: Make sure your CLASSPATH contains the class
JMS-00403: IO Exception {0}
Cause: IO exception
Action: See message is AQxmlException for details
JMS-00404: XML Parse Exception
Cause: An error occured in the XML Parser layer
JMS-00405: XML SAX Exception
Cause: An error occured in the XML SAX layer
JMS-00406: JMS Exception {0}
Cause: An error occured in the JMS layer
Action: See the message inside the linked JMSException for more information
JMS-00407: Operation not allowed on {0}
Cause: The specified operation is not allowed on this object
Action: n/a
JMS-00408: Conversion failed - invalid property type
Cause: An error occured while converting the property to the requested type
Action: Use the method corresponding to the property data type to retrieve it
JMS-00409: No such element
Cause: Element with specified name was not found in the map message
Action: n/a
JMS-00410: XML SQL Exception
Cause: An error occured in the JDBC SQL layer
Action: See the message inside the linked SQLException for more information
JMS-00400 to JMS-00448 31-1
JMS-00411: Payload body cannot be null

Cause: An invalid body string or document was specified
Action: Specify a non-null body string or document
JMS-00412: Byte conversion failed
Cause: An invalid username/password was specified
Action: Specify a non-null username and password
JMS-00413: Autocommit not allowed for operation
Cause: The autocommit flag cannot be set for this operation
Action: Do not set the autocommit flag
JMS-00414: Destination owner must be specified
Cause: A null Destination owner was specified
Action: Specify a non-null destination name
JMS-00415: Invalid Visibility value
Cause: Visibility value specified is invalid
Action: Valid values are AQxmlConstants.VISIBILITY_ONCOMMIT,
AQxmlConstants.VISIBILITY_IMMEDIATE
JMS-00416: Invalid Dequeue mode
Cause: Invalid dequeue mode was specified
Action: Valid Dequeue modes are AQxmlConstants.DEQUEUE_BROWSE,
AQxmlConstants.DEQUEUE_REMOVE, AQxmlConstants.DEQUEUE_LOCKED,
AQxmlConstants.DEQUEUE_REMOVE_NODATA
JMS-00417: Invalid Navigation mode
Cause: An invalid navigation mode was specified
Action: The valid navigation modes are
AQxmlConstants.NAVIGATION_FIRST_MESSAGE,
AQxmlConstants.NAVIGATION_NEXT_MESSAGE,
AQxmlConstants.NAVIGATION_NEXT_TRANSACTION
JMS-00418: Invalid value for wait_time
Cause: Invalid value for wait type
Action: Wait time can be AQDequeueOption.WAIT_FOREVER,
AQDequeueOption.WAIT_NONE or any value greater than 0
JMS-00419: invalid ConnectionPoolDataSource
Cause: A null or invalid ConnectionPoolDataSource was specified
Action: Specify a valid OracleConnectionPoolDataSource object with the correct url
and user/password
JMS-00420: Invalid value for cache_size
Cause: An invalid cache_size was specified
Action: Cache size must be greater than 0
JMS-00421: Invalid value for cache_scheme
Cause: An invalid cache scheme was specified
31-2 Error Messages
Action: The valid cache schemes are

OracleConnectionCacheImpl.DYNAMIC_SCHEME
OracleConnectionCacheImpl.FIXED_WAIT_SCHEME
JMS-00422: Invalid tag - {0}
Cause: An invalid tag was encountered in the XML document
Action: Verify that the XML document conforms to the AQ schema
JMS-00423: Invalid value
Cause: An invalid value was specified
Action: Verify that the value specified in the XML document conforms to those
specifid in the AQ schema
JMS-00424: Invalid message header
Cause: The message header specified is null or invalid
Action: Specify a valid message header
JMS-00425: Property name must be specified
Cause: Property name was null
Action: Specify a non-null property name
JMS-00426: Property does not exist
Cause: Invalid property name specified. The property does not exist
Action: The property does not exist
JMS-00427: Subscriber name must be specified
Cause: Subscriber name was null
Action: Specify a non-null subscription name
JMS-00428: Valid message must be specified
Cause: message was null
Action: Specify a non-null message
JMS-00429: Register Option must be specified
Cause: Register option is null
Action: Specify a non-null Register Option
JMS-00430: Database Link must be specified
Cause: DB Link is null
JMS-00431: Sequence Number must be specified
Cause: Register option is null
JMS-00432: Status must be specified
Cause: status option is null
JMS-00433: User not authenticated
Cause: User is not authenticated
JMS-00400 to JMS-00448 31-3
Action: Specify an authenticated user

JMS-00434: Invalid data source
Cause: Data source is null or invalid
Action: Specify a valid data source
JMS-00435: Invalid schema location
Cause: Schema location is null or invalid
Action: Specify a valid URL for the schema
JMS-00436: AQ Exception
Cause: An error occured in the AQ java layer
Action: See the message inside the AQxmlException and the linked exception for
more information
JMS-00437: Invalid Destination
Cause: An invalid destination object was specified
Action: Specify a valid destination (Queue/Topic) object
JMS-00438: AQ agent {0} not mapped to a valid database user
Cause: The AQ agent specified does not map to a database user which has privileges
to perform the requested operation
Action: Use dbms_aqadm.enable_db_access to map the agent to a database user with
the required queue privileges
JMS-00439: Invalid schema document
Cause: The schema document specified is not valid
Action: Specify a valid URL for the schema document
JMS-00440: Invalid operations - agent {0} maps to more than one database user
Cause: The aq agent mapped to more than one database user in the the same session
Action: Map the aq agent to only one database user Check the aq$internet_users view
for database users that map to this agent
JMS-00441: {0} cannot be null
Action: Specify a non-null value
JMS-00442: Name and Address for Agent cannot be null
Cause: Both the name and address parameters were specified as null
Action: Specify a non-null value for the name or address
JMS-00443: IMMEDIATE visibility mode not supported for this queue/topic
Cause: IMMEDIATE visibility mode not supported for JMS type queue/topic
Action: Use ON_COMMIT or the default visibility mode for JMS type queue/topic
JMS-00444: This feature is not supported yet
Cause: The requested feature is not yet supported
Action: wait for future releases that support the feature.
31-4 Error Messages
JMS-00445: Destination alias must be specified

Cause: A null Destination alias was specified
Action: Specify a non-null destination alias
JMS-00446: Agent alias must be specified
Cause: A null Agent alias was specified
Action: Specify a non-null agent alias
JMS-00447: error in accessing LDAP server
Cause: error in accessing the LDAP server
Action: check the LDAP server is up and the environment parameters provided to the
servlet are correct
JMS-00448: Invalid Content-Type
Cause: Invalid Content-Type
Action: Content-Type must be "text/xml" or "application/x-www-form-urlencoded"
with parameter name "aqxmldoc"
JMS-00400 to JMS-00448 31-5
31-6 Error Messages
32
KFED-00400 to KFED-00403
KFED-00400: Operating system dependent operation: string failed with status:
string
KFED-00401: Operating system failure message: string
KFED-00402: failure occurred at: string
KFED-00403: additional information: string
KFED-00400 to KFED-00403 32-1
32-2 Error Messages
33
KFNDG-00200 to KFNDG-00701
KFNDG-00200: invalid syntax
Cause: Invalid syntax for renamedg was specified.
Action: Try renamedg -help for more information.
KFNDG-00201: invalid arguments
Cause: Invalid key or value was specified for renamedg.
Action: Try renamedg -help for more information.
KFNDG-00202: invalid value (string) for parameter phase
Cause: Incorrect value for parameter PHASE was specified.
Action: Valid values for parameter PHASE are ONE, TWO, BOTH. Retry with correct
values.
KFNDG-00203: disk group name (string) exceeds maximum allowed length number
Cause: Invalid disk group name was specified.
Action: Disk group name can be a maximum of 32 characters.
KFNDG-00204: disk group name string has invalid characters
Cause: Invalid disk group name was specified.
Action: Disk group name can only contain alphabetic, numeric and the underscore (_)
characters.
KFNDG-00205: failed to interpret configuration file name
Cause: Invalid configuration file name was specified.
Action: Verify configuration file name and folder permissions and retry renamedg.
KFNDG-00301: new disk group (string) already exists, ignorning renamedg
Cause: disk group specified in NEWDGNAME already exists.
Action: None
KFNDG-00302: disk (string:string) does not contain a valid header
Cause: Device header could not be located or corrupt.
Action: Verify if the device mentioned is an ASM disk device.
KFNDG-00303: failed to update disk group name for string
Cause: Insufficient privileges or write error in disk.
Action: Verify disk permissions and retry renamedg. Also, see log for additional
information.
KFNDG-00200 to KFNDG-00701 33-1
KFNDG-00304: unable to access heartbeat block of the device string:string

Cause: Heartbeat block of the disk was corrupt.
Action: Verify disk header with ASM utilities, retry renamedg.
KFNDG-00305: failed to create configuration file
Cause: Insufficient privileges or invalid path.
Action: Verify folder permissions and retry the command.
KFNDG-00306: unable to write to configuration file
Cause: Insufficient privileges.
Action: Check file permissions and retry renamedg.
KFNDG-00307: unable to read configuration file
Cause: Insufficient privileges or disk read error.
Action: Check file permissions and retry renamedg.
KFNDG-00308: failed to process configuration file entry: string
Cause: Configuration file was corrupt.
Action: Check file information and retry renamedg.
KFNDG-00401: allocation unit size conflict (number, number)
Cause: Allocation unit size of disk group and the disk did not match.
Action: Verify that the device is not corrupt and retry renamedg.
KFNDG-00402: ASM metadata block size conflict (number, number)
Cause: Metadata block size of the disk group and disk did not match.
Action: Verify if the device is not corrupt and retry renamedg.
KFNDG-00403: not all disks of disk group string were discovered
Cause: Offine disks were present in the specified disk group.
Action: Refer to Oracle Database Storage Administator's Guide for more details.
KFNDG-00404: disk group string contains offline disks, ignoring renamedg
Cause: Disk group with offline disks could not be renamed.
Action: Refer to Oracle Database Storage Administator's Guide for more details.
KFNDG-00405: specified disk group string appears to be mounted
Cause: Disk group was mounted.
Action: Unmount the disk group and retry renamedg.
KFNDG-00406: disk group (string) is in use by CSS
Cause: Cluster Synchronization Service(CSS) was using the disk group to be renamed.
Action: Refer to crsctl command to relocate voting disks from disk group.
KFNDG-00407: Could not find disks for disk group string
Cause: No disks were discovered for disk group.
Action: Try renamedg with a different discovery string.
KFNDG-00408: disk (string:string) could not be discovered
Cause: Disk was either deleted or moved.
33-2 Error Messages
Action: None
KFNDG-00409: disk (string) doesn't belong to disk group (string)
Cause: Disk is not part of the specified disk group.
Action: None
KFNDG-00410: failed to discover devices in folder string
Cause: Insufficient privileges or invalid discovery string.
Action: See log for additional details.
KFNDG-00600: internal error string
Cause: An internal error occured while executing renamedg.
KFNDG-00601: fatal error string
Cause: A fatal error occurred while executing renamedg.
KFNDG-00603: failed to initialize device discovery
Cause: Error occurred while communicating with generic services layer.
KFNDG-00700: system dependent error (number, string, string, string) occurred
Cause: Internal system error occurred.
KFNDG-00701: Error number while performing I/O
Cause: I/O failure.
KFNDG-00200 to KFNDG-00701 33-3
33-4 Error Messages
34
KFOD-00316 to KFOD-00403
KFOD-00316: Error acquiring ASM discovery string: string
Cause: Call to the Grid Plug and Play service to request disk discovery string failed.
Action: Ensure that the Grid Plug and Play component of Cluster Ready Services is
available. If Grid Plug and Play is operational and command still fails, contact Oracle
Support Services.
KFOD-00317: error returned from Patch Query API: string
Cause: A call to the Patch Query API returned unsuccessfully.
Action: See the returned error message for details.
KFOD-00318: unable to retrieve error message from Patch Query API: string
Cause: A call to the Patch Query API returned unsuccessfully.
Action: See the returned error message for details.
KFOD-00320: Invalid operation or option for this cluster type
Cause: This operation is invalid for this cluster type
Action: Retry the operation with cluster=true
KFOD-00321: failed to read the credential file string
Cause: The credential file was not valid.
Action: Verify that the credential file is valid and accessible. Ensure that the user has
read access permission on the credential file. Rerun the command.
KFOD-00322: credential file not specified
Cause: The previous 'kfod' command was rejected because it did not include a valid
credential file name.
Action: Reexecute the 'kfod' command providing a valid credential file name. Refer to
the command line help for information.
KFOD-00323: Client Cluster version 'string' in the credential file does not match
software version 'string'
Cause: There was a version mismatch between the Client Cluster version in the
credential file and the software version.
Action: Install a version of the Client Cluster that matches the version in the
credential file.
KFOD-00324: The Client Cluster version 'string' is incompatible with the Storage
Server version 'string'.
Cause: The Client Cluster installation or upgrade was not supported by the Storage
Server configured at the version listed in the message.
KFOD-00316 to KFOD-00403 34-1
Action: Install or upgrade the Client Cluster to a version that is compatible with the
Storage Server. Refer to the product documentation for information.
KFOD-00325: failed to verify Client Cluster 'string'\nstring
Cause: The Client Cluster installation verification failed. The possible causes are: - A
Client Cluster with the same name was already configured. - A Client Cluster with
the same name was deinstalled, but the Client Cluster's configuration was not
removed at the Storage Server.
Action: Verify if there is already a Client Cluster with the name listed in the message
by executing the 'asmcmd lscc' command on the Storage Server. If the Client Cluster is
configured and in use, execute the 'asmcmd mkcc' command on the Storage Server,
and provide an unused Client Cluster name to generate a new credential file. Retry
the Grid Infrastructure installation using the new credential file. If the Client Cluster
is configured and not in use, deinstall the existing Client Cluster. Execute the
'asmcmd rmcc' command on the Storage Server to delete the Client Cluster
configuration. Retry the Grid Infrastructure installation. If the Client Cluster is not
configured or if the error persists, contact Oracle Support Services.
KFOD-00326: Client Cluster(s) 'string' will be incompatible if the Storage Server is
upgraded to version 'string'.
Cause: Storage Server upgrade to the listed version failed because the listed Client
Cluster will become incompatible.
Action: Upgrade the Storage Server to a version that is compatible with all of the
configured Client Clusters. If the Storage Server could not be upgraded to a
compatible version, forcibly upgrade the Storage Server using the procedure
documented in the product documentation.
KFOD-00327: failed to delete Client Cluster 'string'\nstring
Cause: There was a failure in deleting the Client Cluster configuration. The
accompanying error message provides the details.
Action: Examine the accompanying error message, address the reported issue and
KFOD-00328: Client Cluster installation or upgrade failed because the Storage
Server is in the 'In Rolling Upgrade' or the 'In Rolling Patch' state.
Cause: The Client Cluster installation or upgrade was rejected because the Storage
Server was in the 'In Rolling Upgrade' or the 'In Rolling Patch' state.
Action: Retry the installation or upgrade procedure after the Storage Server upgrade
or patching has completed.
KFOD-00329: no cluster name specified
Cause: The previous 'kfod' command was rejected because it did not include a cluster
name.
Action: Reexecute the 'kfod' command providing a valid cluster name. Refer to the
command line help for information.
KFOD-00330: invalid cluster name 'string' specified
Cause: An invalid cluster name was supplied to the 'kfod' utility.
34-2 Error Messages
KFOD-00331: forcibly deleted Client Cluster 'string'

Cause: The configuration for the Client Cluster listed in the message was was forcibly
deleted.
Action: The Client Cluster listed in the message will no longer be able to access the
Storage Server. Follow the steps to enable access from the Client Cluster. - Delete all
the Oracle Clusterware files in the '+<diskgroup_name>/<client_cluster_name>/'
directory in all disk groups. - Deinstall the Client Cluster. - Install the Client Cluster.
KFOD-00334: failed to list the configured Client Clusters\nstring
Cause: A failure occurred while attempting to display the Client Cluster
configuration. The accompanying error message provides the details.
Action: Examine the accompanying error message, address the reported issue and
KFOD-00400: OS system dependent operation: string failed with status: string
Cause: OS system call error
Action: contact Oracle Support
KFOD-00401: OS failure message: string
KFOD-00402: failure occurred at: string
KFOD-00403: additional information: string
KFOD-00316 to KFOD-00403 34-3
34-4 Error Messages
35
KUP-00552 to KUP-11602
KUP-00552: internal XAD package failed to load
Cause: An error was encountered while attempting to initialize the XAD package.
Action: This message should be accompanied by other error message(s) indicating the
cause of the error.
KUP-00554: error encountered while parsing access parameters
Cause: The parser detected a syntax error.
cause of the error.
KUP-00561: invalid length for binary integer field string\n
Cause: An integer field was specified with an invalid length. The only supported
lengths for binary integer fields are 1, 2, 4, and 8.
Action: n/a
KUP-00562: unknown escape sequence\n
Cause: An unknown escape sequence was specified to the parser. An escape sequence
is a backslash followed by a character.
Action: Consult documentation for list of allowable control characters.
KUP-00600: internal error, arguments [string] [string] [string] [string] [string]
Cause: An internal XAD error occurred.
KUP-00601: fatal XAD error
Cause: A fatal error has occurred.
cause of the error.
KUP-01006: error signalled during parse of access parameters
Cause: An error was signalled during parsing of the access parameters.
cause of the error.
KUP-01007: at line number column number
Cause: This is an informational message indicating the line and column where a
syntax error was detected.
Action: n/a
KUP-00552 to KUP-11602 35-1
KUP-01008: the bad identifier was: string

Cause: This is an informational message indicating the identifier token that caused a
syntax error.
Action: n/a
KUP-02000: wrong message file version (msg number not found)
Cause: The kupxx.msb file is not the correct version.
Action: Check that the installation was done correctly.
KUP-02001: unrecognized punctuation symbol "string"
Cause: An illegal punctuation character was encountered.
Action: Remove the illegal character.
KUP-02002: unexpected end of input file reached
Cause: This is probably caused by failure to supply the closing quote for a quoted
string.
Action: Correct the input.
KUP-02003: unrecognized character: string
Cause: An input character that is neither an alpha, digit, or punctuation was
encountered.
Action: Remove the character.
KUP-02004: quoted string too big
Cause: A quoted string longer than 2000 bytes was encountered.
Action: This may be caused by a missing close quote. If so, add the missing quote,
otherwise shorten the string.
KUP-02005: token too big
Cause: A token longer than 1000 bytes was encountered
Action: Tokens must be separated by whitespace or punctuation. Either add the
missing whitespace or punctuation, or shorten the token.
KUP-02006: script line too long
Cause: a line longer than 500 bytes was encountered
Action: break the line up into shorter lines
KUP-03001: fatal error during library cache pre-loading
Cause: This message should be accompanied by other error message(s) indicating the
cause of the error.
Action: Check the accompanying errors.
KUP-03002: end position (number) <= start position (number) for field: string
Cause: Error in specifying position for the specified field in the access parameters."
Action: Check that the specified end position is greater than the specified start
position.
35-2 Error Messages
KUP-03003: absolute end(number) - start(number) != fieldlength (number) for field

string
Cause: The number of bytes occupied by the field as specified by the starting offset
and ending offset of the field is not the same as the number of bytes specified for the
datatype of the field.
Action: Verify the absolute begin/end position(s) specified match the length of the
field.
KUP-03004: absolute end (number) specified with relative start (number) for field
string
Cause: The position of field was specified with a relative start and an absolute end.
Action: Use relative end with relative start
KUP-03005: relative end (number) specified does not match fieldlen(number) for
field string
Cause: The number of bytes specified by the relative end position for the field does
not match the number of bytes in the datatype.
Action: Correct either the datatype length or the relative end position.
KUP-03006: error initializing handle for character set string
Cause: Error attempting to retrieve information for the character set.
Action: Verify that the character set name is valid.
KUP-03007: end position (number) is less than start position (number) for range
Cause: A byte range specified a start position that comes after the end position.
Action: Verify the start and end positions are correctly specified.
KUP-03008: OCI error getting column parameters.
Cause: An error occurred while trying to obtain column parameters.
KUP-03009: OCI error getting column name.
Cause: An error occurred while trying to obtain column name.
KUP-03010: OCI error getting database column type.
Cause: An error occurred while trying to obtain database column type.
KUP-03011: OCI error getting database column size.
Cause: An error occurred while trying to obtain database column size.
KUP-03012: OCI error getting database column precision.
Cause: An error occurred while trying to obtain database column precision.
KUP-03013: OCI error getting database column scale.
Cause: An error occurred while trying to obtain database column scale.
KUP-00552 to KUP-11602 35-3
KUP-03014: OCI error getting datetime fsprecision.

Cause: An error occurred while trying to obtain a datetime column precision value."
KUP-03015: OCI error getting datetime lfprecision.
Cause: An error occurred while trying to obtain database column precision.
KUP-03016: length specified for FIXED records must be greater than 0\n
Cause: A record format of FIXED was specified with a length of 0.
Action: n/a
KUP-03017: length specified for VARIABLE records must be greater than 0\n
Cause: A record format of VARIABLE was specified with a length of 0.
Action: n/a
KUP-03018: invalid date mask "string" specified for column string\n
Cause: The date mask for the specified column is invalid.
Action: n/a
KUP-03019: directory object not specified in LOBFILE clause for field string\n
Cause: A LOBFILE clause was specified for the field, but no directory object was
specified. When no directory object is specified, then the default directory specified
for the external table is used, but no default directory was specified.
Action: Specify a directory object in the LOBFILE clause or specify a default directory
for the external table.
KUP-03020: empty delimiter specified for record\n
Cause: An empty delimiter string was specified for a record delimiter.
Action: Specify the string used to delimiter records.
KUP-03021: clause references unknown field string\n
Cause: A WHEN, NULLIF or DEFAULTIF clause referenced a field that doesn't exist
in the data file.
Action: n/a
KUP-03022: lob data could not be found for field string\n
Cause: The field specified in the data source that contains the name of the lob file for
the record could not be identified.
Action: n/a
KUP-03023: string for TERMINATED BY or ENCLOSED BY clause for record is
longer than maximum number\n
Cause: The string value for a TERMINATED BY or ENCLOSED BY clause is longer
than the maximum number of bytes allowed. If the character set of the data file is
different than the character set of the database, the string will be converted to the
character set of the data file. If the length of the converted string is too large, then this
error will also be returned.
Action: Use shorter delimiters in the data file and the access parameters.
35-4 Error Messages
KUP-03024: string for TERMINATED BY or ENCLOSED BY clause for column

string is longer than maximum number\n
Cause: The string value for a TERMINATED BY or ENCLOSED BY clause for the
columns is longer than the maximum number of bytes allowed. If the character set of
the data file is different than the character set of the database, the string will be
converted to the character set of the data file. If the length of the converted string is
too large, then this error will also be returned.
Action: Use shorter delimiters in the data file and the access parameters.
KUP-03025: For CSV format files, field string is not delimited.\n
Cause: The comma-delimited value (CSV) format files did not have all delimited
fields. CSV format files must have all delimited fields so that the access driver can
process the fields.
Action: Make all of the fields delimited or remove the CSV specification and retry.
KUP-03026: For FIELD NAMES, field string is not delimited.\n
Cause: The data files with a FIELD NAMES record did not have all delimited fields.
Data files with a FIELD NAMES record must have all delimited fields so that the
access driver can process the field names.
Action: Make all of the fields delimited and retry.
KUP-03027: NULLIF at field level not allowed with NO NULLIF for field string.\n
Cause: The field had both NULLIF and NO NULLIF specified. You must specify one
or the other.
Action: Remove one of the specifications and retry.
KUP-03028: Field name string in field list does not match the name of any table
column.\n
Cause: The ALL FIELDS OVERRIDE THESE clause was specified and there was a
field name in the field list in the access parameters that did not match the name of a
column in the table definition. Only names that match the name of columns in the
table may be specified in the field list.
Action: Verify that the correct names are used for the columns in the table and for the
fields in the field list.
KUP-03029: Invalid value specified for parameter string.
Cause: The access parameter contained an invalid value for the parameter specified in
the error message.
Action: Update the access parameters to have a valid value.
KUP-03995: LOCAL TIME ZONE not allowed with DATE_FORMAT TIME\n
Cause: LOCAL can only be specified with TIMESTAMP, not with TIME.
Action: Remove LOCAL or change TIME to TIMESTAMP and try the operation again.
KUP-03996: multiple DATE_FORMAT string masks specified at table level for
table string\n
Cause: Multiple date format masks were specified for the listed datetime or interval
data type at the table level for the listed table.
Action: Remove one of the datetime mask specifications and try the operation again.
KUP-00552 to KUP-11602 35-5
KUP-03997: invalid DATE_FORMAT string mask ("string") specified for table

string\n
Cause: The date format mask for listed datetime type for the specified table was
invalid.
Action: Fix the mask and try the operation again.
KUP-03998: error number formatting KUP message number\n
Cause: error occured while attempting to format a KUP message.
Action: contact Oracle support.
KUP-03999: error occurred while processing a date format: ORA-number: string
Cause: Error converting a date format string into an internal representation.
Action: Verify that the date format strings specified in the access parameters are valid.
KUP-04000: error initializing I/O state for file string\n
Cause: An unexpected error occurred while preparing the file.
KUP-04001: error opening file string\n
Cause: An error occurred while attempting to open the specified file. This message
should be followed by another message with more information about the error.
Action: See the error that follows to determine the action to be taken.
KUP-04002: error getting file size for file string\n
Cause: An error occurred while retrieving the number of bytes in the specified file.
KUP-04003: error while closing file string\n
Cause: An error occurred while closing the specified file.
KUP-04004: error while reading file string\n
Cause: An error occurred while reading the specified file.
KUP-04017: OS message: string\n
Cause: An error occurred. This message contains the message associated with this
error that was returned by the operating system. The message displayed before this
one should indicate the operation that failed.
Action: n/a
KUP-04018: partial record at end of file string\n
Cause: An incomplete record was found at the end of the file.
Action: Verify the file is not corrupt or missing data.
KUP-04019: illegal length found for VAR record in file string\n
Cause: A record in a VAR file has an length field with either no numeric characters in
it or with non numeric characters in it.
Action: Verify the records in the file have the correct length specified for them.
35-6 Error Messages
KUP-04020: found record longer than buffer size supported, number, in string
(offset=number)\n
Cause: a record in the data source was longer than the maximum data size supported.
The number reported is the maximum supported size of a record.
Action: n/a
KUP-04021: field formatting error for field string\n
Cause: There was an error trying to find the contents of the specified field in a record.
Action: This message should be followed by another message containing more
specific information about the cause of the error.
KUP-04022: field start is before start of record\n
Cause: The position of the start of a field is before the start of a record. This can occur
if a negative number is used to indicate the relative start of a field.
Action: Verify that the definition of the layout of fields in the data file is correct.
KUP-04023: field start is after end of record\n
Cause: This can happen when specifying either absolute or relative positioning for a
field.
Action: Verify that the definition of the layout of fields in the data file is correct. If it is
valid for fields at the end of the record to be missing, use the MISSING FIELD
VALUES ARE NULL clause in the access parameters.
KUP-04024: field end is before field start\n
Cause: The end of the field comes after the start of the field. This can happen if the
field is defined with a relative start position and an absolute end position.
KUP-04025: field extends beyond end of record\n
Cause: This can happen when specifying either absolute or relative positioning for a
field.
KUP-04026: field too long for datatype\n
Cause: The character field in the record is larger than the maximum length specified.
Action: Make sure the definition of the layout of the fields in the data file is correct.
Also make sure the correct maximum size was specified for a character datatype.
KUP-04027: file name check failed: string\n
Cause: The check of the filename failed. These checks are platform specific, but they
can include verifying that there are no hard links in the file path, the file is not a soft
link, the file specification includes a parent reference ("../" on Unix), or the file was
modified between the time the check was made and the file was opened.
Action: Use a file location that does not violate any of the checks.
KUP-04028: conversion of character length to a number failed\n
Cause: The character length portion of the field could not be converted to a number.
This message is followed by another message with information on why the
conversion failed.
Action: Make sure the data is correct. Also verify the datatypes specified for the fields
are correct.
KUP-00552 to KUP-11602 35-7
KUP-04029: numeric field overflowed\n

Cause: An attempt to convert a character string to number failed because the value of
the number in the string was too large.
Action: n/a
KUP-04030: invalid numeric data\n
Cause: An attempt to convert a character string to a number failed because nonnumeric characters were found.
Action: n/a
KUP-04031: empty filename specified for LOB file in column string\n
Cause: The field in the data file that was supposed to contain the name of a LOB file
was empty.
Action: Correct the data so that it contains a valid file name.
KUP-04032: internal error string while parsing field string:\n
Cause: An internal error occurred while parsing a field.
KUP-04035: beginning enclosing delimiter not found\n
Cause: The beginning enclosure was not found for a field that is enclosed by
delimiters.
Action: Verify that the data is correct. Also verify that the correct enclosing delimiters
were specified and whether the enclosing delimiter should be optional.
KUP-04037: terminator not found\n
Cause: The terminator for the field is missing.
Action: Verify that the records are formatted correctly.
KUP-04038: internal error: string\n
Cause: an unexpected error condition was detected.
Action: contact Oracle customer support
KUP-04039: unexpected error while trying to find file string in string\n
Cause: An error occurred while trying to find path containing the file.
Action: This message should be followed by another message with more information
about the error.
KUP-04040: file string in string not found\n
Cause: The file was not found in the directory specified
Action: Verify the correct file and directory names were specified.
KUP-04041: error generating full file name for string in string\n
Cause: Unexpected error occurred while trying to form a file name.
Action: n/a
KUP-04043: table column not found in external source: string\n
Cause: A column in the external table was not found in the access parameters that
define the contents of the data source.
Action: Verify that the external table is defined correctly and that the access
parameters are also correct.
35-8 Error Messages
KUP-04044: error positioning file string\n

Cause: An attempt to position a file to an absolute file offset failed.
Action: See messages that follow for more information.
KUP-04045: unexpected OCI status string
Cause: An OCI call returned a status that cannot be handled.
KUP-04047: error parsing record from external data source\n
Cause: An error occurred while trying to extract a record from the data source.
Action: Look in the log file for more messages about the error.
KUP-04048: internal error parsing record from external data source\n
Cause: An unexpected or unhandled error occurred while getting a record from the
data source
KUP-04049: record number discarded from file string\n
Cause: Informational message displayed whenever the WHEN clause has been
satisfied. If a DISCARD file has been specified for the operation, the record will be
written to that file.
Action: None
KUP-04050: error while attempting to allocate number bytes of memory\n
Cause: An error occurred while trying to allocate memory. This is likely caused by
Action: Reconnect to the instance and retry the operation.
KUP-04051: error processing column string in row number for datafile string\n
Cause: an error occurred while trying to convert the data from the data file into the
type of a column in the external table.
Action: See messages that follow for more details.
KUP-04052: \nerror processing column string in a row for datafile string\n
Cause: an error occurred while trying to convert the data from the data file into the
type of a column in the external table.
KUP-04053: record number number\n
Cause: This message identifies a record number in a file for a record that had an error.
The message preceding this one contains information about the error and the name of
the file.
Action: n/a
KUP-04054: internal error: invalid bad row number identified for bad column
number\n
KUP-00552 to KUP-11602 35-9
KUP-04055: column string is both a field in the data file and a column transform\n
Cause: The specified column was in the list of fields in the data file and in the list of
column transforms. The column should be in one list or the other, but not both.
Action: Determine whether the value for the field in the data file or the value for the
field in the column transform should be loaded in to the table. If the value for the data
file is to be loaded, then remove the column transform. If the value for the column
transform is to be loaded, then rename the field in the data file so that it does not
match the name of a field in the table.
KUP-04056: internal error: OCI error while fetching record: number\n
Cause: An OCI error occurred while processing the granule.
KUP-04057: internal error: OCI error while fetching record.\n
Cause: An OCI error occurred while processing the granule.
KUP-04058: unrecoverable error occurred, operation aborted.\n
Cause: An unrecoverable error occurred during processing.
Action: See preceding error messages for more information.
KUP-04059: found EOF in length portion of VARIABLE record in file string\n
Cause: The record parser was looking for the size portion of a file a record format of
VARIABLE. It found EOF before finding all the bytes for the length.
Action: Correct the corruption in the file.
KUP-04060: field string referenced by lobfile column string not found\n
Cause: The LOBFILE transform for the named column referenced a field for either the
directory object portion or the name portion of the LOBFILE. However, that field did
not exist anywhere in the definition of the data file.
Action: Verify that the LOBFILE clause is specified correctly. Also verify that the field
definitions for the data file are correct.
KUP-04061: directory object string specified for LOBFILE column string is not valid
\n
Cause: The column being loaded from a LOBFILE specified the directory object
containing the LOBFILE through another field in the data file. In this case, the
LOBFILE clause in the access parameters must specify a list of all directory objects
that will be used for this field. This error occurs because a field contains the name of a
directory object that is not in this list.
Action: Verify that the data file contains the correct directory object and verify that
the list of valid directory objects in the LOBFILE clause for this column is complete.
KUP-04062: no data source specified\n
Cause: No location for the data source of the external table was specified when the
external table was created. An empty string is not valid.
Action: Specify the name of the data source in the LOCATION clause when creating
an external table.
KUP-04063: unable to open log file string\n OS error string\n
Cause: An attempt to open the log file failed.
Action: Specify a different log file or use NO LOGFILE to disable logging.

KUP-04064: fatal error during initialization\n
Cause: An unexpected error occurred while initializing access to an external table.
KUP-04065: error processing LOBFILE for field string\n
Cause: An error occured while opening or reading a LOBFILE for a column in a row.
Action: See message in log file for more information about the error.
KUP-04066: error initializing access to external table source\n
Cause: An error occurred while attempting to retrieve information about a data
source.
Action: See messages preceding this one for more information about the error.
KUP-04067: internal error allocating handle type string\n
Cause: An attempt to create an internal object failed.
KUP-04068: internal error fetching attribute string\n
Cause: An attempt to fetch information about an internal object failed.
KUP-04069: error fetching data for external table\n
Cause: An error occurred while atempting to fetch data from an external table.
Action: See messages the precede this one for more information.
KUP-04070: field string referenced by column transform string not found\n
Cause: The column transform for the named column references a field that did not
exist anywhere in the definition of the data file.
Action: Verify that the column transform clause is specified correctly. Also verify that
the field definitions for the data file are correct.
KUP-04071: record discarded from file string\n
written to that file. The record number in the source data file is not known because
multiple servers are loading from the file.
Action: n/a
KUP-04072: error writing to file string\n
Cause: An error occurred while attempting to write to the named file.
Action: See messages that follow this message for more information about the error.
KUP-04073: record ignored because all referenced fields are null for a record\n
Cause: A record was rejected because all fields in the data file referenced by the query
were NULL.
Action: n/a
KUP-00552 to KUP-11602 35-11
KUP-04074: no write access to directory object string\n

Cause: The user does not have write access to the directory object used for a log, bad
or reject file.
Action: n/a
KUP-04075: no read access to directory object string\n
Cause: The user does not have read access to the directory object used for a data file.
Action: n/a
KUP-04076: file name cannot contain a path specification: string\n
Cause: The name of a data file, log file, bad file or reject file contains a path
specification.
Action: Use the name of a directory object to indicate where the file should be stored.
KUP-04077: unknown format specifier in file name string\n
Cause: A format specifier is a percent sign followed by a character. The percent sign
and character are replaced by a value depending on the character. This error occurs
when the character following the percent sign is not defined to have a value.
Action: See the documentation for information on valid format specifiers. If the file to
be opened needs to have a percent sign in its name then use two pecent signs. They
will get replaces by a single percent sign in the resulting file name.
KUP-04078: invalid file name specified: string
Cause: Attempt to parse the file name failed.
Action: Specify a valid file name.
KUP-04079: error fetching list of valid directories\n
Cause: An attempt to retrieve a list of valid directories that can be used by the user to
open files failed. See messages that follow for more information.
Action: Contact Oracle support. As a workaround try specifing no log file, no discard
files and no bad files.
KUP-04080: directory object string not found\n
Cause: The directory object specified for an input file or a log, bad or discard file does
not exist in the database or the user has no privileges to access this directory.
Action: n/a
KUP-04081: field string used in concatenation for column string is not a character
type\n
Cause: The specified field was part of a concatenation of strings used to create the
value for the names column. However, the field was not of a character datatype. Only
character fields may be used as part of concatenating fields.
Action: Verify the correct field was used in the CONCAT clause. Also verify that the
correct datatype is specified for the field in the field list.
KUP-04082: error converting field string for LOBFILE column string\n
Cause: The LOBFILE column had either its directory object name or filename
specified by a field in the data file and that field needed to be converted to the server's
character set before it could be used. This message indicates that an attempt to
convert the field failed.
Action: Verify that the data file has the correct value for the fields. Also verify that the
correct character set was specified for the data file.
KUP-04083: no directory object specified in LOBFILE clause for column string\n
Cause: There was no directory object specified for the LOB files used to populate the
named column and no default directory was specified for the external table.
Action: Either specify a directory name, or the name of a data field containing the
name of the directory object that contains the files.
KUP-04084: The ORACLE_DATAPUMP access driver does not support the ROWID
column.\n
Cause: A query of an external table of type ORACLE_DATAPUMP tried to reference
the ROWID column. The ORACLE_DATAPUMP access driver does not support
ROWIDs.
Action: Remove the ROWID from the query. If that is not possible, create a table in
the database with the same columns as the external table, copy the data from the
external table into the newly created table, and use that new table for the query.
KUP-04085: duplicate directory object string and file string specified for unload\n
Cause: A CREATE TABLE AS SELECT statement was executed for an external table
of type ORACLE_DATAPUMP and the same directory object and filename
combination was specified multiple times.
Action: Issue the CREATE TABLE AS SELECT command again but make sure the
combination of directory objects and filenames is unique.
KUP-04086: length of file name exceeds platform maximum of number\n
Cause: The length of a filename is longer than the maximum length supported by
Oracle on the server platform.
Action: Verify that the name is correct. If so, use a shorter file name.
KUP-04087: no execute access to directory object string\n
Cause: Execute access to the directory object used for a preprocessor file was not
granted.
Action: Grant execute privilege on the directory object or specify a different directory
which already has execute privilege enabled.
KUP-04088: data sampling is not supported by this access driver\n
Cause: A query of an external table requested a sample of the data returned. The
access driver for the external table does not support sampling.
Action: Do not try to use sampling for this external table.
KUP-04089: column transform string is not the name of a table column\n
Cause: The specified column was in the list of column transforms but a column by
that name does not exist in the table
Action: Verify that the correct name was specified in the column transform.
KUP-04090: big endian byte order mark found when little endian expected in string
\n
Cause: A big endian byte order mark was found at the beginning of the specified file
and either the access parameters specified the data was in little endian order or the
byte order mark for a previous file was little endian.
KUP-00552 to KUP-11602 35-13
Action: The file needs to be loaded separately. If a byte order was specified in the
access parameters, make sure it is changed to be big endian.
KUP-04091: little endian byte order mark found when big endian expected in string
\n
Cause: A little endian byte order mark was found at the beginning of the specified file
and either the access parameters specified the data was in big endian order or the byte
order mark for a previous file was big endian.
Action: The file needs to be loaded separately. If a byte order was specified in the
access parameters, make sure it is changed to be little endian.
KUP-04092: attempt to audit directory object string returned internal error number
\n
Cause: An error occurred while attempting to enable auditing for the specified
directory object.
KUP-04093: error processing the FIELD NAMES record in data file string\n
Cause: An error occurred while processing the FIELD NAMES record for the data file.
Action: See the messages that preceed this one for more details. Fix the error and retry
the operation.
KUP-04094: preprocessing cannot be performed if Database Vault is installed\n
Cause: The Database Vault option did not permit the execution a program from an
Oracle directory object.
Action: If preprocessing must be performed, then the Database Vault option must not
be installed.
KUP-04095: preprocessor command string encountered error "string"\n
Cause: The specified preprocessor command encountered an error during execution.
Action: Verify that the preprocessor command along with any arguments are correct.
KUP-04096: Warning: lobfile column transform ignored with PREPROCESSOR
option.\n
Cause: The specified column was in the list of lobfile column transforms but the
PREPROCESSOR option was also specfied. The PREPROCESSOR option does not
work in conjuction with lobfile column transforms.
Action: Do not use column transforms with the PREPROCESSOR option.
KUP-04097: RECORDS clause specified without a record format\n
Cause: The RECORDS clause was part of the external table access parameters but no
record format type was provided.
Action: If the RECORDS clause is used, then it must be followed by one of the
VARIABLE, FIXED, or DELIMITED BY clauses.
KUP-04098: empty field name for field number in the FIELD NAMES record in data
file\n
Cause: The field name for the listed field number in the FIELD NAMES record was
empty.
Action: Specify a valid field name in the data file and retry the operation.
KUP-04099: Missing one or more field names in the FIELD NAMES record in the
data file. Found number fields, there should be number fields.\n
Cause: One or more field names was not listed in the FIELD NAMES record.
However, it was listed in the access parameter list for the external table.
Action: Include all field names in the data file and retry the operation.
KUP-04100: record rejected in file string\n
Cause: A record in the data file was not loaded into the table because of an error
while finding fields in the record. See the previous error for more information. The
record will be written to the BAD file, if one is being used. The record number in the
source data file is not known because multiple servers are loading from the file.
Action: n/a
KUP-04101: record number rejected in file string\n
Cause: A record in the data file was not loaded into the table because of an error
while finding fields in the record. See the previous error for more information. The
record will be written to the BAD file, if one is being used.
Action: n/a
KUP-04102: record number discarded from file string\n
written to that file.
Action: n/a
KUP-04103: error converting zoned decimal field to number for string\n
Cause: An error occurred converting a zoned decimal number to an Oracle number.
Action: Verify that the zoned decimal number is formatted correctly.
KUP-04104: zoned decimal field has bad values for string\n
Cause: A zoned decimal number has an invalid format.
KUP-04105: zoned decimal to number conversion caused overflow for string\n
Cause: A zoned decimal number could not be converted to an Oracle number because
the number is too big for an oracle number.
KUP-04106: precision for zoned decimal number is too large for string\n
Cause: The precision of a zoned decimal number is larger than the precision that can
be stored in an Oracle number.
KUP-04107: substring of field string for column string is not a character type\n
Cause: A substring was specified for a field that which is not a character datatype.
Only character fields may be used when specifying the substring transform.
Action: Verify the correct field was used in the STARTOF clause. Also verify that the
correct datatype is specified for the field in the field list.
KUP-00552 to KUP-11602 35-15
KUP-04108: unable to reread file string\n

Cause: The query that is executing requires that a data source for an external table be
read multiple times. However, the data source is a sequential device that cannot be
reread. Examples of this type of data source is a tape or pipe.
Action: There are a few ways around this problem. One is to rewrite the query so that
the external table is referenced only once. Another option is to move the data source
to a rereadable device such as a disk file. A third option is to load the data for the
external table into a temporary table and change the query to reference the temporary
table.
KUP-04109: specified path for directory object "string" is invalid\n
Cause: The default directory or a directory object specified for an input data file or an
output dump, log, bad or discard file contains an invalid path name.
Action: Specify a valid path name for the directory object.
KUP-04116: Field name stringstringstring in the FIELD NAMES record in the data
file is too long.\n
Cause: The field name exceeded the maximum of 30 characters.
Action: Specify at most 30 characters.
KUP-04117: Field name stringstringstring was not found in the access parameter
field list or table.\n
Cause: The listed field name in the FIELD NAMES record of the data file was not
found in the access parameter field list or in the table columns. The next error
message, if any, lists the name of the data file where the error was found.
Action: Verify that the field name in the FIELD NAMES record is correct. If that is
correct, verify that the external table is defined correctly and that the access parameter
field list is also correct.
KUP-04118: operation "string", location "string"\n
Cause: This message provides information about the previous messages.
Action: Refer to the help for the previous message for more information.
KUP-04119: Error number opening directory for wild card search: string\n
Cause: An error occured while trying to open a directory to look for files that match a
wild card specification.
KUP-04120: Error number fetching count of files for wild card search in directory
string\n
Cause: An error occured while trying to retrieve the count of files matching a wild
card specification in the directory
KUP-04121: Error number fetching file names for wild card search in directory
string\n
Cause: An error occured while trying to retrieve the names of files matching a wild
card specification in the directory
KUP-04122: Error number finishing wild card search in directory string\n

Cause: An error occured while trying to finish a search for files that match a wild card
specification the directory. matching a wild card specification in the directory
KUP-05001: Shift based character sets not supported with CSV format files\n
Cause: CSV is being used with a shift based chararcter set.
Action: Either use a non-shift based cahracter set or do not use CSV format files.
KUP-05002: There are no matching files for any file specification in the
LOCATION clause.
Cause: One or more file specifications including wild cards were specified in the
LOCATION clause, but none of the files matched any of the specifications.
Action: Check to make sure that the file specifications are correct and that one or more
files match the file specifications and then try the operation again.
KUP-05003: Warning: There are no matching files for this specification.\n
Cause: No matching files were found for the LOCATION clause specification listed in
the previous error message.
Action: No action is required. However, if you expected the LOCATION clause
specification to match one or more files, check the specification and the files in the
directory to make sure that they are correct. If needed, try the operation again.
KUP-05004: Warning: Intra source concurrency disabled because parallel select was
not requested.\n\n
Cause: Intra source concurrency can only be used when parallel select has been
requested.
Action: No action is required this message is informational.
KUP-05005: Warning: Intra source concurrency disabled because a field of type
RECNUM exists.\n\n
Cause: Intra source concurrency cannot be used with RECNUM fields.
KUP-05006: Warning: Intra source concurrency disabled because a complex
terminator string is being used.\n\n
Cause: Intra source concurrency cannot be used with terminators where replicated
substrings in the terminator could cause ambiguity during record parsing.\n\n"
KUP-05007: Warning: Intra source concurrency disabled because the preprocessor
option is being used.\n\n
Cause: Intra source concurrency cannot be used with the PREPROCESSOR option.
KUP-05008: Warning: Intra source concurrency disabled because the input data is
in DELIMITED record format and the characterset is neither fixed width nor
UTF8.\n\n
Cause: Intra source concurrency cannot be used with the DELIMITED record format
if the characterset is neither fixed width or UTF8.
KUP-00552 to KUP-11602 35-17
in VARIABLE record format.\n\n
Cause: Intra source concurrency cannot be used with the VARIABLE record format.
in CSV format with embedded record delimiters/terminators.\n\n
Cause: Intra source concurrency cannot be used with the CSV record format that has
embedded record delimiters/terminators.
KUP-11000: file truncated error\n
Cause: A truncated file was used for the load operation.
Action: Verify unload operation completed successfully.
KUP-11001: files not from the same unload operation\n
Cause: Files used for the load operation were not from the same unload operation.
Action: Verify the files used are from the same unload operation.
KUP-11002: unable to read data chunk string\n
Cause: A read or seek to this data chunk was not possible. This chunk may not have
existed.
Action: Verify the files used for the load operation are correct.
KUP-11003: bad data encountered while reading from file string\n
Cause: There was a datatype conversion error while attempting to convert the data in
the data file to match the datatype of a column in the external table. The message that
follows this one displays the name of the column and the start of the data for the
column that could not be converted. The row containing the bad data is rejected and
not included as a row in the external table.
Action: If the row containing the bad data should not be filtered out, then modify the
definition of the external table so that the datatypes of the columns match the
datatypes of the fields in the data file.
KUP-11004: requested version string not supported by ORACLE_DATAPUMP\n
Cause: This database version (defaulted to COMPATIBLE if not user-specified) was
not supported by ORACLE_DATAPUMP external table access driver. Note: Database
versions before 9.2 were not supported.
Action: Specify a supported version and rerun the operation.
KUP-11005: error seeking in file: string\n
Cause: An attempt to seek to the specified position in file failed.
Action: Review the error message. Resolve the problem and retry the the operation.
Contact Oracle Support Services if the problem cannot be resolved.
KUP-11006: file truncated error in string\n
Cause: A truncated or incomplete file was used for the load operation.
Action: Verify unload operation completed successfully.
KUP-11007: conversion error loading table string.string

Cause: A row could not be loaded into the table because there was a conversion error
for one or more columns in a row.
Action: See the message that follows for more information about the row that could
not be loaded. To avoid this error, make sure the definition of the table being loaded
matches the definition of the table being unloaded.
KUP-11008: conversion error loading table string.string partition string
not be loaded. To avoid this error, make sure the definition of the table being loaded
matches the definition of the table being unloaded.
KUP-11009: data for row: string \n
Cause: A conversion error occurred while loading data into a table. The message
shows values for the field in the row that had the conversion error.
Action: None. This is only an informational message.
KUP-11010: unable to open at least one dump file for fetch\n
Cause: None of the files in the LOCATION clause can be opened for a fetch on an
external table.
Action: A fetch operation on an external table in SQL mode requires that at least one
file could be opened. Check that the directory object and file names to the dump files
are correct.
KUP-11011: the following file is not valid for this load operation\n
Cause: This file could not be used for this load operation. See the following message
for more information.
Action: Verify all the files in the LOCATION clause are from the same unload
operation and that the unload was successful.
KUP-11012: file string in string already exists\n
Cause: The specified file could not be used for this unload because that would mean
overwriting an existing file.
Action: Specify a file that does not currently exist.
KUP-11013: internal number in header in file string is not valid\n
Cause: The specified file could not be used for this operation because the internal
number in the header was not valid.
Action: If the dump files were transferred over, verify the transfer operation was done
correctly.
KUP-11014: internal metadata in file string is not valid\n
Cause: The specified file could not be used for this operation because the internal
metadata stored in this file does not match the metadata stored in the first file piece
set.
Action: Verify all the files in the LOCATION clause are the correct dump files to use.
KUP-11015: error in unloading or loading data\n
Cause: An error has occurred in a stream unload or load operation.
KUP-00552 to KUP-11602 35-19

KUP-11016: database version in file string is not valid\n
Cause: The specified file could not be used for this fetch because its database version
was not compatible with the database version in the other files in the LOCATION
clause.
Action: Verify all the files in the LOCATION clause were populated with compatible
database versions.
KUP-11017: file string not found\n
Cause: The file was not found.
Action: Verify the correct file (path and file name) was specified.
KUP-11018: file string not a valid dump file\n
Cause: This file did not have the correct file format. It could not be used for an
external table fetch operation.
Action: Verify this file is from a SQL mode external table populate operation and that
the operation was successful.
KUP-11019: the following file is not valid for this fetch operation\n
Cause: A file could not be used for this fetch. See the following message for more
information.
Action: Verify all the files in the LOCATION clause are from successful populate
operations. If the files were generated from various populate operations, then verify
that those were done with common attributes such as with the same tables and
compatible database versions.
KUP-11020: header in file string may not contain correct information\n
Cause: The header may be corrupted.
Action: Contact Oracle Support Servicess.
KUP-11021: header in file string has an incompatible version number\n
Cause: A dump file was specified for a load operation whose version number is
incompatible with the dump file version currently produced by the Oracle server on
the system. Usually this message indicates that the dump file was produced by a
newer version of the Oracle server.
Action: Load this dump file using the same version of the Oracle server that created
the file.
KUP-11022: specified file name "string" is invalid\n
Cause: The file name specified for a dump or log file was invalid or null.
Action: Specify a valid file name for the dump or log file.
KUP-11023: specified path for directory object "string" is invalid\n
Cause: The default directory or a directory object specified for a dump or log file
contained an invalid path name or was null.
Action: Specify a valid path name for the directory object.
KUP-11024: This external table can only be accessed from within a Data Pump job.
Cause: An attempt was made to access a temporary external table that was created by
Data Pump to be used internally during the execution of an export or import job.
Action: None
KUP-11025: LOCATION clause is not allowed for ORACLE_HIVE external tables.

\n
Cause: The LOCATION clause was specified for an ORACLE_HIVE access driver.
The ORACLE_HIVE access driver gets LOCATION information from the metadata in
the Hive catalog.
Action: Omit the LOCATION clause when creating an external table using the
ORACLE_HIVE access driver.
KUP-11502: unexpected error loading Java Virtual Machine\n
Cause: The external procedure agent for the external table access driver was unable to
load the Java Virtual Machine.
KUP-11503: cannot access cluster\n
Cause: An attempt was made to access table data in an ORACLE_HIVE or an
ORACLE_HDFS external data source.
Action: Contact the database administrator about gaining access to ORACLE_HIVE
and ORACLE_HDFS external data sources.
KUP-11504: error from external driver: string\n
Cause: An error occurred while attempting to access data in an ORACLE_HIVE or an
ORACLE_HDFS external data source.
Action: Correct the problem as suggested by the error message and retry the
operation.
KUP-11505: invalid value "string" specified for access parameter "string"\n
Cause: A NULL or invalid value was supplied for the access parameter.
Action: Correct the invalid value and retry the operation.
KUP-11506: cannot change cluster in the same session\n
Cause: The first access to an Oracle BigData external table within a database session
establishes the cluster for that session. This is determined by the cluster specified in
the table's access parameters or, if no cluster was specified in the table's access
parameters, by the default cluster set in the Oracle Big Data configuration file.
Accessing an Oracle BigData external table in a different cluster within the same
database session is not allowed.
Action: Establish a new database session and retry the operation.
KUP-11507: missing separator at offset string in line "string"\n
Cause: Access parameters in an Oracle Big Data external table as well as entries in the
Oracle Big Data configuration file were lists of one or more property name or value
pairs. In some cases, the property name does not require a value. In other cases where
a value must be supplied with the property name, the two must be separated by an
equal sign ('=') or a colon (':').
operation.
KUP-11508: invalid character at offset string in line "string"\n
Cause: An invalid multibyte UTF character was encountered in the access parameters
of an Oracle Big Data external table.
KUP-00552 to KUP-11602 35-21
KUP-11509: invalid escape sequence at offset string in line "string"\n

Cause: An invalid escape sequence was encountered in the access parameters of an
Oracle Big Data external table. This may be caused by \unnnn Unicode code point
that does not generate a valid Unicode character.
operation.
KUP-11510: missing value at offset string in line "string"\n
Cause: Access parameters in an Oracle Big Data external table as well as entries in the
Oracle Big Data configuration file were lists of one or more property name or value
pairs. In some cases, the property name does not require a value. In other cases,
where a value must be supplied with the property name, the two must be separated
by an equal sign ('=') or a colon (':'). In this instance, a property name and a separator
were found without a corresponding value.
operation. Supply a value if the property name requires one. Otherwise, remove the
separator and supply only the property name.
KUP-11511: failed to initialize logging in external driver\n
Cause: The external driver code could not initialize a context for logging messages.
This usually indicates a problem with the value of the Java classpath used by the
external driver.
Action: Contact your system administrator to examine the contents of both the Oracle
Big Data configuration file and the Oracle Big Data log4j configuration file to ensure
that the entries in these files contain correct information.
KUP-11516: memory allocation error while initializing the Java Virtual Machine\n
Cause: An error occurred while trying to allocate memory in order to initialize the
Java Virtual Machine in the external driver.
KUP-11523: external driver failed with unexpected error: string\n
Cause: The ORACLE_HIVE or ORACLE_HDFS external driver encountered an
unexpected error condition.
KUP-11524: initialization failure for Java Native Interface (JNI) call\n
Cause: The external driver encountered an unexpected error while trying to initialize
its internal context for call the Java Native Interface (JNI). This may indicate a
classpath problem in the Oracle Big Data configuration file or a problem in the Oracle
Big Data log4j configuration file.
Action: Contact your system administrator to examine the contents of both the Oracle
Big Data configuration file and the Oracle Big Data log4j configuration file to ensure
that the entries in these files contain correct information.
KUP-11525: The external driver was unable to attach to the Java Virtual Machine.\n
Cause: The external driver encountered an unexpected error while trying to attach a
thread to the Java Virtual Machine.
KUP-11526: memory allocation failure for Java Native Interface (JNI) call\n
Cause: An error occurred while trying to allocate memory in order to make a Java
Native Interface (JNI) call in the external driver.
KUP-11527: The external driver was unable to attach to shared memory.\n
Cause: The external driver encountered an unexpected error while trying to attach to
a shared memory segment.
KUP-11530: value for com.oracle.bigdata.buffersize larger than maximum allowed
value number\n
Cause: The com.oracle.bigdata.buffersize was specified for the external table and the
value specified was larger than the maximum allowed value.
Action: Change the value specified for com.oracle.bigdata.buffersize to be smaller
than the maximum value reported in the message.
KUP-11531: missing mandatory property "string" in the Oracle Big Data
configuration file\n
Cause: A mandatory property was not found in the Oracle Big Data configuration file.
Action: Contact your system administrator to modify the Oracle Big Data
configuration file so that it contains all of the required information.
KUP-11532: duplicate property "string" in the Oracle Big Data configuration file\n
Cause: A duplicate property was found in the Oracle Big Data configuration file.
Action: Contact your system administrator to remove all duplicate properties from
the Oracle Big Data configuration file.
KUP-11533: error collecting JVM information: string\n
unexpected error while trying to collect information such as memory usage from the
Java Virtual Machine (JVM).
KUP-11534: external driver JNI initialization failure: string\n
unexpected error while trying to initialize its internal context for calling the Java
Native Interface (JNI). This may indicate a classpath problem in the Oracle Big Data
configuration file or a problem in the Oracle Big Data log4j configuration file.
KUP-11535: XAD version "string" incompatible with JXADProvider version
"string"\n
Cause: A version mismatch between the ORACLE_HIVE or ORACLE_HDFS access
driver and the external driver Java components has been detected.
KUP-11536: external driver MTA initialization failure: string\n
Cause: The ORACLE_HIVE or ORACLE_HDFS multithreaded external agent
encountered an initialization failure that prevented it from starting.
KUP-00552 to KUP-11602 35-23
KUP-11542: error initializing dynamic-link librarian: string\n

Cause: An error occurred while trying to initialize the dynamic-link librarian needed
to access the Java Virtual Machine library.
KUP-11543: error accessing the Java Virtual Machine library: string\n
Cause: An error occurred while trying to open the Java Virtual Machine library in the
external driver.
KUP-11544: error locating symbol address in the Java Virtual Machine library:
string\n
Cause: An error occurred while trying to locate a symbol address in the Java Virtual
Machine library.
KUP-11545: Cannot set the NLS parameter string to the required value string.
Cause: An error occurred while the ORACLE_HIVE or the ORACLE_HDFS external
agent was trying to set up its NLS environment.
KUP-11546: external driver unable to attach to shared memory: [string] [string]
[string] [string] [string] [string][string]\n
unexpected error while trying to attach to a shared memory segment.
KUP-11547: external driver unable to detach from shared memory: [string] [string]
[string] [string] [string] [string][string]\n
unexpected error while trying to detach from a shared memory segment.
KUP-11548: error encountered creating shared memory: [string] [string] [string]
[string] [string] [string][string]\n
Cause: The ORACLE_HIVE or ORACLE_HDFS access driver encountered an
unexpected error while trying to create a shared memory segment.
KUP-11549: error encountered destroying shared memory: [string] [string] [string]
[string] [string] [string][string]\n
Cause: The ORACLE_HIVE or ORACLE_HDFS access driver encountered an
unexpected error while trying to destroy a shared memory segment.
KUP-11550: invalid JNI version "string" encountered while initializing the Java
Virtual Machine\n
Cause: A Java Native Interface JNI version error occurred while trying to create and
initialize the Java Virtual Machine in the external agent.
KUP-11551: error generating file name for file "string" in directory "string": string\n
Cause: An error occurred while trying to generate a full file name specification.
KUP-11552: error initializing the Java Virtual Machine: string\n
Cause: An error occurred while trying to create and initialize the Java Virtual
Machine in the external agent.
KUP-11553: The Oracle Big Data configuration file "string" is empty.\n
Cause: There was no content in the Oracle Big Data configuration file.
Action: Contact your system administrator to correct the configuration files for the
Hadoop cluster.
KUP-11554: error accessing the Oracle Big Data configuration file "string": string\n
Cause: A file I/O error occurred while attempting to access the Oracle Big Data
configuration file.
Hadoop cluster.
KUP-11555: error opening the Oracle Big Data configuration file "string": string\n
Cause: A file I/O error occurred while trying to open the Oracle Big Data
configuration file.
Hadoop cluster.
KUP-11556: error reading the Oracle Big Data configuration file "string": string\n
Cause: A file I/O error occurred while trying to read from the Oracle Big Data
configuration file.
Hadoop cluster.
KUP-11557: error closing the Oracle Big Data configuration file "string": string\n
Cause: A file I/O error occurred while trying to close the Oracle Big Data
configuration file.
Hadoop cluster.
KUP-11558: invalid cluster name "string"\n
Cause: An invalid cluster name was specified for the external table in the
com.oracle.bigdata.cluster access parameter. The name must contain only
alphanumeric characters or the underscore character. In Oracle release 12.1.0.2, the
cluster name is limited to 15 bytes. In Oracle release 12.2 and higher, the cluster name
is limited to 113 bytes.
Action: Correct the cluster name for the external table and retry the operation.
KUP-11559: invalid default cluster name "string"\n
Cause: An invalid cluster name was specified for the bigdata.cluster.default property
in the Oracle Big Data configuration file. The name must contain only alphanumeric
characters, the hyphen or underscore character. In Oracle release 12.1.0.2, the cluster
KUP-00552 to KUP-11602 35-25
name is limited to 15 bytes. In Oracle release 12.2 and higher, the cluster name is
limited to 113 bytes.
Action: Contact your system administrator to correct the value of the
bigdata.cluster.default property in the Oracle Big Data Configuration file and retry
the operation.
KUP-11560: error accessing the Oracle Big Data cluster directory "string": string\n
Cause: A file I/O error occurred while attempting to access the Oracle Big Data
cluster directory file.
Hadoop cluster.
KUP-11600: unable to find first record in a split with I/O buffer size of number
kilobytes\n
Cause: The access driver was unable to find the first record in the split for a Hadoop
Distributed File System (HDFS) file.
Action: The access driver requires that the size of records in the file are not larger than
the size of the I/O buffers. Try increasing the size of the I/O buffers with the access
parameter com.oracle.bigdata.fieldmode.buffersize.
KUP-11601: record exceeded the maximum record size of number kilobytes\n
Cause: The access driver found a record in a Hadoop Distributed File System (HDFS)
file that is longer than the largest size allowed for this table.
Action: The access driver requires that the size of records in the file are not larger than
the size of the I/O buffers. Try increasing the size of the I/O buffers with the access
parameter com.oracle.bigdata.fieldmode.buffersize.
KUP-11602: conversion error for column string in column array row number\n
Cause: There was a datatype conversion error while attempting to convert the data in
the data file to match the datatype of a column in the external table.
Action: Make sure the data is correct. Also verify that the data types specified for the
fields are correct.
36
LCD-00100 to LCD-00219
LCD-00100: internal error, argument [number]
Cause: An internal error has occurred
Action: Report it to your System Administrator immediately
LCD-00111: value not in legal range [string]
Cause: The value of the parameter is outside bounds
Action: Refer to the manual for the bounds on the parameter
LCD-00112: illegal integer radix specification [string]
Cause: Self Explanatory
Action: valid characters are 'd', 'h', 'D' and 'H'
LCD-00113: integer conversion error or negative integer [string]
Cause: A bad or negative integer was assigned to an integer parameter
Action: Self explanatory
LCD-00114: illegal boolean response [string]
Cause: You a value than TRUE or FALSE to a boolean parameter
Action: Boolean parameters only take TRUE or FALSE
LCD-00122: unrecognized keyword [string]
Cause: You have misspelled the parameter name
Action: Spell the parameter name correctly
LCD-00128: invalid positional parameter value [string]
Cause: An invalid positional parameter value has been entered
Action: Remove the invalid positional parameter
LCD-00161: ORACLE error (possible syntax error) parameter [string]
Cause: Possible syntax error. Additional messages follow.
Action: Correct the parameter in error.
LCD-00201: could not open specified filename [string]
Cause: The file specified does not exist
Action: Create an appropriate parameter file
LCD-00203: missing keyword [string]
Cause: A keyword is expected but none was found
Action: Add a keyword followed by an '=' sign and a parameter value
LCD-00100 to LCD-00219 36-1
LCD-00204: left parenth and no parameter specified [string]

Cause: A parameter list was started but no parameter was specified
Action: Add an appropriate list of values and close the parameter list
LCD-00205: unbalanced parentheses [string]
Cause: Self explanatory
Action: Balance the parentheses
LCD-00206: positional parameter entered after keyword [string]
Cause: An '=' sign is missing
Action: All keywords must be followed by '=' signs
LCD-00207: nested parentheses encountered [string]
Cause: Only one set of parentheses is permitted
Action: Remove the nested parentheses
LCD-00208: unexpected keyword in value list [string]
Cause: A keyword was found instead of a value
Action: Insert an appropriate value for the given parameter
LCD-00209: missing value for keyword at end of string [string]
Cause: A keyword is specified with no value
Action: Specify a valid value for the keyword
LCD-00210: illegal assignment operator [string]
Cause: You used a sign other than '=' to assign a keyword a value
Action: Use only the '=' sign
LCD-00211: unexpected delimiter [string]
Cause: An invalid delimiter was found between values
Action: A comma or a space is a valid delimiter
LCD-00212: runaway quoted string [string]
Cause: The parameter value was quoted on the left side but not on the right
Action: Quote the parameter value on both sides
LCD-00215: parameter files nested too deep [string]
Cause: Too many levels of indirection of file parameters. Maximum is 3.
Action: Reduce the level of indirection to less than 3
LCD-00217: failure while processing file parameter [string]
Cause: An error occurred while processing the specified file parameter
Action: Specific details will appear in other messges
LCD-00218: error in file [string]
Cause: An error occurred in the particular file.
Action: Refer to the other messages for the specific error.
36-2 Error Messages
LCD-00219: nested include file [string] is too large

Cause: There is a limit on the size of a parameter file, and it was exceeded. This limit
is now 8192 bytes.
Action: Remove characters from the file to make it smaller, or use another level of
nesting.
LCD-00100 to LCD-00219 36-3
36-4 Error Messages
37
LFI-00002 to LFI-01525
LFI-00002: Out of memory. string
Cause: The File IO package failed in trying to dynamically allocate memory. function
name is used for additional comments to indicate where, when and why the error
occured.
Action: Perform whatever actions necessary to make more memory available to the
executing program.
LFI-00003: Internal exception code. icode = [string], [string].
Cause: Unknown - indicated by parameters. The first '%s' gives the internal exception
code; the second is for any other additional comments.
Action: Report to the appropriate development group
LFI-00004: Call to string failed.
Cause: A function call has failed. This error is a generic message to show that the
exception has occurred in a particular function function name. This allows the client
to know the trace runtime calling sequence by examining the exception stack.
LFI-00005: Free some memory failed in string.
Cause: A call to free some memory in function function name has failed.
Action: See the accompanying error messages for more information and contact
Oracle Worldwide Support immediately.
LFI-00006: Invalid parameter to function string.
Cause: The function was called with an invalid parameter.
Action: Check the function call to make sure that the correct parameters are being
passed.
LFI-00007: NLSRTL's call failed. string.
Cause: LX calls return failure
Action: Check if our parameters are correct. Contact the appropriate group
immediately if we parameters are valid.
LFI-00008: SLTS's initializing/terminating mutex failed for string.
Cause: SLTS's call return failure in function '%s'.
Action: Contact the appropriate development group.
LFI-00100: Unable to perform operation, file not opened in string.
Cause: The file has not been successfully opened at the time the operation is
attempted.
LFI-00002 to LFI-01525 37-1
Action: Check to make sure that the file exists (for read) or that the program has
access to the write a file (for write). It is also possible that the file was just never
opened
LFI-00101: Write failed, file cannot be written to.
Cause: The buffer write operation failed. Possibly due to incorrect parameters being
passed in.
Action: Check the underlying error for more information.
LFI-00102: Unable to seek in sequentially accessed file.
Cause: The file was opened with the flag LFILFA_SEQ for sequential file operations.
Use seek only on files that are opened with the LFILFA_RANDOM flag for random
access.
Action: Check to see how the file is being opened and accessed and make the two
operations consistent (that is, make them both operations either sequential or
random).
LFI-00103: Seek operation failed.
Cause: The buffer seek operation failed. Probably due to incorrect parameters or flags.
Action: Check syntax of the seek command and retry the operation.
LFI-00104: Read operation failed.
Cause: The buffer read operation failed. Probably due to incorrect parameters or flags.
Action: Check syntax of the read command and retry the operation.
LFI-00105: Unable to add path.
Cause: One of the following might have caused the error: the current path might not
be in the proper format the directory might not be in the proper format the name
object might not have been initialized properly
Action: Check the format of the current path and the new directory; check that the
name object was initialized properly.
LFI-00106: Path object holds more than one path.
Cause: The path object passed to lfippth() holds more than one path.
Action: Make sure that the path object used in lfippth() holds only one path.
LFI-00107: Open does not expect the file [string][string] to exist.
Cause: The flags specified for the open indicate that the file does not exist. However,
the file does exist.
Action: Check to make sure that the options that were specified for the file are correct
and that you do not expect that the file should exist. If so then find out why the file
does exist.
LFI-00108: Open expect the file [string][string] to exist.
Cause: The flags specified for the open indicate that the file the file to exist and it does
not.
Action: Check to make sure that the options that were specified for the file are correct
and that you expect that the file should exist. If so then find out why the file doesn't.
LFI-00109: Unable to open file [string][string]. string.
Cause: Either: the process does not have the proper access rights to open the file the
file is already open
37-2 Error Messages
Action: Check to make sure the proper access permissions are assigned. If they are
and the file still cannot be opened, then contact Oracle Worldwide Support.
LFI-00110: Unable to initialize the Buffer Manager.
Cause: The Buffer Manager initialization routine failed; probably because memory
was exhausted.
LFI-00111: No other flags allowed in fixed length format.
Cause: The function lfigfo() was called with an invalid File ID Descriptor. The valid
File ID Descriptors are LFISTDIN, LFISTDOUT, and LFISTDERR.
Action: Check the call to lfigfo() to make sure it is correct.
LFI-00113: Unable to initialize the Standard File object string.
Cause: The call to open the standard file object failed.
Action: Check the underlying errors for more information.
LFI-00114: Append is not allowed with string.
Cause: Attempting to append using certain options.
Action: Check the flag options to verify its usage.
LFI-00115: Buffer free failed.
Cause: Probably do to the buffer flush failing.
LFI-00116: Unable to close file in operation string.
Cause: The file close operation failed.
LFI-00117: Unable to rename file.
Cause: The rename operation failed. Rename is called when we are protecting a file
by operating on a temp file.
Action: Check to make sure that the process has the correct access rights to perform a
rename.
LFI-00118: Unable to change type to Unknown.
Cause: The function lfichty() was called to change the file extension to LFIEXUNK
(Unknown). This is not a valid operation.
Action: Check why you are doing this. If the extension is already unknown then you
do not need to do this. If you just want no extension then use the extension type
LFIEXNONE.
LFI-00119: Unable to Abort an Unprotected file.
Cause: The Abort function lfiabt() was called on a file that was not opened as a
protected file. As such the abort operation is not valid.
Action: Check to see if you intended to open the file as a protected file.
LFI-00120: Unable to parse root filename string.
Cause: The root filename that was given to lfimknam() is not in a format that this
platform understands.
Action: Check the format of the filename and retry the operation.
LFI-00002 to LFI-01525 37-3
LFI-00121: Only one of REPLACE, or PROT allowed for opty.

Cause: Two or more of the following open type options were specified for the lfilini()
function: LFILOPTY_REPLACE, or LFILOPTY_PROT.
Action: Remove one or more the of options such that you are only passing in one of
the three.
LFI-00122: Can only delete a file if we create it.
Cause: The delete file flag was specified for a file that was not created by this file
operation. The ability to delete a file is not portable. As such the only deletion that is
allowed by this package is if we know we want to delete the file when we create it.
Action: You can only delete a file that you create. If you need to delete a file that you
do not create then you will have to find another means of doing so.
LFI-00123: Cannot access file Sequentially and Randomly.
Cause: Both the LFILFA_SEQ (sequential) and LFILFA_RANDOM (random) flags
were specified during the file object creation. This is not allowed. Only one of the two
may be specified.
Action: Choose how you wish to access the file. If you choose random you can still
access sequentially by just not using the repositioning functions.
LFI-00124: No access mode was specified, default is sequential.
Cause: Neither LFILFA_SEQ (sequential) or LFILFA_RANDOM (random) were
specified during file object creation.
Action: The default is sequential but this should be explicitly set.
LFI-00125: Random access only allowed on fixed length record files.
Cause: The LFILFA_RANDOM flag was specified on a file that was not organized
into fixed-length records. Random access is only allowed on fixed-length record files.
Action: Determine if the organization of your data needs to be in variable-length
records and if you need to have random access to the file. If both conditions are true
then you might need to buffer the entire file or enough of it to remove your need for
random access. Another option is to close and rescan the file although this is not the
optimal solution.
LFI-00126: Record format can only be one of Fixed or Variable.
Cause: Both LFILRF_FIXED (fixed) and LFILRF_VAR (variable) were specified during
file object creation. Only one of the two is allowed for a given file.
Action: Determine how the file is organized and choose the option that matches.
LFI-00127: No Record Format was specified, default is variable.
Cause: Neither LFILRF_FIXED (fixed) or LFILRF_VAR (variable) were specified for
record format. One of the two must be specified for each file.
Action: The default is LFILRF_VAR, but this should be explicitly set during file object
creation.
LFI-00128: Carriage Control is only valid for Standard file objects.
Cause: The Carriage Control option is only valid for the standard file objects
(LFISTDIN, LFISTDOUT, LFISTDERR). You may not specify this option for any other
type of file.
Action: Choose between LFILRF_FIXED and LFILRF_VAR for the record format.
37-4 Error Messages
LFI-00129: Invalid option string were specified on an input only file.

Cause: The file was opened as input only but the output mode option
LFILRF_WR_ASIS or delete option LFLOPTY_DELETE was specified.
Action: Check to see how you intend to open this file and make the necessary
changes.
LFI-00130: Input option specified on output only file.
Cause: The file was opened as output only but one of the input mode options
(LFILRF_READ_NL or LFILRF_FORCE_NL) or was specified.
changes.
LFI-00131: No open type specified.
Cause: The file object was created without an open type (that is, LFILOPTY_INPUT,
LFILOPTY_OUTPUT, etc.).
Action: Decide how the file should be accessed and specify one of the open types.
LFI-00132: Record length string is greater than max length of string.
Cause: The record length specified for the file is greater than the max supported by
this platform.
Action: Decrease the record length.
LFI-00133: Trying to create file string that already exists.
Cause: The file object was initialized with LFILOPTY_OUTPUT and without
LFILOPTY_REPLACE and yet a file by this name already exists.
Action: Check to make sure that you are creating the right file. If you intend to
overwrite the file if it exists that specify the replace option LFILOPTY_REPLACE
when initializing the file object.
LFI-00134: Unable to protect a file for an append operation.
Cause: The LFILOPTY_APPEND and LFILOPTY_PROT options were both specified
for the file. This is currently not allowed because it would require copying the entire
file at open time.
Action: Decide if you really need to protect the file for append. If so then think about
making a copy of it before appending.
LFI-00135: Unable to remove temporary file.
Cause: A temporary file was created to protect a file and when the the tempfile was
nolonger needed it LFI attempted to remove it and was unable to do so.
Action: Check the permissions and where the temp files are being created.
LFI-00136: Unable to change type of open file.
Cause: The function lfichty() was called on an opened file.
Action: This is a bug in the client code. lfichty() cannot be used in this case.
LFI-00137: Unable to perform string on a file object that is string.
Cause: Unable to perform an LFI operation on a file object for the given reason.
Action: Take the appropriate corrective measure. For example if a file is supposed to
be opened before the operation can be performed, client code will need to open the
file first.
LFI-00002 to LFI-01525 37-5
LFI-00138: Unable to perform string on a name object that is string.

Cause: Unable to perform an LFI operation on a name object for the given reason.
Action: Take the appropriate corrective measure.
LFI-00139: Option string cannot be used with option string in calling string.
Cause: First option cannot be used with second option in such a function call.
Action: Re-examine code to determine which option is needed.
LFI-00140: Invalid option string were specified on input-output file.
Cause: The file was opened as input-output and one of the mode options
(LFIOPTY_DELETE or non-LFIOPTY_RANDOM) was specified.
changes.
LFI-00141: Unable to abort file in operation string.
Cause: The abort operation failed.
LFI-00142: Unable to delete an existing file [string][string] not owned by Oracle.
Cause: The file was not created by Oracle.
Action: Change owner of file to Oracle or give Oracle access privileges to delete it.
LFI-00143: Unable to delete non-existent file string.
Cause: The file to be deleted does not exist.
LFI-00144: File [string][string] does not exist
Cause: The file does not exist.
Action: Check to make sure the file exists and retry the operation.
LFI-00145: User buffer too short.
Cause: The buffer that was passed is not large enough.
Action: Allocate a larger buffer and retry the operation.
LFI-00146: copy does not expect the file string.string to exist
Cause: We are expecting the destination file not to exist and it does.
Action: Find out why the file does exist.
LFI-00147: File string.string does not exist
Cause: The file does not exist.
Action: Check to make sure the file exists and retry the operation.
LFI-00148: string can be called only on files opened in byte mode
Cause: A routine that should be used only for files in byte mode was called for a file
that was opened in record mode
Action: In order to use this function, the file should be opened in byte mode.
LFI-00149: Error on destroying hash table in function string
Cause: We were expecting the cache path object and it does not.
Action: In order to use this function, the path object should be cache path object.
37-6 Error Messages
LFI-00150: Error on creating hash table in function string

Cause: routine failed to create path object hash table
Action: make sure that startsize <= LHTQMAXSLOTS
LFI-00151: Error on inserting into hash table in function string
Cause: routine failed to insert into hash table
Action: make sure there is enough memory for allocation and that the hash table
exists.
LFI-00152: Read operation (byte mode) failed.
Cause: Byte mode read operation failed. Probably due to incorrect parameters or
flags, or trying to read beyond end of file.
Action: Check syntax of the read command and size of file.
LFI-01000: Unable to write line to file.
Cause: The file being written to may no longer be open or we may have reached the
end of the file.
Action: Examine underlying errors for more information.
LFI-01001: Unable to write string bytes to file.
Cause: The file being written to may no longer be open or we may have reached the
end of the file.
LFI-01002: Unable to read line from file.
Cause: The file being read from may no longer be open.
LFI-01003: Unable to read string bytes from file.
Cause: The file being read from may no longer be open.
LFI-01004: Unable to empty buffer.
Cause: The buffer manager is probably unable to write to the underlying file.
LFI-01005: Unable to fill buffer.
Cause: The buffer manager is probably unable to read from the underlying file.
LFI-01006: File ends in partial character in string.
Cause: A line ends in a partial character.
LFI-01007: Line is too long; encountered in function string.
Cause: The length of the line exceeds the maximum length.
LFI-00002 to LFI-01525 37-7
LFI-01500: Error condition on call to OSD function string.

Cause: An error condition arises in calling an OSD function. This message occurs if
calls to malloc or free functions failed.
LFI-01501: tmpnam() fails to generate temporary file name.
Cause: Operating system was unable to create temporary file name.
Action: Contact the development organization.
LFI-01502: Base filename does not exist.
Cause: The filename that was parsed had no base file. It was either all path or
extension.
Action: Check the filename being passed in to make sure it is correct.
LFI-01503: Max filename size exceeded generating filename.
Cause: While building a filename we exceeded the buffer allocated to hold the new
filename.
LFI-01504: fseek() failed(OSD return value = string) in string.
Cause: The function fseek() returned an error condition.
LFI-01505: fclose() failed(OSD return value = string) in string.
Cause: The function fclose() returned an error condition.
LFI-01506: fflush() failed(OSD return value = string).
Cause: The function fflush() returned an error condition.
LFI-01507: fwrite() failed(OSD return value = string) in string.
Cause: File pointer may be null or may not be opened for write.
LFI-01508: access() failed.
Cause: Call to access() failed.
LFI-01509: fopen() failed(OSD return value = string).
Cause: Call to fopen() failed.
LFI-01510: fread() failed(OSD return value = string) in string.
Cause: Call to fread() failed.
LFI-01511: unlink() failed(OSD errno = string) in string.
Cause: Call to unlink() failed.
37-8 Error Messages
LFI-01512: stat() failed

Cause: Call to stat() failed.
LFI-01514: ftell() failed in string
Cause: The ftell() function returned an error.
LFI-01515: truncate() failed.
Cause: The function truncate() returned an error condition.
LFI-01516: read() failed (OSD return value = string) in string.
Cause: Call to read() failed.
LFI-01517: open() failed(OSD return value = string).
Cause: Call to open() failed.
LFI-01518: write() failed(OSD return value = string) in string.
Cause: Call to write() failed.
LFI-01519: llseek() failed(OSD return value = string) in string.
Cause: The llseek() function returned an error.
LFI-01520: close() failed(OSD return value = string) in string.
Cause: The function close() returned an error condition.
LFI-01521: fsync() failed(OSD return value = string) in string.
Cause: The function fsync() returned an error condition.
LFI-01522: opendir() failed.
Cause: The function opendir() returned an error condition.
LFI-01523: rename() failed.
Cause: The function rename() returned an error condition.
LFI-01524: fdopen() failed(OSD return value = string).
Cause: Call to fdopen() failed.
LFI-01525: setvbuf() failed.
Cause: A call to lficstd() had failed.
LFI-00002 to LFI-01525 37-9
Action: Contact development service
38
LPX-00000 to LPX-01160
LPX-00000: normal, successful completion
Cause: Normal exit
LPX-00001: NULL pointer
Cause: A NULL pointer was detected as an internal error condition.
Action: This is a programming error by the caller of the XML parser. Please contact
someone who can fix the problem.
LPX-00002: out of memory
Cause: The operating system has run out of memory.
Action: Make more memory available to the program.
LPX-00003: duplicate entry in hash table
Cause: An internal error has occurred (a key was requested to be placed in a hash
table but was already there).
Action: Contact Oracle Support Services and report the error.
LPX-00004: internal error "~s"
LPX-00005: ~1s buffer overflow, maximum size is ~2u bytes
Cause: A name, quoted string, URL, or other document component was too long.
Action: Restrict the component to the maximum size shown.
LPX-00006: invalid child type for parent node
Cause: An attempt was made to add an invalid node-type to a parent node.
Action: Correct the code.
LPX-00007: unexpected end-of-file encountered
Cause: The documented ended unexpectedly, perhaps due to truncation.
Action: Verify that the document is complete.
LPX-00008: invalid memory callback
Cause: The memory callback structure passed to xmlinit was missing the allocate or
free functions (or both).
Action: Provide both functions in the callback structure.
LPX-00000 to LPX-01160 38-1
LPX-00011: In line ~1u of ~2s [general entity ~3S]:

Cause: Error message prefixes, not errors themselves. These are the possible banner
messages which appear before an XML error to describe the position (line#) and
source (buffer or URI) in which the error occurred, as well as the entity's name (if the
source is an entity). Parameter entity banner must be at +1 to non-entity banner,
general entity at +2 (see lpxerr.c).
Action: No action required. This is not an error message.
LPX-00012: Unicode data alignment error
Cause: An input Unicode (UCS2) datum was not aligned properly.
Action: UCS2 data consists of an array of shorts (ub2) which must be aligned on an
even-byte boundary.
LPX-00013: wrong node type
Cause: The wrong node type was given as argument to a DOM call.
Action: Review the failing function call, consult the documentation, and make sure
the node types passed as correct.
LPX-00014: context is not clean
Cause: An operation was performed on a context that has already been used (so is not
"clean").
Action: Some functions must be performed on a newly initialized context before being
used for parsing. For example, setting a shared DTD. Change the code and do the call
before parsing.
LPX-00017: ~1sNodeName: <~2S>
Cause: More error message boilerplate.
Action: No action required. This is not an error message.
LPX-00018: internal error "nested open strings"
LPX-00019: property "~s" unknown
Cause: An unexpected error has occured in a subsystem used by XML. Subcode is the
error code returned by that failing subsystem.
Action: Contact Oracle Support Services and report the error and subcode.
LPX-00050: initialization error: NLS mismatch
Cause: A language ID was specified without the matching global area.
Action: Internal error, contact Oracle Support Services and report the error.
LPX-00051: NLS initialization failed
Cause: The NLS (National Language Support) package initialization failed.
LPX-00052: LEH initialization failed
Cause: The LEH (Library Exception Handling) package initialization failed.
38-2 Error Messages
LPX-00053: LML initialization failed

Cause: The LML (Low-Level Memory manager) package initialization failed.
LPX-00054: LPU initialization failed, error ~u
Cause: The LPU (URL Parser/Loader) package initialization failed.
LPX-00100: root element "~1S" does not match DTD root "~2S"
Cause: Validity Constraint 2.8 failed: "The Name in the document type declaration
must match the element type of the root element." *Example: <?xml version="1.0"?>
<!DOCTYPE greeting [ <!ELEMENT greeting (#PCDATA)> ]> salutationHello!/
salutation *Explanation: The document's root element, salutation, does not match the
root element declared in the DTD (greeting).
Action: Correct the document.
LPX-00101: parameter-entity markup cannot be split up
Cause: Validity Constraint 2.8 failed: "Parameter-entity replacement text must be
properly nested with markup declarations." *Example: <?xml version="1.0"?> <!
DOCTYPE greeting [ <!ENTITY % e "<!ELEMENT "> %e; greeting (#PCDATA)> ]>
greetingHello!/greeting *Explanation: The parameter entity 'e' contains markup which
may not be split up; the entire ELEMENT (or ATTLIST or ENTITY) definition must be
present in one piece.
LPX-00102: standalone document declaration should be "no"
Cause: Validity Constraint 2.9 failed: "Standalone document declaration must have
the value 'no' if any external markup declarations contain declarations of: * attributes
with default values - or - * entities - or - * attributes with values subject to
normalization - or - * element types with element content"
LPX-00103: document structure does not match DTD
Cause: Validity Constraint 3 failed: "An element is valid if there is a declaration
matching elementdecl where the Name matches the element type, and one of the
following holds: * The declaration matches EMPTY and the element has no content *
The declaration matches children and the sequence of child elements belongs to the
language generated by the regular expression in the content model, with optional
white space (characters matching the nonterminal S) between each pair of child
elements. * The declaration matches Mixed and the content consists of character data
and child elements whose types match names in the content model. * The declaration
matches ANY, and the types of any child elements have been declared."
LPX-00104: element "~S" is not declared in the DTD
Cause: Validity Constraint 3 failed: The named element has no matching elementdecl
in the DTD
LPX-00105: element "~S" is not empty as required by the DTD
Cause: Validity Constraint 3 failed: The named element is declared as EMPTY in the
DTD but contains sub-elements in the document.
LPX-00000 to LPX-01160 38-3

LPX-00106: attribute "~1S" of element "~2S" is undefined
Cause: Validity Constraint 3.1 failed:
LPX-00107: element "~S" has multiple declarations
Cause: Validity Constraint 3.2 failed: "No element type may be declared more than
once."
Action: Correct the DTD.
LPX-00108: parameter-entity parenthetical cannot be split up
Cause: Validity Constraint 3.2.1 failed: "Parameter-entity replacement text must be
properly nested with parenthesized groups. For interoperability, if a parameter-entity
reference appears in a choice, seq, or Mixed construct, its replacement text should not
be empty, and neither the first nor last non-blank character of the replacement text
should be a connector (| or ,). *Example: <?xml version="1.0"?> <!DOCTYPE foo [ <!
ELEMENT greeting (#PCDATA)> <!ENTITY % e "(#PCDATA|"> <!ELEMENT foo
%e; greeting)> ]> greetingHello!/greeting *Explanation: The parenthetical content of the
'e' entity may not be split up into sections: both open and close parentheses must be in
the same declaration.
LPX-00109: duplicate name "~S" in mixed-content declaration
Cause: Validity Constraint 3.2.2 failed: "The same name must not appear more than
once in a single mixed-content declaration." *Example: <!ELEMENT p (#PCDATA|a|
b|c|d|a)> *Explanation: 'a' occurs more than once in the mixed-content declaration.
LPX-00110: invalid ~1s "~2S" (not a Name)
Cause: Validity Constraint 3.3.1 failed: Given thing is not a Name
LPX-00111: invalid ~1s "~2S" (not a Nmtoken)
Cause: Validity Constraint 3.3.1 failed: Given thing is not a Nmtoken
LPX-00112: element "~S" has multiple ID attributes
Cause: Validity Constraint 3.3.1 failed: "No element type may have more than one ID
attribute specified."
LPX-00113: element "~1S" ID attribute "~2S" must be #IMPLIED or #REQUIRED
Cause: Validity Constraint 3.3.1 failed: "An ID attribute must have a declared default
of #IMPLIED or #REQUIRED."
LPX-00114: element "~1S" attribute "~2S" has invalid enumeration value "~3S"
Cause: Validity Constraint 3.3.1 failed: "Values of this type must match one of the
Nmtoken tokens in the declaration."
38-4 Error Messages
LPX-00115: element "~1S" is missing required attribute "~2S"

Cause: Validity Constraint 3.3.2 failed: "If the default declaration is the keyword
#REQUIRED, then the attribute must be specified for all elements of the type in the
attribute-list declaration."
LPX-00116: element "~1S" attribute "~2S" has invalid value "~3S", must be "~4S"
Cause: Validity Constraint 3.3.2 failed: "If an attribute has a default value declared
with the #FIXED keyword, instances of that attribute must match the default value."
LPX-00118: undefined entity "~S"
Cause: Validity Constraint 4.1 failed: "In a document with an external subset or
external parameter entities with "standalone='no'", the Name given in the entity
reference must match that in an entity declaration."
LPX-00119: element "~1S" attribute "~2S" must be an unparsed entity
Cause: The attribute value must be an unparsed entity.
LPX-00120: entity "~1S" NDATA (notation) "~2S" is undefined
Cause: Entity's NDATA (notation) is undefined
LPX-00121: undefined notation "~S"
Cause: Notation is not known.
LPX-00122: undefined ID "~S" in IDREF
Cause: Validity Constraint 3.3.1 failed: "A name must not appear more than once in
an XML document as a value of this type; i.e., ID values must uniquely identify the
elements which bear them."
LPX-00123: duplicate ID "~S"
Cause: An ID was used twice, they must be unique.
LPX-00124: attribute value should be one or more tokens
Cause: An attribute with tokenized type (IDREFS, ENTITIES, NMTOKENS) did not
contain any tokens.
Action: Value must contain one or more tokens, separated by spaces.
LPX-00125: duplicate entity "~S" (ignored)
Cause: Warning returned by XmlDomGetDecl when original document did not
contain an XMLDecl
Action: This is a warning, not an error. The value XMLERR_NO_DECL is used by the
programmer to detect whether a document had an XMLDecl or not. It does not
indicate a problem.
LPX-00000 to LPX-01160 38-5
LPX-00200: could not convert from encoding ~1s to ~2s

Cause: The conversion cannot be made between the specified encodings.
Action: Choose a data encoding which can represent all expected input encoding
(such as a Unicode-based encoding, UTF-8 or UTF-16).
LPX-00201: unknown encoding "~s"
Cause: The specified encoding was not known. It should be an IANA or Oracle
encoding name.
Action: Use an appropriate encoding.
LPX-00202: could not open "~s" (error ~u)
Cause: The named input (file, URL, etc) does not exist.
Action: Make sure the named input is available and can be opened.
LPX-00203: could not read from "~s" (error ~u)
Cause: Data could not be read from the named input.
Action: Take appropriate action to allow data to be read.
LPX-00204: syntax error
Cause: A syntax error was found.
Action: Check the XML document line and correct it.
LPX-00205: expected ""
Cause: A syntax error was detected in the comment.
Action: Be sure to end the comment with '-->'.
LPX-00214: CDATA section did not end in "]]>"
Cause: A syntax error was detected in the CDATA section.
Action: Be sure to end the CDATA section with ']]>'.
LPX-00215: processing instruction did not end in "?>"
Cause: A syntax error was detected in the PI section.
Action: Be sure to end the PI with '?>'.
LPX-00216: invalid character ~1u (~2X)
Cause: An invalid multibyte character was found.
Action: Use only characters allowed by the XML specification.
LPX-00217: invalid character ~1u (~2x)
Cause: An invalid Unicode character was found.
LPX-00218: invalid character ~1u ('~2c')
Cause: An invalid native (ASCII/EBCDIC) character was found.
LPX-00219: invalid digit '~c' in character reference
Cause: An invalid digit was found in a character reference.
Action: Character references are either &#DDD; where D's are decimal digits, or
&#xHHH; where H's are hexadecimal digits.
LPX-00220: the string "]]>" cannot occur in character data
Cause: Found ']]>' in character data.
Action: Do not use ']]>' in character data.
LPX-00221: the character "<" cannot occur in attribute values
Cause: Found '<' in an attribute value.
Action: Do not use '<' in attribute values.
LPX-00222: error received from SAX callback function
Cause: An error was received from the SAX callback function.
Action: Examine the additional error messages and take corrective action.
LPX-00223: external entity "~s" found in an attribute value
Cause: An external entity reference was found in an attribute value.
Action: Use only references to internal or character entities in attribute values.
LPX-00000 to LPX-01160 38-7
LPX-00224: multiple occurrences of attribute "~S" found

Cause: An attribute occurred multiple times in the same start-tag or empty-element
tag.
Action: Make sure that the attributes are unique.
LPX-00225: end-element tag "~1S" does not match start-element tag "~2S"
Cause: An element tag was not ended properly.
Action: Make sure that the correct end element tag is used.
LPX-00226: entity "~S" is not declared
Cause: An entity is not declared.
Action: Declare the entity before referencing it.
LPX-00227: entity "~S" is not a parsed entity
Cause: An entity reference contained the name of an unparsed entity.
Action: Only reference parsed entities.
LPX-00228: entity reference "~S" refers to itself
Cause: An entity reference contains a recursive reference to itself.
Action: Modify the contents of the entity reference to remove this recursion.
LPX-00229: input source is empty
Cause: An XML input file has no contents.
Action: The XML file representing a document must contain at least one element.
LPX-00230: invalid character ~1u (~2x) found in a Name or Nmtoken
Cause: An invalid character was found in a NAME or NMTOKEN.
Action: Use only the characters allowed for NAMES and NMTOKENS by the XML
specification.
LPX-00231: invalid character ~1u ('~2c') found in a Name or Nmtoken
Cause: An invalid character was found in a NAME or NMTOKEN.
Action: Use only the characters allowed for NAMES and NMTOKENS by the XML
specification.
LPX-00232: invalid use of a parameter entity reference
Cause: A parameter entity reference was found in an improper location in the internal
DTD subset.
Action: Use a parameter entity reference only where markup declarations can occur in
the internal DTD subset, in the external DTD subset, or in an external entity.
LPX-00233: namespace prefixes starting with "xml" are reserved
Cause: Namespace prefix starting with XML was found.
Action: Use another name for the namespace prefix.
LPX-00234: namespace prefix "~S" is not declared
Cause: Namespace prefix is not declared.
Action: Declare the prefix in an attribute list.
38-8 Error Messages
LPX-00235: invalid XML version, must be 1.0 or 1.1

Cause: An invalid XML version was specified. Only version 1.0 of the XML
specification is supported. Version 1.1 may be specified but will be treated as version
1.0.
Action: Use the 1.0 or 1.1 specification and set the version number accordingly.
LPX-00236: invalid character ~1u ('~2c') found in public identifier
Cause: An invalid character was found in a public identifier.
Action: Use only the characters allowed for public identifiers by the XML
specification.
LPX-00237: invalid condition section keyword, must be INCLUDE or IGNORE
Cause: A conditional section <![ keyword [ markup ]]> had invalid keyword, must be
either "IGNORE" or "INCLUDE"
Action: Correct condition section usage in document.
LPX-00238: unterminated conditional section
Cause: A conditional section was not properly terminated with ]]>.
Action: Verify conditional nesting in document and correct.
LPX-00239: invalid attribute type "~s"
Cause: The attribute type is not valid. Options are CDATA, ID, IDREF, IDREFS,
ENTITY, ENTITIES, NMTOKEN, or NMTOKENS.
Action: Check and correct attribute declaration.
LPX-00240: element-start tag is not well formed
Cause: A start-element tag was improperly formed.
Action: Check and correct the start-element syntax.
LPX-00241: entity reference is not well formed
Cause: An entity reference (general or parameter) was not formed properly.
Action: Form entity reference correctly as "&name;" or "%name;".
LPX-00242: invalid use of ampersand ('&') character (use &)
Cause: The ampersand character is used only to start entity or character references.
Action: To include an ampersand character as data, use the built-in & general
entity.
LPX-00243: element attribute value must be enclosed in quotes
Cause: An attribute defined in an element's start-tag must be enclosed in single ('') or
double ("") quotes.
Action: Enclose the attribute value in quotes.
LPX-00244: invalid use of less-than ('<') character (use <)
Cause: The less-than character ('<') is not permitted as data.
Action: Use the built-in entity < instead. Check for mismatched quotes ("') in case
the '<' is part of subsequent markup.
LPX-00245: extra data after end of document
Cause: After the close of the top-level element, more data was found.
LPX-00000 to LPX-01160 38-9
Action: The end-element tag for the top-level element must be the last thing in the
document.
LPX-00246: missing system ID after public ID
Cause: In an external ID declaration, the public ID literal was not followed by the
system ID literal as required.
Action: Provide with public *and* system IDs for 'PUBLIC' type.
LPX-00247: invalid Document Type Declaration (DTD)
Cause: Problems were encountered in the DTD declaration.
Action: Review the DTD and correct the problems.
LPX-00248: invalid entity declaration
Cause: Problems were encountered parsing an entity declaration.
Action: Check and correct the declaration syntax.
LPX-00249: invalid external ID declaration
Cause: Problems were encountered parsing an external ID declaration.
LPX-00250: invalid attribute declaration
Cause: Problems were encountered parsing an attribute declaration.
LPX-00251: conditional sections are valid only in external DTDs
Cause: A condition section is not permitted in internal DTDs.
Action: Remove the condition section.
LPX-00252: invalid entity replacement-text nesting
Cause: Markup included from an entity must nest/group properly. That is, open/
close markup must occur within the same entity. For example, <!DOCTYPE doc [ <!
ENTITY e "/foofoo"> ]> docfoo&e;/foo/doc Is invalid since foo's start-tag occurs in the
top-level document, but the close-tag is provided by the "e" entity. Both start and end
must be provided by the same source.
Action: Examples, such as the ones above, are not permitted.
LPX-00253: missing required version number in XML declaration
Cause: An XML declaration was missing the required version#.
Action: Always provide a version#, which must come first in the declaration. XML is
case sensitive, so only "version" (not "Version", and so on) is valid.
LPX-00254: invalid XML declaration
Cause: Problems were encountered parsing an XML declaration.
LPX-00255: XML standalone declaration must be "yes" or "no"
Cause: The "standalone" parameter in the XML declaration had an invalid value.
Action: standalone must be set to either "yes" or "no". Case is sensitive, so "Yes",
"YES", and so on, are invalid.
LPX-00256: invalid element declaration

Cause: Problems were encountered parsing an element declaration.
Action: Check and correct the declaration.
LPX-00257: invalid children specification in element declaration
Cause: The 'children' specification in an element declaration was invalid.
LPX-00258: invalid "Mixed" specification in element declaration
Cause: The 'Mixed' specification in an element declaration was invalid.
LPX-00259: invalid notation declaration
Cause: Problems were encountered parsing a notation declaration.
LPX-00260: invalid xml:space attribute declaration
Cause: The xml:space attribute must be declared as an enumeration with choices
"default" and "preserve". For example, <!ATTLIST foo xml:space (default|preserve)
'preserve').
Action: Declare the special attribute as above.
LPX-00261: invalid URL ~s
Cause: The specified URL was invalid and could not be parsed.
Action: Correct the URL; consult RFC-2396.
LPX-00262: unsupported protocol ~s
Cause: An URL was encountered which requested a protocol not supported by the
XML parser. Only HTTP and file are currently allowed.
Action: Make the data available through the filesystem or HTTP.
LPX-00263: couldn't connect to host ~s port ~d
Cause: A TCP connection couldn't be opened to the named host.
Action: Verify the hostname and connectivity to the host.
LPX-00264: send failed to host ~s
Cause: An error occurred trying to send data over a TCP connection.
Action: Verify network connectivity, and so on.
LPX-00265: read failed from to host ~s
Cause: An error occurred trying to read data from a TCP connection.
Action: Verify network connectivity, and so on.
LPX-00266: invalid language specification ~s
Cause: The given language specification was invalid.
Action: Language specification has the format language_territory.character set. For
example, "French_France".
LPX-00267: could not resolve relative URL ~s
Cause: The named relative URL couldn't be resolved against its parent.
LPX-00000 to LPX-01160 38-11
Action: Make sure the relative makes sense in relation to its parent URL; see RFC-2396
sections 4, 5, and appendix C.
LPX-00268: invalid access method ~1d, must be 0 to ~2d
Cause: The provided access code was not in the valid range.
Action: The code should be one of the XMLACCESS_xxx codes defined in oraxml.h,
in the range shown in the error message.
LPX-00269: all three access functions (open/close/read) must be provided
Cause: An attempt was made to set the access method callbacks, but all three
functions were not provided.
Action: All three callback functions (open, close, and read) are required. They must all
be provided, even if they are stub functions which do nothing.
LPX-00270: FTP error: ~s
Cause: An error was returned from the FTP server while trying to retrieve a file. See
the specific message for details.
Action: Corrective action depends on the error.
LPX-00271: FTP login failed: ~s
Cause: The username/password combination was invalid for FTP login.
Action: Specify a valid pair.
LPX-00272: FTP server unavailable: ~s
Cause: The FTP server is unavailable for use.
Action: No action is possible from the client side. See server's error message.
LPX-00273: failed to initialize TCP/IP
Cause: The TCP/IP package could not be initialized.
Action: Check with system administrator to see if this is a configuration problem or a
connectivity problem.
LPX-00274: can't import node type
Cause: Some node types (DOCUMENT_NODE & DOCUMENT_TYPE_NODE)
cannot be imported with importNode().
LPX-00275: can't set output/data encoding AFTER parsing
Cause: Output/data encoding must be set after initialization but BEFORE any parsing
has taken place.
Action: Set encoding before parsing any documents.
LPX-00276: bad HTTP/Mime header
Cause: An HTTP reply contained an invalid Mime header.
Action: Verify HTTP reply for accuracy. See RFC 2616.
LPX-00277: no closing quote was seen
Cause: A quoted string was started but not finished.
Action: Put a closing quote in the proper location.
LPX-00278: invalid ~s proxy "~s"

Cause: The proxy specification for the given protocol was invalid.
Action: Check and correct the proxy specification. For HTTP, this is the environment
variable "http_proxy".
LPX-00279: invalid no_proxy "~s"
Cause: The no_proxy specification was invalid.
Action: Check and correct it. no_proxy is a comma- or space-separated list of machine
or domain names, with an optional port part. If no port part is present, then it applies
to all ports on that domain.
LPX-00280: HTTP error ~s
Cause: An HTTP protocol error occurred.
Action: Corrective action depends on the error..
LPX-00281: unsupported encoding "~s"
Cause: The specified encoding is known but not supported by the parser.
Action: Try a different encoding.
LPX-00282: document cannot have both internal/external and shared DTDs
Cause: A parser context which had a shared DTD set was used to parse a document
which also contained a DTD. You cannot use both a shared DTD and and internal/
external one.
Action: If a shared DTD is to be used, then the documents parsed must not contain or
reference a DTD.
LPX-00283: document encoding is ~s-based but default input encoding is not
Cause: The input document was detected to be ASCII (or EBCDIC) based, but no
encoding was specified in the XMLDecl and the default input coding was not ASCII
(or EBCDIC) based, so could not be applied.
Action: Add an explicit encoding specification to the XMLDecl so the default input
encoding is not needed, or pick a default encoding which matches the input
document.
LPX-00284: namespace prefix to NULL URI is not allowed
Cause: An element's namespace prefix declarations was for a NULL URI, e.g. <foo
xmlns:bar=""/> This is illegal presently in XML 1.0, but will be legal in XML 1.1
Action: Remove erroneous prefix definition.
LPX-00285: invalid Unicode surrogate ~X ~X
Cause: A Unicode document contained an invalid surrogate. If the first (high)
surrogate is in the correct range 0xD800 to 0xDBFF, then the second (low) surrogate
must be in the range 0xDC00 to 0xDFFF.
LPX-00286: Exceeded max depth for recursion
Cause: The depth of embedded elements in the document exceeded the limit of 2000.
LPX-00287: Max limit of ~1d exceeded for ~s
Cause: Max limit exceeded
LPX-00000 to LPX-01160 38-13

LPX-00288: CDATA-section-close delimiter is prohibited in element content
Cause: Element content contained CDATA-section-close delimiter.
LPX-00289: invalid redefinition of xmlns URI
Cause: The XML namespace Uniform Resource Identifier 'http://www.w3.org/2000/
xmlns/' must not be assigned a prefix.
LPX-00290: invalid use of xmlns as a prefix
Cause: The prefix 'xmlns' was reserved and could not be used as a prefix.
LPX-00300: no name in attribute set
Cause: The name attribute was not found in the attribute-set element.
Action: Add a name attribute for this element.
LPX-00301: error in XPATH evaluation
Cause: The XPATH evaluation returns an error.
Action: Check specified XPATH expression to determine the error.
LPX-00302: Incorrect stylesheet. The node is not valid.
Cause: The child node is of invalid type or has invalid name for this particular
location in stylesheet, rendering the stylesheet as invalid XSLT.
Action: Fix the stylesheet by using valid nodes only.
LPX-00303: attribute value "~S" not expected for ~S
Cause: Attribute is found but its value is not the expected value.
Action: Set the attribute value to the correct value.
LPX-00304: input parameter to function is null
Cause: An input parameter passed into this function is null when it is not supposed
to.
Action: Make sure the caller function is not passing null for this parameter.
LPX-00305: missing token
Cause: An expected token is not found.
Action: Check the input string to make sure the expected token is present.
LPX-00306: inputed string ended with no corresponding closing '}'
Cause: A closing '}' is expected.
Action: Add the closing '}' to the input string or remove the extra opening '{'.
LPX-00307: namespace prefix ~S used but not declared
Cause: Namespace prefix is used but not declared.
Action: Either declare the namespace or don't use this namespace prefix.
LPX-00308: attribute ~S not found in ~S
Cause: The expected attribute for this node is not found.
Action: Need to add this attribute to the node.

LPX-00309: cannot initialize XPATH
Cause: XPATH context could not be initialized.
Action: Check the initialization function LpxsutInitXpathCtx().
LPX-00310: element ~S not found in ~S
Cause: The expected element is not found.
Action: Check the initialization function LpxsutInitXpathCtx().
LPX-00311: unsupported feature: ~s
Cause: This feature is not supported.
Action: Do not use this feature.
LPX-00312: cannot construct XML PI with content: ~S
Cause: The content of XML PI node might be invalid.
Action: Make necessary changes to make the node valid according to spec.
LPX-00313: cannot construct XML comment with content: ~S
Cause: The content of XML comment node might be invalid.
Action: Make necessary changes to make the node valid according to spec.
LPX-00314: an internal failure occurred
Cause: An internal error occurred in the code.
Action: Contact appropriate developer.
LPX-00315: extension function ~S not supported
Cause: This extension function is not supported.
Action: Either contact appropriate developer for more information or don't use this
extension function.
LPX-00316: invalid value ~S for ~S attribute ~S
Cause: The value for the specified attribute is invalid.
Action: Consult the XSL spec, use only legal values.
LPX-00317: undefined decimal-format "~S"
Cause: The named decimal-format is undefined (the name "#default" means the
default format).
Action: Define the desired decimal-format before trying to use it.
LPX-00318: duplicate xsl:decimal-format "~S"
Cause: The named decimal-format was declared more than once.
Action: Make sure there is only a single declaration.
LPX-00319: The node specified is not valid
Cause: The node specified is not of expected type.
Action: Use only the nodes of legal type.
LPX-00320: No more attributes can be added to a non empty element
Cause: The element to which an attribute was being added is non empty and hence
can not add anymore attributes to it.
LPX-00000 to LPX-01160 38-15
Action: Modify the XSLT stylesheet so that all the attributes are added to an element
before anything else is added to it. If you absolutely can not do that then select your
output method to be DOM based rather then a stream or SAX based output which
you are using presently.
LPX-00321: None of the output method (DOM, SAX, Stream) is selected
Cause: User is trying to process an XML file with out selecting any mechanism for
output.
Action: User must select one of the output mechanisms (SAX/DOM/Stream) before
attempting to process the XML file.
LPX-00322: A doc referred by XSLT stylesheet could not be opened : ~s
Cause: Either an import,include or document() function tried to open a document and
failed.
Action: Make sure that document is present and can be opened.
LPX-00323: illegal apply-imports because of no current template: ~s
Cause: apply-imports was used even when there was no current template possibly
with in for-each.
Action: Make sure that apply-imports are invoked only if there is a current template
and it is not in a xsl:for-each.
LPX-00324: "~S" is not a valid value for the lang attribute of xsl:sort
Cause: An invalid language name was specified for sorting.
Action: Provide a valid value for the lang attribute of xsl:sort.
LPX-00400: an internal error has occurred in XPATH
Cause: An internal error has occurred in XPATH.
Action: Contact the appropriate developer.
LPX-00401: invalid QName in the XSL file
Cause: An invalid QName was passed to the XPATH parser.
Action: See whether there are any invalid QNames in the XSL file.
LPX-00402: invalid axisname in the XSL file
Cause: An invalid axis name was passed to the XPATH parser.
Action: See whether all axis names in the XSL file are correct.
LPX-00403: unmatched quote in the XSL file
Cause: An unmatched quote was found in the XSL file.
Action: Check for unmatched quotes in the XSL file.
LPX-00404: unable to resolve namespace URI
Cause: The namespace URI may not be valid.
Action: Make sure that the name space URIs are valid.
LPX-00405: unable to allocate memory
Cause: May be out of memory.
Action: Try increasing virtual memory.
LPX-00406: object of incorrect type passed to the function

Cause: An object of incorrect type was passed to the XPATH/XSL function.
Action: Do the required conversion before passing in an object of type which is
different from the expected type.
LPX-00407: right square bracket missing in the XSL file
Cause: Right square bracket missing in the XSL file.
Action: Check for unmatched square bracket in the XSL file.
LPX-00408: right parenthesis missing in the XSL file
Cause: Right parenthesis missing in the XSL file.
Action: Check for unmatched parenthesis in the XSL file.
LPX-00409: incorrect token encountered while parsing
Cause: An unexpected token encountered while parsing the expression/ pattern.
Action: Check the syntax of the expressions/patterns.
LPX-00410: unable to resolve the variable reference
Cause: Variable reference may not be valid.
Action: Check whether the variable references are valid.
LPX-00411: unknown function name encountered
Cause: The function is not supported at this time or the name is invalid.
Action: Check the function names. If valid and this error occurs, then avoid using
them at this time.
LPX-00413: loss of precision due to excessively large numerical constant
Cause: The numerical constant in the XPath expression is too big.
Action: n/a
LPX-00601: Invalid token in: '~S'
Cause: Invalid token in XPath expression.
Action: Check the expression.
LPX-00602: Invalid child element '~1S' of element '~2S'.
Cause: Invalid child element in this stylesheet context.
Action: Check the stylesheet.
LPX-00603: Invalid attribute value '~1S': {element '~2S', attribute '~3S'}.
Cause: Invalid attribute value in this stylesheet context.
LPX-00604: Invalid attribute value '~1S', for attribute '~2s'.
Cause: Invalid attribute value for this attribute.
LPX-00605: Invalid attribute '~1S' in element '~2S'.
Cause: Invalid attribute for this element.
LPX-00000 to LPX-01160 38-17
LPX-00606: Missing attribute '~1s' in element '~2S'.

Cause: Missing attribute for this element.
LPX-00607: Invalid reference: '~S'.
Cause: Invalid variable or parameter or template reference.
LPX-00608: Repeated declaration of '~1S' in element '~2S'.
Cause: Only one declaration is allowed at this level.
LPX-00609: Function call with invalid number of arguments in '~1S'.
Cause: Invalid number of arguments.
Action: Check the function signature.
LPX-00651: VM Stack overflow.
Cause: The XML data is too large.
Action: Increase the size of VM stacks in XmlXslVMCreate().
LPX-00652: SAX callback returns with error.
Cause: SAX callback returns an error.
Action: Check the callback function.
LPX-00653: Output attribute '~S' doesn't have a parent element.
Cause: Attribute is generated in a wrong context.
Action: Check the XSLT stylesheet.
LPX-00654: Output namespace attribute '~S' doesn't have a parent element.
Cause: Attribute generated in the wrong context.
LPX-00655: Invalid output comment '~S'.
Cause: Invalid comment node.
LPX-00656: XSLTVM terminate.
Cause: VM terminates.
Action: No action.
LPX-00657: Invalid output PI '~S'.
Cause: Invalid PI node.
LPX-00658: Invalid XSLT object type.
Cause: Invalid object type in XPath evaluation.
LPX-00659: Output write failed.
Cause: Write operation failed.
Action: Check the write method.

LPX-00660: Not a well-formed document or external entity.
Cause: The generated document is not well-formed.
LPX-00661: Failed to load: '~s'.
Cause: Failed to load a document.
LPX-00662: Invalid encoding.
Cause: Invalid encoding specified.
Action: Check the encoding string.
LPX-00663: VM String-Stack overflow.
Cause: The string data is too large.
Action: Increace the size of VM StringStack in XmlXslVMCreate().
LPX-00664: VM Node-Stack overflow.
Cause: Too many XML nodes.
Action: Increace the size of VM NodeStack in XmlXslVMCreate().
LPX-00690: Invalid argument.
Cause: Invalid or missing argument.
Action: Check the function signature.
LPX-00700: invalid SOAP context
Cause: The SOAP context passed to an XmlSoap function was invalid.
Action: Make sure the context passed is an xmlsoapctx and is still valid (has not been
destroyed).
LPX-00701: invalid SOAP role
Cause: An invalid SOAP role was specified.
Action: Only xmlsoaprole enum values should be used (see xml.h).
LPX-00702: invalid SOAP connection binding
Cause: An invalid SOAP connection binding was specified.
Action: Only xmlsoapbind enum values should be used (see xml.h).
LPX-00703: SOAP POST failed
Cause: A SOAP message sent with an HTTP binding failed.
Action: See the returned HTTP error to determine the problem.
LPX-00704: elem has no mustUnderstand
Cause: Header block does not have a mustUnderstand attribute.
Action: This is legal, no action required.
LPX-00705: elem has no role
Cause: Header block does not have a role attribute.
LPX-00000 to LPX-01160 38-19
LPX-00706: message has no fault

Cause: Message body has no Fault child.
LPX-00707: no Fault reason w/given language
Cause: Fault element does not have a reason with given language.
LPX-00708: SOAP failed to make HTTP connection
Cause: SOAP failed to make an HTTP connection to the given URL.
Action: Possible cause is invalid URL or memory exhaustion.
LPX-00709: SOAP reply not valid XML
Cause: The reply to a SOAP call was not a valid XML document.
Action: Check the calling URL for validity; otherwise the problem is likely to be on
the reply side.
LPX-00711: invalid SOAP version
Cause: The version string specified at SOAP creation time was invalid.
Action: Specify a valid version string, either '1.1' or '1.2'.
LPX-00712: failed to set HTTP header
Cause: Connection does not exists, or header is badly formed, or maximum number
of headers is exceeded.
Action: Check that connection exists, header has ':', decrease number of headers.
LPX-00713: body has more than one fault
Cause: Message body has multiple Fault children.
Action: Most likely bug in the server.
LPX-00714: fault is not a single child
Cause: Message body has additional children besides Fault.
LPX-00715: badly formed fault elemen
Cause: Fault element does not have one of mandatory children or has children, which
are not allowed.
LPX-00716: badly formed Text subelement
Cause: Mandatory text child is missing from the requested message subelemt.
LPX-00717: badly formed Value subelement
Cause: Mandatory Value child of the Code child of the Fault badly formed or absent.
LPX-00718: message has no envelope
Cause: The message has no envelope element child.
LPX-00719: prefix too long

Cause: The maximum size of encoded namespace attribute name is 1022.
Action: Use shorter prefix.
LPX-00720: envelope has no header
Cause: The message envelope does not have header.
Action: This is legal, no action required
LPX-00721: envelope has no body
Cause: The message envelope does not have body.
LPX-00722: elem has no relay
Cause: Header block does not have a relay attribute.
LPX-00723: no such element
Cause: The element with requested namespace name and local part does not exists.
LPX-00750: arguments "~1s" to function "~2s" are null
Cause: Input arguments passed into this function are null when it is not supposed to.
Action: Make sure the caller function is not passing null for this parameter.
LPX-00751: arguments "~s" are exclusive
Cause: Input arguments passed into this function are exclusive. Specify only one of
them.
Action: Specify only one of the exclusive arguments.
LPX-00752: invalid ~1s, must be ~2s
Cause: Invalid value was specified for attribute.
Action: Correct the value with one of the suggested values.
LPX-00753: invalid proxy "~s"
Cause: The proxy specification for the given protocol was invalid.
Action: Check and correct the proxy specification. For HTTP, this is the environment
variable "http_proxy".
LPX-00754: invalid no_proxy "~s"
Cause: The no_proxy specification was invalid.
Action: Check and correct the specification. no_proxy is a comma- or space-separated
list of machine or domain names, with an optional port part. If no port part is present,
then it applies to all ports on that domain.
LPX-00755: missing required argument "~s"
Cause: A required argument was missing.
Action: Provide the missing argument to the function.
LPX-00756: Etags and tokens must be either all tagged or all untagged
Cause: The list of condition factors need to be either all tagged with absoluteURI's or
all untagged with absoluteURI's.
LPX-00000 to LPX-01160 38-21
Action: If all condition factors were applied to the resource receiving the request,
make them all untagged. Otherwise, make them all tagged with appropriate
resource's URI's.
LPX-00757: maximum XML document size (~s bytes) exceeded
Cause: The input XML document's size exceeded the limit set by "max_xml_size"
attribute set in XmlDavCreate().
Action: Raise the value set for max_xml_size attribute in XmlDavCreate() if this does
not create problems with security.
LPX-00758: user-provided callback returns null
Cause: Null was returned from user-provided callback function.
Action: Check error(s) encoutered within the callback function.
LPX-00759: failed to initialize TCP/IP
Cause: The TCP/IP package could not be initialized.
Action: Check with your system administrator to see if this is a configuration problem
or a connectivity problem.
LPX-00760: couldn't connect to host ~s port ~u
Cause: A TCP connection couldn't be opened to the named host.
Action: Verify the hostname and connectivity to the host.
LPX-00761: send failed to host ~s
Cause: An error occurred trying to send data over a TCP connection.
Action: Verify network connectivity.
LPX-00762: read failed from host ~s
Cause: An error occurred trying to read data from a TCP connection.
Action: Verify network connectivity.
LPX-00763: exceeded maximum TCP connections
Cause: The maximum allowable number of TCP connections were exceeded. This
happens only if too many pending HTTP responses have not been properly ended or
destroyed.
Action: End a pending response session or destroy response objects that have been
processed.
LPX-00764: TCP connection was broken
Cause: Either the server terminated the TCP connection or the TCP connection is in a
bad state.
Action: Analyze the error. After cleanup, retry the method.
LPX-00765: HTTP error ~s
Cause: An HTTP protocol error occurred.
Action: Corrective action depends on the error.
LPX-00766: unsupported transfer-coding values: ~s
Cause: Only "chunked" and "identity" transfer-coding values are supported.
Action: This is WebDAV implementation's shortfall. There is no workaround for this
problem.
LPX-00767: not a text media type

Cause: A text media type was expected. But other media types were found.
Action: Since this data cannot be read as a text type, use another routine to read it.
LPX-00768: no entity body found
Cause: No entity body was found when it was read.
Action: Check the HTTP status code and headers to see why the entity body was not
found.
LPX-00769: not xml media type
Cause: An XML media type was expected. But other media types were found.
Action: Since this data cannot be read as an XML type, use another routine to read it.
LPX-00770: missing lock token in lock refresh request
Cause: A LOCK request to refresh a lock had no lock token header specified.
Action: Use XmlDavUpdResDesc to set a lock token in the resource
LPX-00771: missing lock token in UNLOCK request
Cause: An UNLOCK request to remove a lock had no lock token header specified.
Action: Use XmlDavUpdResDesc to set a lock token in the resource
LPX-00772: wrong object type
Cause: The wrong object type was given as argument to a WebDAV call.
Action: Review the failing function call, consult the documentation, and make sure
the object types pass as correct.
LPX-00773: protocol violation: ~s
Cause: The entity body sent by the server in Chunked Transfer Encoding violated
protocol.
Action: Either this is an internal implementation error or a server implementation
error. Users should file a bug agaist either the server's or the client's implementation.
LPX-00800: XQuery invalid token
Cause: Invalid XQuery query.
Action: Correct the query.
LPX-00801: XQuery syntax error at
LPX-00802: Too many arguments
LPX-00803: Too few arguments
LPX-00804: Invalid token: '~S'
Cause: Invalid program.
Action: Correct the program.
LPX-00000 to LPX-01160 38-23
LPX-00805: Syntax error at '~S'

Cause: Invalid program.
LPX-00806: Invalid token in the pattern
Cause: The program was invalid.
LPX-00807: Invalid range
Cause: The program was invalid.
LPX-00808: internal error, invalid OPCODE
LPX-00809: Invalid subexpression reference
Cause: The replacement string was invalid.
Action: Correct the replacement string.
LPX-00825: Can't compile the element:
Cause: XSLT Stylesheet can't be compiled to XQuery query.
Action: Correct the the stylesheet.
LPX-00826: Can't compile the attribute:
LPX-00827: Namespace conflict for prefix:
LPX-00903: Invalid flags specified for XmlDiff or XmlPatch
Cause: Invalid value supplied to flags parameter for XmlDiff or XmlPatch functions.
Action: Specify valid flags (see xmldf.h).
LPX-00904: Invalid inputs were supplied to XmlDiff or XmlPatch
Cause: Data could not be read from inputs to XmlDiff or XmlPatch functions.
Action: Specify valid inputs (see xmldf.h).
LPX-00910: The root nodes in input documents to XmlDiff did not match
Cause: The root nodes in input documents do not match.
Action: Make sure the root nodes have same qualified name in both input documents.
XmlDiff can be called only if the root nodes are same in input documents.
LPX-00913: XmlPatch could not process the XML PI oracle-xmldiff
Cause: The diff document either did not specify the XML Processing Instruction
"oracle-xmldiff" or did not specify all data required by XmlPatch. The PI should be
the first child of the top-level xdiff element. This error is also thrown when the
output-model is 'snapshot' and operations-in-docorder is 'false'.
Action: Specify the "oracle-xmldiff" PI correctly. See documentation for XmlPatch C

function in xmldf.h.
LPX-00918: XmlPatch encountered an error in translating XPATH using XmlXVM
Cause: XmlPatch encountered an invalid XPATH in the diff document.
Action: If you handcoded the diff document, make sure all the XPATHs in the diff
document are valid.
LPX-00950: JSON path processing error
Cause: The JavaScript Object Notation (JSON) path engine encountered a fatal
condition.
LPX-01001: [XPST0001] Static context component '~S' has no value
Cause: It is a static error if analysis of an expression relies on some component of the
static context that has not been assigned a value.
Action: n/a
LPX-01002: [XPDY0002] Dynamic context component '~S' has no value
Cause: It is a dynamic error if evaluation of an expression relies on some// part of the
dynamic context that has not been assigned a value.
Action: n/a
LPX-01003: [XPST0003] Syntax error at '~s'
Cause: It is a static error if an expression is not a valid instance of the grammar
defined in A.1 EBNF
Action: n/a
LPX-01004: [XPTY0004] Expression type does not match a required type
Cause: It is a type error if, during the static analysis phase, an expression is found to
have a static type that is not appropriate for the context in which the expression
occurs, or during the dynamic evaluation phase, the dynamic type of a value does not
match a required type as specified by the matching rules in 2.5.4 SequenceType
Matching.
Action: Check the expression type.
LPX-01005: [XPST0005] Invalid empty-sequence() expression
Cause: During the analysis phase, it is a static error if the static type assigned to an
expression other than the expression () or data(()) is empty-sequence().
Action: n/a
LPX-01006: [XPTY0006]
Cause: Not currently used.
Action: n/a
LPX-01007: [XPTY0007]
Action: n/a
LPX-01008: [XPST0008] Invalid reference
Cause: It is a static error if an expression refers to an element name, attribute name,
schema type name, namespace prefix, or variable name that is not defined in the static
LPX-00000 to LPX-01160 38-25
context, except for an ElementName in an ElementTest or an AttributeName in an

AttributeTest.
Action: n/a
LPX-01009: [XQST0009] Schema Import Feature not supported
Cause: An implementation that does not support the Schema Import Feature must
raise a static error if a Prolog contains a schema import.
Action: n/a
LPX-01010: [XPST0010] Axis '~S' not supported
Cause: An implementation must raise a static error if it encounters a reference to an
axis that it does not support.
Action: n/a
LPX-01012: [XQST0012] Invalid XML schema
Cause: It is a static error if the set of definitions contained in all schemas imported by
a Prolog do not satisfy the conditions for schema validity specified in Sections 3 and 5
of [XMLSchema] Part 1 i.e., each definition must be valid, complete, and unique
Action: n/a
LPX-01013: [XQST0013] Invalid pragma content
Cause: It is a static error if an implementation recognizes a pragma but determines
that its content is invalid.
Action: n/a
LPX-01014: [XQST0014]
Action: n/a
LPX-01015: [XQST0015]
Action: n/a
LPX-01016: [XQST0016] Module Feature not supported
Cause: An implementation that does not support the Module Feature raises a static
error if it encounters a module declaration or a module import.
Action: n/a
LPX-01017: [XPST0017] Invalid function call
Cause: It is a static error if the expanded QName and number of arguments in a
function call do not match the name and arity of a function signature in the static
context.
Action: n/a
LPX-01018: [XPTY0018] Path last step contains both nodes and atomic values
Cause: It is a type error if the result of the last step in a path expression contains both
nodes and atomic values.
Action: n/a
LPX-01019: [XPTY0019] Path step contains atomic values

Cause: It is a type error if the result of a step (other than the last step) in a path
expression contains an atomic value.
Action: n/a
LPX-01020: [XPTY0020] The path step context item is not a node
Cause: It is a type error if, in an axis step, the context item is not a node.
Action: n/a
LPX-01021: [XPDY0021]
Action: n/a
LPX-01022: [XQST0022] The value of a namespace must be a URILiteral.
Cause: It is a static error if the value of a namespace declaration attribute is not a
URILiteral.
Action: n/a
LPX-01023: [XPDY0023]
Action: n/a
LPX-01024: [XQTY0024] Attribute node out of context
Cause: It is a type error if the content sequence in an element constructor contains an
attribute node following a node that is not an attribute node.
Action: n/a
LPX-01025: [XQDY0025] Repeated attribute name
Cause: It is a dynamic error if any attribute of a constructed element does not have a
name that is distinct from the names of all other attributes of the constructed element.
Action: n/a
LPX-01026: [XQDY0026] Processing instruction content contains '?>'
Cause: It is a dynamic error if the result of the content expression of a computed
processing instruction constructor contains the string '?>'.
Action: n/a
LPX-01027: [XQDY0027] Invalid PSVI validity property of the root element
Cause: In a validate expression, it is a dynamic error if the root element information
item in the PSVI resulting from validation does not have the expected validity
property: valid if validation mode is strict, or either valid or notKnown if validation
mode is lax.
Action: n/a
LPX-01028: [XQDY0028]
Cause: Not currently used
Action: n/a
LPX-01029: [XQDY0029]
Action: n/a
LPX-00000 to LPX-01160 38-27
LPX-01030: [XQTY0030] Expression should evaluate to exactly one node

Cause: It is a type error if the argument of a validate expression does not evaluate to
exactly one document or element node.
Action: n/a
LPX-01031: [XQST0031] Version not supported by the implementation
Cause: It is a static error if the version number specified in a version declaration is not
supported by the implementation.
Action: n/a
LPX-01032: [XQST0032] Repeated base URI declaration
Cause: A static error is raised if a Prolog contains more than one base URI declaration.
Action: n/a
LPX-01033: [XQST0033] Multiple bindings for the namespace prefix '~s'
Cause: It is a static error if a module contains multiple bindings for the same
namespace prefix.
Action: n/a
LPX-01034: [XQST0034] Repeated function declaration
Cause: It is a static error if multiple functions declared or imported by a module have
the number of arguments and their expanded QNames are equal (as defined by the eq
operator).
Action: n/a
LPX-01035: [XQST0035] Repeated schema components
Cause: It is a static error to import two schema components that both define the same
name in the same symbol space and in the same scope.
Action: n/a
LPX-01036: [XQST0036] Importing module should import schema '~s'
Cause: It is a static error to import a module if the importing module's in-scope
schema types do not include definitions for the schema type names that appear in the
declarations of variables and functions (whether in an argument type or return type)
that are present in the imported module and are referenced in the importing module.
Action: n/a
LPX-01037: [XQST0037]
Action: n/a
LPX-01038: [XQST0038] Invalid collation
Cause: It is a static error if a Prolog contains more than one default collation
declaration, or the value specified by a default collation declaration is not present in
statically known collations.
Action: n/a
LPX-01039: [XQST0039] Repeated parameter name
Cause: It is a static error for a function declaration to have more than one parameter
with the same name.
Action: n/a
LPX-01040: [XQST0040] Repeated attribute name

Cause: It is a static error if the attributes specified by a direct element constructor do
not have distinct expanded QNames.
Action: n/a
LPX-01041: [XQDY0041] Expression can't be cast to the type xs:NCName
Cause: It is a dynamic error if the value of the name expression in a computed
processing instruction constructor cannot be cast to the type xs:NCName.
Action: n/a
LPX-01042: [XQST0042]
Action: n/a
LPX-01043: [XQST0043]
Action: n/a
LPX-01044: [XQDY0044] Invalid attribute namespace
Cause: It is a dynamic error if the node-name property of the node constructed by a
computed attribute constructor is in the namespace http://www.w3.org/2000/
xmlns/ (corresponding to namespace prefix xmlns), or is in no namespace and has
local name xmlns.
Action: n/a
LPX-01045: [XQST0045] Invalid function namespace
Cause: It is a static error if the function name in a function declaration is in one of the
following namespaces: http://www.w3.org/XML/1998/namespace, http://
www.w3.org/2001/XMLSchema, http://www.w3.org/2001/XMLSchema-instance,
http://www.w3.org/2005/xpath-functions.
Action: n/a
LPX-01046: [XQST0046] Invalid URILiteral
Cause: An implementation MAY raise a static error if the value of a URILiteral is of
nonzero length and is not in the lexical space of xs:anyURI.
Action: n/a
LPX-01047: [XQST0047] Repeated import module target namespace
Cause: It is a static error if multiple module imports in the same Prolog specify the
same target namespace.
Action: n/a
LPX-01048: [XQST0048] Namespace should be as the module target namespace
Cause: It is a static error if a function or variable declared in a library module is not in
the target namespace of the library module.
Action: n/a
LPX-01049: [XQST0049] Repeated variable declaration
Cause: It is a static error if two or more variables declared or imported by a module
have equal expanded QNames (as defined by the eq operator.)
Action: n/a
LPX-00000 to LPX-01160 38-29
LPX-01050: [XPDY0050] Invalid dynamic type

Cause: It is a dynamic error if the dynamic type of the operand of a treat expression
does not match the sequence type specified by the treat expression. This error might
also be raised by a path expression beginning with "/" or "//" if the context node is
not in a tree that is rooted at a document node. This is because a leading "/" or "//" in
a path expression is an abbreviation for an initial step that includes the clause treat as
document-node().
Action: n/a
LPX-01051: [XPST0051] AtomicType not defined
Cause: It is a static error if a QName that is used as an AtomicType in a SequenceType
is not defined in the in-scope schema types as an atomic type.
Action: n/a
LPX-01052: [XQDY0052]
Action: n/a
LPX-01053: [XQDY0053]
Action: n/a
LPX-01054: [XQST0054] The variable depends on itself
Cause: It is a static error if a variable depends on itself.
Action: n/a
LPX-01055: [XQST0055] Repeated copy-namespaces declaration
Cause: It is a static error if a Prolog contains more than one copy-namespaces
declaration.
Action: n/a
LPX-01056: [XQST0056]
Action: n/a
LPX-01057: [XQST0057] Missing schema import target namespace
Cause: It is a static error if a schema import binds a namespace prefix but does not
specify a target namespace other than a zero-length string.
Action: n/a
LPX-01058: [XQST0058] Repeated schema import target namespace
Cause: It is a static error if multiple schema imports specify the same target
namespace.
Action: n/a
LPX-01059: [XQST0059] Can't find schema or module with namespace '~s'
Cause: It is a static error if an implementation is unable to process a schema or
module import by finding a schema or module with the specified target namespace.
Action: n/a
LPX-01060: [XQST0060] Function name should have a namespace

Cause: It is a static error if the name of a function in a function declaration is not in a
namespace (expanded QName has a null namespace URI).
Action: n/a
LPX-01061: [XQDY0061] Invalid document node
Cause: It is a dynamic error if the operand of a validate expression is a document
node whose children do not consist of exactly one element node and zero or more
comment and processing instruction nodes, in any order.
Action: n/a
LPX-01062: [XQDY0062]
Action: n/a
LPX-01063: [XQST0063]
Action: n/a
LPX-01064: [XQDY0064] Processing instruction name contains 'XML'
processing instruction constructor is equal to "XML" (in any combination of upper
and lower case).
Action: n/a
LPX-01065: [XQST0065] Repeated ordering mode declaration
Cause: A static error is raised if a Prolog contains more than one ordering mode
declaration.
Action: n/a
LPX-01066: [XQST0066] Repeated default declaration
Cause: A static error is raised if a Prolog contains more than one default element/type
namespace declaration, or more than one default function namespace declaration.
Action: n/a
LPX-01067: [XQST0067] Repeated construction declaration
Cause: A static error is raised if a Prolog contains more than one construction
declaration.
Action: n/a
LPX-01068: [XQST0068] Repeated boundary-space declaration
Cause: A static error is raised if a Prolog contains more than one boundary-space
declaration.
Action: n/a
LPX-01069: [XQST0069] Repeated empty order declaration
Cause: A static error is raised if a Prolog contains more than one empty order
declaration.
Action: n/a
LPX-00000 to LPX-01160 38-31
LPX-01070: [XQST0070] Invalid (prefix, URI) combination

Cause: A static error is raised if a namespace URI is bound to the predefined prefix
xmlns, or if a namespace URI other than http://www.w3.org/XML/1998/namespace
is bound to the prefix xml, or if the prefix xml is bound to a namespace URI other
than http://www.w3.org/XML/1998/namespace.
Action: n/a
LPX-01071: [XQST0071] Repeated namespace attribute
Cause: A static error is raised if the namespace declaration attributes of a direct
element constructor do not have distinct names.
Action: n/a
LPX-01072: [XQDY0072] Element content contains invalid hyphens combination
Cause: It is a dynamic error if the result of the content expression of a computed
comment constructor contains two adjacent hyphens or ends with a hyphen.
Action: n/a
LPX-01073: [XQST0073] Cyclic import sequence
Cause: It is a static error if the graph of module imports contains a cycle (that is, if
there exists a sequence of modules M1 ... Mn such that each Mi imports Mi+1 and Mn
imports M1), unless all the modules in the cycle share a common namespace.
Action: n/a
LPX-01074: [XQDY0074] Invalid element or attribute QName
element or attribute constructor cannot be converted to an expanded QName (for
example, because it contains a namespace prefix not found in statically known
namespaces.)
Action: n/a
LPX-01075: [XQST0075] Validate expression not supported
Cause: An implementation that does not support the Validation Feature must raise a
static error if it encounters a validate expression.
Action: n/a
LPX-01076: [XQST0076] Invalid collation
Cause: It is a static error if a collation subclause in an order by clause of a FLWOR
expression does not identify a collation that is present in statically known collations.
Action: n/a
LPX-01077: [XQST0077]
Action: n/a
LPX-01078: [XQST0078]
Action: n/a
LPX-01079: [XQST0079] Invalid extension expression
Cause: It is a static error if an extension expression contains neither a pragma that is
recognized by the implementation nor an expression enclosed in curly braces.
Action: n/a
LPX-01080: [XPST0080] Invalid target type
Cause: It is a static error if the target type of a cast or castable expression is
xs:NOTATION or xs:anyAtomicType.
Action: n/a
LPX-01081: [XPST0081] Invalid prefix
Cause: It is a static error if a QName used in a query contains a namespace prefix that
cannot be expanded into a namespace URI by using the statically known namespaces.
Action: n/a
LPX-01082: [XQST0082]
Action: n/a
LPX-01083: [XQST0083]
Action: n/a
LPX-01084: [XQDY0084] Missing top-level element declaration
Cause: It is a dynamic error if the element validated by a validate statement does not
have a top-level element declaration in the in-scope element declarations, if validation
mode is strict.
Action: n/a
LPX-01085: [XQST0085] The namespace URI shouldn't be a zero-length string
Cause: It is a static error if the namespace URI in a namespace declaration attribute is
a zero-length string, and the implementation does not support [XML Names 1.1].
Action: n/a
LPX-01086: [XQTY0086] No-preserve mode conflict
Cause: It is a type error if the typed value of a copied element or attribute node is
namespace-sensitive when construction mode is preserve and copy-namespaces
mode is no-preserve.
Action: n/a
LPX-01087: [XQST0087] Invalid encoding
Cause: It is a static error if the encoding specified in a Version Declaration does not
conform to the definition of EncName specified in [XML 1.0].
Action: n/a
LPX-01088: [XQST0088] Target namespace string shouldn't be of zero length
Cause: It is a static error if the literal that specifies the target namespace in a module
import or a module declaration is of zero length.
Action: n/a
LPX-01089: [XQST0089] Repeated variable name
Cause: It is a static error if a variable bound in a for clause of a FLWOR expression,
and its associated positional variable, do not have distinct names (expanded
QNames).
Action: n/a
LPX-00000 to LPX-01160 38-33
LPX-01090: [XQST0090] Invalid character reference

Cause: It is a static error if a character reference does not identify a valid character in
the version of XML that is in use.
Action: n/a
LPX-01091: [XQDY0091] Invalid xml:id
Cause: An implementation MAY raise a dynamic error if an xml:id error, as defined
in [XML ID], is encountered during construction of an attribute named xml:id.
Action: n/a
LPX-01092: [XQDY0092] Invalid xml:space value
Cause: An implementation MAY raise a dynamic error if a constructed attribute
named xml:space has a value other than preserve or default.
Action: n/a
LPX-01093: [XQST0093] Module depends on itself
Cause: It is a static error to import a module M1 if there exists a sequence of modules
M1 ... Mi ... M1 such that each module directly depends on the next module in the
sequence (informally, if M1 depends on itself through some chain of module
dependencies.)
Action: n/a
LPX-01094: [FORG0003] fn:zero-or-one called with a sequence containing more
than one item
Cause: It is a dynamic error if fn:zero-or-one is called with a sequence containing
more than one item
Action: n/a
LPX-01095: [FORG0004] fn:one-or-more called with a sequence containing no items
Cause: It is a dynamic error if fn:one-or-more is called with a sequence containing no
items
Action: n/a
LPX-01096: [FORG0005] fn:exactly-one called with a sequence containing zero or
more than one item
Cause: It is a dynamic error if fn:exactly-one is called with a sequence containing zero
or more than one item
Action: n/a
LPX-01097: [FORG0006] Invalid argument type
Cause: It is a dynamic error if an XQuery F&O is called with wrong argument type.
Action: n/a
LPX-01098: [FOCA0002] Invalid lexical value
Cause: It is a dynamic error if an XQuery F&O is called with wrong argument value.
Action: n/a
LPX-01099: [FOCA0001] Input value too large for decimal
Cause: It is a dynamic error if the Input value too large for decimal
Action: n/a
LPX-01100: [FOCA0003] Input value too large for integer

Cause: It is a dynamic error if the Input value too large for integer
Action: n/a
LPX-01101: External Error '~s' occurs
Cause: An error occurred during the processing of the XQuery expression.
Action: Check the detailed error message for the possible causes.
LPX-01102: [FORG0008] both arguments to fn:dateTime have a specified timezone
Cause: It is an error to pass arguments to fn:dateTime having a specified timezone
Action: n/a
LPX-01105: [FOAR0001] Division by zero
Cause: It is an error to divide by zero
Action: n/a
LPX-01106: [FOAR0002] Numeric operation overflow/underflow
Cause: Numeric operations causes overflow/underflow
Action: n/a
LPX-01107: [FORG0002] invalid argument to fn:resolve-uri()
Cause: Wrong argument to fn:resolve-uri() function
Action: n/a
LPX-01108: [FORG0009] error in resolving a relative URI against a base URI in
fn:resolve-uri()
Cause: Error resolving relative URI in fn:resolve-uri() function
Action: n/a
LPX-01109: [FOCA0005] NaN supplied as float/double value
Cause: NaN supplied as float/double value
Action: n/a
LPX-01110: [FOCA0006] String to be cast to decimal has too many digits of
precision
Cause: String to be cast to decimal has too many digits of precision
Action: n/a
LPX-01111: [FOCH0002] Unsupported collation
Cause: Unsupported collation
Action: n/a
LPX-01112: [FOCH0003] Unsupported normalization form
Cause: Unsupported normalization form
Action: n/a
LPX-01113: [FOCH0004] Collation does not support collation units
Cause: Collation does not support collation units
Action: n/a
LPX-00000 to LPX-01160 38-35
LPX-01114: [FODC0001] No context document

Cause: No context document
Action: n/a
LPX-01115: [FODC0002] Error retrieving resource
Cause: Error retrieving resource
Action: n/a
LPX-01116: [FODC0003]
Cause: Function stability not defined
Action: Function stability not defined
LPX-01117: [FODC0004] Invalid argument to fn:collection
Cause: Invalid argument to fn:collection
Action: n/a
LPX-01118: [FODC0005] Invalid argument to fn:doc or fn:doc-available
Cause: Invalid argument to fn:doc or fn:doc-available
Action: n/a
LPX-01119: [FODT0001] Overflow/underflow in date/time operation
Cause: Overflow/underflow in date/time operation
Action: n/a
LPX-01120: [FODT0002] Overflow/underflow in duration operation
Cause: Overflow/underflow in duration operation
Action: n/a
LPX-01121: [FODT0003] Invalid timezone value
Cause: Invalid timezone value
Action: n/a
LPX-01122: [FONS0005] Base-uri not defined in the static context
Cause: Base-uri not defined in the static context
Action: n/a
LPX-01123: [FORG0001] Invalid value for cast/constructor
Cause: Invalid value for cast/constructor
Action: n/a
LPX-01124: [FORX0001] Invalid regular expression flags
Cause: Invalid regular expression flags
Action: n/a
LPX-01125: [FORX0002] Invalid regular expression
Cause: Invalid regular expression
Action: n/a
LPX-01126: [FORX0003] Regular expression matches zero-length string
Cause: Regular expression matches zero-length string
Action: n/a
LPX-01127: [FORX0004] Invalid replacement string
Cause: Invalid replacement string
Action: n/a
LPX-01128: [FOTY0012] Argument node does not have a typed value
Cause: Argument node does not have a typed value
Action: n/a
LPX-01129: [XUST0001] Updating expression in a wrong position
Cause: It is a static error if an updating expression is used in any position other than
one of the following: 1. The topmost expression in the body of a query. 2. The modify
clause of a transform expression. 3. The return clause of a FLWOR expression. 4. The
return clauses of a typeswitch expression in which every return clause contains an
updating expression, an empty expression ( ), or a call to the fn:error function. 5. The
then and else clauses of a conditional statement in which both the then and else
clauses contain either an updating expression, an empty expression ( ), or a call to the
fn:error function. 6. An operand of a comma expression in which each operand is
either an updating expression, an empty expression ( ), or a call to the fn:error
function. 7. The content of a parenthesized expression. 8. The body of a function
declaration in which the keyword updating is specified.
Action: n/a
LPX-01130: [XUST0002] Non-updating expression in a wrong position
Cause: It is a static error if an non-updating expression other than an empty
expression ( ) or a call to the fn:error function is used in one of the following positions:
1. The modify clause of a transform expression. 2. The top-level expression in the
body of a function declaration in which the keyword updating is specified.
Action: n/a
LPX-01131: [XUST0003] Repeated revalidation declaration
Cause: It is a static error if a Prolog contains more than one revalidation declaration.
Action: n/a
LPX-01132: [XUTY0004] Invalid attribute node in the insertion sequence
Cause: It is a type error if the insertion sequence of an insert expression contains an
attribute node following a node that is not an attribute node.
Action: n/a
LPX-01133: [XUTY0005] Invalid target expression for 'insert'
Cause: In an insert expression where into, as first into, or as last into is specified, it is a
type error if the target expression returns a non-empty result that does not consist of a
single element or document node.
Action: n/a
LPX-01134: [XUTY0006] Invalid target expression for 'insert'
Cause: In an insert expression where before or after is specified, it is a type error if the
target expression returns a non-empty result that does not consist of a single element,
text, comment, or processing instruction node.
Action: n/a
LPX-00000 to LPX-01160 38-37
LPX-01135: [XUTY0007] Invalid target expression for 'delete'

Cause: It is a type error if the target expression of a delete expression does not return
a sequence of zero or more nodes.
Action: n/a
LPX-01136: [XUTY0008] Invalid target expression for 'replace'
Cause: In a replace expression, it is a type error if the target expression returns a nonempty result that does not consist of a single element, attribute, text, comment, or
processing instruction node.
Action: n/a
LPX-01137: [XUDY0009] Invalid target expression for 'replace'
Cause: In a replace expression where value of is not specified, it is a dynamic error if
the node returned by the target expression does not have a parent.
Action: n/a
LPX-01138: [XUTY0010] Invalid replacement sequence for 'replace'
Cause: In a replace expression where value of is not specified and the target is an
element, text, comment, or processing instruction node, it is a type error if the
replacement sequence does not consist of zero or more element, text, comment, or
processing instruction nodes.
Action: n/a
LPX-01139: [XUTY0011] Invalid replacement sequence for 'replace'
Cause: In a replace expression where value of is not specified and the target is an
attribute node, it is a type error if the replacement sequence does not consist of zero or
more attribute nodes.
Action: n/a
LPX-01140: [XUTY0012] Invalid target expression for 'rename'
Cause: In a rename expression, it is a type error if the target expression returns a nonempty result that does not consist of a single element, attribute, or processing
instruction node.
Action: n/a
LPX-01141: [XUTY0013] Invalid copy expression for transform
Cause: In a transform expression, it is a type error if a source expression in the copy
clause does not return a single node.
Action: n/a
LPX-01142: [XUDY0014] Modified node was not created by the copy clause
Cause: In a transform expression, it is a dynamic error if the modify clause modifies
any node that was not created by the copy clause.
Action: n/a
LPX-01143: [XUDY0015] Duplicate 'rename' for the same target node
Cause: It is a dynamic error if any node is the target of more than one rename
expression within the same query.
Action: n/a
LPX-01144: [XUDY0016] Duplicate 'replace' for the same target node

Cause: It is a dynamic error if any node is the target of more than one replace
expression (without value of being specified) within the same query.
Action: n/a
LPX-01145: [XUDY0017] Duplicate 'replace' for the same target node
Cause: It is a dynamic error if any node is the target of more than one replace value of
expression within the same query.
Action: n/a
LPX-01146: [XUDY0018] External not updating function returns an updated value
Cause: It is a dynamic error if a function that was declared to be external but not
updating returns a non-empty pending update list.
Action: n/a
LPX-01147: [XUDY0019] External updating function returns an invalid value
Cause: It is a dynamic error if a function that was declared to be both external and
updating returns a non-empty data model instance.
Action: n/a
LPX-01148: [XUDY0020] Deleted node has no parent
Cause: An implementation may (but is not required to) raise a dynamic error if a node
is deleted that had no parent before execution of the query began.
Action: n/a
LPX-01149: [XUDY0021] The result XDM instance violates XDM constraints
Cause: It is a dynamic error if the XDM instance that would result from applying all
the updates in a query violates any constraint specified in [XQuery/XPath Data
Model (XDM)]. In this case, none of the updates in the query are made effective.
Action: n/a
LPX-01150: [XUTY0022] Invalid attribute insertion into a document node
Cause: It is a type error if an insert expression specifies the insertion of an attribute
node into a document node.
Action: n/a
LPX-01151: [XUDY0023] Updating expression introduces a namespace conflict
Cause: It is a dynamic error if an insert, replace, or rename expression affects an
element node by introducing a new namespace binding that conflicts with one of its
existing namespace bindings.
Action: n/a
LPX-01152: [XUDY0024] Updating expression introduces a namespace conflict
Cause: It is a dynamic error if the effect of a set of updating expressions is to
introduce conflicting namespace bindings into an element node.
Action: n/a
LPX-01153: [XUDY0025] Invalid QName for processing instruction rename
Cause: It is a dynamic error if the target of a rename expression is a processing
instruction node, and the new name expression returns a QName with a non-empty
namespace prefix.
LPX-00000 to LPX-01160 38-39
Action: n/a
LPX-01154: [XUST0026] Revalidation mode '~s' is not supported
Cause: It is a static error if a revalidation declaration in a Prolog specifies a
revalidation mode that is not supported by the current implementation.
Action: n/a
LPX-01155: [XUDY0027] Invalid target expression
Cause: It is a dynamic error if the target expression of an insert, replace, or rename
expression evaluates to an empty sequence.
Action: n/a
LPX-01156: [XUST0028] Updating function should not have a return type
Cause: It is a static error if a function declaration specifies both updating and a return
type.
Action: n/a
LPX-01157: [XUDY0029] Insert expression target node doesn't have a parent
Cause: In an insert expression where before or after is specified, it is a dynamic error
if node returned by the target expression does not have a parent.
Action: n/a
LPX-01158: [XUDY0030] Invalid insertion of an attribute node
Cause: It is a dynamic error if an insert expression specifies the insertion of an
attribute node before or after a child of a document node.
Action: n/a
LPX-01159: [FOUP0001] Invalid 'fn:put' first operand
Cause: It is a dynamic error if the first operand of fn:put is not a node of a supported
kind.
Action: n/a
LPX-01160: [FOUP0002] Invalid 'fn:put' second operand
Cause: It is a dynamic error if the second operand of fn:put is not a valid lexical
representation of the xs:anyURI type.
Action: n/a
39
LRM-00100 to LRM-00123
LRM-00100: internal error [number]
LRM-00101: unknown parameter name 'string'
Cause: The parameter name was misspelled.
Action: Spell the parameter name correctly.
LRM-00102: 'string' is not in the legal range for 'string'
Cause: The value of the parameter is not within the legal range.
Action: Refer to the manual for the allowable values for this parameter.
LRM-00103: 'string' contains an illegal integer radix for 'string'
Cause: An illegal integer radix specification was found.
Action: Only 'd', 'h', 'D', and 'H' may be used as radix specifications.
LRM-00104: 'string' is not a legal integer for 'string'
Cause: The value is not a valid integer.
Action: Specify only valid integers for this parameter.
LRM-00105: 'string' is not a legal Boolean for 'string'
Cause: The value is not a valid Boolean.
Action: Refer to the manual for allowable Boolean values.
LRM-00106: out of memory
Action: Take action to make more memory available to the program.
LRM-00107: parameter name abbreviation 'string' is not unique
Cause: The given abbreviation was not unique.
Action: Use a longer abbreviation to make the parameter name unique.
LRM-00108: invalid positional parameter value 'string'
Cause: An invalid positional parameter value has been entered.
Action: Remove the invalid positional parameter.
LRM-00109: could not open parameter file 'string'
Cause: The parameter file does not exist.
Action: Create an appropriate parameter file.
LRM-00100 to LRM-00123 39-1
LRM-00110: syntax error at 'string'

Action: Change the input so that the correct syntax is used.
LRM-00111: no closing quote for value 'string'
Cause: A quoted string was started but not finished.
LRM-00112: multiple values not allowed for parameter 'string'
Cause: An attempt was made to specify multiple values for a parameter which can
take only one value.
Action: Do not specify more than one value for this parameter.
LRM-00113: error when processing file 'string'
Cause: A problem occurred when processing this file.
Action: Examine the additional error messages and correct the problem.
LRM-00114: error when processing from command line
Cause: A problem occurred when processing the command line.
LRM-00115: error when processing an environment variable
Cause: A problem occurred when processing an environment variable.
LRM-00116: syntax error at 'string' following 'string'
LRM-00117: syntax error at 'string' at the start of input
LRM-00118: syntax error at 'string' at the end of input
LRM-00119: unable to obtain a valid value for 'string'
Cause: No valid value was obtained for this parameter.
Action: Rerun the application and enter a valid value.
LRM-00120: 'string' is not a legal Oracle number for 'string'
Cause: The value is not a valid Oracle number.
Action: Refer to the manual for allowable Oracle number values.
LRM-00121: 'string' is not an allowable value for 'string'
Cause: The value is not a legal value for this parameter.
Action: Refer to the manual for allowable values.
39-2 Error Messages
LRM-00122: value 'string' for 'string' must be between 'number' and 'number'
Action: Specify a value that is within the legal range.
LRM-00123: invalid character number found in the input file
Cause: A character that is invalid was found in the input file.
Action: Specify an input file that contains only valid characters.
LRM-00100 to LRM-00123 39-3
39-4 Error Messages
40
LSX-00001 to LSX-00345
LSX-00001: NULL pointer
Cause: A NULL pointer was detected as an internal error condition.
Action: This is a programming error by the caller of the Schema processor. Contact
someone who can fix the problem.
LSX-00002: root element is not schema
Cause: The top-level element of an XML Schema must be schema.
Action: Correct the Schema; consult the Schema specification.
LSX-00003: invalid attribute "~1S" for element "~2S"
Cause: The named Schema element had an invalid attribute.
Action: Correct the Schema; consult the Schema specification.
LSX-00004: unexpected XML node type
Cause: Schema contains an XML node other than element, text (or CDATA),
Action: Other node types are not permitted; remove them.
LSX-00008: feature "~s" is not implemented
Cause: An attempt was made to use a feature that is not yet implemented.
Action: Make an enhancement request for the feature.
LSX-00009: data missing for type "~S"
Cause: Data is missing for an element or attribute of a simple type.
Action: Add data in the element or attribute.
LSX-00010: extra element(s) at end of "~S"
Cause: Extra elements exist at the end of schema component declarations.
Action: Remove the extra elements.
LSX-00011: internal error: ~s\n
Cause: Implementation error.
Action: File a bug.
LSX-00013: element "~S" not from Schema of Schemas
Cause: Bogus element exists in the schema file. Its name is not from Schema of
Schemas.
Action: Remove the bogus element.
LSX-00014: empty instance document
Cause: Instance document to be Schema validated was empty (no top-level element).
LSX-00001 to LSX-00345 40-1
Action: Provide a complete XML instance document.

LSX-00015: failed to parse document
Cause: Failed to parse the schema document using the given URI.
Action: Provide the correct URI and make sure that the schema document is valid.
LSX-00016: schema and instance document have incompatible character sets
Cause: Parsed schema components were in a simple-type character set while the
parsed instance document data was not. A simple-type character set is single-byte,
not shift sensitive, and has no linguistic specials in use.
Action: Reinitialize the schema global context with appropriate parser context
settings, i.e. pass a parser context with its output encoding set to be a multibyte or
Unicode character set.
LSX-00018: invalid schema context
Cause: An invalid schema context was provided to the processor. Multiple schema
documents were loaded and assembled into the schema context. At least one of them
is not fully valid with respect to a schema corresponding to the Schema for Schemas.
Action: Check the errors reported when schema documents were loaded, mapped, or
validated. Correct errors found in the identified schema documents and reload them
into a new schema context. Then provide the new schema context to the processor.
LSX-00020: unknown type "~S"
Cause: A specified type was unknown (not defined in any loaded Schemas).
Action: Make sure the type was defined and that the type usage referenced the correct
Schema.
LSX-00021: undefined element "~S"
Cause: Element is undefined in the specified namespace.
Action: If the element name is misspelled, correct the spelling.
LSX-00022: unknown namespace prefix "~S"
Cause: Prefix in a QName is undefined in the current scope.
Action: Correct the prefix name if it's misspelled.
LSX-00023: unknown namespace URI "~S"
Cause: Namespace URI is unknown to the schema processor.
Action: Correct the namespace URI if it's misspelled.
LSX-00024: unknown attribute group "~S"
Cause: The name of attribute group is unknown to the schema processor in the
current scope.
Action: Correct the name of attribute group if it's misspelled.
LSX-00025: unknown group "~S"
Cause: The name of group is unknown to the schema processor in the current scope.
Action: Correct the name of group if it's misspelled.
LSX-00026: unknown attribute "~S"
Cause: The name of attribute is unknown to the schema processor in the current
scope.
Action: Correct the name of attribute if it's misspelled.
40-2 Error Messages
LSX-00027: property "~s" unknown

Cause: The named validation property was unknown.
Action: Refer to the documentation for the complete list of validation properties.
LSX-00102: duplicate element "~S"
Cause: Element declaration is not unique within its scope.
Action: Rename the element.
LSX-00103: duplicate group "~S"
Cause: Group declaration is not unique within its scope.
Action: Rename the group.
LSX-00104: duplicate type "~S"
Cause: Type definition is not unique within its scope.
Action: Rename the type.
LSX-00105: duplicate attribute group "~S"
Cause: Attribute group declaration is not unique within its scope.
Action: Rename the attribute group.
LSX-00106: duplicate attribute "~S"
Cause: Attribute declaration is not unique within its scope.
Action: Rename the attribute.
LSX-00110: facet "~S" should have single value attribute
Cause: A facet declaration did not have a value attribute.
Action: Each facet declaration must contain one and only one value attribute.
LSX-00111: type "~S" contains invalid facets
Cause: A specified facet was invalid for a type. Each datatype has a different set of
facets which may apply.
Action: Use only applicable facets for the type.
LSX-00112: facet "~S" duplicated
Cause: A facet (other than "enumeration") was specified more than once.
Action: Only the enumeration facet may be used more than once for a type.
LSX-00113: facet "~1S" has invalid value "~2S"
Cause: Facet value contained illegal characters or its value was out of range.
Action: Remove illegal characters.
LSX-00114: facet "~S" not in schema schema
Cause: Facets are not defined in the XMLSchema namespace.
Action: Remove illegal facet declarations.
LSX-00116: mutually exclusive facets are not allowed
Cause: Mutual exclusiveness violations were found for facets. For example, both
"length" and either "minLength" or "maxLength" are not allowed to be facets.
Action: Remove the facets that are at fault.
LSX-00001 to LSX-00345 40-3
LSX-00117: "minLength" should not be greater than "maxLength"

Cause: The value of "minLength" must be less than or equal to the value of
"maxLength".
Action: Correct either "minLength" or "maxLength".
LSX-00118: fixed facet value cannot be changed
Cause: The value of a fixed facet in the base type definition should remain the same.
Action: Remove the fixed facet specification in the parent's type for the erroneous
facet component.
LSX-00119: value is not valid restriction of parent's minLength
Cause: There was an error in that minLength was among the members of {facets} of
{base type definition} and {value} was less than the {value} of the parent minLength.
Action: Increase the {value} of minLength.
LSX-00120: value is not valid restriction of parent's maxLength
Cause: There was an error in that maxLength was among the members of {facets} of
{base type definition} and {value} was greater than the {value} of the parent
maxLength.
Action: Increase the {value} of maxLength.
LSX-00121: value is not valid restriction of parent's length
Cause: There was an error in that length was among the members of {facets} of {base
type definition} and {value} was not equal to the {value} of the parent length.
Action: Make {value} the same as parent's.
LSX-00122: value is not valid restriction of parent's whiteSpace
Cause: There was an error in that whiteSpace was among the members of {facets} of
{base type definition} and at least one of the following conditions was true: 1 {value}
is replace or preserve and {value} of the parent whiteSpace is collapse 2 {value} is
preserve and the {value} of the parent whiteSpace is replace
Action: Change the {value} of whiteSpace.
LSX-00123: base type is required
Cause: Missing base type declaration in the type definition.
Action: Define a base type.
LSX-00124: "list" element is improperly defined
Cause: A "list" element either must have its "itemType" attribute set or have one of its
children be a "simpleType" element, but both conditions cannot exist.
Action: Remove the erroneous condition.
LSX-00125: "restriction" element is improperly defined
Cause: A "restriction" element either must have its "base" attribute set or have one of
its children be a "simpleType" element, but both conditions cannot exist.
LSX-00126: facet "~1S" has invalid value "~u"
Cause: Facet value contained illegal characters or its value was out of range.
40-4 Error Messages
LSX-00127: totalDigits must be greater than or equal to fractionDigits

Cause: The value of the facet totalDigits is less than the value of the facet
fractionDigits.
Action: Ensure that totalDigits is greater than or equal to fractionDigits.
LSX-00130: attribute "processContents" has invalid value "~S"
Cause: Attribute "processContents" in the "any" element or "anyAttribute" declaration
has an invalid value.
Action: Specify one of the following values: lax, skip, or strict.
LSX-00132: attribute "~1S" has invalid occurrences value "~2S"
Cause: A minOccurs or maxOccurs attribute had an invalid value (not a integer or
less than zero).
Action: Use a legal "occurs" value.
LSX-00133: attribute "use" has invalid value "~S"
Cause: A "use" attribute had an invalid value. Choices for "use" are "default", "fixed",
"optional", "prohibited", or "required".
Action: Change the attribute to one of the above values.
LSX-00134: attribute "~1S" has invalid qualification "~2S"
Cause: An attribute that specifies qualification (form, attributeFormDefault,
elementFormDefault) was invalid; it must be one of "qualified" or "unqualified".
LSX-00135: invalid min/max Occurs for all element, must be 0/1
Cause: "minOccurs" has a value other than 0/1 or "maxOccurs" has a value other than
1.
Action: Specify 0/1 for "minOccurs" or "maxOccurs".
LSX-00136: "maxOccurs" is less than "minOccurs"
Cause: The value of the "maxOccurs" specification is less than the value of the
"minOccurs" specification.
Action: Correct "minOccurs" or "maxOccurs".
LSX-00141: ID type may only be used in attributes
Cause: For backward compatibility with DTD, ID type may only be used in attributes.
Action: Remove the ID type.
LSX-00142: invalid sub-element "~1S" for element "~2S"
Cause: There was an invalid sub-element in the content of either the attribute or the
element declaration. This was because the sub-element was either at the wrong
position or out of context.
Action: Remove the sub-element or move it to the correct position.
LSX-00143: element "~S" must have type or ref
Cause: A Schema element was declared but was neither type or reference.
Action: One of type or reference must be specified.
LSX-00001 to LSX-00345 40-5
LSX-00144: attribute "~1S" invalid derivation-restriction value "~2S"

Cause: An attribute which specifies a derivation-restriction setting (block, content,
final) had an invalid value. Choices are "#all", "extension", or "restriction".
LSX-00145: attribute "~1S" invalid derived value "~2S"
Cause: A derivedBy attribute had an invalid value. Choices are "extension" or
"restriction".
LSX-00146: element or attribute is improperly defined
Cause: An element or attribute definition must have either its "type" attribute set or
must have one of its children be a "simpleType" or "complexType" element but both
conditions cannot exist.
LSX-00147: "~1S" cannot contain "~2S"
Cause: An invalid schema component exists in the current declaration.
Action: Remove the schema component.
LSX-00148: annotation must come first in "~S"
Cause: "annotation" element must be the first in the content.
Action: Make "annotation" the first element.
LSX-00149: duplicated ID specified in "~S"
Cause: An attempt was made to specify two distinct members of {attribute uses}with
{attribute declaration}s, both of whose {type definition}s are from ID or are derived
from ID.
Action: Declare only one member of the {attribute uses} whose {type definition} is
from ID or will be derived from ID.
LSX-00150: attributeGroup reference shouldn't have children
Cause: A reference-to-attributeGroup element has children. It is suppose to be empty
except for annotations.
Action: Remove the children.
LSX-00151: invalid combination of attributes "ref" and "name"
Cause: If the item's parent is not schema, then either the "ref" or the "name" attribute
must be present, but not both. Top-level elements or attributes must have a name.
Action: Specify either the "ref" or "name" attribute.
LSX-00152: only "minOccurs", "maxOccurs", or "id" is allowed
Cause: If the item's parent is not schema and "ref" is present, then "complexType",
"simpleType", "key", "keyref", "unique", "nillable", "default", "fixed", "form", "block",
and "type" must be absent.
Action: Remove the prohibited attribute.
LSX-00153: invalid combination of default and fixed attributes
Cause: It is an error for a declaration to contain both fixed and default attributes.
Action: Remove either the default or the fixed attributes.
40-6 Error Messages
LSX-00154: attribute "use" must have its value set to "optional"

Cause: If "default" and "use" are both present, use must have its value set to
"optional".
Action: Remove the default attribute or change the value of the "use" attribute.
LSX-00155: invalid use of attribute "ref"
Cause: If the item's parent is not schema and the attribute "ref" is present, then the
element "simpleType" and the attributes "form" and "type" must be absent.
Action: Remove the prohibited items.
LSX-00156: type is final and no derivations are allowed
Cause: Derivation from a type that is declared to be final occurred.
Action: Remove the final declaration from the base type.
LSX-00157: "~S" is abstract and cannot be used in an instance document
Cause: The element declaration or the type definition was abstract.
Action: When an element is declared to be abstract, a member of that element's
substitution group must appear in the instance document. When an element's
corresponding type definition is declared as abstract, all instances of that element
must use xsi:type to indicate a derived type that is not abstract.
LSX-00158: base type of "~S" must be simple type or primitive datatype
Cause: The derivation constraint was violated.
Action: Use complexType instead of simpleType.
LSX-00159: list content of multiple simple types is not allowed
Cause: Two or more simple types were specified within the list content .
Action: Specify only one simple type.
LSX-00160: invalid substitution group affiliation between "~S" and "~S"
Cause: There was an error in that {substitution group exclusions} prevented
substitution group affiliation by type restriction or type extension.
Action: Remove the offending deriving method from the {substitution group
exclusions} list.
LSX-00161: disallowed type substitution between "~S" and "~S"
Cause: There was a substituted type whose deriving method falls in the union of the
{disallowed substitutions} and the {type definition}'s {prohibited substitutions}.
Action: Remove the offending deriving method from the element's {disallowed
substitutions} list or the {type definition}'s {prohibited substitutions} list.
LSX-00162: string "~S" is an invalid default for the complex type
Cause: If the {content type} is a simple type definition, then the string must be valid
with regard to the simple type definition as defined by String Valid (3.14.4). If the
{content type} is mixed, then the {content type}'s particle must be emptiable as
defined by Particle Emptiable (3.9.6). However, one of these conditions was not met,
resulting in this error.
Action: Make the default string a valid default with regard to the complex type
definition.
LSX-00001 to LSX-00345 40-7
LSX-00163: duplicated content specification in "~S"

Cause: There was a duplicate content specification in the children of complexType.
Action: Remove the duplicate content specification.
LSX-00164: no content specified in "~S"
Cause: In a simpleContent specification, either "restriction" or "extension" was not
specified as a child.
Action: Add either a "restriction" or an "extension" element information item.
LSX-00165: content type of "~S" must be simple type
Cause: The content type of the type definition was not a simple type definition.
Action: Use complexContent instead of simpleContent .
LSX-00166: both content types must be mixed or both must be element-only
Cause: If the content types of the derived type and base type are not the same simple
type definition and the content type of the base type is not empty, then both content
types must be mixed or both must be element-only. This was not the case, resulting in
this error.
Action: Add attribute mixed="true" or remove it.
LSX-00167: defining form of "~S" must occur at the top level
Cause: The defining form did not occur at the top level of a schema.
Action: Move attributeGroup or group definition to the top level of the schema.
LSX-00168: referring form of "~S" must NOT occur at the top level
Cause: The referring form did not occur within a complex type definition or an
attribute group definition.
Action: Move the attributeGroup definition to within a complex type definition or an
attribute group definition. Or, move the group definition to within a complex type,
restriction, extension, choice, or sequence.
LSX-00169: circular group reference is disallowed outside redefine
Cause: There was a circular group reference.
Action: One of the group references needs to be changed to a group definition.
LSX-00170: union must have memberTypes attribute or some simpleType children
Cause: There was no member type definition for the union declaration.
Action: Add memberTypes attribute or simpleType children.
LSX-00171: missing required sub-element "~S"
Cause: The sub-element specified in the error message was required.
Action: Add the required sub-element.
LSX-00172: "~S" is not a valid restriction of "~S"
Cause: The schema component constraint, Derivation Valid (Restriction, Complex) or
Particle Valid (Restriction), was violated.
Action: Modify the base type (particle) or the restricted type (particle) definition.
LSX-00173: ~S of ~S type is not a valid restriction of ~S of ~S type
Cause: The schema component constraint, Particle Restriction OK (Elt:Elt -NameAndTypeOK), was violated.
40-8 Error Messages
Action: Modify either or both element declaration particles.

LSX-00174: "~S" is not a valid derivation of "~S"
Cause: The schema component constraint, Derivation Valid (Restriction, simple),
(Restriction, complex) or (Extension), was violated.
Action: Modify the base type or the derived type definition.
LSX-00175: a complex base within "simpleContent" must have simple content
Cause: A complex base within "simpleContent" was not restricted to contain only
simple content.
Action: Modify the base type or the derived type definition.
LSX-00176: circular reference detected in schema component named "~S"
Cause: An attempt was made to use a circular reference. This is not allowed. For
example, it is not possible to return to an element declaration by repeatedly following
the {substitution group affiliation} property. Or, within the {particles} of a group there
must not be at any depth a particle whose {term} is the group itself.
Action: Modify one of the schema components in the loop.
LSX-00200: element "~S" not empty
Cause: Content of the element must be empty.
Action: Remove any schema components in the content.
LSX-00201: contents of "~S" should be elements only
Cause: Node with type other than "element", "processing instruction", or "comment"
exists in the content of the violating element.
Action: Remove the offending nodes.
LSX-00202: contents of "~S" should be text only
Cause: Node with type other than "text", "processing instruction", or "comment" exists
in the content of the violating element.
Action: Remove the offending nodes.
LSX-00204: extra data at end of complex element
Cause: Extra nodes exist at the end of an element with a complex type definition.
Action: Remove the offending nodes or check the definition of the complex type.
LSX-00205: element "~1S" value "~2S" is wrong (must be "~3S")
Cause: The element had a value other than its fixed value.
Action: Use the fixed value as its value.
LSX-00206: substitution for element "~S" is disallowed
Cause: An attempt was made to substitute an element that violated a constraint.
Action: Change to a valid new element that can be substituted for the headElement.
LSX-00207: empty list is disallowed
Cause: An empty list was supplied where at least one value is required.
Action: Specify at least one valid list item.
LSX-00001 to LSX-00345 40-9
LSX-00208: circular type reference disallowed

Cause: A type referenced itself as a member type, either directly or indirectly using
other types.
Action: Remove the circular type dependency.
LSX-00209: fixed or default not allowed on ID-based type
Cause: A type derived from the ID type specified a fixed value or a default value.
Action: Remove the fixed or default value from the type.
LSX-00210: value "~1S" out of range for type "~2S"
Cause: Value is out of range for the data with a specific type.
Action: Fix the value.
LSX-00211: value "~1S" whose fractional digits exceeds ~2d
Cause: Too many fractional digits after the decimal point.
Action: Remove the extra fractional digits.
LSX-00212: value "~1s" whose total digits exceeds ~2d
Cause: Too many digits in the decimal data.
Action: Remove the extra digits.
LSX-00213: only ~1d occurrences of particle "~2S", minimum is ~3d
Cause: Too few occurrences of particles in the node.
Action: Specify more particles.
LSX-00214: too many occurrences of particle "~1S", maximum is ~2d
Cause: Too many occurrences of particles in the node.
Action: Remove extra ones.
LSX-00215: value "~1S" whose total digits exceeds ~2d
Cause: There were too many digits in the decimal data.
Action: Remove the extra digits.
LSX-00220: "~1S" is wrong length, should be ~2d
Cause: Data of simple type has invalid length.
Action: Fix the length of the data.
LSX-00221: "~1S" is too short (minimum length is ~2d)
Cause: The length of the data is too short.
Action: Prepend extra characters (such as zeros or blank characters) to make the data
longer.
LSX-00222: "~1S" is too long (maximum length is ~2d)
Cause: The length of the data is too long.
Action: Remove extra characters from the data.
LSX-00229: item type is not a valid type for a list simple type
Cause: The specified item type must not itself be a list type, and must be one of the
types identified in [XML Schemas: Datatypes] as a suitable item type for a list simple
type.
Action: Change the list schema component's declaration.
LSX-00230: invalid integer "~S"

Cause: Illegal characters exist in the "integer" or its derivative type declarations.
LSX-00231: invalid unsigned integer "~S"
Cause: Illegal characters exist in the "unsignedLong", "unsignedInt", "unsignedShort",
or "unsignedByte" declarations.
LSX-00232: invalid unsigned long "~S"
Cause: Illegal characters exist in the "unsignedLong" declaration.
LSX-00233: invalid long "~S"
Cause: Illegal characters exist in the "long" declaration.
LSX-00234: invalid decimal "~S"
Cause: Illegal characters exist in the "decimal" declaration.
LSX-00235: invalid URI "~S"
Cause: Invalid URI specification for data of "anyURI" type.
LSX-00237: invalid Name "~S"
Cause: Invalid XML name.
LSX-00238: invalid Nmtoken "~S"
Cause: Invalid Nmtoken.
LSX-00240: bad float "~S"
Cause: Invalid value for "float" type data.
LSX-00241: bad double "~S"
Cause: Invalid value for "double" type data.
LSX-00242: bad Boolean "~S"
Cause: Boolean data must have a value from the following set: "1", "0", "true", or
"false".
Action: Specify one of "1", "0", "true", or "false".
LSX-00243: invalid date "~S"
Cause: Invalid value for data of "date" type.
LSX-00001 to LSX-00345 40-11
LSX-00244: invalid NCName "~S"

Cause: Invalid value for data of "NCName" type.
LSX-00245: invalid ID "~S"
Cause: Data specified is not of "NCName" type.
LSX-00246: invalid QName "~S"
Cause: Invalid value for data of "QName" type.
LSX-00247: invalid language specification "~S"
Cause: Invalid value for data of "language" type.
LSX-00248: invalid duration "~S"
Cause: Invalid value for data of "duration" type.
LSX-00249: invalid date or time "~S"
Cause: Invalid value for data of "dateTime", "time", "gYearMonth", "gYear",
"gMonthDay", "gDay", or "gMonth" type.
LSX-00250: invalid normalizedString "~S"
Cause: Invalid value for data of "normalizedString" type.
LSX-00251: invalid token "~S"
Cause: Invalid value for data of "token" type.
LSX-00252: invalid union "~S"
Cause: Data of simple type is not one of the union type.
Action: Use one of the union type as its type.
LSX-00253: branch is empty
Cause: The pattern specification "branch1 | branch2" has either "branch1" or
"branch2" missing.
Action: Remove '|' or add either "branch1" or "branch2".
LSX-00255: mismatched parentheses
Cause: ")" found without a matching "(" in a pattern specification.
Action: Add "(" to the pattern specification.
LSX-00256: empty character class expression
Cause: "[]" found when processing a character class expression.
Action: Specify the character group within the brackets.
LSX-00257: atom specification is missing

Cause: A quantifier was found without an atom specification.
Action: Add an atom specification in front of the quantifier.
LSX-00258: invalid escape character
Cause: "x" in "\x" is not a valid escape character.
Action: Change "x" to a valid escape character.
LSX-00259: invalid character found in the pattern
Cause: An unexpected character was found in the pattern.
Action: Fix the pattern.
LSX-00260: unexpected end of pattern
Cause: Something is missing at the end of the pattern.
Action: Fix the pattern.
LSX-00261: invalid character property
Cause: An error occurred when processing the character property. For example, "{" is
missing after "\p" or "\P".
Action: Fix the character property.
LSX-00262: attribute "~1S" cannot have complex type "~2S"
Cause: The type of the attribute is "complex".
Action: Specify the type of the attribute to be "simple".
LSX-00263: undefined attribute "~S"
Cause: Violating attribute is not defined in the current scope.
Action: Correct the attribute name if it's misspelled.
LSX-00264: attribute "~S" is prohibited (may not occur)
Cause: Global declarations cannot contain the attributes "ref", "minOccurs", or
"maxOccurs", or the use of this attribute is explicitly declared as "prohibited" by the
schema.
Action: Remove the attribute.
LSX-00265: attribute "~1S" value "~2S" is wrong (must be "~3S")
Cause: Attribute has a value other than its fixed value.
Action: Use fixed value as its value.
LSX-00266: missing required attribute "~S"
Cause: A required attribute is missing.
Action: Add the required attribute.
LSX-00270: hex-encoded binary has odd length
Cause: Data of "hexBinary" type has odd number of digits.
Action: Add missing digits as appropriate.
LSX-00271: invalid character "~c" in hex-encoded binary
Cause: Data of "hexBinary" type has invalid characters.
LSX-00001 to LSX-00345 40-13
LSX-00272: BASE64-encoded binary grouped improperly (not 4's)

Cause: Number of digits is not a multiple of four.
Action: Add missing digits as appropriate.
LSX-00273: invalid character "~c" in base64-encoded binary
Cause: Data of "base64Binary" type has invalid characters.
LSX-00274: invalid padding in base64-encoded binary
Cause: Invalid padding characters at the end of data.
Action: Use "=" as the padding characters.
LSX-00280: duplicate ID "~S"
Cause: ID name is not unique within the schema scope.
Action: Rename the ID.
LSX-00281: referenced ID "~S" is not defined
Cause: Referenced ID name is not defined within the schema scope.
Action: Define the ID.
LSX-00282: duplicate notation name "~S"
Cause: The name of the "notation" element is not unique within the schema scope.
Action: Rename the element.
LSX-00283: referenced notation "~S" is not defined
Cause: Referenced notation name is not defined within the schema scope.
Action: Define the element.
LSX-00284: duplicate constraint name "~S"
Cause: Each constraint declaration has a name which exists in a single symbol space
for constraints.
Action: Choose a different name.
LSX-00285: referenced key "~S" is not defined
Cause: Referenced key name is not defined within the schema scope.
Action: Define the key.
LSX-00286: duplicate key "~S" for {"~S"}"~S"
Cause: The key value was not unique within its scope.
Action: Change the key value.
LSX-00287: duplicate key "~S"
Cause: The key value was not unique within its scope.
Action: Change the key value.
LSX-00290: invalid enumeration choice "~S"
Cause: The value of the data is not one of the enumeration choice.
Action: Select one of the enumeration choice as its value.
LSX-00291: value "~1S" is less than minimum "~2S" (~3S)

Cause: Data has a value less than required minimum.
Action: Increase the value.
LSX-00292: value "~1S" is greater than maximum "~2S" (~3S)
Cause: Data has a value greater than maximum.
Action: Decrease the value.
LSX-00293: missing one or more fields from element "~S"
Cause: The required fields were missing from the content of the element.
Action: Add the fields.
LSX-00294: field "~S" produced multiple hits
Cause: XPath expressions relative to each element selected by a {selector}are specified
by {fields}. These XPath expressions must identify a single node (element or attribute)
whose content or value was used in the constraint. This content or value must be of a
simple type.
Action: Remove duplicate elements or attributes.
LSX-00295: field element "~S" is not a simple type
Cause: The field element evaluated to a node-set with a member that was not a simple
type.
Action: Change the field element's type.
LSX-00296: field value "~S" could not be compared to facet
Cause: The value of the data could not be compared to the facet value because one
value had a time zone while the other did not.
Action: Correct the data to add the necessary time zone or to remove the unnecessary
time zone.
LSX-00300: group must have name or ref but not both
Cause: "ref" or "name" attributes are either both missing or have both been specified.
Action: Specify either "ref", "name", but not both.
LSX-00310: local element or attribute should be namespace qualified
Cause: Element or attribute name is not namespace qualified.
Action: Add prefix or default namespace URI declaration.
LSX-00311: local element or attribute shouldn't be namespace qualified
Cause: Element or attribute name is namespace qualified.
Action: Remove prefix or default namespace URI declaration from itself or ancestors.
LSX-00320: missing required elements in all
Cause: Some required elements in "all" particle are missing.
Action: Add the missing elements.
LSX-00330: missing range start character
Cause: Missing range start character in a character range specification.
Action: Add the missing characters.
LSX-00001 to LSX-00345 40-15
LSX-00331: missing comma

Cause: A comma is missing in a range specification.
Action: Add the missing characters.
LSX-00332: bad decimal digits in a quantifier specification
Cause: Quatifier has invalid characters.
LSX-00333: literal "~S" is not valid with respect to the pattern
Cause: Literal is not valid with respect to the pattern.
Action: Choose correct characters in the literal.
LSX-00340: improper namespace value for the imported element
Cause: If the namespace attribute is present, then its actual value must not match the
actual value of the enclosing schema's targetNamespace attribute. If the namespace
attribute is not present, then the enclosing schema must have a targetNamespace
attribute.
Action: Match namespace value.
LSX-00341: ENTITY or ENTITIES type may only be used in attributes
Cause: For compatibility, ENTITY or ENTITIES should be used only on attributes.
Action: Remove the ENTITY or ENTITIES.
LSX-00342: value of attribute "base" must be a complex type definition
Cause: If the "complexContent" alternative is chosen, then the type definition resolved
to by the actual value of the attribute "base" must be a complex type definition.
Action: Choose a complex type definition as its base type.
LSX-00343: "~S" is not nillable
Cause: Attribute nillable was set to be "false" in element's declaration.
Action: Remove attribute xsi:nil from the instance document.
LSX-00344: namespace values "~1S" and "~2S" differ
Cause: The targetNamespace specified in the schema document differed from either:
a) the value of the enclosing schema's namespace attribute, or b) the value of the
namespace attribute identified in the import element information item.
Action: Match the namespace value to the enclosing schema's targetNamespace
attribute or the actual value of the namespace attribute identified in the import
element information item.
LSX-00345: Element ("~1S") from "~2S" namespace is unexpected. Expecting
element from "~3S" namespace
Cause: The namespace of the Xml Node in the instance document does not match
with the expected element definition namespace
Action: n/a
41
MGTCA-01001 to MGTCA-01117
MGTCA-01001: clusterware stack did not respond
Cause: A wallet operation was requested when the Oracle Clusterware stack was
down.
MGTCA-01002: clusterware stack did not respond to wallet operation
Cause: User attributes could not be read because the Grid Infrastructure Management
Repository wallet location was not accessible.
MGTCA-01003: wallet access denied
Cause: An attempt to access the wallet was denied because the user does not have the
required permissions.
MGTCA-01004: clusterware wallet internal error
Cause: An invalid wallet operation was performed or Oracle Cluster Registry storage
for wallet was not present.
MGTCA-01005: cannot perform database operation while setting Grid
Infrastructure Management Repository users
Cause: Failed to connect to Grid Infrastructure Management Repository using JDBC
during new user setup.
MGTCA-01006: could not change user credentials for Grid Infrastructure
Management Repository
Cause: SQL execute query failed.
MGTCA-01007: Grid Infrastructure Management Repository is not running on this
node
Cause: During the execution of 'mgmtca', no running instance of the Grid
Infrastructure Management Repository was found on the node.
Action: Run 'mgmtca' on the node having Grid Infrastructure Management
Repository.
MGTCA-01001 to MGTCA-01117 41-1
MGTCA-01008: An internal error occurred while querying for the node running
Grid Infrastructure Management Repository
Cause: During the execution of 'mgmtca', an internal error occurred while querying
for the node running Grid Infrastructure Management Repository.
MGTCA-01100: This utility is used to configure the Grid Infrastructure
Management Repository.\nUsage: mgmtca [[-em passwd] | [-gridhome] |
[[setpasswd -user user-1 [passwd-1] [, user-n passwd-n]]]
Cause: None
Action: None
MGTCA-01101: failure in Oracle Grid Infrastructure Management Repository
operation
Cause: A SQL request to the Oracle Grid Infrastructure Management Repository
encountered an error.
MGTCA-01102: failure in performing database operation to retrieve the name of
the Pluggable Database in the Oracle Grid Infrastructure Management Repository
Cause: An attempt to retrieve the name of the Pluggable Database in Oracle Grid
Infrastructure Management Repository failed.
MGTCA-01103: failure in performing database operation to unlock the user of
Oracle Grid Infrastructue Management Database
Cause: The user account to be unlocked did not exist.
MGTCA-01104: An internal error occurred during the remote execution of 'mgmtca'
on the node running the Grid Infrastructure Management Repository.
Cause: During the execution of 'mgmtca', an internal error occurred while remotely
executing the operation of the node running the Grid Infrastructure Management
Repository.
MGTCA-01105: Grid Infrastructure Management Repository is not running in the
cluster.
Cause: The execution of 'mgmtca' could not complete because the Grid Infrastructure
Management Repository was not running in the cluster.
MGTCA-01106: An internal error occurred while querying the state of the Grid
Cause: During the execution of 'mgmtca', an internal error occurred while querying
the state of the Grid Infrastructure Management Repository.
41-2 Error Messages
MGTCA-01107: The resource for the Grid Infrastructure Management Repository

does not exist.
Cause: The execution of 'mgmtca' could not complete because the resource for the
Grid Infrastructure Management Repository did not exist.
MGTCA-01108: failed to determine CRS Home location
Cause: Execution of 'mgmtca' to retrieve the CRS Home location failed. This is an
internal error.
MGTCA-01109: failed to determine Oracle Base location
Cause: Execution of 'mgmtca' to retrieve the Oracle Base location failed. This is an
internal error.
MGTCA-01110: An internal error occurred while querying the state of the Grid
Infrastructure Management Repository during reconfiguration.
Cause: The execution of 'mgmtca' could not complete because an internal error
occurred while querying the state of the Grid Infrastructure Management Repository
during reconfiguration.
MGTCA-01111: An internal error occurred while stopping the existing instance of
the Grid Infrastructure Management Repository during reconfiguration.
occurred while stopping the existing instance of the Grid Infrastructure Management
Repository during reconfiguration.
MGTCA-01112: An internal error occurred while removing the existing instance of
the Grid Infrastructure Management Repository during reconfiguration.
occurred while removing the existing instance of the Grid Infrastructure Management
MGTCA-01113: The reconfigure operation for the Grid Infrastructure Management
Repository could not complete because there was already an instance running on
the cluster.
Cause: The reconfigure operation for the Grid Infrastructure Management Repository
could not complete because there was already an instance running on the cluster.
MGTCA-01114: An internal error occurred while creating the Grid Infrastructure
Management Repository during reconfiguration.
occurred while creating the Grid Infrastructure Management Repository during
reconfiguration.
MGTCA-01001 to MGTCA-01117 41-3
MGTCA-01115: An internal error occurred while starting the resource for the Grid
Infrastructure Management Repository during reconfiguration.
occurred while starting the resource for the Grid Infrastructure Management
MGTCA-01116: The syntax of the 'mgmtca' command is incorrect.
Cause: The 'mgmtca' command was rejected because the syntax as entered was
incorrect.
Action: Reenter the 'mgmtca' command with the correct syntax. Enter 'mgmtca -h' to
display usage.
MGTCA-01117: The username specififed in the 'mgmtca' command is incorrect.
Cause: The 'mgmtca' command was rejected because the syntax as entered was
incorrect.
Action: Provide correct username for the 'mgmtca' command.
41-4 Error Messages
42
NCR-00001 to NCR-04028
NCR-00001: NCR: Could not allocate memory
Cause: Insufficient swap space or system memory.
Action: Increase swap space or system memory.
NCR-00002: NCR: Invalid usage
Cause: Bad function parameter.
Action: Check function call.
NCR-00003: NCR: Initialization failure
Cause: Usually insufficient swap space or system memory.
Action: Increase swap space or system memory.
NCR-01003: NCRS: Read error.
Cause: Failed to read data from an input device.
Action: Check the input device driver return code for further information.
NCR-01004: NCRS: Write error.
Cause: Failed to write data to an output device.
Action: Check the output device driver return code for further information.
NCR-01005: NCRS: Failed to flush the output buffer.
Cause: Failed to write data in the output buffer to an output device.
Action: Check the output device driver return code for further information.
NCR-01006: NCRS: Data buffer overflow.
Cause: An attempt to read or write data outside of a given data buffer.
Action: Check data buffer size.
NCR-01007: NCRS: Operation is not supported in a given mode.
Cause: Attempt to perform an operation which is not supported for the current mode.
Action: See documentation for a list of work modes and supported operations.
NCR-01008: NCRS: Failed to obtain transport parameters.
Cause: Could not identify transport layer parameters.
Action: Check the transport layer return code for further information.
NCR-01009: NCRS: Record handling error.
Cause: Encountered an invalid record or an attempt to read beyond last record.
Action: See documentation for description of record handling methods.
NCR-00001 to NCR-04028 42-1
NCR-01010: NCRS: Invalid network address length.

Cause: Network address size is set to 0.
Action: See documentation for valid network address sizes.
NCR-01011: NCRS: Send message failure.
Cause: Failed to send a message over network.
Action: Check the network interface return code for further information.
NCR-01012: NCRS: Receive message failure.
Cause: Failed to receive a network message.
Action: Check the network interface return code for further information.
NCR-01013: NCRS: Unvalid connection type.
Cause: Connection type is other than stream or message.
Action: See documentation for description of connection types.
NCR-01018: NCRS: Encryption failure.
Cause: Can not do the encryption for the data.
Action: See the SNS documentation for more information.
NCR-01019: NCRS: Checksumming failure.
Cause: Can not add the checksumming for the data.
Action: See the SNS documentation for more information.
NCR-01020: NCRS: Operation would block.
Cause: An I/O operation returned with no data read/written because the transport
connection is "non-blocking" and, to succeed, the operation would have needed to
block.
Action: This is a soft error; retry the operation.
NCR-02003: NCRF: Invalid type passed to format interpreter.
Cause: The format interpreter was given a data type it did not recognize.
Action: Check the types returned to the interpreter from either the type callback
routine or from the type context structure.
NCR-02004: NCRF: Invalid format interpreter type context
Cause: The format interpreter was given an invalid type context.
Action: This error usually happens due to an improperly described aggregrate. For
example, declaring NCRF_END_STRUCT_DATA_TYPE within a context, without a
complementary NCRF_STRUCT_DATA_TYPE, is invalid.
NCR-02005: NCRF: Invalid session mode
Cause: The data format layer received a session mode other than GET,PUT or FREE.
Action: None
NCR-02006: NCRF: Invalid floating point representation received
Cause: The data format layer received a floating point representation it did not
recognize.
Action: Check incoming format descriptor for errors.
42-2 Error Messages
NCR-02007: NCRF: Invalid format descriptor received

Cause: The data format layer received an improperly formed format descriptor.
Subsequent data could not be formatted.
Action: Check for data integrity on receipt from remote host.
NCR-02008: NCRF: Error within stream processing in format interpreter
Cause: An error occured while the interpreter was processing an
NCRF_STREAM_DATA_TYPE.
Action: Check for data integrity, or for stream existence.
NCR-02009: NCRF: Unable to open trace file
Cause: Failure to open tracing file.
Action: Make sure that this is a legal file name and that the user has write access.
NCR-02010: NCRF: Call context is not available
Cause: Call context not passed to format context.
Action: Make sure that create call context has been called.
NCR-02011: NCRF: Exceeded maximum number of rfids.
Cause: Exceeded maximum number of rfids.
Action: Call Oracle Support.
NCR-03002: NCRO: Maximum number of contexts has been reached
Cause: An attempt to create either a call context or a service context has failed because
all context slots are in use.
Action: Free-up context slots by destroying those contexts no longer required, or,
reconfigure NCRO with more context slots.
NCR-03003: NCRO: Unexpected message
Cause: Message read from service connection is not of the expected type.
Action: Application error - debug and fix.
NCR-03004: NCRO: Unknown message
Cause: Message read from service connection is of unknown type.
Action: Internal error - contact customer support.
NCR-03005: NCRO: Orphan message
Cause: Message read from service connection is for a call context that no longer exists.
NCR-03006: NCRO: Invalid operation
Cause: Attempted operation over call context is invalid. For example, attempting to
send IN args for a procedure which is defined to have none.
NCR-03007: NCRO: Context is busy
Cause: Attempted operation failed because service/call context is busy performing a
previous operaion.
NCR-00001 to NCR-04028 42-3
NCR-03008: NCRO: Call rejected

Cause: An attempt to execute a remote procedure has failed because the server has
rejected the procedure id.
Action: If wrong procedure id, send the correct one. If wrong server was contacted,
then contact the right one.
NCR-03009: NCRO: Protocol version mismatch
Cause: Client and server NCRO layers are at incompatible versions levels.
Action: Upgrade to latest NCRO version.
NCR-03010: NCRO: Transfer callback error
Cause: Application transfer callback function has returned a "FAILED" status.
Action: Debug the transfer callback function.
NCR-03012: NCRO: Invalid session mode
Cause: Attempted operation has failed because the session context is in an invalid
state.
NCR-03013: NCRO: Operation not supportd
Cause: Attempted operation is not supported on this service connection because it is
incompatible with the NCRO version level of the remote application.
Action: Link remote application with latest NCR library.
NCR-03014: NCRO: Bad transport address
Cause: A service context cannot be created because the transport address descriptor
(contained in the binding context) is invalid.
Action: Application error - initialize the transport address descriptor correctly.
NCR-03015: NCRO: No transport address
Cause: A service context cannot be created because no transport address was
provided (in the binding context) and the transport protocol uses datagrams.
Action: Application error - provide a transport address.
NCR-03016: NCRO: Message has bad address
Cause: Message read from service connection has bad address information.
NCR-03017: NCRO: Transport type RSLV not supported
Cause: Support for transport type RSLV has not been built.
Action: Re-compile NCR library with NCR_USE_RSLV defined.
NCR-03018: NCRO: Failed to make RSLV connection
Cause: Failure to make RSLV connection usually means that the name resolution
failed or the resolved TNS address is bad.
Action: Make sure that the name is in TNSNAMES.ORA and that it is set to the
correct TNS address.
NCR-03019: NCRO: Unable to initialize thread support
Cause: Attempt to initialize the Core thread package has failed.
42-4 Error Messages
NCR-03020: NCRO: Invalid call context

Cause: The call context is not an valid call context.
Action: Call context was destroyed, probably because the Break was received
NCR-03021: NCRO: Reset the in-band line
Cause: Our parnter is asking to reset the in-band line, after receiving a break
Action: The in-band line is required to be reset
NCR-03022: NCRO: Cannot send the break
Cause: There is an error occur when sending the break using the side-band channel
Action: Read the documention regarding to side-band break support issues
NCR-03023: NCRO: Cannot receive the break
Cause: There is an error occur when receiving the break using the side-band channel
Action: Read the documention regarding to side-band break support issues
NCR-03024: NCRO: Transport type LIST not supported
Cause: Support for transport type LIST has not been built.
Action: Re-compile NCR library with NCR_USE_LIST defined.
NCR-03025: NCRO: Failed to make LIST connection(s)
Cause: Failure to make LIST connection(s) usually means one of two things: (1)
Address list syntax error, (2) Could not connect with supplied addresses
Action: Check address list syntax and make sure that there is a 'listener' process for
each (or some) of the supplied addresses.
NCR-03026: NCRO: The result buffer has overflowed
Cause: The result buffer for holding the pickling result is too small.
Action: Please enlarge the result buffer and try again.
NCR-03027: NCRO: No remote service session set up yet.
Cause: Sender-makes-right needs the remote FID.
Action: Please set up the remote session before using the Send Make's Right option.
NCR-03028: NCRO: Partner refused request for sender-makes-right.
Cause: Sender-makes-right was requested by the current side, yet refused by the
server.
Action: Check the server side to see why it refused SMR.
NCR-04002: NCRR: Invalid interface descriptor
Cause: An attempt to register an interface has failed because of an invalid interface
descriptor.
Action: Check interface descriptor passed into the ncrrri_register_interface call.
NCR-04003: NCRR: Interface exists
Cause: An attempt to register an interface has failed because an interface already
exists.
Action: Application error - register a new interface, destroy the old one, or indicate
that the old one must be replaced.
NCR-00001 to NCR-04028 42-5
NCR-04004: NCRR: Invalid interface instance handle

Cause: A service registration API call has failed because of an invalid instance handle.
NCR-04005: NCRR: Invalid procedure handle
Cause: A procedure/object registration has failed because of an invalid procedural
handle.
NCR-04006: NCRR: Invalid argument descriptor
Cause: A procedure registration has failed because of an invalid argument descriptor.
NCR-04007: NCRR: Invalid object handle
Cause: A service registration API call failed because of an invalid object handle, for
example, one that does not exist.
NCR-04008: NCRR: Procedure exists
Cause: An attempt to register a remote procedure has failed because the procedure
already exists in this interface.
Action: Application error - register a new procedure, destroy the old one, or indicate
that the old one must be replaced.
NCR-04009: NCRR: Object exists
Cause: An attempt to register an object has failed because the object already exists in
this interface.
Action: Application error - register a new object, destroy the old one, or indicate that
the old one must be replaced.
NCR-04010: NCRR: Unable to contact Oracle Internet Directory Server
Cause: Service export or import failed to contact Oracle Internet Directory Server.
Action: Ensure Oracle Internet Directory configuration is correct. Otherwise, turn on
tracing and/or contact customer support.
NCR-04011: NCRR: Oracle Internet Directory error
Cause: Service export or import failed during interaction with Oracle Internet
Directory Server.
Action: Either wrong parameters with respect to the Remote Operations Service
Registration Schema were passed in and/or the Oracle Internet Directory server
refused to perform the requested operation. Refer the Remote Operations Service
Registration Schema and/or turn on Oracle Internet Directory tracing and/or contact
customer support.
NCR-04012: NCRR: Invalid address descriptor
Cause: An ncrrei_export_interface call failed because of an invalid address descriptor.
NCR-04013: NCRR: Insufficient authorization
Cause: Attempted Oracle Internet Directory Server operation has failed because of
insufficient authorization.
42-6 Error Messages

NCR-04014: NCRR: Invalid instance name
Cause: Service export or import failed because of an invalid instance name
NCR-04015: NCRR: Invalid interface name
Cause: Service export or import failed because of an invalid interface name
NCR-04016: NCRR: Last interface instance handle
Cause: The instance handle passed in is the last instance handle in the list.
Action: Not an error - means reaching the end of the list.
NCR-04017: NCRR: Unable to find the interface instance handle
Cause: The instance handle corresponding to the instance name was not found.
NCR-04018: NCRR: Unable to create the TNS address list
Cause: Unable to create the TNS address list from the interface instance list.
NCR-04019: NCRR: Interface or instance name already exists
Cause: Service export failed because the name already exists with the Oracle Internet
Directory server
NCR-04020: NCRR: Interface or instance name does not exist
Cause: Service expunge/query failed because the name does not exist with the Oracle
Internet Directory server
Action: Use Oracle Internet Directory tools on the relevant Oracle Internet Directory
instance to verify the same. Otherwise turn on tracing and/or contact customer
support
NCR-04021: NCRR: Pickler errors
Cause: Service export/query failed because of pickler errors
NCR-04022: NCRR: Invalid procedure descriptor
Cause: A procedure registration has failed because of an invalid procedural
descriptor.
NCR-04023: NCRR: Invalid object descriptor
Cause: An object registration has failed because of an invalid object descriptor.
NCR-04024: NCRR: Maximum number of procedures reached
Cause: A procedure registration has failed because the procedures array is filled up.
Action: Re-register the interface increasing the maximum # of procedures.
NCR-00001 to NCR-04028 42-7
NCR-04025: NCRR: Operation timed out

Cause: An operation for the Oracle Internet Directory server failed because it
exceeded the timeout period.
Action: Retry the operation and/or turn on Oracle Internet Directory tracing.
NCR-04026: NCRR: Operation not supported
Cause: An operation for the Oracle Internet Directory server failed because it met
with a server referral to another instance.
Action: Unify the Remote Ops registration entries into the Oracle Internet Directory
instance and/or turn on Oracle Internet Directory tracing.
NCR-04027: NCRR: Operation failed
Cause: An operation for the Oracle Internet Directory server failed because the
Service Registration interfaces met with invalid parameters.
NCR-04028: NCRR: Operation failed
Cause: An operation for the Oracle Internet Directory server failed because the data
involved exceeds the maximum allowed size.
Action: Check the entries in the Oracle Internet Directory instance with tools available
from Oracle Internet Directory and/or turn on Oracle Internet Directory tracing.
42-8 Error Messages
43
NID-00001 to NID-00604
NID-00001: Illegal command line syntax - parse error = (number)
Cause: Illegal operand on command line.
Action: Remove illegal operand.
NID-00002: Parse error: string
Cause: An error was encountered while parsing the command line.
Action: Remove offending operand.
NID-00010: Password:
Cause: Password was not specified in command line.
Action: Type password at this prompt.
NID-00100: Cannot open datafile "string"
Cause: The specified datafile could not be opened.
Action: Ensure that the specified datafile exists and is writable.
NID-00101: LOGFILE (string) not accessible
Cause: The specified log file could not be opened.
Action: Specify a log file that is writable.
NID-00102: Garbled target string
Cause: The supplied connect string could not be parsed. The connect string does not
have the correct format.
Action: Refer to Oracle9i Database Concepts.
NID-00103: Missing password in connect string "string"
Cause: Could not find the password in the supplied connect string. The connect string
does not have the correct format.
Action: Refer to Oracle9i Database Concepts.
NID-00104: Need to specify TARGET connection parameter in command line
Cause: The mandatory parameter TARGET was not specified.
Action: Specify TARGET=username/password when invoking this utility.
NID-00105: Need to specify "LOGFILE=logfile" when using APPEND=YES option
Cause: The APPEND parameter was specified without a LOGFILE.
Action: Specify APPEND=YES only when LOGFILE is also specified.
NID-00106: LOGIN to target database failed with Oracle error:\nstring
Cause: An Oracle error was reported while attempting to log in to the target database.
NID-00001 to NID-00604 43-1
Action: Follow the actions for the specified Oracle error.

NID-00107: File I/O error on datafile "string" during string operation (number/
string)
Cause: An operating system error was reported while performing the specified
operation in the specified file.
Action: Verify the datafile and check for operating system errors.
NID-00109: DBNAME string length number exceeds maximum length of number
Cause: The specified new database name exceeded the maximum size.
Action: Specify a shorter, valid name.
NID-00110: Cannot use REVERT and specify a database name at the same time
Cause: Conflicting options were specified in the command line.
Action: Choose only one of the options.
NID-00111: Oracle error reported from target database while executing\nstring
\nstring
Cause: An Oracle error was reported when executing an OCI operation.
Action: Follow the actions for the specified Oracle error.
NID-00112: unsupported connection mode
Cause: A mode different than SYSDBA or SYSBACKUP was specified for the
connection to the target.
Action: Specify only AS SYSDBA or AS SYSBACKUP.
NID-00113: Error reading answer - aborting
Cause: Response caused an error.
NID-00114: Must specify new database name when SETNAME is used
Cause: SETNAME=YES was specified but no DBNAME was provided.
Action: Specify DBNAME or remove the SETNAME=YES option.
NID-00115: Database should be mounted
Cause: The database was not mounted.
Action: Mount the database.
NID-00120: Database should be mounted exclusively
Cause: The database was started in parallel mode. To change the DBID, the database
must be mounted exclusively.
Action: Shut down the database and start it in exclusive mode.
NID-00121: Database should not be open
Cause: The database was open. To change the DBID, the database must be mounted
exclusively.
Action: Shutdown the database and mount it in exclusive mode.
NID-00122: Database should have no offline immediate datafiles
Cause: The database has one or more datafiles that are in OFFLINE IMMEDIATE
mode.
43-2 Error Messages
Action: Drop the datafiles or recover them and bring them online.
NID-00123: Magic number for datafile "string" is incorrect
Cause: Block 0 header has an incorrect magic number for the specified datafile.
Action: Verify that the datafile is correct and retry the operation.
NID-00124: Mismatched dbid for datafile string, expected number, found number
Cause: The dbid of the datafile does not match the 'old' DBID or the 'new' DBID.
Action: Verify that this datafile belongs to the database. You may need to restore a
backup of the datafile.
NID-00125: Database should have no disabled datafiles
Cause: The database has one or more datafiles that are disabled.
NID-00126: Database should have no datafiles in unknown state
Cause: The database has one or more datafiles that are in an unknown state.
NID-00127: All online files in the database must have the same checkpoint SCN
Cause: The database has one or more datafiles that have a checkpoint SCN that does
not match the database checkpoint SCN.
Action: Restart the database and shut it down cleanly, then retry the operation.
NID-00128: Cannot revert change of database, change not in progress
Cause: The REVERT option was used, but the control file does not show that a change
of DBID was in progress.
Action: Do not use the REVERT option, or possibly restore the control file that was in
place when the utility was started.
NID-00129: Invalid DBID for datafile "string", expecting number, found number
Cause: A datafile header shows a different DBID from the rest of the database files.
Action: Ensure that the file belongs to this database.
NID-00130: Mismatched CHECKPOINT_CHANGE# in datafile "string", expecting
string, found string
Cause: The datafile header does not match information in the control file.
Action: Revert the change, open the database, and verify that all datafiles are
consistent. Then, shut down the database and retry the operation.
NID-00131: Control file is not current
Cause: A non-current control file is currently mounted.
Action: Perform necessary actions to make the control file current and retry.
NID-00132: CHECKPOINT_CHANGE# in datafile "string": string in the future of
controlfile: string
Cause: The checkpoint in the datafile header is ahead of the checkpoint in the control
file.
Action: Make the database consistent and retry.
NID-00001 to NID-00604 43-3
NID-00133: Database should have only consistent datafiles

Cause: The database has one or more datafiles that are marked FUZZY in the control
file.
Action: Restart the database and shut down consistently, then retry the operation.
NID-00134: Datafile "string" is not consistent
Cause: The datafile is marked as fuzzy in its header.
Action: Restart the database and shut down cleanly, then retry the operation.
NID-00135: There are number active threads
Cause: There are active threads in the database. The most likely cause is that the
database crashed the last time it was shut down.
Action: Ensure that all threads are closed before retrying the operation. Start and
open the database to perform crash recovery, then shut down with the NORMAL or
IMMEDIATE options to close it cleanly. Finally, try running the utility again.
NID-00137: All datafiles that are not dropped should be readable
Cause: The database had one or more files that could not be read.
Action: Restore the missing files and retry the operation.
NID-00138: Block verification failed for datafile string (number)
Cause: Block header checksum yields a nonzero value for the specified datafile.
Action: Verify that the datafile is correct and retry the operation.
NID-00139: Mismatched dbname for datafile string, expected string, found string
Cause: The dbname of the datafile does not match the 'old' dbname or the 'new'
dbname.
Action: Verify that this datafile belongs to the database. You may need to restore a
backup of the datafile.
NID-00140: Specified database name string does not match previous name used
string
Cause: This is a continuation of a failed attempt. However in the failed attempt, the
database name is different than the one used in the last attempt.
Action: Retry the command using the original database name.
NID-00141: No database name specified, previous attempt used string
Cause: This is a continuation of a failed attempt. However, in the failed attempt, a
database name was provided.
Action: Retry the command using the original database name.
NID-00142: Only changing database name, previous attempt changed dbid to
number
Cause: This is a continuation of a failed attempt. However, in the failed attempt, the
database id was also being changed.
Action: Retry the command removing SETNAME=YES.
NID-00143: Mismatched controlfile string
Cause: A controlfile did not have the correct status.
Action: Shutdown the database, remove the mismatched controlfile, mount the
database, and retry the operation.
43-4 Error Messages
NID-00144: New name for database string is the same as current name string
Cause: The specified name is the same as the current name of the database.
Action: Specify a different name or do not use the DBNAME option.
NID-00145: nls subsystem initialization failure for product=string, facility=string
Cause: The NLS product/facility error message file could not be located or properly
initialized.
Action: Check that the error message directory and file(s) have been properly
installed.
NID-00300: Connected to database string (DBID=number)
NID-00301: Datafile string - dbid changed, wrote new name
NID-00302: Datafile string - dbid changed
NID-00303: Datafile string - wrote new name
NID-00304: Datafile string - reverted
NID-00305: Datafile string - already changed
NID-00306: Datafile string - no revert needed
NID-00307: Control File string - dbid changed, wrote new name
NID-00308: Control File string - dbid changed
NID-00309: Control File string - wrote new name
NID-00001 to NID-00604 43-5
NID-00310: Control File string - reverted

NID-00311: Control File string - modified
NID-00312: Connected to server version string
NID-00315: Operation already in progress, continuing
NID-00320: Operation cancelled at user request
NID-00321: Proceeding with operation
NID-00330: The following datafiles are offline immediate:
NID-00331: The following datafiles are disabled:
NID-00332: The following datafiles are in unknown state:
NID-00333: Cannot read the header of the following datafiles:
NID-00334: The following datafiles are not checkpointed to string:
NID-00335: The following datafiles are not consistent:
NID-00336: The following datafiles are offline clean:
43-6 Error Messages

NID-00337: The following datafiles are read-only:
NID-00338: Control Files in database:
NID-00350: string (number) string
NID-00351: string (number)
NID-00352: string (number), error: number
NID-00353: string
NID-00354: Instance shut down
NID-00370: Change database ID of database string? (Y/[N]) =>
NID-00371: Change database name of database string to string? (Y/[N]) =>
NID-00372: Change database ID and database name string to string? (Y/[N]) =>
NID-00373: Revert changes for database string (Y/[N]) =>
NID-00390: These files must be writable by this utility.
NID-00001 to NID-00604 43-7
NID-00395: Reverting database name from string to string

NID-00396: Reverting database ID from number to number
NID-00397: Changing database name from string to string
NID-00398: Changing database ID from number to number
NID-00400: DBNEWID - Completed with errors.
NID-00401: Must finish REVERT changes before attempting any database
operation.
NID-00402: Must finish change or REVERT changes before attempting any
database operation.
NID-00403: DBNEWID - Completed with validation errors.
NID-00404: DBNEWID - Completed succesfully.
NID-00405: Reversion of database name and database ID failed.
NID-00406: Reversion of database name failed.
NID-00407: Reversion of database ID failed.
43-8 Error Messages
NID-00410: Reversion of database changes failed during validation - database is

intact.
NID-00415: Change of database name and database ID failed.
NID-00416: Change of database name failed.
NID-00417: Change of database ID failed.
NID-00420: Change of database name and ID failed during validation - database is
intact.
NID-00421: Change of database name failed during validation - database is intact.
NID-00422: Change of database ID failed during validation - database is intact.
NID-00425: Database name restored to string.
NID-00426: Database ID for database string restored to number.
NID-00430: Database is ready to be open or shut down.
NID-00431: DBNEWID - Reversion completed.
NID-00435: Database name changed to string.
NID-00001 to NID-00604 43-9
NID-00436: Modify parameter file and generate a new password file before
restarting.
NID-00440: Database ID for database string changed to number.
NID-00441: All previous backups and archived redo logs for this database are
unusable.
NID-00442: Database has been shutdown, open database with RESETLOGS option.
NID-00450: Succesfully changed database name and ID.
NID-00451: Succesfully changed database name.
NID-00452: Succesfully changed database ID.
NID-00480: Database is intact - database is ready to be open or shut down.
NID-00481: DBNEWID - Cancelled.
NID-00482: Database is not aware of previous backups and archived logs in
Recovery Area.
Cause: Because the database id was changed, previous backups and archived redo
logs in recovery area are not managed by this database.
Action: This is the informational message only.
NID-00490: LOG being redirected to STDERR due to errors.
Cause: Could no write message to log file.
Action: None
NID-00500: Keyword Description (Default)

NID-00501: ---------------------------------------------------Cause: Informational message.
NID-00502: TARGET Username/Password (NONE)
NID-00503: DBNAME New database name (NONE)
NID-00504: LOGFILE Output Log (NONE)
NID-00505: REVERT Revert failed change NO
NID-00506: SETNAME Set a new database name only NO
NID-00507: APPEND Append to output log NO
NID-00508: HELP Displays these messages NO
NID-00600: Internal Error - [number] [number] [number] [number]
indicates that the program has encountered an exceptional condition.
Action: Report as a bug - the first argument is the internal error number
NID-00601: Internal Error - [number] [string] [number] [number]
indicates that the program has encountered an exceptional condition.
NID-00602: Could not allocate number bytes for "string"
Action: Free memory at the operating system level and retry operation.
NID-00603: No datafiles found in database
Cause: Controlfile has not datafiles recorded
NID-00001 to NID-00604 43-11
NID-00604: No control files found in database

Cause: Instance has no control files recorded
44
NDFN-00020 to NDFN-00025
NDFN-00020: missing IPMI userid
Cause: Required user name argument was not specified.
Action: Reissue command with correct arguments.
NDFN-00021: missing node list
Cause: Required node list was not supplied.
Action: Re-issue command with correct arguments.
NDFN-00022: unrecognized command option: 'string'
Cause: Operation type missing or mis-spelled.
Action: Re-issue command with correct arguments.
NDFN-00023: no password read. Re-issue request
Cause: Required administrator password was not read in response to the password
prompt before finding end-of-line.
Action: Re-issue command and be sure to type the password immediately following
the prompt.
NDFN-00024: caught I/O exception: string
Cause: Unexpected I/O exception was encountered while attempting to read the
password. Exception string should indicate the precise cause.
Action: Re-issue command after repairing root cause.
NDFN-00025: string failed for node string
Cause: The indicated operation could not be completed for the specified node. The
lower-level error messages attached should indicate the root cause.
Action: Re-issue command after repairing the condition indicated.
NDFN-00020 to NDFN-00025 44-1
44-2 Error Messages
45
NMP-00001 to NMP-00011
NMP-00001: value too big
Cause: The SNMP program interface received a value too large for it to process. This
error is usually displayed underneath an error which describes in more detail the
value which caused the problem.
Action: Not normally visible to the user. For further details, turn on tracing and reexecute the failing operation. If the error persists, contact Worldwide Customer
Support.
NMP-00002: no such SNMP variable name
Cause: An SNMP request was not processed because the one or more of the variable
names in the request does not exist. This error is not normally visible to the user
except in a trace file, where it is usually part of a "soft" error condition which is
normal.
Action: The error may indicate that a managed server does not support an operation
requested by its control program, perhaps because of version incompatibility. For
further details, turn on tracing and re-execute the failing operation. If the error
persists, and does not occur as part of a "soft" error condition as noted in the trace file,
contact Worldwide Customer Support.
NMP-00003: bad SNMP variable value
Cause: The SNMP program interface received a variable value which has an
unsupported data type. This error may occur if a standard SNMP network monitor is
sending requests to an Oracle service through an SNMP-to-TNS gateway, and that
service cannot understand the requests.
Action: Not normally visible to the user. For further details, turn on tracing and reexecute the failing operation. If the error persists, and occurs when an Oracle control
program sends requests to an Oracle service, contact Worldwide Customer Support.
NMP-00004: SNMP variable is read only
Cause: The user attempted to change a variable value at a remote server, and that
variable is read-only. This error is usually displayed underneath an error which
describes the problem in more detail.
Action: Read-only variables may never be modified.
NMP-00005: general SNMP error
Cause: an SNMP error occured which did not fall under the heading of any other
more specific error condition. This error may occur if a standard SNMP network
monitor is sending requests to an Oracle service through an SNMP-to-TNS gateway,
and that service cannot understand the requests.
Action: Not normally visible to the user. For further details, turn on tracing and reexecute the failing operation. If the error persists, and occurs when an Oracle control
program sends requests to an Oracle service, contact Worldwide Customer Support.
NMP-00001 to NMP-00011 45-1
NMP-00006: uninitialized SNMP context

Cause: An internal function attempted to use an uninitialize SNMP handle.
Support.
NMP-00007: I/O failure
Cause: The SNMP program interface attempted to send or receive an SNMP request
and was unable to do so because of a network failure of some sort. This error is
usually displayed underneath an error which describes the problem in more detail.
The problem typically occurs when a control program is attempting to communicate
with a service and either that service has unexpectedly terminated or the network
path between the control program and the service has been interrupted.
Action: n/a
NMP-00008: SNMP message has incorrect version, version 0 is required
Cause: The SNMP program interface received a protocol request with an illegal
version number. This error may occur if a standard SNMP network monitor is
sending malformed requests to an Oracle service through an SNMP-to-TNS gateway.
Action: Ensure that the management platform in question is sending SNMP requests
with the correct version number. If the error persists, and occurs when an Oracle
control program sends requests to an Oracle service, contact Worldwide Customer
Support.
NMP-00009: SNMP initialization failure
Cause: The SNMP program interface could not be initialized, either because its error
message file could not be found, or because there is a malformed snmp.communities
parameter value in the parameter table.
Action: Check that SQL*Net has been installed properly and that all message files are
in their proper locations. Turn on tracing and look for parameter table load errors.
NMP-00010: memory exhausted
Cause: The program interface has run out of memory.
Action: Add more memory or run fewer processes.
NMP-00011: internal SNMP program interface error
Cause: An internal error occurred inside the SNMP program interface. This error is
usually displayed underneath an error which describes the problem in more detail.
Support.
45-2 Error Messages
46
NNC-00001 to NNC-00501
NNC-00001: maximum number of connections already open
Cause: All available name service connections are handling requests.
Action: If the problem occurs when running a name server, increase the values of
names.max_open_connections. If the problem occurs in a client program, turn on
tracing and re-execute the failing operation. If the error persists, contact Worldwide
Customer Support.
NNC-00002: error listening on stream string
Cause: The name server was asked to listen on the specified address, and failed,
probably because the address is malformed, or because it uses a SQL*Net protocol
adaptor which has not been installed.
Action: Make sure the address is properly formed, and that it uses a protocol adaptor
which has been installed on your system.
NNC-00003: error opening stream string
Cause: A name server or client program attempted to open a connection to another
server and failed, either because the server is down, or because the network path to
that server is not working. This error is usually displayed underneath an error which
describes the problem in more detail.
Action: Make sure that the server being connected to is listening on the address used,
and that there is network connectivity between the two end-points.
NNC-00004: connection is broken
Cause: The connection from a name server or client program to another server has
been broken, either because that server has shut down, or because the network path
to the server has stopped working. This error is usually displayed underneath an
error which describes the problem in more detail.
Action: Make sure that the server being connected to is running and listening on the
address used, and that there is network connectivity between the two end-points.
NNC-00005: cannot initialization stream subsystem
Cause: The name service stream subsystem could not be started, probably because of
a missing TNS error message file.
in their proper locations.
NNC-00050: message format error
Cause: A corrupted name server message was received by a name server or the name
server program interface.
NNC-00001 to NNC-00501 46-1
Support.
NNC-00051: message content error
Cause: A corrupted name server message was received by a name server or the name
server program interface.
Support.
NNC-00052: client and server protocol versions are incompatible
Cause: A name server message with an incompatible protocol version was received
by a name server or the name server program interface. This problem will occur when
there are clients and servers with widely varying protocol versions that are trying to
communicate.
Action: upgrade older client and server software so it is compatible with newer
software.
NNC-00053: ASN.1 error encountered while sending or receiving message
Cause: The name server or the name server program interface attempted to send or
receive a message and failed because of an ASN.1 error.
Support.
NNC-00400: memory exhausted
Cause: The program interface has run out of memory.
Action: Add more memory or run fewer processes.
NNC-00401: program interface initialization failed
Cause: The name server program interface could not be initialised, probably because
of a missing TNS or name server error message file.
NNC-00402: program interface de-initialization failed
Cause: An internal error occurred while the name server program interface was being
de-initialised by an internal function.
Support.
NNC-00403: program interface has not been initialised
Cause: An internal function has attempted to de-initialise the name service program
interface when it has not yet been initialised.
Support.
46-2 Error Messages
NNC-00404: supplied buffer of size string is smaller than minimum size string
Cause: A caller supplied the name server program interface with a memory buffer too
small for the interface's requirements. This error is usually displayed underneath an
error which describes the problem in more detail.
Support.
NNC-00405: network failure
Cause: The network connection between the client program and the name server has
failed, either because the server has shut down, or because the network path to the
server has stopped working. This error is usually displayed underneath an error
which describes the problem in more detail.
Action: Contact your name server administrator to make sure that the server being
connected to is running and listening on the address used, and that there is network
connectivity between the two end-points.
NNC-00406: name "string" does not exist
Cause: The user asked for information associated with a global name that does not
exist.
Action: Re-try the failing operation with a global name that exists.
NNC-00407: alias loop in name request
Cause: The name service detected an "alias loop" when trying to retrieve information
associated with a global name. An alias loop occurs when an alias name X points to
another alias name Y, which in turn points back to X, rather than eventually to a
global name which contains data.
Action: Contact your name server administrator to have the alias loop investigated
and fixed.
NNC-00408: name "string" exists but desired data does not
Cause: The user asked for information associated with a global name. The name in
question exists, but does not contain the desired type of information.
Action: Re-try the failing operation with a type which the desired name does contain.
NNC-00409: temporary name service failure
Cause: There are no name servers available to handle a client request, or a name
server was temporarily unable to handle a client request. This situation is almost
always temporary, and occurs when the program interface has issued a name server
request and not received a timely response from any of its preferred servers. Such
delays can occur due to transient network or name server outages or heavy load.
Action: Re-try the failing operation. If the error persists, make sure there is network
connectivity between the client and its preferred name servers, and contact your
name server administrator to make sure that those name servers are running.
NNC-00410: invalid preferred server address list
Cause: The names.preferred_servers parameter in sqlnet.ora is malformed.
Action: Make sure the address list is properly formatted.
NNC-00411: invalid default domain name "string"
Cause: The names.default_domain parameter in sqlnet.ora is invalid.
NNC-00001 to NNC-00501 46-3
Action: Make sure the parameter value is a valid global name. See your
documentation for the characters which may be used in a global name.
NNC-00412: invalid name "string"
Cause: The name server program interface was given an invalid global name to
process.
Action: Supply a valid domain name. If the error is caused by an internal function,
contact Worldwide Customer Support.
NNC-00413: general failure
Cause: A name server program interface error occured which did not fall under the
heading of any other more specific error condition. The error will usually be followed
by more specific lower-level information.
Support.
NNC-00414: invalid name-value binding string "string"
Cause: A caller provided the name server program interface with an invalid namevalue binding string value.
Action: Not normally visible to the user, except when using the name server control
program. If the error occurs when using the control program, retry the failing
operation with a valid name-value binding string argument. Otherwise, turn on
tracing and re-execute the failing operation. If the error persists, contact Worldwide
Customer Support.
NNC-00415: section identifier string is invalid, must be between string and string
Cause: An internal function has called the name server program interface with illegal
arguments.
Support.
NNC-00416: user callback function returned error number string
arguments.
Support.
NNC-00417: name "string" already exists
Cause: A caller has attempted to create a new global name, and that name already
exists.
operation with a name that does not already exist. Otherwise, turn on tracing and reexecute the failing operation. If the error persists, contact Worldwide Customer
Support.
NNC-00418: name "string" cannot be modified because it has children
Cause: A caller has attempted to delete or rename a global name, and that name
cannot be modified because it has child names underneath it in the name space.
46-4 Error Messages
operation with a name that is a leaf node. Otherwise, turn on tracing and re-execute
the failing operation. If the error persists, contact Worldwide Customer Support.
NNC-00419: authoritative server is unreachable
Cause: A name server request cannot be processed because the server which received
the operation does not own the name specified in the request and cannot locate the
server which does own the name. The error is almost always transient, and occurs
either because the path between the server receiving the request and the request's
final destination has been interrupted, or because the final destination is down.
program. Because the error is typically a transient one, retrying the failing operation
will usually work. If the failure persists, the name server which is allowed to process
the failing operation is probably shut down or unreachable. Contact your name server
administrator to make sure that your site's name servers are running, and are
properly configured.
NNC-00420: operation not allowed
Cause: A name server request cannot be processed because the server which received
the operation is not allowed to process it. The problem typically occurs when an
administrator has disabled request processing at a particular server for some reason.
Action: Contact your name server administrator to determine why server request
processing has been disabled.
NNC-00421: invalid modification directive string, must be between string and
string
arguments.
Support.
NNC-00422: invalid data type name "string"
Cause: A caller has provided an invalid data type name to the name server program
interface.
operation with a valid type name. Otherwise, turn on tracing and re-execute the
failing operation. If the error persists, contact Worldwide Customer Support.
NNC-00423: invalid data item syntax code string
Cause: A caller has provided an invalid data type code to the name server program
interface.
operation with a valid type name. Otherwise, turn on tracing and re-execute the
NNC-00424: invalid address "string"
Cause: A caller provided the name server program interface with an invalid address
value.
NNC-00001 to NNC-00501 46-5
operation with a valid address argument. Otherwise, turn on tracing and re-execute
NNC-00425: meta-data violation
Cause: A caller issued a name server modification request and that request cannot be
processed because it would violate data type meta-data constraints.
program. If the error occurs when using the control program, examine the meta-data
constraints for the data type being operated upon and don't violate them. Examples of
typical constraint violations are attempts to add a new data item to a name which
already contains alias information, or attempts to add alias information to a name
which already contains other data, or attempts to replace a data item with another
item that has the wrong syntax. If the error occurs outside the control program, turn
on tracing and re-execute the failing operation. If the error persists, contact
Worldwide Customer Support.
NNC-00426: no such data type
Cause: A caller attempted to create a data item, and could not because the data item's
type does not exist.
program. If the error occurs when using the control program, retry the operation with
an existent data type. Otherwise, turn on tracing and re-execute the failing operation.
If the error persists, contact Worldwide Customer Support.
NNC-00427: server does not support this version of the protocol
Cause: A name server message with an incompatible protocol version was received
by a name server or the name server program interface. This problem will occur when
there are clients and servers with widely varying protocol versions that are trying to
communicate.
Action: upgrade older client and server software so it is compatible with newer
software.
NNC-00428: invalid meta-data data item
Cause: A caller provided the name server program interface with an invalid metadata data item.
operation with a valid meta-data argument. Otherwise, turn on tracing and re-execute
NNC-00429: invalid octet string literal "string"
Cause: A caller provided the name server program interface with an invalid octet
string string value.
operation with a valid octet string argument. Otherwise, turn on tracing and reexecute the failing operation. If the error persists, contact Worldwide Customer
Support.
46-6 Error Messages
NNC-00430: Database not accessible

Cause: When a database is used for consistency between different nameservers, any
modify operation should not only modify the cache but also the database. And if the
database is not accessible, this error occurs.
program. If the error occurs when using the control program, make sure database is
available and then re-execute the operation. If error persists, contact Worldwide
Customer Support.
NNC-00431: NS address does not match any of the current addresses
Cause: When delegating a domain, the address of the Nameserver is provided by the
client. If the nameserver already exists, then it already has address(es) associated with
it. So, the address supplied by the client must match one of them. Otherwise, this
error occurs.
Action: Not normally visible to the user, except when using name server control
program. If the error occurs when using the control program, either provide an one of
the existing addresses of the name server or delegate the domain to a new
nameserver.
NNC-00500: warning: "string" parameter value is illegal, setting to string
Cause: The named parameter value is invalid.
Action: Make sure the parameter value is formatted correctly. Valid choices for
boolean parameter values are TRUE, FALSE, YES, NO, ON, and OFF.
NNC-00501: warning: "string" parameter value must be between number and
number, setting to number
Cause: The named parameter value is invalid or outside legal boundary values.
Action: Make sure the parameter value is a number, and falls between valid
minimum and maximum values, as specified in the error text.
NNC-00001 to NNC-00501 46-7
46-8 Error Messages
47
NNF-00001 to NNF-04009
NNF-00001: Not a TNS address
Cause: While asking to read an address the name service returned a record which was
not an address.
Support.
NNF-00002: Invalid value passed to function call
Cause: An invalid value was passed to an interface function.
Support.
NNF-00003: Naming adapter string does not exist
Cause: The requested name service adapter was not found in the current adapter
table.
Action: Check the spelling of the adapter reqested. Verify that the adapter runs on
this platform, and the adapter is compiled into the adapter table linked into the
executable.
NNF-00004: Operation not supported in string
Cause: The operation requested is not supported under this adapter.
Action: Verify that the operation being performed is not under restriction, such as
writing to read-only name service. For further details, turn on tracing and re-execute
NNF-00005: Functionality not implemented
Cause: The operation requested is not supported in this implementation.
Action: If this is retrieved from a production release, contact Worldwide Customer
Support. Otherwise, check the release notes as to the restrictions in this release.
NNF-00110: no values exist
Cause: Test program help text.
Action: None
NNF-00540: Failed to insert name: string
Cause: Failed to insert name into the native service.
Action: Verify that the name is not already in the native namespace and the
appropriate access permissions are set for the namespace.
NNF-00001 to NNF-04009 47-1
NNF-01001: ds_initialize: workspace initialization failed

Cause: The DCE workspace as setup by ds_initialize() failed to initialize.
Action: Verify that conditions necessary for a successful ds_initialize() call are present
on this platform (e.g is there enough memory?). Check that there is not another
workspace user in this program. For further details, turn on tracing and re-execute the
NNF-01002: DCE could not open configuration file
Cause: A DCE call returned an error that it could not access its configuration file.
Action: Check that the DCE configuration file for this platform is present, and
accessable. On Unix this file is dce_cf.db. Check if a simple call to
dce_cf_get_cell_name() succeeds.
NNF-01003: DCE could not find cell name
Cause: A DCE call returned an error that it could not find the cell name in its
configuration file.
Action: Check that this machine has been configured for a DCE cell. Chcek that the
DCE configuration file is not corrupted. On Unix, this file is dce_cf.db. Check if a
simple call to dce_cf_get_cell_name() succeeds.
NNF-01004: DCE returned unspecified error string
Cause: A DCE call returned an status that was not in this implementation's list of
possible status values for this DCE call.
Action: Verify that this platform's DCE release is not beyond those supported by this
Oracle application. If the error persists, contact Worldwide Customer Support.
NNF-01005: Internal XOM class violation
Cause: A DCE XOM call returned statuses inconsistent with the class definitions in
the DCE documentation.
Support.
NNF-01006: Attribute string not available
Cause: A insertion call attempted to use an attribute which did not have a translation
to a DCE attribute.
Action: Use another attribute, or insert the translation into DCE.
NNF-01007: DCE long strings are not supported
Cause: A query returned a object which has a XOM OM_S_LONG_STRING. The
current implementation does not support such objects.
Action: For further details, turn on tracing and re-execute the failing operation. If the
error persists, contact Worldwide Customer Support.
NNF-01008: XDS attribute syntax string incorrect for Oracle Names syntax string
Cause: The syntax as specified in the XDS object is different than that which is
expected for the given Oracle names syntax.
47-2 Error Messages
NNF-02001: NIS client error string: string

Cause: A call to an NIS (YP) function failed. This message contains the text of the NIS
error code returned.
Action: Should only be visible when returned as part of another error. If the error
persists, contact Worldwide Customer Support.
NNF-02002: NIS value does not conform to adapter schema: string
Cause: The values in the maps used by the NIS adapter must conform to a specific set
of internal formatting rules. This value returned did not conform to those rules.
Action: Should not be visible, unless you are attempting to create your own maps. If
the error persists, contact Worldwide Customer Support.
NNF-02003: Unknown NIS error code: string
Cause: An error code returned by a NIS (YP) function was not in the list expected by
this program.
Action: Verify that the error is generated by the YP functions on this platform. Notify
Worldwide Customer Support of the error.
NNF-02004: NIS map string does not exist
Cause: The requested attribute does not exist.
Action: For an unused attribute, no action is required, as this is the expected error.
Otherwise, add the attribute and reload the NIS (YP) maps.
NNF-02005: NIS key string does not exist in map string
Cause: The requested name was not found.
Action: For an unused name, no action is required, as this is the expected error.
Otherwise, add the name to the map and reload the NIS (YP) maps.
NNF-03002: Unknown BIND error code: string
Cause: The return code in the BIND (DNS) query response did not conform to those
values listed in RFC 1035.
Action: Verify that the error is generated by the BIND functions on this platform.
Notify Worldwide Customer Support of the error.
NNF-03003: Format error parsing server response
Cause: The query response packet returned from the BIND (DNS) API did not
conform to the format listed in RFC 1035.
NNF-03004: DNS Class mismatch (string)
Cause: The query response packet returned a class different from the ones expected
by the interface.
NNF-04000: File succesfully converted
Cause: The requested conversion is performed.
Action: Normal condition, no action necessary.
NNF-00001 to NNF-04009 47-3
NNF-04001: Error converting input file

Cause: The input file contains lines that cannot be converted by the conversion
program.
Action: Check that the syntax of the input file is correct.
NNF-04002: Outputfile already exists
Cause: An old output file already exists in the current directory
Action: Remove the existing file, and restart the conversion tool
NNF-04003: Entry in inputfile is too long
Cause: The makedbm program, limits entries in mapfiles to 1017 characters. Therefor,
the conversion tool will not process TNS addresses which are longer than 1017
characters.
Action: Shorten the offending entry.
NNF-04004: Invalid string in inputfile
Cause: the input file contains invalid lines.
Action: Check that the syntax of the input file is correct.
NNF-04005: Cannot open inputfile
Cause: The specified input file could not be found.
Action: restart the conversion tool with the correct input file.
NNF-04006: Could not create outputfile
Cause: An output file could not be created in the current working directory
Action: Change the permissions of the current directory and restart the conversion
tool.
NNF-04007: Error reading input file
Cause: A problem while reading the input file. This could be caused by an
unexpected end of file in the input file.
Action: Check that the file is intact and that the syntax of the input file is correct.
NNF-04008: Error writing outputfile
Cause: An error occured while writing to the output file.
Action: Check available disk space. If the error persists, contact Worldwide Customer
Support.
NNF-04009: Usage: tns2nis filename
Cause: The conversion tool was not invoked properly. The filename should either be
tnsnames.ora or native.ora
Action: Restart the conversion tool with the proper parameter.
47-4 Error Messages
48
NNL-00001 to NNL-01078
NNL-00001: request argument "string" is invalid
Cause: The user entered an invalid request command argument.
NNL-00002: request argument "string" is not allowed with this operation
Cause: The user entered a request command argument which is not valid with the
particular request command.
NNL-00003: memory exhausted
Cause: The program has run out of memory
Action: Check the amount of available memory on your machine to ensure that there
is enough memory to run this executable. If necessary, free up memory by running
fewer programs, then try again.
NNL-00004: invalid command argument "string"
Cause: The user entered an invalid command argument.
NNL-00005: no server has been set. Use the "SET SERVER" command first
Cause: The user attempted to issue a command which requires that a default
managed Oracle Names server be set first.
Action: Use the SET SERVER command to set your default server, then reissue the
command. Alternatively, if the command allows, re-issue it with a specific server
name so the control program does not need to use the default.
NNL-00006: timeout, server is not responding
Cause: The control program issued a request to an Oracle Names server and no
response arrived in a timely fashion. The network connection between the control
program and the server may be faulty, the server may be very heavily loaded, or
there may be substantial network delays between the control program and the server.
The latter is especially true for WAN links.
Action: Reissue the command; if it continues to fail, check to see that the server being
managed is running correctly and that the network connection between the server
and the control program is working correctly.
NNL-00007: server responded with an error
Cause: The control program issued a request to an Oracle Names server and the
server responded with an error.
NNL-00001 to NNL-01078 48-1
NNL-00008: request not understood by server

Cause: The control program issued a request to an Oracle Names server and the
server did not understand the request.
Action: If the server and the control program have different versions, they may be
unable to communicate. Check your documentation for version compatibility
constraints. If the server and control program are compatible, turn on tracing for
further details, and re-execute the failing operation. If the error persists, contact
Worldwide Customer Support.
NNL-00009: encryption of server password failed
Cause: The control program attempted and failed to encrypt a server password,
supplied either through the SET PASSWORD command or the
namesctl.server_password configuration parameter.
Action: An internal error not normally visible to the user. Contact Worldwide
Customer Support.
NNL-00010: error getting address for server "string"
Cause: The control program attempted to translate a server name to its corresponding
address, and failed. There are a large number of possible causes for the failure. The
control program's SQLNET.ORA file must exist in the correct system-specific location,
and must be readable by the control program. The file must contain a
names.preferred_servers entry with valid name server addresses. If the user has
changed managed servers with the SET SERVER command, the new server must be
running, and must be able to resolve the address or forward the request to another
server which can resolve the address. Alternatively, a TNSNAMES.ORA file with
valid name server names and addresses must exist in the correct system-specific
location.
NNL-00011: no server with name "string" exists
Cause: The user issued a SET SERVER request and the current managed Oracle
Names server was unable to translate that name into an address. Alternatively, the
user issued a control program request to a specific server, and that server's name
could not be translated into an address. Both problems are almost always caused by
mis-typing the server name.
Action: Re-issue the request with a valid server name.
NNL-00012: invalid "string" value "string"
Cause: The first argument is a data type, the second is a value. The user supplied an
invalid data value of the specified type.
Action: Re-issue the failing operation with correct data.
NNL-00013: not performed, permission denied for supplied password
Cause: The user issued a request to an Oracle Names server, and the password
supplied with the request was incorrect.
Action: Check to see that the password sent by the control program to the server is
correct for that server. You can set a new password with the SET PASSWORD control
program command.
48-2 Error Messages
NNL-00014: unknown data type "string"

Cause: The user issued a name server request which contained an unknown data
type.
Action: It is possible that the server had no information on the type, but automatically
fetched it in response to the failing request. Re-issue the failing request; if the server
has in the meantime fetched the appropriate data type information, the error will go
away. If the error persists, the data type is probably invalid.
NNL-00015: type "string" has "string" syntax, which has no textual representation
Cause: Not all data type syntaxes can be represented as text. This message indicates
that the user issued a name server request for a type with an non-textual
representation.
Action: Re-issue the operation with a data type that has a syntax with a textual
representation.
NNL-00016: cannot start server, error getting program directory's name
Cause: The user issued a STARTUP request, but the control program was unable to
start the server because it was unable to find the name of the directory where the
server executable resides.
Customer Support.
NNL-00017: cannot start server, program "string" does not exist
Cause: The user issued a STARTUP request, but the control program was unable to
start the server because it was unable to find the server executable.
Action: Make sure that a copy of the server executable exists in your system's oracle
executable directory.
NNL-00018: warning: could not contact default name server
Cause: The control program was unable to contact its default name server during
startup. There are a number of possible causes for this error. The control program's
SQLNET.ORA file must exist in the correct system-specific location, and must be
readable by the control program. The file must contain a names.preferred_servers
entry with valid name server addresses. The first server in the preferred-server list
must be running, and there must be network connectivity between the control
program and that server.
Action: Check to see that all of the above are true. If the control program is still unable
to contact its default server, turn on tracing and restart the control program. If the
NNL-00019: warning: server either changed or ignored your request
Cause: The user issued a request to an Oracle Names server and that request was
altered in some way. Typically the user specified an invalid argument of some sort,
and the server either ignored the request, or replaced the invalid argument with a
reasonable default.
Action: Use the control program to check the current state of the value that you
attempted to change. The server's log file may also contain information about the
exact cause of the problem. Re-issue the operation with correct arguments.
NNL-00001 to NNL-01078 48-3
NNL-00020: warning: no TNSNAMES.ORA file and no preferred name servers in

SQLNET.ORA
Cause: The control program was unable to find a TNSNAMES.ORA file and was
unable to find a default name server in SQLNET.ORA. The control program will
operate in this state, but will be unable to resolve any names until a default server has
been set, and that server must be set using its raw TNS address.
Action: The control program's SQLNET.ORA file must exist in the correct systemspecific location, and must be readable by the control program. The file must contain
a names.preferred_servers entry with valid name server addresses. The first server in
the preferred-server list must be running, and there must be network connectivity
between the control program and that server. Alternatively, a TNSNAMES.ORA file
with valid name server information must exist in the correct system-specific location.
NNL-00022: error changing trace level from string to string, level change ignored
Cause: The user attempted to change the control program's local trace level, and the
program encountered an error while changing the level. Usually the problem is that
tracing was enabled for the first time (by changing the trace level from OFF to
something else) and the trace file is not writeable by the control program.
Action: Check to see that the trace file is writeable. Your documentation will tell you
the name of the trace file.
NNL-00023: SET command is missing an argument
Cause: The user attempted to issue a SET command with no argument.
Action: Supply a valid argument to the SET command.
NNL-00024: warning: no preferred name servers in SQLNET.ORA
Cause: The control program was unable to find any preferred name servers in
SQLNET.ORA, and will therefore not connect to a default server.
Action: Make sure that the SQLNET.ORA file contains a valid
names.preferred_servers entry.
NNL-00035: File string or nested IFILEs not found.
Cause: Error in loading from the tnsfile.
Action: None
NNL-00036: No records loaded
Cause: No loadable data.
Action: None
NNL-00037: Error number while sequencing through parameter table.
Cause: The NL Parameter system reported an error while retrieving the next name
from the table.
Customer Support.
NNL-00038: Distinguished Name syntax error
Cause: Distinguished Name incorrectly specified.
Action: Supply a valid DN.
NNL-00039: no RRs
Cause: Object has no relevant RRs to be mapped to LDAP objects.
48-4 Error Messages
Action: None
NNL-00040: Distinguished Name exceeds buffer length: string
Cause: Distinguished Name derived from Domain Name is too long.
Action: Either move the object to a domain whose name is shorter or manually update
the LDAP object.
NNL-00041: Object string not in domain string
Cause: Object has no relevant RRs to be mapped to LDAP objects.
Action: None
NNL-00042: LDAP bind failure: number, string
Cause: Call to ldap_bind failed with return set to given number.
Action: Correct user/pwd parameters or definitions.
NNL-00043: LDAP open failure
Cause: LDAP server could not be contacted.
Action: Correct connect info or server unavailability.
NNL-00044: Unsupported data type string not mapped
Cause: ONames data type could not be mapped to LDAP attributes
Customer Support.
NNL-00045: No host given for LDAP server
Cause: LDAP open will dump core without a host.
Action: Provide appropriate host with '-h' option.
NNL-00046: Name string exceeds DN template depth
Cause: There are more domains in the name than are specified in the DN template.
Action: Add fields to the template or migrate subdomains with separate dump
operations.
NNL-00047: LDAP modify returned error: 0xnumber, string
Cause: LDAP failed with the return code shown.
Action: Refer to LDAP documentation for the meaning of the error.
NNL-00048: Error opening file: string
Cause: Named file cannot be opened.
Action: Provide for access to file.
NNL-00049: Output in string cannot be renamed to string
Cause: The given file cannot be created.
Action: Insure that the file specified can be created before running the command. Or
use the temporary file itself.
NNL-00201: Shutdown occurs in string
Cause: Control program general message.
Action: None
NNL-00001 to NNL-01078 48-5
NNL-00202: No shutdown currently scheduled

Action: None
NNL-00203: Scheduled shutdown to occur in string
Action: None
NNL-00204: Cancelled shutdown
Action: None
NNL-00205: Reload check occurs in string
Action: None
NNL-00206: No reload check currently scheduled
Action: None
NNL-00207: Scheduled reload check to occur in string
Action: None
NNL-00208: Cancelled reload check
Action: None
NNL-00209: Cache checkpoint interval is currently string
Action: None
NNL-00210: Cache checkpointing is currently disabled
Action: None
NNL-00211: Cache checkpoint interval is now string
Action: None
NNL-00212: Cache checkpointing is now disabled
Action: None
NNL-00213: No entry with specified index number, try "SHOW
SYSTEM_QUERIES"
Action: None
48-6 Error Messages
NNL-00214: Next auto-refresh for specified index number occurs in string

Action: None
NNL-00215: Scheduled specified index number's next auto-refresh to occur in string
Action: None
NNL-00216: Disabled auto-refresh for specified index number
Action: None
NNL-00217: Controller is sleeping for number seconds
Action: None
NNL-00218: Ignoring spurious trailing text "string"
Action: None
NNL-00219: Statistic counter logging interval is currently string
Action: None
NNL-00220: Statistic counter logging is currently disabled
Action: None
NNL-00221: Statistic counter logging interval is now string
Action: None
NNL-00222: Statistic counter logging is now disabled
Action: None
NNL-00223: Statistic counters are next logged in string
Action: None
NNL-00224: Scheduled statistic counters to be logged in string
Action: None
NNL-00225: Currently managing name server "string"
Action: None
NNL-00226: Current request-processing delay is string
NNL-00001 to NNL-01078 48-7
Action: None
NNL-00227: Request-processing delay is currently disabled
Action: None
NNL-00228: Request-processing delay is now string
Action: None
NNL-00229: Request-processing delay is now disabled
Action: None
NNL-00230: Controller NOCONFIRM mode is currently string
Action: None
NNL-00231: Controller NOCONFIRM mode is now string
Action: None
NNL-00232: Auto-refresh failure-retry interval is currently string
Action: None
NNL-00233: Auto-refresh failure-retry interval is now string
Action: None
NNL-00234: Auto-refresh failure-retry expiration period is currently string
Action: None
NNL-00235: Auto-refresh failure-retry expiration period is now string
Action: None
NNL-00236: Statistic counter reset interval is currently string
Action: None
NNL-00237: Resetting of statistic counters is currently disabled
Action: None
NNL-00238: Statistic counter reset interval is now string
Action: None
48-8 Error Messages
NNL-00239: Resetting of statistic counters is now disabled

Action: None
NNL-00240: Starting "string"...
Action: None
NNL-00241: Processing of modification requests is currently enabled
Action: None
NNL-00242: Processing of modification requests is currently disabled
Action: None
NNL-00243: Processing of modification requests is now enabled
Action: None
NNL-00244: Processing of modification requests is now disabled
Action: None
NNL-00245: General request processing is currently enabled
Action: None
NNL-00246: General request processing is currently disabled
Action: None
NNL-00247: General request processing is now enabled
Action: None
NNL-00248: General request processing is now disabled
Action: None
NNL-00249: DEFAULT-FORWARDERS-ONLY mode is currently enabled
Action: None
NNL-00250: DEFAULT-FORWARDERS-ONLY mode is currently disabled
Action: None
NNL-00251: DEFAULT-FORWARDER-ONLY mode is now enabled
NNL-00001 to NNL-01078 48-9
Action: None
NNL-00252: DEFAULT-FORWARDER-ONLY mode is now disabled
Action: None
NNL-00253: Server-generated requests currently request forwarding
Action: None
NNL-00254: Server-generated requests currently do not request forwarding
Action: None
NNL-00255: Server-generated requests now request forwarding
Action: None
NNL-00256: Server-generated requests now do not request forwarding
Action: None
NNL-00257: Server-generated requests currently require authoritative answers
Action: None
NNL-00258: Server-generated requests currently do not require authoritative
answers
Action: None
NNL-00259: Server-generated requests now require authoritative answers
Action: None
NNL-00260: Server-generated requests now do not require authoritative answers
Action: None
NNL-00261: Request forwarding is currently enabled
Action: None
NNL-00262: Request forwarding is currently disabled
Action: None
NNL-00263: Request forwarding is now enabled
Action: None
NNL-00264: Request forwarding is now disabled

Action: None
NNL-00266: Round trip time is string
Action: None
NNL-00267: Address is string
Action: None
NNL-00268: Enter name server password:
Cause: Prompt for password after user has issued 'set password'
Action: Type password, invisibly.
NNL-00270: Current default domain is "string"
Action: None
NNL-00271: Default domain is now "string"
Action: None
NNL-00272: Removed name "string" from caches along the following path:
Action: None
NNL-00273: server successfully started\n
Action: None
NNL-00274: server not started, errors follow
Action: None
NNL-00275: Trace level is currently number
Action: None
NNL-00276: Trace level is now number
Action: None
NNL-00277: Maximum number of times a request can be reforwarded is currently
number
Action: None
NNL-00001 to NNL-01078 48-11
NNL-00278: Maximum number of times a request can be reforwarded is now

number
Action: None
NNL-00279: Restart occurs in string
Action: None
NNL-00280: No restart currently scheduled
Action: None
NNL-00281: Scheduled restart to occur in string
Action: None
NNL-00282: Cancelled restart
Action: None
NNL-00283: Next cache checkpoint occurs in string
Action: None
NNL-00284: Scheduled cache checkpoint to occur in string
Action: None
NNL-00285: Server has no queued system queries
Action: None
NNL-00286: Server does not own any domains
Action: None
NNL-00287: Cache flush occurs in string
Action: None
NNL-00288: No cache flush currently scheduled
Action: None
NNL-00289: Scheduled cache flush to occur in string
Action: None
NNL-00290: Cancelled cache flush

Action: None
NNL-00291: Statistic counters are next reset in string
Action: None
NNL-00292: Scheduled statistic counters to be reset in string
Action: None
NNL-00293: Controller's trace level remains unchanged
Action: None
NNL-00294: No entries found
Action: None
NNL-00295: Controller's local trace level is currently number
Action: None
NNL-00296: Controller's local trace level changed from number to number
Action: None
NNL-00297: Cache will be dumped to trace file in string
Action: None
NNL-00298: No cache dump currently scheduled
Action: None
NNL-00299: Scheduled server cache dump to occur in string
Action: None
NNL-00300: Cancelled server cache dump
Action: None
NNL-00301: Server shutting down
Action: None
NNL-00302: Server restarting
NNL-00001 to NNL-01078 48-13
Action: None
NNL-00303: Server checking for reload
Action: None
NNL-00304: Server flushing its cache
Action: None
NNL-00305: Server dumping statistics to the log file
Action: None
NNL-00306: Server setting all statistic counters to zero
Action: None
NNL-00307: Server checkpointing its cache
Action: None
NNL-00308: Server dumping its cache to the trace file
Action: None
NNL-00340: Trace file name is currently string
Action: None
NNL-00341: Trace file name is now string
Action: None
NNL-00342: Log file name is currently string
Action: None
NNL-00343: Log file name is now string
Action: None
NNL-00344: Save_config_on_stop is currently ON
Action: None
NNL-00345: Save_config_on_stop is currently OFF
Action: None
NNL-00346: Save_config_on_stop is now ON

Action: None
NNL-00347: Save_config_on_stop is now OFF
Action: None
NNL-00348: Server saving the config file now
Action: None
NNL-00349: Configuration will be saved in string
Action: None
NNL-00350: No save config currently scheduled
Action: None
NNL-00351: Scheduled configuration save to occur in string
Action: None
NNL-00352: Cancelled save config
Action: None
NNL-00353: Not allowed
Action: None
NNL-00400: Response status:
Action: None
NNL-00401: Authoritative answer: string
Action: None
NNL-00402: Authoritative server: string
Action: None
NNL-00403: Number of answers: number
Action: None
NNL-00404: TTL: string
NNL-00001 to NNL-01078 48-15
Action: None
NNL-00405: Forwarding information:
Action: None
NNL-00406: Canonical name: string
Action: None
NNL-00407: Alias translations:
Action: None
NNL-00408: Answers:
Action: None
NNL-00409: data type is "string"
Action: None
NNL-00410: Average response time: string
Action: None
NNL-00411: Minimum response time: string
Action: None
NNL-00412: Number of requests: number
Action: None
NNL-00413: Total response time: string
Action: None
NNL-00414: Maximum response time: string
Action: None
NNL-00415: Name: string
Action: None
NNL-00416: Last timestamp: number
Action: None
NNL-00417: Distinguished Name: string

Action: None
NNL-00418: Attributes Mapped: number
Action: None
NNL-00500: Shows information on domains served by this server
Cause: Control program help text.
Action: None
NNL-00501: set|show log_stats_interval [seconds] [<server_list>] :\nset|show the
server's statistic counter logging interval
Action: None
NNL-00502: Shows, sets, or cancels when the server next dumps its statistic
counters
Action: None
NNL-00503: repeat number command [args] : repeat a command number times
Action: None
NNL-00505: log_stats [<server_list>] : write Names server statistics to the log file
Action: None
NNL-00506: reset_stats [<server_list>] : reset Names server statistics
Action: None
NNL-00507: Shows, sets, or cancels the time when an auto-refresh query is next
issued
Action: None
NNL-00508: show system_queries [<server_list>] : show system query information
Action: None
NNL-00509: set|show cache_checkpoint_interval [seconds] [<server_list>] :\nset|
show the server's cache checkpoint interval
Action: None
NNL-00510: Adds a data record to an existing name
NNL-00001 to NNL-01078 48-17
Action: None
NNL-00511: Shows or sets the server's system query authority requirements
Action: None
NNL-00512: Shows or sets the server's auto-refresh expiration period
Action: None
NNL-00513: Shows or sets the server's auto-refresh failure retry interval
Action: None
NNL-00514: Creates a new name with a default TTL
Action: None
NNL-00515: Deletes a name and its data
Action: None
NNL-00516: Displays complete server status
Action: None
NNL-00517: Insert-replaces a data item under an existing name
Action: None
NNL-00518: Shows or sets the maximum number of times a server can reforward a
request
Action: None
NNL-00519: Shows, enables, or disables modification request processing
Action: None
NNL-00520: Changes an existing name's TTL
Action: None
NNL-00521: Shows or sets the server's system query forwarding requirements
Action: None
NNL-00522: Removes a data item from a name by value or by type
Action: None
NNL-00523: Renames an existing name

Action: None
NNL-00524: Replaces a data item with another data item
Action: None
NNL-00525: Shows or sets the server's default-forwarding status
Action: None
NNL-00526: Starts a server using a non-standard executable and optional
arguments
Action: None
NNL-00527: Shows, sets, or cancels the time when the server next checkpoints its
cache
Action: None
NNL-00528: [set] password password : set the password for subsequent calls
Action: None
NNL-00529: set|show default_domain [<domain_name>] : set|show the current
default domain
Action: None
NNL-00530: quit|exit : exit the names control program
Action: None
NNL-00531: flush_name name :\nremoves a name from caches along a route to an
authoritative server
Action: None
NNL-00532: set|show forwarding_available [<on|off>] [<server_list>] :\nenable,
disable or show server request forwarding
Action: None
NNL-00533: ping [<server_list>] : ping one or more Names servers
Action: None
NNL-00001 to NNL-01078 48-19
NNL-00534: query name [type] : query for a desired name and RR type
Action: None
NNL-00535: reload [<server_list>] : reload server cache data if there are changes
Action: None
NNL-00536: set|show requests_enabled [<on|off>] [<server_list>] :\nenable,
disable or show server request processing
Action: None
NNL-00537: set|show server [<server_name>] : set|show the currently managed
server
Action: None
NNL-00538: stop|shutdown [<server_list>] : stop one or more Names servers
Action: None
NNL-00539: start|startup [args] : start the Names server with optional arguments
Action: None
NNL-00540: [show] status [<server_list>] : display server status summary
Action: None
NNL-00541: set|show trace_level [level] [<server_list>] :\nset|show the server's
tracing level
Action: None
NNL-00542: restart [<server_list>] : restart one or more Names servers
Action: None
NNL-00543: [show] version [<server_list>] :\nshow the name and version of one or
more Names servers
Action: None
NNL-00544: Displays operations statistics
Action: None
NNL-00545: Displays query request statistics
Action: None
NNL-00546: Displays delete request statistics
Action: None
NNL-00547: Displays rename request statistics
Action: None
NNL-00548: Displays update request statistics
Action: None
NNL-00549: Displays stream usage statistics
Action: None
NNL-00550: flush [<server_list>] : flush one or more servers' cache(s)
Action: None
NNL-00551: Displays cache statistics
Action: None
NNL-00553: Displays forwarding statistics
Action: None
NNL-00555: Displays meta data statistics
Action: None
NNL-00556: set|show reset_stats_interval [seconds] [<server_list>] :\nset|show
server statistic counter reset interval
Action: None
NNL-00557: Causes the controller to sleep for N seconds
Action: None
NNL-00558: set|show namesctl_trace_level : set|show the controller's tracing level
Action: None
NNL-00559: Shows, sets, or cancels the time for the next cache dump to the trace
file
Action: None
NNL-00001 to NNL-01078 48-21
NNL-00560: Shows or sets the server's request-processing delay

Action: None
NNL-00561: register name [-ttype] [-daddress] [-hhostname] [-l<listener_name>] :
\nregister an object with Oracle Names
Action: None
NNL-00562: unregister name [-daddress] [-l<listener_name>] :\nunregister an
object with Oracle Names
Action: None
NNL-00563: timed_query [timestamp] : query all objects in the Names server's
cache
Action: None
NNL-00565: set trace_file_name [filename] [<server_list>] :\nset|show the server's
trace file name
Action: None
NNL-00566: set|show log_file_name [filename] [<server_list>] :\nset|show the log
file name on one or more servers
Action: None
NNL-00567: reorder_ns [<server_address>] : Generate the enhanced discovery file
Action: None
NNL-00568: delegate_domain <domain_name> <NS_name> <NS_Addr> : Delegate
the given domain to the given nameserver
Action: None
NNL-00569: domain_hint <domain_name> <NS_name> <NS_Addr> : Provide hint
of a nameserver for a given domain
Action: None
NNL-00570: save_config [<server_list>] : saves server configuration to parameter
file
Action: None
NNL-00571: set|show save_config_on_stop [<on|off>]
Action: None
NNL-00572: set|show save_config_interval [seconds] [<server_list>] : set time of

next config save
Action: None
NNL-00573: load_tnsnames [file, ... ] : load tnsnames into ONames
Action: None
NNL-00574: dump_tnsnames [file] : dump ONames addresses into tnsnames file
Action: None
NNL-00575: list_objects: list all objects in a domain or subtree
Action: None
NNL-00576: list_delegated: list all delegated domains in the region or subtree
Action: None
NNL-00577: list_domains: list authoritative domains in the region or subtree
Action: None
NNL-00578: dump_ldap: dump addresses in the domain or region to LDAP
Action: None
NNL-00579: _scan: find objects/records matching the given types
Action: None
NNL-00580: register_ns: name server address domain
Action: None
NNL-00581: unregister_ns: name server domain
Action: None
NNL-00582: dump_alias: dump aliases in the domain or region to LDAP
Action: None
NNL-00800: Query requests received: number
Cause: Control program statistic description
Action: None
NNL-00001 to NNL-01078 48-23
NNL-00801: Queries received, type ANY: number

Action: None
NNL-00802: Queries received, type ADDRESS: number
Action: None
NNL-00803: Queries received, type ALIAS: number
Action: None
NNL-00804: Queries received, type META-DATA: number
Action: None
NNL-00805: Queries received, type NAME-SERVER: number
Action: None
NNL-00806: Queries received, type RELATED-INFO: number
Action: None
NNL-00807: Queries received, type SOA: number
Action: None
NNL-00808: Queries received, all user-defined types: number
Action: None
NNL-00809: Queries received, multiple types: number
Action: None
NNL-00810: Queries received with no type: number
Action: None
NNL-00811: Fastest query processing time: string
Action: None
NNL-00812: Slowest query processing time: string
Action: None
NNL-00813: Average query processing time: string
Action: None
NNL-00814: Total query processing time: string
Action: None
NNL-00830: Delete requests received: number
Action: None
NNL-00831: Deletes refused, name is not a leaf name: number
Action: None
NNL-00832: Deletes refused, name is a topology name: number
Action: None
NNL-00833: Fastest delete processing time: string
Action: None
NNL-00834: Slowest delete processing time: string
Action: None
NNL-00835: Average delete processing time: string
Action: None
NNL-00836: Total delete processing time: string
Action: None
NNL-00850: Rename requests received: number
Action: None
NNL-00851: Renames refused, name is not a leaf name: number
Action: None
NNL-00852: Renames refused, name is a topology name: number
Action: None
NNL-00853: Renames refused, new name already exists: number
Action: None
NNL-00001 to NNL-01078 48-25
NNL-00854: Fastest rename processing time: string

Action: None
NNL-00855: Slowest rename processing time: string
Action: None
NNL-00856: Average rename processing time: string
Action: None
NNL-00857: Total rename processing time: string
Action: None
NNL-00870: Update requests received: number
Action: None
NNL-00871: Updates refused, name is a topology name: number
Action: None
NNL-00872: Updates refused, data is topology data: number
Action: None
NNL-00873: Fastest update processing time: string
Action: None
NNL-00874: Slowest update processing time: string
Action: None
NNL-00875: Average update processing time: string
Action: None
NNL-00876: Total update processing time: string
Action: None
NNL-00890: Messages received: number
Action: None
NNL-00891: Corrupted messages received: number
Action: None
NNL-00892: Duplicate requests received: number
Action: None
NNL-00893: Similar requests received: number
Action: None
NNL-00894: Requests refused, permission denied: number
Action: None
NNL-00895: Requests refused, processing disabled: number
Action: None
NNL-00896: Requests refused, modifications disabled: number
Action: None
NNL-00897: Messages sent: number
Action: None
NNL-00898: Responses sent: number
Action: None
NNL-00899: OK responses sent: number
Action: None
NNL-00900: NO SUCH NAME responses sent: number
Action: None
NNL-00901: CONTENT ERROR responses sent: number
Action: None
NNL-00902: ALIAS LOOP responses sent: number
Action: None
NNL-00903: SERVER FAILURE responses sent: number
Action: None
NNL-00001 to NNL-01078 48-27
NNL-00904: NAME EXISTS responses sent: number

Action: None
NNL-00905: NOT AUTHORITY responses sent: number
Action: None
NNL-00906: NOT A LEAF NAME responses sent: number
Action: None
NNL-00907: NOT ALLOWED responses sent: number
Action: None
NNL-00908: UNKNOWN TYPE responses sent: number
Action: None
NNL-00909: META VIOLATION responses sent: number
Action: None
NNL-00910: VERSION SKEW responses sent: number
Action: None
NNL-00911: Responses sent with invalid error code: number
Action: None
NNL-00912: Alias loops detected: number
Action: None
NNL-00913: Server-generated requests sent: number
Action: None
NNL-00914: Forwarding desired on server queries: string
Action: None
NNL-00915: Authority required on server queries: string
Action: None
NNL-00916: Modification requests enabled: string
Action: None
NNL-00917: Artificial request processing delay: string
Action: None
NNL-00918: Time until server restart: string
Action: None
NNL-00919: Time until server shutdown: string
Action: None
NNL-00920: Time until next config save: string
Action: None
NNL-00930: Requests refused, unknown data type: number
Action: None
NNL-00931: Requests refused, no cached meta-data: number
Action: None
NNL-00932: Requests refused, type syntax mismatch: number
Action: None
NNL-00933: Requests refused, OTHER-DATA violation: number
Action: None
NNL-00934: Requests refused, ALIAS-EXISTS violation: number
Action: None
NNL-00935: Requests refused, SINGLE-VALUE violation: number
Action: None
NNL-00936: Requests refused, DATA-EXISTS violation: number
Action: None
NNL-00950: Cache lookup requests: number
Action: None
NNL-00001 to NNL-01078 48-29
NNL-00951: Names created on lookup: number

Action: None
NNL-00952: Cache lookup failures: number
Action: None
NNL-00953: Cache lookup exact matches: number
Action: None
NNL-00954: Hash tables created: number
Action: None
NNL-00955: Hash tables enlarged: number
Action: None
NNL-00956: Hash tables freed: number
Action: None
NNL-00957: Name nodes created: number
Action: None
NNL-00958: Name nodes freed: number
Action: None
NNL-00959: Time until cache dump to trace file: string
Action: None
NNL-00960: Time until cache flush: string
Action: None
NNL-00961: Cache checkpoints: number
Action: None
NNL-00962: Cache checkpoint failures: number
Action: None
NNL-00963: Timeouts, name TTL expired: number
Action: None
NNL-00970: System query index number: number
Action: None
NNL-00971: Query ID: number
Action: None
NNL-00972: Query next issued in: string
Action: None
NNL-00973: Query state: number
Action: None
Action: None
NNL-00975: Desired data type: string
Action: None
NNL-00980: Forwarding failures: number
Action: None
NNL-00981: Timeouts, server not responding: number
Action: None
NNL-00982: Not forwarded, no servers found: number
Action: None
NNL-00983: Name-to-hint translations: number
Action: None
NNL-00984: Name-to-hint translations failed: number
Action: None
NNL-00985: Requests reforwarded using referrals: number
Action: None
NNL-00001 to NNL-01078 48-31
NNL-00986: Reforwarded requests expired: number

Action: None
NNL-00987: Authoritative answers when authority: number
Action: None
NNL-00988: Non-authoritative NACKs received: number
Action: None
NNL-00989: Objects received with no TTL: number
Action: None
NNL-00990: DEFAULT-FORWARDERS-ONLY mode: string
Action: None
NNL-00991: Maximum number of reforwards per request: number
Action: None
NNL-00992: Auto-refresh failure retry interval: string
Action: None
NNL-00993: Auto-refresh failure retry expiration: string
Action: None
NNL-00994: Responses received: number
Action: None
NNL-00995: Unmatched responses received: number
Action: None
NNL-00996: OK responses received: number
Action: None
NNL-00997: NO SUCH NAME responses received: number
Action: None
NNL-00998: CONTENT ERROR responses received: number
Action: None
NNL-00999: ALIAS LOOP responses received: number
Action: None
NNL-01000: SERVER FAILURE responses received: number
Action: None
NNL-01001: NAME EXISTS responses received: number
Action: None
NNL-01002: NOT AUTHORITY responses received: number
Action: None
NNL-01003: NON LEAF responses received: number
Action: None
NNL-01004: NOT ALLOWED responses received: number
Action: None
NNL-01005: UNKNOWN TYPE responses received: number
Action: None
NNL-01006: META VIOLATION responses received: number
Action: None
NNL-01007: VERSION SKEW responses received: number
Action: None
NNL-01008: Outbound message contexts allocated: number
Action: None
NNL-01009: Outbound message contexts freed: number
Action: None
NNL-01010: Forwarding contexts allocated: number
Action: None
NNL-00001 to NNL-01078 48-33
NNL-01011: Forwarding contexts freed: number

Action: None
NNL-01030: Domain index number: number
Action: None
Action: None
NNL-01032: Minimum TTL: string
Action: None
NNL-01040: Data streams opened by server: number
Action: None
NNL-01041: Data stream open failures: number
Action: None
NNL-01042: Data streams answered by server: number
Action: None
NNL-01043: Data stream answer failures: number
Action: None
NNL-01044: Errors reading data stream: number
Action: None
NNL-01045: Errors writing data stream: number
Action: None
NNL-01050: Version banner is "string"\n
Action: None
NNL-01051: Server name: string
Action: None
NNL-01052: Server has been running for: string
Action: None
NNL-01053: Request processing enabled: string
Action: None
NNL-01054: Request forwarding enabled: string
Action: None
NNL-01055: Requests received: number
Action: None
NNL-01056: Requests forwarded: number
Action: None
NNL-01057: Foreign data items cached: number
Action: None
NNL-01058: Region data next checked for reload in: string
Action: None
NNL-01059: Region data reload check failures: number
Action: None
NNL-01060: Cache next checkpointed in: string
Action: None
NNL-01061: Cache checkpoint interval: string
Action: None
NNL-01062: Cache checkpoint file name: string
Action: None
NNL-01063: Statistic counters next reset in: string
Action: None
NNL-01064: Statistic counter reset interval: string
Action: None
NNL-00001 to NNL-01078 48-35
NNL-01065: Statistic counters next logged in: string

Action: None
NNL-01066: Statistic counter logging interval: string
Action: None
NNL-01067: Trace level: number
Action: None
NNL-01068: Trace file name: string
Action: None
NNL-01069: Log file name: string
Action: None
NNL-01070: System parameter file name: string
Action: None
NNL-01071: Command-line parameter file name: string
Action: None
NNL-01072: Administrative region name: string
Action: None
NNL-01073: Administrative region description: string
Action: None
NNL-01074: ApplTable Index: number
Action: None
NNL-01075: Contact string
Action: None
NNL-01076: Operational Status number
Action: None
NNL-01077: Save Config on Stop string
Action: None
NNL-01078: Access/Create File Error : string
Cause: Failed to access/create named file or its backup File due to incorrect
permissions
Action: Provide correct access to file.
NNL-00001 to NNL-01078 48-37
49
NNO-00050 to NNO-00854
NNO-00050: serious errors in configuration data, server cannot run
Cause: The server's configuration data has a problem of some sort which prevents the
server from starting.
Action: Previous error messages in the log file will specify the exact problems leading
to the shutdown. The problem most frequently occurs when the network is broken up
into multiple administrative regions and the delegation points are incorrect. Read the
Oracle Names documentation sections on region delegation and ensure that their
directions are being followed correctly.
NNO-00051: domain count number exceeds maximum of number, first number will
be loaded
Cause: The server's configuration contains more domains than the server can support.
Customer Support.
NNO-00052: invalid domain description list
Cause: The server's configuration contains an invalid domain description list.
Customer Support.
NNO-00053: duplicate domain description for domain "string"
Cause: The server's configuration contains duplicate domain descriptions in the
domain description list.
Customer Support.
NNO-00054: invalid domain name "string"
Cause: The server's configuration contains a domain description with an invalid
name.
Customer Support.
NNO-00055: invalid domain minimum TTL "string"
minimum TTL.
Customer Support.
NNO-00050 to NNO-00854 49-1
NNO-00056: warning: domain minimum TTL must be between number and number,
set to number seconds
minimum TTL. This error is not fatal; the server will automatically set the TTL to a
default value which is suitable for most uses.
Customer Support.
NNO-00057: loading and verifying topology data
Cause: An informational message written to the log file during normal server startup.
Action: None
NNO-00058: cannot load topology data from configuration database
Cause: An error was encountered while trying to load the server's topology data from
the configuration database. If more information is available, it will appear under this
error. This error will cause the server to shut down.
Action: Make sure that the database is running, that its name and password as
specified in the Oracle Network Manager are accurate, and that there is SQL*Net
connectivity between the Oracle Names server and the database. To force the server
to start up anyway, using its checkpoint data, start the server with the
names.no_region_database parameter set to TRUE. If no checkpoint data is available,
the server will shut down.
NNO-00059: cannot construct topology checkpoint file name
Cause: the server could not construct a system-dependent file name.
Action: An internal error not normally visible to the user. For further details, turn on
tracing and restart the server. If the error persists, contact Worldwide Customer
Support.
NNO-00060: loading server topology from checkpoint file "string"
Cause: An informational message written to the log file when the server has been
forced to load from its most recent topology checkpoint file, by setting the
names.no_region_database parameter to TRUE.
Action: None
NNO-00061: loading data for domain "string"
Action: None
NNO-00062: cannot load domain data from configuration database
Cause: An error was encountered while trying to load the server's domain data from
NNO-00063: cannot construct domain checkpoint file name
49-2 Error Messages
Support.
NNO-00064: loading domain data from checkpoint file "string"
forced to load from its most recent domain checkpoint file, by setting the
Action: None
NNO-00065: loading cached data from checkpoint file "string"
Action: None
NNO-00066: server will perform reload check of administrative region in number
seconds
Cause: An informational message written to the log file whenever the Oracle Network
Manager or the Oracle Names control program send a reload request to the server.
Action: None
NNO-00067: server reload check countdown aborted
Cause: An informational message written to the log file whenever the Oracle Names
control program halts a reload request previously sent to the server
Action: None
NNO-00068: warning: administrative region check failed, next check in number
seconds
Cause: this warning is issued whenever the server fails to connect to the configuration
database to see if any configuration data has changed. The server will automatically
begin reissuing reload checks more frequently, and will eventually give up if
connections fail continuously for three days.
connectivity between the Oracle Names server and the database.
NNO-00069: warning: too many administrative region check failures, checking
disabled
Cause: a warning issued whenever the server has continuously failed for three days
in its attempts to connect to the configuration database. The server disables reload
checking. Reload checking can later be re-enabled from the Oracle Network Manager
or the Oracle Names control program.
NNO-00070: administrative region has changed, reloading domain data
Cause: An informational message written to the log file whenever the server's
configuration has changed, and the server is reloading the new configuration from
the configuration database.
Action: None
NNO-00050 to NNO-00854 49-3
NNO-00071: cannot construct cache checkpoint file name

Support.
NNO-00072: loading from region database
Cause: normal
Support.
NNO-00073: loading server config from region database
Action: None
NNO-00074: downloading region from server string
Action: None
NNO-00080: domain "string" cannot be delegated because its parent is already
delegated
Cause: an internal delegation error has occurred. Delegation is controlled by the
Oracle Network Manager, which enforces correct delegation rules.
Customer Support.
NNO-00081: domain "string" has no name servers
Cause: an internal configuration error has occurred. The Oracle Network Manager is
responsible for configuring Oracle Names servers correctly.
Customer Support.
NNO-00082: domain "string" is missing my name "string" as a name server
Customer Support.
NNO-00083: domain "string" server "string" has no addresses
Customer Support.
NNO-00084: domain "string" is not in the authoritative domain list
Customer Support.
49-4 Error Messages
NNO-00104: line string: syntax error, data ignored

Cause: the server found a syntax error its domain data. This message will also appear
if the server's internal checkpoint files become corrupted. The record in question is
not loaded, but the server continues to load data.
Customer Support.
NNO-00105: line string: invalid name "string", data ignored
Cause: the server found an invalid global name in its domain data. The record in
question is not loaded, but the server continues to load data.
Customer Support.
NNO-00106: line string: invalid TTL "string", data ignored
Cause: the server found an invalid TTL in its domain data. The record in question is
Customer Support.
NNO-00107: line string: ignoring stale checkpoint data
Cause: an informational message which appears during server startup when the
server detects out-of-date cached data in its cache checkpoint file. The message is part
of normal server startup.
Action: None
NNO-00108: line number: TTL of number seconds below domain minimum number,
using minimum
Cause: the server found an invalid TTL value in its domain data. The record in
Customer Support.
NNO-00109: line string: invalid data type name "string", data ignored
Cause: the server found an invalid data type name in its domain data. The record in
Customer Support.
NNO-00110: line string: unknown data type "string", data ignored
Cause: the server found an unknown data type in its domain data. The record in
Customer Support.
NNO-00111: line string: data type "string" has syntax "string", should be "string",
data ignored
Cause: the server found an invalid data type syntax in its domain data. The record in
Customer Support.
NNO-00050 to NNO-00854 49-5
NNO-00112: line string: ignored duplicate data of type "string"

Cause: the server found a duplicate record in its domain data. The record in question
is not loaded, but the server continues to load data.
Customer Support.
NNO-00113: line string: alias data already exists, all other data ignored
Cause: the server found a alias and non-alias data with the same global name in its
domain data. The record in question is not loaded, but the server continues to load
data.
Customer Support.
NNO-00114: line string: other data exists, alias data ignored
Cause: the server found a alias and non-alias data with the same global name in its
domain data. The record in question is not loaded, but the server continues to load
data.
Customer Support.
NNO-00115: line string: single-value data type "string", other instances ignored
Cause: the server found more than one record with the same name and type, when
the type allows only a single record with a particular name. The record in question is
Customer Support.
NNO-00116: warning: data type "string" in string load
Cause: the server found a record with an invalid data type in its domain data.
Action: No action required; adjustments to data will eliminate warning.
NNO-00117: line string: missing data type, data ignored
Cause: the server found a record with a missing data type in its domain data. The
record in question is not loaded, but the server continues to load data.
Customer Support.
NNO-00118: line string: data length string exceeds maximum of string, data ignored
Cause: the server found a record whose length exceeds an internal limit. The record in
Customer Support.
NNO-00119: line string: server not authoritative for name "string", data ignored
Cause: the server found a global name in its domain data for which it is not
authoritative. The record in question is not loaded, but the server continues to load
data.
Customer Support.
49-6 Error Messages
NNO-00120: line string: topology name "string" not allowed here

Cause: the server found an invalid record in its domain data. The record in question is
Customer Support.
NNO-00121: LDIF file string open failed: error = number
Cause: the server found an invalid record in its domain data. The record in question is
Customer Support.
NNO-00122: invalid name, data ignored: entry:\nstring
Cause: the server found an invalid global name in its domain data. The record in
Customer Support.
NNO-00123: node "string" has no authoritative parent, data ignored
Cause: an object in the domain data is apparently not in the domain(s) which the
server is authoritative for. The record in question is not loaded, but the server
continues to load data.
Action: Check for inconsistencies in the data and correct any errors in topology
definition or domain data outside of authoritative domains.
NNO-00150: warning: invalid hint list, no hints loaded
Cause: The server's configuration contains an invalid hint description list. The server
will continue to run, but will not load any hints.
Customer Support.
NNO-00151: warning: ignoring hint for domain "string", server is authoritative
Cause: the server's configuration contained a hint for a domain in the server's
administrative region. The hint is ignored and the server continues to run.
Customer Support.
NNO-00152: warning: hint count number exceeds maximum of number, first number
will be loaded
Cause: There are too many hints in the server's hint list. The server will load a
specified maximum number of hints, ignore the rest, and continue running.
Customer Support.
NNO-00153: warning: hint domain number has invalid name "string", hint domain
ignored
Cause: The server's configuration contains a hont domain with an invalid name. The
domain is ignored and the server continues to run.
Customer Support.
NNO-00050 to NNO-00854 49-7
NNO-00154: warning: hint number has invalid server name "string", hint ignored
Cause: The server's configuration contains a hint with an invalid server name. The
hint is ignored and the server continues to run.
Customer Support.
NNO-00155: warning: hint number has missing address, hint ignored
Cause: The server's configuration contains a hint with no server address. The hint is
ignored and the server continues to run.
Customer Support.
NNO-00156: warning: hint number address length number exceeds maximum of
number, hint ignored
Cause: The server's configuration contains a hint whose address length exceeds an
internal limit. The hint is ignored and the server continues to run.
Customer Support.
NNO-00157: warning: hint number has invalid address, hint ignored
Cause: The server's configuration contains a hint with an invalid address. The hint is
ignored and the server continues to run.
Customer Support.
NNO-00158: warning: hint domain count number exceeds maximum of number, first
number will be loaded
Cause: The server's hint domain list is too long. The server will load a specified
maximum number of hint domains, ignore the rest, and continue running.
Customer Support.
NNO-00159: warning: ignoring duplicate hint domain number name "string"
Cause: The server's hint domain list contains a duplicate domain. The duplicate is
ignored and the server continues running.
Customer Support.
NNO-00160: warning: ignoring duplicate hint server "string"
Cause: The server's hint server list contains a duplicate server. The duplicate is
Customer Support.
NNO-00250: invalid administrative region description
Cause: The server encountered an invalid administrative region description during
startup. This error will prevent the server from starting. The administrative region
description is stored in the server's names.ora configuration file.
Action: Make sure that the names.admin_region parameter in names.ora is correct.
The names.ora file is automatically generated by the Oracle Network Manager, but
administrators can edit the file at any time, introducing errors. If the file was never
changed, contact Worldwide Customer Support.
49-8 Error Messages
NNO-00251: missing administrative region parameter string

Cause: The server's administrative region description is missing a required parameter.
This error will prevent the server from starting. The administrative region description
is stored in the server's names.ora configuration file.
NNO-00252: invalid administrative region parameter string value "string"
Cause: The server encountered an invalid administrative region parameter. This error
will prevent the server from starting. The administrative region description is stored
in the server's names.ora configuration file.
NNO-00253: administrative region parameter string length string exceeds maximum
of string
Cause: The server encountered an administrative region parameter whose length
exceeds an internal limit. This error will prevent the server from starting. The
administrative region description is stored in the server's names.ora configuration
file.
NNO-00254: warning: parameter string value must be between number and number,
set to number seconds
Cause: The server encountered an administrative region parameter with an invalid
value. The value is set to a default suitable for most applications, and the server
continues running. The administrative region description is stored in the server's
names.ora configuration file.
NNO-00255: cannot initialize ROS
Cause: The server was unable to initialize ROS during startup. The error prevents the
server from running.
Customer Support.
NNO-00256: using administrative region "string"
Cause: an informational message which appears during server startup, and notes the
name of the administrative region for future diagnostic use by administrators. The
message is part of normal server startup.
Action: None
NNO-00050 to NNO-00854 49-9
NNO-00257: warning: cannot get serial number from region store

Cause: The server encountered an error while trying to get the configuration
database's serial number. The error occurs almost always because time the server is
unable to access the configuration database. If the error occurs during server startup,
the server will shut down. If the error occurs during server operation (the server
checks the serial number periodically to see if it should reload itself), then the server
assumes a transient failure has occurred and repeats the operation a short while later.
If the repetitions continue to fail for three days, the server will log another error and
stop issuing the serial number load operation.
Action: First make sure that the Netadmin program has exported a server
configuration for this name server. Next, make sure that the database is running, that
its name and password as specified in the Oracle Network Manager are accurate, and
that there is SQL*Net connectivity between the Oracle Names server and the
database. If the error occurs during server startup, you can force startup anyway,
with checkpoint data, by starting the server with the names.no_region_database
parameter set to TRUE. If no checkpoint data is available, the server will shut down.
NNO-00258: cannot load configuration from configuration database
Cause: An error was encountered while trying to load the server's configuration from
NNO-00259: configuration tables have not been installed or are inaccessible
Cause: The configuration database has not been properly installed.
Action: Make sure the Oracle Network Manager and its database have been properly
installed
NNO-00260: loading configuration data from checkpoint file "string"
forced to load from its most recent configuration checkpoint file, by setting the
Action: None
NNO-00261: cannot construct configuration checkpoint file name
Support.
NNO-00262: warning: cannot write checkpoint file "string"
Cause: the server was unable to write the named checkpoint file. This problem is
typically due to the file system's protection settings. The error is not fatal; it simply
means the server will not create any checkpoint data. Note, however, that if the
configuration database is ever unavailable during a future server startup, the lack of
checkpoint data means you will be unable to force a startup from checkpoint data
with the names.no_region_database parameter.
Action: Check to see that the server has permission to write the file named in the error
message.
NNO-00263: error from configuration database
Cause: the server encountered an error while accessing the configuration database.
The error can occur when the database is unavailable, or SQL*Net connectivity to the
database is interrupted.
NNO-00264: configuration database query returned no data
Cause: the server attempted to fetch data from the configuration database and no data
was found.
Action: The error generally appears underneath a more specific error which will tell
you the exact nature of the problem.
NNO-00265: warning: cannot load data from checkpoint file
Cause: the server was started using checkpoint data, and was unable to read that
data. The remaining errors below this one on the error stack provide more specific
information about the problem.
Action: Check to see that the named file exists and that the server has permission to
read it.
NNO-00266: cannot find document "string" in configuration database
Cause: The server encountered an error while trying to get its configuration ID from
the configuration database. The error can occur any time the server is unable to access
the configuration database. This error will cause the server to shut down.
NNO-00267: warning: configuration database contains no data for server "string"
Cause: the server successfully contacted the configuration database, but was unable to
find any configuration information associated with the server's name. The name is
specified in the server's names.ora configuration file. The error occurs almost always
because the server configuration has not been exported from the Netadmin program.
Action: Make sure that the Netadmin program has exported a server configuration for
this name server.
NNO-00268: warning: configuration database is not used, using checkpoint data
instead
Cause: An informational message indicating that the server has been started with the
names.no_region_database parameter set to TRUE, and that it will use checkpoint
data rather than attempting to contact the configuration database.
Action: None
NNO-00050 to NNO-00854 49-11
NNO-00269: configuration database is version string, server requires at least

version string
Cause: The server cannot use the specified configuration database because it is of an
incorrect version.
Action: Run the document conversion utility supplied with the Network Manager
and re-export your network. The conversion utility will upgrade old documents to a
version which can be understood by the name server.
NNO-00270: ORACLE error string
Cause: An ORACLE error was encountered while accessing the configuration
database. The error can occur when the database is unavailable, or SQL*Net
connectivity to the database is interrupted.
NNO-00271: warning: names.ora region is version string, network definition is
version string
Cause: The region description in names.ora is out of synch with the network
definition.
Action: No action is required unless the name server cannot run with the network
definition. To be safe names.ora should be updated with one which is consistent with
the network definition.
NNO-00272: line string; invalid DIT/DN
Cause: There is a syntax error in the DIT/DN provided in the region description.
Action: Correct the error and restart the server.
NNO-00300: no listen addresses specified, at least one is required
Cause: the server's configuration is missing addresses on which to listen.
Customer Support.
NNO-00301: server will shut down in number seconds
Cause: An informational message written to the log file when the server receives a
shutdown request from the Oracle Names control program.
Action: None
NNO-00302: server stopped
Cause: An informational message written to the log file when the server shuts down.
Action: None
NNO-00303: server "string" started with process ID number
Cause: An informational message written to the log file when the server successfully
starts up.
Action: None
NNO-00304: listen address string length string exceeds maximum of string

Cause: the length of one of the server's listen addresses exceeds an internal limit.
Customer Support.
NNO-00305: trace level changed from number to number
Cause: An informational message written to the log file when the server changes its
trace level in response to a request from the Oracle Names control program.
Action: None
NNO-00306: server shutdown countdown aborted
control program halts a shutdown request previously sent to the server
Action: None
NNO-00307: invalid server name "string"
Cause: the server's name is invalid. The name is specified in the server's names.ora
configuration file.
Action: Make sure that the names.server_name parameter in names.ora is correct. The
names.ora file is automatically generated by the Oracle Network Manager, but
NNO-00308: server will restart in number seconds
Cause: An informational message written to the log file when the server receives a
restart request from the Oracle Names control program.
Action: None
NNO-00309: server restarting
Cause: An informational message written to the log file when the server restarts.
Action: None
NNO-00310: server restart countdown aborted
control program halts a restart request previously sent to the server
Action: None
NNO-00311: invalid listen address list
Cause: the server's configuration contains an invalid listen address list.
Customer Support.
NNO-00312: listen address string is invalid
Cause: the server's configuration contains an invalid listen address.
Customer Support.
NNO-00313: server password length string exceeds maximum of string
Cause: the server's password length exceeds an internal limit.
Customer Support.
NNO-00050 to NNO-00854 49-13
NNO-00314: error changing trace level from number to number, level change
ignored
Cause: the server encountered an error while changing its trace level in response to a
request from the Oracle Names control program.
Support.
NNO-00315: server is listening on address string
Cause: An informational message written to the log file during server startup.
Action: None
NNO-00316: statistic counter reset disabled
Cause: An informational message written to the log file when the server disables
statistic counter resetting in response to a request from the Oracle Names control
program.
Action: None
NNO-00317: statistic counter reset interval changed to number seconds
statistic counter reset interval in response to a request from the Oracle Names control
program.
Action: None
NNO-00318: overriding next statistic counter reset, resetting in number seconds
Cause: An informational message written to the log file when the server resets its
statistic counters in response to a request from the Oracle Names control program.
Action: None
NNO-00320: missing server name parameter
Cause: the server could not find a names.server_name parameter. The name is
specified in the server's names.ora configuration file.
Action: Make sure that the names.server_name parameter in names.ora is correct. The
names.ora file is automatically generated by the Oracle Network Manager, but
NNO-00321: statistic counter dump disabled
statistics dumping in response to a request from the Oracle Names control program.
Action: None
NNO-00322: statistic counter dump interval changed to number seconds
statistic dump interval in response to a request from the Oracle Names control
program.
Action: None
NNO-00323: overriding next statistic counter dump, dumping in number seconds
Cause: An informational message written to the log file when the server dumps its
statistic counters in response to a request from the Oracle Names control program.
Action: None
NNO-00326: server statistic counter dump follows
Cause: An informational message written to the log file at the beginning of a statistic
dump. The message is followed by a set of server statistics, and ends with another
informational message indicating the dump has finished.
Action: None
NNO-00327: server statistic counter dump ends
Cause: An informational message written to the log file at the end of a statistic dump.
The message is preceded by a set of server statistics.
Action: None
NNO-00328: server has reset statistic counters to zero
Cause: An informational message written to the log file when the server resets its
statistic counters to zero in response to a request from the Oracle Names control
program.
Action: None
NNO-00329: server will save the config file in number seconds
Cause: An informational message written to the log file when the server saves the
config to config file in response to a request from the Oracle Names control program.
Action: None
NNO-00330: server saved the config file "string".
Cause: An informational message written to the log file when the server saves the
config to config file in response to a request from the Oracle Names control program.
Action: None
NNO-00331: error saving new value string of string to the save config table.
Cause: An informational message written to the log file when the a set operation is
performed and the change cannot be saved in the save config ptable, but should be.
Action: None
NNO-00332: warning: region store serial number reduced from number to number
Cause: An informational message written to the log file when the server finds the
region database has its serial number set lower than it was when the server
previously loaded the region data. This is an unnatural condition- every update to the
region should increment the serial number so a reduction of the serial number might
reflect tampering or accidental manual alteration this and possibly other region
tables.
Action: Administrators should find out how/why the serial number decreased.
NNO-00333: warning: ROS admin_region types obsolete; using SQL
Cause: the value set in names.admin_region is an obsolete ROS type
Action: No action is necessary; administrators should set the value to the correct typeprobably SQL, possibly LDAP or LDIF
NNO-00334: region load failure: ROS admin_region type number unsupported
Cause: the value set in names.admin_region is an obsolete ROS type
Action: No action is necessary; administrators should set the value to the correct typeprobably SQL, possibly LDAP or LDIF
NNO-00050 to NNO-00854 49-15
NNO-00600: warning: forwarder count number exceeds maximum of number, first

number will be loaded
Cause: the server's configuration contains too many default forwarders. The server
loads a specified maximum number of forwarders, ignores the rest, and continues
running.
Customer Support.
NNO-00601: warning: no forwarders, DEFAULT-FORWARDERS-ONLY mode
ignored
Cause: the server's configuration enables DEFAULT-FORWARDERS-ONLY mode but
the configuration contains no default forwarders. The server ignores the request and
continues running.
Customer Support.
NNO-00602: warning: forwarder number has invalid address, forwarder ignored
Cause: One of the forwarders in the default forwarder list has an invalid address. The
forwarder definition is ignored and the server continues running.
Customer Support.
NNO-00603: enabling all request processing
Cause: An informational message written to the log file when the server enables
request processing in response to a request from the Oracle Names control program.
Action: None
NNO-00604: disabling all request processing
request processing in response to a request from the Oracle Names control program.
Action: None
NNO-00605: enabling modification requests
modification-request processing in response to a request from the Oracle Names
control program.
Action: None
NNO-00606: disabling modification requests
modification-request processing in response to a request from the Oracle Names
control program.
Action: None
NNO-00607: server will forward to default forwarders only
Cause: An informational message written to the log file when the server's
configuration enables DEFAULT-FORWARDERS-ONLY mode.
Action: None
NNO-00608: received corrupted message
Cause: The server received a corrupted request. The request is ignored.
Action: corrupted requests are usually caused by transient network problems. If

many corrupted messages are received, turn on tracing for further information. If the
errors persist, contact Worldwide Customer Support.
NNO-00609: warning: forwarder number address length number exceeds maximum
of number, ignored
Cause: the server's configuration contains a forwarder address whose length exceeds
an internal limit.
Customer Support.
NNO-00610: detected possible alias loop involving name "string"
Cause: the server detected an alias loop involving the specified name. An alias loop
occurs when an alias "X" points to another alias "Y", which points back to "X" rather
than to an address or other name server data. The loop can contain more hops but the
basic idea remains the same. Loops occur when administrators mis-enter network
data, particularly when an alias in one administrative region points to data in another
administrative region.
Action: Use the Oracle Names control program to query for the specified name. The
control program will describe the alias path, and you can use that information to find
which names are incorrect and what administrative regions the incorrect data belongs
to.
NNO-00611: disabling request forwarding
request forwarding in response to a request from the Oracle Names control program.
Action: None
NNO-00612: enabling request forwarding
request forwarding in response to a request from the Oracle Names control program.
Action: None
NNO-00613: disabling FORWARDING-DESIRED on system queries
Cause: An informational message written to the log file when the server disables the
FORWARDING-DESIRED attribute on queries that it generates. The message comes
in response to a request from the Oracle Names control program.
Action: None
NNO-00614: enabling FORWARDING-DESIRED on system queries
Cause: An informational message written to the log file when the server enables the
FORWARDING-DESIRED attribute on queries that it generates. The message comes
Action: None
NNO-00615: disabling DEFAULT-FORWARDERS-ONLY mode
DEFAULT-FORWARDERS-ONLY mode in response to a request from the Oracle
Names control program.
Action: None
NNO-00050 to NNO-00854 49-17
NNO-00616: enabling DEFAULT-FORWARDERS-ONLY mode

DEFAULT-FORWARDERS-ONLY mode in response to a request from the Oracle
Names control program.
Action: None
NNO-00617: enabling AUTHORITY-REQUIRED on system queries
Cause: An informational message written to the log file when the server enables the
AUTHORITY-REQUIRED attribute on queries that it generates. The message comes
Action: None
NNO-00618: disabling AUTHORITY-REQUIRED on system queries
Cause: An informational message written to the log file when the server disables the
AUTHORITY-REQUIRED attribute on queries that it generates. The message comes
Action: None
NNO-00622: warning: too many auto-refresh failures for name "string", query
expired
Cause: If an auto-refresh query is issued and continuously returns an error for three
days, the query is removed from the auto-refresh queue and a warning logged. The
query can be restarted from the Oracle Names control program.
Action: this message will be preceded by numerous warnings that the query in
question is failing. Use the Oracle Names control program to describe the failing
query. Make sure the server being queried is running and that there is network
connectivity between the querying server and the server being queried.
NNO-00623: setting auto-refresh retry interval to number seconds
auto-refresh retry interval in response to a request from the Oracle Names control
program.
Action: None
NNO-00624: setting auto-refresh expiration period to number seconds
auto-refresh expiration period in response to a request from the Oracle Names control
program.
Action: None
NNO-00625: overriding auto-refresh of name "string", type "string", refresh in
number seconds
Cause: An informational message written to the log file when the server changes the
time when an auto-refresh query is next issued. The message comes in response to a
request from the Oracle Names control program.
Action: None
NNO-00626: cannot enable DEFAULT-FORWARDERS-ONLY mode, no default
forwarders exist
Cause: the Oracle Names control program issued a request to enable DEFAULTFORWARDERS-ONLY mode, and the request was ignored because the server has no
default forwarders.
Action: None
NNO-00627: cancelling auto-refresh of name "string", type "string"
Cause: An informational message written to the log file when the server removes a
query from the auto-refresh queue in response to a request from the Oracle Names
control program.
Action: None
NNO-00628: setting maximum reforwards per query to number
maximum-reforward count in response to a request from the Oracle Names control
program.
Action: None
NNO-00629: warning: invalid forwarder list, no default forwarders loaded
Cause: The server's configuration contains an invalid forwarder description list.
Customer Support.
NNO-00630: setting request-processing delay to number seconds
Cause: An informational message written to the log file when the server sets an
artificial request-processing delay in response to a request from the Oracle Names
control program.
Action: None
NNO-00631: warning: forwarder number has invalid name "string", forwarder
ignored
Cause: The server's configuration contains a forwarder description with an invalid
server name.
Customer Support.
NNO-00632: warning: forwarder number has missing address, forwarder ignored
Cause: The server's configuration contains a forwarder description with a missing
address.
Customer Support.
NNO-00633: detected fatal delegation loop involving server "string"
Cause: the server detected a fatal delegation loop while forwarding a request. A loop
occurs when the server's topology data indicates that it should forward a request to
itself. The server immediately shuts down in response to this error.
Support.
NNO-00634: received authoritative name "string" when we are its authority
Cause: a server "X" received authoritative data from another server "Y" when server
"X" is also authoritative for the data. Such situations should never arise because if
server "X" is authoritative for the requested data, it should never forward the request
to another server.
NNO-00050 to NNO-00854 49-19
Support.
NNO-00635: warning: ignoring duplicate forwarder "string"
Cause: The server's default forwarder list contains a duplicate server. The duplicate is
Customer Support.
NNO-00700: warning: cannot checkpoint the cache, trying again in number seconds
Cause: The server was unable to perform its normal periodic cache checkpointing,
typically because the cache checkpoint file could not be written. The cache checkpoint
file name appears as an informational message during server startup.
Action: Check to see that the server has permission to write the cache checkpoint file,
and that there is sufficient disk space for the file to be written.
NNO-00701: warning: cannot construct checkpoint file name, checkpointing
disabled
Support.
NNO-00702: cache checkpointing disabled
cache checkpointing in response to a request from the Oracle Names control program.
Action: None
NNO-00703: checkpoint interval changed to number seconds
cache checkpoint interval in response to a request from the Oracle Names control
program.
Action: None
NNO-00705: warning: cannot open checkpoint file "string", checkpointing disabled
Cause: the server was unable to open the named checkpoint file for writing. This
problem is typically due to the file system's protection settings. The error is not fatal;
it simply means the server will not checkpoint its cache.
Action: Check to see that the server has permission to write the file named in the error
message.
NNO-00706: overriding next cache checkpoint, checking in number seconds
Cause: An informational message written to the log file when the server checkpoints
its cache in response to a request from the Oracle Names control program.
Action: None
NNO-00707: server's cache will be flushed in number seconds
Cause: An informational message written to the log file when the server flushes its
cache in response to a request from the Oracle Names control program.
Action: None
NNO-00708: cache flush countdown aborted

control program halts a cache flush request previously sent to the server
Action: None
NNO-00709: failed delete of cache checkpoint file "string", cache flush may not
work
Cause: the server attempted to flush its cache, which also deletes the cache checkpoint
file. The file deletion failed, although the rest of the cache flush succeeded.
Succeeding errors describe the reason for the deletion failure.
Action: This error typically occurs when two cache-flush operations are issued in
succession without an intervening cache checkpoint operation (which would recreate
the file). The first deletes the cache file, the second attempts to do so, but fails since
the file has already been deleted. In such cases, the message is harmless and can be
ignored. If, however, the error occurs because the server lacks permission to delete
the file, then you must change the file system permissions so the server is allowed to
delete the file.
NNO-00710: server's cache will be dumped to the trace file in number seconds
Cause: An informational message written to the log file when the server dumps its
cache to the trace file in response to a request from the Oracle Names control
program.
Action: None
NNO-00711: cache dump countdown aborted
control program halts a cache dump request previously sent to the server
Action: None
NNO-00712: warning: group string cache checkpoint failed
Cause: The server was unable to perform its normal periodic cache checkpointing,
typically because the cache checkpoint file could not be written. The cache checkpoint
file name appears as an informational message during server startup.
Action: Check to see that the server has permission to write the cache checkpoint file,
and that there is sufficient disk space for the file to be written.
NNO-00800: Error: cannot read version from config database
Cause: The query for the region database version failed. The database may be shut
down, or the tables may not exist in the schema specified in names.ora.
Action: Correct any access problems accordingly.
NNO-00801: Error: OCI_SUCCESS_WITH_INFO: string
Cause: Diagnostic information was returned from OCI during region database access.
Action: None
NNO-00802: Error: OCI_NEED_DATA
Cause: The server did not provide sufficient data to the OCI interface while accesing
the region database.
Customer Support.
NNO-00050 to NNO-00854 49-21
NNO-00803: Error: OCI_INVALID_HANDLE

Cause: The server called OCI with an invalid handle whilc accessing the region
database.
Customer Support.
NNO-00804: Error: OCI_STILL_EXECUTE
Cause: An OCI operation between the server and the database is still in progress.
Action: None
NNO-00805: Error: OCI_CONTINUE
Cause: Not possible.
Action: None
NNO-00806: Error: OCI_ERROR: string
Cause: An OCI occurred accessing the region database. More specific details will be
written to the log file.
Action: Find the appropriate entry in the log file and correct the cause of the failure if
possible. Otherwise contact Worldwide Customer Support.
NNO-00807: End of Fetch: OCI_NO_DATA
Cause: All rows have been returned from the region table.
Action: None
NNO-00808: Error connecting to region database
Action: None
NNO-00809: Unknown OCI error: number
Action: None
NNO-00850: Error: LDAP query returns string
Cause: The LDAP API returned an error. More specific details will be written to the
log file.
Action: Find the appropriate entry in the log file and correct the cause of the failure if
possible. Otherwise contact Worldwide Customer Support.
NNO-00851: LDAP open/bind failed: error = number
Cause: the server failed to connect to the LDAP directory.
Action: Find the cause of the error and correct it and restart the server.
NNO-00852: failed to get LDAP entry: error = number
Cause: the server could not retrieve query entries from the LDAP API.
NNO-00853: failed to get LDAP attribute/value: error = number
NNO-00854: error unbinding LDAP: error = number

NNO-00050 to NNO-00854 49-23
50
NPL-00100 to NPL-00420
NPL-00100: cannot initialize ASN.1 context
Cause: The ASN.1 program interface could not be initialized, probably because its
error message file could not be found.
NPL-00101: uninitialized ASN.1 context
Cause: The ASN.1 program interface received an uninitialized ASN.1 handle.
Support.
NPL-00102: missing stream functions in ASN.1 context initialization
Cause: An internal function imporoperly attempted to initialize an ASN.1 handle.
Support.
NPL-00103: unusable ASN.1 context
Cause: The ASN.1 program interface received an unusable ASN.1 handle.
Support.
NPL-00300: maximum ASN.1 element nesting depth string exceeded on read
Cause: An ASN.1 construct is too complex for the program interface to read.
Support.
NPL-00301: maximum ASN.1 element nesting depth string exceeded on write
Cause: An ASN.1 construct is too complex for the program interface to write.
Support.
NPL-00302: ASN.1 type tag is greater than maximum of 16383
Cause: An internal function attempted to create an illegal ASN.1 construct
Support.
NPL-00100 to NPL-00420 50-1
NPL-00303: uninitialized ASN.1 class attribute

Support.
NPL-00304: uninitialized ASN.1 tag attribute
Support.
NPL-00305: unsupported ASN.1 "UNIV" type string
Support.
NPL-00307: ASN.1 sequence has already been ended on write
Cause: An internal function attempted to end an ASN.1 construct prematurely.
Support.
NPL-00308: requested ASN.1 class string does not match received class string
Cause: An internal function requested an ASN.1 construct different from that
received by the ASN.1 protocol engine.
Support.
NPL-00309: requested ASN.1 type tag string does not match received type tag string
Cause: An internal function requested an ASN.1 construct different from that
received by the ASN.1 protocol engine.
Support.
NPL-00310: ASN.1 sequence has already been ended on read
Cause: An internal function attempted to finish reading an ASN.1 construct which has
already been completely read.
Support.
NPL-00311: cannot end constructed ASN.1 encoding, string encoding octets unread
Cause: An internal function attempted to finish reading an ASN.1 construct
prematurely.
Support.
50-2 Error Messages
NPL-00312: attempt to put ASN.1 "UNIV" type with illegal tag string
Cause: An internal function attempted to create an illegal ASN.1 construct.
Support.
NPL-00313: requested form string does not match actual form string
Cause: An internal function received an ASN.1 construct different from that expected.
Support.
NPL-00410: incoming ASN.1 value too large (string octets) to store locally
Cause: The ASN.1 protocol engine was unable to translate an ASN.1 construct to its
host representation because the construct was too big.
Support.
NPL-00411: incoming ASN.1 NULL encoding has nonzero length of string
Cause: The ASN.1 protocol engine received a corrupted ASN.1 construct.
Support.
NPL-00412: incoming ASN.1 BOOLEAN encoding has incorrect length of string
Support.
NPL-00413: incoming ASN.1 encoding has length string, maximum allowed is
string
Cause: The ASN.1 protocol engine received an ASN.1 construct too large for it to
process.
Support.
NPL-00414: incoming ASN.1 type tag is greater than maximum of 16383
Cause: The ASN.1 protocol engine received an illegal ASN.1 construct.
Support.
NPL-00415: received unsupported ASN.1 INDEFINITE-LENGTH encoding
Cause: The ASN.1 protocol engine received an ASN.1 encoding which it could not
process because its implementation does not support it.
Support.
NPL-00100 to NPL-00420 50-3
NPL-00416: received illegal ASN.1 encoding length of string

Support.
NPL-00417: received ASN.1 length octet count greater than maximum of string
process because its implementation does not support it..
Support.
NPL-00418: received malformed ASN.1 object identifier
Support.
NPL-00419: received ASN.1 object identifier with sub-identifier that is too large
Support.
NPL-00420: received ASN.1 object identifier with more than 256 sub-identifiers
Support.
50-4 Error Messages
51
NZE-28750 to NZE-29249
NZE-28750: unknown error
Cause: An Oracle Security Server error of an unspecified type occurred.
Action: Enable tracing to determine the exact cause of this error. Contact Oracle
customer support if needed.
NZE-28751: memory allocation failure
Cause: The allocation of memory failed due to insufficient system memory.
Action: Terminate other processes to free up memory or add memory to the system.
NZE-28752: data source initialization failure
Cause: A data source failed to initialize. Frequently, this error is caused by insufficient
system resources.
NZE-28753: failure to terminate use of data source
Cause: The system failed to terminate its use of a data source. This error may have
been caused by memory or disk corruption, among other things.
NZE-28755: object retrieval failure
Cause: The system failed to retrieve information from a file or a database.
Action: Check if the data source exists, or check to ensure that the correct information
exists.
NZE-28756: callback failure to allocate memory
Cause: A function supplied by the caller failed to allocate memory. This error could
have been caused by system memory exhaustion.
NZE-28757: system attempt to allocate 0 bytes of memory
Cause: The system attempted to allocate 0 bytes of memory because there was no
available memory left to allocate. This error could have been caused by insufficient
system memory.
NZE-28758: memory release failure
Cause: The release of a memory fragment failed. This may be due to memory
corruption either within the application or in the Oracle Security Server library.
NZE-28750 to NZE-29249 51-1
NZE-28759: failure to open file
Cause: The system could not open the specified file.
NZE-28763: Invalid parameter type found in configuration file.
Cause: A parameter in the sqlnet.ora file may have been specified incorrectly.
Action: Check the sqlnet.ora file for this parameter value.
NZE-28764: failure to retrieve a configuration parameter
Cause: The system failed to retrieve a configuration parameter from the sqlnet.ora
file. This error may have occurred because a necessary configuration parameter was
not specified in the sqlnet.ora file.
Action: Supply the needed configuration parameter in the sqlnet.ora file.
NZE-28766: failure to terminate use of data source
Cause: The system failed to terminate its use of a data source. This error may have
been caused by memory or disk corruption, or a system error.
NZE-28767: invalid version number
Cause: Version number of the wallet was incorrect. A corrupt wallet or an
incompatible wallet was provided.
Action: Ensure that proper wallet is being used.
NZE-28768: bad magic number
Cause: An invalid magic number was specified in a data file. This could have been
caused by a corrupted disk or by some other process overwriting the file.
NZE-28769: Specified method does not exist.
Cause: The data access method that was specified in the configuration file is not
supported.
Action: Specify a supported method. Consult the Oracle Security Server
documentation to determine the supported types.
NZE-28770: Data source is already initialized.
Cause: The caller attempted to initialize a data source which was already initialized.
Action: This is a programming error. An application should not attempt to initialize a
data source more than once.
NZE-28771: Data source is not yet initialized.
Cause: The caller attempted to use a data source which had not yet been initialized.
Action: This is a programming error. The application must always initialize the data
source before it can be used.
51-2 Error Messages
NZE-28773: failure to write magic and version numbers

Cause: Both the magic and version numbers failed to write. This usually occurs
because of insufficient disk space.
Action: Delete unnecessary files to free up disk space or add disk space to the system.
NZE-28774: file cannot write to disk
Cause: The output of a file failed. This error usually occurs because of insufficient
disk space.
Action: Delete unnecessary files to free up disk space or add disk space to the system.
NZE-28775: file cannot close
Cause: Failed to close a file which is used by a data access method. This error usually
indicates memory corruption or a system error.
NZE-28776: Output buffer supplied is too small.
Cause: The data returned by a function was too large for the supplied buffer.
Action: Call the routine again with a larger buffer.
NZE-28777: binding creation failure
Cause: Failed to create a binding for use in the parsing of a parameter value. This
error can be caused by the parameter value being in an incorrect format, such as a
right parenthesis was not supplied where expected, or due to insufficient system
memory.
Action: Make sure that the parameter is specified in the correct format. If the format is
correct, free up system memory by terminating processes or adding more memory.
NZE-28778: Configuration parameter is not specified in the proper format.
Cause: The configuration parameter was not specified in the proper format.
Action: Consult the Oracle Security Server documentation for a description of the
proper format for this parameter.
NZE-28779: no data access method specified in parameter
Cause: No method for data access was specified in the parameter value.
Action: Specify a method for data access in the parameter. Consult the Oracle Security
Server documentation for the supported data access methods for this data type.
NZE-28780: invalid data access method specified by the parameter
Cause: The data access method specified by the parameter value is not supported.
Action: Specify a supported data access method. Consult the Oracle Security Server
documentation for the supported data access methods for this data data type.
NZE-28781: No data for the access method is specified in the parameter.
Cause: No data was specified in the parameter for use with the specified access
method.
Action: Consult the Oracle Security Server documentation for the data that must be
specified for the access method.
NZE-28782: data source is not allocated
Cause: No memory was allocated for a data source.
NZE-28750 to NZE-29249 51-3
Action: Ensure that the application calls in the data source initialization function.
NZE-28783: invalid parameter
Cause: There was no match for the parameter name that was used in the
configuration file.
Action: Check your sqlnet.ora file for the correct parameter name.
NZE-28784: file name translation failure
Cause: The translation of a file name from Oracle format to native format has failed.
Action: Specify a correct file name. Consult your Oracle documentation for the correct
file name format.
NZE-28785: parameter does not exist
Cause: A necessary configuration parameter was not found in the parameter file.
Action: Supply the required parameter.
NZE-28786: decryption of encrypted private key failure
Cause: An incorrect password was used to decrypt an encrypted private key.
Action: Enter the correct password.
NZE-28787: private key encryption failure
Cause: This may have been caused by an error in the mkwallet parameter of the
sqlnet.ora file.
NZE-28788: user provided invalid information, or an unknown error
Cause: User may have responded to a prompt with unexpected input, or an unknown
error occurred.
Action: Enter correct input, or enable tracing to check the trace file for errors.
NZE-28790: NLS string open failure
Cause: The opening of a string for use by the NLS subsystem failed.
NZE-28791: certificate verification failure
Cause: Verification of the certificate, which the user supplied, failed.
NZE-28794: data type attribute did not initialize
Cause: The initialization of the attribute data type failed. This error may be due to
insufficient system resources.
NZE-28795: data type attribute did not terminate
Cause: The termination of the use of the attribute data type subsystem failed.
51-4 Error Messages
NZE-28796: access method is not supported

Cause: The method specified to access data is not supported.
Action: Use a supported access method. Consult your Oracle documentation to
determine which access methods are supported.
NZE-28797: invalid key data type
Cause: The type specified for a key is not supported.
Action: Correct the key type. Consult your Oracle documentation to determine which
key types are supported.
NZE-28800: data source failed to open
Cause: A data source (a file or a database) failed to open.
NZE-28802: invalid mode or data source in configuration file
Cause: An invalid mode or data source has been specified in the configuration file
(sqlnet.ora).
Action: Check the method parameter in the sqlnet.ora file. If the parameter value is
correct, then enable tracing to determine the exact error.
NZE-28803: I/O operation failure
Cause: The system or application failed to access a data source (file or database).
NZE-28804: Data source cannot close.
Cause: The data source, which could be either a file or a database), failed to close.
NZE-28805: Cannot retrieve information from the data source.
Cause: The system or application failed to retrieve information from the data source
(file or database).
NZE-28806: Cannot write to the data source.
Cause: The system or application failed to write to the data source (file or database).
NZE-28807: Cannot update the data source.
Cause: The system or application failed to update the data source (file or database).
NZE-28808: Cannot retrieve method information from the configuration file.
Cause: The system or application failed to retrieve method information from the
sqlnet.ora configuration file.
NZE-28750 to NZE-29249 51-5
Action: Check the method configuration parameters in the sqlnet.ora file. If the
method configuration parameters are correct, then enable tracing to determine the
exact error.
NZE-28809: Cannot delete information from the data source.
Cause: The system or application failed to delete information from the data source
(file or database).
NZE-28810: Cannot create key descriptor.
Cause: The system failed to create a key descriptor.
NZE-28814: Cannot convert a number in Oracle format to native format.
Cause: Failed to convert a number from Oracle format to native format.
Action: This is an internal programming exception. Enable tracing to try and
reproduce the problem. Contact Oracle customer support and supply the trace file.
NZE-28815: Cannot convert a number in native format to Oracle format.
Cause: Failed to convert a number from native format to Oracle portable format
failed.
Action: This is an internal programming exception. Enable tracing to try and
reproduce the problem. Contact Oracle customer support and supply the trace file.
NZE-28818: No package context provided.
Cause: The context that holds the state of the security package was not passed to a
function or procedure that was expecting it.
Action: This is an internal error. Enable tracing to find more information. Contact
Oracle customer support if needed.
NZE-28836: Wallet is not open.
Cause: The wallet to be used has not yet been opened.
Action: Call the function that opens the wallet.
NZE-28840: Wallet is already open.
Cause: An attempt was made to open a wallet that was already open.
Action: This is a programming error. A wallet should only be opened once.
NZE-28841: Operation is not supported.
Cause: An attempt was made to perform an operation that is not supported.
Action: This is a programming error. Please refer to Oracle documentation to
determine which operations are supported.
NZE-28842: Incorrect file permissions
Cause: The subject file did not have the correct permissions for the operation.
Action: Ensure that the file permissions allow the current operation.
NZE-28843: Operating system error while creating/opening file
Cause: An operating system dependent error occurred while trying to create/ open
the file or while trying to set the appropriate permissions on the file.
51-6 Error Messages
NZE-28844: No wallet present
Cause: There was no wallet in the location specified.
Action: Check to ensure that the wallet is in the correct directory location.
NZE-28845: No certificate
Cause: Either there is no certificate or the system cannot find it.
Action: Check to ensure that the certificate is in the specified wallet.
NZE-28846: No private key
Cause: Either there is no private key or the system cannot find it.
Action: Check to ensure that the private key is in the specified wallet.
NZE-28847: No clear private key file
Cause: Failed to retrieve private key from SSO wallet
NZE-28848: No encrypted private key file
Cause: Failed to retrieve private key from the wallet
NZE-28849: No Trustpoints
Cause: The wallet does not have any trusted certificates
Action: Ensure that the wallet/keystore has trusted certificates.
NZE-28853: Initialization failure
Cause: Either initialization or module loading has failed.
NZE-28854: Memory allocation failure
Cause: The allocation of memory failed due to insufficient system memory.
NZE-28855: Unsupported SSL operation
Cause: An unsupported operation was attempted, for example, an attempt was made
to select a mode of operation that is not allowed.
Action: Refer to the SSL chapter in the product's documentation.
NZE-28857: Unknown SSL error
Cause: An unknown SSL error occurred.
NZE-28858: SSL protocol error
Cause: An error occurred while negotiating the SSL handshake between two
processes.
NZE-28750 to NZE-29249 51-7
NZE-28859: SSL negotiation failure
Cause: An error occurred during negotiation between two processes as part of the SSL
protocol. This error will occur if the two sides to the connection do not support a
common cipher suite.
Action: Configure each process so they support a common cipher suite. Then attempt
the connection again. If error occurs again, enable tracing and retry the connection.
Then contact Oracle customer support with the trace output.
NZE-28860: Fatal SSL error
Cause: An error occurred during the SSL connection to the peer. It is likely that this
side sent data which the peer rejected.
NZE-28861: SSL connection would block
Cause: This error is informational. It should never be communicated to the user.
Action: Enable tracing and retry the connection to determine the exact cause of the
error. Contact Oracle customer support if needed.
NZE-28862: SSL connection failed
Cause: This error occurred because the peer closed the connection.
Action: Enable tracing on both sides and examine the trace output. Contact Oracle
Customer support with the trace output.
NZE-28863: SSL session not found
Cause: This error is informational. It indicates that a specified session does not exist.
Action: Enable tracing and attempt the connection again. Contact Oracle customer
support with the trace output.
NZE-28864: SSL connection closed gracefully
Cause: This error is informational. It indicates that the connection closed without
error.
Action: This error is not normally visible to the user. Enable tracing and retry the
connection. If the error persists, contact Oracle customer support.
NZE-28865: SSL connection closed
Cause: The SSL connection closed because of an error in the underlying transport or
because the peer process quit unexpectedly.
Action: Enable tracing and retry the connection. The trace output should indicate how
the failure occurred.
NZE-28866: Invalid peer certificate encoding
Cause: A field from a certificate in the peer's certificate chain could not be recognized.
Action: Refer to Oracle Wallet Manager documentation to find out how to obtain the
peer's certificate. Then contact Oracle customer support with the peer's certificate
chain.
NZE-28867: Integer value is too big.
Cause: The certificate presented had an integer field whose value was too large.
51-8 Error Messages
chain.
NZE-28868: Peer certificate chain check failed.
Cause: The check of the certificate list presented by the peer failed. Possible causes
include: 1. the expiration of one of the certificates; 2. a certificate authority in a
certificate was not recognized as a trust point; 3. the signature in a certificate could
not be verified.
Action: Refer to Oracle Wallet Manager documentation to find out how to open your
wallet and ensure that: 1. all of the certificates installed in your wallet are current 2. a
certificate authority's certificate from your peer's certificate chain is added as a trusted
certificate in your wallet
NZE-28869: Peer's certificate is expired.
Cause: The certificate being used to authenticate a client or server has expired.
Action: Obtain a new certificate, which is unexpired, and attempt the connection
again.
NZE-28870: Name comparison failure
Cause: A comparison of the names contained in two certificates failed.
NZE-28871: Peer certificate chain is incomplete.
Cause: The peer certificate chain presented was incomplete because it did not end
with a self-signed root certificate.
Action: Refer to Oracle Wallet Manager documentation to find out how to open your
wallet and ensure that: 1. the certificate authority's root certificate is self-signed. 2. a
certificate authority's certificate from your peer's certificate chain is added as a trusted
certificate in your wallet
NZE-28872: Invalid peer certificate format
Cause: The peer certificate does not conform to the X.509v3 standard.
Action: Refer to Oracle Wallet Manager documentation to find out how to get the
peer certificate. Then contact Oracle customer support with the peer's certificate.
NZE-28874: SSL: I/O closed - override goodbye kiss
Cause: This error is informational. It indicates that the connection closed without
error.
NZE-28875: SSL: use server-gated cryptographic suites
Cause: This is used as a internal status indicator and not really an error.
Action: This message is not normally visible to the user. Enable tracing and retry the
NZE-28884: invalid cipher suite
Cause: An invalid cipher suite string has been specified in the product's configuration
file.
NZE-28750 to NZE-29249 51-9
Action: Refer to the product documentation for information about supported cipher
suites.
NZE-28885: No certificate with the required key usage found.
Cause: Certificate not created with the appropriate X509v3 key usage extension.
Action: Refer to Oracle Wallet Manager documentation to find out the supported key
usages.
NZE-28890: Entrust Login Failed
Cause: An application failed to log in to an Entrust Profile. Possible causes include: 1.
Entrust Admin/Authority was not online. 2. Invalid password for Entrust profile was
specified. 3. Invalid path to Entrust profile was specified 4. Invalid Entrust
initialization file was specified. 5. Entrust Server Login program was not executed
(server-side only).
Action: Make sure that: 1. Entrust Authority is online; 2. Password for Entrust profile
is specified correctly; 3. Path to Entrust profile is specified correctly; 4. A valid Entrust
initialization file is provided; 5. Entrust Server Login program is run before the
database startup. For more information, enable tracing and examine the trace output
to get exact the Entrust failure codes.
NZE-29000: Certificate not installed
Cause: Trying to delete a certificate which has not been installed.
Action: Refer to the Oracle Wallet Manager documentation for information about
delete option.
NZE-29002: SSL transport detected invalid or obsolete server certificate.
Cause: The client detected a mismatch between the server's distinguished name
specified on the server's certificate and the server's SID or service name.
Action: Refer to the SSL chapter in Oracle Advanced Security Administrator's Guide
for information about enabling server distinguished name matching. Contact your
administrator to perform the appropriate action.
NZE-29003: SSL transport detected mismatched server certificate.
Cause: The client detected a mismatch between the server's distinguished name
specified on the server's certificate and the server's SID or service name.
Action: Refer to the SSL chapter in Oracle Advanced Security Administrator's Guide
for information about enabling server distinguished name matching. Contact your
administrator to perform the appropriate action.
NZE-29005: The certificate is invalid.
Cause: The peer certificate encoding is invalid when using SSL 2.0.
chain.
NZE-29006: The certificate request message is invalid when using SSL 2.0.
Cause: There is an error processing the SSL 2.0 REQUEST-CERTIFICATE message.
NZE-29007: Bad Clear Key Length when using SSL 2.0

Cause: The clear key length of an SSL 2.0 Client Master key handshake message is
invalid.
NZE-29008: Bad DH Param key length
Cause: The length of the Diffie-Hellman params exceeds export restrictions.
NZE-29009: Bad encrypted key length when using SSL 2.0
Cause: The encrypted key length of an SSL 2.0 Client Master key handshake message
is invalid.
NZE-29010: Export key length does not meet export restrictions.
Cause: The server sent a ServerKeyExchange message with an export key which does
not meet export restrictions. For RSA, the export key must be exactly 512 bits.
Action: Obtain a certificate with the appropriate key length.
NZE-29011: Finished message is incorrect.
Cause: The FINISHED message data verification failed.
NZE-29012: Bad key argument length when using SSL 2.0
Cause: The key argument length of an SSL 2.0 Client Master Key handshake message
is invalid.
NZE-29013: SSL MAC verification failure
Cause: Verification of SSL Record MAC failed.
NZE-29014: Maximum fragment length extension is incorrect.
Cause: The maximum fragment length extension specified is incorrect.
NZE-29015: incorrect message length
Cause: The message length is not correct.
NZE-29016: inadequate PKCS1 message padding
Cause: The message was not properly padded before encryption.
NZE-28750 to NZE-29249 51-11
NZE-29017: The premaster secret length is incorrect.
Cause: The premaster secret sent by the peer has an incorrect length.
NZE-29018: The premaster secret contains an incorrect version number.
Cause: The premaster secret must contain the same version number as the
ClientHello. The version sent by the client was incorrect.
NZE-29019: The protocol version is incorrect.
Cause: There is a protocol version mismatch between the two peers.
Action: Specify the correct protocol version in the product's configuration file.
NZE-29020: The handshake record length is too long.
Cause: The handshake record length exceeds the maximum that is allowed by the SSL
specification.
NZE-29021: Secret key length is incorrect when using SSL 2.0.
Cause: The length of the decrypted ENCRYPTED-KEY is incorrect.
NZE-29022: Operation is being attempted on the wrong side of the client/server
connection.
Cause: The SSL network layer has detected that the operation has been attempted on
the wrong side of the client/server connection.
Action: Select the protocol side (of this protocol) to be the same as the one selected
with a previous protocol.
NZE-29023: The buffers are not empty.
Cause: Trying to free buffers that are not empty.
NZE-29024: Certificate validation failure
Cause: The certificate sent by the other side could not be validated. This may occur if
the certificate has expired, has been revoked, or is invalid for another reason.
Action: Check the certificate to determine whether it is valid. Obtain a new certificate,
alert the sender that the certificate has failed, or resend.
NZE-29025: Error found in certificate check callback.
Cause: The application callback failed during additional certificate validation.
Additional checks include CRL validation and extension checking.
NZE-29026: Decryption failure

Cause: SSL record decryption failed.
NZE-29027: Error in entropy collection
Cause: The internal entropy collection failed to generate enough seed data.
NZE-29028: Server verification failure when using SSL 2.0
Cause: Processing of an SSL 2.0 SERVER-VERIFY message failed.
NZE-29029: SSL handshake already completed
Cause: The system is trying to initiate a handshake when it has already been
completed.
NZE-29030: SSL handshake is requested.
Cause: The peer sends this message if it wishes to renegotiate. The application can
either proceed with the renegotiation or reject the request.
Action: This is not an error. To find out more details enable tracing and retry the
connection. Contact Oracle customer support with the trace output.
NZE-29031: SSL handshake is required.
Cause: Renegotiation cannot proceed before the SSL handshake is completed.
NZE-29032: The given identity is not complete.
Cause: The certificate list does not contain both private key and certificate.
NZE-29034: Correct cipher suite or client authentication is needed.
Cause: Before installing a private key, a cipher suite or client authentication suite
using the same key exchange algorithm must be installed first. This has not been
done.
Action: Install a cipher suite or client authentication suite that uses the same key
exchange algorithm as the private key before re-installing the private key.
NZE-29036: This feature is not supported
Cause: Operation is not supported by the current connection parameters.
Action: Check the Oracle documentation to determine the appropriate connection
parameters required for this operation.
NZE-28750 to NZE-29249 51-13
NZE-29037: No certificate is present

Cause: The other client or server sent a certificate message that contained no
certificates.
Action: Check the other side (client or server) to ensure they have appropriate
credentials.
NZE-29038: There are no matching certificates.
Cause: The other client or server sent a certificate message that contained a certificate
which was not signed by a trusted certificate authority (CA).
Action: Check to ensure that the other client or server sends a certificate which is
signed by a CA that is in your trusted list. Or, include the CA certificate for the other
client or server's certificate as a trustpoint in your wallet.
NZE-29039: There are no matching cipher suites.
Cause: Neither end of the handshake can agree on a cipher suite.
Action: Check to ensure that both sides of the handshake select cipher suites that are
supported.
NZE-29040: There are no supported cipher suites.
Cause: This end of the handshake cannot support any cipher suites. This connection
and the peer have some matching cipher suites, however, these cipher suites cannot
be negotiated because they cannot be supported by the connection.
Action: Check to ensure that both sides of the handshake select cipher suites that are
supported by the connection. Refer to Oracle documentation for supported cipher
suites.
NZE-29043: Read is required.
Cause: Renegotiation with the peer has not yet started. There is application data
which must be processed before the handshake can proceed.
NZE-29044: Renegotiation has already been requested.
Cause: Renegotiation has already been requested.
NZE-29045: Renegotiation request has been refused.
Cause: A renegotiated handshake has been refused by the peer.
NZE-29046: Session is resumable.
Cause: Server is trying to resume a session with different session parameters.
Action: Server should resume the session with the correct session parameters.
NZE-29047: Mismatch in Transport Layer Security extension
Cause: Neither side can agree on a TLS extension.
NZE-29048: Unexpected message received.

Cause: An unexpected message has been received.
NZE-29049: Unknown record
Cause: The record type is unknown.
NZE-29050: Installed client authentication mode is not supported.
Cause: The enabled client authentication mode(s) cannot be used within the selected
cipher suite.
Action: Enable a client authentication mode that can be used within the selected
cipher suite.
NZE-29051: The given public key type is not supported.
Cause: The public key in the first certificate is not supported.
Action: Check to ensure that the certificate complies with the X.509v3 standard.
NZE-29052: Write buffer is not empty.
Cause: There is an attempt to free a write buffer that is not empty.
NZE-29084: The parameter specified is illegal.
Cause: The parameter is not correct. For example, it could be bad input, or an invalid
message.
NZE-29095: Index is not correct.
Cause: The instance identified by the index parameter doesn't exist.
NZE-29096: The given length is incorrect.
Cause: The specified length is too small or is invalid.
NZE-29100: Cannot create local key ID.
Cause: Creation of local key identifier for the certificate or the private key failed.
NZE-29101: Cannot add private key bag.
Cause: The private key could not be added to the PKCS#12 object. Possible reasons
are: (i) A required parameter is NULL (ii) The PKCS#12 construct is not supported
(iii) An ASN.1 encoding error occurred in the certificate.
NZE-28750 to NZE-29249 51-15
NZE-29102: Cannot add certificate bag.
Cause: Creation of certificate bag failed. The application could have run out of
memory.
NZE-29103: Cannot create PKCS #12 wallet.
Cause: Creation of PKCS#12 wallet failed possibly due to memory allocation failure.
NZE-29104: Cannot add certificate request.
Cause: Adding certificate request to the PKCS#12 wallet failed.
NZE-29105: Cannot export PKCS #12 wallet.
Cause: A required parameter is NULL or the PKCS#12 construct is not supported.
NZE-29106: Cannot import PKCS #12 wallet.
Cause: A required parameter is NULL or the BER-encoding is malformed.
NZE-29107: Cannot create PKCS #12 wallet.
Cause: PKCS#12 wallet creation failed. The application may have run out of memory.
NZE-29108: Cannot initialize random object.
Cause: The random object could not be initialized or seeded. Either memory
allocation has failed or the pseudo random number generator module has not been
installed.
NZE-29109: Cannot create private key object.
Cause: The private key object could not be created. Memory allocation may have
failed.
NZE-29110: Invalid PKCS #12 bag type
Cause: The PKCS #12 bag type is invalid. Either one of the required parameters is
NULL or the requested OID is not in the list.
NZE-29111: Invalid index

Cause: The index passed for getting the bag type is less than 1.
Action: Check to ensure that the index is greater than 1.
NZE-29112: Cannot access attributes from a PKCS #12 certificate bag.
Cause: The certificate cannot be accessed. One of the required parameters is probably
NULL, or the index specified by the application does not contain a certbag, or the
certificate could be malformed.
NZE-29113: Cannot access attributes from a PKCS #12 key bag.
Cause: Retrieval of the private key failed. One of the required parameters is probably
NULL or the index specified by the application does not contain a key bag.
NZE-29114: Cannot import private key.
Cause: The private key could not be imported. One of the required parameters could
be NULL or the encoded private key could be malformed.
NZE-29115: Cannot export private key.
Cause: The private key could not be exported. Either the application ran out of
memory or the key type is not valid.
NZE-29116: Cannot get PKCS #12 attributes.
Cause: Retrieval of an attribute failed. One of the required parameters could be
NULL.
NZE-29117: Cannot add PKCS #12 attributes.
Cause: Could not add an attribute. The attribute parameter could be NULL.
NZE-29118: Cannot create PKCS #12 attributes.
Cause: Creation of the attributes failed, possibly due to a memory allocation error.
NZE-29119: Cannot import certificate.
Cause: The certificate cannot be imported. One of the required parameters could be
NULL or the certificate has an invalid X.509 BER or DER encoding.
NZE-28750 to NZE-29249 51-17
NZE-29120: Cannot export certificate.

Cause: The certificate cannot be exported. One of the required parameters could be
NULL.
NZE-29122: could not add pkcs11 info to the pkcs12 wallet
Cause: Failed while adding pkcs11 information into a pkcs12 wallet.
NZE-29123: could not get pkcs11 info from the pkcs12 wallet
Cause: An error was encountered while retrieving pkcs11 information from the
wallet.
NZE-29124: pkcs11 library name already set
Cause: pkcs11 library information was already set in the wallet.
Action: Use a different wallet that does not have this information. If issue persists,
enable tracing to determine the exact cause of the error. Contact Oracle customer
support if needed.
NZE-29125: pkcs11 token label already set
Cause: pkcs11 token label information was already set in the wallet.
support if needed.
NZE-29126: pkcs11 token passphrase already set
Cause: The pkcs11 token passphrase can be set only once in the wallet.
support if needed.
NZE-29127: unknown pkcs11 information
Cause: An unknown pkcs11 information type was encountered. The wallet may have
been corrupted due to a system error or memory corruption.
Action: Enable tracing and retry the failed operation. Contact Oracle customer
NZE-29128: pkcs11 library name not set
Cause: The wallet does not have pkcs11 library information.
Action: Ensure that the wallet was created with valid library location or update the
wallet with this information.
NZE-29129: pkcs11 token label not set
Cause: The wallet does not have pkcs11 token label information.
Action: Ensure that the wallet was created with valid token label information or
update the wallet with this information.
NZE-29130: pkcs11 token passphrase not set

Cause: The wallet does not have pkcs11 token passphrase.
Action: Ensure that the wallet was created with valid token passphrase information or
update the wallet with this information.
NZE-29131: pkcs11 certificate label already set in wallet
Cause: The pkcs11 certificate label was already set in the wallet.
Action: Use an empty wallet (created with orapki).
NZE-29135: Seed generation for Random Number Generator failed.
Cause: Generation of seed for random number generator failed.
NZE-29136: The allocated buffer is too small.
Cause: The output buffer is too small.
NZE-29137: The global context is incorrect.
Cause: The global context is incorrectly configured or invalid.
NZE-29140: Cannot create certificate object.
Cause: Creation of the certificate object failed. The application could have run out of
memory.
NZE-29141: Cannot import in the der format.
Cause: Cannot import the certificate into the certificate object. The reason could be a
malformed certificate.
NZE-29150: DES self-test failure
Cause: DES power up self-test has failed.
NZE-29151: 3DES self-test failure
Cause: 3DES power up self-test has failed.
NZE-29152: SHA-1 self-test failure
Cause: The SHA-1 power up self-test has failed.
NZE-28750 to NZE-29249 51-19
NZE-29153: RSA self-test failure

Cause: The RSA power up self-test has failed.
NZE-29154: deterministic RNG self-test failure
Cause: The deterministic Random Number Generator power up self-test has failed.
NZE-29155: continuous key pair consistency check self-test failure
Cause: The public-private key pair check test failed.
NZE-29156: conditional RNG self-test failure
Cause: Continuous Random Number Generator test, which is needed in FIPS mode,
has failed.
NZE-29157: Unable to build an absolute path to the library.
Cause: Not able to construct an absolute path to the location of the library.
NZE-29158: Unable to open library.
Cause: Opening of the library failed.
Action: Check to ensure that the library is present in the location specified, and that it
has the appropriate file permissions.
NZE-29159: Unable to read library.
Cause: Not able to read the library on which the DAC check has to be performed.
Read call failed.
Action: Check if the library has the appropriate file permissions.
NZE-29160: NZ library being used is different.
Cause: The NZ library being used at runtime is not the same one on which the digest
was computed for the software integrity check.
Action: Check to ensure that the library being used is the same as the one on which
the digest was pre-computed.
NZE-29161: software integrity self-test failure
Cause: The software integrity check test on the NZ shared library has failed.
Action: Check to ensure that the library being used is the same as the one on which
the digest was pre-computed.
NZE-29162: Non-FIPS cipher suites being used in FIPS mode.
Cause: The cipher suite being used does not contain FIPS-approved algorithms.
Action: Use cipher suites that contain FIPS-approved algorithms.
NZE-29163: Third party PKI vendor is not supported in FIPS mode.

Cause: Third party PKI vendors like Entrust and MCS are not supported in FIPS
mode.
Action: Use only Oracle PKI when running in FIPS mode.
NZE-29164: External PKCS #12 wallet is not supported in FIPS mode.
Cause: PKCS #12 wallets created using third party software cannot be used in FIPS
mode.
Action: Use only PKCS #12 wallets created by Oracle Wallet Manager when running
in FIPS mode.
NZE-29166: Bad key size in FIPS mode.
Cause: User attempted to use a key size that is not allowed in FIPS mode
Action: Ensure that the key size meets FIPS usage requirement. For example, RSA key
modulus cannot be less than 1024 bits in FIPS mode.
NZE-29176: CRL signature verification failed
Cause: A CRL is verified before being used. CRL signature cannot be verified.
Action: Get a new CRL from CA
NZE-29177: certificate serial number is not in CRL
Cause: Cert is not revoked
Action: n/a
NZE-29178: certificate serial number is in CRL
Cause: Cert has been revoked
Action: Reject the certificate
NZE-29179: certificate validation check failed
Cause: Could not complete checking certificate status with a CRL.
Action: Enable tracing to find more information on this error. Contact Oracle
NZE-29180: Unsupported validation protocol
Cause: The certificate validation protocol is not supported
Action: Make sure a supported certificate validation protocol is specified
NZE-29181: ldap_open failed
Cause: Could not connect to the LDAP server
Action: Ensure that correct LDAP information was provided. Enable tracing to find
more information. Contact Oracle customer support if needed.
NZE-29182: ldap_bind failed
Cause: Could not log in to the LDAP server
Action: Ensure that correct LDAP credentials were provided. Enable tracing to find
more information. Contact Oracle customer support if needed.
NZE-29183: ldap_search failed
Cause: Failed to complete search operation in LDAP server
NZE-28750 to NZE-29249 51-21
NZE-29184: ldap_result failed

Cause: Failed to retrieve results from LDAP operation
NZE-29185: ldap_first_attribute failed
Cause: Could not get the first attribute from LDAP entry.
NZE-29186: ldap_get_values_len failed
Cause: Failed to retrieve attribute values from LDAP entry
NZE-29187: unsupported validation mechanism
Cause: The validation mechanism specified in OID is not supported
Action: Make sure a supported validation mechanism is set in OID
NZE-29188: ldap_count_entries failed
Cause: Failed to get count of entries from a search result chain.
NZE-29189: No entry found in OID
Cause: CRL not found in OID
Action: Upload the CRL to OID
NZE-29190: Multiple entries in OID
Cause: For a given issuer name there should be only one CRL in OID
Action: Make sure there is only one CRL for a given issuer name in OID
NZE-29191: OID connection information not set
Cause: To connect to OID the connection information must be available
Action: Set the OID connection information.
NZE-29192: Validation mechanism not set in OID
Cause: The validation mechanism to be used is not set in OID
Action: Set validation mechanism to be used in OID at cn=ValidationMechanism,
cn=Validation, cn=PKI, cn=Products, cn=OracleContext
NZE-29193: no CRL found using CRLDP mechanism
Cause: A CRL could not fetched using CRL Distribution point (CRLDP)
Action: Contact the CA
NZE-29194: no CRL found in cache
Cause: CRL not in cache
Action: n/a
NZE-29195: CRL is expired
Cause: CRL nextUpdate time is in the past
Action: Get a new CRL from the CA

NZE-29222: Distinguished name does not match.
Cause: Distinguished name (DN) on certificate doesn't match user.
Action: Create the global user in the database with the DN that matches with the one
in the user certificate on the client side.
NZE-29223: Cannot create certificate chain.
Cause: Unable to create a certificate chain with the existing trust points for the
certificate that is to be installed.
Action: Install the trust point that signed the certificate.
NZE-29224: Cannot locate matching certificate request.
Cause: No matching certificate request for the certificate was found.
Action: Install the correct certificate.
NZE-29225: Certificate already installed.
Cause: Attempting to install a certificate into a persona which already has it.
Action: Do not install the certificate.
NZE-29226: No matching private key found.
Cause: Could not locate a matching private key in the persona for the given certificate
(public key).
Action: n/a
NZE-29227: Certificate is expired.
Cause: Certificate is no longer valid..
Action: Obtain another certificate or renew this certificate.
NZE-29228: Cannot calculate the number of bytes for output.
Cause: The cryptographic engine is confused about the algorithm.
Action: Check the parameters being used with the cryptographic functions.
NZE-29229: the magic number found in the header does not match expected
Cause: The input TDU has either been corrupted or is not being used correctly.
Action: Check that the TDU is being used from the beginning. If possible, compare the
size of the TDU upon generation to the size being used.
NZE-29230: the header length is not sufficient for message header
Cause: The input TDU has either been corrupted or it is not being used correctly.
Action: Check that the TDU is being used from the beginning. If possible, compare the
size of the TDU upon generation to the size being used.
NZE-29231: the cryptographic engine failed to initialize
Cause: During initialization of the cryptographic engine, some failure occurred.
Possible causes include running out of memory and trying to seed the random
number generator.
Action: Make sure the executable has been linked with compatible library versions,
and that you are not running out of swap space.
NZE-28750 to NZE-29249 51-23
NZE-29232: the cryptographic engine key initialization failed

Cause: During initialization of a key for cryptography, some failure occurred. This
includes running out of memory and passing illegal arguments.
Action: Make sure the executable has been linked with compatible library versions,
and that the correct parameters are being used for the cryptographic functions.
NZE-29233: the key object could not be encoded
Cause: The key object may be corrupted or may be an unsupported type.
Action: Check the key object being passed to the encoding routine.
NZE-29234: a key object was not extracted from encoding
Cause: The encoding may be corrupted or may not be a key object at all.
Action: Check the encoding and parameters passed to decoding routine.
NZE-29235: the key information could not be retrieved
Cause: The key may be corrupted or may be an unsupported type.
NZE-29236: the random number generator will not accept seed
Cause: The cryptographic engine may have run out of memory.
Action: Make sure the executable has been linked with compatible library versions.
NZE-29237: the cryptographic engine could not finish the algorithm
Cause: The cryptographic engine does not have enough information to correctly
finish applying the algorithm.
NZE-29238: the cryptographic engine could not apply the algorithm
apply the algorithm.
NZE-29239: the cryptographic engine could not initialize the algorithm
initialize the algorithm.
NZE-29240: the cryptographic engine does not recognize the algorithm
Cause: The application may be passing wrong parameters.
NZE-29241: a buffer block needs more space but its length is fixed
Cause: The application has preallocated an output buffer that is too short for the
operation and has specified that the buffer should not grow as needed.
Action: Either preallocate a larger buffer or allow the toolkit to grow the output buffer
as needed.
NZE-29242: the asymmetric key is too short to be used with the data.
Cause: An asymmetric key must be at least 11 bytes longer than the data it is being
used to encrypt.
Action: Use an asymmetric key with more bits or break the data into smaller pieces.
NZE-29243: the toolkit does not recognize the type of key being used
Cause: The application may be passing wrong parameters.
Action: Check the parameters being used with the toolkit functions.
NZE-29245: the toolkit does not recognize the function being used
Cause: The application is probably passing the wrong parameters.
NZE-29246: the toolkit could not parse the tdu
Cause: The TDU could be corrupted.
NZE-29247: an unopen toolkit object was used before it was opened
Cause: Some toolkit objects must be opened before they can be used.
NZE-29248: an unrecognized WRL was used to open a wallet
Cause: WRL's have a specific set of types and must be formatted correctly.
NZE-29249: an unrecognized state was passed to a cryptographic function
Cause: The application is probably passing the wrong parameters.
NZE-28750 to NZE-29249 51-25
52
NZE-43000 to NZE-43021
NZE-43000: pkcs11 library not found
Cause: The PKCS11 library could not be found.
Action: Make sure that the pkcs11 library is at the location specified in the wallet.
NZE-43001: pkcs11 token not found
Cause: The PKCS11 token could not be found.
Action: Make sure that a token with correct label is present in slot.
NZE-43002: pkcs11 passphrase is wrong
Cause: The PKCS11 passphrase is wrong.
Action: Make sure that the token passphrase specified is correct.
NZE-43005: pkcs11: No tokens present
Cause: a token is not present in the slot
Action: Place a pkcs11 token in the slot
NZE-43011: pkcs11: Token login failed
Cause: To login to the pkcs11 token a correct passphrase is needed
Action: Check the token passphrase.
NZE-43014: pkcs11: finding private key on token error
Cause: error occurred while finding private key on token
Action: Make sure the private key corresponding to the certificate in wallet is on the
token. Check trace message
NZE-43015: pkcs11: key pair gen error
Cause: error occurred while generating key pair using HSM
Action: Check trace message
NZE-43017: pkcs11: No certificate found on the smart card/HSM
Cause: No certificate was found on the smart card/HSM.
Action: Follow smart card/HSM vendor documentation to populate the smart
card/HSM with certificate.
NZE-43018: pkcs11: No user certificate found on the smart card/HSM
Cause: No user certificate was found on the smart card/HSM.
Action: Follow smart card/HSM vendor documentation to populate the smart
card/HSM with certificate and private key.
NZE-43000 to NZE-43021 52-1
NZE-43019: pkcs11: No certificate found on smart card/HSM label with given cert
label
Cause: There were no certificate labels on the smart card/HSM that matched the
certificate label specified in the wallet.
Action: Follow smart card/HSM vendor documentation to set certificate label in
smart card/HSM.
NZE-43020: pkcs11: Multiple certificates found on smart card/HSM with given cert
label
Cause: Certificates with identical labels were found in the smart card/HSM.
Action: Follow smart card/HSM vendor documentation to assign unique certificate
labels to certificates.
NZE-43021: pkcs11: Certificate with given cert label is not a user cert
Cause: The certificate with the specified certificate label did not have a matching
private key in the smart card/HSM.
Action: Follow smart card/HSM vendor instructions to create credentials (certificate/
private key) in smart card/HSM.
52-2 Error Messages
53
O2F-00301 to O2F-00341
O2F-00301: Error attempting to read from the INTYPE file
Cause: An operating system error occurred while attempting to read from the
INTYPE file.
Action: Try opening the INTYPE file with an editor to make sure you are able to
access the file.
O2F-00302: Unable to allocate memory
Cause: OTT was unable to allocate memory.
Action: Contact ORACLE customer support.
O2F-00303: No INTYPE file was specified
Cause: The required option INTYPE was not specified.
Action: Set the INTYPE option to the name of the file containing names of types for
OTT to translate. The INTYPE option may be specified on the command line or in a
CONFIG file.
O2F-00304: Invalid filename for the INTYPE file
Cause: The filename specified for the INTYPE file is not syntactically correct.
Action: Make sure you spelled the filename of the INTYPE file correctly.
O2F-00305: Error opening the INTYPE file for reading
Cause: An operating system error occurred while attempting to open the INTYPE file.
Action: Make sure you spelled the filename of the INTYPE file correctly. Try opening
the INTYPE file with an editor to make sure you have access to the file.
O2F-00306: Unable to close the INTYPE file
Cause: An operating system error occurred while attempting to close the INTYPE file.
access the file.
O2F-00307: Unable to read the INTYPE file
Cause: The first token of the INTYPE file was not read. Either an operating system
error occurred while attempting to read from the INTYPE file, or all lines of the
INTYPE file are blank lines or comment lines.
access the file. Make sure the INTYPE file contains one or more type specifications.
O2F-00308: No type specifications were seen in the INTYPE file
Cause: Either there are no type specifications in the INTYPE file, or the first type
specification could not be read due to a previously reported error.
O2F-00301 to O2F-00341 53-1
Action: Fix any previously reported errors. Make sure there are one or more type
specifications in the INTYPE file.
O2F-00309: Name of user-defined type is illegal or missing
Cause: The name of a user-defined type is expected following the keyword TYPE at
the beginning of a type specification. No legal type name was seen.
Action: Make sure that the type specification is syntactically correct, and that the type
name is spelled correctly.
O2F-00310: Illegal or missing identifier name
Cause: A legal C or C++ identifier was expected following AS, but was not seen.
Action: Use a legal C or C++ identifier, consisting of letters, digits, and underscores
not beginning with a digit.
O2F-00311: Illegal or missing file name
Cause: A legal file name was expected, but was not seen.
Action: Make sure your TYPE file syntax is correct. Use a correct file name.
O2F-00312: Illegal or missing type version string
Cause: A type version name was expected, but was not seen.
Action: Make sure your TYPE file syntax is correct. Use a correct version name.
O2F-00313: Illegal or missing attribute name
Cause: An attribute name was expected in the INTYPE file, but was not seen.
Action: Make sure your TYPE file syntax is correct. Use a correct attribute name.
O2F-00314: AS expected but not seen in the INTYPE file
Cause: Incorrect syntax in the INTYPE file.
Action: Make sure your TYPE file syntax is correct.
O2F-00315: An attribute of a type is listed twice in a type specification
Cause: An attribute of a user-defined type is listed twice in a type specification in the
INTYPE file. The second occurrence is ignored.
Action: Remove one of the two occurrences of the attribute.
O2F-00316: An unexpected token was seen at the end of a type specification
Cause: There is a syntax error in the INTYPE file.
Action: Check your documentation to make sure the type specifications in the
INTYPE file are syntactically correct. Check your documentation to make sure the
type specifications
O2F-00317: Error opening the ERRTYPE file for writing
Cause: An operating system error occurred while attempting to open the ERRTYPE
file for writing.
Action: Make sure you spelled the ERRTYPE filename correctly. Try creating or
modifying the ERRTYPE file to make sure you have write access to the file.
O2F-00318: Error writing to the OUTTYPE file
Cause: An operating system error occurred when attempting to write to the
OUTTYPE file.
Action: Make sure you have operating system permission to write to the file. Also,
make sure disk space is available.
53-2 Error Messages
O2F-00319: No OUTTYPE file specified

Cause: The required option OUTTYPE was not specified.
Action: Set the OUTTYPE option to the name of the file to which the TYPE file
produced by OTT should be written. The OUTTYPE option may be specified on the
command line or in a CONFIG file.
O2F-00320: Invalid filename for the OUTTYPE file
Cause: The filename specified for the OUTTYPE file is not syntactically correct.
Action: Make sure you spelled the filename of the OUTTYPE file correctly.
O2F-00321: Error opening the OUTTYPE file for writing
Cause: An operating system error occurred while attempting to open the OUTTYPE
file.
Action: Make sure you spelled the filename of the OUTTYPE file correctly. Make sure
you have operating system permission to open the the file.
O2F-00322: Unable to close the OUTTYPE file
Cause: An operating system error occurred while attempting to close the OUTTYPE
file.
Action: Try opening the OUTTYPE file with an editor to make sure you are able to
access the file.
O2F-00323: Internal error in OTT facility O2F
Cause: An internal OTT error occurred in the O2F component of OTT.
O2F-00324: Unable to convert from the database character set to the compiler
character set
Cause: The name of a type, attribute, or method cannot be converted from the client
character set in effect when OTT was invoked to the compiler character set (typically
ASCII or EBCDIC).
Action: A name is translated first from the database character set to the client
character set, and then from the client character set to the compiler character set. The
client character set is specified in a platform-dependent manner (On UNIX platforms,
the client character set is specified by setting the NLS_LANG environment variable).
Use a client character set that can be translated to the compiler character set. The
compiler character set itself is one such character set. Specify synonyms in the
INTYPE file for any names of database objects that cannot be successfully translated
to the client character set.
O2F-00325: None of the characters in a name were legal identifier characters
Cause: None of the characters in the name of a database entity could be translated to a
character that may begin a C or C++ identifier, such as a letter or an underscore.
Action: Specify an explicit translation for the name in the INTYPE file.
O2F-00326: Some characters in this name were not legal identifier characters
Cause: One or more characters in the name of a database entity could not be
translated to a character that may appear in a C or C++ identifier, such as a letter, an
underscore, or a digit. The characters that could not be translated were replaced with
underscores.
O2F-00301 to O2F-00341 53-3
Action: Make sure that the name is spelled correctly, and that it is terminated by a
blank, the end of a line, or an equals sign ("="). You may use the translated name with
added underscores, or you may specify an explicit translation for the name in the
INTYPE file.
O2F-00327: CASE option has an illegal value
Cause: The value given for the CASE option in the INTYPE file is not legal.
Action: Change the value given for the CASE option to one of the following legal
values: SAME, LOWER, UPPER, or OPPOSITE.
O2F-00328: Illegal INITFUNC name
Cause: The function name given for the INITFUNC option in the INTYPE file is not a
legal C or C++ identifier.
Action: Specify the name of the INITFUNC function as a legal C or C++ identifier.
This name can be given in the INTYPE file, given on the command line, or derived
from the INITFILE name.
O2F-00329: Type or option specification expected
Cause: A type or option specification was expected in the INTYPE file, but was not
seen.
Action: Check the INTYPE file for syntax errors. Supply a type or option specification.
A type specification begins with the word TYPE. An option specification begins with
the word CASE, INITFILE, or INITFUNC.
O2F-00330: Name exceeds 265 bytes in length
Cause: A name seen in the INTYPE file exceeds 265 bytes in length.
Action: Choose a shorter name.
O2F-00331: A syntactically illegal name was seen in the INTYPE file
Cause: A syntax error occurred in a name used in the INTYPE file.
Action: If the name is quoted, make sure that the quotes are at the beginning and at
the end of the name. If a period (which separates a schema name from a type name)
appears, make sure that the schema name and the type name are both present.
O2F-00332: A database link may not appear in the name of a user-defined type
Cause: A database link was seen in the name of a user-defined type. This feature is
not yet supported.
Action: Declare the user-defined type in the database to which OTT connects.
O2F-00333: An unexpected token appeared where a keyword was expected in the
INTYPE file
Cause: A keyword such as TYPE was expected in the INTYPE file, but an incorrect or
misspelled keyword was seen.
Action: Verify that your TYPE specification obeys the syntax described in your
documentation. Verify that your keyword is spelled correctly.
O2F-00334: A user-defined type is listed more than once in the INTYPE file
Cause: The same name of a user-defined type appears in more than one type
specification. The duplicate specifications of the type name will be ignored.
Action: Put all of the information about the type, including all type name and
attribute name translations, in a single TYPE specification, and eliminate the duplicate
TYPE specifications.
53-4 Error Messages
O2F-00335: Internal error in O2F component of OTT

Cause: A request was made that all types in the database schema are to database.
Action: List the types to be processed in an INTYPE file. Contact ORACLE customer
support.
O2F-00336: Error reported by subsystem:\n
Cause: A request was made to generate declarations for all the types in a database
schema. An error occurred in a subsystem when accessing the database.
Action: Examine the error message reported by the sybsystem to determine its cause.
List the types to be processed in an INTYPE file.
O2F-00337: Schema not found, or no types found in schema
Cause: A request was made to generate declarations for all the types in a database
schema. Either the schema was not found, no user-declared types were found in the
schema, or unable to connect to Oracle.
Action: Ensure that a login/password string was specified for OTT and that the
Oracle database can be accessed with it. Ensure that the USER_TYPES table contains
at least one row.
O2F-00338: Illegal or missing package name
Cause: A legal Java package name was expected following IN or PACKAGE or IN
PACKAGE, but was not seen.
Action: Use a legal Java package name.
O2F-00339: CODE option has an illegal value
Cause: The value given for the CODE option in the INTYPE file is not legal.
Action: Change the value given for the CODE option to one of the following legal
values: C, ANSI_C, KR_C, JAVA, NATIVE_JAVA, ORACLE_JAVA.
O2F-00340: Name was null
Cause: A name had a length of 0 characters.
Action: This error should never be reported to the user. Contact ORACLE customer
support.
O2F-00341: An error occurred for which no message is available
Cause: The cause of this error was not reported.
O2F-00301 to O2F-00341 53-5
53-6 Error Messages
54
O2I-00101 to O2I-00133
O2I-00101: Invalid value for the USERID parameter
Cause: The value supplied for the USERID parameter is not a legal username/
password[@databasename] string.
Action: Set the USERID option to the correct username/password or username/
password@database name combination to use when connecting to the database. If you
have an OPS$ account, you may instead omit the USERID option, in which case OTT
will attempt to connect to the database using the userid OPS$username. The USERID
option may be specified on the command line or in a CONFIG file.
O2I-00102: Unable to connect to Oracle
Cause: OTT could not connect to Oracle with the username, password, and, if
applicable, database link that was supplied. Either the USERID option value was
incorrect, or, if the USERID was not supplied, the userid OPS$username was not
accepted.
Action: Check that the username and password are current and correct. Run another
program that connects to Oracle to verify that you can connect using that username
and password.
O2I-00103: Two file names refer to the same HFILE file in the INTYPE file
Cause: Two different file names have been used in the INTYPE file to refer to the
same HFILE file, or different file names have been used to refer to the same HFILE file
on the command line and in the INTYPE file.
Action: Consistently refer to each HFILE file using the same file name.
O2I-00110: Internal error in OTT component O2I
Cause: An internal OTT error occurred in the O2I component of OTT.
O2I-00111: Unable to allocate memory
O2I-00112: Unable to write to the HFILE file
Cause: An operating system error occurred when attempting to write to the HFILE
file.
O2I-00113: No HFILE specified
Cause: The HFILE file to which C declarations generated by OTT are written was not
specified.
O2I-00101 to O2I-00133 54-1
Action: Specify the global HFILE option on the command line or in a CONFIG file.
You may choose a different HFILE for a particular type by specifying a different
HFILE in the INTYPE file entry describing the type. If every INTYPE file entry
specifies an HFILE, and if none of the types in the HFILE require declarations of types
not mentioned there, the global HFILE option may be omitted. An INTYPE file
generated by a previous invocation of OTT satisfies these conditions.
O2I-00114: Invalid HFILE file name
Cause: An HFILE file name was specified that is not syntactically correct.
Action: Make sure the HFILE filename is spelled correctly.
O2I-00115: Error opening the HFILE file
Cause: An operating system error occurred while attempting to open the HFILE file
for writing.
Action: Make sure the HFILE filename is spelled correctly. Try creating or modifying
the HFILE to make sure you have write access to the file.
O2I-00116: Unable to close the HFILE file
Cause: An operating system error occurred while attempting to close the HFILE file.
Action: Try creating or modifying the HFILE file to make sure you are able to access
the file.
O2I-00117: Internal error: No message file for component O2U
Cause: The message file for the internal OTT component O2U was not found. OTT
may not be correctly installed.
O2I-00118: This user-defined type was not found in the database
Cause: A user-defined type specified in the INTYPE file was not found in the
database.
Action: Make sure the name of the type is spelled correctly. Make sure the type is
actually declared in the database.
O2I-00119: Warning reported by subsystem:\n
Cause: A subsystem invoked by OTT reported a warning. This warning immediately
follows the "Warning reported by subsystem" message.
Action: Examine the warning reported by the subsystem to determine its cause.
O2I-00120: Error reported by subsystem:\n
Cause: A subsystem invoked by OTT reported an error. This error immediately
follows the "Error reported by subsystem" message.
Action: Examine the error message reported by the sybsystem to determine its cause.
O2I-00121: No value was specified for the CODE option
Cause: The required CODE option was not specified on the command line or in a
configuration file.
Action: Specify the CODE option on the command line or in a configuration file.
Currently, the following values of the CODE option are supported: CODE=ANSI_C,
CODE=KR_C, CODE=C
O2I-00122: Invalid filename for the INITFILE file
Cause: The filename specified for the INITFILE file is not syntactically correct.
54-2 Error Messages
Action: Make sure the filename of the INITFILE file is spelled correctly.
O2I-00123: Unable to close the INITFILE file
Cause: An operating system error occurred while attempting to close the INITFILE
file.
Action: Try opening the INITFILE file with an editor to make sure the file can be
accessed.
O2I-00124: Error opening the INITFILE file for writing
Cause: An operating system error occurred while attempting to open the INITFILE
file for writing.
Action: Make sure the INITFILE filename is spelled correctly. Try creating or
modifying the INITFILE file to make sure you have write access to the file.
O2I-00125: Error writing to the INITFILE file
Cause: An operating system error occurred when attempting to write to the INITFILE
file.
O2I-00126: You must specify an INTYPE file with
SCHEMA_NAMES=FROM_INTYPE
Cause: The option SCHEMA_NAMES=FROM_INTYPE requests that schema names
be written to the OUTTYPE file as given in the INTYPE file. However, an INTYPE file
was not specified.
Action: Either supply the name of an INTYPE file, or specify the SCHEMA_NAMES
option ALWAYS or IF_NEEDED.
O2I-00127: Illegal INITFUNC name
Cause: The name of the INITFUNC function is not a legal C or C++ identifier.
Action: Specify the name of the INITFUNC function as a legal C or C++ identifier.
This name may be given in the INTYPE file, given on the command line, or derived
from the INITFILE name.
O2I-00128: Unable to write to the Java file
Cause: An operating system error occurred when attempting to write to a Java source
file.
O2I-00129: No Java file specified
Cause: The file to which Java declarations generated by OTT are written was not
specified.
Action: This message should never be seen, because Java files are named after the
classes declared within them. Contact ORACLE customer support.
O2I-00130: Invalid Java file name
Cause: A Java file name was specified that is not syntactically correct.
Action: Make sure the Java filename is spelled correctly.
O2I-00101 to O2I-00133 54-3
O2I-00131: Error opening a Java file

Cause: An operating system error occurred while attempting to open a Java file for
writing.
Action: Make sure the filename is spelled correctly. Try creating or modifying the file
to make sure you have write access to the file.
O2I-00132: Unable to close a Java file
Cause: An operating system error occurred while attempting to close a Java file.
Action: Try creating or modifying the Java file to make sure you are able to access the
file.
O2I-00133: An error occurred for which no message is available
54-4 Error Messages
55
O2U-00200 to O2U-00212
O2U-00200: Internal error in OTT facility O2U
Cause: An internal OTT error occurred in the O2U facility of OTT.
O2U-00201: Illegal arguments to function o2upt()
Cause: Illegal arguments were passed to the function o2upt(). This is an internal error
that should not be encountered by an end user.
O2U-00202: Invalid data passed to function
Cause: Arguments with incorrect values were passed to the function o2upt(). This is
an internal error that should not be encountered by the end user.
O2U-00203: Type to be declared must be an object type or a named collection type
Cause: You have asked OTT to generate code for a type it does not support. When
generating Java code, OTT will only generate code for object types. When generating
C declarations, OTT will only generate declarations for object types and named
collection types.
Action: You are probably asking OTT to declare a built-in type, or, if you are
generating Java code, a named collection type. Do not ask OTT to generate a
declaration for this type.
O2U-00204: Unable to convert from the database character set to the compiler
character set
Cause: The name of a type, attribute, or method cannot be converted from the client
character set in effect when OTT was invoked to the compiler character set (typically
ASCII or EBCDIC).
Action: A name is translated first from the database character set to the client
character set, and then from the client character set to the compiler character set. The
client character set is specified in a platform-dependent manner (On UNIX platforms,
the client character set is specified by setting the NLS_LANG environment variable.)
Use a client character set that includes the character set of the INTYPE file and can be
translated to the compiler character set. The database character set is one such
character set. Specify synonyms in the INTYPE file for any names of database objects
that cannot be successfully translated to the client character set.
O2U-00205: None of the characters in a type name were legal identifier characters
Cause: None of the characters in the name of a user-defined type could be translated
to a character that can begin a C or C++ identifier, such as a letter or an underscore.
Action: Specify an explicit translation for the type name in the INTYPE file.
O2U-00200 to O2U-00212 55-1
O2U-00206: Some characters in a type name were not legal identifier characters
Cause: One or more characters in the name of a user-define type could not be
translated to a character that can appear in a C or C++ identifier, such as a letter, an
underscore, or a digit. The characters that could not be translated were replaced with
underscores.
Action: Specify an explicit translation for the type name in the INTYPE file, or just use
the translated type name with added underscores.
O2U-00207: None of the characters in an attribute name were legal identifier
characters
Cause: None of the characters in the name of an attribute of a type could be translated
to a character that can begin a C or C++ identifier, such as a letter or an underscore.
To find the affected attribute, look in the declaration generated for this type for data
member names that are obviously incorrect.
Action: Specify an explicit translation for the attribute name in the INTYPE file.
O2U-00208: One or more characters in an attribute name were not legal identifier
characters
Cause: If an attribute name contains one or more characters that can not be translated
to a legal C or C++ identifier character, the characters that can not be translated are
replaced with underscores. To find the affected attribute or attributes, look in the
declaration generated for this type for data member names that have extra
underscores not present in the original attribute names.
Action: Specify explicit translations for the affected attribute names in the INTYPE
file, or just use the translated attribute names with added underscores.
O2U-00209: Attribute or function name to be translated was not found
Cause: This name, for which a translation was requested, is not the name of an
attribute or a function of the current type.
Action: Make sure that the name is spelled correctly, and is the name of an attribute
or function defined in the current type.
O2U-00210: Unable to allocate memory
O2U-00211: A type without attributes was translated
Cause: OTT translated a type without attributes. The corresponding C-type will be a
struct without any components, which is not legal C. The empty type in the database
may be the result of an error during type creation. Additionally, incomplete types
may be used temporarily in the creation of types that reference one another.
Action: Re-create a full version of the type in the database and then re-run OTT.
O2U-00212: An error occurred for which no message is available
55-2 Error Messages
56
OCI-00601 to OCI-31199
OCI-00601: cleanup lock conflict
Cause: PMON process runs into lock conflict trying to recover processes.
Action: This is trapped internally, no action necessary.
OCI-00602: internal programming exception
Cause: Internal programming exception.
Action: Report as a bug. Caution: The following error code is not relocatable.
OCI-00972: identifier is too long
Cause: An identifier with more than 30 characters was specified.
OCI-01841: (full) year must be between -4713 and +9999, and not be 0
Cause: Illegal year entered
Action: Input year in the specified range
OCI-01854: julian date must be between 1 and 5373484
Cause: An invalid Julian date was entered.
Action: Enter a valid Julian date between 1 and 5373484.
OCI-01858: a non-numeric character was found where a numeric was expected
Cause: The input data to be converted using a date format model was incorrect. The
input data did not contain a number where a number was required by the format
model.
Action: Fix the input data or the date format model to make sure the elements match
in number and type. Then retry the operation.
OCI-01859: a non-alphabetic character was found where an alphabetic was expected
input data did not contain a letter where a letter was required by the format model.
OCI-01861: literal does not match format string
Cause: Literals in the input must be the same length as literals in the format string
(with the exception of leading whitespace). If the "FX" modifier has been toggled on,
the literal must match exactly, with no extra whitespace.
Action: Correct the format string to match the literal.
OCI-00601 to OCI-31199 56-1
OCI-01862: wrong number of digits for this format item

Cause: The number of digits used for this format item is not equal to the number
necessary for this format when specifying Format eXact ("FX") for this item.
Action: Fill out this format item with leading zeros to the number necessary for this
format. (This is generally the number of characters in the format code--DD needs 2
digits, for example. The exceptions are HH24 & HH12, which both need 2, and J,
which needs 9.)
OCI-01864: the date is out of range for the current calendar
Cause: Your calendar doesn't extend to the specified date.
Action: Specify a date which is legal for this calendar.
OCI-01865: not a valid era
Cause: Era input does not match a known era.
Action: Provide a valid era on input.
OCI-01867: the interval was invalid
Cause: The character string you specified is not a valid interval.
Action: Please specify a valid interval.
OCI-01868: the leading precision of the interval was too small
Cause: The leading precision of the interval is too small to store the specified interval.
Action: Increase the leading precision of the interval or specify an interval with a
smaller leading precision.
OCI-01870: the intervals or datetimes were not mutually comparable
Cause: The intervals or datetimes are not mutually comparable.
Action: Specify a pair of intervals or datetimes that are mutually comparable.
OCI-01871: the 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 smaller.
OCI-01873: the leading precision of the interval was too small
OCI-01874: time zone hour must be between -12 and 14
Cause: The time zone hour specified was not in the valid range.
Action: Specify a time zone hour between -12 and 14.
OCI-01875: time zone minute must be between -59 and 59
Cause: The time zone minute specified was not in the valid range.
Action: Specify a time zone minute between -59 and 59.
OCI-01876: year must be at least -4713
Cause: The specified year was not in range.
Action: Specify a year that is greater than or equal to -4713.
56-2 Error Messages
OCI-01878: specified field not found in datetime or interval

Cause: The specified field was not found in the datetime or interval.
Action: Make sure that the specified field is in the datetime or interval.
OCI-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.
OCI-01880: the fractional seconds must be between 0 and 999999999
Cause: The specified fractional seconds were not in the valid range.
Action: Specify a value for fractional seconds between 0 and 999999999.
OCI-01881: time zone region ID is invalid
Cause: The region ID referenced an invalid region.
OCI-01882: time zone region not found
Cause: The specified region name was not found.
OCI-01883: overlap was disabled during a region transition
Cause: The region was changing state and the overlap flag was disabled.
OCI-01884: divisor is equal to zero
Cause: An attempt was made to divide by zero.
Action: Avoid zero divisor.
OCI-01890: NLS error detected
Cause: An NLS error was detected.
Action: Look for additional error messages and take appropriate action. If there are no
additional errors, call Oracle Support Services.
OCI-01898: too many precision specifiers
Cause: While trying to truncate or round dates, extra data was found in the date
format picture
Action: Check the syntax of the date format picture and retry.
OCI-02083: database name has illegal character 'string'
Cause: Supplied database name can contain only A-Z, 0-9, '_', '#', '$' '.' and '@'
characters.
Action: n/a
OCI-02084: database name is missing a component
Cause: Supplied database name cannot contain a leading '.', trailing '.' or '@', or two '.'
or '@' in a row.
Action: n/a
OCI-00601 to OCI-31199 56-3
OCI-04020: deadlock detected while trying to lock object

stringstringstringstringstring
Cause: While trying to lock a library object, a deadlock is detected.
Action: Retry the operation later.
OCI-04021: timeout occurred while waiting to lock object
Cause: While waiting to lock a library object, a timeout is occurred.
OCI-04022: nowait requested, but had to wait to lock dictionary object
Cause: Had to wait to lock a library object during a nowait request.
OCI-04028: cannot generate diana for object stringstringstringstringstring
Cause: Cannot generate diana for an object because of lock conflict.
Action: Please report this error to your support representative.
OCI-04029: error ORA-string occurred when querying stringstringstring
Cause: The table or view being queried might be missing. The error number indicates
the error.
Action: Fix the error.
OCI-04030: out of process memory when trying to allocate string bytes
(string,string)
Cause: Operating system process private memory has been exhausted
Action: n/a
OCI-04031: unable to allocate string bytes of shared memory
("string","string","string")
Cause: More shared memory is needed than was allocated in the shared pool.
Action: Either use the dbms_shared_pool package to pin large packages, reduce your
use of shared memory, or increase the amount of available shared memory by
increasing the value of the init.ora parameter "shared_pool_size".
OCI-04054: database link string does not exist
Cause: During compilation of a PL/SQL block, an attempt was made to use a nonexistent database link.
Action: Either use a different database link or create the database link.
OCI-04060: insufficient privileges to execute string
Cause: Attempt to execute a stored procedure without sufficient privileges.
Action: Get necessary privileges.
OCI-04061: existing state of string has been invalidated
Cause: Attempt to resume the execution of a stored procedure using the existing state
which has become invalid or inconsistent with the stored procedure because the
procedure has been altered or dropped.
Action: Try again; this error should have caused the existing state of all packages to
be re-initialized.
56-4 Error Messages
OCI-04062: timestamp of string has been changed

Cause: Attempt to execute a stored procedure to serve an RPC stub which specifies a
timestamp that is different from the current timestamp of the procedure.
Action: Recompile the caller in order to pick up the new timestamp.
OCI-04063: string has errors
Cause: Attempt to execute a stored procedure or use a view that has errors. 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's defining query
to a non-existent table.
Action: Fix the errors and/or create referenced objects as necessary.
OCI-04064: not executed, invalidated string
Cause: Attempt to execute a stored procedure that has been invalidated.
Action: Recompile it.
OCI-04065: not executed, altered or dropped string
Cause: Attempt to execute a stored procedure that has been altered or dropped thus
making it not callable from the calling procedure.
Action: Recompile its dependents.
OCI-04066: non-executable object, string
Cause: Attempt to execute a non-procedure.
Action: Make sure that a correct name is given.
OCI-04067: not executed, string does not exist
Cause: Attempt to execute a non-existent stored procedure.
OCI-04068: existing state of packagesstringstringstring has been discarded
Cause: One of errors 4060 - 4067 when attempt to execute a stored procedure.
Action: Try again after proper re-initialization of any application's state.
OCI-19200: Invalid column specification
Cause: All input arguments must be valid columns
Action: Specify a valid list of columns
OCI-19201: Datatype not supported
Cause: The particular datatype is not supported in the XMLGEN operator
Action: Specify only supported datatypes as arguments to the XMLGEN operator
OCI-19202: Error occurred in XML processingstring
Cause: An error occurred when processing the XML function
Action: Check the given error message and fix the appropriate problem
OCI-19203: Error occurred in DBMS_XMLGEN processingstring
Cause: An error occurred when processing the DBMS_XMLGEN functions
OCI-00601 to OCI-31199 56-5
OCI-19204: Non-scalar value 'string' is marked as XML attribute

Cause: Only scalar values (i.e. values which are not of object or collection type) can be
marked as XML attribute,i.e. is prefixed by '@'. In this case, a non-scalar value was
prefixed with '@'
Action: Remove the '@' sign, or make the value a scalar.
OCI-19205: Attribute 'string' qualifies a non-scalar value in the select list
Cause: The attribute immediately follows a value of object or collection type in the
select list or type definition.
Action: Remove the '@' sign, or make the previous value a scalar.
OCI-19206: Invalid value for query or REF CURSOR parameter
Cause: The queryString argument passed to DBMS_XMLGEN.newContext was not a
valid query, or REF CURSOR.
Action: Rewrite the query so that the queryString argument is a valid query or REF
CURSOR.
OCI-19207: scalar parameter string of XMLELEMENT cannot have an alias.
Cause: The scalar parameter to XMLELEMENT has been qualified with an alias.
Action: Remove the AS clause of the scalar element.
OCI-19208: parameter string of function string must be aliased
Cause: The indicated parameter of the XML generation function has not been aliased,
although it is an expression.
Action: Specify an alias for the expression using the AS clause.
OCI-19209: invalid or unsupported formatting argument
Cause: An invalid or unsupported formatting argument was supplied
Action: Change the formatting argument to legal supported values
OCI-19210: column 'string', specified to be a key or update column for
DBMS_XMLSTORE, does not not exist in table 'string'
Cause: The column specified using setKeyColumn()/setUpdateColumn() did not exist
in the table.
Action: Change the column specified to be a column in the table
OCI-19211: column 'string', specified as key using
DBMS_XMLSTORE.setKeyColumn() , must be of scalar type
Cause: The column specified using setKeyColumn() was a non-scalar type column.
Action: Change the column specified to be a scalar column in the table
OCI-19212: no key columns specified before call to
DBMS_XMLSTORE.updateXML()
Cause: No columns were specified as key columns before the call to
DBMS_XMLSTORE.updateXML.
Action: Use DBMS_XMLSTORE.setKeyColumn() to specify key columns
OCI-21300: objects option not installed
Cause: The objects option is not installed at this site. Object types and other object
features are, therefore, unavailable.
56-6 Error Messages
Action: Install the objects option. The objects option is not part of the Oracle Server
product and must be purchased separately. Contact an Oracle sales representative if
the objects option needs to be purchased.
OCI-21301: not initialized in object mode
Cause: This function requires the oci process to be initialized in object mode.
Action: Specify OCI_OBJECT mode when calling OCIInitialize().
OCI-21500: internal error code, arguments: [string], [string], [string], [string],
Cause: This is the generic error number for the OCI environment (client-side) internal
errors. This indicates that the OCI environment has encountered an exceptional
condition.
OCI-21501: program could not allocate memory
OCI-21503: program terminated by fatal error
Cause: A program is in an unrecoverable error state.
Action: Report as a bug.
OCI-21520: database server driver not installed
Cause: User attempted to access a database server through an object-mode OCI
environment but the necessary driver for supporting such access to the database
server is not installed or linked in.
Action: Check if the driver corresponding to the database server has been installed/
linked in and entered in the server driver table.
OCI-21521: exceeded maximum number of connections in OCI (object mode only)
Cause: User exceeded the maximum number of connections (255) that can be
supported by an OCI environment in object mode.
Action: Close some of existing and unused connections before opening more
connections.
OCI-21522: attempted to use an invalid connection in OCI (object mode only)
Cause: User attempted to use an invalid connection or a connection that has been
terminated in an OCI environment (object mode), or user attempted to dereference a
REF obtained from a connection which has been terminated.
Action: Ensure that the connection exists and is still valid.
OCI-21523: functionality not supported by the server (object mode only)
Cause: User attempted to use a functionality that the server does not support.
Action: Upgrade the server
OCI-21524: object type mismatch
Cause: The object type of the object is different from what is specified.
Action: Check the type of the object and correct it.
OCI-00601 to OCI-31199 56-7
OCI-21525: attribute number (or collection element at index) string violated its
constraints
Cause: Attribute value or collection element value violated its constraint.
Action: Change the value of the attribute or collection element such that it meets its
constraints. The constraints are specified as part of the attribute or collection element's
schema information.
OCI-21526: initialization failed
Cause: The initialization sequence failed. This can happen, for example, if an
environment variable such as NLS_DATE_FORMAT is set to an invalid value.
Action: Check that all NLS environment variables are well-formed.
OCI-21527: internal OMS driver error
Cause: A process has encountered an exceptional condition. This is the generic
internal error number for Oracle object management services exceptions.
Action: Report this as a bug to Oracle Support Services.
OCI-21560: argument string is null, invalid, or out of range
Cause: The argument is expecting a non-null, valid value but the argument value
passed in is null, invalid, or out of range. Examples include when the LOB/FILE
positional or size argument has a value outside the range 1 through (4GB - 1), or
when an invalid open mode is used to open a file, etc.
Action: Check your program and correct the caller of the routine to not pass a null,
invalid or out-of-range argument value.
OCI-21562: column string has unsupported data type string
Cause: A data type was specified which is currently unsupported.
Action: Choose another data type which is supported.
OCI-21563: Error string while calling string for column string with datatype string
Cause: OCI Error encountered while performing data type conversion.
Action: Check the OCI Error code
OCI-21570: current string LCR has unreceived chunk data
Cause: The client did not receive all the chunk data for the current LCR.
Action: If OCIXStreamOutLCRCallbackReceive is used in your program then modify
your callback functions to return OCI_CONTINUE while
OCI_XSTREAM_MORE_ROW_DATA flag is set; otherwise, modify your program to
call OCIXStreamOutChunkReceive until all the chunks are received (that is, the flag
returned by OCIXStreamOutChunkReceive API does not have
OCI_XSTREAM_MORE_ROW_DATA bit set).
OCI-21571: must provide a LOB WRITE, LOB TRIM or LOB ERASE LCR in string
call (input LCR=string)
Cause: An attempt was made to invoke the specified function without providing a
piece-wise LOB LCR (for example, LOB WRITE, LOB TRIM or LOB ERASE LCR).
Action: Correct the 'row_lcrp' argument in the call.
OCI-21572: Invalid LCR type (string) in string call
Cause: An attempt was made to invoke the specified function with an incorrect
logical change record (LCR) type.
56-8 Error Messages
Action: Provide an LCR of the correct type.

OCI-21573: Invalid command type (string) when sending a chunk.
Cause: An attempt was made to send a chunk when the command type for the
current LCR was not INSERT, UPDATE, or LOB WRITE.
Action: Check your program and provide an LCR with a valid command type to
OCIXStreamInChunkSend call or to OCICallbackXStreamInChunkCreate callback.
OCI-21574: Invalid data type (string) specified for LOB chunk.
Cause: Invalid data type specified for LOB chunk in OCIXStreamInChunkSend call.
Action: Check your program and provide either SQLT_CHR or SQLT_BIN for 'coldty'
argument to OCIXStreamInChunkSend call.
OCI-21577: Input string LCR has no LOB column.
Cause: An attempt was made to invoke OCILCRLobInfoGet call with an LCR that had
no LOB column.
Action: Replace the input LCR to OCILCRLobInfoGet call.
OCI-21578: Only one LOB column allowed per string LCR.
Cause: An attempt was made to set multiple LOB columns on a piece-wise LOB LCR.
Action: Check your program and make sure OCIXStreamInChunkSend is called for
only one column per piece-wise LOB LCR.
OCI-21579: Input LCR must have at least one old or new column.
Cause: An attempt was made to call OCIXStreamInChunkSend with an LCR that had
empty column lists.
Action: Use OCILCRRowColumnInfoSet to add one or more columns to the input
LCR before calling OCIXStreamInChunkSend.
OCI-21580: The LOB operation length (value=string) for column (string) must be an
even number of bytes.
Cause: An attempt was made to call OCIXStreamInChunkSend with an odd number
of bytes for a column flagged as AL16UTF16 or NCLOB.
Action: Correct either the LOB column length or 'column_flag' argument to
OCIXStreamInChunkSend call.
OCI-21583: invalid XStream server name 'string'
Cause: An attempt was made to attach to an XStream server with a nonexistent server
name.
Action: Correct the server name in the attach call.
OCI-21600: path expression too long
Cause: The path expression that is supplied by the user is too long. The path
expression is used to specify the position of an attribute in an object. This error occurs
when one of the intermediate elements in the path expression refers to an attribute of
a built-in type. Thus, the OCI function cannot proceed on to process the rest of the
elements in the path expression.
Action: User should pass in the correct path expression to locate the attribute.
OCI-00601 to OCI-31199 56-9
OCI-21601: attribute is not an object

Cause: The user attempts to perform an operation (that is valid only for an object) to
an attribute of a built-in type. An example of such an illegal operation is to
dynamically set a null structure to an attribute of a built-in type.
Action: User should avoid performing such operation to an attribute of built-in type.
OCI-21602: operation does not support the specified typecode
Cause: The user attempts to perform an operation that does not support the specified
typecode.
Action: User should use the range of valid typecodes that are supported by this
operation.
OCI-21603: property id [string] is invalid
Cause: The specified property id is invalid.
Action: User should specify a valid property id. Valid property ids are enumerated by
OCIObjectPropId.
OCI-21604: property [string] is not a property of transient or value instances
Cause: Trying to get a property which applies only to persistent objects.
Action: User should check the lifetime and only get this property for persistent
objects.
OCI-21605: property [string] is not a property of value instances
Cause: Trying to get a property which applies only to persistent and transient objects.
Action: User should check the lifetime and only get this property for persistent and
transient objects.
OCI-21606: can not free this object
Cause: Trying to free an object that is persistent and dirty and the
OCI_OBJECTFREE_FORCE flag is not specified.
Action: Either flush the persistent object or set the flag to OCI_OBJECTFREE_FORCE
OCI-21607: memory cartridge service handle not initialized
Cause: Attempt to use the handle without initializing it.
Action: Initialize the memory cartridge service handle.
OCI-21608: duration is invalid for this function
Cause: Attempt to use a duration not valid for this function.
Action: Use a valid duration - a previously created user duration or
OCI_DURATION_STATEMENT or OCI_DURATION_SESSION. For callout duration
or external procedure duration, use OCIExtProcAllocCallMemory.
OCI-21609: memory being resized without being allocated first
Cause: Attempt to resize memory without allocating it first.
Action: Allocate the memory first before resizing it.
OCI-21610: size [string] is invalid
Cause: Attempt to resize memory with invalid size.
Action: Pass in a valid size (must be a positive integer).
OCI-21611: key length [string] is invalid

Cause: Attempt to use an invalid key length.
Action: Key length is invalid and valid range is 0 to 64
OCI-21612: key is already being used
Cause: Attempt to use a key that is already used.
Action: Use a new key that is not yet being used.
OCI-21613: key does not exist
Cause: Attempt to use a non-existent key
Action: Use a key that already exists.
OCI-21700: object does not exist or is marked for delete
Cause: User attempted to perform an inappropriate operation to an object that is nonexistent or marked for delete. Operations such as pinning, deleting and updating
cannot be applied to an object that is non-existent or marked for delete.
Action: User needs to re-initialize the reference to reference an existent object or the
user needs to unmark the object.
OCI-21701: attempt to flush objects to different servers
Cause: User attempted to flush objects to different servers in one function call. These
objects are obtained by calling a callback functions provided by the program.
Action: User should avoid performing such operation.
OCI-21702: object is not instantiated or has been de-instantiated in cache
Cause: User attempted to perform an inappropriate operation to a transient object
that is not instantiated in the object cache. Operations that cannot be applied to a notinstantiated transient object include deleting or pinning such an object.
Action: User should check their code to see if they are performing such an operation
without instantiating the object first, or performing such an operation after the
allocation duration of the object has expired.
OCI-21703: cannot flush an object that is not modified
Cause: See the error message.
Action: The object should not be flushed.
OCI-21704: cannot terminate cache or connection without flushing first
Action: The transaction should be aborted or committed before terminating the cache
or connection.
OCI-21705: service context is invalid
Cause: The service context that is supplied by the user is not valid.
Action: User needs to establish the service context.
OCI-21706: duration does not exist or is invalid
Cause: The duration number that is supplied by the user is not valid.
Action: User needs to establish the duration or use a correct predefined duration.
OCI-00601 to OCI-31199 56-11
OCI-21707: pin duration is longer than allocation duration

Cause: The pin duration supplied by the user is longer than the allocation duration.
This affects operations such as pinning and setting default parameters.
Action: User should use a shorter pin duration or use the null duration.
OCI-21708: inappropriate operation on a transient object
Cause: User attempted to perform an inappropriate operation on a transient object.
Operations that cannot be applied to a transient object include flushing and locking.
Action: User should avoid performing such operation on a transient object.
OCI-21709: cannot refresh an object that has been modified
Cause: User attempted to refresh an object that has been marked for delete, update or
insert (new).
Action: User should unmark the object before refreshing it.
OCI-21710: argument is expecting a valid memory address of an object
Cause: The object memory address that is supplied by the user is invalid. The user
may have passed in a bad memory address to a function that is expecting a valid
memory address of an object.
Action: User should pass in a valid memory address of an object to the function.
OCI-21779: duration not active
Cause: User is trying to use a duration that has been terminated.
OCI-22053: overflow error
Cause: This operation's result is above the range of Oracle number.
Action: Decrease the input value(s) so that the result is in the range of Oracle number.
OCI-22054: underflow error
Cause: This operation's result is below the range of Oracle number.
Action: Increase the input value(s) so that the result is in the range of Oracle number.
OCI-22055: unknown sign flag value [string]
Cause: Signed flag used is not OCI_NUMBER_SIGNED or
OCI_NUMBER_UNSIGNED.
Action: Use either OCI_NUMBER_SIGNED or OCI_NUMBER_UNSIGNED as sign
flag.
OCI-22056: value [string] is divided by zero
Cause: Given value is divied by zero.
Action: Modify divisor value to be non-zero.
OCI-22057: bad integer length [string]
Cause: The length of the integer (ie number of bytes) to be converted to or from an
Oracle number is invalid.
Action: Use integer length 1, 2, 4 or 8 bytes only.
OCI-22059: buffer size [string] is too small - [string] is needed
Cause: The buffer to hold the resulting text string is too small.
Action: Provide a buffer of the required size.
OCI-22060: argument [string] is an invalid or uninitialized number

Cause: An invalid or uninitialized number is passed in.
Action: Use a valid number. To initialize number call OCINumberSetZero().
OCI-22061: invalid format text [string]
Cause: The numeric format string for converting characters to or from an Oracle
number is invalid.
Action: Use valid format string as documented in OCI Programmer's Guide.
OCI-22062: invalid input string [string]
Cause: The text string for converting to numbers is invalid.
Action: Use a valid input string as documented in OCI Programmer's Guide.
OCI-22063: reading negative value [string] as unsigned
Cause: Attempt to convert a negative number to an unsigned integer.
Action: Use the sign flag ORLTSB to convert a signed number.
OCI-22064: invalid NLS parameter string [string]
Cause: The NLS parameter string for converting characters to or from an Oracle
number is invalid.
OCI-22065: number to text translation for the given format causes overflow
Cause: Rounding done due to the given string format causes overflow.
Action: Change the format such that overflow does not occur.
OCI-22130: buffer size [string] is less than the required size [string]
Cause: The size of the buffer into which the hexadecimal REF string is to be written is
too small.
OCI-22131: hexadecimal string length is zero
Cause: The given hexadecimal string length must be greater than zero.
Action: Specify a length greater than zero.
OCI-22132: hexadecimal string does not correspond to a valid REF
Cause: The given hexadecimal string is invalid.
Action: Provide a valid hexadecimal string which was previously returned by a call to
OCIRefToHex().
OCI-22140: given size [string] must be in the range of 0 to [string]
Cause: The given resize size is invalid.
Action: Ensure that the given size is in the required range.
OCI-22141: given size [string] must be even in UTF-16 environment
Cause: The given resize size is odd. In a UTF-16 environment, all characters are 2
bytes in length.
Action: Ensure that the given size is even.
OCI-00601 to OCI-31199 56-13
OCI-22150: variable-length array has not been initialized

Cause: An un-initialized variable-length array is being operated upon.
Action: Initialize the variable-length array prior to calling this function.
OCI-22151: cannot resize non-zero variable-length array to zero elements
Cause: Trying to resize a non-zero variable-length array to 0 elements.
Action: Specify a non-zero size.
OCI-22152: destination variable-length array is not initialized
Cause: The variable-length array on the right-hand-side of an assignment or the
destination array of an append is not initialized.
Action: Initialize the destination variable-length array prior to calling this function.
OCI-22153: source variable-length array is not initialized
Cause: The variable-length array on the left-hand-side of an assignment or the source
array of an append is not initialized.
OCI-22160: element at index [string] does not exist
Cause: Collection element at the given index does not exist.
Action: Specify the index of an element which exists.
OCI-22161: type code [string] is not valid
Cause: Given type code is not valid.
Action: Use one of the typecodes enumerated in OCITypeCode.
OCI-22162: element at index [string] has been previously deleted
Cause: Trying to delete a non-existent collection element.
Action: Check for the existence of the element prior to calling this function.
OCI-22163: left hand and right hand side collections are not of same type
Cause: Left hand and right side collections are not of same type.
Action: Ensure that the same collection type is passed for both left hand and right
hand side of this function.
OCI-22164: delete element operation is not allowed for variable-length array
Cause: Trying to delete an element of a variable-length array.
Action: Ensure that the collection is not a variable-length array prior to calling this
function.
OCI-22165: given index [string] must be in the range of [string] to [string]
Cause: Given index is not in the required range.
Action: Ensure that the given index is in the required range.
OCI-22166: collection is empty
Cause: Given collection is empty.
Action: Test if collection is empty prior to invoking this function.
OCI-22167: given trim size [string] must be less than or equal to [string]
Cause: Given trim size is greater than the current collection size.
Action: Ensure that the given size is less than or equal to the collection size prior to
calling this function.
OCI-22275: invalid LOB locator specified
Cause: There are several causes: (1) the LOB locator was never initialized; (2) the
locator is for a BFILE and the routine expects a BLOB/CLOB/NCLOB locator; (3) the
locator is for a BLOB/CLOB/NCLOB and the routine expects a BFILE locator; (4)
trying to update the LOB in a trigger body -- LOBs in trigger bodies are read only.
Action: For (1), initialize the LOB locator by selecting into the locator variable or by
setting the LOB locator to empty. For (2) and (3), pass the correct type of locator into
the routine. For (4), remove the trigger body code that updates the LOB value.
OCI-22276: invalid locator for LOB buffering
Cause: There are several causes: (1) the locator was never enabled for buffering (2) it
is not an updated locator but is being used for a write/flush operation
Action: For (1) enable the locator for buffering; (2) ensure that only an updated locator
is used for a LOB update operation
OCI-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 LOB buffering, modify the LOB through one LOB locator only.
OCI-22278: must update the LOB only through the LOB buffers
Cause: LOB buffering is enabled for this LOB and there are buffers for this LOB in the
buffer pool. Thus, updating the LOB through means other than the 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, buffers associated with this LOB
should either be flushed as necessary or buffering should be disabled. Once this is
done, reissue the command.
OCI-22279: cannot perform operation with LOB buffering enabled
Cause: The operation attempted is not allowed when LOB buffering is enabled.
Action: If the operation is required, LOB buffering should not be used. In this case,
flush buffers associated with the input LOB locator as necessary, disable buffering on
the input LOB locator and reissue the command.
OCI-22280: no more buffers available for operation
Cause: There are two causes: (1) All buffers in the buffer pool have been used up by
previous operations (2) Attempt to flush a LOB without any previous buffered update
operations.
Action: For (1), flush the LOB(s) through the locator that is being used to update the
LOB. For (2), write to the LOB through a locator enabled for buffering before
attempting to flush buffers.
OCI-22281: cannot perform operation with an updated locator
Cause: The input locator has buffering enabled and was used to update the LOB
value through the LOB buffering subsystem. The modified buffer has not been
flushed since the write that was performed by the the input locator; thus, the input
locator is considered an updated locator. Updated locators cannot be the source of a
copy operation. Only one locator per LOB may be used to modify the LOB value
through the LOB buffering subsystem.
OCI-00601 to OCI-31199 56-15
Action: Depending on whether the modifications made through the input locator to
the LOB buffering subsystem should be written to the server, either flush the buffer to
write the modifications, or, disable buffering on the locator to discard the
modifications. Then, reissue the command.
OCI-22282: non-contiguous append to a buffering enabled LOB not allowed
Cause: The buffered write operation has an input offset value more than one byte or
character past the end of the LOB.
Action: Specify an input offset value which is exactly one character or byte greater
than the length of the LOB that you are attempting to update through a buffered write
operation.
OCI-22285: non-existent directory or file for string operation
Cause: Attempted to access a directory that does not exist, or attempted to access a
file in a directory that does not exist.
Action: Ensure that a system object corresponding to the specified directory exists in
the database dictionary, or make sure the name is correct.
OCI-22286: insufficient privileges on directory or file to perform string operation
Cause: The user does not have the necessary access privileges on the directory alias
and/or the file for the operation.
Action: Ask the database/system administrator to grant the required privileges on the
directory alias and/or the file.
OCI-22287: invalid or modified directory occurred during string operation
Cause: The directory alias used for the current operation is not valid if being accessed
for the first time, or has been modified by the DBA since the last access.
Action: If you are accessing this directory for the first time, provide a valid directory
name. If you have been already successful in opening a file under this directory
before this error occured, then close the file and retry the operation with a valid
directory alias as modified by your DBA. Oracle recommends that directories should
be modified only during quiescent periods.
OCI-22288: file operation string failed\nstring
Cause: The operation attempted on the file failed.
Action: See the next error message for more detailed information. Also, verify that the
file exists and that the necessary privileges are set for the specified operation. If the
error still persists, report the error to the DBA.
OCI-22289: cannot perform string operation on an unopened file
Cause: The file is not open for the required operation to be performed.
Action: Check that the current operation is preceded by a successful file open
operation.
OCI-22290: operation would exceed the maximum number of opened files
Cause: The number of open files has reached the maximum limit.
Action: Close some of the opened files and retry the operation.
OCI-22303: type "string"."string" not found
Cause: The user is trying to obtain information for a type that cannot be found.
Action: Check that the schema is correct and that the type has been created correctly.
OCI-22305: attribute/method/parameter "string" not found

Cause: Type element with the given name is not found in the type.
Action: Check to make sure that the type element exists.
OCI-22306: type "string"."string" already exists
Cause: The user is trying to create a type that already exists.
Action: Check to make sure that the type has not been created prior to this.
OCI-22307: type to alter is not a user-defined type
Cause: The user is trying to alter a built-in type.
Action: Check to make sure that only user-defined types are being altered.
OCI-22309: attribute with name "string" already exists
Cause: The user is attempting to create an object type where more than one attributes
have the same name.
Action: Check to make sure that all attribute names are unique.
OCI-22311: type for attribute "string" does not exist
Cause: The type of the attribute does not exist.
Action: No types were created/modified for this DDL transaction. Redo the DDL
transaction and add the creation of the attribute's type in the DDL transaction.
OCI-22313: cannot use two versions of the same type "string"
Cause: The version of this type conflicts with the version of this type used by another
library that was linked in with the application. An application may only use one
version of a type.
Action: Check that the libraries being linked with this application and use the same
versions of the type.
OCI-22314: method information mismatch in ALTER TYPE
Cause: The number of methods or the method signature do not match that of the
original type declaration. This is not supported.
Action: Make sure the method signature stay identical for the previously declared
method. Do not drop existing methods.
OCI-22315: type "string" does not contain a map or order function
Cause: The input type does not contain a map or order function so one cannot be
returned.
Action: Add a map or order function to the type or catch this error.
OCI-22316: input type is not a collection type
Cause: The user is trying to obtain information for collection types on a non-named
collection type.
Action: Use a named collection type for the function.
OCI-22317: typecode number is not legal as a number type
Cause: The user is trying to use a number typecode that is not valid.
Action: Use only OCI_TYPECODE_SMALLINT, OCI_TYPECODE_INTEGER,
OCI_TYPECODE_REAL, OCI_TYPECODE_DOUBLE, OCI_TYPECODE_FLOAT,
OCI_TYPECODE_NUMBER, or OCI_TYPECODE_DECIMAL.
OCI-00601 to OCI-31199 56-17
OCI-22318: input type is not an array type

Cause: The user is trying to obtain the number of elements for a non-array type.
Action: Pass in only a named collection type which is an array.
OCI-22319: type attribute information altered in ALTER TYPE
Cause: The type attribute information does not match that of the original type
declaration when altering type. Attributes cannot be altered during ALTER TYPE.
Only new methods can be added.
Action: Check that all type alterations are legal.
OCI-22321: method does not return any result
Cause: OCITypeResult() was called on a method that does not return any results.
Action: Check that you are passing in the correct method descriptor, or that your
method creation was done correctly.
OCI-22337: the type of accessed object has been evolved
Cause: The type of the accessed object has been altered and the client's object is based
on an earlier type definition.
Action: The user needs to exit application and modify application to accommodate
the type change. From SQL/PLUS, reconnect and resubmit statement.
OCI-22351: This API is not supported by the ORACLE server.
Cause: An attempt was made to call an API which is not supported by the Oracle
server.
Action: Do not call the unsupported API when connected to this Oracle server.
OCI-22352: Type is unsupported or contains an unsupported attribute or element.
Cause: A PL/SQL package type was not supported on the client or contained an
attribute or element that was not supported on the client. Unsupported types include
index by VARCHAR2 collections, remote types and MLSLABELs.
Action: Do not attempt to use unsupported PL/SQL package types or types that
contain unsupported attributes or elements on the client.
OCI-22369: invalid parameter encountered in method string
Cause: An invalid parameter is being passed to this method of SYS.RowType or
SYS.RowSet.
Action: Check the parameters being passed to this method and make sure that the
parameters are allowed.
OCI-22370: incorrect usage of method string
Cause: This method of SYS.RowType or SYS.RowSet is being used inappropriately.
Action: Check the documentation for correct usage.
OCI-22600: encountered 8.0.2 (Beta) VARRAY data that cannot be processed
Cause: Production Oracle8 (8.0.3 and beyond) encounters some VARRAY data which
was created and stored by Oracle8 8.0.2 (Beta 2). Production Oracle8 cannot
understand or process such VARRAY data.
Action: Delete the VARRAY data from the table by dropping the table, deleting the
rows, or nulling out the VARRAY columns, and then re-insert the VARRAY data.
There is no provided script or tool to help automate this conversion.
OCI-22601: pickler TDS context [string] is not initialized

Cause: Attempt to use the pickler TDS context without initializing it.
Action: Use OCIPicklerTdsCtxInit to initialize the context.
OCI-22602: pickler TDS handle [string] is not well-formed
Cause: Attempt to use the pickler TDS handle without initializing/ constructing it.
Action: Use OCIPicklerTdsInit to initialize the handle before it is constructed. Use
OCIPicklerTdsGenerate to generate the TDS before its attributes can be accessed.
OCI-22603: cannot add an attribute to the already generated TDS handle
Cause: Attempt to add an attribute to the already constructed TDS.
Action: Use a TDS handle that is initialized but not yet constructed.
OCI-22604: TDS handle already generated
Cause: Attempt to geneate TDS that is already genearated.
Action: Use a TDS handle that is initialized but not yet generated.
OCI-22605: FDO handle [string] is not initialized
Cause: Attempt to use an uninitialized FDO handle.
Action: Use OCIPicklerFdoInit to initialize FDO handle".
OCI-22606: pickler image handle [string] is not well-formed
Cause: Attempt to use the image handle without initializing/ constructing it.
Action: Use OCIPicklerImageInit to initialize the handle before it is constructed. Use
OCIPicklerImageGenerate to generate the image before its attributes can be accessed.
OCI-22607: image handle already generated
Cause: Attempt to geneate image that is already genearated.
Action: Use a image handle that is initialized but not yet generated.
OCI-22608: cannot add an attribute to the already generated image handle
Cause: Attempt to add an attribute to the already constructed image.
Action: Use an image handle that is initialized but not yet constructed.
OCI-22609: error string during initialization of FDO
Cause: Error during FDO initialization.
Action: Take an action based on the specified error.
OCI-22626: Type Mismatch while constructing or accessing OCIAnyData
Cause: Type supplied is not matching the type of the AnyData. If piece wise
construction or access is being attempted, the type supplied is not matching the type
of the current attribute.
Action: Make sure the type supplied matches the type of object to to be constucted or
accessed.
OCI-22975: cannot create a PRIMARY KEY-based REF to this object view
Cause: The object view specified in the MAKE_REF function does not have a
PRIMARY KEY-based object identifier. A PRIMARY KEY-based REF cannot be
created for such a view.
Action: Specify an object view that has a PRIMARY KEY-based object identifier in the
MAKE_REF function.
OCI-00601 to OCI-31199 56-19
OCI-22976: incorrect number of arguments to MAKE_REF

Cause: Number of arguments for MAKE_REF is different from the number of
PRIMARY KEY attributes of the object view.
Action: Specify all the necessary arguments for MAKE_REF.
OCI-29783: GPnP attribute SET failed with error [string]
Cause: An attempt to set the Grid Plug and Play (GPnP) attribute failed. See the
brackets for the reason.
Action: Resolve the problem in the included message and retry the request.
OCI-29785: GPnP attribute GET failed with error [string]
Cause: An attempt to get the Grid Plug and Play (GPnP) attribute failed. See the
brackets for the reason.
OCI-29786: SIHA attribute GET failed with error [string]
Cause: An attempt to get the Single-Instance High Availability (SIHA) attribute failed.
See the brackets for the reason.
OCI-29787: SIHA attribute SET failed with error [string]
Cause: An attempt to set the Single-Instance High Availability (SIHA) attribute failed.
See the brackets for the reason.
OCI-30100: internal error [number]
Action: Contact Oracle Worldwide Support and report the error.
OCI-30101: unknown parameter name 'string'
Cause: You have misspelled the parameter name.
Action: Spell the parameter name correctly.
OCI-30102: 'string' is not in the legal range for 'string'
Action: Refer to the manual for the allowable values for this parameter.
OCI-30103: 'string' contains an illegal integer radix for 'string'
Cause: An illegal integer radix specification was found.
Action: Only 'd', 'h', 'D', and 'H' may be used as radix specifications.
OCI-30104: 'string' is not a legal integer for 'string'
Cause: The value is not a valid integer.
Action: Specify only valid integers for this parameter.
OCI-30105: 'string' is not a legal boolean for 'string'
Cause: The value is not a valid boolean.
Action: Refer to the manual for allowable boolean values.
OCI-30106: reserved for future use

Cause: None.
Action: None
OCI-30107: parameter name abbreviation 'string' is not unique
Cause: The abbreviation given was not unique.
Action: Use a longer abbreviation to make the parameter name unique.
OCI-30108: invalid positional parameter value 'string'
Cause: An invalid positional parameter value has been entered.
Action: Remove the invalid positional parameter.
OCI-30109: could not open parameter file 'string'
Cause: The parameter file does not exist.
Action: Create an appropriate parameter file.
OCI-30110: syntax error at 'string'
OCI-30111: no closing quote for value 'string'
Cause: A quoted string was begun but not finished.
OCI-30112: multiple values not allowed for parameter 'string'
Cause: You attempted to specify multiple values for a parameter which can take only
one value.
Action: Do not specify more than one value for this parameter.
OCI-30113: error when processing file 'string'
Cause: A problem occurred when processing this file.
OCI-30114: error when processing from command line
Cause: A problem occurred when processing the command line.
OCI-30115: error when processing an environment variable
Cause: A problem occurred when processing an environment variable.
OCI-30116: syntax error at 'string' following 'string'
OCI-30117: syntax error at 'string' at the start of input
OCI-00601 to OCI-31199 56-21
OCI-30118: syntax error at 'string' at the end of input

OCI-30119: unable to obtain a valid value for 'string'
Cause: No valid value was obtained for this parameter.
Action: Rerun the application and enter a valid value.
OCI-30120: 'string' is not a legal oracle number for 'string'
Cause: The value is not a valid oracle number.
Action: Refer to the manual for allowable oracle number values.
OCI-30121: 'string' is not an allowable value for 'string'
Cause: The value is not a legal value for this parameter.
Action: Refer to the manual for allowable values.
OCI-30122: value 'string' for 'string' must be between 'number' and 'number'
Action: Specify a value that is within the legal range.
OCI-30129: invalid function argument received
Cause: A function received an invalid argument
Action: Check function calls, make sure correct arguments are being passed.
OCI-30130: invalid parameter key type received
Cause: A function received an invalid parameter key type
Action: Check parameter key types in function calls
OCI-30131: number of keys being set exceeds allocation
Cause: Number of parameter keys being set exceeds allocation
Action: Reduce the number of keys being set or increase allocation
OCI-30132: invalid key index supplied
Cause: The key index specified was not within bounds
Action: Change key index to ensure it lies within bounds
Cause: None.
Action: None
Cause: None.
Action: None
OCI-30135: OCI Thread operation fails
Cause: An OCI Thread function call has failed.
Action: Check the function call to make sure that the correct parameters are being
passed and take the apropriate action.
OCI-30150: Invalid argument passed to OCIFile function

Cause: An invalid argument is passed to the OCIFile function. The most common
cause is that a NULL pointer is passed where a non-NULL pointer is expected.
Action: Make sure that the values passed as arguments are valid. Esp check for NULL
pointers.
OCI-30151: File already exists
Cause: Tried to open a file with OCI_FILE_EXCL flag and the file already exists.
Action: OCIFile is supposed throw this exception in this case.
OCI-30152: File does not exist
Cause: The OCIFile function requires the file to exist, but it does not.
Action: Make sure that the file exists.
OCI-30153: An invalid File Object is passed to the OCIFile function
Cause: An invalid File Object is passed to the OCIFile function.
Action: Make sure that the file object is a valid one. Create a new file object by calling
OCIFileOpen if needed.
OCI-30154: The memory address given as buffer for OCIFileRead/Write is invalid
Cause: An invalid memory address is given as the buffer pointer for OCIFileRead/
Write.
Action: Make sure that the required memory is allocated and pass a valid memory
address as buffer pointer.
OCI-30155: An I/O Error occured during an OCIFile function call
Cause: An I/O error occurred at the system level.
Action: This is a system error and the action will depnd on the error.
OCI-30156: Out of disk space
Cause: The disks associated with the underlying file system are full.
Action: Create more disk space.
OCI-30157: An invalid argument was given to operating system call
Cause: The OS call was called with an invalid argument.
Action: Check the values passed. If unsuccessful to solve the problem contact
ORACLE support.
OCI-30158: The OCIFileWrite causes the file to exceed the maximum allowed size
Cause: There is no space to write to the file. Its size is at the maximum limit.
Action: Up to the user.
OCI-30159: OCIFileOpen: Cannot create the file or cannot open in the requested
mode
Cause: The create flag was specified in OCIFileOpen such that the file was to be
created. But unable to do so. Or the file already exists and the permissions on it
doesn't allow the file to be opened in in the requested open mode
Action: Check whether the user has permissions to create the specified file or if the
file exists whether the permissions on it allow the requested open mode.
OCI-00601 to OCI-31199 56-23
OCI-30160: Unable to access the file

Cause: The function was unable to access the existing the file.
Action: Check if the user has the required permissions on the file.
OCI-30161: A system error occurred during the OCIFile function call
Cause: A system error occured while executing the OCIFile function.
Action: Depend on the error.
OCI-30162: The OCIFile context is not initialzed
Cause: The function OCIFileInit need to be called before calling any other OCIFile
function to initialize the OCIFile context.
Action: Call the function OCIFileInit need to be called before calling any other
OCIFile function.
OCI-30163: The thread safety initialization failed
Cause: The call to SlgInit failed in OCIFileInit.
OCI-30175: invalid type given for an argument
Cause: There is an argument with an invalid type in the argument list.
Action: Use the correct type wrapper for the argument.
OCI-30176: invalid format code used in the format string
Cause: There is an invalid format code in the format string.
Action: Replace the invalid format code with a valid one.
OCI-30177: invalid flag used in a format specification
Cause: There is an invalid flag in a format specification.
Action: Replace the invalid flag with a valid one.
OCI-30178: duplicate flag used in a format specification
Cause: There is a duplicate flag in a format specification.
Action: Remove the duplicate flag.
OCI-30179: invalid argument index used in a format code
Cause: Zero or negative argument index or index not following (."
Action: Replace the invalid argument index with a valid one.
OCI-30180: argument index is too large
Cause: An argument index exceeds actual number of arguments supplied.
Action: Fix format string or pass additional arguments.
OCI-30181: integer in argument index is not immediately followed by )
Cause: Missing closing parenthesis in argument index.
Action: Fix the format specification.
OCI-30182: invalid precision specifier
Cause: Period in format specification not followed by valid format.
Action: Replace the invalid precision specifier with a valid one.
OCI-30183: invalid field width specifier

Cause: Invalid field width supplied.
Action: Replace the invalid field width with a valid one.
OCI-30184: argument type not compatible with a format code
Cause: Bad argument type given for a format code.
Action: Make format and arguments be compatible.
OCI-30185: output too large to fit in the buffer
Cause: The buffer is not large enough to hold the entire output string.
Action: Fix the buffer size and length passed in.
Cause: None.
Action: None
Cause: None.
Action: None
Cause: None.
Action: None
Cause: None.
Action: None
Cause: None.
Action: None
OCI-30191: missing argument list
Cause: No argument list supplied.
Action: Modify the argument list to have at least OCIFormatEnd in it.
Cause: None.
Action: None
Cause: None.
Action: None
Cause: None.
Action: None
Cause: None.
OCI-00601 to OCI-31199 56-25
Action: None
Cause: None.
Action: None
Cause: None.
Action: None
Cause: None.
Action: None
Cause: None.
Action: None
OCI-30930: XML node 'string' (type=string) does not support this operation
Cause: The given node's type is not supported for this operation. For example, trying
to add children to an attribute node, or passing in a document node as a child, are
unsupported operations.
Action: Use a valid node type for the operation.
OCI-30931: Element 'string' cannot contain mixed text
Cause: XML elements must be declared mixed to contain multiple text nodes
Action: Declare this element type as mixed in its schema
OCI-30932: Reference node 'string' not contained in specified parent node 'string'
Cause: When using a reference node, it must have the specified parent node
Action: Use a node in the specified parent as the reference
OCI-30933: Element 'string' may not appear at this point within parent 'string'
Cause: The ordering specified by the content model of the parent does not allow for
this element to occur at this position.
Action: Reorder the child elements to conform with the content model of the parent
element
OCI-30934: 'string' (string node) cannot be inserted in parent 'string' (string node)
Cause: The schema does not allow a child node of this type to be inserted into a
parent node of this type. For example, only element nodes may only be inserted into a
document
Action: Insert only child nodes that make sense for this node type
OCI-30935: XML maxoccurs value (string) exceeded
Cause: An attempt was made to insert more than maxoccurs values into a schemabased XML document.
Action: Do not insert more than maxoccurs values into the document.
OCI-30936: Maximum number (string) of 'string' XML node elements exceeded

Cause: An attempt was made to insert more than the allowed number of elements
(specified by the maxoccurs facet) into an XML document.
Action: Do not attempt to add more than the maximum number of elements to XML
documents.
OCI-30937: No schema definition for 'string' (namespace 'string') in parent 'string'
Cause: The schema definition for the parent node being processed does not allow for
the specified child node in its content model. Note that any typecasting via xsi:type
must occur before the schema definitions for the new type can be used.
Action: Only insert elements and attributes declared in the schema. Check to make
sure that xsi:type (if used) is specified first.
OCI-30938: No prefix defined for namespace 'string' (particle string)
Cause: An XML namespace mapping (xmlns:prefix=namespace URL) must be defined
for each particle (element or attribute) stored in an schema-constrained XMLType
document.
Action: Add an xmlns attribute definition (attribute name="xmlns:prefix" and
value="namespace URL") to the current XMLType document. The safest place to add
this attribute is in the root node of the document to ensure that the mapping will be in
scope.
OCI-30939: Order violation: Element 'string' may not follow element 'string'
Cause: The XML schema specifies a content model that is sequential, where the order
of nodes in the instance must follow the order specified by the schema, and this
instance relies on the schema validity to avoid maintaining instance order information
Action: Insert elements only in the order specified in the schema
OCI-30940: Cannot resolve prefix 'string' for QName node 'string'
Cause: An attempt was made to store a QName value without having a valid
namespace in scope for that prefix.
Action: Declare the namespace for the prefix used
OCI-30941: Cannot specify empty URI for non-default namespace 'string'
Cause: An attempt was made to insert a namespace declaration for a non-default
namespace using an empty URI string.
Action: Specify a non-empty URI for namespace declarations other than the default
namespace.
OCI-30942: XML Schema Evolution error for schema 'string' table string column
'string'
Cause: The given XMLType table/column which conforms to the given schema had
errors during evolution. For more information, see the more specific error below this
one
Action: Based on the schema, table and column information in this error and the more
specific error below, take corrective action
OCI-30943: XML Schema 'string' is dependent on XML schema 'string'
Cause: Not all dependent schemas were specified and/or the schemas were not
specified in dependency order, i.e., if schema S1 is dependent on schema S, S must
appear before S1.
OCI-00601 to OCI-31199 56-27
Action: Include the previously unspecified schema in the list of schemas and/or
correct the order in which the schemas are specified. Then retry the operation.
OCI-30944: Error during rollback for XML schema 'string' table string column
'string'
Cause: The given XMLType table/column which conforms to the given schema had
errors during a rollback of XML schema evolution. For more information, see the
more specific error below this one
Action: Based on the schema, table and column information in this error and the more
specific error below, take corrective action
OCI-30945: Could not create mapping table 'string'
Cause: A mapping table could not be created during XML schema evolution. For
more information, see the more specific error below this one
Action: Ensure that a table with the given name does not exist and retry the operation
OCI-30946: XML Schema Evolution warning: temporary tables not cleaned up
Cause: An error occurred after the schema was evolved while cleaning up temporary
tables. The schema evolution was successful
Action: If the user needs to remove the temporary tables, use the mapping table to get
the temporary table names and drop them.
OCI-30951: Element or attribute at Xpath string exceeds maximum length
Cause: An attempt was made to insert a node of length exceeding the maximum
length (specified by the maxLength facet) into an XML document.
Action: Do not attempt to add a node exceeding the maximum length to XML
documents.
OCI-30990: insufficient privileges to change owner of resource string
Cause: An attempt was made to change the Owner field of an XML DB resource
without sufficient privileges to do so.
Action: Switch to SYS before performing the ownership change, or have the intended
recipient of the resource perform the transfer.
OCI-30991: cannot use DOM to add special attribute to schema-based parent
Cause: An attempt was made to add or remove an xsi:schemaLocation,
xsi:noNamespaceSchemaLocation, xsi:type, or xsi:nil attribute to or from a schemabased XML node using DOM.
Action: Use the updateXML operator instead of DOM.
OCI-31000: Resource 'string' is not an XDB schema document
Cause: The given schema URL does not refer to a registered XDB schema
Action: Make sure the specified schema has been registered in XDB
OCI-31001: Invalid resource handle or path name "string"
Cause: An invalid resource handle or path name was passed to the XDB hierarchical
resolver.
Action: Pass a valid resouce handle or path name to the hierarchical resolver.
OCI-31002: Path name string is not a container
Cause: XDB expected the given path name to represent a container.
Action: Pass a path name or resource handle that represents a container.
OCI-31003: Parent string already contains child entry string

Cause: An attempt was made to insert a duplicate child into the XDB hierarchical
resolver.
Action: Insert a unique name into the container.
OCI-31004: Length string of the BLOB in XDB$H_INDEX is below the minimum
string
Cause: In the XDB$H_INDEX table, the CHILDREN column, a BLOB, must have a
certain minimum length without being chained. The calculated length of the LOB was
less than the stated minimum.
Action: Set the value of the init.ora parameter db_block_size to at least 2K. For XDB to
run at its fastest, set db_block_size to 8K.
OCI-31005: Path name length string exceeds maximum length string
Cause: The length of a path name passed to the XDB hierarchical resolver exceeded
the maximum length.
Action: Choose a shorter path name.
OCI-31006: Path name segment length string exceeds maximum length string
Cause: The length of a path name segment passed to the XDB hierarchical resolver
exceeded the maximum length of a path name segment.
Action: Choose a shorter path name segment.
OCI-31007: Attempted to delete non-empty container string/string
Cause: An attempt was made to delete a non-empty container in the XDB hierarchical
resolver.
Action: Either perform a recursive deletion, or first delete the contents of the
container.
OCI-31009: Access denied for property string
Cause: An attempt was made to access a property you don't have access to
Action: Check the ACL to see what privileges you have for this property
OCI-31010: XML element index string exceeds maximum insertion index string
Cause: An attempt was made to insert an XML element at an invalid index location in
the node.
Action: Choose a new index that falls within the allowed range.
OCI-31011: XML parsing failed
Cause: XML parser returned an error while trying to parse the document.
Action: Check if the document to be parsed is valid.
OCI-31012: Given XPATH expression not supported
Cause: XPATH expression passed to the function is currently unsupported.
Action: Check the xpath expression and change it to use a supported expression.
OCI-31013: Invalid XPATH expression
Cause: XPATH expression passed to the function is invalid.
Action: Check the xpath expression for possible syntax errors.
OCI-00601 to OCI-31199 56-29
OCI-31014: Attempted to delete the root container

Cause: An attempt was made to delete the root container in the hierarchical index.
Action: Do not delete the root container.
OCI-31015: Attempted to insert entry without name
Cause: An attempt was made to insert an entry into the hierarchical resolver without
a child name.
Action: Supply a child name and try inserting again.
OCI-31016: Attempted to delete entry without name
Cause: An attempt was made to delete an entry from the hierarchical resolver without
a child name.
Action: Supply a child name and try deleting again.
OCI-31017: Error generating unique OID for XML document
Cause: An error occurred while generating a globally unique OID for storing an XML
document.
Action: n/a
OCI-31018: Error deleting XML document
Cause: The XMLType object pointed to by the given REF could not be deleted because
either the REF was invalid or it pointed to a non-existent table.
Action: Either use FORCE deletion or supply a valid REF.
OCI-31019: Recursive deletion snapshot too old for string/string
Cause: Changes were made to the structure of a directory while it was being
recursively deleted.
Action: Try deleting the directory again.
OCI-31020: The operation is not allowed, Reason: string
Cause: The operation attempted is not allowed
Action: See reason and change to a valid operation.
OCI-31021: Element definition not found
Cause: The element definition was not found.
Action: Supply the definition for the element or use a defined element.
OCI-31022: Element not found
Cause: The element was not found.
Action: Make sure the specified element exists.
OCI-31023: Index size error
Cause: The index is greater than the allowed value.
Action: Make sure the index is less than allowed value.
OCI-31025: Invalid document element
Cause: An attempt was made to replace the data at an invalid index number in the
XML document
Action: Supply a correct occurrence number and try again.
OCI-31027: Path name or handle string does not point to a resource

Cause: An attempt was made to retrieve a resource based on a path name or resource
handle that points to an entity other than a resource.
Action: Do not attempt to retrieve a resource based on that path name or resource
handle.
OCI-31028: Resource metadata length string exceeded maximum length string
Cause: An attempt was made to insert resource metadata that exceeded the maximum
length of that type of metadata.
Action: Keep resource metadata within its allowed length.
OCI-31029: Cannot bind to unsaved resource
Cause: An attempt was made to bind to a resource that had not been saved to disk.
Action: Bind only to saved resources.
OCI-31030: Unable to retrieve XML document
Cause: The resource had an invalid (dangling) REF to an XML document.
Action: Rebind the resource using a valid XMLType REF.
OCI-31033: Requested number of XML children string exceeds maximum string
Cause: An attempt was made to add more than the maximum number of allowable
children in an XML element.
Action: Redefine the schema to allow breaking up of the children among siblings.
OCI-31035: Could not bind locked resource to path string/string
Cause: An attempt was made to bind an existing resource to a new location in the
hierarchy, but a lock could not be obtained on the resource.
Action: Commit or roll back the transaction that has the lock on the resource.
OCI-31037: Invalid XML attribute name string
Cause: The attribute name in the XML document did not match anything in the
associated schema.
Action: Supply only schema-defined or XML standard attributes.
OCI-31038: Invalid string value: "string"
Cause: The text in the XML document did not represent a valid value given the
datatype and other constraints in the schema.
Action: Ensure that the specified value in XML documents is valid with respect to the
datatype and other constraints in the schema.
OCI-31039: XML namespace length string exceeds maximum string
Cause: The length of the disk-formatted XML namespace exceeded the maximum.
Action: Keep XML namespace declarations below the maximum length.
OCI-31040: Property string: XML type (string) not compatible with internal memory
type (string)
Cause: The XML datatype given is inconsistent with the database datatype, and a
conversion cannot be made.
Action: This is an internal error, generally resulting from corruption of the compiled
XML schema. Re-register schemas, or contact Oracle support.
OCI-00601 to OCI-31199 56-31
OCI-31041: Property string: Memory type (string) not compatible with database
type (string)
Cause: The memory type associated with this property is mapped to an incompatible
database type, and a conversion cannot be made.
Action: This is an internal error, generally resulting from corruption of the compiled
XML schema. Re-register schemas, or contact Oracle support.
OCI-31042: Too many properties in type 'string'
Cause: The type can only have the same number of properties (elements and
attributes) as a table can have columns.
Action: Modify the XML schema to move properties into subelements that are not
inlined.
OCI-31043: Element 'string' not globally defined in schema 'string'
Cause: The specified element name has not been defined at the top level of the XML
schema (i.e. globally). Elements must be defined globally to be the root of an
XMLType object.
Action: Check the XML schema definition to make sure the specified element name
has been defined at the top level.
OCI-31044: Top-level prefix length string exceeds maximum string
Cause: An attempt was made to save to disk a top-level XML namespace prefix whose
length exceeded the maximum.
Action: Do not define XML namespace prefixes that exceed the maximum length.
OCI-31045: Cannot store more than string extras outside the root XML node
Cause: An attempt was made to store more than the maximum number of XML extras
(e.g. comments and processing instructions) either before or after the document's root
node.
Action: Keep the number of extras outside the root node below the maximum.
OCI-31046: Incorrect argument(s) specified in the operator
Cause: One or more of the arguments specified in the operator in the query are
incorrect
Action: Correct the arguments specified in the operator
OCI-31047: Could not retrieve resource data at path string
Cause: An error occurred while retrieving the contents and/or metadata of a
resource.
Action: Contact Oracle customer support.
OCI-31048: Unsaved resources cannot be updated
Cause: An attempt was made to update a resource that was never saved to disk.
Action: Perform a resource insertion instead.
OCI-31050: Access denied
Cause: The requested access privileges have not been granted to the current user.
User must be granted privileges prior to resource access.
Action: Check the set of requested access privileges to make sure that they are
included in the set of access privilges granted to the user.
OCI-31051: Requested access privileges not supported

Cause: The requested access privileges are not supported for the specified resource.
Action: Ensure that the set of requested access privileges are valid access privileges
for the specified resource.
OCI-31052: Cannot delete ACL with other references
Cause: The requested deletion of an ACL resource cannot proceed. The ACL is in use
by other resources.
Action: Remove the resources that are making reference to the ACL in question and
try again.
OCI-31053: The value of the depth argument in the operator cannot be negative
Cause: The value of the depth argument passed to the primary operator is not a
positive integer
Action: Pass a positive value of the depth argument
OCI-31054: The string operator cannot have an ancillary operator
Cause: An ancillary operator was used with an operator which does not does not
support ancillary operators
Action: Remove the ancillary operator in the query
OCI-31055: A null XMLType element cannot be inserted into RESOURCE_VIEW
Cause: The element which is being inserted into the RESOURCE_VIEW is NULL
Action: Specify a non-null XMLType element to insert into RESOURCE_VIEW
OCI-31056: The document being inserted does not conform to string
Cause: The XMLType element being inserted into the RESOURCE_VIEW does not
conform to the specified Schema
Action: Insert an element which conforms to the specified Schema
OCI-31057: Display Name of the element being inserted is null
Cause: The Display Name of the element which is being inserted into the
RESOURCE_VIEW is null
Action: Specify the Display Name and insert the element into RESOURCE_VIEW
OCI-31058: cannot modify read-only XOBs
Cause: Read-Only XOBs cannot be modified.
Action: Use only read operations on such a XOB.
OCI-31059: Cannot insert root XML document node if it already exists
Cause: An attempt was made to insert a root node into an XML document that
already had a root node.
Action: Call the appropriate replace function to replace the node instead of inserting it
anew.
OCI-31060: Resource at path string could not be deleted
Cause: An error occurred while deleting the named resource. The specific error can be
found one lower on the error stack.
Action: Look at the next error on the stack and take approprate action.
OCI-00601 to OCI-31199 56-33
OCI-31061: XML event error

Cause: The specified error occurred in XDB.
Action: Correct the error or contact Oracle Support Services.
OCI-31062: Cannot delete an unsaved resource
Cause: An attempt was made to delete a resource that had not been saved to disk.
Action: Delete only saved resources.
OCI-31065: Cannot modify read-only property [string]
Cause: An attempt was made to modify an immutable XML node.
Action: Use only read operations on such properties.
OCI-31066: Insertion of string into string creates a cycle
Cause: An attempt was made to insert a link into the XDB hierarchy that would create
a cycle in the tree.
Action: Ensure that links to existing resources do not cause cycles.
OCI-31067: XML nodes must be updated with nodes of the same type
Cause: An attempt was made to use updateXML to update an XML node with a node
of another type.
Action: Ensure that the node specified by the XPath matches the type of new data
provided.
OCI-31068: updateXML expected data format [string] instead of [string]
Cause: An attempt was made to use updateXML to update data with a node of the
incorrect type. Text and attribute nodes must be updated with string data, whereas
element nodes must be updated with XMLType data.
Action: Use CREATEXML or getStringVal to coerce the new data to the proper
format.
OCI-31069: Cannot apply typed changes to non-schema-based XMLType nodes
Cause: An attempt was made to insert, delete, or update a non-schema-based
XMLType node using an XML schema definition.
Action: Make changes to non-typed nodes only by referencing their tag names.
OCI-31070: Invalid database user ID string
Cause: An attempt was made set an invalid user ID into an XDB resource metadata
property.
Action: Verify the validity of the user ID and try again.
OCI-31071: Invalid database username or GUID string
Cause: An attempt was made to set an invalid username or GUID into an XDB
resource metadata property.
Action: Verify the validity of the username or GUID and try again.
OCI-31072: Too many child nodes in XMLType fragment for updateXML
Cause: An attempt was made to pass an XMLType fragment with multiple children as
new data for the updateXML operator.
Action: Extract the desired child from the XMLType before passing it to updateXML
as the desired new XML node.
OCI-31073: Resource not retrieved using path name

Cause: An attempt was made to access the path name of a resource that was either
never saved to disk or was loaded using a method other than with its path name.
Action: Perform path name operations only on resources obtained using a path name.
OCI-31075: invalid string declaration in XML Schema
Cause: The XML schema contains an invalid declaration identified by the message.
Action: Fix the identified error and try again.
OCI-31076: required attribute "string" not specified
Cause: The XML schema does not specify a required attribute.
Action: Specify a value for the required attribute.
OCI-31077: invalid attribute "string" specified
Cause: The XML schema specifies an invalid attribute.
Action: Remove specification of the invalid attribute.
OCI-31078: error in SQL mapping information
Cause: There is an error in the SQL type and table specification within the XML
Schema.
Action: Ensure that all specified SQL types and tables are valid and compatible with
the corresponding XML types.
OCI-31079: unable to resolve reference to string "string"
Cause: The identified type or attribute or element could not be resolved.
Action: Make sure that the name corresponds to a valid XML (simple/complex) type
or attribute or element and try again.
OCI-31080: type not specified for attribute or element "string"
Cause: The identified attribute or element does not have a type.
Action: Make sure that every attribute and element has a valid type specification.
OCI-31081: name not specified for global declaration
Cause: The XML schema does not specify the name for the global declaration of
attribute or element or simpleType or complexType.
Action: Specify names for all global declarations.
OCI-31082: invalid attribute "string" specified in declaration of "string"
Cause: The XML schema specifies an invalid attribute.
Action: Remove specification of the invalid attribute.
OCI-31083: error while creating SQL type "string"."string"
Cause: An error occurred while trying to create the SQL type based on the
specification of a complex type.
OCI-31084: error while creating table "string"."string" for element "string"
Cause: An error occurred while trying to create the table based on the declaration for
the identified element.
OCI-00601 to OCI-31199 56-35
OCI-31085: schema "string" already registered

Cause: An attempt was made to register a schema with the same URL as a previously
registered schema.
Action: Register the schema with a different URL.
OCI-31086: insufficient privileges to register global schema "string"
Cause: An attempt was made to register a global schema without sufficient privileges.
Action: Make sure that the user has sufficient privileges to register a global schema.
OCI-31087: insufficient privileges to delete schema "string"
Cause: An attempt was made to delete a schema resource without sufficient
privileges.
Action: Make sure that the user has sufficient privileges to delete the schema.
OCI-31088: object "string"."string" depends on the schema
Cause: An attempt was made to delete a schema which has dependent objects.
Action: Either drop the dependent objects prior to deleting the schema or use the
CASCADE or FORCE options.
OCI-31089: schema "string" does not target namespace "string"
Cause: The schema document contains references (via include and import definitions)
to other schemas that do not belong to valid namespaces.
Action: Make sure that all schemas referenced via include definitions target the same
namespace as the parent schema. Further make sure that the namespace specified in
the import definition matches the actual target namespace of the specified schema.
OCI-31090: invalid database schema name "string"
Cause: The XML schema document contains an invalid database schema name For
example, the value of attribute SQLSchema
Action: Make sure that all database user/schema names specified in the XML schema
document refer to existing database users/schemas.
OCI-31091: empty string specified as a SQL name
Cause: The XML schema document contains a null SQL name. For example, the
values of attributes SQLName, SQLType, defaultTable.
Action: Make sure that all names of SQL schema objects specified in the XML schema
document are valid SQL names. Otherwise, remove such attributes from the schema
and try again.
OCI-31092: invalid SQL name "string"
Cause: The XML schema document contains an invalid SQL name. For example, the
values of attributes SQLName, SQLType, defaultTable.
Action: Make sure that all names of SQL schema objects specified in the XML schema
document are valid SQL names. This implies that the database length and other
restrictions on names be satisfied.
OCI-31093: null or invalid value specified for parameter : string
Cause: The argument value passed for the given parameter is null or invalid.
Action: Make sure that all the input argument values are valid.
OCI-31094: incompatible SQL type "string" for attribute or element "string"

Cause: The SQL type information provided in the XML schema is not compatible with
the XML datatype for the specified attribute or element.
Action: Make sure that the specified SQL types are compatible with the declared XML
datatypes.
OCI-31095: cannot generate string : "string.string" already exists
Cause: The type/table name specified in the XML schema document cannot be
generated because it is already being used.
Action: Use different names for types/tables or use the NOGEN mode so that schema
compiler does not generate new types/tables.
OCI-31096: validation failed for schema
Cause: The XML Schema could not be validated.
Action: Make sure that the SQLType and other datatype mapping is valid.
OCI-31097: Hierarchical Index not empty
Cause: An attempt was made to rebuild the hierarchical index which is not empty.
Action: Delete all rows in the hierarchical index and then rebuild it.
OCI-31099: XDB Security Internal Error
Cause: An XDB Security internal error has occurred.
OCI-31100: XDB Locking Internal Error
Cause: An XDB Locking Internal error has occurred.
OCI-31101: Token "string" not given while locking resource "string"
Cause: Locking attempted on resource when the pricipal already owns a lock given
by the token above.
Action: Reattempt the lock with the token.
OCI-31102: Already locked in exclusive mode. Cannot add lock.
Cause: The resource is already locked in exclusive mode. Cannot add another lock.
Action: Unlock the existing lock.
OCI-31103: Resource locked in shared mode. Cannot add exclusive lock
Cause: The resource is locked in shared mode. Cannot add a shared lock.
Action: Try locking in shared mode or unlocking the existing lock.
OCI-31104: Cannot find lock with token "string" on "string" for unlock
Cause: The lock may have been unlock or it may have expired.
Action: No action needed. Unlock already successful.
OCI-31105: User does not own lock "string"
Cause: The lock to be unlocked is not owned by the user.
Action: n/a
OCI-00601 to OCI-31199 56-37
OCI-31107: Action failed as resource "string" is locked by name lock

Cause: Lock requests cause the whole request URI to be locked
Action: Supply lock token or unlock the lock
OCI-31108: Action failed as resource string is locked
Cause: Delete/Rename failed because of an existing lock
Action: Do lockdiscovery to find the lock and delete it.
OCI-31109: Action failed as parent resource string is locked
Cause: Delete/Rename failed because of an lock on parent resource
OCI-31110: Action failed as resource string is locked by name
Cause: Delete/Rename failed because one of the children is locked.
OCI-31111: table string cannot be hierarchically enabled
Cause: Trigger tabname_xdb_pitrigger already exists
Action: Either the table is already hierarchically enabled or the user trigger
tabname_xdb_pitrigger needs to be dropped. Delete all rows in the hierarchical index
and then rebuild it.
OCI-31112: fail to string for string port using xdb configuration
Cause: port number for the defined presentation is not valid
Action: Either the port number is already in use or it is protected. Specify another port
number.
OCI-31113: XDB configuration may not be updated with non-schema compliant
data
Cause: An attempt was made to update the XDB configuration resource with nonschema or non-schema compliant data.
Action: Check the document to make sure it is schema based and schema compliant.
OCI-31114: XDB configuration has been deleted or is corrupted
Cause: The XDB configuration resource has been deleted or corrupted.
Action: Reinstall XDB, or reinsert a valid configuration document.
OCI-31115: XDB configuration error: string
Cause: An error related to XDB configuration has occurred.
Action: Make sure the configuration resource contains valid data.
OCI-31116: Tablespace not specified correctly
Cause: XDB cannot be moved to the specified tablespace.
Action: Specify a valid tablespace.
OCI-31121: The string operator can not be FALSE
Cause: The value of the operator that is specified is FALSE
Action: Specify an operator that evaluates to TRUE
OCI-31122: The string operator has incorrect RHS value

Cause: The right hand side value that has been specified for the operator does not
evaluate to TRUE
Action: Specify value on the right hand side that evaluate to TRUE
OCI-31151: Cyclic definition encountered for string: "string"
Cause: The schema definition for this type has cycles.
Action: Remove cyclic definition and re-compile schema.
OCI-31153: Cannot create schema URL with reserved prefix "http://
xmlns.oracle.com/xdb/schemas/"
Cause: This prefix is reserved for XDB extended schema URLs and cannot be used in
a user specified URL.
Action: Modify the prefix to a different one.
OCI-31154: invalid XML document
Cause: The XML document is invalid with respect to its XML Schema.
Action: Fix the errors identified and try again.
OCI-31155: attribute string not in XDB namespace
Cause: The specified attribute should be prefixed with XDB's namespace.
Action: Ensure that all XDB specified attributes are prefixed with XDB's namespace
and try again.
OCI-31157: Invalid Content-Type charset
Cause: HTTP Content-Type header had a charset that Oracle does not understand.
Action: Fix the Content-Type header in the HTTP request.
OCI-31158: schema "string" currently being referenced
Cause: The specified schema URL is currently being referenced by the same session.
This could happen because of PLSQL XMLType variables still in scope.
Action: Ensure all references to this schema in this session are released and try the
operation again.
OCI-31159: XML DB is in an invalid state
Cause: XML DB's internal tables are in an invalid state, probably because the database
was not upgraded or the upgrade was not successful
Action: Ensure that the database is upgraded successfully. If the problem persists,
contact Oracle Support
OCI-31160: max substitution group size string exceeded by "string" (string) for head
element "string" (string)
Cause: The maximum limit on nested substitution groups has been exceeded by an
element.
Action: Delete specified schema and re-register it after removing the offending
substitution element.
OCI-31161: element or attribute "string" cannot be stored out of line
Cause: An element or attribute of a simple type has SQLInline=false
Action: Remove the SQLInline=false qualification for the offending element or
attribute
OCI-00601 to OCI-31199 56-39
OCI-31162: element or attribute "string" has no SQLType specified

Cause: Schema registration was invoked with GENTYPES=false without specifying a
SQLType for some element or attribute
Action: Specify a SQLType for the offending element or attribute and register the
schema again
OCI-31163: element or attribute "string" has invalid attribute value "string" (should
be "string")
Cause: An element or attribute for a complextype derived by restriction has an
attribute whose value is different from that in the base type
Action: Remove the mismatched attribute values from the offending element or
attribute
OCI-31164: cannot load object-relational XML attribute using direct path \n
Cause: The table being loaded contains a xml column with object-relational storage.
The xmltype column contains a type with subtypes. This type of attribute cannot be
loaded with direct path.
Action: Perform the load with conventional path mode.
OCI-31165: cannot load object-relational XML attribute using direct path \n
Cause: The table being loaded contains a xml column with object-relational storage.
The xmltype column either contains an out-of-line partitioned table or the table itself
is partitioned by one of the attributes of xmltype. This type of table cannot be loaded
with direct path.
Action: Perform the load with conventional path mode.
OCI-31167: XML nodes over 64K in size cannot be inserted
Cause: An attempt was made to insert an XML Text Node with a size greater than
64K. This is not supported.
Action: Create text nodes under 64K.
OCI-31168: Node localname and namespace values should be less than 64K
Cause: An attempt was made to specify an XML Node with localname or namespace
value greater than or equal to 64K. This is not supported.
Action: Node localnames and namespace values should be under 64K.
OCI-31180: DOM Type mismatch in invalid PL/SQL DOM handle
Cause: The specified PL/SQL DOM handle is referencing a DOM Node whose DOM
Type that does not match the one available in the session. This could happen because
the pl/sql handle was reused, or the original document is no longer available.
Action: Ensure that the pl/sql handle for the target node is valid and try the operation
again.
OCI-31181: PL/SQL DOM handle accesses node that is no longer available
Cause: The specified pl/sql handle is referencing a node in a DOM Document that is
no longer available.
Action: Ensure that the pl/sql handle for the target node is valid and try the operation
again.
OCI-31182: Too many PL/SQL DOM handles specified

Cause: An attempt was made to create a PL/SQL DOM handle that exceeded the
maximum allowable number of PL/SQL DOM handles.
Action: Free PL/SQL DOM handles and try the operation again.
OCI-31185: DOM Nodes do not belong to the same DOM Document
Cause: The specified PL/SQL DOM Node does not belong to the parent DOM
Document of the referring DOM Node.
Action: Ensure that both the DOM Nodes are part of the same DOM Document.
OCI-31190: Resource string is not a version-controlled resource
Cause: Either one of the following is the cause: - Checkout is requested for a resource
that isn't under version control". Only version-controlled resource can be checked out.
- Checkout is requested for a row of a non-versioned table.
Action: put the resource under version-control before checking out.
OCI-31191: Resource string is already checked out
Cause: Either one of the following is the cause: - Checkout is requested for a resource
that is already checked out to the workspace by the same of different user.
Action: checked in the resource from the workspace before checking out
OCI-31192: Resource string has not been checked out
Cause: Either one of the following is the cause: - Checkin or uncheckout is requested
for a resource that has not been checked out to the workspace by any user in a
workspace
Action: checked in the resource from the workspace before checking out
OCI-31193: This versioning feature isn't supported for resource string
Cause: Either one of the following is the cause: - Container cannot be put under
version-controlled.
Action: Avoid using these features.
OCI-31194: Resource string is already deleted
Cause: Access a version-controlled resource that is already deleted.
Action: Recreate the resource. Remove the cyclic definitions in the type and retry
compilation.
OCI-31195: XML node 'string' (type=string) does not support this operation
Cause: The given node's type is not supported for this operation. For example, trying
to add children to an attribute node, or passing in a document node as a child, are
unsupported operations.
Action: Use a valid node type for the operation.
OCI-31196: XML nodes over string in size cannot be printed
Cause: An attempt was made to use an XML Text Node with a size greater than 64K,
or an XML Comment Node with a size greater than 4K. These cannot be printed. For
example, trying to add children to an attribute node, or passing in a document node
as a child, are unsupported operations.
Action: Use getClobVal() or getStringVal() to print the Document.
OCI-00601 to OCI-31199 56-41
OCI-31197: Error in processing file string

Cause: An error occurred while operating on the specifed file. The possible causes are
the file header is corrupt or check the next error on stack
Action: Ensure that the specified file is correct. Look at the next error on the stack and
OCI-31198: Mismatch in number of bytes transferred due to non-binary mode
Cause: An error occurred while reading the specifed file. The most probable cause is
that the transfer was initiated in ASCII mode.
Action: Ensure that the transfer mode is set to BINARY
OCI-31199: Warning in processing file string
Cause: A warning was raised while operating on the specifed file. However, the
current operation was completed successfully.
Action: This is primarily an informational message. Look at the next error on the stack
to obtain further information.
57
OKSK-00000 to OKSK-00029
OKSK-00000: %2 %3
Action: None
OKSK-00001: %2 %3
Action: None
OKSK-00002: %2 %3
Action: None
OKSK-00003: %2 %3
Action: None
OKSK-00004: Module load succeeded. Build information: %2 %3 %4
Action: None
OKSK-00005: Module failed to load and start with status %2. Build information: %3
%4 %5
Action: None
OKSK-00006: Module unloaded.
Action: None
OKSK-00007: Information has been saved in the file %2 . Include the contents of
this file if reporting a problem to Oracle.
Action: None
OKSK-00008: Cluster Membership Change starting - Incarnation %2.
Action: None
OKSK-00009: Cluster Membership Change complete.
OKSK-00000 to OKSK-00029 57-1
Action: n/a
OKSK-00010: Persistent OKS log opened at %2.
Action: None
OKSK-00011: Failed to allocate kernel memory for %2.
Cause: Unable to allocate memory for a required function.
OKSK-00012: Failed to open %2.
Cause: Unable to open a persistent OKS log file. Likely an invalid file path was
specified or there was an internal error.
Action: Ensure that the file or directory exists else. If it does, contact Oracle Support
Services.
OKSK-00013: Terminating Persistent OKS log.
Cause: Persistent OKS logging terminated due to the previous message.
Action: Informational.
OKSK-00014: Unable to generate an persistent OKS log file name.
Cause: Failed to generate an persistent OKS log fime name.
OKSK-00015: Persistent log thread creation failed.
Cause: Failed to create a kernel thread.
OKSK-00016: Configuration error: buffer size %2 bytes is out of range.
Cause: The user selected an invalid buffer size.
Action: Select a different buffer size.
OKSK-00017: Configuration error: interval timer of %2 ms is out of range.
Cause: The user selected an invalid timer interval.
Action: Select a different timer value.
OKSK-00018: Configuration error: low water level of %2 bytes isout of range.
Cause: The user selected an invalid low water value.
Action: Select a different low water value.
OKSK-00019: Configuration error: high water level of %2 bytes is out of range.
Cause: The user selected an invalid high water value.
Action: Select a different high water value.
OKSK-00020: Configuration error: maximum number of log files (%2) is out of
range.
Cause: The user selected an invalid maximum file number value.
Action: Select a different file number value.
57-2 Error Messages
OKSK-00021: Configuration error: The maximum file size of %2 bytes is out of

range.
Cause: The user selected an invalid maximum log file size value.
Action: Select a different maximum log file size value.
OKSK-00022: File write error: File name 'string'.
Cause: A write to the persistent OKS log file failed - possibly due to a full file system.
Otherwise, it is an internal error. The in-memory OKS log will contain details
regarding the error.
Action: Free up file systems space and restart the OKS persistent log ('acfsutil
plogconfig -d dir'). If freeing up file system space does not resolve the problem,
OKSK-00023: Cluster membership node list:
Action: None
OKSK-00024: Node %2 (Interconnect address: %3.%4.%5.%6)
Action: None
OKSK-00025: Cluster membership node count: %2, Local Node Number: %3.
Action: None
OKSK-00026: Cluster membership rebuild manager failed to initialize.
OKSK-00027: Oracle kernel distributed lock manager hash size is %2
Action: None
OKSK-00028: In memory kernel log buffer address: %2, size: %3
Action: None
OKSK-00029: Unable to %2 the log buffer.
Action: None
OKSK-00000 to OKSK-00029 57-3
57-4 Error Messages
58
ORA-00000 to ORA-00877
ORA-00000: normal, successful completion
Cause: Normal exit.
Action: None
ORA-00001: unique constraint (string.string) violated
Cause: An UPDATE or INSERT statement attempted to insert a duplicate key. For
Trusted Oracle configured in DBMS MAC mode, you may see this message if a
duplicate entry exists at a different level.
Action: Either remove the unique restriction or do not insert the key.
ORA-00017: session requested to set trace event
Cause: The current session was requested to set a trace event by another session.
Action: This is used internally; no action is required.
ORA-00018: maximum number of sessions exceeded
Cause: All session state objects are in use.
Action: Increase the value of the SESSIONS initialization parameter.
ORA-00019: maximum number of session licenses exceeded
Cause: All licenses are in use.
Action: Increase the value of the LICENSE MAX SESSIONS initialization parameter.
ORA-00020: maximum number of processes (string) exceeded
Cause: All process state objects are in use.
Action: Increase the value of the PROCESSES initialization parameter.
ORA-00021: session attached to some other process; cannot switch session
Cause: The user session is currently used by others.
Action: Do not switch to a session attached to some other process.
ORA-00022: invalid session ID; access denied
Cause: Either the session specified does not exist or the caller does not have the
privilege to access it.
Action: Specify a valid session ID that you have privilege to access, that is either you
own it or you have the CHANGE_USER privilege.
ORA-00023: session references process private memory; cannot detach session
Cause: An attempt was made to detach the current session when it contains
references to process private memory.
ORA-00000 to ORA-00877 58-1
Action: A session may contain references to process memory (PGA) if it has an open
network connection, a very large context area, or operating system privileges. To
allow the detach, it may be necessary to close the session's database links and/or
cursors. Detaching a session with operating system privileges is always disallowed.
ORA-00024: logins from more than one process not allowed in single-process mode
Cause: Trying to login more than once from different processes for ORACLE started
in single-process mode.
Action: Logoff from the other process.
ORA-00025: failed to allocate string
Cause: Out of memory.
Action: Restart with larger sga heap.
ORA-00026: missing or invalid session ID
Cause: Missing or invalid session ID string for ALTER SYSTEM KILL SESSION.
Action: Retry with a valid session ID.
ORA-00027: cannot kill current session
Cause: Attempted to use ALTER SYSTEM KILL SESSION to kill the current session.
Action: None
ORA-00028: your session has been killed
Cause: A privileged user has killed your session and you are no longer logged on to
the database.
Action: Login again if you wish to continue working.
ORA-00029: session is not a user session
Cause: The session ID specified in an ALTER SYSTEM KILL SESSION command was
not a user session (for example, recursive, etc.).
Action: Retry with a user session ID.
ORA-00030: User session ID does not exist.
Cause: The user session ID no longer exists, probably because the session was logged
out.
Action: Use a valid session ID.
ORA-00031: session marked for kill
Cause: The session specified in an ALTER SYSTEM KILL SESSION command cannot
be killed immediately (because it is rolling back or blocked on a network operation),
but it has been marked for kill. This means it will be killed as soon as possible after its
current uninterruptable operation is done.
Action: No action is required for the session to be killed, but further executions of the
ALTER SYSTEM KILL SESSION command on this session may cause the session to be
killed sooner.
ORA-00032: invalid session migration password
Cause: The session migration password specified in a session creation call was invalid
(probably too long).
Action: Retry with a valid password (less than 30 chars).
58-2 Error Messages
ORA-00033: current session has empty migration password

Cause: An attempt was made to detach or clone the current session and it has an
empty migration password. This is not allowed.
Action: Create the session with a non-empty migration password.
ORA-00034: cannot string in current PL/SQL session
Cause: An attempt was made to issue a commit or rollback from a PL/SQL object
(procedure, function, package) in a session that has this disabled (by 'alter session
disable commit in procedure')
Action: Enable commits from PL/SQL in this session, or do not attempt to use commit
or rollback in PL/SQL when they are disabled in the current session.
ORA-00035: LICENSE_MAX_USERS cannot be less than current number of users
ORA-00036: maximum number of recursive SQL levels (string) exceeded
Cause: An attempt was made to go more than the specified number of recursive SQL
levels.
Action: Remove the recursive SQL, possibly a recursive trigger.
ORA-00037: cannot switch to a session belonging to a different server group
Cause: An attempt was made to switch to a session in a different server group. This is
not allowed.
Action: Make sure the server switches to a session that belongs to its server group.
ORA-00038: Cannot create session: server group belongs to another user
Cause: An attempt was made to create a non-migratable session in a server group that
is owned by a different user.
Action: A server group is owned by the first user who logs into a server in the server
group in non-migratable mode. All subsequent non-migratable mode logins must be
made by the user who owns the server group. To have a different user login in nonmigratable mode, the ownership of the server group will have to be changed. This can
be done by logging off all current sessions and detaching from all existing servers in
the server group and then having the new user login to become the new owner.
ORA-00039: error during periodic action
Cause: An unexpected error occurred while executing a periodically invoked action.
Action: Check the error stack for detailed error information.
ORA-00040: active time limit exceeded - call aborted
Cause: The Resource Manager SWITCH_TIME limit was exceeded.
Action: Reduce the complexity of the update or query, or contact your database
administrator for more information.
ORA-00041: active time limit exceeded - session terminated
Cause: The Resource Manager SWITCH_TIME limit was exceeded.
Action: Reduce the complexity of the update or query, or contact your database
administrator for more information.
ORA-00042: Unknown Service name string
Cause: An attempt was made to use an invalid application service.
Action: Use a valid service name from SERVICE$ or add a new service using the
DBMS_SERVICE package.
ORA-00000 to ORA-00877 58-3
ORA-00043: remote operation failed

Cause: Execution of the inter-instance operation failed.
Action: Check the status of the target instance. The operation may have partially
executed. Verify the result of the intended operation.
ORA-00044: timed_statistics must be TRUE when statistics_level is not BASIC
Cause: The user attempted to set timed_statistics to FALSE when statistics_level was
not BASIC. timed_statistics is required to be TRUE to collect meaningful statistics
when statistics_level is set to TYPICAL or ALL.
Action: Either set timed_statistics to TRUE or set statistics_level to BASIC.
ORA-00045: Your session has been terminated with no replay.
Cause: A privileged user terminated your session and you were no longer logged on
to the database. Your session will not be replayed by Application Continuity or
Transparent Application Failover (TAF).
Action: Log in again if you wish to continue working.
ORA-00046: cannot modify sessions parameter
Cause: An attempt was made to alter the sessions parameter in the root container or
non-consolidated database.
Action: The sessions parameter behaves like a static parameter in root containers and
non-consolidated databases and hence cannot be altered. It can only be altered from a
pluggable database.
ORA-00047: cannot set sessions parameter to this value
Cause: An attempt was made to alter the sessions parameter to a value greater than
the root container's session value.
Action: The sessions parameter can only be set to a value less than or equal to the root
container's session value.
ORA-00050: operating system error occurred while obtaining an enqueue
Cause: Could not obtain the operating system resources necessary to cover an oracle
enqueue. This is normally the result of an operating system user quota that is too low.
Action: Look up the operating system error in your system documentation and
perform the needed action.
ORA-00051: timeout occurred while waiting for a resource
Cause: Usually due to a dead instance.
Action: Check for any dead, unrecovered instances and recover them.
ORA-00052: maximum number of enqueue resources (string) exceeded
Cause: Ran out of enqueue resources.
Action: Increase the value of the ENQUEUE_RESOURCES initialization parameter.
ORA-00053: maximum number of enqueues exceeded
Cause: Ran out of enqueue state objects.
Action: Increase the value of the ENQUEUES initialization parameter.
ORA-00054: resource busy and acquire with NOWAIT specified or timeout expired
Cause: Interested resource is busy.
Action: Retry if necessary or increase timeout.
58-4 Error Messages
ORA-00055: maximum number of DML locks exceeded

Cause: Ran out of DML lock state objects.
Action: Increase the value of the DML_LOCKS initialization parameter and warm
start.
ORA-00056: DDL lock on object 'string.string' is already held in an incompatible
mode
Cause: An attempt was made to acquire a DDL lock that is already locked.
Action: This happens if you attempt to drop a table that has parse locks on it.
ORA-00057: maximum number of temporary table locks exceeded
Cause: The number of temporary tables equals or exceeds the number of temporary
table locks. Temporary tables are often created by large sorts.
Action: Increase the value of the TEMPORARY_TABLE_LOCKS initialization
parameter and warm start.
ORA-00058: DB_BLOCK_SIZE must be string to mount this database (not string)
Cause: DB_BLOCK_SIZE initialization parameter is wrong for the database being
mounted. It does not match the value used to create the database.
Action: Fix the value of the DB_BLOCK_SIZE parameter or mount a database that
matches the value.
ORA-00059: maximum number of DB_FILES exceeded
Cause: The value of the DB_FILES initialization parameter was exceeded.
Action: Increase the value of the DB_FILES parameter and warm start.
ORA-00060: deadlock detected while waiting for resource
Cause: Transactions deadlocked one another while waiting for resources.
Action: Look at the trace file to see the transactions and resources involved. Retry if
necessary.
ORA-00061: another instance has a different DML_LOCKS setting
Cause: The shared instance being started is using DML locks, and the running
instances are not, or vice-versa.
Action: Ensure that all instances' INIT.ORA files specify the DML_LOCKS parameter
as 0 or all as non-zero.
ORA-00062: DML full-table lock cannot be acquired; DML_LOCKS is 0
Cause: The instance was started with DML_LOCKS = 0, and the statement being
executed needs a full-table lock (S, X, or SSX).
Action: Restart the instance with DML_LOCKS not equal to zero, and reexecute the
statement.
ORA-00063: maximum number of log files exceeded string
Cause: The number of log files specificied exceeded the maximum number of log files
supported in this release.
Action: Re-create the control file with the highest number of log files no greater than
the maximum supported in this release.
ORA-00000 to ORA-00877 58-5
ORA-00064: object is too large to allocate on this O/S (string,string,string)

Cause: An initialization parameter was set to a value that required allocating more
contiguous space than can be allocated on this operating system.
Action: Reduce the value of the initialization parameter.
ORA-00065: initialization of FIXED_DATE failed
Cause: The FIXED_DATE string was not in date format yyyy-mm-dd:hh24:mi:ss.
Action: Make sure the initialization parameter is in the correct date format.
ORA-00066: SID 'string' contains an illegal character or is too long
Cause: The specified SID contained an illegal character or the SID specified was too
long, which cannot occur in an SPFILE setting. Illegal characters include ,#"'=() and
whitespace.
Action: Use a SID that does not contain a special character or whitespace. Check
platform specific documentation for the maximum length of SID.
ORA-00067: invalid value string for parameter string; must be at least string
Cause: The value for the initialization parameter is invalid.
Action: Choose a value as indicated by the message.
ORA-00068: invalid value string for parameter string, must be between string and
string
ORA-00069: cannot acquire lock -- table locks disabled for string
Cause: A command was issued that tried to lock the table indicated in the message.
Examples of commands that can lock tables are: LOCK TABLE, ALTER TABLE ...
ADD (...), and so on.
Action: Use the ALTER TABLE ... ENABLE TABLE LOCK command, and retry the
command.
ORA-00070: command string is not valid
Cause: An invalid debugger command was specified.
Action: Type HELP to see the list of available commands.
ORA-00071: process number must be between 1 and string
Cause: An invalid process number was specified.
Action: Specify a valid process number.
ORA-00072: process "string" is not active
Cause: An invalid process was specified.
Action: Specify a valid process.
ORA-00073: command string takes between string and string argument(s)
Cause: An incorrect number of arguments was specified.
Action: Specify the correct number of arguments. Type HELP to see the list of
commands and their syntax.
ORA-00074: no process has been specified
Cause: No debug process has been specified.
58-6 Error Messages

ORA-00075: process "string" not found in this instance
Cause: The specified process was not logged on to the current instance.
ORA-00076: dump string not found
Cause: An attempt was made to invoke a dump that does not exist.
Action: Type DUMPLIST to see the list of available dumps.
ORA-00077: dump string is not valid
Cause: An attempt was made to invoke an invalid dump.
Action: Try another dump.
ORA-00078: cannot dump variables by name
Cause: An attempt was made to dump a variable by name on a system that does not
support this feature.
Action: Try the PEEK command.
ORA-00079: variable string not found
Cause: An attempt was made to dump a variable that does not exist.
Action: Use a valid variable name.
ORA-00080: invalid global area specified by level string
Cause: An attempt was made to dump an invalid global area.
Action: Use level 1 for the PGA, 2 for the SGA, and 3 for the UGA. Use <extra + level>
to dump global area level as well as extra bytes for every pointer; extra must be a
multiple of 4.
ORA-00081: address range [string, string) is not readable
Cause: An attempt was made to read/write an invalid memory address range.
Action: Try another address or length.
ORA-00082: memory size of string is not in valid set of [1], [2],
[4]stringstringstringstringstring
Cause: An invalid length was specified for the POKE command.
Action: Use a valid length (either 1, 2, 4, or possibly 8).
ORA-00083: warning: possibly corrupt SGA mapped
Cause: Even though there may be SGA corruptions, the SGA was mapped.
Action: Use the DUMPSGA command to dump the SGA.
ORA-00084: global area must be PGA, SGA, or UGA
Cause: An attempt was made to dump an invalid global area.
Action: Specify either PGA, SGA, or UGA.
ORA-00085: current call does not exist
Cause: An invalid attempt was made to dump the current call heap.
Action: Wait until the process starts a call.
ORA-00000 to ORA-00877 58-7
ORA-00086: user call does not exist

Cause: An invalid attempt was made to dump the user call heap.
Action: Wait until the process starts a call.
ORA-00087: command cannot be executed on remote instance
Cause: Cluster database command issued for non cluster database ORADEBUG
command.
Action: Issue the command without the cluster database syntax.
ORA-00088: command cannot be executed by shared server
Cause: Debug command issued on shared server.
Action: Reissue the command using a dedicated server.
ORA-00089: invalid instance number in ORADEBUG command
Cause: An invalid instance number was specified in a cluster database ORADEBUG
command.
Action: Reissue the command with valid instance numbers.
ORA-00090: failed to allocate memory for cluster database ORADEBUG command
Cause: Could not allocate memory needed to execute cluster database oradebug.
Action: Reissue the command on each instance with single-instance oradebug.
ORA-00091: LARGE_POOL_SIZE must be at least string
Cause: The value of LARGE_POOL_SIZE is below the minimum size.
Action: Increase the value of LARGE_POOL_SIZE past the minimum size.
ORA-00092: LARGE_POOL_SIZE must be greater than
LARGE_POOL_MIN_ALLOC
Cause: The value of LARGE_POOL_SIZE is less than the value of
LARGE_POOL_MIN_ALLOC.
Action: Increase the value of LARGE_POOL_SIZE past the value of
LARGE_POOL_MIN_ALLOC.
ORA-00093: string must be between string and string
Cause: The parameter value is not in a valid range.
Action: Modify the parameter value to be within the specified range.
ORA-00094: string requires an integer value
Cause: The parameter value is not an integer.
Action: Modify the parameter value to be an integer.
ORA-00096: invalid value string for parameter string, must be from among string
ORA-00097: use of Oracle SQL feature not in SQL92 string Level
Cause: Usage of Oracle's SQL extensions.
Action: n/a
58-8 Error Messages
ORA-00098: creating or mounting the database requires a parameter file

Cause: An attempt was made to create or mount the database when the instance was
started without a parameter file.
Action: Restart the instance with a parameter file.
ORA-00099: warning: no parameter file specified for string instance
Cause: Even though no parameter file was specified, the instance was started with all
default values.
Action: None
ORA-00100: no data found
Cause: An application made reference to unknown or inaccessible data.
Action: Handle this condition within the application or make appropriate
modifications to the application code. NOTE: If the application uses Oracle-mode SQL
instead of ANSI-mode SQL, ORA-01403 will be generated instead of ORA-00100.
ORA-00101: invalid specification for system parameter DISPATCHERS
Cause: The syntax for the DISPATCHERS parameter is incorrect.
Action: Refer to the manual for correct syntax.
ORA-00102: network protocol string cannot be used by dispatchers
Cause: The network specified in DISPATCHERS does not have the functionality
required by the dispatchers.
Action: Refer to the manual on network protocols supported by the dispatchers.
ORA-00103: invalid network protocol; reserved for use by dispatchers
Cause: The network specified in the SQL*Net connect string is reserved for use by the
dispatchers.
Action: Specify other network protocols in the connection string.
ORA-00104: deadlock detected; all public servers blocked waiting for resources
Cause: All available public servers are servicing requests that require resources
locked by a client which is unable to get a public server to release the resources.
Action: Increase the limit for the system parameter MAX_SHARED_SERVERS as the
system will automaticaly start up new servers to break the deadlock until the number
of servers reaches the value specified in MAX_SHARED_SERVERS.
ORA-00105: too many dispatcher configurations
Cause: Too many dispatcher configurations have been specified. No more can be
added.
Action: Consolidate the dispatcher configurations if possible.
ORA-00106: cannot startup/shutdown database when connected to a dispatcher
Cause: An attempt was made to startup/shutdown database when connected to a
shared server via a dispatcher.
Action: Re-connect as user INTERNAL without going through the dispatcher. For
most cases, this can be done by connect to INTERNAL without specifying a network
connect string.
ORA-00107: failed to connect to ORACLE listener process
Cause: Most likely due to the fact that ORACLE listener has not been started.
ORA-00000 to ORA-00877 58-9
Action: Start ORACLE listener if it has not been started. Or else contact your
ORACLE representative.
ORA-00108: failed to set up dispatcher to accept connection asynchronously
Cause: Most likely due to the fact that the network protocol used by the the
dispatcher does not support aynchronous operations.
Action: Contact your ORACLE representative.
ORA-00109: invalid value for attribute string: string
Cause: The value specified for the attribute was incorrect.
Action: Refer to the manual for the proper values.
ORA-00110: invalid value string for attribute string, must be between string and
string
Cause: The value specified for the attribute was incorrect.
Action: Specify a value within the range allowed.
ORA-00111: invalid attribute string
Cause: The specified attribute was not recognized.
Action: Refer to the manual for the proper keyword to use to specify a dispatcher
attribute.
ORA-00112: value of string is null
Cause: The attribute was specified with no value.
Action: Specify a non-null value.
ORA-00113: protocol name string is too long
Cause: A protocol name specified in the DISPATCHERS system parameter is too long.
Action: Use a valid protocol name for the DISPATCHERS value.
ORA-00114: missing value for system parameter SERVICE_NAMES
Cause: No value was specified for the SERVICE_NAMES system parameter, nor for
the DB_NAME parameter.
Action: Add an SERVICE_NAMES or DB_NAME definition to the INIT.ORA file. By
default, SERVICE_NAMES is the value of DB_NAME unless SERVICE_NAMES is
explicitly specified.
ORA-00115: connection refused; dispatcher connection table is full
Cause: A connection request was refused by a dispatcher because the dispatcher
cannot support any more connections.
Action: Connect to a different dispatcher, or use a dedicated server.
ORA-00116: SERVICE_NAMES name is too long
Cause: A service name specified in the SERVICE_NAMES system parameter is too
long.
Action: Use a shorter name in the SERVICE_NAMES value (<= 255 chars).
ORA-00117: PROTOCOL, ADDRESS or DESCRIPTION must be specified
Cause: PROTOCOL, ADDRESS or DESCRIPTION was not specified.
Action: Use one of the attributes: PROTOCOL, ADDRESS or DESCRIPTION to
specify the listening address for dispatchers.
ORA-00118: Only one of PROTOCOL, ADDRESS or DESCRIPTION may be

specified
Cause: More than one of PROTOCOL, ADDRESS or DESCRIPTION was specified.
Action: Use only one of the attributes: PROTOCOL, ADDRESS or DESCRIPTION to
specify the listening address for dispatchers.
ORA-00119: invalid specification for system parameter string
Cause: The syntax for the specified parameter is incorrect.
Action: Refer to the Oracle Reference Manual for the correct syntax.
ORA-00120: invalid 'shared_servers' value for the PDB
Cause: 'shared_servers' cannot be set to a non-zero value in a non-ROOT pluggable
database (PDB).
Action: In a multitenant container database (CDB) setup, shared servers can be
configured only in ROOT. A non-ROOT PDB can disable shared servers for the PDB
by setting 'shared_servers' to 0. No other values are allowed. To reenable within the
PDB, use 'alter system reset shared_servers'.
ORA-00122: cannot initialize network configuration
Cause: ORACLE could not initialize SQL*Net version 2.
Action: Check the error stack for detailed information.
ORA-00123: idle public server terminating
Cause: Too many idle servers were waiting on the common queue.
Action: This error is used internally, no action is required.
ORA-00125: connection refused; invalid presentation
Cause: The PRESENTATION in the CONNECT_DATA of the TNS address
DESCRIPTION is not correct or is not supported.
Action: Correct the PRESENTATION specified in the TNS address.
ORA-00126: connection refused; invalid duplicity
Cause: The DUPLICITY in the CONNECT_DATA of the TNS address DESCRIPTION
is not correct or is not supported.
Action: Correct the DUPLICITY specified in the TNS address.
ORA-00127: dispatcher string does not exist
Cause: There is currently no dispatcher running with the specified name.
Action: Retry with a name of the form "D###" denoting an existing dispatcher process.
ORA-00128: this command requires a dispatcher name
Cause: Wrong syntax for ALTER SYSTEM SHUTDOWN
Action: Use correct syntax: ALTER SYSTEM SHUTDOWN [ IMMEDIATE ]
'dispatcher name'
ORA-00129: listener address validation failed 'string'
Cause: An error was encountered while validating the listener address.
Action: Resolve error or contact your ORACLE representative.
ORA-00130: invalid listener address 'string'
Cause: The listener address specification is not valid.
ORA-00000 to ORA-00877 58-11
Action: Make sure that all fields in the listener address (protocol, port, host, key, ...)
are correct.
ORA-00131: network protocol does not support registration 'string'
Cause: The specified protocol does not support async notification.
Action: Refer to the manual for information on supported network protocols.
ORA-00132: syntax error or unresolved network name 'string'
Cause: Listener address has syntax error or cannot be resolved.
Action: If a network name is specified, check that it corresponds to an entry in
TNSNAMES.ORA or other address repository as configured for your system. Make
sure that the entry is syntactically correct.
ORA-00133: value of string is too long
Cause: The value specified for the attribute was too long.
Action: Use shorter names and keywords or remove unneeded blanks.
ORA-00134: invalid DISPATCHERS specification #string
Cause: The syntax for the n-th DISPATCHERS specification was incorrect.
ORA-00135: missing attribute string
Cause: The indicated mandatory attribute was not specified.
Action: Specify a non-null value for the attribute.
ORA-00136: invalid LISTENER_NETWORKS specification #string
Cause: The syntax for the nth LISTENER_NETWORKS specification was invalid.
ORA-00137: invalid LISTENER_NETWORKS specification with NAME=string
Cause: The syntax for the LISTENER_NETWORKS specification with the indicated
NAME was invalid.
ORA-00138: all addresses specified for attribute string are invalid
Cause: All of the specified addresses or aliases for the attribute were invalid.
Action: Specify at least one valid address or alias.
ORA-00139: duplicate attribute string
Cause: The indicated attribute was specified more than once.
Action: Specify the attribute at most once.
ORA-00150: duplicate transaction ID
Cause: Attempted to start a new transaction with an ID already in use by an existing
transaction.
Action: Check your application.
ORA-00151: invalid transaction ID
Cause: The specified transaction ID does not correspond to an existing valid
transaction.
ORA-00152: current session does not match requested session

Cause: The current session is not the same as the session that was passed into a
upixado() call.
ORA-00153: internal error in XA library
Cause: The XA library could not access thread-specific pointers.
ORA-00154: protocol error in transaction monitor
Cause: The transaction monitor returned TMJOIN on an AX_REG call but the
transaction was locally suspended.
Action: Contact the transaction monitor customer support.
ORA-00155: cannot perform work outside of global transaction
Cause: The application tried to perform some work on either an Oracle 7.3 server or
an Oracle8 server with local transactions disabled while outside of a global
transaction.
Action: Check if the application is connected to an Oracle 7.3 server. The Transaction
monitor must not return a NULL XID on an AX_REG call when the resource manager
is Oracle 7.3. If the application is connected to an Oracle8 server, either set nolocal=f
in the xa_open string or start a global transaction prior to attempting the work.
ORA-00160: global transaction length string is greater than maximum (string)
Cause: An external global transaction ID with a too large length field was passed in.
Action: Report the problem to your external transaction coordinator vendor.
ORA-00161: transaction branch length string is illegal (maximum allowed string)
Cause: An external transaction branch ID with a length either too large or 0 was
passed in.
ORA-00162: external dbid length string is greater than maximum (string)
Cause: An external database name with too large a length field was passed in.
ORA-00163: internal database name length string is greater than maximum (string)
Cause: An internal database name with a too large length field was passed in.
ORA-00164: distributed autonomous transaction disallowed within migratable
distributed transaction
Cause: A request was made by the application to start a distributed autonomous
transaction when the application was in a migratable distributed transaction.
Action: Roll back or commit the current distributed transaction first.
ORA-00165: migratable distributed autonomous transaction with remote operation
is not allowed
Cause: A request was made by the application to start a migratable distributed
autonomous transaction with remote operation.
Action: n/a
ORA-00000 to ORA-00877 58-13
ORA-00166: remote/local nesting level is too deep

Cause: Too many remote table operations required a reverse trip back to the local site,
for example to execute a local function on a remote table.
Action: Rearrange the query or co-locate the functions with the tables.
ORA-00200: control file could not be created
Cause: It was not possible to create the control file.
Action: Check that there is sufficient disk space and no conflicts in filenames and try
to create the control file again.
ORA-00201: control file version string incompatible with ORACLE version string
Cause: The control file was created by incompatible software.
Action: Either restart with a compatible software release or use CREATE
CONTROLFILE to create a new control file that is compatible with this release.
ORA-00202: control file: 'string'
Cause: This message reports the name file involved in other messages.
Action: See associated error messages for a description of the problem.
ORA-00203: using the wrong control files
Cause: The mount ID in the control file is not the same as the mount ID in the control
file used by the first instance to mount this database. The control files are for the same
database but they are not the same files. Most likely one instance is using a backup
control file.
Action: Check that the correct control files were specified.
ORA-00204: error in reading (block string, # blocks string) of control file
Cause: A disk I/O failure was detected on reading the control file.
Action: Check if the disk is online, if it is not, bring it online and try a warm start
again. If it is online, then you need to recover the disk.
ORA-00205: error in identifying control file, check alert log for more info
Cause: The system could not find a control file of the specified name and size.
Action: Check that ALL control files are online and that they are the same files that
the system created at cold start time.
ORA-00206: error in writing (block string, # blocks string) of control file
Cause: A disk I/O failure was detected on writing the control file.
Action: Check if the disk is online, if it is not, bring it online and try a warm start
again. If it is online, then you need to recover the disk.
ORA-00207: control files are not for the same database
Cause: The database ID in the control file is not the same as the database ID in the
control file used by the first instance to mount this database. Most likely one of the
mounts used the wrong control file or there are two databases with the same name.
Action: Check that the control file is for the correct database and is not an old version.
ORA-00208: number of control file names exceeds limit of string
Cause: An attempt was made to use more control files than Oracle supports.
Action: Shut down Oracle. Reduce the number of control files specified in the
CONTROL_FILES parameter in the initialization parameter file, and restart Oracle.
Delete usused files.
ORA-00209: control file blocksize mismatch, check alert log for more info
Cause: The block size in the control file header does not match the size specified in the
DB_BLOCK_SIZE parameter.
Action: Look at the alert log for more information.
ORA-00210: cannot open the specified control file
Cause: Cannot open the control file.
Action: Check to make sure the control file exists and is not locked by some other
program.
ORA-00211: control file does not match previous control files
Cause: A control file was specified that belongs to another database.
Action: Find and install the correct control file.
ORA-00212: block size string below minimum required size of string bytes
Cause: The block size specified was too small. Space for the system overhead is
required.
Action: Specify a larger block size and retry the operation.
ORA-00213: cannot reuse control file; old file size string, string required
Cause: To reuse a control file, it must be the same size as the one previously used.
Action: Either do not specify REUSE, or specify a matching combination of
MAXDATAFILES, MAXLOGFILES, MAXLOGMEMBERS, MAXLOGHISTORY, and
MAXINSTANCES clauses in the CREATE DATABASE or CREATE CONTROLFILE
statement.
ORA-00214: control file 'string' version string inconsistent with file 'string' version
string
Cause: An inconsistent set of control files, datafiles/logfiles, and redo files was used.
Action: Use a consistant set of control files, datafiles/logfiles, and redo log files. That
is, all the files must be for the same database and from the same time period.
ORA-00215: must be at least one control file
Cause: No control file is specified or the control file specified does not exist.
Action: Specify at least one valid control file and retry the operation.
ORA-00216: control file could not be resized for migration from 8.0.2
Cause: The control file created by release 8.0.2 was missing some record types. These
record types are automatically added by resizing the control file during mount. The
resize has failed.
Action: Look in the alert log for the reason that the resize has failed. If indicated in the
alert log, give the control file more space. Otherwise, use the CREATE
CONTROLFILE script dumped to the trace file to create a new control file.
ORA-00217: control file could not be resized for new record types
Cause: The control file was missing some new record types supported by this release.
These record types are automatically added by resizing the contol file during mount.
The resize has failed.
ORA-00000 to ORA-00877 58-15
Action: Look in the alert log for the reason that the resize has failed. If indicated in the
alert log, give the control file more space. Otherwise, use the CREATE
CONTROLFILE script dumped to the trace file to create a new control file.
ORA-00218: block size string of control file 'string' does not match
DB_BLOCK_SIZE (string)
Cause: The block size as stored in the control file header is different from the value of
the initialization parameter DB_BLOCK_SIZE. This might be due to an incorrect
setting of DB_BLOCK_SIZE, or else might indicate that the control file has either been
corrupted or belongs to a different database.
Action: Restore a good copy of the control file. If the control file is known to be clean
set the DB_BLOCK_SIZE to match control file headers block size value.
ORA-00219: required control file size (string logical blocks) exceeds maximum
allowable size (string logical blocks)
Cause: An invocation of CREATE DATABASE or CREATE CONTROLFILE was
executed specifying a combination of parameters that would require the control file
size in blocks to exceed the maximum allowable value.
Action: In the case of CREATE DATABASE or CREATE CONTROLFILE, use a
different combination of MAXDATAFILES, MAXLOGFILES, MAXLOGMEMBERS,
MAXLOGHISTORY, and MAXINSTANCES clauses.
ORA-00220: control file not mounted by first instance, check alert log for more info
Cause: The specified control file has a different mount ID than the other control files
that are being mounted. This means that the first instance to mount the database did
not use this control file.
Action: Find and install the correct control file.
ORA-00221: error on write to control file
Cause: An error occurred when writing to one or more of the control files.
Action: See accompanying messages.
ORA-00222: operation would reuse name of a currently mounted control file
Cause: The filename supplied as a parameter to the ALTER DATABASE BACKUP
CONTROLFILE command or to cfileSetSnapshotName matches the name of the
specified currently mounted control file.
Action: Retry the operation with a different filename.
ORA-00223: convert file is invalid or incorrect version
Cause: An Oracle7 to Oracle8 convert file contains invalid data or was created with an
different version of the migration utility. This error can also be caused by incorrect
ORACLE_HOME environment variable when ALTER DATABASE CONVERT
command is issued.
Action: Use a correct version of the convert file or regenerate it with the migration
utility. Make sure that the migration utility is the same version as the Oracle8 RDBMS
executable and that the ORACLE_HOME environment variable is properly set.
ORA-00224: control file resize attempted with illegal record type (string)
Cause: An attempt was made to expand or shrink the control file by calling
cfileResizeSection using an invalid value for the RECORD_TYPE parameter.
Action: Use a value for the RECORD_TYPE parameter that specifies a valid record
type other than type 0 (valid range is 1-16).
ORA-00225: expected size string of control file differs from actual size string
Cause: The expected size of the control file as stored in its header was different than
the actual operating system file size. This usually indicates that the control file was
corrupted.
Action: Restore a good copy of the control file.
ORA-00226: operation disallowed while alternate control file open
Cause: The attempted operation could not be executed at this time because this
process had an alternate control file open for fixed table access.
Action: Retry the operation after calling cfileUseCurrent.
ORA-00227: corrupt block detected in control file: (block string, # blocks string)
Cause: A block header corruption or checksum error was detected on reading the
control file.
Action: Use the CREATE CONTROLFILE or RECOVER DATABASE USING
BACKUP CONTROLFILE command.
ORA-00228: length of alternate control file name exceeds maximum of string
Cause: The specified filename, which was supplied as a parameter to
cfileSetSnapshotName or cfileUseCopy, exceeds the maximum filename length for
this operating system.
Action: Retry the operation with a shorter filename.
ORA-00229: operation disallowed: already hold snapshot control file enqueue
Cause: The attempted operation cannot be executed at this time because this process
currently holds the snapshot control file enqueue.
Action: Retry the operation after calling cfileUseCurrent to release the snapshot
control file enqueue.
ORA-00230: operation disallowed: snapshot control file enqueue unavailable
Cause: The attempted operation cannot be executed at this time because another
process currently holds the snapshot control file enqueue.
Action: Retry the operation after the concurrent operation that is holding the snapshot
control file enqueue terminates.
ORA-00231: snapshot control file has not been named
Cause: During an invocation of cfileMakeAndUseSnapshot or cfileUseSnapshot it was
detected that no filename for the snapshot control file had previously been specified.
Action: Specify a name for the snapshot control file by calling cfileSetSnapshotName.
ORA-00232: snapshot control file is nonexistent, corrupt, or unreadable
Cause: The snapshot control file was found to be nonexistent, corrupt, or unreadable
during an invocation of cfileUseSnapshot.
Action: Call cfileMakeAndUseSnapshot again (or for the first time).
ORA-00233: copy control file is corrupt or unreadable
Cause: The specified copy control file was found to be corrupt or unreadable during
an invocation of cfileUseCopy.
Action: Before retrying cfileUseCopy, use the ALTER DATABASE BACKUP
CONTROLFILE command and specify the same filename that was specified for
cfileUseCopy.
ORA-00000 to ORA-00877 58-17
ORA-00234: error in identifying or opening snapshot or copy control file

Cause: A snapshot or copy control file of the specified name could not be found or
opened during an invocation of cfileUseSnapshot, cfileMakeAndUseSnapshot, or
cfileUseCopy.
Action: Re-create the snapshot or copy control file using cfileMakeAndUseSnapshot
or ALTER DATABASE BACKUP CONTROLFILE, respectively.
ORA-00235: control file read without a lock inconsistent due to concurrent update
Cause: Concurrent update activity on a control file caused a process to read
inconsistent information from the control file without a lock.
ORA-00236: snapshot operation disallowed: mounted control file is a backup
Cause: Attempting to invoke cfileSetSnapshotName, cfileMakeAndUseSnapshot, or
cfileUseSnapshot when the currently mounted control file is a backup control file.
Action: Mount a current control file and retry the operation.
ORA-00237: snapshot operation disallowed: control file newly created
Cause: An attempt to invoke cfileMakeAndUseSnapshot with a currently mounted
control file that was newly created with CREATE CONTROLFILE was made.
Action: Mount a current control file and retry the operation.
ORA-00238: operation would reuse a filename that is part of the database
Cause: The filename supplied as a parameter to the ALTER DATABASE BACKUP
CONTROLFILE command or to cfileSetSnapshotName matches the name of a file that
is currently part of the database.
Action: Retry the operation with a different filename.
ORA-00239: timeout waiting for control file enqueue: held by 'string' for more than
string seconds
Cause: The specified process waited the maximum allowed time for the control file
enqueue.
Action: Restart the blocking instance indicated in the incident trace file or reboot the
blocking node.
ORA-00240: control file enqueue held for more than string seconds
Cause: The current process did not release the control file enqueue within the
maximum allowed time.
Action: Reissue any commands that failed and contact Oracle Support Services with
the incident information.
ORA-00241: operation disallowed: control file inconsistent with data dictionary
Cause: The control file was either recently created via CREATE CONTROLFILE or an
incomplete recovery has been done. Thus, the datafiles in the control file and the ones
in the data dictionary may not match.
Action: Open the database, then retry the operation.
ORA-00242: maximum allowed filename records used up in control file
Cause: Failed to create a new filename record entry in the control file because the
maximum allowed filename records have been allocated and are in use.
Action: Free up controlfile filename section entries by dropping unwanted

tablespaces/datafiles/redofiles.
ORA-00243: failed to expand control file filename section by string records
Cause: Failed to expand control file filename section. See alert log for more details.
Action: Retry the operation after increasing disk space for controlfile expansion.
ORA-00244: concurrent control file backup operation in progress
Cause: Failed to create a control file backup because concurrent control file backup
operation was in progress.
Action: Retry backup creation later.
ORA-00245: control file backup failed; in Oracle RAC, target might not be on
shared storage
Cause: Failed to create a control file backup because some process signaled an error
during backup creation. This is likely caused by the backup target (i.e., RMAN
snapshot controlfile) being on a local file system so it could not be accessed by other
instances. It can also be caused by other I/O errors to the backup target. Any process
of any instance that starts a read/write control file transaction must have access to the
backup control file during backup creation.
Action: Check whether RMAN snapshot controlfile is on shared storage. Also, check
alert files of all instances for further information.
ORA-00246: control file backup failed; error accessing backup target
Cause: An attempt to create a control file backup failed because some process
signaled an I/O error when accessing the backup target.
Action: Check alert and trace files for further information.
ORA-00250: archiver not started
Cause: An attempt was made to stop automatic archiving, but the archiver process
was not running.
ORA-00251: LOG_ARCHIVE_DUPLEX_DEST cannot be the same destination as
string string
Cause: The destination specified by the LOG_ARCHIVE_DUPLEX_DEST parameter
is the same as the destination specified by an ALTER SYSTEM ARCHIVE LOG
START TO command.
Action: Specify a different destination for parameter
LOG_ARCHIVE_DUPLEX_DEST, or specify a different destination with the ALTER
SYSTEM command.
ORA-00252: log string of thread string is empty, cannot archive
Cause: A log must be used for redo generation before it can be archived. The specified
redo log was not been used since it was introduced to the database. However it is
possible that instance death during a log switch left the log empty.
Action: Empty logs do not need to be archived. Do not attempt to archive the redo log
file.
ORA-00253: character limit string exceeded by archive destination string string
Cause: The destination specified by an ALTER SYSTEM ARCHIVE LOG START TO
command was too long.
ORA-00000 to ORA-00877 58-19
Action: Retry the ALTER SYSTEM command using a string shorter than the limit
specified in the error message.
ORA-00254: error in archive control string 'string'
Cause: The specified archive log location is invalid in the archive command or the
LOG_ARCHIVE_DEST initialization parameter.
Action: Check the archive string used to make sure it refers to a valid online device.
ORA-00255: error archiving log string of thread string, sequence # string
Cause: An error occurred during archiving.
Action: Check the accompanying message stack for more detailed information. If the
online log is corrupted, then the log can be cleared using the UNARCHIVED option.
This will make any existing backups useless for recovery to any time after the log was
created, but will allow the database to generate redo.
ORA-00256: cannot translate archive destination string string
Cause: The destination specified by an ALTER SYSTEM ARCHIVE LOG START TO
command could not be translated.
Action: Check the accompanying message stack for more detailed information. Then,
retry the ALTER SYSTEM command using a different string.
ORA-00257: Archiver error. Connect AS SYSDBA only until resolved.
Cause: The archiver process received an error while trying to archive a redo log. If the
problem is not resolved soon, the database will stop executing transactions. The most
likely cause of this message is that the destination device is out of space to store the
redo log file. Another possible cause is that a destination marked as MANDATORY
has failed.
Action: Check the alert log and trace files for detailed error information.
ORA-00258: manual archiving in NOARCHIVELOG mode must identify log
Cause: The database is in NOARCHIVELOG mode and a command to manually
archive a log did not specify the log explicitly by sequence number, group number or
filename.
Action: Specify log by filename, by group number or by thread and sequence number.
ORA-00259: log string of open instance string (thread string) is the current log,
cannot archive
Cause: An attempt was made to archive the current log of an open thread. This is not
allowed because the redo log file may still be in use for the generation of redo entries.
Action: Force a log switch in the instance where the thread is open. If no instances are
open, open the database so that instance recovery can recover the thread.
ORA-00260: cannot find online log sequence string for thread string
Cause: The log sequence number supplied to the archival command does not match
any of the online logs for the thread. The log might have been reused for another
sequence number, it might have been dropped, the sequence number might be greater
than the current log sequence number, or the thread might not have any logs.
Action: Check the ARCHIVE statement, then specify a valid log sequence number.
Specify a valid log sequence number.
ORA-00261: log string of thread string is being archived or modified

Cause: The log is either being archived by another process or an administrative
command is modifying the log. Operations that modify the log include clearing,
adding a member, dropping a member, renaming a member, and dropping the log.
Action: Wait for the current operation to complete and try again.
ORA-00262: current log string of closed thread string cannot switch
Cause: The log cannot be cleared or manually archived because it is the current log of
a closed thread, and it is not possible to switch logs so another log is current. All other
logs for the thread need to be archived, or cleared, and cannot be reused.
Action: Archive another log in the same thread first, or complete the clearing. See
attached errors for the reason the switch cannot be completed.
ORA-00263: there are no logs that need archiving for thread string
Cause: An attempt was made to manually archive the unarchived logs in this thread
but no logs needed archiving.
ORA-00264: no recovery required
Cause: An attempt was made to perform media recovery on files that do not // need
any type of recovery.
Action: Do not attempt to perform media recovery on the selected files. Check to see
that the filenames were entered properly. If not, retry the command with the proper
filenames.
ORA-00265: instance recovery required, cannot set ARCHIVELOG mode
Cause: The database either crashed or was shutdown with the ABORT option. Media
recovery cannot be enabled because the online logs may not be sufficient to recover
the current datafiles.
Action: Open the database and then enter the SHUTDOWN command with the
NORMAL or IMMEDIATE option.
ORA-00266: name of archived log file needed
Cause: During media recovery, the name of an archived redo log file was requested,
but no name was entered.
Action: Mount the correct redo log file and enter its name when it is requested.
ORA-00267: name of archived log file not needed
Cause: During media recovery, the name of an archived redo log file was entered, but
no name was requested.
Action: Continue media recovery, but do not enter a new log name.
ORA-00268: specified log file does not exist 'string'
Cause: The given redo log file does not exist.
Action: Check the spelling and capitalization of the filename and retry the command.
ORA-00269: specified log file is part of thread string not string
Cause: The given redo log file is not part of the given thread
Action: Check that the thread of the redo log file matches the thread on the command
line. If not, use a redo log file from the appropriate thread. Retry the command after
correcting the error.
ORA-00000 to ORA-00877 58-21
ORA-00270: error creating archive log string

Cause: An error was encountered when either creating or opening the destination file
for archiving.
Action: Check that the archive destination is valid and that there is sufficient space on
the destination device.
ORA-00271: there are no logs that need archiving
Cause: An attempt was made to archive the unarchived redo log files manually, but
there are no files that need to be archived.
ORA-00272: error writing archive log string
Cause: An I/O error occurred while archiving a redo log file.
Action: Check that the output device is still available and correct any device errors
that may have occurred. Also, make certain that sufficient space for archiving is
available on the output device.
ORA-00273: media recovery of direct load data that was not logged
Cause: A media recovery session encountered a table that was loaded by the direct
loader without logging any redo information. Some or all of the blocks in this table
are now marked as corrupt.
Action: The table must be dropped or truncated so that the corrupted blocks can be
reused. If a more recent backup of the file is available, try to recover this file to
eliminate this error.
ORA-00274: illegal recovery option string
Cause: An illegal option was specified for a recovery command.
Action: Correct the syntax and retry the command.
ORA-00275: media recovery has already been started
Cause: An attempt was made to start a second media recovery operation in the same
session.
Action: Complete or cancel the first media recovery session or start another session to
perform media recovery.
ORA-00276: CHANGE keyword specified but no change number given
Cause: The CHANGE keyword was specified on the command line, but no change
number was given.
Action: Retry the command using a valid change number after the CHANGE
keyword.
ORA-00277: illegal option to the UNTIL recovery flag string
Cause: Only CANCEL, CHANGE, CONSISTENT and TIME can be used with the
UNTIL keyword.
Action: Correct the syntax.
ORA-00278: log file 'string' no longer needed for this recovery
Cause: The specified redo log file is no longer needed for the current recovery.
Action: No action required. The archived redo log file may be removed from its
current location to conserve disk space, if needed. However, the redo log file may still
be required for another recovery session in the future.
ORA-00279: change string generated at string needed for thread string

Cause: The requested log is required to proceed with recovery.
Action: Please supply the requested log with "ALTER DATABASE RECOVER
LOGFILE <file_name>" or cancel recovery with "ALTER DATABASE RECOVER
CANCEL".
ORA-00280: change string for thread string is in sequence #string
Cause: This message helps to locate the redo log file with the specified change
number requested by other messages.
Action: Use the information provided in this message to specify the required archived
redo log files for other errors.
ORA-00281: media recovery may not be performed using dispatcher
Cause: An attempt was made to use a dispatcher process for media recovery. Memory
requirements disallow this recovery method.
Action: Connect to the instance via a dedicated server process to perform media
recovery.
ORA-00282: UPI string call not supported, use ALTER DATABASE RECOVER
Cause: The given UPI call is no longer supported.
Action: Use the ALTER DATABASE RECOVER command for all recovery actions.
ORA-00283: recovery session canceled due to errors
Cause: An error during recovery was determined to be fatal enough to end the
current recovery session.
Action: More specific messages will accompany this message. Refer to the other
messages for the appropriate action.
ORA-00284: recovery session still in progress
Cause: An error during recovery was determined to be minor enough to allow the
current recovery session to continue.
Action: More specific messages will accompany this message. Refer to the other
messages for the appropriate action.
ORA-00285: TIME not given as a string constant
Cause: TIME was not followed by a string constant for the time.
Action: Enter the time enclosed in single quotation marks.
ORA-00286: no members available, or no member contains valid data
Cause: None of the members of a redo log file group are available, or the available
members do not contain complete data.
Action: If a member is temporarily offline, attempt to make it available. Make sure
that the correct filenames are being used, especially if the redo log file is being
accessed from a remote location.
ORA-00287: specified change number string not found in thread string
Cause: The given change number does not appear in any of the online redo logs for
the given thread.
Action: Check the statement to make certain a valid change number is given. Perhaps
try to use the NEXT option for archiving logs.
ORA-00000 to ORA-00877 58-23
ORA-00288: to continue recovery type ALTER DATABASE RECOVER CONTINUE

Cause: During media recovery, a new log is not required but the continuation
command is necessary to do a checkpoint and report errors.
Action: Type ALTER DATABASE RECOVER CONTINUE and recovery will resume.
ORA-00289: suggestion : string
Cause: This message reports the next redo log filename that is needed, according to
the initialization parameters LOG_ARCHIVE_DEST and LOG_ARCHIVE_FORMAT.
This message assumes that LOG_ARCHIVE_DEST and LOG_ARCHIVE_FORMAT
are the same now as when the required redo log file was archived.
Action: Consider using this filename for the next log needed for recovery.
ORA-00290: operating system archival error occurred. See error below
Cause: While attempting to archive to a redo log file, the server encountered an
unexpected operating system error.
Action: Correct the operating system error given in the messages and retry the
operation. See also your operating system-specific Oracle documentation.
ORA-00291: numeric value required for PARALLEL option
Cause: A recovery command was specified incorrectly. The PARALLEL option must
be followed by a numeric argument that specifies the degree of parallelism.
Action: Re-enter the command with a numeric argument specifying the degree of
parallelism desired.
ORA-00292: parallel recovery feature not installed
Cause: A parallel recovery was requested when the parallel recovery option is not
installed.
Action: Delete the PARALLEL clause from the RECOVER command. Also, delete the
RECOVERY_PARALLELISM parameter in the initialization file.
ORA-00293: control file out of sync with redo log
Cause: The redo log file and control file are out of sync because a non-current controle
file was specified when the instance was started.
Action: Retry the RECOVER command using the current control file, or retry the
RECOVER command using the USING BACKUP CONTROLFILE clause.
ORA-00294: invalid archivelog format specifier 'string'
Cause: An invalid format specifier was found in the LOG_ARCHIVE_FORMAT
initialization parameter. The only characters permitted following the % symbol are s,
S, t, and T.
Action: Correct the initialization file and re-start the instance.
ORA-00295: datafile/tempfile number string is invalid, must be between 1 and
string
Cause: An invalid file number was specified.
Action: Specify a valid datafile or tempfile number and retry the operation.
ORA-00296: maximum number of files (string) exceeded for RECOVER DATAFILE
LIST
Cause: The RECOVER DATAFILE LIST command specified more datafiles than are
allowed by the DB_FILES initialization parameter. This error occurs when doing
recovery with Recovery Manager, and the instance has been started with a DB_FILES
parameter specifying fewer datafiles than recovery manager needs to recover to
satisfy the user's RECOVER command.
Action: Re-start the instance with a higher value for DB_FILES.
ORA-00297: must specify RECOVER DATAFILE LIST before RECOVER
DATAFILE START
Cause: The RECOVER DATAFILE START command was issued, but no RECOVER
DATAFILE LIST commands had been issued. This only happens when doing
recovery with Recovery Manager, and is an internal error in Recovery Manager,
because Recovery Manager should always issue RECOVER DATAFILE LIST before
RECOVER DATAFILE START.
ORA-00298: Missing or invalid attribute value
Cause: A non-zero integer value is required when the following keyword attributes
are specified: TIMEOUT, EXPIRE, DELAY, NEXT
ORA-00299: must use file-level media recovery on data file string
Cause: The control file does not contain an entry for this file, so block media recovery
cannot be done.
Action: Restore the data file and perform file-level media recovery.
ORA-00300: illegal redo log block size string specified - exceeds limit of string
Cause: The specified block size of the redo log is greater than the maximum block size
for the operating system.
Action: Create the redo log on a device with a smaller block size
ORA-00301: error in adding log file 'string' - file cannot be created
Cause: The creation of the redo log file failed
Action: Check: 1) there is enough storage space on the device 2) the name of the file is
valid 3) the device is online 4) an IO error occurred Also, it is possible REUSE was
specified on the command line and a file of the incorrect size exists. Either do not
specify REUSE or use a file of the correct size.
ORA-00302: limit of string logs exceeded
Cause: The maximum number of redo log files has been exceeded.
Action: Use the CREATE CONTROLFILE command with a larger value for
MAXLOGFILES if the compatibility is lower than 10.2.0. Otherwise, allocate more
storage space for the control file.
ORA-00303: cannot process Parallel Redo
Cause: A redo log containing Parallel Redo has been detected. The current Oracle
release cannot process this format of redo.
Action: Use a later release that supports Parallel Redo. to process this log.
ORA-00304: requested INSTANCE_NUMBER is busy
Cause: An instance tried to start by using a value of the initialization parameter
INSTANCE_NUMBER that is already in use.
ORA-00000 to ORA-00877 58-25
Action: Either a) specify another INSTANCE_NUMBER, b) shut down the running

instance with this number c) wait for instance recovery to complete on the instance
with this number.
ORA-00305: log string of thread string inconsistent; 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.
Action: Specify the correct redo log file, then retry the operation.
ORA-00306: limit of string instances in this database
Cause: Starting this instance would exceed the maximum number of instances
allowed for this database. This message occurs only with STARTUP shared and
multiple instances.
Action: You cannot start more than the lower of a) port-specific limit as to the number
of instances b) the number of instances specified at create-database time
ORA-00307: requested INSTANCE_NUMBER out of range, maximum is string
Cause: The initialization parameter INSTANCE_NUMBER specified a number that
was out of range.
Action: Change INSTANCE_NUMBER to a valid range and restart the instance. The
minimum value is one and the maximum value is the lower of the operating systemspecific maximum or the MAXINSTANCES option specified in the CREATE
DATABASE statement. See also your operating system-specific Oracle
documentation.
ORA-00308: cannot open archived log 'string'
Cause: The system cannot access a required archived redo log file.
Action: Check that the off line log exists, the storage device is online, and the archived
file is in the correct location. Then attempt to continue recovery or restart the recovery
session.
ORA-00309: log belongs to wrong database
Cause: The system cannot access the archived redo log because it belongs to another
database.
Action: Specify the correct redo log file, then retry the operation.
ORA-00310: archived log contains sequence string; sequence string required
Cause: The archived log was out of sequence, probably because it was corrupt or the
wrong redo log file name was specified during recovery.
Action: Specify the correct redo log file; then retry the operation.
ORA-00311: cannot read header from archived log
Cause: An I/O error occurred when attempting to read the log file header from the
specified archived redo log file.
Action: Other messages will accompany this message. See the associated messages for
the appropriate action to take.
ORA-00312: online log string thread string: 'string'
Cause: This message reports the filename for details of another message.
Action: Other messages will accompany this message. See the associated messages for
the appropriate action to take.
ORA-00313: open failed for members of log group string of thread string
Cause: The online log cannot be opened. May not be able to find file.
Action: See accompanying errors and make log available.
ORA-00314: log string of thread string, expected sequence# string doesn't match
string
Cause: The online log is corrupted or is an old version.
Action: Find and install correct version of log or reset logs.
ORA-00315: log string of thread string, wrong thread # string in header
ORA-00316: log string of thread string, type string in header is not log file
ORA-00317: file type string in header is not log file
Cause: This is not an archived log file.
Action: Find the correct file and try again.
ORA-00318: log string of thread string, expected file size string doesn't match string
Cause: On header read the file size indicated in the control file did not match the file
size contained in the log file.
Action: Restore correct file or reset logs.
ORA-00319: log string of thread string has incorrect log reset status
Cause: Check of log file header at database open found that an online log has log reset
data that is different from the control file. The log is probably an incorrectly restored
backup.
ORA-00320: cannot read file header from log string of thread string
Cause: The file is not available.
Action: Restore the log file.
ORA-00321: log string of thread string, cannot update log file header
Cause: Cannot write to the log file.
Action: Restore the access to the file.
ORA-00322: log string of thread string is not current copy
Cause: Check of log file header at database open found that an online log appears to
be an incorrectly restored backup.
ORA-00323: Current log of thread string not useable and all others need archiving
Cause: Attempt to open thread failed because it is necessary to switch redo generation
to another online log, but all the other logs need to be archived before they can be
used.
Action: Archive the logs for the thread then retry open.
ORA-00000 to ORA-00877 58-27
ORA-00324: log file 'string' translated name 'string' too long, string characters
exceeds string limit
Cause: the translated name for a log file is too long.
Action: Choose a untranslated name that yields a shorter translated name.
ORA-00325: archived log for thread string, wrong thread # string in header
Cause: The archived log is corrupted or for another thread. Can not use the log for
applying redo.
Action: Find correct archived log.
ORA-00326: log begins at change string, need earlier change string
Cause: The archived log supplied for recovery was generated after the log that is
needed. Can not yet use the log for applying redo.
ORA-00327: log string of thread string, physical size string less than needed string
Cause: A log file has shrunk in size. This is likely to have been caused by operator or
operating system error.
Action: Restore the log file from backup. If backup is not available, drop this log and
re-create. If the database was shut down cleanly, no further action should be required;
otherwise incomplete recovery may be required.
ORA-00328: archived log ends at change string, need later change string
Cause: The archived log supplied for recovery was generated before the log that is
needed. Can not use the log for applying redo.
ORA-00329: archived log begins at change string, need change string
Cause: The archived log is not the correct log. An earlier log is needed.
Action: Restore the correct log file.
ORA-00330: archived log ends at change string, need change string
Cause: The archived log is not the correct log. A later log is needed.
ORA-00331: log version string incompatible with ORACLE version string
Cause: The log was written by incompatible version of Oracle.
Action: Recover the database with the compatible software, shut it down cleanly, then
restart with current software.
ORA-00332: archived log is too small - may be incompletely archived
Cause: The log is smaller than the space allocated in it. May be the result of a
shutdown abort while it was being written by the archiver.
Action: Get a complete version of this log and use it for recovery. There should either
be an online version of it or a copy that was successfully archived.
ORA-00333: redo log read error block string count string
Cause: An IO error occurred while reading the log described in the accompanying
error.
Action: Restore accessibility to file, or get another copy of the file.
ORA-00334: archived log: 'string'

Cause: Reporting filename for details of another error
Action: See associated error messages
ORA-00335: online log string: No log with this number, log does not exist
Cause: Reporting filename for details of another error
Action: See associated error messages
ORA-00336: log file size string blocks is less than minimum string blocks
Cause: The log file size as specified in create database is too small.
Action: Increase the log file size.
ORA-00337: log file 'string' does not exist and no size specified
Cause: An attempt to add a log found neither an existing file nor a size for creating
the file.
Action: Specify a size for the log file.
ORA-00338: log string of thread string is more recent 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 make it stop happening without correcting the
real problem. Every attempt to open the database will advance the control file change
sequence number until it is great enough.
Action: Use the current control file or do backup control file recovery to make the
control file current. Be sure to follow all restrictions on doing a backup control file
recovery.
ORA-00339: archived log does not contain any redo
Cause: The archived log is not the correct log. It is a copy of a log file that has never
been used for redo generation, or was an online log being prepared to be the current
log.
ORA-00340: IO error processing online log string of thread string
Cause: An IO error occurred on the named online log.
Action: Restore accessibility to file, or restore file from backup.
ORA-00341: log string of thread string, wrong log # string in header
Cause: The internal information in an online log file does not match the control file.
ORA-00342: archived log does not have expected resetlogs SCN string
Cause: Recovery was given a log that does not belong to current incarnation or one of
the parent incarnation. There should be another log that contains the correct redo.
Action: Supply the correct log file.
ORA-00344: unable to re-create online log 'string'
Cause: An I/O failure occurred when attempting to re-create an online as part of
either ALTER DATABASE OPEN RESETLOGS or ALTER DATABASE CLEAR
LOGFILE command.
Action: Correct the file/device as indicated by accompanying errors.
ORA-00000 to ORA-00877 58-29
ORA-00345: redo log write error block string count string

Cause: An IO error has occurred while writing the log
Action: Correct the cause of the error, and then restart the system. If the log is lost,
apply media/incomplete recovery.
ORA-00346: log member marked as STALE and closed
Cause: A log file member was no longer complete.
Action: Correct the underlying problem by referring to the other error messages
found with this one.
ORA-00347: log string of thread string, expected block size string doesn't match
string
Cause: On header read the blocksize indicated in the control file did not match the
blocksize contained in the log file.
ORA-00348: single-process redo failure. Must abort instance
Cause: A failure occurred during a critical portion of the log code during single
process operation. This error does not occur during normal multi-process operation.
Action: Shutdown abort and warmstart the database.
ORA-00349: failure obtaining block size for 'string'
Cause: The operating system was unable to determine the blocksize for the given
filename.
Action: Consult the accompanying error message, and correct the device or specify
another filename.
ORA-00350: log string of instance string (thread string) needs to be archived
Cause: The command cannot be done 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 an
UNARCHIVED option then it can be used. However this may result in making
backups unuseable, and forcing the drop of some offline files.
ORA-00351: recover-to time invalid
Cause: The time specified in a recover-until statement must be after January 1st 1988.
Action: Specify a time after January 1st 1988.
ORA-00352: all logs for thread string need to be archived - cannot enable
Cause: Attempting to enable a thread with all logs needing to be archived, and media
recovery has been enabled. There is no log that can be made the new current log for
the thread.
Action: Archive a log for the thread or disable media recovery.
ORA-00353: log corruption near block string change string time string
Cause: Some type of redo log corruption has been discovered. This error describes the
location of the corruption. Accompanying errors describe the type of corruption.
Action: Do recovery with a good version of the log or do incomplete recovery up to
the indicated change or time.
ORA-00354: corrupt redo log block header

Cause: The block header on the redo block indicated by the accompanying error, is
not reasonable.
Action: Do recovery with a good version of the log or do time based recovery up to
the indicated time. If this happens when archiving, archiving of the problem log can
be skipped by clearing the log with the UNARCHIVED option. This must be followed
by a backup of every datafile to insure recoverability of the database.
ORA-00355: change numbers out of order
Cause: A change number found in the redo log is lower than a previously
encountered change number. The log is corrupted in some way. The corruption may
be at the earlier change or at this one.
the indicated time.
ORA-00356: inconsistent lengths in change description
Cause: A change record in the redo log contains lengths that do not add up to a
consistent value. The log is corrupted in some way.
the indicated time.
ORA-00357: too many members specified for log file, the 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 set when the database is created.
Action: Use fewer log file members.
ORA-00358: Too many file members specified, the maximum is string
Cause: A create or alter statement specified too many members in a parenthesised file
list.
Action: Specify a number of file members that is within the port-defined limit.
ORA-00359: logfile group string does not exist
Cause: An add logfile member or drop logfile request specified a logfile group
number that does not exist.
Action: Check the configuration of the log files and reissue the command.
ORA-00360: not a logfile member: string
Cause: A filename was given to drop logfile member that is not a part of the database,
or which is a data file.
Action: Supply a valid logfile member name.
ORA-00361: cannot remove last log member string for group string
Cause: An attempt has been made to remove the last member of a log file group.
Action: If desired, delete the entire log, by using DROP LOGFILE.
ORA-00362: member is required to form a valid logfile in group string
Cause: A request to drop a logfile member was denied because it would remove data
required to form a complete logfile.
Action: If desired, delete the entire log (after archiving if required), by using DROP
LOGFILE;
ORA-00000 to ORA-00877 58-31
ORA-00363: log is not the archived version

Cause: The log given to recovery is a backup of the online version from the time it
was the current log. The archived version of the log would not be marked as end of
thread. This error can also be caused by failing to list the current log of an enabled
thread in a CREATE CONTROLFILE command.
Action: Find the archived version of the log and supply its name. If this is media
recovery immediately following a CREATE CONTROLFILE, be sure the current log
for this thread was included.
ORA-00364: cannot write header to new log member
Cause: An i/o error occurred when attempting to write the header to a log member
that is being added to an existing group.
Action: See accompanying errors. Fix problem or use another file.
ORA-00365: the specified log is not the correct next log
Cause: The specified log failed to pass checks to ensure it corresponds to the log that
was just applied. This is probably the result of using a log that was generated against
a cold backup image of the database.
Action: Find the log that was generated by this copy of the database and give that
filename to recovery.
ORA-00366: log string of thread string, checksum error in the file header
Cause: The file header for the redo log contains a checksum that does not match the
value calculated from the file header as read from disk. This means the file header is
corrupted
ORA-00367: checksum error in log file header
Cause: The file header for the redo log contains a checksum that does not match the
value calculated from the file header as read from disk. This means 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 not vaild. It has a
checksum that does not match the block contents.
the indicated time. If this happens when archiving, archiving of the problem log can
be skipped by clearing the log with the UNARCHIVED option. This must be followed
by a backup of every datafile to insure recoverability of the database. Restore correct
file or reset logs.
ORA-00369: Current log of thread string not useable and other log being cleared
Cause: Attempt to open thread failed because it is necessary to switch redo generation
to another online log, but all the other logs are being cleared or need to be archived
before they can be used.
Action: If the ALTER DATABASE CLEAR LOGFILE command is still active then wait
for it to complete. Otherwise reissue the CLEAR command. If there are other online
logs for the thread, that are not being cleared, then archive the logs.
ORA-00370: potential deadlock during kcbchange operation
Cause: Error code used internally by software. Should never be reported
Action: Treat as internal error. See error 600.

ORA-00371: not enough shared pool memory, should be at least string bytes
Cause: The SHARED_POOL_SIZE initialization parameter was too small.
Action: Increase the parameter value.
ORA-00372: file string cannot be modified at this time
Cause: attempting to modify the contents of a file that cannot be modified. The file is
most likely part of a read only tablespace but may be in the process of going offline,
or the database may be in the process of closing.
Action: check the status of the file and its tablespace
ORA-00373: online log version string incompatible with ORACLE version string
Cause: The online log was written by incompatible version of Oracle. Can occur when
the log file was created by either a new or older version of Oracle.
Action: Recover the database with the compatible software, shut it down cleanly, then
restart with current software.
ORA-00374: parameter db_block_size = string invalid ; must be a multiple of string
in the range [string..string]
Cause: invalid value for db_block_size parameter
Action: adjust parameter and restart
ORA-00376: file string cannot be read at this time
Cause: attempting to read from a file that is not readable. Most likely the file is offline.
Action: Check the state of the file. Bring it online
ORA-00377: Frequent backups of file string causing write operation to stall
Cause: Backups are occurring too frequently on this file. Each time a new backup is
started for a file, any writes which have been previously issued (but not completed)
have to be re-issued. If hot backups are started very, very frequently, it is possible that
some writes will be re-issued repeatedly and never complete.
Action: Increase the interval between begin hot-backup commands for this file.
ORA-00378: buffer pools cannot be created as specified
Cause: Either the number of buffers or the number of lru latches is too small to satisfy
the specified buffer pool configuration.
Action: Either increase the number of buffers and/or number of lru latches or
configure smaller buffer pools.
ORA-00379: no free buffers available in buffer pool string for block size stringK
Cause: All buffers in the specified buffer pool for the specified block size are in use
and no free buffers are available.
Action: Increase the number of buffers in the specified pool for the specified block
size
ORA-00380: cannot specify db_stringk_cache_size since stringK is the standard
block size
Cause: User specified the parameter db_nk_cache_size (where n is one of 2,4,8,16,32),
while the standard block size for this database is equal to n Kbytes. This is illegal.
ORA-00000 to ORA-00877 58-33
Action: Specify the standard block size cache using db_cache_size (DEFAULT pool)
(and db_recycle_cache_size, db_keep_cache_size if additional buffer pools are
required). Do NOT use the corresponding db_nk_cache_size parameter for the
standard block size.
ORA-00381: cannot use both new and old parameters for buffer cache size
specification
Cause: User specified one or more of { db_cache_size , db_recycle_cache_size,
db_keep_cache_size, db_nk_cache_size (where n is one of 2,4,8,16,32),
db_cache_advice } AND one or more of { db_block_buffers, buffer_pool_keep ,
buffer_pool_recycle }. This is illegal.
Action: Use EITHER the old (pre-Oracle_8.2) parameters OR the new ones. Don't
specify both. If old size parameters are specified in the parameter file, you may want
to replace them with new parameters since the new parameters can be modified
dynamically and allow you to configure additional caches for additional block sizes.
Cache advisory can only be enabled with the new cache parameters.
ORA-00382: string not a valid block size, valid range [string..string]
Cause: User specified a value for db_nk_cache_size where n is one of {2, 4, 8, 16, 32},
but nk is not a valid block size for this platform.
Action: Remove corresponding parameter from the "init.ora" file and restart the
instance.
ORA-00383: DEFAULT cache for blocksize string cannot be reduced to zero
Cause: User attempted to reduce db_cache_size to zero, or attempted to to reduce
db_nK_cache_size to zero while there were still online tablespaces with blocksize nK.
Note that since the SYSTEM tablespace cannot be taken offline, it is always illegal to
set db_cache_size to zero.
Action: Offline any tablespaces with the corresponding blocksize and then perform
the operation again.
ORA-00384: Insufficient memory to grow cache
Cause: The system could not allocate sufficient memory to grow the cache to the
specified size.
Action: Attempt a smaller increase in the value of the parameter.
ORA-00385: cannot enable Very Large Memory with new buffer cache parameters
Cause: User specified one or more of { db_cache_size , db_recycle_cache_size,
db_keep_cache_size, db_nk_cache_size (where n is one of 2,4,8,16,32) } AND
use_indirect_data_buffers is set to TRUE. This is illegal.
Action: Very Large Memory can only be enabled with the old (pre-Oracle_8.2)
parameters.
ORA-00386: use_indirect_data_buffers not supported
Cause: The system could not allocate sufficient memory to grow the cache to the
specified size.
Action: Attempt a smaller increase in the value of the parameter.
ORA-00388: dependent redo for buffers is lost
Cause: The instance contained buffers that had non-durable changes and depended
on redo in another thread that was lost because of that thread crash. No data are lost
because changes to such buffers cannot be commited while they are non-durable.
Action: Restart the instance.
ORA-00390: log string of thread string is being cleared, cannot become current log
Cause: An attempt to switch to a new online log for the redo thread failed because no
reusable log could be found. This log is being cleared and will be useable when the
clearing completes. The command that began the clearing may have terminated
without completing the clearing.
Action: If the clear command is still executing then wait for its completion. If it
terminated then reissue the clear command, or drop the log.
ORA-00391: All threads must switch to new log format at the same time
Cause: An attempt to switch the current log of a single thread is not allowed because
the compatiblity requirements force a new log format version number. When
changing log formats, all threads must switch to the new format at the same time.
Action: Open the database to cause the coordinated log switch. If that is not possible
then return to the same software version and compatibility setting last used to open
the database.
ORA-00392: log string of thread string is being cleared, operation not allowed
Cause: An operation encountered this online log in the middle of being cleared. The
command that began the clearing may have terminated without completing the
clearing.
Action: If the clear command is still executing then wait for its completion. If it
terminated then reissue the clear command, or drop the log.
ORA-00393: log string of thread string is needed for recovery of offline datafiles
Cause: Log cannot be cleared because the redo in it is needed to recover offline
datafiles. It has not been archived so there is no other copy available. If the log is
cleared the tablespaces containing the files will have to be dropped.
Action: Archive the log then repeat the clear command. If archiving is not possible,
and dropping the tablespaces is acceptible, then add the clause UNRECOVERABLE
DATAFILE at the end of the clear command.
ORA-00394: online log reused while attempting to archive it
Cause: It has been detected that an online log that is being archived has been reused
Action: Cannot archive the logfile anymore since it has been overwritten
ORA-00395: online logs for the clone database must be renamed
Cause: A clone database open forces logfile renaming to avoid overwriting the
primary logfiles
Action: Rename the logfiles manually or using the log_file_name_convert
initialization parameter
ORA-00396: error string required fallback to single-pass recovery
Cause: The indicated error caused two-pass instance or crash recovery to fail.
Recovery was retried with an alternate (slower) method to avoid the error.
Action: Correct the cause of the indicated error (also recorded) so that future instance
or crash recovery can succeed with the two-pass algorithm. This usually requires
making more main memory available to the recovery process.
ORA-00397: instance recovery process terminated with error
Cause: The foreground process doing instance recovery died.
Action: Check the foreground trace file for the cause of recovery failure.
ORA-00000 to ORA-00877 58-35
ORA-00398: abort thread recovery due to reconfiguration

Cause: Global enqueue service reconfiguration occurred during instance/crash
recovery.
Action: This is used internally, no action is required.
ORA-00399: corrupt change description in redo log
Cause: A change vector in the redo log failed validation checks.
the indicated time.
ORA-00400: invalid release value string for parameter string
Cause: The release level given for the specified init parameter is invalid.
Action: Correct the parameter value in the parameter file and retry.
ORA-00401: the value for parameter string is not supported by this release
Cause: The value specified cannot be supported by this release of the software.
Action: Choose an appropriate value, or remove the parameter value to use the
default value.
ORA-00402: database changes by release string cannot be used by release string
Cause: Changes have been made to the database that require a newer software release
or that violate the compatibility parameters.
Action: Use a version of the software that can understand the changes or relax the
compatibility requirements in the init file.
ORA-00403: string (string) is not the same as other instances (string)
Cause: Another instance has set the compatible or compatible no recovery parameters
differently than this instance.
Action: Change the parameters of the current instance to match other instances
already running.
ORA-00404: Convert file not found: 'string'
Cause: The file used for converting the database from V7 to V8 could not be found.
Action: Verify that the migration process has been started on this database and that
the convert filename is accessable.
ORA-00405: compatibility type "string"
Cause: Reporting a type associated with another error.
Action: See accompanying error
ORA-00406: COMPATIBLE parameter needs to be string or greater
Cause: The COMPATIBLE initialization parameter is not high enough to allow the
operation. Allowing the command would make the database incompatible with the
release specified by the current COMPATIBLE parameter.
Action: Shutdown and startup with a higher compatibility setting.
ORA-00407: rolling upgrade from release string.string to string.string is not allowed
Cause: Another instance executing software at a different point release already has
the database mounted.
Action: Shutdown all instances then startup with the new software.
ORA-00408: parameter string is set to TRUE

Cause: Reporting the parameter that resulted in the compatibility error.
ORA-00409: COMPATIBLE needs to be string or higher to use AUTO SEGMENT
SPACE MANAGEMENT
Cause: This is due to migrating from an older release of Oracle with tablespaces
created using AUTO SEGMENT SPACE MANAGEMENT. To open the database, the
COMPATIBLE parameter needs to be set to the specified value.
Action: Shutdown and startup with the specified compatibility setting.
ORA-00436: ORACLE is not licensed. Contact Oracle Corp. for assistance
ORA-00437: ORACLE feature is not licensed. Contact Oracle Corp. for assistance
Cause: ORACLE feature is not licensed.
Action: Contact ORACLE for assistance.
ORA-00438: string Option not installed
Cause: The specified option is not installed.
Action: Purchase and install the option.
ORA-00439: feature not enabled: string
Cause: The specified feature is not enabled.
Action: Do not attempt to use this feature.
ORA-00443: background process "string" did not start
Cause: The specified process did not start.
Action: Ensure that the executable image is in the correct place with the correct
protections, and that there is enough memory.
ORA-00444: background process "string" failed while starting
Cause: Usually due to a bad (or non-existent) background process image.
Action: Get a good background process image.
ORA-00445: background process "string" did not start after string seconds
Cause: The specified process did not start after the specified time.
Action: Ensure that the background did not die and leave a trace file.
ORA-00446: background process started when not expected
Cause: The background process specified started up AFTER the RDBMS was already
running.
Action: If nobody at your site started the process, then this is an internal error.
ORA-00447: fatal error in background process
Cause: One of the background processes died unexpectedly.
Action: Warm start the system.
ORA-00448: normal completion of background process
Cause: One of the background processes completed normally (i.e. exited). The
background process thinks that somebody asked it to exit.
Action: Warm start the system.
ORA-00000 to ORA-00877 58-37
ORA-00449: background process 'string' unexpectedly terminated with error string

Cause: A foreground process needing service from a background process has
discovered the process died.
Action: Consult the error code, and the trace file for the process.
ORA-00450: background process 'string' did not start
Cause: The specified process did not start.
Action: Consult the error code, and the trace file for the process.
ORA-00451: foreground process died unexpectedly
Cause: The foreground process for the new connection did not start.
Action: Reconnect to Oracle.
ORA-00452: foreground process unexpectedly terminated with error string
Cause: The foreground process for the new connection did not start.
Action: Reconnect to Oracle.
ORA-00453: backgroud process 'string' is dead
Cause: The background process that was being messaged was dead or its incarnation
was invalid.
Action: Restart the background process.
ORA-00454: The background process 'string' is running
Cause: An attempt to spawn a background process that was already running failed.
Action: None
ORA-00455: timeout waiting for background process 'string' cleanup
Cause: The state of the background process was not cleaned up.
Action: None
ORA-00469: CKPT process terminated with error
Cause: The checkpoint process died
Action: Warm start instance
ORA-00470: LGWR process terminated with error
Cause: The log writer process died
ORA-00471: DBWR process terminated with error
Cause: The database writer process died
ORA-00472: PMON process terminated with error
Cause: The process cleanup process died
ORA-00473: ARCH process terminated with error
Cause: The archive process died
ORA-00474: SMON process terminated with error

Cause: The system cleanup process died
ORA-00475: TRWR process terminated with error
Cause: The system tracing process died
ORA-00476: RECO process terminated with error
Cause: The distributed transaction (two-phase commit) recovery process died.
ORA-00477: SNP* process terminated with error
Cause: A materialized view refresh process died
Action: PMON will restart SNP process shortly. If SNP process does not get started,
contact Oracle support.
ORA-00478: SMON process terminated due to error string
Cause: SMON was unable to service the requests due to error in cleanup of resources
ORA-00479: RVWR process terminated with error string
Cause: The RVWR process died
ORA-00480: LCK* process terminated with error
Cause: A system lock process died
ORA-00481: LMON process terminated with error
Cause: The global enqueue service monitor process died
ORA-00482: LMD* process terminated with error
Cause: A global enqueue service daemon process died
ORA-00483: During shutdown a process abnormally terminated
Cause: One of the background processes did not exit normally at or near the time of
shutdown.
Action: Use shutdown abort.
ORA-00484: LMS* process terminated with error
Cause: A global cache service process died
ORA-00485: DIAG process terminated with error string
Cause: A global diagnostic process died
Action: Wait for process to restart
ORA-00000 to ORA-00877 58-39
ORA-00486: ASMB process terminated with error

Cause: An ASM background process died.
Action: Warm start instance. Also check that ASM Instance is running.
ORA-00487: CTWR process terminated with error
Cause: The change tracking process died
ORA-00488: RBAL process terminated with error
Cause: The ASM rebalance coordinator process died.
Action: Warm start instance.
ORA-00489: ARB* process terminated with error
Cause: An ASM rebalance worker process died.
Action: Wait for process to restart.
ORA-00490: PSP process terminated with error
Cause: The process spawner died
ORA-00491: RMS0 process terminated with error
Cause: The RAC Management Process died
Action: n/a
ORA-00492: GTX* process terminated with error
Cause: A global transaction background process died.
ORA-00493: GMON process terminated with error
Cause: The ASM disk group monitor process died
ORA-00494: enqueue string held for too long (more than string seconds) by 'inst
string, osid string'
Cause: The specified process did not release the enqueue within the maximum
allowed time.
Action: Reissue any commands that failed and contact Oracle Support Services with
the incident information.
ORA-00495: GEN0 process terminated with error
Cause: The generic background processing process died.
Action: Warm start the instance.
ORA-00496: LMHB process terminated with error
Cause: The LM heartbeat monitor process died.
ORA-00497: XDMG process terminated with error
Cause: The Cell automation manager process terminated with error.
Action: PMON will restart XDMG process shortly. If XDMG process does not restart,
ORA-00498: XDWK process terminated with error
Cause: The Cell automation worker actions process terminated with error.
Action: PMON will restart XDWK process shortly. If XDWK process does not restart,
ORA-00499: XDMG repeatedly failed to initialize terminating the instance.
Cause: The Cell automation manager process repeatedly failed to initialize.
Action: Examine the alert log for the reason prior attempts to start XDMG failed. If it
is due to user error or bad configuration, fix it and restart the instance. Otherwise,
ORA-00500: Listener registration process terminated with an error.
Cause: The listener registration process died.
ORA-00566: cannot request processor group - NUMA not enabled
Cause: Cannot start process in a requested processor group when the NUMA feature
is disabled.
Action: Start the process without requesting a NUMA processor group.
ORA-00567: Requested processor group string is too large (maximum string)
Cause: The process could not be started in the requested processor group.
Action: Start the process in another processor group.
ORA-00568: Maximum number of interrupt handlers exceeded
Cause: User specified too many ^c handlers
Action: Remove some old handlers.
ORA-00569: Failed to acquire global enqueue.
Cause: A prior error occurred on one of the instances in the cluster. Typically errors
are caused by shared pool resource contention.
Action: Check for and resolve prior errors on all instances in the cluster. If there is
shared pool resource contention, increase the SHARED_POOL_SIZE, DML_LOCKS,
PROCESSES, TRANSACTIONS, CLUSTER_DATABASE_INSTANCES and
PARALLEL_MAX_SERVERS initialization parameters.
ORA-00574: osndnt: $CANCEL failure (break)
ORA-00575: osndnt: $QIO failure (send out-of-band break)
ORA-00576: in-band break protocol error
ORA-00577: out-of-band break protocol error
ORA-00578: reset protocol error
ORA-00579: osndnt: server received malformed connection request
ORA-00580: protocol versions do not match
ORA-00000 to ORA-00877 58-41
ORA-00581: osndnt: cannot allocate context area

ORA-00582: osndnt: cannot deallocate context area
ORA-00583: osndnt: $TRNLOG failure
ORA-00584: cannot close connection
ORA-00585: host name has incorrect form
ORA-00586: osndnt: LIB$ASN_WTH_MBX failure
ORA-00587: cannot connect to remote host
ORA-00588: message from host was too short
ORA-00589: message from host had incorrect data length
ORA-00590: message from host had incorrect message type
ORA-00591: incorrect number of bytes written
ORA-00592: osndnt: $QIO failure (mailbox queue)
ORA-00593: osndnt: $DASSGN failure (network device)
ORA-00594: osndnt: $DASSGN failure (mailbox)
ORA-00595: osndnt: $QIO failure (receive)
ORA-00596: osndnt: $QIO failure (send)
ORA-00597: osndnt: $QIO failure (mailbox requeue)
ORA-00598: osndnt: $QIO failure (mailbox read)
ORA-00600: internal error code, arguments: [string], [string], [string], [string],
[string], [string], [string], [string], [string], [string], [string], [string]
Cause: This is the generic internal error number for Oracle program exceptions. It
indicates that a process has encountered a low-level, unexpected condition. The first
argument is the internal message number. This argument and the database version
number are critical in identifying the root cause and the potential impact to your
system.
Action: Visit My Oracle Support to access the ORA-00600 Lookup tool (reference Note
600.1) for more information regarding the specific ORA-00600 error encountered. An
Incident has been created for this error in the Automatic Diagnostic Repository
(ADR). When logging a service request, use the Incident Packaging Service (IPS) from
the Support Workbench or the ADR Command Interpreter (ADRCI) to automatically
package the relevant trace information (reference My Oracle Support Note 411.1). The
following information should also be gathered to help determine the root cause: changes leading up to the error - events or unusual circumstances leading up to the
error - operations attempted prior to the error - conditions of the operating system
and databases at the time of the error Note: The cause of this message may manifest
itself as different errors at different times. Be aware of the history of errors that
occurred before this internal error.
ORA-00601: cleanup lock conflict

Cause: PMON process runs into lock conflict trying to recovery processes
Action: This is trapped internally, no action necessary
ORA-00602: internal programming exception
Cause: Internal programming exception
Action: Report as bug
ORA-00603: ORACLE server session terminated by fatal error
Cause: An Oracle server session was in an unrecoverable state.
Action: Log in to Oracle again so a new server session will be created automatically.
Examine the session trace file for more information.
ORA-00604: error occurred at recursive SQL level string
Cause: An error occurred while processing a recursive SQL statement (a statement
applying to internal dictionary tables).
Action: If the situation described in the next error on the stack can be corrected, do so;
otherwise contact Oracle Support.
ORA-00606: Internal error code
Cause: A call to deferred upi functions was made in non deferred mode
ORA-00607: Internal error occurred while making a change to a data block
Cause: An internal error or memory exception occurred while Oracle was applying
redo to a data block.
Action: call Oracle Support
ORA-00608: testing error [string] [string] [string] [string] [string]
Cause: Internal error reserved for testing.
Action: call Oracle Support
ORA-00609: could not attach to incoming connection
Cause: Oracle process could not answer incoming connection
Action: If the situation described in the next error on the stack can be corrected, do so;
ORA-00610: Internal error code
Cause: Oracle process started too late
Action: This error should never be seen by the customer. Contact Oracle Support
ORA-00700: soft internal error, arguments: [string], [string], [string], [string],
[string], [string], [string], [string], [string], [string], [string], [string]
Cause: Internal inconsistency that will not crash a process
Action: Report as a bug - the first argument is the internal error.
ORA-00701: object necessary for warmstarting database cannot be altered
Cause: Attempt to alter or drop a database object (table, cluster, or index) which are
needed for warmstarting the database.
Action: None
ORA-00000 to ORA-00877 58-43
ORA-00702: bootstrap verison 'string' inconsistent with version 'string'

Cause: The reading version of the boostrap is incompatible with the current bootstrap
version.
Action: Restore a version of the software that is compatible with this bootstrap
version.
ORA-00703: maximum number of row cache instance locks exceeded
Cause: There are not enough row cache enqueues.
Action: Increase the row cache enqueue parameter and warm start the system.
ORA-00704: bootstrap process failure
Cause: Failure in processing bootstrap data - see accompanying error.
Action: Contact your customer support representative.
ORA-00705: inconsistent state during start up; shut down the instance, then restart
it
Cause: A previous attempt to start an instance was terminated.
Action: Shut down the instance completely, then restart it.
ORA-00706: error changing format of file 'string'
Cause: An attempt to change the block0 format of the specified file failed because the
file is read-only or offline.
Action: Make the file read-write or bring the file online and set the BLK0_FMTCHG
event.
ORA-00710: new tablespace name is the same as the old tablespace name
Cause: An attempt to rename a tablespace failed because the new name is the same as
the old name.
ORA-00711: new tablespace name is invalid
Cause: An attempt to rename a tablespace failed because the new name is invalid.
Action: Choose a valid new name and retry the command.
ORA-00712: cannot rename system tablespace
Cause: An attempt to rename the system tablespace failed.
ORA-00720: ALTER DATABASE RESET COMPATIBILITY command has been desupported
Cause: ALTER DATABASE RESET COMPATIBILITY command has been desupported since Oracle 10i.
ORA-00721: changes by release string cannot be used by release string
Cause: An attempt to import a tablespace failed because the tablespace contains
changes that require a newer software release or that violate the compatibility
parameters.
Action: Use a version of the software that can understand the changes or relax the
compatibility requirements in the initialization parameter file.
ORA-00722: Feature "string"

Cause: Reporting name of the feature for details of another error.
Action: See associated error message.
ORA-00723: Initialization parameter COMPATIBLE must be explicitly set
Cause: Oracle detected that the initialization parameter COMPATIBLE was not
explicitly specified, and the compatibility of the database is lower than the default
value of the COMPATIBLE parameter. In order to use the new compatible setting, the
intialization parameter must be explicitly set by the user.
Action: Explicitly set the value of COMPATIBLE parameter either in PFILE or
SPFILE, whichever is used.
ORA-00724: ALTER DATABASE CONVERT command has been de-supported
Cause: ALTER DATABASE CONVERT command has been de-supported since Oracle
10i.
ORA-00725: Desupported ALTER DATABASE SET STANDBY clause specified:
string
Cause: A deprecated ALTER DATABASE SET STANDBY was specified.
ORA-00740: datafile size of (string) blocks exceeds maximum file size
Cause: The user specified datafile size exceeded maximum file size.
Action: Please check REFERENCE for maximum size. Reduce the size and retry.
ORA-00741: logfile size of (string) blocks exceeds maximum logfile size
Cause: The user specified logfile size exceeded maximum logfile size.
Action: Please check REFERENCE for maximum size. Reduce the size and retry.
ORA-00742: Log read detects lost write in thread string sequence string block string
Cause: Either a write issued by Oracle was lost by the underlying operating system or
storage system or an Oracle internal error occurred.
Action: The trace file shows the lost write location. Dump the problematic log file to
see whether it is a real lost write. Contact Oracle Support Services.
ORA-00750: database has been previously mounted and dismounted
Cause: The instance has already mounted and dismounted the database, which is
only allowed once in its lifetime.
Action: Shut down the database.
ORA-00751: could not obtain resilvering status for file
Cause: An error occurred while obtaining the mirror resilvering status of a file.
Action: Refer to other error messages shown for additional details of the problem.
ORA-00752: recovery detected a lost write of a data block
Cause: A data block write to storage was lost during normal database operation on
the primary database.
Action: Shutdown the primary database and activate the physical standby database to
failover. Call Oracle Support Services. See the Data Guard documentation for details.
ORA-00000 to ORA-00877 58-45

Cause: A data block write to storage was lost during normal redo database operation
on the standby database or during recovery on a primary database.
Action: Close the database and try the RECOVER MANAGED STANDBY
DATABASE (on the standby database) or RECOVER DATABASE ... FORCE START
AT (on the primary database) statement starting at the SCN of the bad block that was
printed already. See the Administrator's Guide for details.
ORA-00754: recovery detected a data block with invalid SCN
Cause: An error caused a data block mismatch with a log record.
Action: If running on a primary database in recovery mode, you may perform a pointin-time recovery to an earlier time. Otherwise, call Oracle Support Services. See the
Administrator's Guide for details.
Cause: A data block write to storage was lost during normal redo database operation
on the standby database or during recovery on a primary database.
Action: Close the database and try the RECOVER MANAGED STANDBY
DATABASE (on the standby database) or RECOVER DATABASE ... FORCE START
AT (on the primary database) statement starting at the SCN of the bad block that was
printed already. See the Administrator's Guide for details.
ORA-00758: recovery detected a block with inconsistent flag values set
Action: If running on a primary database in recovery mode, you may perform a pointin-time recovery to an earlier time. Otherwise, call Oracle Support Services. See the
Administrator's Guide for details.
ORA-00816: error message translation failed
ORA-00820: Specified value of sga_max_size is too small, needs to be at least
stringM
Cause: The specified value of sga_max_size is too small for the SGA to accommodate
all of the necessary SGA components such as the log buffer, buffer pools, shared pool,
etc.
Action: Set sga_max_size to the recommended value or reduce the values of any SGA
component size parameters you have specified.
ORA-00821: Specified value of sga_target stringM is too small, needs to be at least
stringM
Cause: The specified value of sga_target is too small for the SGA to accommodate all
of the necessary SGA components such as the log buffer, buffer pools, shared pool,
etc.
Action: Set sga_target to the recommended value or reduce the values of any SGA
component size parameters you have specified.
ORA-00822: MMAN process terminated with error
Cause: The Memory Management process died.
ORA-00823: Specified value of sga_target greater than sga_max_size
Cause: The specified value of sga_target is greater than sga_max_size.
Action: Increase sga_max_size to match up with sga_target or decrease sga_target to

match up with sga_maxsize.
ORA-00824: cannot set SGA_TARGET or MEMORY_TARGET due to existing
internal settings
Cause: Could not set SGA_TARGET or MEMORY_TARGET due to current parameter
settings.
Action: Check the other error messages for additional information.
ORA-00825: cannot set DB_BLOCK_BUFFERS if SGA_TARGET or
MEMORY_TARGET is set
Cause: SGA_TARGET or MEMORY_TARGET set with DB_BLOCK_BUFFERS set.
Action: Do not set SGA_TARGET, MEMORY_TARGET or use new cache parameters,
and do not use DB_BLOCK_BUFFERS which is an old cache parameter.
ORA-00826: cannot set SGA_TARGET or MEMORY_TARGET for an ASM
instance
Cause: SGA_TARGET or MEMORY_TARGET set for an ASM instance.
Action: Do not set SGA_TARGET or MEMORY_TARGET.
ORA-00827: could not shrink sga_target to specified value
Cause: Attempted to shrink the SGA to the specified value but did not succeed
because the SGA components could not be shrunk as they were already at their
minimum sizes.
Action: Do not set sga_target to a value below the current value without first
shrinking the individual SGA components.
ORA-00828: specified value of shared_pool_reserved_size inconsistent with
internal settings
Cause: Unable to set shared_pool_reserved_size to specified value if SGA_TARGET
set, either because the specified value is too small, or because it is too large for the
current internal size of shared pool. More details can be found in the alert log.
Action: If possible, do not set shared_pool_reserved_size without setting
shared_pool_size if SGA_TARGET set. Examine the alert log for information about
current internal size of shared pool, and valid range of values for
shared_pool_reserved_size.
ORA-00830: cannot set statistics_level to BASIC with auto-tune SGA enabled
Cause: The user attempted to set statistics_level to BASIC with auto-tune SGA
enabled which cannot be done because auto-tune SGA cannot work with
statistics_level set to BASIC.
Action: Disable auto-tune SGA and try setting the statistics_level to BASIC again.
ORA-00832: no streams pool created and cannot automatically create one
Cause: A database feature which needs STREAMS SGA was being used, however, the
streams_pool_size parameter was not defined and the value of db_cache_size was too
small to permit an automatic transfer of SGA to the streams pool from the buffer
cache.
Action: Please set the parameter streams_pool_size or set SGA_TARGET.
ORA-00000 to ORA-00877 58-47
ORA-00837: Specified value of MEMORY_TARGET greater than

MEMORY_MAX_TARGET
Cause: The specified value of MEMORY_TARGET was greater than
MEMORY_MAX_TARGET.
Action: Set MEMORY_TARGET less than or equal to MEMORY_MAX_TARGET.
ORA-00838: Specified value of MEMORY_TARGET is too small, needs to be at
least stringM
Cause: The specified value of MEMORY_TARGET was less than the sum of the
specified values for SGA_TARGET and PGA_AGGREGATE_TARGET.
Action: Set MEMORY_TARGET to at least the recommended value.
ORA-00839: SGA_TARGET cannot be modified to the specified value
Cause: The specified value of SGA_TARGET was not compatible with current settings
of PGA_AGGREGATE_TARGET and MEMORY_TARGET/
MEMORY_MAX_TARGET.
Action: Set SGA_TARGET to be no more than the difference of MEMORY_TARGET/
MEMORY_MAX_TARGET and PGA_AGGREGATE_TARGET. Also ensure that the
current PGA memory used for non-auto workareas is low.
ORA-00840: PGA_AGGREGATE_TARGET cannot be modified to the specified
value
Cause: The specified value of PGA_AGGREGATE_TARGET was not compatible with
current settings of SGA_TARGET and MEMORY_TARGET/
MEMORY_MAX_TARGET.
Action: Set PGA_AGGREGATE_TARGET to be no more than the difference of
MEMORY_TARGET/MEMORY_MAX_TARGET and SGA_TARGET.
ORA-00841: MEMORY_TARGET not supported on this system
Cause: MEMORY_TARGET parameter was not supported on this system as shmfs
was disabled.
Action: Refer to documentation for a list of supported systems.
ORA-00842: DB_BLOCK_BUFFERS cannot be set with SGA_TARGET or
MEMORY_TARGET
Cause: DB_BLOCK_BUFFERS was incompatible with SGA_TARGET and
MEMORY_TARGET.
Action: Remove the incompatible parameter setting.
ORA-00843: Parameter not taking MEMORY_MAX_TARGET into account
Cause: The parameter was larger than MEMORY_MAX_TARGET.
Action: Check the other error messages for additional information about the
parameter. Set the parameter to a lower value than MEMORY_MAX_TARGET.
ORA-00844: Parameter not taking MEMORY_TARGET into account
Cause: The parameter was larger than MEMORY_TARGET.
Action: Check the other error messages for additional information about the
parameter. Set the parameter to a lower value than MEMORY_TARGET.
ORA-00845: MEMORY_TARGET not supported on this system

Cause: The MEMORY_TARGET parameter was not supported on this operating
system or /dev/shm was not sized correctly on Linux.
Action: Refer to documentation for a list of supported operating systems. Or,
size /dev/shm to be at least the SGA_MAX_SIZE on each Oracle instance running on
the system.
ORA-00846: could not shrink MEMORY_TARGET to specified value
Cause: Attempted to shrink MEMORY_TARGET to the specified value but did not
succeed because the PGA and SGA components could not be shrunk.
Action: Do not set MEMORY_TARGET to a value below the current value without
first shrinking the individual memory components.
ORA-00847: MEMORY_TARGET/MEMORY_MAX_TARGET and LOCK_SGA
cannot be set together
Cause: MEMORY_TARGET/MEMORY_MAX_TARGET was set to a non-zero value
and LOCK_SGA was also set
Action: Do not set MEMORY_TARGET or MEMORY_MAX_TARGET if LOCK_SGA
is set to TRUE.
ORA-00848: STATISTICS_LEVEL cannot be set to BASIC with SGA_TARGET or
MEMORY_TARGET
Cause: STATISTICS_LEVEL of BASIC was incompatible with SGA_TARGET and
MEMORY_TARGET.
Action: Fix the incompatible parameter setting. Set STATISTICS_LEVEL to TYPICAL
or ALL to use SGA_TARGET or MEMORY_TARGET.
ORA-00849: SGA_TARGET string cannot be set to more than
MEMORY_MAX_TARGET string.
Cause: SGA_TARGET value was more than MEMORY_MAX_TARGET value.
Action: Set SGA_TARGET to be less than MEMORY_MAX_TARGET.
ORA-00850: PGA_AGGREGATE_TARGET string cannot be set to more than
Cause: PGA_AGGREGATE_TARGET value was more than
MEMORY_MAX_TARGET value.
Action: Set PGA_AGGREGATE_TARGET to be less than MEMORY_MAX_TARGET.
ORA-00851: SGA_MAX_SIZE string cannot be set to more than
MEMORY_TARGET string.
Cause: SGA_MAX_SIZE value was more than MEMORY_TARGET value.
Action: Set SGA_MAX_SIZE to be less than MEMORY_TARGET.
ORA-00852: Rolling migration monitor process terminated.
Cause: The ASM rolling migration monitor process died.
ORA-00853: SGA_MAX_SIZE string cannot be set to more than
Cause: SGA_MAX_SIZE value was more than MEMORY_MAX_TARGET value.
Action: Set SGA_MAX_SIZE to be less than MEMORY_MAX_TARGET.
ORA-00000 to ORA-00877 58-49
ORA-00854: ASM IOServer Instance Fence monitor process terminated.

Cause: The ASM IOServer Fence monitor process died.
ORA-00875: failed to string the dedicated connection broker
Cause: The dedicated connection broker could not be enabled or disabled.
Action: Check the process trace file for the reason for failure.
ORA-00876: invalid CONNECTION_BROKERS specification #string
Cause: The syntax for the nth CONNECTION_BROKERS specification was invalid.
Action: See the additional errors that were reported. Refer to the Oracle Database
Reference manual for the correct syntax.
ORA-00877: TYPE=string appears in multiple CONNECTION_BROKERS
specifications
Cause: Multiple CONNECTION_BROKER specifications contained the same TYPE.
Action: Specify only one specification for each TYPE.
59
ORA-00900 to ORA-01499
ORA-00900: invalid SQL statement
ORA-00901: invalid CREATE command
ORA-00902: invalid datatype
ORA-00903: invalid table name
ORA-00904: string: invalid identifier
ORA-00905: missing keyword
ORA-00906: missing left parenthesis
ORA-00907: missing right parenthesis
ORA-00908: missing NULL keyword
ORA-00909: invalid number of arguments
ORA-00910: specified length too long for its datatype
Cause: for datatypes CHAR and RAW, the length specified was > 2000; otherwise, the
length specified was > 4000.
Action: use a shorter length or switch to a datatype permitting a longer length such as
a VARCHAR2, LONG CHAR, or LONG RAW
ORA-00911: invalid character
Cause: identifiers may not start with any ASCII character other than letters and
numbers. $#_ are also allowed after the first character. Identifiers enclosed by
doublequotes may contain any character other than a doublequote. Alternative quotes
(q'#...#') cannot use spaces, tabs, or carriage returns as delimiters. For all other
contexts, consult the SQL Language Reference Manual.
Action: n/a
ORA-00912: input parameter too long
Cause: one of your input strings was too long
Action: shorten the input parameter length
ORA-00913: too many values
ORA-00914: missing ADD keyword
ORA-00915: network access of dictionary table not currently allowed
ORA-00900 to ORA-01499 59-1
ORA-00917: missing comma

ORA-00918: column ambiguously defined
ORA-00919: invalid function
ORA-00920: invalid relational operator
ORA-00921: unexpected end of SQL command
ORA-00922: missing or invalid option
ORA-00923: FROM keyword not found where expected
ORA-00924: missing BY keyword
ORA-00925: missing INTO keyword
ORA-00926: missing VALUES keyword
ORA-00927: missing equal sign
ORA-00928: missing SELECT keyword
ORA-00929: missing period
ORA-00930: missing asterisk
ORA-00931: missing identifier
ORA-00932: inconsistent datatypes: expected string got string
ORA-00933: SQL command not properly ended
ORA-00934: group function is not allowed here
ORA-00935: group function is nested too deeply
ORA-00936: missing expression
ORA-00937: not a single-group group function
ORA-00938: not enough arguments for function
ORA-00939: too many arguments for function
ORA-00940: invalid ALTER command
ORA-00941: missing cluster name
ORA-00942: table or view does not exist
ORA-00943: cluster does not exist
ORA-00944: insufficient number of clustered columns
ORA-00945: specified clustered column does not exist
59-2 Error Messages
ORA-00946: missing TO keyword

ORA-00947: not enough values
ORA-00948: ALTER CLUSTER statement no longer supported
ORA-00949: illegal reference to remote database
ORA-00950: invalid DROP option
ORA-00951: cluster not empty
ORA-00952: missing GROUP keyword
ORA-00953: missing or invalid index name
Cause: An index name of the form [ identifier . ] identifier is expected but not present. If
OIDINDEX clause, index name must be identifier
Action: Enter an appropriate index name.
ORA-00954: missing IDENTIFIED keyword
ORA-00955: name is already used by an existing object
ORA-00956: missing or invalid auditing option
Cause: AUDIT or NOAUDIT statement contains an invalid auditing option.
Action: Use a valid option.
ORA-00957: duplicate column name
ORA-00958: missing CHECK keyword
ORA-00959: tablespace 'string' does not exist
ORA-00960: ambiguous column naming in select list
Cause: A column name in the order-by list matches more than one select list columns.
Action: Remove duplicate column naming in select list.
ORA-00961: bad datetime/interval value
ORA-00962: too many group-by / order-by expressions
Cause: The group-by or order-by column list contain more than 1000 expressions.
Action: Use 1000 or less expressions in the group-by or order-by list.
ORA-00963: unsupported interval type
ORA-00964: table name not in FROM list
Cause: The table name referred in the select list is not specified in the from list.
Action: Make sure the name is correctly specified and matches one of the names in the
from list.
ORA-00965: column aliases not allowed for '*'
Cause: The statement is trying to alias the * expression in the select list which is not
legal.
Action: Remove the alias.
ORA-00900 to ORA-01499 59-3
ORA-00966: missing TABLE keyword

ORA-00967: missing WHERE keyword
ORA-00968: missing INDEX keyword
ORA-00969: missing ON keyword
ORA-00970: missing WITH keyword
ORA-00971: missing SET keyword
ORA-00972: identifier is too long
Cause: An identifier with more than 30 characters was specified.
ORA-00973: invalid row count estimate
ORA-00974: invalid PCTFREE value (percentage)
ORA-00975: date + date not allowed
ORA-00976: Specified pseudocolumn or operator not allowed here.
Cause: LEVEL, PRIOR, ROWNUM, CONNECT_BY_ROOT, CONNECT_BY_ISLEAF
or CONNECT_BY_ISCYCLE was specified at an illegal location.
Action: Remove LEVEL, PRIOR, ROWNUM, CONNECT_BY_ROOT,
CONNECT_BY_ISLEAF or CONNECT_BY_ISCYCLE.
ORA-00977: duplicate auditing option
Cause: AUDIT or NOAUDIT statement specifies an option more than once
Action: Either use ALL with no other auditing options or make sure no option is
listed more than once.
ORA-00978: nested group function without GROUP BY
ORA-00979: not a GROUP BY expression
ORA-00980: synonym translation is no longer valid
Cause: A synonym did not translate to a legal target object. This could happen for one
of the following reasons: 1. The target schema does not exist. 2. The target object does
not exist. 3. The synonym specifies an incorrect database link. 4. The synonym is not
versioned but specifies a versioned target object.
Action: Change the synonym definition so that the synonym points at a legal target
object.
ORA-00981: cannot mix table and system auditing options
Cause: Table and system-wide auditing options were specified in the same AUDIT or
NOAUDIT statement.
Action: You must issue table and system options in separate statements.
ORA-00982: missing plus sign
ORA-00983: cannot audit or noaudit SYS user actions
Cause: An attempt was made to AUDIT or NOAUDIT SYS user actions.
59-4 Error Messages
Action: Execute the statement again with a valid user.

ORA-00984: column not allowed here
ORA-00985: invalid program name
ORA-00986: missing or invalid group name(s)
ORA-00987: missing or invalid username(s)
ORA-00988: missing or invalid password(s)
ORA-00989: too many passwords for usernames given
ORA-00990: missing or invalid privilege
ORA-00991: only MAC privileges may be granted to procedures
Cause: Object privileges or non-MAC system privileges were granted to the
procedure.
Action: Only grant MAC privileges using the PROCEDURE clause.
ORA-00992: invalid format for REVOKE command
ORA-00993: missing GRANT keyword
ORA-00994: missing OPTION keyword
ORA-00995: missing or invalid synonym identifier
ORA-00996: the concatenate operator is ||, not |
ORA-00997: illegal use of LONG datatype
ORA-00998: must name this expression with a column alias
ORA-00999: invalid view name
ORA-01000: maximum open cursors exceeded
ORA-01001: invalid cursor
ORA-01002: fetch out of sequence
Cause: This error means that a fetch has been attempted from a cursor which is no
longer valid. Note that a PL/SQL cursor loop implicitly does fetches, and thus may
also cause this error. There are a number of possible causes for this error, including: 1)
Fetching from a cursor after the last row has been retrieved and the ORA-1403 error
returned. 2) If the cursor has been opened with the FOR UPDATE clause, fetching
after a COMMIT has been issued will return the error. 3) Rebinding any placeholders
in the SQL statement, then issuing a fetch before reexecuting the statement.
Action: 1) Do not issue a fetch statement after the last row has been retrieved - there
are no more rows to fetch. 2) Do not issue a COMMIT inside a fetch loop for a cursor
that has been opened FOR UPDATE. 3) Reexecute the statement after rebinding, then
attempt to fetch again.
ORA-01003: no statement parsed
ORA-00900 to ORA-01499 59-5
ORA-01004: default username feature not supported; logon denied

ORA-01005: null password given; logon denied
ORA-01006: bind variable does not exist
ORA-01007: variable not in select list
ORA-01008: not all variables bound
ORA-01009: missing mandatory parameter
ORA-01010: invalid OCI operation
Cause: One of the following: 1) You attempted an invalid OCI operation. 2) You are
using an Oracle client application linked with version 7.1 (or higher) libraries, the
environment variable ORA_ENCRYPT_LOGIN is set to TRUE, and you attempted to
connect to a version 7.0 (or lower) Oracle Server. 3) You are connected to a version 7.1
(or higher) Oracle Server, the initialization parameter DBLINK_ENCRYPT_LOGIN is
set to TRUE, and you attempted to use a database link pointing to a version 7.0 (or
lower) Oracle Server. 4) You are connected to a version 9.0.2(or higher) Oracle Server
and you attempted to use a database link pointing to a version 9.0.1(or lower) Oracle
Server for distributed autonomous transaction.
Action: For the above causes: 1) Do not use the invalid OCI operation. 2) If you do not
wish to use encrypted connect passwords in your distributed database, set
ORA_ENCRYPT_LOGIN to FALSE. If you wish to use encrypted connect passwords,
you must upgrade all Oracle Servers to version 7.1 (or higher). 3) If you do not wish
to use encrypted database links in your distributed database, set
DBLINK_ENCRYPT_LOGIN to FALSE. If you wish to use encrypted database links,
you must upgrade all Oracle Servers to version 7.1 (or higher). 4) Do not attempt
distributed autonomous transaction on version 9.0.1(or lower) Oracle Server.
ORA-01011: Cannot use v7 compatibility mode when talking to v6 server
ORA-01012: not logged on
ORA-01013: user requested cancel of current operation
ORA-01014: ORACLE shutdown in progress
ORA-01015: logon called recursively
ORA-01016: This function can be called only after a fetch
Cause: Cursor in an invalid state.
Action: Make sure that the oci/upi function is called after fetch.
ORA-01017: invalid username/password; logon denied
ORA-01018: column does not have a LONG datatype
ORA-01019: unable to allocate memory in the user side
Cause: The user side memory allocator returned error.
Action: Increase the processes heap size or switch to the old set of calls.
ORA-01020: unknown context state
59-6 Error Messages
ORA-01021: invalid context size specified

ORA-01022: database operation not supported in this configuration
Cause: The attempted database operation does not conform to the user programming
interface (UPI) for the two communicating ORACLE servers.
Action: You may need to upgrade one or more of your ORACLE servers or re-link
your user side application with new libraries. Report the problem to Worldwide
Customer Support.
ORA-01023: Cursor context not found (Invalid cursor number)
Cause: The cursor number is not a valid open cursor.
Action: Make sure that the cursor is open.
ORA-01024: invalid datatype in OCI call
ORA-01025: UPI parameter out of range
Cause: An integer parameter to a upi function is out of range.
Action: This usually indicates an error in a tool built on top of the oracle dbms. Report
the error to your customer support representative.
ORA-01026: multiple buffers of size > 4000 in the bind list
Cause: More than one long buffer in the bind list.
Action: Change the buffer size to be less than 4000 for the bind variable bound to a
normal column.
ORA-01027: bind variables not allowed for data definition operations
Cause: An attempt was made to use a bind variable in a SQL data definition
operation.
Action: Such bind variables are not allowed.
ORA-01028: internal two task error
Cause: Received send long message but don't have the cursor context.
ORA-01029: internal two task error
Cause: Received a request to send the long again when there is no long
Action: Report as a bug
ORA-01030: SELECT ... INTO variable does not exist
Cause: The SELECT... INTO specified in the bind call does not correspond to a
variable in the SQL statement.
Action: If it is not possible to correct the statement, call customer support.
ORA-01031: insufficient privileges
Cause: An attempt was made to perform a database operation without the necessary
privileges.
Action: Ask your database administrator or designated security administrator to
grant you the necessary privileges
ORA-01032: no such userid
Cause: This is an internal error message related to Export/Import.
ORA-00900 to ORA-01499 59-7

ORA-01033: ORACLE initialization or shutdown in progress
Cause: An attempt was made to log on while Oracle is being started up or shutdown.
Action: Wait a few minutes. Then retry the operation.
ORA-01034: ORACLE not available
Cause: Oracle was not started up. Possible causes include the following: - The SGA
requires more space than was allocated for it. - The operating-system variable
pointing to the instance is improperly defined.
Action: Refer to accompanying messages for possible causes and correct the problem
mentioned in the other messages. If Oracle has been initialized, then on some
operating systems, verify that Oracle was linked correctly. See the platform specific
Oracle documentation.
ORA-01035: ORACLE only available to users with RESTRICTED SESSION
privilege
Cause: Logins are disallowed because an instance started in restricted mode. Only
users with RESTRICTED SESSION system privilege can log on.
Action: Request that Oracle be restarted without the restricted option or obtain the
RESTRICTED SESSION system privilege.
ORA-01036: illegal variable name/number
Cause: Unable to find bind context on user side
Action: Make sure that the variable being bound is in the sql statement.
ORA-01037: maximum cursor memory exceeded
Cause: Attempting to process a complex sql statement which consumed all available
memory of the cursor.
Action: Simplify the complex sql statement.
ORA-01038: cannot write database file version string with ORACLE version string
Cause: Attempting to write datafile headers in an old format. The new format can not
be used until after the database has been verified as being compatible with this
software version.
Action: Open the database to advance to the new file formats, then repeat the
operation. If the operation is required before the database can be opened, then use the
previous software release to do the operation.
ORA-01039: insufficient privileges on underlying objects of the view
Cause: Attempting to explain plan on other people's view without the necessary
privileges on the underlying objects of the view.
Action: Get necessary privileges or do not perform the offending operation.
ORA-01040: invalid character in password; logon denied
Cause: There are multibyte characters in the password or some characters in the
password are not in US7ASCII range.
Action: Resubmit password with valid characters.
ORA-01041: internal error. hostdef extension doesn't exist
Cause: Pointer to hstdef extension in hstdef is null.
Action: Report as a bug
59-8 Error Messages
ORA-01042: detaching a session with open cursors not allowed

Cause: An attempt was made to detach a seesio n which had open cursors.
Action: Close all the cursors before detaching the session.
ORA-01043: user side memory corruption [string], [string], [string], [string]
Cause: The application code corrupted some of the usr memory used by oracle
Action: Make sure that the application code is not overwriting memory.
ORA-01044: size string of buffer bound to variable exceeds maximum string
Cause: An attempt was made to bind a buffer whose total size would exceed the
maximum size allowed. Total array size for arrays is calculated as:
(element_size)*(number of elements)
Action: Reduce buffer size.
ORA-01045: user string lacks CREATE SESSION privilege; logon denied
Cause: A connect was attempted to a userid which does not have create session
privilege.
Action: Grant the user CREATE SESSION privilege.
ORA-01046: cannot acquire space to extend context area
ORA-01047: The above error occurred in schema=string, package=string,
procedure=string
ORA-01048: Couldn't find the specified procedure in the given context
Cause: The procedure user specified in deferred RPC doesn't exist.
Action: Check to make sure that the procedure exists and is visible to the replication
process.
ORA-01049: Bind by name is not spupportted in streamed RPC
Cause: A newer version of server is talking with this version requesting an operation
not supported in this version.
Action: n/a
ORA-01050: cannot acquire space to open context area
ORA-01051: deferred rpc buffer format invalid
Cause: The deferred rpc data in sys.def$_call is corrupted.
Action: Contact your customer support representive.
ORA-01052: required destination LOG_ARCHIVE_DUPLEX_DEST is not specified
Cause: A valid destination for parameter LOG_ARCHIVE_DUPLEX_DEST was not
specified when parameter LOG_ARCHIVE_MIN_SUCCEED_DEST was set to two.
Action: Either specify a value for parameter LOG_ARCHIVE_DUPLEX_DEST, or
reduce the value for parameter LOG_ARCHIVE_MIN_SUCCEED_DEST to one.
ORA-01053: user storage address cannot be read
ORA-01054: user storage address cannot be written
ORA-01055: Object datatypes not supported for bind or define in this mode
Cause: Bind or Define used for objects with an invalid mode
ORA-00900 to ORA-01499 59-9
Action: Change the mode.

ORA-01057: invalid or ambiguous block.field reference in user exit
ORA-01058: internal New Upi interface error
Cause: Attempt to delete non existant hstdef extension.
ORA-01059: parse expected before a bind or execute
Cause: The client application attempted to bind a variable or execute a cursor opened
in a PL/SQL block before the statement was parsed.
Action: Ensure the statement is parsed before a bind or execute.
ORA-01060: array binds or executes not allowed
Cause: The client application attempted to bind an array of cursors or attempted to
repeatedly execute against a PL/SQL block with a bind variable of type cursor.
Action: Bind a single cursor or execute the PL/SQL block once.
ORA-01061: cannot start up a V8 server using a V7 client application
Cause: You are using an Oracle client application linked with version 7 (or lower)
libraries and you attempted to start up a V8 (or higher) server.
Action: Use a client application linked with V8 (or higher) libraries.60
ORA-01062: unable to allocate memory for define buffer
Cause: Exceeded the maximum buffer size for current plaform
Action: Use piecewise fetch with a smaller buffer size
ORA-01070: Using an old version of Oracle for the server
Cause: Using pre 7.0.10.1 version of oracle for server
Action: Upgrade server to post 7.0.10.1 version
ORA-01071: cannot perform operation without starting up ORACLE
Cause: Obvious
Action: n/a
ORA-01072: cannot stop ORACLE; ORACLE not running
Cause: Obvious
Action: n/a
ORA-01073: fatal connection error: unrecognized call type
Cause: An illegal internal operation was attempted.
ORA-01074: cannot shut down ORACLE; inside a login session - log off first
Cause: Obvious
Action: n/a
ORA-01075: you are currently logged on
Cause: Attempt to login while logged in.
Action: n/a
ORA-01076: multiple logons per process not yet supported

Cause: Obvious
Action: n/a
ORA-01077: background process initialization failure
Cause: Failure during initialization of ORACLE background processes.
Action: Further diagnostic information should be in the error stack or in the trace file.
ORA-01078: failure in processing system parameters
Cause: Failure during processing of INIT.ORA parameters during system startup.
Action: Further diagnostic information should be in the error stack.
ORA-01079: ORACLE database was not properly created, operation aborted
Cause: There was an error when the database or control file was created.
Action: Check what error was signaled when the database was first created or when
the control file was recreated. Take appropriate actions to recreate the database or a
new control file.
ORA-01080: error in shutting down ORACLE
Cause: Failure during system shutdown.
ORA-01081: cannot start already-running ORACLE - shut it down first
Cause: Obvious
Action: n/a
ORA-01082: 'row_locking = always' requires the transaction processing option
Cause: "row_locking = always" is specified in INIT.ORA file. This feature is not
supported by ORACLE without the transaction processing option.
Action: Remove it from INIT.ORA file or set it to "default" or "intent".
ORA-01083: value of parameter "string" is inconsistent with that of other instances
Cause: The value of the given parameter is required to be the same for all instances in
the cluster database configuration. ROW_LOCKING and SERIALIZABLE are 2
examples.
Action: Change the value of the parameter in INIT.ORA file to match that of other
cluster database instances.
ORA-01084: invalid argument in OCI call
Cause: The failing OCI call contains an argument with an invalid value.
Action: Use valid argument values. For more information, see the Programmer's
Guide to the Oracle Call Interfaces and the appropriate programming language
supplement.
ORA-01085: preceding errors in deferred rpc to "string.string.string"
Cause: Errors were encountered when the named procedure was executed as a
deferred remoted procedure call.
Action: Correct the cause of the preceding errors.
ORA-00900 to ORA-01499 59-11
ORA-01086: savepoint 'string' never established in this session or is invalid

Cause: An attempt was made to roll back to a savepoint that was never established in
this session, or was invalid.
Action: Try rolling back to the savepoint from the session where it is established.
ORA-01087: cannot start up ORACLE - currently logged on
ORA-01088: shutdown in progress - operation not permitted until restart
Cause: The SHUTDOWN command was used to shut down a running Oracle instance
but the shutdown operation was not complete.
Action: Wait for the instance to be restarted or contact your database administrator.
ORA-01089: immediate shutdown or close in progress - no operations are permitted
Cause: The SHUTDOWN IMMEDIATE command was used to shut down a running
Oracle instance, or CLOSE IMMEDIATE was used to shut down a pluggable
database, so your operations have been terminated.
Action: Wait for the instance to be restarted, or contact your DBA.
ORA-01090: shutdown in progress - connection is not permitted
Cause: The SHUTDOWN command was used to shut down a running ORACLE
instance, so you cannot connect to ORACLE.
Action: Wait for the instance to be restarted, or contact your DBA.
ORA-01091: failure during startup force
Cause: Unable to destroy the old SGA.
Action: Manually remove the old SGA and reissue the STARTUP command
ORA-01092: ORACLE instance terminated. Disconnection forced
Cause: The instance this process was connected to was terminated abnormally,
probably via a shutdown abort. This process was forced to disconnect from the
instance.
Action: Examine the alert log for more details. When the instance has been restarted,
retry action.
ORA-01093: ALTER DATABASE CLOSE only permitted with no sessions
connected
Cause: There is at least one more session other than the current one logged into the
instance. ALTER DATABASE CLOSE is not permitted.
Action: Find the other sessions and log them out and resubmit the command
ORA-01094: ALTER DATABASE or ALTER PLUGGABLE DATABASE CLOSE in
progress. Connections not permitted
ORA-01095: DML statement processed zero rows
Cause: During a call to OTEX, an update, delete, or insert statement being executed
processed zero rows. The execution of statements by OTEX was halted at this point.
Action: n/a
ORA-01096: program version (string) incompatible with instance (string)
Cause: A program is trying to connect to an instance using a different version of code
than the database was started with. This is not allowed.
Action: Either relink the program with the same version as the database or restart the
database using the old version of code.
ORA-01097: cannot shutdown while in a transaction - commit or rollback first
Cause: Obvious
Action: n/a
ORA-01098: program Interface error during Long Insert
ORA-01099: cannot mount database in SHARED mode if started in single process
mode
Cause: Obvious
Action: n/a
ORA-01100: database already mounted
Cause: A database is already mounted in this instance.
Action: n/a
ORA-01101: database being created currently mounted by some other instance
Cause: Some other instance has the database of same name currently mounted and
you are trying to create it.
Action: Either change the database name or shutdown the other instance.
ORA-01102: cannot mount database in EXCLUSIVE mode
Cause: Some other instance has the database mounted exclusive or shared.
Action: Shutdown other instance or mount in a compatible mode.
ORA-01103: database name 'string' in control file is not 'string'
Cause: The database name in the control file does not match your database name.
Action: Either find the correct control file or change your database name.
ORA-01104: number of control files (string) does not equal string
Cause: The number of control files used by this instance disagrees with the number of
control files in an existing instance.
Action: Check to make sure that all control files are listed.
ORA-01105: mount is incompatible with mounts by other instances
Cause: An attempt to mount the database discovered that another instance mounted a
database by the same name, but the mount is not compatible. Additional errors are
reported explaining why.
Action: See accompanying errors.
ORA-01106: database must be closed before dismounting
Cause: Obvious
Action: n/a
ORA-01107: database must be mounted for media recovery
Cause: An attempt to perform media recovery was made but the database is not
mounted.
Action: Mount the database.
ORA-00900 to ORA-01499 59-13
ORA-01108: file string is in backup or media recovery

Cause: Either media recovery is actively being applied to the file, or it is being backed
up while the database is in NOARCHIVELOG mode. It cannot be used for normal
database access or crash recovery.
Action: Complete or cancel the media recovery session or backup.
ORA-01109: database not open
Cause: A command was attempted that requires the database to be open.
Action: Open the database and try the command again
ORA-01110: data file string: 'string'
Cause: Reporting file name for details of another error. The reported name can be of
the old file if a data file move operation is in progress.
ORA-01111: name for data file string is unknown - rename to correct file
Cause: The data file was missing from a CREATE CONTROLFILE command or
backup control file recovery was done with a control file that was saved before the file
was created.
Action: Rename the MISSING file to the name of the real file.
ORA-01112: media recovery not started
Cause: An attempt to continue media recovery is being made but media recovery was
not started.
Action: None
ORA-01113: file string needs media recovery
Cause: An attempt was made to online or open a database with a file that is in need of
media recovery.
Action: First apply media recovery to the file.
ORA-01114: IO error writing block to file string (block # string)
Cause: The device on which the file resides is probably offline. If the file is a
temporary file, then it is also possible that the device has run out of space. This could
happen because disk space of temporary files is not necessarily allocated at file
creation time.
Action: Restore access to the device or remove unnecessary files to free up space.
ORA-01115: IO error reading block from file string (block # string)
Cause: Device on which the file resides is probably offline
Action: Restore access to the device
ORA-01116: error in opening database file string
Cause: Usually the file is not accessible.
Action: Restore the database file.
ORA-01117: adding file 'string' with illegal block size: string; limit is string
Cause: An attempt was made to add a database file with a block size that is greater
than the maximum block size allowed.
Action: Retry the DDL command with a smaller block size.
ORA-01118: cannot add any more database files: limit of string exceeded
Cause: There is no more room in the control file for adding database files.
Action: Resize the control file or drop other tablespaces.
ORA-01119: error in creating database file 'string'
Cause: Usually due to not having enough space on the device.
Action: n/a
ORA-01120: cannot remove online database file string
Cause: Attempting to drop a datafile when it is online
Action: Take file offline before dropping.
ORA-01121: cannot rename database file string - file is in use or recovery
Cause: Attempted to use ALTER DATABASE RENAME to rename a datafile that is
online in an open instance or is being recovered.
Action: Close database in all instances and end all recovery sessions.
ORA-01122: database file string failed verification check
Cause: The information in this file is inconsistent with information from the control
file. See accompanying message for reason.
Action: Make certain that the db 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 backup of an on-line tablespace failed because media
recovery is not enabled.
Action: Enable media recovery and retry this operation.
ORA-01124: cannot recover data file string - file is in use or recovery
Cause: An attempt to do media recovery found that the file was not available for
recovery. Either it is online and the database is open in some instance, or another
process is curently doing media recovery on the file.
Action: Do not do media recovery.
ORA-01125: cannot disable media recovery - file string has 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 tablespace and retry this command.
ORA-01126: database must be mounted in this instance and not open in any
instance
Cause: Obvious
Action: n/a
ORA-01127: database name 'string' exceeds size limit of string characters
Cause: Obvious
Action: n/a
ORA-01128: cannot start online backup - file string is offline
Cause: An attempt to start an online backup found that one of the files is offline.
Action: Bring the offending files online and retry this command or do a cold backup.
ORA-00900 to ORA-01499 59-15
ORA-01129: user's default or temporary tablespace does not exist

Cause: The user's default or temporary tablespace was dropped.
Action: Reassign the default or temporary tablespace.
ORA-01130: database file version string incompatible with ORACLE version string
ORA-01131: DB_FILES system parameter value string exceeds limit of string
ORA-01132: length of database file name 'string' exceeds limit of string characters
ORA-01133: length of log file name 'string' exceeds limit of string characters
ORA-01134: database mounted exclusive by another instance
ORA-01135: file string accessed for DML/query is offline
Cause: Attempted to access a data file that is offline
Action: Bring the data file back online
ORA-01136: specified size of file string (string blocks) is less than original size of
string blocks
Cause: A file size was specified in the AS clause of ALTER DATABASE CREATE
DATAFILE, and the size was smaller the the size needed
Action: Create the file with a larger size.
ORA-01137: data file string is still in the middle of going offline
Cause: It was not possible to get the lock for a file that is offline when attempting to
bring it online. The most likely cause is that the lock is still held by the instance that is
took it offline.
Action: Wait a bit and try to online the file again.
ORA-01138: database must either be open in this instance or not at all
Cause: The requested operation can not be done when the database is mounted but
not open in this instance, and another instance has the database open.
Action: Execute the operation in an open instance, open the datbase in this instance,
or close the database in the other instances.
ORA-01139: RESETLOGS option only valid after an incomplete database recovery
Cause: The RESETLOGS option was given in ALTER DATABASE OPEN, but there
has been no incomplete recovery session.
Action: Retry the ALTER DATABASE OPEN without specifying RESETLOGS
ORA-01140: cannot end online backup - all files are offline or readonly
Cause: All the files were found to be offline or readonly when attempting to end an
online backup.
Action: None. Online backup does not need to be ended for this tablespace.
ORA-01141: error renaming data file string - new file 'string' not found
Cause: An attempt to change a data file's name in the control file failed because no file
was found with the new name.
Action: Make sure that the data file has been properly renamed by the operating
system and retry.
ORA-01142: cannot end online backup - none of the files are in backup
Cause: None of the files were found to be in online backup when attempting to end
an online backup.
Action: None. Online backup does not need to be ended for this tablespace.
ORA-01143: cannot disable media recovery - file string needs media recovery
Cause: An attempt to disable media recovery found a file that needs media recovery,
thus media recovery cannot be disabled.
Action: Recover the offending file or drop the tablespace it belongs to and retry this
command.
ORA-01144: File size (string blocks) exceeds maximum of string blocks
Cause: Specified file size is larger than maximum allowable size value.
Action: Specify a smaller size.
ORA-01145: offline immediate disallowed unless media recovery enabled
Cause: ALTER TABLESPACE ... OFFLINE IMMEDIATE or ALTER DATABASE
DATAFILE ... OFFLINE is only allowed if database is in ARCHIVELOG mode.
Action: Take tablespace offline normally or shutdown abort. Reconsider your backup
strategy. You could do this if you were archiving your logs.
ORA-01146: cannot start online backup - file string is already in backup
Cause: When starting an online backup it was noticed that an online backup was
already started for one of the data files.
Action: End the first backup before beginning another.
ORA-01147: SYSTEM tablespace file string is offline
Cause: A file belonging to the SYSTEM tablespace has been marked offline by the
DBA. The database cannot be started until all SYSTEM tablespace files are online and
openable.
Action: Bring the file online.
ORA-01148: cannot refresh file size for datafile string
Cause: An operating system or device error occurred when retrieving the file's size.
The device on which the file resides may have been offline.
Action: Restore access to the device.
ORA-01149: cannot shutdown - file string has online backup set
Cause: An attempt to shutdown normally found that an online backup is still in
progress.
ORA-01150: cannot prevent writes - file string has online backup set
Cause: An attempt to make a tablespace read only or offline normal found that an
online backup is still in progress. It will be necessary to write the file header to end
the backup, but that would not be allowed if this command succeeded.
ORA-01151: use media recovery to recover block, restore backup if needed
Cause: Error 1172 occurred.
Action: This is additional information for error 1172.
ORA-00900 to ORA-01499 59-17
ORA-01152: file string was not restored from a sufficiently old backup
Cause: An incomplete recovery session was started, but an insufficient number of logs
were applied to make the database consistent. This file is still in the future of the last
log applied. The most likely cause of this error is forgetting to restore the file from a
backup before doing incomplete recovery.
Action: Either apply more logs until the database is consistent or restore the database
file from an older backup and repeat recovery.
ORA-01153: an incompatible media recovery is active
Cause: Attempted to start an incompatible media recovery or open resetlogs during
media recovery or RMAN backup . Media recovery sessions are incompatible if they
attempt to recover the same data file. Incomplete media recovery or open resetlogs is
incompatible with any media recovery. Backup or restore by RMAN is incompatible
with open resetlogs
Action: Complete or cancel the other media recovery session or RMAN backup
ORA-01154: database busy. Open, close, mount, and dismount not allowed now
Cause: Some operation is in progress that expects the opened/mounted state of this
instance to remain the same.
Action: Wait for the operation to complete then retry. If attempting to do a shutdown,
SHUTDOWN ABORT will work. If this is a shutdown of a standby database that is
operating in NO DATA LOSS mode, you must shutdown the primary database first.
ORA-01155: the database is being opened, closed, mounted or dismounted
Cause: The requested operation needs the instance to be in a particular state but the
state is being changed.
Action: Wait for the open, close, mount, or dismount to complete then retry the
operation. If necessary, a SHUTDOWN ABORT will always work.
ORA-01156: recovery or flashback in progress may need access to files
Cause: Either media recovery, instance recovery, or flashback was in progress. The
recovery or flashback in progress may need the files to which this operation is being
applied.
Action: Wait for recovery or flashback to complete.
ORA-01157: cannot identify/lock data file string - see DBWR trace file
Cause: The background process was either unable to find one of the data files or
failed to lock it because the file was already in use. The database will prohibit access
to this file but other files will be unaffected. However the first instance to open the
database will need to access all online data files. Accompanying error from the
operating system describes why the file could not be identified.
Action: Have operating system make file available to database. Then either open the
database or do ALTER SYSTEM CHECK DATAFILES.
ORA-01158: database string already mounted
Cause: Another instance has a database by this name mounted.
Action: Find which instance is still running. Perhaps you have not lost the control files
after all.
ORA-01159: file is not from same database as previous files - wrong database id
Cause: Not all of the files specified in CREATE CONTROLFILE are from the same
database. The database ID of this file does not match that from the first file specified.
Action: Please double check the list of files provided to the CREATE
ORA-01160: file is not a string
Cause: The named file in the DATAFILE or LOGFILE section of the CREATE
CONTROLFILE command does not appear to be as stated.
Action: Please double check the mentioned file.
ORA-01161: Database name string in the file header does not match string in the
DATABASE clause.
Cause: The database name provided in the DATABASE clause did not match the
database name found in the file header.
Action: Ensure consistency of database names. Use the SET DATABASE clause if you
are renaming the database.
ORA-01162: block size string in file header does not match configured block sizes
Cause: CREATE CONTROLFILE discovered that the block size for this file is
incompatible with any of the configured cache blocksizes in the INIT.ORA file.
Action: Configure the appropriate cache for this block size using one of the various
(db_2k_cache_size, db_4k_cache_size, db_8k_cache_size, db_16k_cache_size,
db_32K_cache_size) parameters.
ORA-01163: SIZE clause indicates string (blocks), but should match header string
Cause: The size specified in bytes in the SIZE clause of the CREATE CONTROLFILE
statement does not equate to the number of blocks recorded in the header.
Action: Specify the correct filename and size ( in bytes ).
ORA-01164: MAXLOGFILES may not exceed string
Cause: MAXLOGFILES specified on the command line too large.
Action: Resubmit the command with a smaller MAXLOGFILES
ORA-01165: MAXDATAFILES may not exceed string
Cause: MAXDATAFILES specified on the command line too large.
Action: Resubmit the command with a smaller MAXDATAFILES
ORA-01166: file number string is larger than string (string)
Cause: File mentioned in CREATE CONTROLFILE has a file number which is larger
than that specified for MAXDATAFILES or MAXLOGFILES.
Action: Increase the maximum specified on the command line.
ORA-01167: two files are 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 the exact same file then one is likely
to be a backup of the other. If they are two members of the same log they must be
specified together in a group file spec. 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 file mentioned is not a repeat of a file already mentioned in
the command. If they are different files then omit the earlier backup. If they are
members of the same log, insure they are in the same group file specification. If this
message appears because of a duplicate control file, check the control_files parameter
in the init.ora file and see if a file is specified more than once. If all files names appear
to be unique, check to make sure that the actual control files themselves are unique.
ORA-00900 to ORA-01499 59-19
For example, in UNIX check for a symbolic or a hard link to another control file in the
list.
ORA-01168: physical block size string does not match size string of other members
Cause: The file is located on a device with a different physical block size than the
other members in the group
Action: Use a physical device with matching block size.
ORA-01169: DATAFILE number 1 not found. Must be present
Cause: Datafile number 1 was not specified in a CREATE CONTROLFILE command.
Action: Locate datafile number 1 and resubmit the CREATE CONTROLFILE
command.
ORA-01170: file not found 'string'
Cause: ALL datafiles and, if NORESETLOGS, ALL logfiles MUST be accessible by the
process for CREATE CONTROLFILE.
Action: The file specified probably contains a typing error. Double check command
and the existance of all files and then resubmit.
ORA-01171: datafile string going offline due to error advancing checkpoint
Cause: The checkpoint in the file header could not be advanced. See accompanying
errors for the reason. The datafile will be taken offline the same as for a write error of
a data block.
Action: See accompanying errors for details. Restore access to the file, do media
recovery, and bring it back online.
ORA-01172: recovery of thread string stuck at block string of file string
Cause: Crash recovery 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
then repaired during recovery.
Action: Do a RECOVER DATAFILE for the file containing the block. If this does not
resolve the problem then restore the file from a backup and recover it.
ORA-01173: data dictionary indicates missing data file from system tablespace
Cause: Either the database has been recovered to a point in time in the future of the
control file or a datafile from the system tablespace was omitted from the create
control file command previously issued.
Action: For the former problem you need to recover the database from a more recent
control file. For the latter problem, simply recreate the control file checking to be sure
that you include all the datafiles in the system tablespace.
ORA-01174: DB_FILES is string buts needs to be string to be compatible
Cause: The maximum number of database files supported by this instance is not the
same as for the other instances. All instances must be able to open all the files any
instance can open.
Action: Change the value of the DB_FILES parameter to be compatible
ORA-01175: data dictionary has more than the string files allowed by the instance
Cause: The data dictionary is found to have more files than that which can be
supported by this instance.
Action: Shutdown the instance and restart with a larger number of db_files
ORA-01176: data dictionary has more than the string files allowed by the controlfile
Cause: After a CREATE CONTROLFILE, the data dictionary was found to have more
data files than that supported by the control file.
Action: Re-create the control file with a larger MAXDATAFILES.
ORA-01177: data file does not match dictionary - probably old incarnation
Cause: When comparing the control file with the data dictionary after a CREATE
CONTROLFILE or OPEN RESETLOGS, it was noted that this datafile was
inconsistent with the dictionary. Most likely the file is a backup of a file that was
dropped from the database, and the same file number was reused for a new file. It
may also be that an incomplete recovery stopped at a time when this file number was
used for another datafile.
Action: Do a CREATE CONTROLFILE with the correct file or none at all.
ORA-01178: file string created before last CREATE CONTROLFILE, cannot recreate
Cause: Attempted to use ALTER DATABASE CREATE DATAFILE to recreate a
datafile that existed at the last CREATE CONTROLFILE 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 of the file, and recover it. Do incomplete recovery to time
before file was originally created.
ORA-01179: file string does not exist
Cause: During datafile recovery, a file was listed which was not part for the database.
Action: Recheck the datafile name. Remember to use double quotes at the SQLDBA
command line and remember that the file name is translated in the environment of
the SQLDBA.
ORA-01180: can not create datafile 1
Cause: Attempting to create datafile 1 using ALTER DATABASE CREATE
DATAFILE.
Action: Recover file from a backup or recreate database.
ORA-01181: file string created before last known RESETLOGS, cannot recreate
datafile that existed before the last known RESETLOGS.
Action: Find a backup of the file, and recover it. Do incomplete recovery to time
before file was originally created.
ORA-01182: cannot create database file string - file is in use or recovery
datafile that is online in an open instance or is being recovered.
Action: Close database in all instances and end all recovery sessions
ORA-01183: cannot mount database in SHARED mode
Cause: Some other instance has the database mounted exclusive.
Action: Shutdown other instance then mount shared.
ORA-01184: logfile group string already exists
Cause: An ALTER DATABASE ADD LOGFILE command specified a log number for
the new log which is already in use.
ORA-00900 to ORA-01499 59-21
Action: Specify a different logfile number, or let the database choose an unused value.
ORA-01185: logfile group number string is invalid
Cause: An ALTER DATABASE ADD LOGFILE command specified a log number for
the new log which is too large.
Action: Specify a correct logfile number.
ORA-01186: file string failed verification tests
Cause: The data file did not pass the checks to insure it is part of the database. See the
accompanying error messages for the reason the verification failed.
Action: Make the correct file available to the database. Then, either open the database,
or execute ALTER SYSTEM CHECK DATAFILES.
ORA-01187: cannot read from file string because it failed verification tests
Cause: The data file did not pass the checks to insure it is part of the database. Reads
are not allowed until it is verified.
ORA-01188: The block size specified string does not match header block size string
Cause: The block size specified in the BLOCKSIZE clause of the CREATE
CONTROLFILE statement does not equate to the block size recorded in the log file
header.
Action: Specify the correct block size.
ORA-01189: file is from a different RESETLOGS than previous files
Cause: In a CREATE CONTROLFILE command either this file or all previous files
were backups from before the last RESETLOGS. This may also occur if this is a file
that is offline and has been offline since before the last RESETLOGS.
Action: If the file was taken offline normal before the last RESETLOGS, and is still
offline, omit it from the CREATE CONTROLFILE command. Rename and online the
file after the database is open. Otherwise find the version of the mentioned file
consistent with the rest of the datafiles and resubmit the command.
ORA-01190: control file or data file string is from before the last RESETLOGS
Cause: Attempting to use a data file when the log reset information in the file does
not match the control file. Either the data file or the control file is a backup that was
made before the most recent ALTER DATABASE OPEN RESETLOGS.
Action: Restore file from a more recent backup.
ORA-01191: file string is already offline - cannot do a normal offline
Cause: When attempting to do a normal tablespace offline it was discovered that one
of the files in the tablespace was already offline.
Action: Either bring the datafile online first, or use another tablespace offline option.
ORA-01192: must have at least one enabled thread
Cause: You must specify at least two logfiles from at least one thread at the create
contolfile command line.
Action: Find the missing logfiles and resubmit the command with the newly found
logfiles included in the command line.
ORA-01193: file string is not the same file seen at start of recovery
Cause: A different copy of the file was accessed the last time media recovery looked at
the file header. A backup of the file was restored or the meaning of the file name
changed during recovery.
Action: Ensure the correct file is available, then retry recovery.
ORA-01194: file string needs more recovery to be consistent
were applied to make the file consistent. The reported file was not closed cleanly
when it was last opened by the database. It must be recovered to a time when it was
not being updated. The most likely cause of this error is forgetting to restore the file
from a backup before doing incomplete recovery.
Action: Either apply more logs until the file is consistent or restore the file from an
older backup and repeat recovery.
ORA-01195: online backup of file string needs more recovery to be consistent
were applied to make the file consistent. The reported file is an online backup which
must be recovered to the time the backup ended.
Action: Either apply more logs until the file is consistent or restore the database files
from an older backup and repeat recovery.
ORA-01196: file string is inconsistent due to a failed media recovery session
Cause: The file was being recovered but the recovery did not terminate normally. This
left the file in an inconsistent state. No more recovery was successfully completed on
this file.
Action: Either apply more logs until the file is consistent or restore the backup again
and repeat recovery.
ORA-01197: thread string only contains one log
Cause: During CREATE CONTROLFILE all threads represented in the logs must be
represented by at least two logs. A "last log" and a second log. The named thread does
not contain two such logs.
Action: Either find more logs from the named thread. Or use the RESETLOGS option
to CREATE CONTROLFILE.
ORA-01198: must specify size for log file if RESETLOGS
Cause: File sizes must be given for all logfiles if doing a CREATE CONTROLFILE
with the RESETLOGS option.
Action: Resubmit the command with the appropriate logfile size.
ORA-01199: file string is not in online backup mode
Cause: Attempting to end an online backup for a file that is not in online backup.
Action: Do not enter command since it is not needed.
ORA-01200: actual file size of string is smaller than correct size of string blocks
Cause: The size of the file as returned by the operating system is smaller than the size
of the file as indicated in the file header and the control file. Somehow the file has
been truncated. Maybe it is the result of a half completed copy.
Action: Restore a good copy of the data file and do recovery as needed.
ORA-00900 to ORA-01499 59-23
ORA-01201: file string header failed to write correctly

Cause: An I/O error was reported for the file header. The error was trapped and a
second attempt will be made.
Action: The file probably will require recovery. Further error messages will indicate
what is needed.
ORA-01202: wrong incarnation of this file - wrong creation time
Cause: The creation time in the file header is not the same as the creation time in the
control file. This is probably a copy of a file that was dropped.
Action: Restore a current copy of the data file and do recovery as needed.
ORA-01203: wrong incarnation of this file - wrong creation SCN
Cause: The creation SCN in the file header is not the same as the creation SCN in the
control file. This is probably a copy of a file that was dropped.
Action: Restore a current copy of the data file and do recovery as needed.
ORA-01204: file number is string rather than string - wrong file
Cause: The file number in the file header is not correct. This is probably a restored
backup of the wrong file, but from the same database.
Action: Restore a copy of the correct data file and do recovery as needed.
ORA-01205: not a data file - type number in header is string
Cause: The file type in the header is not correct for a data file. This is probably a log
file or control file. If the type is not a small non-zero positive number then the header
is corrupted.
ORA-01206: file is not part of this database - wrong 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
at all. If the database was rebuilt, this may be a file from before the rebuild. Note that
if you see this error when the file is supposed to be plugged in from another database
via the Transportable Tablespace feature, it means the database ID in the file header
does not match the one expected.
ORA-01207: file is more recent 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 make it stop happening without correcting the
real problem. Every attempt to open the database will advance the control file change
sequence number until it is great enough.
Action: Use the current control file or do backup control file recovery to make the
control file current. Be sure to follow all restrictions on doing a backup control file
recovery.
ORA-01208: data file is an old version - not accessing current version
Cause: The checkpoint in the file header is less recent than in the control file. If
opening a database that is already open by another instance, or if another instance
just brought this file online, the file accessed by this instance is probably a different
version. Otherwise, a backup of the file probably was restored while the file was in
use.
ORA-01209: data file is from before 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 opening a database
that is open already by another instance, or if another instance just brought this file
online, the file accessed by this instance is probably a different version. Otherwise, a
backup of the file probably was restored while the file was in use.
ORA-01210: data file header is media corrupt
Cause: The file header block is internally inconsistent. The beginning of the block has
a header with a checksum and other data for insuring the consistancy of the block. It
is possible that the last disk write did not operate correctly. The most likely problem
is that this is not a datafile for any database.
Action: Have operating system make correct file available to database. If the trace file
dump indicates that only the checksum is wrong, restore from a backup and do
media recovery.
ORA-01211: Oracle7 data file is not from migration to Oracle8
Cause: The file is not a copy of the file LAST used under Oracle7. This datafile is
either a backup taken from before the migration, or the database was opened by
Oracle7 after the migration utility was run. When converting a database from Oracle7
to Oracle8, the migration program MUST be the LAST utility to access the database
under Oracle7. Only the datafiles that were current when the migration was done
may be accessed by Oracle8.
Action: Have operating system make correct data file available to database, or repeat
the Oracle7 to Oracle8 migration. Make sure that database is NOT opened after
migration utility is run.
ORA-01212: MAXLOGMEMBERS may not exceed string
Cause: MAXLOGMEMBERS specified on the command line too large.
Action: Resubmit the command with a smaller MAXLOGMEMBERS
ORA-01213: MAXINSTANCES may not exceed string
Cause: MAXINSTANCES specified on the command line too large.
Action: Resubmit the command with a smaller MAXINSTANCES
ORA-01214: MAXLOGHISTORY may not exceed string
Cause: MAXLOGHISTORY specified on the command line too large.
Action: Resubmit the command with a smaller MAXLOGHISTORY
ORA-01215: enabled thread string is missing after CREATE CONTROLFILE
Cause: A CREATE CONTROLFILE statement was given which did not list all the
enabled threads for the database.
Action: Reissue the CREATE CONTROLFILE statement, including all enabled
threads.
ORA-00900 to ORA-01499 59-25
ORA-01216: thread string is expected to be disabled after CREATE CONTROLFILE

Cause: A thread that was given during CREATE CONTROLFILE is enabled, but the
datafiles indicate that it should be disabled. This is probably because the logs
supplied to the CREATE CONTROLFILE are old (from before the disabling of the
thread).
Action: This thread is not required to run the database. The CREATE CONTROLFILE
statement can be reissued without the problem thread, and, if desired, the thread can
be recreated after the database is open.
ORA-01217: logfile member belongs to a different logfile group
Cause: A member of a multiple-member logfile group specified in a CREATE
CONTROLFILE is not part of the same group as previous members.
Action: Group together the correct members for the CREATE CONTROLFILE
command.
ORA-01218: logfile member is not from the same point-in-time
Cause: A member of a multiple-member logfile group is from a different point in
time. One of the members specified may be an older (backup) copy of the log.
Action: Find the correct version of the log, or leave it out of the CREATE
CONTROLFILE command.
ORA-01219: database or pluggable database not open: queries allowed on fixed
tables or views only
Cause: A query was issued against an object not recognized as a fixed table or fixed
view before the database or pluggable database has been opened.
Action: Re-phrase the query to include only fixed objects, or open the database or
pluggable database.
ORA-01220: file based sort illegal before database is open
Cause: A query issued against a fixed table or view required a temporary segment for
sorting before the database was open. Only in-memory sorts are supported before the
database is open.
Action: Re-phrase the query to avoid a large sort, increase the values of the
SORT_AREA_SIZE and/or SORT_AREA_RETAINED_SIZE initialization parameters
to enable the sort to be done in memory.
ORA-01221: data file string is not the same file to a background process
Cause: When the database writer opens the data file, it is accessing a different
physical file than the foreground doing the recovery. The timestamp set in the file
header by the foreground was not found by the background. It may be that the
background process could not read the file at all.
Action: Look in the DBWR trace file for the error it recieved when attempting to read
the file header. Reconfigure the operating system as needed to have the file name
successfully access the same file when opened by a background process.
ORA-01222: MAXINSTANCES of string requires MAXLOGFILES be at least string,
not string
Cause: Attemping to create a database or control file that does not have room for at
least two logs per thread of redo. A thread of redo must have two online logs in order
to be enabled. It does not make sense to allow more redo threads than can be
supported by the logs.
Action: Either reduce the MAXINSTANCES argument or increase MAXLOGFILES.
ORA-01223: RESETLOGS must be specified to set a new database name

Cause: The SET database name option was specified to CREATE CONTROLFILE, but
RESETLOGS was not specified. The database name can only be changed when
opening the database with RESETLOGS.
Action: Either add the RESETLOGS option or drop the SET option to CREATE
CONTROLFILE.
ORA-01224: group number in header string does not match GROUP string
Cause: Group number specified at CREATE CONTROLFILE does not match the
group number stored in the header. Most likely the specification is wrong.
Action: Omit the GROUP option or give the correct one.
ORA-01225: thread number string is greater than MAXINSTANCES string
Cause: The log is for a thread greater than the MAXINSTANCES argument.
Action: Increase the value for MAXINSTANCES and resubmit the command.
ORA-01226: file header of log member is inconsistent with other members
Cause: The log file member in the accompanying error is for the same group as the
previous members, but other fields in the header are different. Either a file header is
corrupted, or some file is a member of a deleted log.
Action: Find the correct log member or omit this member from the command.
ORA-01227: log string is inconsistent with other logs
Cause: The log file in the accompanying error is inconsistent with the contents of
other logs given in the CREATE CONTROLFILE command. Either a file header is
corrupted, or some file is an old copy rather than the current version. The problem
may not be with the log listed since all that can be detected is that there is an
inconsistancy. All log files listed in the command must be the current versions of the
online logs.
Action: Find the correct online logs or use the RESETLOGS option.
ORA-01228: SET DATABASE option required to install seed database
Cause: The SET DATABASE option was not included in the CREATE CONTROLFILE
command when installing a seed database. The database does not have a database ID
because it is intended to be installed at multiple sites, and each site needs to be a
different database with its own database id. Both the SET DATABASE and
RESETLOGS options must be specified to create the control file for this database.
Action: Resubmit command with the SET DATABASE and RESETLOGS options.
ORA-01229: data file string is inconsistent with logs
Cause: The data file in the accompanying error is inconsistent with the contents of the
logs given in the CREATE CONTROLFILE command. The most likely cause is that
one or more of the online logs was missing from the command. It is also possible that
one or more of the logs is an old copy rather than 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 make read only - file string 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 retry this command.
ORA-00900 to ORA-01499 59-27
ORA-01231: cannot make read write - file string is offline

Cause: An attempt to make a tablespace read write found that one of its files is offline.
Action: Bring the file online and retry this command.
ORA-01232: cannot start online backup - file string is being made read-only
Cause: An attempt to start an online backup found that one of the files is in transition
to read-only mode.
Action: Wait for the transition to complete and then retry the command, if this is an
ALTER DATABASE BEGIN BACKUP command, or take the backup without any
begin or end commands, if this is an ALTER TABLESPACE BEGIN BACKUP
command.
ORA-01233: file string is read only - cannot recover using backup control file
Cause: An attempt to do media recovery using a backup control file found that one of
the files is marked read only. Read only files do not normally need to be recovered,
but recovery with a backup control file must recover all online files.
Action: If the file really is read only, take it offline before the recovery, and bring the
read only tablespace online after the database is open. If the file does need recovery
use a control file from the time the file was read-write. If the correct control file is not
available, use CREATE CONTROLFILE to make one.
ORA-01234: cannot end backup of file string - file is in use or recovery
Cause: Attempted to end an online backup of file when the file is busy. Some
operation such as recovery or rename may be active, or there may still be some
instance that has the database open with this file online.
Action: If there is an instance with the database open then the backup can be ended
there by using the ALTER TABLESPACE command. Otherwise wait for the
completion of the other operation.
ORA-01235: END BACKUP failed for string file(s) 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 may have succeeded.
Action: See the accompanying error messages for the reason the backups could not be
ended. Any files not listed in the error messages were successful.
ORA-01236: Error string occurred during initialization of file header access
Cause: The indicated error occurred while doing initialization processing of file
headers.
Action: The error indicated should be corrected. An attempt is made to recover from
this error by using a slower access algorithm.
ORA-01237: cannot extend datafile string
Cause: An operating system error occurred during the resize.
Action: Fix the cause of the operating system error and retry the command.
ORA-01238: cannot shrink datafile string
Cause: An operating system error occurred during the resize.
Action: The error is ignored, operation continues normally.
ORA-01239: database must be in ARCHIVELOG mode to use external cache

Cause: An online file uses an external cache, but the database is in NOARCHIVELOG
mode. Since an external cache may require media recovery this can not be allowed.
Action: Change database to be in ARCHIVELOG mode or do not use an external
cache.
ORA-01240: too many data files to add in one command
Cause: The command specifies adding more data files than can be done in one
command. It is necessary to fit all the file names into one log entry, but that would
make the entry too large.
Action: If this is a CREATE TABLESPACE command, create with fewer files then add
the other files later. If this is an ADD DATAFILE command, break it up into multiple
commands.
ORA-01241: an external cache has died
Cause: The external cache may have been restarted.
Action: Take the file mentioned in the error stack offline, perform media recovery,
bring the file online, and retry the attempted operation. You may also restart all
instances to make sure they access all data files through consistent external caches.
ORA-01242: data file suffered 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 tablespace file suffered media failure
Cause: A system tablespace 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: unnamed datafile(s) added to control file by media recovery
Cause: Media recovery with a backup control file or a control file that was rebuilt,
encountered the creation of a datafile that was not in the control file. An entry has
been added to the control file for the new datafiles, but with the file name
UNNAMEDnnnn, where nnnn is the file number. Attached errors describe the file
names that were originally used to create the files.
Action: Rename the files to valid file names and resume recovery. If necessary the
command ALTER DATABASE CREATE DATAFILE may be used to create a file
suitable for recovery and do the rename. If the file is not going to be recovered then
take it offline with the FOR DROP option.
ORA-01245: offline file string will be lost if RESETLOGS is done
Cause: Attempting to do an OPEN RESETLOGS with a file that will be lost because it
is offline. The file was not taken offline with the FOR DROP option.
Action: Either bring the file online and recover it, or take it offline with the FOR
DROP option.
ORA-01246: recovering files through TSPITR of tablespace string
Cause: The files named in the accompanying errors are backups that were made
before a tablespace point in time recovery of this tablespace. They cannot be
recovered to a time after the point in time recovery.
ORA-00900 to ORA-01499 59-29
Action: Restore more recent backups and recover them.

ORA-01247: database recovery through TSPITR of tablespace string
Cause: Recovery of the whole database encountered redo indicating there was a point
in time recovery of the tablespace. The new version of the files in the tablespace
should be included in the recovery, but that was not done.
Action: If the tablespace should not be recovered, take its file offline for drop. If it
should be recovered, then restore or rename as needed and restart the recovery.
ORA-01248: file string was created in the future of incomplete recovery
Cause: Attempting to do a RESETLOGS open with a file entry in the control file that
was originally created after the UNTIL time of the incomplete recovery. Allowing
such an entry may hide the version of the file that is needed at this time. The file
number may be in use for a different file which would be lost if the RESETLOGS was
allowed.
Action: If more recovery is desired then apply redo until the creation time of the file is
reached. If the file is not wanted and the same file number is not in use at the stop
time of the recovery, then the file can be taken offline with the FOR DROP option.
Otherwise a different control file is needed to allow the RESETLOGS. Another backup
can be restored and recovered, or a control file can be created via CREATE
CONTROLFILE.
ORA-01249: archiving not allowed in a clone database
Cause: Attempting to archive an online redo log or enable archiving for a clone
database.
Action: Do not attempt to archive from a clone. The archive log destination could
easily be the same as the primary database destroying its archived logs. If archiving is
needed then recreate database as not a clone.
ORA-01250: Error string occurred during termination of file header access
Cause: The indicated error occurred while terminating the processing of file headers.
The error was other than a write error.
Action: The indicated error should be corrected.
ORA-01251: Unknown File Header Version read for file number string
Cause: Read of the file header returned a record but its version cannot be identified.
Either the header has been corrupted, or the file is not a valid database file.
Action: Have the operating system make the correct file available to the database, or
recover the file.
ORA-01252: cannot prevent writes - file string in recovery manager backup
Cause: An attempt to make a tablespace read only or offline normal found that a
recovery manager proxy backup is in progress. If the file is made offline or read-only,
then the file header cannot be updated when the backup is complete.
Action: Wait for the Recovery Manager backup to complete and retry this command.
ORA-01253: cannot start online backup - file string in recovery manager backup
Cause: The specified file is being backed up by Recovery Manager.
Action: Wait for the Recovery Manager proxy backup to complete before starting
another backup.
ORA-01254: cannot end online backup - file string in recovery manager backup
Cause: The specified file is being backed up by Recovery Manager.
Action: Wait for the Recovery Manager proxy backup to complete. Recovery Manager
backup mode cannot be initiated or terminated manually.
ORA-01255: cannot 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 retry this
command.
ORA-01256: error in locking database file string
Cause: The file is in use by another database instance.
Action: Determine which database instance legitimately owns the file.
ORA-01257: cannot reuse database file string, unknown file size
Cause: The size of the raw partion cannot be determined
Action: Add the datafile/logfile by specifying the size parameter.
ORA-01258: unable to delete temporary file string
Cause: A DROP TABLESPACE INCLUDING CONTENTS AND DATAFILES or
ALTER DATABASE TEMPFILE DROP INCLUDING DATAFILES operation was not
able to delete a temporary file in the database.
Action: Subsequent errors describe the operating system error that prevented the file
deletion. Fix the problem, if possible, and manually purge the file.
ORA-01259: unable to delete datafile string
Cause: A DROP TABLESPACE INCLUDING CONTENTS AND DATAFILES
operation was not able to delete a datafile in the tablespace.
Action: Subsequent errors describe the operating system error that prevented the file
deletion. Fix the problem, if possible, and manually purge the file.
ORA-01260: warning: END BACKUP succeeded but some files found not to be in
backup mode
Cause: END BACKUP completed successfully for all files that were in online backup
mode. However one or more modifiable files were found not to be in online backup
mode. Backup of those files (if it was done) can be invalid and, if restored, can result
in an inconsistent database.
Action: Check the alert log for a list of the files that were found not to be in backup
mode. If there is a possibility that those files have been modified during online
backup, then replace their backups with new ones.
ORA-01261: Parameter string destination string cannot be translated
Cause: The value for the specified parameter contained a destination string that could
not be translated.
Action: Use a valid destination string in the specified parameter.
ORA-01262: Stat failed on a file destination directory
Cause: Unable to get information about an Oracle managed files destination directory.
Action: Check the permissions on the directory or use a different directory name.
ORA-00900 to ORA-01499 59-31
ORA-01263: Name given for file destination directory is invalid

Cause: The name given for an Oracle managed files destination does not correspond
to a directory.
ORA-01264: Unable to create string file name
Cause: Unable to create an Oracle managed file name.
Action: Check previous error messages for the reason Oracle was unable to create the
file name. Take corrective action, if possible, and retry the command.
ORA-01265: Unable to delete string string
Cause: An error prevented the file from being deleted.
Action: See the subsequent error messsages that describe the operating system error
that prevented the file from being deleted. If possible, fix the problem and manually
delete the file.
ORA-01266: Unable to create unique file name
Cause: Unable to create a unique file name for an Oracle managed file. Oracle tried
several names but each file name was already in use in the default destination
directory for the file type.
Action: Retry the operation. If that fails, also, it may be necessary to change the
default destination directory for the file type and then retry.
ORA-01267: Failure getting date/time
Cause: Could not get date/time when trying to create unique file name.
ORA-01268: invalid TEMPFILE clause for alter of permanent TABLESPACE
Cause: A TEMPFILE clause was specified for an ALTER TABLESPACE for a
permanent tablespace.
Action: Retry with a DATAFILE clause.
ORA-01269: Destination parameter string is too long
Cause: The value for DB_CREATE_FILE_DEST,
DB_CREATE_ONLINE_LOG_DEST_n or DB_RECOVERY_FILE_DEST parameter
was too long.
Action: Replace the destination value for the specified parameter with a shorter
character string.
ORA-01270: string operation is not allowed if STANDBY_PRESERVES_NAMES is
true
Cause: An operation that renames or adds/drops a file was attempted at a standby
database and STANDBY_PRESERVES_NAMES is true.
Action: Set STANDBY_PRESERVES_NAMES false if the operation must be
performed.
ORA-01271: Unable to create new file name for file string
Cause: During standby database recovery an error occurred when trying to create a
new file name for the indicated file.
Action: Use the ALTER DATABASE CREATE DATAFILE command with a new
unique name and then resume the standby database recovery.
ORA-01272: REUSE only allowed when a file name is provided.

Cause: The REUSE parameter was specified in a command without a file name.
Action: Either supply a file name or remove the REUSE parameter.
ORA-01273: STANDBY_FILE_MANAGEMENT = AUTO needs COMPATIBLE =
string or higher
Cause: Automated standby file management was disabled, so an added file
Action: Restart the instance with COMPATIBLE set to the correct release.
ORA-01274: cannot add data file that was originally created as 'string'
Cause: The recovery failed to add the specified data file either because the recovery
tried to create the specified data file but automated standby file management was
disabled, or the recovery tried to look for the specified data file but the data file did
not exist. In the former case, the recovery added a control file entry as
'UNNAMEDnnnnn'.
Action: Either use the ALTER DATABASE CREATE DATAFILE statement to create
the file, or set STANDBY_FILE_MANAGEMENT to AUTO, or restore the data file to
the location specified by the corresponding control file entry, and restart standby
recovery.
ORA-01275: Operation string is not allowed if standby file management is
automatic.
Cause: An operation that renames, adds, or drops a file was attempted at a standby
database and STANDBY_FILE_MANAGEMENT was set to AUTO.
Action: Set STANDBY_FILE_MANAGEMENT to MANUAL if the operation must be
performed.
ORA-01276: Cannot add file string. File has an Oracle Managed Files file name.
Cause: An attempt was made to add to the database a datafile, log file, control file,
snapshot control file, backup control file, datafile copy, control file copy or
backuppiece with an Oracle Managed Files file name.
Action: Retry the operation with a new file name.
ORA-01277: file 'string' already exists
Cause: An ALTER DATABASE BACKUP CONTROLFILE TO TRACE AS 'filename'
command specified a file name which is already in use.
Action: Either specify a different file name, or add the REUSE parameter to the
command to overwrite the existing file.
ORA-01278: error creating file 'string'
Cause: An operating system error occurred while attempting to create a trace file
specified in the command ALTER DATABASE BACKUP CONTROLFILE TO TRACE
AS 'filename'.
Action: Check the error stack for more detailed information.
ORA-01279: db_files too large
Cause: db_files has been set too high to be supported by the system.
Action: Decrease the number of db_files.
ORA-01280: Fatal LogMiner error.
Cause: An internal error occurred inside LogMiner.
ORA-00900 to ORA-01499 59-33
Action: Check the alert log and trace files for further information.
ORA-01281: SCN range specified is invalid
Cause: StartSCN may be greater than EndSCN, or the SCN specified may be invalid.
Action: Specify a valid SCN range.
ORA-01282: date range specified is invalid
Cause: startTime may be greater than endTime. startTime or endTime may be greater
than year 2110. startTime may be less than year 1988.
Action: Specify a valid date range.
ORA-01283: Options specified is invalid
Cause: The specified options parameter is invalid for the procedure.
Action: Specify valid Options parameter.
ORA-01284: file string cannot be opened
Cause: The file or directory may not exist or may be inaccessible. Pathname exceeds
256 characters.
Action: Ensure that the file and the directory exist and are accessible.
ORA-01285: error reading file string
Cause: The file or directory may not exist or is inaccessible.
Action: Specify valid file or directory. Make sure that file and directory are accessible.
ORA-01286: start interval required
Cause: Options were supplied which require a starting time or starting SCN
Action: Specify a starting interval (time or SCN).
ORA-01287: file string is from a different database incarnation
Cause: The logfile is produced by a different incarnation of the database.
Action: Add a logfile that is produced by the same incarnation.
ORA-01288: cannot apply this DDL to the Logminer Dictionary
Cause: A command that is not supported by Logminer was present in a logfile.
Commands that change the character set of the database are not supported by
Logminer. "ALTER DATABASE SET TIME_ZONE" is not supported by Logminer.
Action: Do not execute unsupported commands when using Streams, Logical
Standby, or Logminer. Turn off DDL tracking in order for Logminer to skip
unsupported commands.
ORA-01289: cannot add duplicate logfile string
Cause: The logfile specified has already been added to the list of logfiles.
Action: Specify a different logfile.
ORA-01290: cannot remove unlisted logfile string
Cause: The user attempted to remove a logfile that is not present in the list.
Action: Specify a valid logfile.
ORA-01291: missing logfile
Cause: Not all logfiles corresponding to the time or scn range specified have been
added to the list.
Action: Check the v$logmnr_logs view to determine the missing scn range, and add
the relevant logfiles.
ORA-01292: no log file has been specified for the current LogMiner session
Cause: No logfile has been specified for the LogMiner session.
Action: Specify atleast one log file.
ORA-01293: mounted database required for specified LogMiner options
Cause: Options were specified which required the database to be mounted
Action: Specify different options or mount the database.
ORA-01294: error occurred while processing information in dictionary file string,
possible corruption
Cause: The dictionary file is corrupt.
Action: Get a new dictionary file.
ORA-01295: DB_ID mismatch between dictionary string and logfiles
Cause: The dictionary file is produced by a database that is different from that
produced the logfiles.
Action: Specify a compatible dictionary file.
ORA-01296: character set mismatch between dictionary string and logfiles
Cause: The character set of the database that produced the dictionary file is different
from the charatcter set of the database that produced the logfiles.
Action: Specify a dictionary file with the same character set.
ORA-01297: redo version mismatch between dictionary string and logfiles
Cause: The redo version of the database generating the dictionary is different from
the one generating the logfiles.
Action: n/a
ORA-01298: conflicting dictionary option
Cause: More than one dictionary source was specified or DDL_DICT_TRACKING
was specified with DICT_FROM_ONLINE_CATALOG.
Action: n/a
ORA-01299: dictionary string corresponds to a different database incarnation
Cause: The dictionary file was extracted from a different incarnation of the database.
Action: Specify a dictionary file extracted from the correct database incarnation.
ORA-01300: writable database required for specified LogMiner options
Cause: Options were specified which required the database to be writable.
Action: Specify different options or open the database for write access.
ORA-01301: error writing to file during flat file build
Cause: Error writing to file during flat file build
Action: n/a
ORA-01302: dictionary build options missing or incorrect
Cause: Missing dictionary build options or incorrectly specified options
ORA-00900 to ORA-01499 59-35
Action: Specify either a build to redo log or to flat file. If build to flat file, specify
filename and directory.
ORA-01303: subordinate process error: string. Check alert and trace logs
Cause: A process subordinate to this Logminer process has exited with this error
status.
Action: Search for this error in the alert log and trace files for additional information.
ORA-01304: subordinate process error. Check alert and trace logs
Cause: A process subordinate to this Logminer process has exited with an error
condition.
Action: Look in the alert log and trace files for additional information.
ORA-01305: incompatible database character set
Cause: The database character set of the mining database was not a superset of the
source database character set.
Action: Perform the mining operation on a database having a compatible database
character set.
ORA-01306: dbms_logmnr.start_logmnr() must be invoked before selecting from v
$logmnr_contents
Cause: A select was issued from v$logmnr_contents without first invoking the
dbms_logmnr.start_logmnr() procedure.
Action: Invoke 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 invoking 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.
ORA-01308: initialization parameter utl_file_dir is not set
Cause: utl_file_dir is not set in the initialization file.
Action: Set utl_file_dir to the appropriate directory.
ORA-01309: invalid session
Cause: The specified Logminer session ID or session handle is invalid.
Action: Use a valid Logminer session ID or session handle.
ORA-01310: requested return type not supported by the lcr_mine function
Cause: The return type requested by the user is not supported by lcr_mine"
Action: Pick a return type supported by the lcr_mine function"
ORA-01311: Illegal invocation of the mine_value function
Cause: An attempt was made to use mine_value function on a column other than
redo_value or undo_value columns of SYS.X$LOGMNR_CONTENTS or SYS.V
$LOGMNR_CONTENTS fixed table/view.
Action: Rewrite the SQL statement with a legal invocation of mine_value
ORA-01312: Specified table/column does not exist

Cause: The table/column specified in the lcr_mine call does not exist at the the
specified SCN. The table/column definition has to exist at the start SCN specified for
lcr_mine to be able to identify the table/column correctly.
Action: Create a LogMiner session at a start SCN at which the table definition is
available.
ORA-01313: LogMiner dictionary column type different from specified type
Cause: The return type specified for the column in lcr_mine call is different from the
actual type of the column.
Action: Rewrite the lcr_mine invocation with the right return type.
ORA-01314: Name of the column to be mined should be a string literal
Cause: The fully qualified name of the column to be mined by the LogMiner functions
should be string literal.
Action: If the fully qualified name of the column to be mined is a.b.c.d, enclose the
column name in quotes as in 'a.b.c.d'.
ORA-01315: Log file has been added or removed during select
Cause: A redo log file has been added or removed while selecting on the v
$logmnr_logs fixed view.
Action: Re-issue the SQL select statement on the v$logmnr_logs view.
ORA-01316: Already attached to a Logminer session
Cause: A Logminer attach session was issued while already attached to a Logminer
session.
Action: Detach from the current Logminer session and attach to the requested session.
ORA-01317: Not attached to a Logminer session
Cause: A command or procedure was issued which requires an attached Logminer
session.
Action: Attach to a Logminer session before issuing the command or procedure.
ORA-01318: incompatible national character set
Cause: The national character set of the mining database was not a superset of the
source database national character set.
Action: Perform the mining operation on a database having a compatible national
character set.
ORA-01319: Invalid Logminer session attribute
Cause: A session attribute was supplied which is invalid.
Action: Re-issue with valid session attribute.
ORA-01320: Invalid Logminer dictionar attribute
Cause: A Logminer dictionary attribute was supplied which is invalid.
Action: Re-issue with valid dictionary attribute.
ORA-01321: No Logminer Dictionary for requested start SCN
Cause: The requested session start SCN is less than the SCN of any available
Logminer Dictionary build. It is not possible to unwind a Logminer Dictionary to the
requested start SCN.
ORA-00900 to ORA-01499 59-37
Action: Re-issue the start_logminer request with a start SCN for which a Logminer
Dictionary is available.
ORA-01322: No such table
Cause: An non-existent table was supplied to Logminer include_src_tbl() or
exclude_src_table().
Action: Re-issue with valid table name.
ORA-01323: Invalid state
Cause: A Logminer routine was called from the wrong state.
Action: n/a
ORA-01324: cannot add file string due to DB_ID mismatch
Cause: The logfile is produced by a different database than other logfiles already
added to the list.
Action: Specify a logfile produced by the same database.
ORA-01325: archive log mode must be enabled to build into the logstream
Cause: Database does not have archivelog mode enabled.
Action: Mount the database, then issue commands to enable archivelog mode. startup
pfile=init.ora mount alter database archivelog alter database open
ORA-01326: compatability of 9.0 or greater required to build into the logstream
Cause: Compatibility mode set to some value less than 9.0
Action: Ensure that init.ora parameter establishing a compatability of 9.0 or greater is
set. For example: compatible=9.0.0.0.0
ORA-01327: failed to exclusively lock system dictionary as required by build
Cause: Other users are performing DDL operations.
Action: n/a
ORA-01328: only one build operation may occur at one time
Cause: Another processes is simultaneously attempting to run build();
Action: Wait until the other processes completes.
ORA-01329: unable to truncate required build table
Cause: The table may be missing, or locked by another user.
Action: n/a
ORA-01330: problem loading a required build table
ORA-01331: general error while running build
ORA-01332: internal Logminer Dictionary error
Cause: Unexpected error condition
Action: Check trace and/or alert logs
ORA-01333: failed to establish Logminer Dictionary
Cause: No previously established Logminer Dictionary is available and a complete
gather of a source system data dictionary was not found in the logstream. build() may
not have been run to force the gathering of a source system data dictiony. Or
add_log_file() may not have been called to add all log files which contain the
complete gathered system data dictionary.
Action: If build() was not employed prior to this mining session the Logminer Ad Hoc
user may elect to employ an alternate dictionary such as the current system catalog or
a previously built flat file dictionary. Other Logminer clients must run build() prior to
mining. If build() has been run, ensure that all logfiles which comprise the gathered
system dictionary have beed added. The following query, run on the system which
build() was run, can be helpful in identifying the requried files. select
DICTIONARY_BEGIN, DICTIONARY_END, name from v$archived_log; Minimally
a set of files beginning with one which has DICTIONARY_BEGIN = 'YES' and all
following log files through one marked DICTIONARY_END = 'YES' must be added.
ORA-01334: invalid or missing logminer dictionary processes context
Cause: Unexpected internal error condition
Action: n/a
ORA-01335: feature not yet implemented
ORA-01336: specified dictionary file cannot be opened
Cause: The dictionary file or directory does not exist or is inaccessible.
Action: Make sure that the dictionary file and directory exist and are accessible.
ORA-01337: log file has a different compatibility version
Cause: The logfile has a different compatibility version then the rest of the logfile in
the session"
Action: Make sure that the logfile has the same compatibility version as the rest of the
logfiles in the session.
ORA-01338: Other process is attached to LogMiner session
Cause: Can not do this when other process is attached to LogMiner session.
Action: n/a
ORA-01339: LogMiner BUILD: Error copying system catalog metadata to LogMiner
dictionary
Cause: Unexpected result while accessing system catalog metadata.
Action: Check the alert log.
ORA-01340: NLS error
Cause: Could not load NLS package.
Action: n/a
ORA-01341: LogMiner out-of-memory
Cause: The LogMiner session requires more system resources than is currently
available.
Action: Allocate more SGA for LogMiner.
ORA-01342: LogMiner can not resume session due to inability of staging
checkpointed data
Cause: Logmnr can not resume session because there is not enough SGA memory
available to read in checkpointed data. Logminer periodically checkpoints data to
enable faster crash recovery.
Action: Specify a bigger max_sga for the given LogMiner session and try again.
ORA-00900 to ORA-01499 59-39
ORA-01343: LogMiner encountered corruption in the logstream

Cause: Log file is missing a range of scn values.
Action: Verify the contiguity of the scn range reprented by the log files added to
LogMiner.
ORA-01344: LogMiner coordinator already attached
Cause: A coordinator process is already attached to the specified logminer context.
Action: Detach from the active coordinator session and retry the attach.
ORA-01345: Must be a LogMiner coordinator process
Cause: A LogMiner client attempted to perform a privileged operation.
Action: Issue the operation from the coordinator process.
ORA-01346: Oracle LogMiner processed redo beyond primary reset log SCN string
Cause: Oracle LogMiner detected a new branch with reset log SCN information prior
to redo already mined.
Action: If running inside SQL Apply, retrieve standby reset SCN by executing
DBMS_LOGSTDBY.MAP_PRIMARY_SCN (primary reset log SCN). And, execute
FLASHBACK STANDBY DATABASE [<database_name>] TO BEFORE SCN standby
reset SCN. Note: If the primary reset log SCN is 0, then intermediary log files are
missing. Check the primary database for missing log files. In other scenarios, contact
ORA-01347: Supplemental log data no longer found
Cause: The source database instance producing log files for this LogMiner session
was altered to no longer log supplemental data.
Action: Destroy this Logminer session. Re-enable supplemental log data on the source
system and create a new LogMiner session.
ORA-01348: LogMiner testing event
ORA-01349: LogMiner tracing event
ORA-01350: must specify a tablespace name
Cause: Invocation failed to specify a valid tablespace
Action: Reformat invocation of DBMS_LOGMNR_D.SET_TABLESPACE to include
the name of a valid tablespace.
ORA-01351: tablespace given for Logminer dictionary does not exist
Cause: The tablespace name given as a parameter to
DBMS_LOGMNR_D.SET_TABLESPACE does not exist.
Action: Check spelling of the tablespace name. If spelling is correct verify that the
named tablespace has already been created. DBMS_LOGMNR_D.SET_TABLESPACE
does not create a tablespace.
ORA-01352: tablespace given for Logminer spill does not exist
Cause: The tablespace name given as the parameter to
DBMS_LOGMNR_D.SET_TABLESPACE does not exist.
Action: Check spelling of the tablespace name. If spelling is correct verify that the
named tablespace has already been created. DBMS_LOGMNR_D.SET_TABLESPACE
does not create a tablespace.
ORA-01353: existing Logminer session

Cause: An attempt was made to execute DBMS_LOGMNR_D.SET_TABLESPACE
while a Logminer session(s) was active.
Action: First cause all Logminer sessions to be closed. A Logminer session can exist as
a result of executing DBMS_LOGMNR.START_LOGMNR or as the result of using
Oracle features such as Data Guard SQL Apply or Streams which use Logminer. Next,
execute DBMS_LOGMNR_D.SET_TABLESPACE.
ORA-01354: Supplemental log data must be added to run this command
Cause: An attempt was made to perform an operation that required that
supplemental log data be enabled.
Action: Execute a command such as ALTER DATABASE ADD SUPPLEMENTAL
LOG DATA; and then reissue the command that failed with this error.
ORA-01355: logminer tablespace change in progress
Cause: The tables used by logminer are in the process of being moved to another
tablespace.
Action: Wait until the move is complete and try again.
ORA-01356: active logminer sessions found
Cause: Logminer sessions are currently active.
Action: End all logminer sessions and retry.
ORA-01358: LogMiner version is less than mined dictionary version
Cause: An attempt was made to mine a LogMiner dictionary from redo logs. The
version of the Oracle database that created the logs was higher than the Oracle
database version that attempted to mine the logs.
Action: Mine the logs using a newer version of the Oracle database having a version
number that is equal to or greater than the dictionary version.
ORA-01360: invalid token
ORA-01361: global name mismatch
Cause: The database global name where the log file was generated did not match the
user-specified global name of the Streams Capture process.
Action: Start a new capture process and ensure that the user-specified global name
matches that of the database that generated the log file.
ORA-01362: Specified SQL_REDO_UNDO parameter is invalid
Cause: The specified input value for the parameter was not a valid number.
Action: Specify a valid number and try again.
ORA-01363: Specified COLUMN_NAME parameter is NULL
Cause: NULL was specified for input value of parameter.
Action: Specify a non-NULL value and try again.
ORA-01364: waiting for branch at SCN string
Cause: LogMiner reader process has completed mining of physical standby terminal
logs up to the stop SCN. LogMiner reader is now waiting for logs from the new
branch.
ORA-00900 to ORA-01499 59-41
Action: No action necessary. This informational statement is provided to record the

event for diagnostic purposes. If there is a problem with log transport, the files can be
registered manually using the ALTER DATABASE REGISTER LOGICAL LOGFILE
statement.
ORA-01365: waiting for new branch registration
Cause: LogMiner reader process has completed mining of physical standby terminal
logs up to the stop SCN. The builder process is now waiting for logs from the new
branch to be registered before continuing.
event for diagnostic purposes. If there is a problem with log transport, the files may
be registered manually using the ALTER DATABASE REGISTER LOGICAL
LOGFILE statement.
ORA-01366: failed to find redo logs required for terminal apply
Cause: LogMiner failed to find all the expected log files required to complete the
terminal apply, requested using the FINISH APPLY clause. During terminal apply,
LogMiner does not wait for logs to be registered. It expects all logs between the
starting point and the last log on any redo branch that it will or could mine through,
to be present at the mining site.
Action: Examine system.logmnr_log$ to see which logs are known to LogMiner.
Then, locate or restore any missing logs and use the ALTER DATABASE REGISTER
LOGICAL LOGFILE statement to register them. Alternatively, do not use the FINISH
APPLY clause, but if activating a logical standby, only do this when you are sure that
the missing log files can not be located and registered as this can lead to data loss.
ORA-01370: Specified restart SCN is too old
Cause: specified restart scn is too old, logmnr could not find a proper checkpoint.
Action: Specify a bigger restart SCN to try again
ORA-01371: Complete LogMiner dictionary not found
Cause: One or more log files containing the LogMiner dictionary was not found.
Action: Add into LogMiner all log files containing the dictionary.
ORA-01372: Insufficient processes for specified LogMiner operation
Cause: The number of processes requested by the caller can not be allocated
Action: Increase number of parallel servers allocated to the instance
ORA-01373: insufficient memory for staging persistent LogMiner session
Cause: The maximum number of concurrent persistent LogMiner sessions allowed is
limited by LOGMNR_MAX_PERSISTENT_SESSIONS parameter. Not enough
memory has been set aside at instance startup to allocate the new LogMiner session.
Action: Increase LOGMNR_MAX_PERSISTENT_SESSIONS and restart instance.
ORA-01374: _log_parallelism_max greater than 1 not supported in this release
Cause: LogMiner does not mine redo records generated with _log_parallelism_max
set to a value greater than 1.
Action: n/a
ORA-01375: Corrupt logfile string recovered
Cause: A corrupt logfile has been recovered by RFS
Action: None. Logical Standby should automatically restart. If logfile is still corrupt,
may need to manually copy and reregister the logfile on the standby.
ORA-01377: Invalid log file block size
Cause: An invalid value was specified in the BLOCKSIZE clause.
Action: Use correct syntax.
ORA-01378: The logical block size (string) of file string is not compatible with the
disk sector size (media sector size is string and host sector size is string)
Cause: One of the following occurred: (1) An attempt was made to create a file. (2) A
file was moved to disks with different sector size.
Action: Create file or move file to the proper disk.
ORA-01380: Instance string (thread string) has less than two string block size log
files
Cause: One of the following occurred: (1) An attempt was made to switch to specified
block size logs for all threads. (2) An attemp was made to open a thread.
Action: Add log files to the thread that signals error, and try again.
ORA-01381: Dropping log string would leave less than two log files with block size
string for instance string (thread string)
Cause: The database was migrated to use a specified log block size. Dropping all the
logs specified would leave fewer than the required two log files with the specified
block size per enabled thread.
Action: Either drop fewer logs or disable the thread before deleting the logs. It may be
possible to clear the log rather than drop it.
ORA-01382: Thread string failed to open log file string. The log file's block size
(string) is larger than the disk sector size (string)
Cause: Log file was created on bigger sector disks, and moved to smaller sector disks.
Action: Move the log file back to bigger sector disks.
ORA-01383: Thread string failed to open string block size log file 'string' on string
sector native-mode disks
Cause: Log file was copied from smaller sector disks to larger sector native-mode
disks.
Action: Move the log file back to smaller sector disks.
ORA-01398: LogMiner public event
ORA-01399: LogMiner public event
ORA-01400: cannot insert NULL into (string)
Cause: An attempt was made to insert NULL into previously listed objects.
Action: These objects cannot accept NULL values.
ORA-01401: inserted value too large for column
Cause: The value inserted was too large for the given column.
Action: Do not insert a value greater than what the column can hold.
ORA-00900 to ORA-01499 59-43
ORA-01402: view WITH CHECK OPTION where-clause violation

ORA-01403: no data found
Cause: No data was found from the objects.
Action: There was no data from the objects which may be due to end of fetch.
ORA-01404: ALTER COLUMN will make an index too large
ORA-01405: fetched column value is NULL
ORA-01406: fetched column value was truncated
Cause: The fetched column values were truncated.
Action: Use the right data types to avoid truncation.
ORA-01407: cannot update (string) to NULL
ORA-01408: such column list already indexed
ORA-01409: NOSORT option may not be used; rows are not in ascending order
Cause: Creation of index with NOSORT option when rows were not ascending. For
non-unique indexes the rowid is considered part of the index key. Therefore, if you
create an index nosort and two of the rows in the table have the same key and are
stored in ascending order, but get split accross two extents where the dba of the first
block in the second extent is less than the dba of the last block in the first extent, then
the create index nosort may fail.
Action: Create the index without the NOSORT option, or ensure table is stored in one
extent.
ORA-01410: invalid ROWID
ORA-01411: cannot store the length of column in the indicator
Cause: Tried to fetch a column of size more than 64K and couldn't store the length of
the column in the given indicator of size 2 bytes.
Action: Use the new bind type with call backs to fetch the long column.
ORA-01412: zero length not allowed for this datatype
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 trying to bind array
Cause: An attempt was made to bind an array without either a current array length
pointer or a zero maximum array length.
Action: Sepcify 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 outer-joined to each other
ORA-01417: a table may be outer joined to at most one other table
Cause: a.b (+) = b.b and a.c (+) = c.c is not allowed
Action: Check that this is really what you want, then join b and c first in a view.
ORA-01418: specified index does not exist
ORA-01419: datdts: illegal format code
ORA-01420: datstd: illegal format code
ORA-01421: datrnd/dattrn: illegal precision specifier
ORA-01422: exact fetch returns more than requested number of rows
Cause: The number specified in exact fetch is less than the rows returned.
Action: Rewrite the query or change number of rows requested
ORA-01423: error encountered while checking for extra rows in exact fetch
ORA-01424: missing or illegal character following the escape character
Cause: The character following the escape character in LIKE pattern is missing or not
one of the escape character, '%', or '_'.
Action: Remove the escape character or specify the missing character.
ORA-01425: escape character must be character string of length 1
Cause: Given escape character for LIKE is not a character string of length 1.
Action: Change it to a character string of length 1.
ORA-01426: numeric overflow
Cause: Evaluation of an value expression causes an overflow/underflow.
Action: Reduce the operands.
ORA-01427: single-row subquery returns more than one row
ORA-01428: argument 'string' is out of range
ORA-01429: Index-Organized Table: no data segment to store overflow row-pieces
Cause: No overflow segment defined.
Action: Add overflow segment.
ORA-01430: column being added already exists in table
ORA-01431: internal inconsistency in GRANT command
ORA-01432: public synonym to be dropped does not exist
ORA-01433: synonym to be created is already defined
ORA-01434: private synonym to be dropped does not exist
ORA-01435: user does not exist
ORA-00900 to ORA-01499 59-45
ORA-01436: CONNECT BY loop in user data

ORA-01437: cannot have join with CONNECT BY
ORA-01438: value larger than 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.
Action: Enter a value that complies with the numeric column's precision, 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 datatype
ORA-01440: column to be modified must be empty to decrease precision or scale
ORA-01441: cannot decrease column length because some value is too big
ORA-01442: column to be modified to NOT NULL is already NOT NULL
ORA-01443: internal inconsistency; illegal datatype in resultant view column
ORA-01444: internal inconsistency; internal datatype maps to invalid external type
ORA-01445: cannot select ROWID from, or sample, a join view without a keypreserved table
ORA-01446: cannot select ROWID from, or sample, a view with DISTINCT,
GROUP BY, etc.
ORA-01447: ALTER TABLE does not operate on clustered columns
ORA-01448: index must be dropped before changing to desired type
ORA-01449: column contains NULL values; cannot alter to NOT NULL
ORA-01450: maximum key length (string) exceeded
ORA-01451: column to be modified to NULL cannot be modified to NULL
Cause: the column may already allow NULL values, the NOT NULL constraint is part
of a primary key or check constraint.
Action: if a primary key or check constraint is enforcing the NOT NULL constraint,
then drop that constraint.
ORA-01452: cannot CREATE UNIQUE INDEX; duplicate keys found
ORA-01453: SET TRANSACTION must be first statement of transaction
Cause: self-evident
Action: commit (or rollback) transaction, and re-execute
ORA-01454: cannot convert column into numeric datatype
ORA-01455: converting column overflows integer datatype
ORA-01456: may not perform insert/delete/update operation inside a READ ONLY

transaction
Cause: A non-DDL insert/delete/update or select for update operation was
attempted
ORA-01457: converting column overflows decimal datatype
ORA-01458: invalid length inside variable character string
ORA-01459: invalid length for variable character string
ORA-01460: unimplemented or unreasonable conversion requested
ORA-01461: can bind a LONG value only for insert into a LONG column
ORA-01462: cannot insert string literals longer than 4000 characters
ORA-01463: cannot modify column datatype with current constraint(s)
Cause: An attempt was made to modify the datatype of column which has referential
constraints; or has check constraints which only allows changing the datatype from
CHAR to VARCHAR or vise versa.
Action: Remove the constraint(s) or do not perform the offending operation.
ORA-01464: circular grant (granting to grant ancestor) of table or view
ORA-01465: invalid hex number
ORA-01466: unable to read data - table definition has changed
Cause: Query parsed after tbl (or index) change, and executed w/old snapshot
ORA-01467: sort key too long
ORA-01468: a predicate may reference only one outer-joined table
ORA-01469: PRIOR can only be followed by a column name
Cause: Attempting to specify "PRIOR something" where something is not a column
name.
Action: Only a column name can follow PRIOR. Replace with a column name.
ORA-01470: In-list iteration does not support mixed operators
Cause: Constants of different types are specified in an in-list.
Action: Use constants of same type for in-lists.
ORA-01471: cannot create a synonym with same name as object
ORA-01472: cannot use CONNECT BY on view with DISTINCT, GROUP BY, etc.
ORA-01473: cannot have subqueries in CONNECT BY clause
ORA-01474: cannot have START WITH or PRIOR without CONNECT BY
ORA-01475: must reparse cursor to change bind variable datatype
ORA-00900 to ORA-01499 59-47
ORA-01476: divisor is equal to zero

ORA-01477: user data area descriptor is too large
ORA-01478: array bind may not include any LONG columns
Cause: User is performing an array bind with a bind variable whose maximum size is
greater than 2000 bytes.
Action: Such bind variables cannot participate in array binds. Use an ordinary bind
operation instead.
ORA-01479: last character in the buffer is not Null
Cause: A bind variable of type 97 does not contain null at the last position
Action: Make the last character null
ORA-01480: trailing null missing from STR bind value
Cause: A bind variable of type 5 (null-terminated string) does not contain the
terminating null in its buffer.
Action: Terminate the string with a null character
ORA-01481: invalid number format model
Cause: The user is attempting to either convert a number to a string via TO_CHAR or
a string to a number via TO_NUMBER and has supplied an invalid number format
model parameter.
Action: Consult your manual.
ORA-01482: unsupported character set
Cause: The character set used to perform the operation, such as the CONVERT
function, is not a supported character set.
Action: Use one of the supported character sets.
ORA-01483: invalid length for DATE or NUMBER bind variable
Cause: A bind variable of type DATE or NUMBER is too long.
Action: Consult your manual for the maximum allowable length.
ORA-01484: arrays can only be bound to PL/SQL statements
Cause: You tried to bind an array to a non-PL/SQL statement.
Action: n/a
ORA-01485: compile bind length different from execute bind length
Cause: You bound a buffer of type DTYVCS (VARCHAR with the two byte length in
front) and at execute time the length in the first two bytes is more than the maximum
buffer length (given in the bind call). The number of elements in the array and the
current number of elements in the array cannot be more than the maximum size of
the array.
Action: n/a
ORA-01486: size of array element is too large
Cause: You tried to bind a data value which was either too large for the datatype (for
example, NUMBER) or was greater than 4000 bytes (for example, VARCHAR or
LONG).
Action: n/a
ORA-01487: packed decimal number too large for supplied buffer

Cause: An impossible request for decimal to oracle number conversion was made
Action: This conversion cannot be performed
ORA-01488: invalid nibble or byte in the input data
Cause: An impossible request for decimal to oracle number conversion was made
ORA-01489: result of string concatenation is too long
Cause: String concatenation result is more than the maximum size.
Action: Make sure that the result is less than the maximum size.
ORA-01490: invalid ANALYZE command
Cause: Incorrect syntax specified
Action: Retry the command
ORA-01491: CASCADE option not valid
Cause: The CASCADE option is only valid for tables or clusters.
Action: Do not specify CASCADE
ORA-01492: LIST option not valid
Cause: The LIST option is only valid for tables or clusters.
Action: Do not specify LIST
ORA-01493: invalid SAMPLE size specified
Cause: The specified SAMPLE size is out of range
Action: Specify a value within the proper range.
ORA-01494: invalid SIZE specified
Cause: The specified histogram SIZE value was out of range.
Action: Specify a value within the proper range.
ORA-01495: specified chain row table not found
Cause: The specified table either does not exist or user does not have the proper
privleges.
Action: Specify the correct table to use.
ORA-01496: specified chain row table form incorrect
Cause: The specified table does not have the proper field definitions.
ORA-01497: illegal option for ANALYZE CLUSTER
Cause: The FOR COLUMNS column-list clause may not be used with ANALYZE
CLUSTER.
Action: Retry with a legal syntax.
ORA-01498: block check failure - see trace file
ORA-01499: table/index cross reference failure - see trace file
ORA-00900 to ORA-01499 59-49
60
ORA-01500 to ORA-02098
ORA-01500: failure in getting date/time
Cause: During create database or alter tablespace, there was a failure in getting the
date and time.
ORA-01501: CREATE DATABASE failed
Cause: An error occurred during create database
ORA-01502: index 'string.string' or partition of such index is in unusable state
Cause: An attempt has been made to access an index or index partition that has been
marked unusable by a direct load or by a DDL operation
Action: DROP the specified index, or REBUILD the specified index, or REBUILD the
unusable index partition
ORA-01503: CREATE CONTROLFILE failed
Cause: An error occurred during CREATE CONTROLFILE
ORA-01504: database name 'string' does not match parameter db_name 'string'
Cause: The name in a database create or mount does not match the name given in the
INIT.ORA parameter db_name.
Action: correct or omit one of the two names.
ORA-01505: error in adding log files
Cause: During create or alter database, error(s) occurred when adding new log files.
Action: Check error stack for detailed error information.
ORA-01506: missing or illegal database name
Cause: No db_name INIT.ORA aprameter was specified.
Action: The database name must be given in the db_name INIT.ORA parameter.
ORA-01507: database not mounted
Cause: A command was attempted that requires the database to be mounted.
Action: If you are using the ALTER DATABASE statement via the SQLDBA startup
command, specify the MOUNT option to startup; else if you are directly doing an
ALTER DATABASE DISMOUNT, do nothing; else specify the MOUNT option to
ALTER DATABASE. If you are doing a backup or copy, you must first mount the
desired database. If you are doing a FLASHBACK DATABASE, you must first mount
the desired database.
ORA-01500 to ORA-02098 60-1
ORA-01508: cannot create database; error in file 'string' at line string

Cause: CREATE DATABASE was unable to process the specified file.
Action: Check the offending line in the specified file.
ORA-01509: specified name 'string' does not match actual 'string'
Cause: The database name specified in ALTER DATABASE does not match the name
of the currently mounted database.
Action: Correct the database name spelling or DISMOUNT the mounted database.
ORA-01510: error in deleting log files
Cause: During ALTER DATABASE, an error occurred while dropping log files.
ORA-01511: error in renaming log/data files
Cause: An error occurred during the ALTER DATABASE RENAME FILE command.
ORA-01512: error renaming log file string - new file string not found
Cause: An attempt to change a log file's name in the control file failed because no file
was found with the new name.
Action: Make sure that the log file has been properly renamed by the operating
system and retry.
ORA-01513: invalid current time returned by operating system
Cause: The operating system returned a time that was not between 1988 and 2121.
Action: Correct the time kept by the operating system.
ORA-01514: error in log specification: no such log
Cause: A log file name, or list of member names, did not correspond to an existing
log.
Action: Specify an existing log file.
ORA-01515: error dropping log group string: no such log
Cause: ALTER DATABASE is attempting to drop a log file which is not known to the
database control file.
Action: Specify the name of an existing log file.
ORA-01516: nonexistent log file, data file, or temporary file "string"
Cause: An attempt was made to use ALTER DATABASE to rename a log file, data
file, or temporary file; or to change attributes of a data file or temporary file (for
example, resize, autoextend, online or offline); or to re-create or move a data file. The
attempt failed because the specified file is not known to the database's control file or
is not of a type supported by the request.
Action: Specify the name or number of an existing file of the correct type, as
appropriate. Check the relevant V$ table for a list of possible files.
ORA-01517: log member: 'string'
Cause: Used to print member names
Action: See top level error for information
60-2 Error Messages
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 while processing file 'string' near line string
Cause: CREATE DATABASE encountered a problem while processing specified file.
The specified file is bad.
Action: Retry your system installation procedure or contact your customer support
representative.
ORA-01520: number of data files to add (string) exceeds limit of string
Cause: CREATE TABLESPACE statement specifies more files than is permitted for
this database.
Action: Use fewer files or re-create the database with a larger value of
MAXDATAFILES.
ORA-01521: error in adding data files
Cause: During CREATE or ALTER TABLESPACE, an error was detected while
adding data files.
ORA-01522: file 'string' to be renamed does not exist
Cause: During ALTER TABLESPACE RENAME, a file to be renamed was not found
in the database control file.
Action: Specify the correct file name.
ORA-01523: cannot rename data file to 'string' - file already part of database
Cause: During ALTER DATABASE RENAME or ALTER TABLESPACE RENAME,
the new name of a file is already present in the control file.
Action: Rename the file to a name not already being used as part of the database.
ORA-01524: cannot create data file as 'string' - file already part of database
Cause: During ALTER DATABASE CREATE DATAFILE, the new name of a file is
already present in the control file.
Action: Create the file as a name not already being used as part of the database.
ORA-01525: error in renaming data files
Cause: An error occurred when renaming files as part of ALTER TABLESPACE.
Action: Check the error stack for detailed information. All files are renamed except for
those mentioned in the error stack.
ORA-01526: error in opening file 'string'
Cause: CREATE DATABASE was not able to open the specified file. This is probably
due to a system installation error.
representative.
ORA-01527: error while reading file
Cause: CREATE DATABASE was not able to read the specified file. This is probably
due to a system installation error.
ORA-01500 to ORA-02098 60-3
representative.
ORA-01528: EOF while processing SQL statement
Cause: CREATE DATABASE unexpectedly hit EOF while reading the specified file.
The sql.bsq file is bad.
representative.
ORA-01529: error closing file 'string'
Cause: CREATE DATABASE was not able to close the specified file.
representative.
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 in which a database is or has previously been mounted.
Action: If you wish to mount the database, shutdown the instance and then startup
the instance and retry the operation.
ORA-01531: a database already open by the instance
Cause: During ALTER DATABASE, an attempt was made to open a database on an
instance for which there is already an open database.
Action: If you wish to open a new database on the instance, first shutdown the
instance and then startup the instance and retry the operation.
ORA-01532: cannot create database; instance being started elsewhere
Cause: During CREATE DATABASE, another user appears to be simultaneously
altering the instance.
Action: Make sure no one else is simultaneously altering the instance. If no one is,
contact your customer support representative; otherwise, retry the operation.
ORA-01533: cannot rename file 'string'; file does not belong to tablespace
Cause: During ALTER TABLESPACE RENAME, a file to be renamed was not found
in the argument tablespace.
Action: Specify the correct file name or the correct tablespace name.
ORA-01534: rollback segment 'string' doesn't exist
Cause: During ALTER or DROP ROLLBACK SEGMENT, the specified rollback
segment name is unknown.
Action: Use the correct rollback segment name.
ORA-01535: rollback segment 'string' already exists or given name has prefix
_SYSSMU
Cause: Specified rollback segment already exists or given name starts with _SYSSMU.
Action: Use a different name. Note that _SYSSMU is an illegal prefix to an RBU
segment.
ORA-01536: space quota exceeded for tablespace 'string'
Cause: The space quota for the segment owner in the tablespace has been exhausted
and the operation attempted the creation of a new segment extent in the tablespace.
60-4 Error Messages
Action: Either drop unnecessary objects in the tablespace to reclaim space or have a
privileged user increase the quota on this tablespace for the segment owner.
ORA-01537: cannot add file 'string' - file already part of 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 segment
Cause: Failed to acquire any rollback segment during startup in shared mode
Action: Startup in exclusive mode to create one more public segment or specify
available private segments in the INIT.ORA parameter rollback_segments_required,
then startup in shared mode
ORA-01539: tablespace 'string' is not online
Cause: Failed to either make a tablespace read-only or offline because it is not online.
A tblespace must be online before it can become read-only or offline normal.
Action: Check the status of the tablespace. Use IMMEDIATE or TEMPORARY options
to force all files offline. Bring the tablespace online before making it read-only.
ORA-01540: tablespace 'string' is not offline
Cause: Failed to bring a tablespace online because it is not offline
Action: Check the status of the tablespace
ORA-01541: system tablespace cannot be brought offline; shut down if necessary
Cause: Tried to bring system tablespace offline
Action: Shutdown if necessary to do recovery
ORA-01542: tablespace 'string' is offline, cannot allocate space in it
Cause: Tried to allocate space in an offline tablespace
Action: Bring the tablespace online or create the object in other tablespace
ORA-01543: tablespace 'string' already exists
Cause: Tried to create a tablespace which already exists
Action: Use a different name for the new tablespace
ORA-01544: cannot drop system rollback segment
Cause: Tried to drop system rollback segment
Action: None
ORA-01545: rollback segment 'string' specified not available
Cause: Either: 1) An attempt was made to bring a rollback segment online that is
unavailable during startup; for example, the rollback segment is in an offline
tablespace. 2) 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. 3) An attempt was made to drop a
rollback segment that is currently online. 4) An attempt was made to alter a rollback
segment that is currently online to use unlimited extents. 5) An attempt was made to
online a rollback segment that is corrupted. This is because the rollback is specified in
_corrupted_rollback_segments parameter in initialization parameter file.
ORA-01500 to ORA-02098 60-5
Action: Either: 1) Make the rollback segment available; for example, bring an offline
tablespace online. 2) Remove the name from the ROLLBACK_SEGMENTS parameter
if the name is a duplicate or if another instance has already acquired the rollback
segment. 3) Bring the rollback segment offline first. This may involve waiting for the
active transactions to finish, or, if the rollback segment needs recovery, discover
which errors are holding up the rolling back of the transactions and take appropriate
actions. 4) Same as 3). 5) Remove the name from the _corrupted_rollback_segments
parameter.
ORA-01546: tablespace contains active rollback segment 'string'
Cause: Tried to make a tablespace that contains active rollback segment(s) offline or
read-only
Action: Shutdown instances that use the active rollback segments in the tablespace
and then make the tablespace offline or read-only
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get
error below
Cause: Media recovery with one of the incomplete recovery options ended without
error. However, if the ALTER DATABASE OPEN RESETLOGS command were
attempted now, it would fail with the specified error. The most likely cause of this
error is forgetting to restore one or more datafiles from a sufficiently old backup
before executing the incomplete recovery.
Action: Rerun the incomplete media recovery using different datafile backups, a
different control file, or different stop criteria.
ORA-01548: active rollback segment 'string' found, terminate dropping tablespace
Cause: Tried to drop a tablespace that contains active rollback segment(s)
Action: Shutdown instances that use the active rollback segments in the tablespace
and then drop the tablespace
ORA-01549: tablespace not empty, use INCLUDING CONTENTS option
Cause: Tried to drop a non-empty tablespace
Action: To drop all the objects in the tablespace, use the INCLUDING CONTENTS
option
ORA-01550: cannot drop system tablespace
Cause: Tried to drop system tablespace
Action: None
ORA-01551: extended rollback segment, pinned blocks released
Cause: Doing recursive extent of rollback segment, trapped internally by the system
Action: None
ORA-01552: cannot use system rollback segment for non-system tablespace 'string'
Cause: Tried to use the system rollback segment for operations involving non-system
tablespace. If this is a clone database then this will happen when attempting any data
modification outside of the system tablespace. Only the system rollback segment can
be online in a clone database.
Action: Create one or more private/public segment(s), shutdown and then startup
again. May need to modify the INIT.ORA parameter rollback_segments to acquire
private rollback segment. If this is a clone database being used for tablspace point in
time recovery then this operation is not allowed. If the non-system tablespace has
AUTO segment space management, then create an undo tablespace.
60-6 Error Messages
ORA-01553: MAXEXTENTS must be no smaller than the string extents currently

allocated
Cause: The number of extents allocated is greater than the MAXEXTENTS specified.
Action: Specify a larger MAXEXTENTS value.
ORA-01554: transaction concurrency limit reached reason:string params:string,
string
Cause: Too many concurrent transactions
Action: Shutdown the system, modify the INIT.ORA parameters transactions,
rollback_segments or rollback_segments_required, then startup again.
ORA-01555: snapshot too old: rollback segment number string with name "string"
too small
Cause: rollback records needed by a reader for consistent read are overwritten by
other writers
Action: If in Automatic Undo Management mode, increase undo_retention setting.
Otherwise, use larger rollback segments
ORA-01556: MINEXTENTS for rollback segment must be greater than 1
Cause: Specified MINEXTENTS of less than 2 for rollback segment
Action: Specify larger MINEXTENTS
ORA-01557: rollback segment extents must be at least string blocks
Cause: Specified extent of less than minimum size for rollback segment
Action: Specify larger extents
ORA-01558: out of transaction ID's in rollback segment string
Cause: All the available transaction id's have been used
Action: Shutdown the instance and restart using other rollback segment(s), then drop
the rollback segment that has no more transaction id's.
ORA-01559: MAXEXTENTS for rollback segment must be greater than 1
Cause: Specified MAXEXTENTS of less than 2 for rollback segment
Action: Specify larger MAXEXTENTS
ORA-01560: LIKE pattern contains partial or illegal character
Cause: like pattern is not formed correctly
Action: make sure like pattern is specified correctly
ORA-01561: failed to remove all objects in the tablespace specified
Cause: Failed to remove all objects when dropping a tablespace
Action: Retry the drop tablespace until all objects are dropped
ORA-01562: failed to extend rollback segment number string
Cause: Failure occurred when trying to extend rollback segment
Action: This is normally followed by another error message that caused the failure.
You may take the rollback segment offline to perform maintainence. Use the alter
rollback segment offline command to take the rollback segment offline.
ORA-01563: rollback segment is PUBLIC, need to use the keyword PUBLIC
Cause: Did not use the keyword PUBLIC to identified public rollback segment
ORA-01500 to ORA-02098 60-7
Action: Use the keyword PUBLIC when identifying public rollback segment
ORA-01564: rollback segment is not PUBLIC
Cause: The rollback segment segment identified is not public
Action: Do not use the keyword PUBLIC when identifying private rollback segment
ORA-01565: error in 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 ALTER DATABASE
Cause: The list of files supplied to the command contained at least one duplicate.
Action: Remove the duplicate file specification and retry.
ORA-01567: dropping log string would leave less than 2 log files for instance string
(thread string)
Cause: Dropping all the logs specified would leave fewer than the required two log
files per enabled thread.
Action: Either drop fewer logs or disable the thread before deleting the logs. It may be
possible to clear the log rather than drop it.
ORA-01568: cannot set space quota on PUBLIC
Cause: Trying to set space quota on a tablespace for PUBLIC.
Action: If trying to grant system-wide or tablespace-wide space priviledges to all
users, use GRANT RESOURCE [ON tablespace] TO PUBLIC.
ORA-01569: data file too small for system dictionary tables
Cause: The datafile specified during creation of the database is too small to hold the
system dictionary tables.
Action: Recreate the database by specifying a larger file or more files.
ORA-01570: MINEXTENTS must be no larger than the string extents currently
allocated
Cause: The number of extents allocated is smaller than the MINEXTENTS specified.
Action: Specify a smaller MINEXTENTS value.
ORA-01571: redo version string incompatible with ORACLE version string
Cause: This software version can not read the current redo logs, and either crash
recovery is required or there are offline database files that need media recovery. If a
file name is listed then it needs media recovery.
Action: Shutdown and startup using the compatible software. Do any required media
recovery, and open the database. Shutdown and then startup using current software.
If the file is going to be dropped then take it offline with the DROP option to skip this
check.
ORA-01572: rollback segment 'string' cannot be brought online, string extents
exceeded
Cause: The number of extents in the rollback segment exceeds the hard limit. It cannot
be brought online for writing.
Action: Drop and recreate the rollback segment.
60-8 Error Messages
ORA-01573: shutting down instance, no further change allowed

Cause: Some process tries to make changes while the db is being shutdown
Action: None
ORA-01574: maximum number of concurrent transactions exceeded
Cause: the limit on the number of concurrent transactions has been hit
Action: shutdown the system, increase the INIT.ORA parameter 'transactions' , and
then restart the system.
ORA-01575: timeout waiting for space management resource
Cause: failed to acquire necessary resource to do space management.
ORA-01576: The instance string is not enabled
Cause: The thread associated with instance is not enabled.
Action: Enable the thread associated with the instance using ALTER DATABASE
ENABLE INSTANCE command.
ORA-01577: cannot add log file 'string' - file 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.
ORA-01578: ORACLE data block corrupted (file # string, block # string)
Cause: The data block indicated was corrupt. This was a physical corruption, also
called a media corruption. The cause is unknown but is most likely external to the
database. If ORA-26040 is also signaled, the corruption is due to NOLOGGING or
UNRECOVERABLE operations.
Action: The general method to repair a media corrupt block is to restore a backup and
recover the backup. For databases in ARCHIVELOG mode, use block media recovery
or media recovery. In some situations, you can also drop the segment and re-create it.
For example, you can drop an index and re-create the index.
ORA-01579: write error occurred during recovery
Cause: A write error occurred during recovery
Action: Consult trace files for the nature of the write error, and correct error.
ORA-01580: error creating control backup file string
Cause: An operating system error occurred while attempting to create a control file
backup.
Action: Check the error stack for more detailed information
ORA-01581: attempt to use rollback segment (string) new extent (string) which is
being allocated
Cause: Undo generated to extend a rollback segment run out of current undo block
space and is attempting to write into the new extent which has not been completely
allocated.
Action: The rollback segment extending will be rollbacked by the system, no more
extension will be possible untill the next extent is freed up by rolling back or
committing other transactions.
ORA-01500 to ORA-02098 60-9
ORA-01582: unable to open control file for backup

Cause: An operating system error occurred while attempting to open a control file for
backup.
ORA-01583: unable to get block size of control file to be backed up
Cause: An operating system error occurred while attempting to get the block size of a
control file for backup.
ORA-01584: unable to get file size of control file to be backed up
Cause: An operating system error occurred while attempting to get the file size of a
control file for backup.
ORA-01585: error identifying backup file string
Cause: An operating system error occurred when attempting to identify the file to be
used for control file backup.
ORA-01586: database must be mounted EXCLUSIVE and not open for this
operation
Cause: Attempting to DROP DATABASE when the database is not mounted
EXCLUSIVE.
Action: Mount the database in EXCLUSIVE mode.
ORA-01587: error during control file backup file copy
ORA-01588: must use RESETLOGS option for database open
Cause: An earlier attempt to open the database with the RESETLOGS option did not
complete, or recovery was done with a control file backup, or a FLASHBACK
DATABASE was done.
Action: Use the RESETLOGS option when opening the database.
ORA-01589: must use RESETLOGS or NORESETLOGS option for database open
Cause: Either incomplete or backup control file recovery has been 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: number of segment free list (string) exceeds maximum of string
Cause: storage parameter FREELIST GROUPS is too large.
Action: Reduce storage parameters FREELIST GROUPS
ORA-01591: lock held by in-doubt distributed transaction string
Cause: Trying to access resource that is locked by a dead two-phase commit
transaction that is in prepared state.
Action: DBA should query the pending_trans$ and related tables, and attempt to
repair network connection(s) to coordinator and commit point. If timely repair is not
possible, DBA should contact DBA at commit point if known or end user for correct
outcome, or use heuristic default if given to issue a heuristic commit or abort
command to finalize the local portion of the distributed transaction.
ORA-01592: error converting Version 7 rollback segment (string) to Oracle 8 format

Cause: Look at the accompanying internal error; Version 7 database may not have
shutdown cleanly.
Action: Investigate the internal error; may have to reload the Version 7 Investigate the
internal error; may have to reload the Version 7 database (from backup) and
shutdown the database cleanly.
ORA-01593: rollback segment optimal size (string blks) is smaller than the
computed initial size (string blks)
Cause: Specified OPTIMAL size is smaller than the cumulative size of the initial
extents during create rollback segment.
Action: Specify a larger OPTIMAL size.
ORA-01594: attempt to wrap into rollback segment (string) extent (string) which is
being freed
Cause: Undo generated to free a rollback segment extent is attempting to write into
the same extent due to small extents and/or too many extents to free
Action: The rollback segment shrinking will be rollbacked by the system; increase the
optimal size of the rollback segment.
ORA-01595: error freeing extent (string) of rollback segment (string))
Cause: Some error occurred while freeing inactive rollback segment extents.
Action: Investigate the accompanying error.
ORA-01596: cannot specify system in string parameter
Cause: The system rollback segment is specified in the INIT.ORA parameter referred
to in the error message
Action: change the INIT.ORA parameter
ORA-01597: cannot alter system rollback segment online or offline
Cause: Tried to online or offline the system rollback segment
Action: None
ORA-01598: rollback segment 'string' is not online
Cause: Could have been taken offline before by DBA or cleaned up by SMON.
Action: Check the status of rollback segment in undo$ or dba_rollback_segs to make
sure the rollback segment is actually online.
ORA-01599: failed to acquire rollback segment (string), cache space is full
Cause: the amount statically allocated is not enough based on max_rollback_segments
parameter.
Action: For now take another rollback segment offline or increase the parameter
max_rollback_segments
ORA-01600: at most one "string" in clause "string" of string
Cause: The INIT.ORA parameter was mis-specified.
Action: Correct the INIT.ORA parameter and restart the instance.
ORA-01601: illegal bucket size in clause "string" of string
Cause: The bucket size was invalid for this parameter.
ORA-01500 to ORA-02098 60-11
ORA-01603: illegal grouping size in clause "string" of string

Cause: The grouping size was invalid for this parameter.
ORA-01604: illegal number range in clause "string" of string
Cause: The number range was invalid for this parameter.
ORA-01605: missing numbers in clause "string" of string
Cause: The numbers were missing for this parameter.
ORA-01606: parameter not identical to that of another mounted instance
Cause: A parameter was different on two instances.
Action: Modify the initialization parameter and restart.
ORA-01607: cannot add logfile to the specified instance
Cause: The limit on the number of instances supported by the control file has been
reached.
Action: Use an instance name supported by the control file, or resize the thread record
and/or checkpoint progress record secions of the control file.
ORA-01608: cannot bring rollback segment 'string' online, its status is (string)
Cause: Could have been brought online before by DBA or left as a result of process
crash.
Action: Check the status of rollback segment in undo$ or dba_rollback_segs
ORA-01609: log string is the current log for thread string - cannot drop members
Cause: A member of the current log for a thread cannot be dropped.
Action: If the thread is opened, request a log switch by the instance that is using it. If
it is not open, disable the thread, manually archive the log, or clear it.
ORA-01610: recovery using the BACKUP CONTROLFILE option must be done
Cause: Either an earlier database recovery session specified BACKUP
CONTROLFILE, or the control file was recreated with the RESETLOGS option, or the
control file being used is a backup control file. After that only BACKUP
CONTROLFILE recovery is allowed and it must be followed by a log reset at the next
database open.
Action: Perform recovery using the BACKUP CONTROFILE option.
ORA-01611: thread number string is invalid - must be between 1 and string
Cause: A thread number in a command is greater than the number of threads
supported by the control file.
Action: Use a thread number that is valid, or resize the thread record and/or
checkpoint progress record sections of the control file.
ORA-01612: instance string (thread string) is already enabled
Cause: An attempt was made to enable a thread that is already enabled.
Action: Either use this thread or enable another thread.
ORA-01613: instance string (thread string) only has string logs - at least 2 logs
required to enable.
Cause: The thread cannot be enabled because it only has two online log files
associated with it.
Action: Add logs to the thread or pick another thread to enable
ORA-01614: instance string (thread string) is busy - cannot enable
Cause: The mount enqueue for the thread could not be acquired when attempting to
enable the thread. This probably means that another process has already started
enabling this thread.
Action: Wait and try again, or find another thread to enable.
ORA-01615: instance string (thread string) is mounted - cannot disable
Cause: Some instance, possibly this one, has allocated the thread for its use. The
thread can not be disabled while in use.
Action: Shut the instance down cleany using the thread.
ORA-01616: instance string (thread string) is open - cannot disable
Cause: The thread is not closed. The last instance to use the thread died leaving the
thread open. A thread cannot be disabled until it is closed. It is still required for crash
or instance recovery.
Action: If the database is open, instance recovery should close the thread soon - wait a
few minutes. Otherwise open the database - crash recovery will close the thread.
ORA-01617: cannot mount: string is not a valid thread number
Cause: The INIT.ORA parameter "thread" is not between 1 and the number of threads
allowed by the control file.
Action: Shut down the instance, change the INIT.ORA parameter and startup, or
resize the thread record and/or checkpoint progress record sections of the control file.
ORA-01618: redo thread string is not enabled - cannot mount
Cause: The INIT.ORA parameter "thread" requests a thread that is not enabled. A
thread must be enabled before it can be mounted.
Action: Shutdown the instance, change the INIT.ORA parameter and startup
mounting a different thread. If the database is open in another instance then the
thread may be enabled.
ORA-01619: thread string is mounted by another instance
Cause: The INIT.ORA parameter "thread" requests a thread that has been mounted by
another instance. Only one instance may use a thread.
Action: Shutdown the instance, change the INIT.ORA parameter and startup
mounting a different thread.
ORA-01620: no public threads are available for mounting
Cause: The INIT.ORA parameter "thread" is zero, its default value. There are no
threads which have been publicly enabled, and not mounted.
Action: Shutdown the instance, change the INIT.ORA parameter to a thread which is
privately enabled and not mounted. If the database is open in another instance, then a
thread may be publicly enabled.
ORA-01500 to ORA-02098 60-13
ORA-01621: cannot rename member of current log if database is open

Cause: This is a rename command for a member of the current log for an open thread.
If the database is open anywhere, the log may be in use, so the rename cannot be
done.
Action: Wait until the log is not current, or mount the database exclusively.
ORA-01622: thread number must be specified - default not specific
Cause: The thread was not specified when adding a log, and the currently mounted
thread was chosen by default at mount time. Since the current thread was not
specified explicitly the user cannot know which thread the log will be added to.
Action: Explicitly specify the thread number either in the INIT.ORA parameter
"thread", or in the add command.
ORA-01623: log string is current log for instance string (thread string) - cannot drop
Cause: A thread's current log cannot be dropped even if the thread is closed. A
disabled thread usually does not have a current log, but a half completed disable may
need to be disabled again.
Action: If the database is not open then disable the thread. If the database is open and
an instance has the thread open, then the instance can be requested to switch logs. If
the database is closed the log can be archived or cleared to force a switch.
ORA-01624: log string needed for crash recovery of instance string (thread string)
Cause: A log cannot be dropped or cleared until the thread's checkpoint has advanced
out of the log.
Action: If the database is not open, then open it. Crash recovery will advance the
checkpoint. If the database is open force a global checkpoint. If the log is corrupted so
that the database cannot be opened, it may be necessary to do incomplete recovery
until cancel at this log.
ORA-01625: rollback segment 'string' does not belong to this instance
Cause: Trying to shrink or take a rollback segment offline that does not belong to this
instance.
Action: n/a
ORA-01626: rollback segment number 'string' cannot handle more transactions
Cause: Too many transactions in this segment.
Action: Choose a different rollback segment, or reduce the number of concurrent
transactions.
ORA-01627: rollback segment number 'string' is not online
Cause: Could have been taken offline before by DBA or cleaned up by SMON.
Action: Check the status of rollback segment in undo$ or dba_rollback_segs to make
sure the rollback segment is actually online.
ORA-01628: max # extents (string) reached for rollback segment string
Cause: An attempt was made to extend a rollback segment that was already at the
MAXEXTENTS value.
Action: If the value of the MAXEXTENTS storage parameter is less than the
maximum allowed by the system, raise this value.
ORA-01629: max # extents (string) reached saving undo for tablespace string
Cause: Save undo for the offline tablespace at max extents
Action: Check the storage parameters for the system tablespace. The tablespace needs
to be brought back online so the undo can be applied .
ORA-01630: max # extents (string) reached in temp segment in tablespace string
Cause: A temp segment tried to extend past max extents.
Action: If maxextents for the tablespace is less than the the system maximum, you can
raise that. Otherwise, raise pctincrease for the tablespace
ORA-01631: max # extents (string) reached in table string.string
Cause: A table tried to extend past maxextents
Action: If maxextents is less than the system maximum, raise it. Otherwise, you must
recreate with larger initial, next or pctincrease params
ORA-01632: max # extents (string) reached in index string.string
Cause: An index tried to extend past maxextents
Action: If maxextents is less than the system max, raise it. Otherwise, you must
recreate with larger initial, next or pctincrease params.
ORA-01633: Real Application Clusters Option needed for this operation
Cause: System doesn't have Real Application Clusters configured
Action: Obtain Real Application Clusters option
ORA-01634: rollback segment number 'string' is about to go offline
Cause: The rollback segment specified was marked to go offline by DBA.
Action: Bring the rollback segment online first.
ORA-01635: rollback segment #string specified not available
Cause: (same as 1545)
Action: (same as 1545)
ORA-01636: rollback segment 'string' is already online
Cause: The instance is trying to online an already online RS
Action: n/a
ORA-01637: rollback segment 'string' is being used by another instance (#string)
Cause: The instance is trying to online a RS already in use by another instance
Action: n/a
ORA-01638: parameter string does not allow ORACLE version string to mount
cluster database
Cause: The recovery compatible parameter is set too low to allow this software
version to mount in cluster database mode.
Action: Either use an earlier software release or advance the recovery_compatible
parameter. If this happens when no recovery_compatible parameter has been
specified then set it to the current software release.
ORA-01639: instance string has no thread assigned to it
Cause: There is no mapping from instance to thread for this instance in the control
file.
ORA-01500 to ORA-02098 60-15
Action: Make sure that this instance has a thread assigned to it by adding logfiles to
this instance or by starting the instance with an existing thread which will
automatically create a mapping.
ORA-01640: cannot make tablespace read-only with changes by in-doubt
transactions
Cause: An attempt was made to alter a tablespace read-only while there were changes
in the tablespace made by in-doubt distributed transactions. The in-doubt
transactions must commit or rollback to ensure that there is no undo for a tablespace
before it can be made read-only.
Action: Any in-doubt transactions that made changes to the tablespace must be
resolved.
ORA-01641: tablespace 'string' is not online - cannot add data file
Cause: Attempting to add a datafile to a tablespace that has been set to read-only or
offline.
Action: Make the tablespace online and read write then add the datafile.
ORA-01642: begin backup not needed for read-only tablespace 'string'
Cause: Attempting to begin or end a backup for a tablespace that has been set to readonly.
Action: Take the backup without any begin or end commands. The files are not being
modified so the backup will be consistent.
ORA-01643: system tablespace can not be made read-only
Cause: Attempting to set the system tablespace to read-only. The system tablespace
must remain read write for database operation.
Action: Leave system tablespace read write.
ORA-01644: tablespace 'string' is already read-only
Cause: Attempting to make tablespace read-only that is already read-only.
Action: Leave tablespace read-only, or make read write then make read-only again.
ORA-01645: previous attempt to make read write is half complete
Cause: A failure while making the tablespace read write left it read only, but the
checkpoint was advanced. The tablespace will not be useable after a resetlogs if its
files are offline.
Action: Repeat the command to make the tablespace read write.
ORA-01646: tablespace 'string' is not read-only - cannot make read write
Cause: Attempting to make a tablespace read write that is not read-only. It may be
either online or offline.
Action: Leave tablespace read write.
ORA-01647: tablespace 'string' is read-only, cannot allocate space in it
Cause: Tried to allocate space in a read-only tablespace
Action: Create the object in another tablespace
ORA-01648: log string is the current log of disabled instance string (thread string)
Cause: An attempt to enable the thread failed after it was half completed. This log
was left as the current log even though the thread is still disabled. Since a log switch
cannot be done until the thread is enabled, the log can not be cleared or archived.
Action: Complete the thread enable by issuing the enable command again.
ORA-01649: operation not allowed with a backup control file
Cause: An attempt is being made to perform a command that does not make sense
when the control file is a restored backup.
Action: Wait until after the database has been opened and try again.
ORA-01650: unable to extend rollback segment string by string in tablespace string
Cause: Failed to allocate an extent of the required number of blocks for a rollback
segment in the tablespace.
Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more
files to the tablespace indicated.
ORA-01651: unable to extend save undo segment by string for tablespace string
Cause: Failed to allocate an extent of the required number of blocks for saving undo
entries for the indicated offline tablespace.
Action: Check the storage parameters for the SYSTEM tablespace. The tablespace
needs to be brought back online so the undo can be applied.
ORA-01652: unable to extend temp segment by string in tablespace string
Cause: Failed to allocate an extent of the required number of blocks for a temporary
segment in the tablespace indicated.
ORA-01653: unable to extend table string.string by string in tablespace string
Cause: Failed to allocate an extent of the required number of blocks for a table
ORA-01654: unable to extend index string.string by string in tablespace string
Cause: Failed to allocate an extent of the required number of blocks for an index
ORA-01655: unable to extend cluster string.string by string in tablespace string
Cause: Failed to allocate an extent of the required number of blocks for a cluster
segment in tablespace indicated.
ORA-01656: max # extents (string) reached in cluster string.string
Cause: A cluster tried to extend past maxextents
ORA-01657: invalid SHRINK option value
Cause: The specified value must be an integer.
Action: Choose an appropriate integer value.
ORA-01500 to ORA-02098 60-17
ORA-01658: unable to create INITIAL extent for segment in tablespace string

Cause: Failed to find sufficient contiguous space to allocate INITIAL extent for
segment being created.
Action: Use ALTER TABLESPACE ADD DATAFILE to add additional space to the
tablespace or retry with a smaller value for INITIAL
ORA-01659: unable to allocate MINEXTENTS beyond string in tablespace string
Cause: Failed to find sufficient contiguous space to allocate MINEXTENTS for the
segment being created.
Action: Use ALTER TABLESPACE ADD DATAFILE to add additional space to the
tablespace or retry with smaller value for MINEXTENTS, NEXT or PCTINCREASE
ORA-01660: tablespace 'string' is already permanent
Cause: Attempting to make tablespace permanent that is already permanent.
Action: Leave tablespace permanent.
ORA-01661: tablespace 'string' is already temporary
Cause: Attempting to make tablespace temporary that is already temporary.
Action: Leave tablespace permanent.
ORA-01662: tablespace 'string' is non-empty and cannot be made temporary
Cause: Tried to convert a non-empty tablespace to a temporary tablespace
Action: To drop all the objects in the tablespace.
ORA-01663: the contents of tablespace 'string' is constantly changing
Cause: The contents of the tablespace is always changing between PERMANENT and
TEMPORARY.
Action: To decide what the tablespace contents should be and stay with it.
ORA-01664: Transaction which has expanded the Sort Segment has aborted
Cause: Internal Error.
ORA-01665: control file is not a standby control file
Cause: Attempting 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 database.
ORA-01666: control file is for a standby database
Cause: Attempting to mount, recover, or open a standby database without the
appropriate command option to designate a standby database.
Action: Use the standby option or appropriate commands, or mount with the primary
control file.
ORA-01667: cannot add any more tablespaces: limit of string exceeded
Cause: There is no more room in the control file for adding tablespaces.
Action: Resize the control file or drop other tablespaces.
ORA-01668: standby database requires DROP option for offline of data file
Cause: Attempting to take a datafile offline in a standby database without specifying
the DROP option. Files that are offline in a standby database are not recovered, and
are likely to be unusable if the standby is activated. Note that specifying DROP does
not prevent bringing the file online later.
Action: Specify the DROP option or leave the file online.
ORA-01669: standby database control file not consistent
Cause: Attempting to activate a standby database with a control file that has not been
recovered to the same point as the data files. Most likely the control file was just
copied from the primary database and has not been used for recovery.
Action: Recover the standby database until all the files are consistent.
ORA-01670: new datafile string needed for standby database recovery
Cause: Standby database recovery noticed that a file was added to the primary
database, but is not available on the standby.
Action: Either copy the file from the primary database or do an ALTER DATABASE
CREATE DATAFILE command on the standby to create a file to recover.
ORA-01671: control file is a backup, cannot make a standby control file
Cause: The currently mounted control file is a backup control file, and attempting to
create a control file for a standby database.
Action: Complete any needed recovery and open the database with the resetlogs
option.
ORA-01672: control file may be missing files or have extra ones
Cause: Attempting to create a standby control file, but the control file was either
recently created via CREATE CONTROLFILE or an incomplete recovery has been
done. Thus the datafiles in the control file and the ones in the data dictionary may not
match.
Action: Open the database, then retry the operation.
ORA-01673: data file string has not been identified
Cause: This data file was not in the control file after an incomplete recovery or
CREATE CONTROLFILE. Since information from its header is needed for standby
database recovery, we can not create a standby control file.
Action: Find the file and bring it online. If desired it may be taken offline again. If you
intend to drop this file, then taking it offline with the DROP option will avoid this
error.
ORA-01674: data file string is an old incarnation rather than current file
Cause: Recovery encountered redo that indicates this file was dropped from the
database and another file was added using the same file number. This implies that a
CREATE CONTROLFILE command was given the old file which was dropped rather
than the latest file.
Action: Rebuild the control file using CREATE CONTROLFILE, and give the correct
file.
ORA-01675: max_commit_propagation_delay inconsistent with other instances
Cause: The max_commit_propagation_delay INIT.ORA parameter is inconsistent
with those in other instances.
Action: Make sure all instances have the same max_commit_propagation_delay.
ORA-01500 to ORA-02098 60-19
ORA-01676: standby file name conversion of 'string' exceeds maximum length of

string
Cause: When the given file name was converted to the name used for the standby
database, the converted name was bigger than the maximum allowed file name.
Action: Change initialization parameter DB_FILE_NAME_CONVERT or
LOG_FILE_NAME_CONVERT to convert to a valid file name.
ORA-01677: standby file name conversion parameters differ from other instance
Cause: The DB_FILE_NAME_CONVERT or LOG_FILE_NAME_CONVERT
initialization parameters were not the same as in other instances that already had the
database mounted.
Action: Change initialization parameters DB_FILE_NAME_CONVERT or
LOG_FILE_NAME_CONVERT to match other instances.
ORA-01678: parameter string must be pairs of pattern and replacement strings
Cause: The initialization parameter does not have even number of strings for its
value. The odd numbered strings are patterns to be found in file names. The even
numbered strings are used to replace the corresponding patterns when found in file
names.
Action: Specify even number of strings for the parameter, or omit the parameter.
ORA-01679: database is being opened
Cause: An attempt was made to activate a standby database when the database was
in the middle of being opened.
Action: Wait for database open to finish and retry the ACTIVATE command.
ORA-01680: unable to extend LOB segment by string in tablespace string
Cause: Failed to allocate an extent of the required number of blocks for a LOB
ORA-01681: max # extents (string) reached in LOB segment in tablespace string
Cause: A LOB segment tried to extend past max extents.
Action: If maxextents for the tablespace is less than the the system maximum, you can
raise that. Otherwise, raise pctincrease for the tablespace
ORA-01682: read-only DB cannot allocate temporary space in tablespace string
Cause: Temporary space (usually for sorting) could not be allocated in either main
storage or a tempfile. An attempt was made to allocate the space from the tablespace
named, but the database is opened read-only. The database open requires a sort work
space.
Action: Either allow sufficient workspace in main storage (SORT_AREA_SIZE
initialization parameter), or create a temporary tablespace before making the database
read-only. Use ALTER TABLESPACE ADD TEMPFILE statement to add temporary
files to the temporary tablespace.
ORA-01683: unable to extend index string.string partition string by string in
tablespace string
Cause: Failed to allocate an extent of the required number of blocks for index segment
in the tablespace indicated.
ORA-01684: max # extents (string) reached in table string.string partition string
Cause: A table tried to extend past maxextents
ORA-01685: max # extents (string) reached in index string.string partition string
Cause: An index tried to extend past maxextents
ORA-01686: max # files (string) reached for the tablespace string
Cause: The number of files for a given tablespace has reached its maximum value
Action: Resize existing files in the tablespace, or partition the objects among multiple
tablespaces, or move some objects to a different tablespace.
ORA-01687: specified logging attribute for tablespace 'string' is same as the existing
Cause: Attempting to change the tablespace default logging attribute (LOGGING or
NOLOGGING) to be the same as the existing logging attribute
Action: Change the specified logging attribute
ORA-01688: unable to extend table string.string partition string by string in
tablespace string
Cause: Failed to allocate an extent of the required number of blocks for table segment
ORA-01689: syntax error in clause "string" of string
Cause: There was a syntax in the INIT.ORA parameter.
Action: Fix the syntax error and restart the instance.
ORA-01690: sort area size too small
Cause: sort area size too small to fit two records in memory
Action: increase sort_area_size
ORA-01691: unable to extend lob segment string.string by string in tablespace
string
Cause: Failed to allocate an extent of the required number of blocks for LOB segment
ORA-01692: unable to extend lob segment string.string partition string by string in
tablespace string
Cause: Failed to allocate an extent of the required number of blocks for LOB segment
ORA-01500 to ORA-02098 60-21
ORA-01693: max # extents (string) reached in lob segment string.string

Cause: A LOB segment tried to extend past maxextents
ORA-01694: max # extents (string) reached in lob segment string.string partition
string
Cause: A LOB segment tried to extend past maxextents
ORA-01695: error converting rollback segment string to version 8.0.2
Cause: Version 8.0.1 database may not have shutdown cleanly
Action: May have to reload the 8.0.1 database and shutdown cleanly
ORA-01696: control file is not a clone control file
Cause: Attempting to mount, a database as a clone when it is already mounted by
another instance not as a clone or attempting to use a current control file for a clone.
Action: Mount without the clone option or use a backup control file and shutdown
the other instances before mounting as a clone.
ORA-01697: control file is for a clone database
Cause: Attempting to mount a clone database without the appropriate command
option to designate a clone database.
Action: Use the clone option or appropriate commands, or mount with the primary
control file.
ORA-01698: a clone database may only have SYSTEM rollback segment online
Cause: Attempting to online a rollback segment in a clone database.
Action: Do not use this command.
ORA-01699: tablespace 'string' is being imported for point in time recovery
Cause: Attempting to online a tablespace or begin another point in time import while
a point in time import is already in progress
Action: Wait until the import complets
ORA-01700: duplicate username in list
ORA-01701: a cluster is not appropriate here
ORA-01702: a view is not appropriate here
Cause: Among other possible causes, this message will be produced if an attempt was
made to define an Editioning View over a view.
Action: An Editioning View may only be created over a base table.
ORA-01703: missing SYNONYM keyword
ORA-01704: string literal too long
Cause: The string literal is longer than 4000 characters.
Action: Use a string literal of at most 4000 characters. Longer values may only be
entered using bind variables.
ORA-01705: an outer join cannot be specified on a correlation column

ORA-01706: user function result value was too large
ORA-01707: missing LIST keyword
ORA-01708: ACCESS or SESSION expected
ORA-01709: program does not exist
ORA-01710: missing OF keyword
ORA-01711: duplicate privilege listed
ORA-01712: you cannot grant a privilege which you do not have
ORA-01713: GRANT OPTION does not exist for that privilege
ORA-01714: error in execution of user function
ORA-01715: UNIQUE may not be used with a cluster index
Cause: An attempt was made to create a cluster index with the UNIQUE attribute.
Action: Remove UNIQUE from the CREATE INDEX statement.
ORA-01716: NOSORT may not be used with a cluster index
Cause: An attempt was made to create a cluster index using the NOSORT option.
Action: Remove NOSORT from the CREATE INDEX statement.
ORA-01717: seccta: invalid access mode token passed
ORA-01718: BY ACCESS | SESSION clause not allowed for NOAUDIT
Cause: Attempt to specify BY ACCESS | SESSION in a NOAUDIT statement.
Action: Remove BY ACCESS | SESSION.
ORA-01719: outer join operator (+) not allowed in operand of OR or IN
Cause: An outer join appears in an or clause.
Action: If A and B are predicates, to get the effect of (A(+) or B), try (select where
(A(+) and not B)) union all (select where (B)).
ORA-01720: grant option does not exist for 'string.string'
Cause: A grant was being performed on a view or a view was being replaced and the
grant option was not present for an underlying object.
Action: Obtain the grant option on all underlying objects of the view or revoke
existing grants on the view.
ORA-01721: USERENV(COMMITSCN) invoked more than once in a transaction
Cause: The USERENV('COMMITSCN') function can only be used once in a
transaction.
Action: Re-write the transactioin to use USERENV('COMMITSCN') only once
ORA-01722: invalid number
Cause: The specified number was invalid.
Action: Specify a valid number.
ORA-01500 to ORA-02098 60-23
ORA-01723: zero-length columns are not allowed

Cause: Columns with zero length were not allowed.
Action: Correct the use of the column.
ORA-01724: floating point precision is out of range (1 to 126)
Cause: The specified number had an invalid range.
Action: Use a floating point precision that is in the correct precision.
ORA-01725: USERENV('COMMITSCN') not allowed here
Cause: The function USERENV('COMMITSCN') is only allowed as a top-level
expression in the VALUES clause of an INSERT statement, and on the right-hand side
of an assignment in an UPDATE statement.
Action: Correct the use of the function.
ORA-01726: a table is not appropriate here
ORA-01727: numeric precision specifier is out of range (1 to 38)
ORA-01728: numeric scale specifier is out of range (-84 to 127)
ORA-01729: database link name expected
ORA-01730: invalid number of column names specified
ORA-01731: circular view definition encountered
ORA-01732: data manipulation operation not legal on this view
ORA-01733: virtual column not allowed here
ORA-01734: illegal parameters - EXTENT MIN higher than EXTENT MAX
Cause: A wrong value is specified for the parameter.
Action: Correct the parameter and reissue the statement.
ORA-01735: invalid ALTER TABLE option
ORA-01736: [NOT] SUCCESSFUL expected
ORA-01737: valid modes: [ROW] SHARE, [[SHARE] ROW] EXCLUSIVE, SHARE
UPDATE
ORA-01738: missing IN keyword
ORA-01739: missing MODE keyword
ORA-01740: missing double quote in identifier
ORA-01741: illegal zero-length identifier
ORA-01742: comment not terminated properly
Cause: The indicated comment or hint begun with the /* token did not have the
terminating */.
Action: Properly terminate the comment or hint with a */.
ORA-01743: only pure functions can be indexed

Cause: The indexed function uses SYSDATE or the user environment.
Action: PL/SQL functions must be pure (RNDS, RNPS, WNDS, WNPS). SQL
expressions must not use SYSDATE, USER, USERENV(), or anything else dependent
on the session state. NLS-dependent functions are OK.
ORA-01744: inappropriate INTO
ORA-01745: invalid host/bind variable name
ORA-01746: indicator variable not permitted here
ORA-01747: invalid user.table.column, table.column, or column specification
ORA-01748: only simple column names allowed here
ORA-01749: you may not GRANT/REVOKE privileges to/from yourself
ORA-01750: UPDATE/REFERENCES may only be REVOKEd from the whole table,
not by column
ORA-01751: Invalid dump undo option
Cause: An invalid option is specified in the ALTER DUMP UNDO command.
Action: Correct and reissue the command.
ORA-01752: cannot delete from view without exactly one key-preserved table
Cause: The deleted table had - no key-preserved tables, - more than one keypreserved table, or - the key-preserved table was an unmerged view.
Action: Redefine the view or delete it from the underlying base tables.
ORA-01753: column definition incompatible with clustered column definition
ORA-01754: a table may contain only one column of type LONG
Cause: An attempt was made to add a LONG column to a table which already had a
LONG column. Note that even if the LONG column currently in the table has already
been marked unused, another LONG column may not be added until the unused
columns are dropped.
Action: Remove the LONG column currently in the table by using the ALTER TABLE
command.
ORA-01755: Must specify an extent number or block number
Cause: Expecting an extent or block number but something else was specified.
Action: Correct the error and reissue the command.
ORA-01756: quoted string not properly terminated
ORA-01757: Must specify an object number
Cause: Expecting an object number but something else was specified.
ORA-01758: table must be empty to add mandatory (NOT NULL) column
ORA-01759: user function is incorrectly defined
ORA-01500 to ORA-02098 60-25
ORA-01760: illegal argument for function

ORA-01761: DML operation does not map to a unique table in the join
Cause: The primary table is the base table against which the update, insert or delete
operation is finally being done. For delete either there is no primary table in the join
query or there is more than one. For update or insert the columns specified map to
more than one base table.
Action: Change the join specification.
ORA-01762: vopdrv: view query block not in FROM
ORA-01763: update or delete involves outer joined table
Cause: For deletes, the table being deleted from is outer joined to some other table.
For updates, either the table being updated is outer- joined to some other table, or
some table reachable from the primary table is being outer joined to a table not
reachable from the primary table.
ORA-01764: new update value of join is not guaranteed to be unique
Cause: A row of a join query table is being updated using a row of a table that is not
guaranteed to have exactly one value for the row being updated.
ORA-01765: specifying owner's name of the table is not allowed
Cause: An attempt was made to rename the object with dotted object name.
Action: Do not specify username.tablename in query for table name.
ORA-01766: dictionary table not allowed in this context
ORA-01767: UPDATE ... SET expression must be a subquery
ORA-01768: number string too long
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: CLUSTER option not allowed in CREATE CLUSTER command
ORA-01771: illegal option for a clustered table
Cause: During a CREATE or ALTER of a clustered table, the user attempted to enter
one or more of the following options: INITRANS, MAXTRANS, PCTFREE,
PCTUSED, STORAGE, TABLESPACE. These options may only be specified for the
cluster itself.
Action: Remove the illegal option(s).
ORA-01772: Must specify a value for LEVEL
Cause: Expecting the value of LEVEL but something else was specified.
ORA-01773: may not specify column datatypes in this CREATE TABLE
ORA-01774: Dump undo 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.
ORA-01775: looping chain of synonyms
ORA-01776: cannot modify more than one base table through a join view
Cause: Columns belonging to more than one underlying table were either inserted
into or updated.
Action: Phrase the statement as two or more separate statements.
ORA-01777: WITH GRANT OPTION not allowed in this system
ORA-01778: maximum subquery nesting level exceeded
ORA-01779: cannot modify a column which maps to a non key-preserved table
Cause: An attempt was made to insert or update columns of a join view which map to
a non-key-preserved table.
Action: Modify the underlying base tables directly.
ORA-01780: string literal required
ORA-01781: UNRECOVERABLE cannot be specified without AS SELECT
Cause: UNRECOVERABLE was specified in a CREATE TABLE statement without
also specifying a populating subquery with an AS clause.
Action: Do not specify UNRECOVERABLE.
ORA-01782: UNRECOVERABLE cannot be specified for a cluster or clustered table
Cause: A CREATE CLUSTER, or clustered CREATE TABLE statement specified
UNRECOVERABLE.
Action: Do not specify UNRECOVERABLE.
ORA-01783: only one RECOVERABLE or UNRECOVERABLE clause may 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: RECOVERABLE cannot be specified 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 being
archived, they will be overwritten and the object being created cannot be recovered
from a backup taken before the object was created.
Action: Do not specify RECOVERABLE, or restart the database with media recovery
enabled.
ORA-01785: ORDER BY item must be the number of a SELECT-list expression
ORA-01786: FOR UPDATE of this query expression is not allowed
ORA-01500 to ORA-02098 60-27
ORA-01787: only one clause allowed per query block

ORA-01788: CONNECT BY clause required in this query block
ORA-01789: query block has incorrect number of result columns
ORA-01790: expression must have same datatype as corresponding expression
ORA-01791: not a SELECTed expression
ORA-01792: 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 which pushes it over the maximum
allowable limit of 1000. Note that unused columns in the table are counted toward the
1000 column limit.
Action: If the error is a result of a CREATE command, then reduce the number of
columns in the command and resubmit. If the error is a result of an ALTER TABLE
command, then there are two options: 1) If the table contained unused columns,
remove them by executing ALTER TABLE DROP UNUSED COLUMNS before
adding new columns; 2) Reduce the number of columns in the command and
resubmit.
ORA-01793: maximum number of index columns is 32
ORA-01794: maximum number of cluster columns is 32
ORA-01795: maximum number of expressions in a list is 1000
Cause: Number of expressions in the query exceeded than 1000. Note that unused
column/expressions are also counted Maximum number of expressions that are
allowed are 1000.
Action: Reduce the number of expressions in the list and resubmit.
ORA-01796: this operator cannot be used with lists
ORA-01797: this operator must be followed by ANY or ALL
ORA-01798: missing EXCEPTION keyword
ORA-01799: a column may not be outer-joined to a subquery
Cause: expression(+) relop (subquery) is not allowed.
Action: Either remove the (+) or make a view out of the subquery. In V6 and before,
the (+) was just ignored in this case.
ORA-01800: a literal in the date format was too large to process
ORA-01801: date format is too long for internal buffer
ORA-01802: Julian date is out of range
ORA-01803: failure in getting date/time
ORA-01804: failure to initialize timezone information
Cause: The timezone information file was not properly read.
Action: Please contact Oracle Customer Support.
ORA-01805: possible error in date/time operation

Cause: The timezone files on client and server do not match. Operation can
potentially result in incorrect results based on local timezone file.
Action: Please ensure client and server timezone versions are same.
ORA-01810: format code appears twice
ORA-01811: Julian date precludes use of day of year
ORA-01812: year may only be specified once
ORA-01813: hour may only be specified once
ORA-01814: AM/PM conflicts with use of A.M./P.M.
ORA-01815: BC/AD conflicts with use of B.C./A.D.
ORA-01816: month may only be specified once
ORA-01817: day of week may only be specified once
ORA-01818: 'HH24' precludes use of meridian indicator
ORA-01819: signed year precludes use of BC/AD
ORA-01820: format code cannot appear in date input format
ORA-01821: date format not recognized
ORA-01822: era format code is not valid with this calendar
ORA-01830: date format picture ends before converting entire input string
ORA-01831: year conflicts with Julian date
ORA-01832: day of year conflicts with Julian date
ORA-01833: month conflicts with Julian date
ORA-01834: day of month conflicts with Julian date
ORA-01835: day of week conflicts with Julian date
ORA-01836: hour conflicts with seconds in day
ORA-01837: minutes of hour conflicts with seconds in day
ORA-01838: seconds of minute conflicts with seconds in day
ORA-01839: date not valid for month specified
ORA-01840: input value not long enough for date format
ORA-01841: (full) year must be between -4713 and +9999, and not be 0
Cause: Illegal year entered
Action: Input year in the specified range
ORA-01500 to ORA-02098 60-29
ORA-01842: quarter must be between 1 and 4

ORA-01843: not a valid month
ORA-01844: week of year must be between 1 and 52
ORA-01845: week of month must be between 1 and 5
ORA-01846: not a valid day of the week
ORA-01847: day of month must be between 1 and last day of month
ORA-01848: day of year must be between 1 and 365 (366 for leap year)
ORA-01849: hour must be between 1 and 12
ORA-01850: hour must be between 0 and 23
ORA-01851: minutes must be between 0 and 59
ORA-01852: seconds must be between 0 and 59
ORA-01853: seconds in day must be between 0 and 86399
ORA-01854: julian date must be between 1 and 5373484
Cause: An invalid Julian date was entered.
Action: Enter a valid Julian date between 1 and 5373484.
ORA-01855: AM/A.M. or PM/P.M. required
ORA-01856: BC/B.C. or AD/A.D. required
ORA-01857: not a valid time zone
ORA-01858: a non-numeric character was found where a numeric was expected
input data did not contain a number where a number was required by the format
model.
ORA-01859: a non-alphabetic character was found where an alphabetic was
expected
input data did not contain a letter where a letter was required by the format model.
ORA-01860: week of year must be between 1 and 53
ORA-01861: literal does not match format string
Cause: Literals in the input must be the same length as literals in the format string
(with the exception of leading whitespace). If the "FX" modifier has been toggled on,
the literal must match exactly, with no extra whitespace.
Action: Correct the format string to match the literal.
ORA-01862: the numeric value does not match the length of the format item
Cause: When the FX and FM format codes are specified for an input date, then the
number of digits must be exactly the number specified by the format code. For
example, 9 will not match the format specifier DD but 09 will.
Action: Correct the input date or turn off the FX or FM format specifier in the format
string.
ORA-01863: the year is not supported for the current calendar
Cause: The year is not supported for the current calendar.
Action: Please check the documentation to find out what years are supported for the
current calendar.
ORA-01864: the date is out of range for the current calendar
Cause: Your calendar doesn't extend to the specified date.
Action: Specify a date which is legal for this calendar.
ORA-01865: not a valid era
Cause: Era input does not match a known era.
Action: Provide a valid era on input.
ORA-01866: the datetime class is invalid
Action: Please contact Oracle Worldwide Support.
ORA-01867: the interval is invalid
Cause: The character string you specified is not a valid interval.
Action: Please specify a valid interval.
ORA-01868: the leading precision of the interval is too small
ORA-01869: reserved for future use
ORA-01870: the intervals or datetimes are not mutually comparable
Cause: The intervals or datetimes are not mutually comparable.
Action: Specify a pair of intervals or datetimes that are mutually comparable.
ORA-01871: the 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 smaller.
ORA-01872: reserved for future use
ORA-01873: the leading precision of the interval is too small
ORA-01500 to ORA-02098 60-31
ORA-01874: time zone hour must be between -12 and 14

Cause: The time zone hour specified was not in the valid range.
Action: Specify a time zone hour between -12 and 14.
ORA-01875: time zone minute must be between -59 and 59
Cause: The time zone minute specified was not in the valid range.
Action: Specify a time zone minute between -59 and 59.
ORA-01876: year must be at least -4713
Cause: The specified year was not in range.
Action: Specify a year that is greater than or equal to -4713.
ORA-01877: string is too long for internal buffer
ORA-01878: specified field not found in datetime or interval
Cause: The specified field was not found in the datetime or interval.
Action: Make sure that the specified field is in the datetime or interval.
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: the fractional seconds must be between 0 and 999999999
Cause: The specified fractional seconds were not in the valid range.
Action: Specify a value for fractional seconds between 0 and 999999999.
ORA-01881: timezone region ID is invalid
Cause: The region ID referenced an invalid region.
ORA-01882: timezone region not found
Cause: The specified region name was not found.
ORA-01883: overlap was disabled during a region transition
Cause: The region was changing state and the overlap flag was disabled.
Action: Please contact Oracle Customer Support.
ORA-01884: divisor is equal to zero
Cause: An attempt was made to divide by zero.
Action: Avoid zero divisor.
ORA-01885: public synonym collides with Oracle-supplied schema name
Cause: The public synonym was the same as the Oracle-supplied schema name.
Action: Use either a different synonym or a different schema name.
ORA-01890: NLS error detected
Cause: An NLS error was detected.
Action: Look for additional error messages and take appropriate action. If there are no
additional errors, call Oracle Worldwide Support.
ORA-01891: Datetime/Interval internal error
ORA-01898: too many precision specifiers
Cause: While trying to truncate or round dates, extra data was found in the date
format picture
Action: Check the syntax of the date format picture and retry.
ORA-01899: bad precision specifier
ORA-01900: LOGFILE keyword expected
Cause: keyword missing
Action: supply missing keyword
ORA-01901: ROLLBACK keyword expected
ORA-01902: SEGMENT keyword expected
ORA-01903: EVENTS keyword expected
ORA-01904: DATAFILE keyword expected
ORA-01905: STORAGE keyword expected
ORA-01906: BACKUP keyword expected
ORA-01907: TABLESPACE keyword expected
ORA-01908: EXISTS keyword expected
ORA-01500 to ORA-02098 60-33
ORA-01909: REUSE keyword expected

ORA-01910: TABLES keyword expected
ORA-01911: CONTENTS keyword expected
ORA-01912: ROW keyword expected
ORA-01913: EXCLUSIVE keyword expected
ORA-01914: invalid auditing option for sequence numbers
Cause: AUDIT or NOAUDIT on a sequence number specifies an auditing option that
is not legal for sequence numbers.
Action: The following options may not be used for sequence numbers and should be
removed: COMMENT, DELETE, INDEX, INSERT, LOCK, RENAME, UPDATE,
REFERENCES, EXECUTE
ORA-01915: invalid auditing option for views
Cause: AUDIT or NOAUDIT on a view specifies an auditing option that is not legal
for views.
Action: The following options may not be used for views and should be removed:
ALTER, INDEX, REFERENCES, EXECUTE
ORA-01916: keyword ONLINE, OFFLINE, RESIZE, AUTOEXTEND, END, DROP,
ENCRYPT, or DECRYPT expected
Cause: An expected keyword was not used for data file or the temp file clause.
Action: Use the correct syntax.
ORA-01917: user or role 'string' does not exist
Cause: There is not a user or role by that name.
Action: Re-specify the name.
ORA-01918: user 'string' does not exist
Cause: User does not exist in the system.
Action: Verify the user name is correct.
ORA-01919: role 'string' does not exist
Cause: Role by that name does not exist.
Action: Verify you are using the correct role name.
ORA-01920: user name 'string' conflicts with another user or role name
Cause: There is already a user or role with that name.
Action: Specify a different user name.
ORA-01921: role name 'string' conflicts with another user or role name
Cause: There is already a user or role with that name.
Action: Specify a different role name.
ORA-01922: CASCADE must be specified to drop 'string'
Cause: Cascade is required to remove this user from the system. The user own's object
which will need to be dropped.
Action: Specify cascade.
ORA-01923: CASCADE aborted, objects locked by another user
Cause: Cannot drop the user's objects; someone has them locked.
Action: Use the lock monitor to determine who has the objects locked.
ORA-01924: role 'string' not granted or does not exist
Cause: Either the role was not granted to the user, or the role did not exist.
Action: Create the role or grant the role to the user and retry the operation.
ORA-01925: maximum of string enabled roles exceeded
Cause: The INIT.ORA parameter "max_enabled_roles" has been exceeded.
Action: Increase max_enabled_roles and warm start the database.
ORA-01926: cannot GRANT to a role WITH GRANT OPTION
Cause: Role cannot have a privilege with the grant option.
Action: Perform the grant without the grant option.
ORA-01927: cannot REVOKE privileges you did not grant
Cause: You can only revoke privileges you granted.
Action: Don't revoke these privileges.
ORA-01928: GRANT option not granted for all privileges
Cause: In order to grant a privilege, you must first have the privilege with the grant
option.
Action: Obtain the privilege with the grant option and try again.
ORA-01929: no privileges to GRANT
Cause: "ALL" was specified but the user doesn't have any privileges with the grant
option.
Action: Don't grant privileges on that object.
ORA-01930: auditing the object is not supported
Cause: AUDIT or NOAUDIT was specified for an object that cannot be audited.
Action: Don't attempt to AUDIT the object.
ORA-01931: cannot grant string to a role
Cause: REFERENCES, INDEX, SYSDBA, SYSOPER or SYSASM privilege could not be
granted to a role.
ORA-01500 to ORA-02098 60-35
Action: Grant 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: Obtain the grant option and re-try.
ORA-01933: cannot create a stored object using privileges from a role
Cause: An attempt was made to create a stored object using privileges from a role.
Stored objects cannot use privileges from roles.
Action: Grant the privileges required to the user directly.
ORA-01934: circular role grant detected
Cause: Roles cannot be granted circularly. Also, a role cannot be granted to itself.
Action: Do not perform the grant.
ORA-01935: missing user or role name
Cause: A user or role name was expected.
Action: Specify a user or role name.
ORA-01936: cannot specify owner when creating users or roles
Cause: Users and roles do not have owners.
Action: Don't specify an owner.
ORA-01937: missing or invalid 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 "IDENTIFIED
EXTERNALLY".
Action: Specify one of the password clauses.
ORA-01939: only the ADMIN OPTION can be specified
Cause: System privileges and roles can only be granted with the admin option. The
grant option cannot be used with system privileges and roles. The delegate option
cannot be used with system privileges.
Action: Specify the admin option.
ORA-01940: cannot drop a user that is currently connected
Cause: Attempt was made to drop a user that is currently logged in.
Action: Make sure user is logged off, then repeat command.
ORA-01941: SEQUENCE keyword expected
ORA-01942: IDENTIFIED BY and EXTERNALLY cannot both be specified
Cause: A user cannot be specified to have and not have a password.
Action: Specify only one of the options.
ORA-01943: IDENTIFIED BY already specified

Cause: The identified clause has been given twice.
Action: Use only one identified by clause.
ORA-01944: IDENTIFIED EXTERNALLY already specified
Cause: The identified externaly clause has been given twice.
Action: Use only one identified clause.
ORA-01945: DEFAULT ROLE[S] already specified
Cause: The default roles clause has been given twice.
Action: Use only on default role clause.
ORA-01946: DEFAULT TABLESPACE already specified
Cause: The default tablespace clause has been given twice.
Action: Use only one default tablespace clause.
ORA-01947: TEMPORARY TABLESPACE already specified
Cause: The temporary tablespace clause has been given twice.
Action: Use only one temporary tablespace clause.
ORA-01948: identifier's name length (string) exceeds maximum (string)
Cause: A name has been specified that is too long. For example,
dbms_session.is_role_enabled() specifies a role name that is too long.
Action: Change the application or command to use a correct identifier.
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: User does not have privileges to allocate an extent in 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: Don't try to revoke a privilege which is not granted.
ORA-01952: system privileges not granted to 'string'
Cause: A system privilege you tried to revoke was not granted to the user.
Action: Make sure the privileges you are trying to revoke are granted.
ORA-01953: command no longer valid, see ALTER USER
Cause: The syntax for assigning quotas on tablespaces 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 not valid for CREATE USER
Cause: Default roles cannot be specified for create user.
Action: Grant and alter the user's default roles after creating the user.
ORA-01500 to ORA-02098 60-37
ORA-01955: DEFAULT ROLE 'string' not granted to user

Cause: The user being altered does not have the specified role granted directly to the
user. Note, sub-roles cannot be used in the default role clause.
Action: Grant the role to the user.
ORA-01956: invalid command when OS_ROLES are being used
Cause: This command cannot be used when the INIT.ORA parameter OS_ROLES is
TRUE.
Action: Grant the role to the user in the operating system.
ORA-01957: Keyword MIN or MAX expected, not found
ORA-01958: Must supply an integer for the LAYER option
ORA-01959: Must supply an integer for the OPCODE option
ORA-01960: Invalid dump logfile option
ORA-01961: Invalid dump option
ORA-01962: Must specify a file number or log sequence number
ORA-01963: Must specify a block number
ORA-01964: Must specify a time for the TIME option
ORA-01965: Must specify a PERIOD
ORA-01967: invalid option for CREATE CONTROLFILE
Cause: An invalid CREATE CONTROLFILE option is present.
Action: Specify only valid CREATE CONTROLFILE options.
ORA-01968: Only specify RESETLOGS or NORESETLOGS once
Cause: The keyword RESETLOGS or NORESETLOGS has appeared more than once
Action: Be sure to specify RESETLOGS or NORESETLOGS exactly once.
ORA-01969: You must specify RESETLOGS or NORESETLOGS
Cause: Missing a RESETLOGS or a NORESETLOGS
Action: Be sure to specify RESETLOGS or NORESETLOGS exactly once.
ORA-01970: You must specify a database name for CREATE CONTROLFILE
Cause: Missing a database name
Action: Retype CREATE CONTROLFILE command with the DATABASE keyword.
ORA-01971: Illegal ALTER TRACING option
ORA-01972: Must specify a string for ALTER TRACING ENABLE or DISABLE
ORA-01973: Missing change number
Cause: Keyword "CHANGE" found but change number not specified.
Action: Fix command line and resubmit
ORA-01974: Illegal archive option

Cause: Not a valid option to the "ALTER SYSTEM ARCHIVE" command
Action: n/a
ORA-01975: Illegal character in change number string
ORA-01976: Missing change number
ORA-01977: Missing thread number
Cause: Keyword "THREAD" found but thread number not specified.
ORA-01978: Missing sequence number
Cause: Keyword "SEQUENCE" found but sequence number not specified.
ORA-01979: missing or invalid password for role 'string'
Cause: An attempt was made to enable a role without giving the proper password.
Action: Use the IDENTIFIED BY clause in SET ROLE to specify the correct password.
ORA-01980: error during OS ROLE initialization
Cause: An OS error occurred while loading a users OS ROLES.
Action: Check the OS error.
ORA-01981: CASCADE CONSTRAINTS must be specified to perform this revoke
Cause: During this revoke some foreign key contraints will be removed. In order to
perform this automatically, CASCADE CONSTRAINTS must be specified.
Action: Remove the constraints or specify CASCADE CONSTRAINTS.
ORA-01982: invalid auditing option for tables
Cause: AUDIT or NOAUDIT on a table specifies an auditing option that is not legal
for tables.
Action: The following options may not be used for tables and should be removed:
REFERENCES, EXECUTE
ORA-01983: invalid auditing option for DEFAULT
Cause: AUDIT or NOAUDIT on a DEFAULT specifies an auditing option that is not
legal for DEFAULT.
Action: The following options may not be used for DEFAULT and should be
removed: REFERENCES
ORA-01984: invalid auditing option for procedures/packages/functions
Cause: AUDIT or NOAUDIT on a DEFAULT specifies an auditing option that is not
legal for procedures, packages, or functions.
Action: The following options may not be used for procedures, packages, and
functions and should be removed: all but EXECUTE
ORA-01985: cannot create user as LICENSE_MAX_USERS parameter exceeded
Cause: Maximum users in the database license limit exceeded.
Action: Increase license limit.
ORA-01500 to ORA-02098 60-39
ORA-01986: OPTIMIZER_GOAL is obsolete

Cause: An obsolete parameter, OPTIMIZER_GOAL, was referenced.
Action: Use the OPTIMIZER_MODE parameter.
ORA-01987: client os username is too long
Cause: A client's os username is too long for the os logon to succeed.
Action: Use a shorter os username.
ORA-01988: remote os logon is not allowed
Cause: Remote os login attempted when not allowed.
Action: Use a local client, or use the remote_os_authent system parameter to turn on
remote os logon.
ORA-01989: role 'string' not authorized by operating system
Cause: The os role does not exist, is not granted to you, or you did not provide the
correct password.
Action: Re-attempt the SET ROLE with a valid os role and password, if necessary.
ORA-01990: error opening password file 'string'
Cause: The password file either did not exist or was inaccessible.
Action: Ensure that the file exists and is accessible.
ORA-01991: invalid password file 'string'
ORA-01992: error closing password file 'string'
ORA-01993: error writing password file 'string'
ORA-01994: GRANT failed: password file missing or disabled
Cause: The operation failed either because the INIT.ORA parameter
REMOTE_LOGIN_PASSWORDFILE was set to NONE or else because the password
file was missing.
Action: Create the password file using the orapwd tool and set the INIT.ORA
parameter REMOTE_LOGIN_PASSWORDFILE to EXCLUSIVE.
ORA-01995: error reading password file 'string'
ORA-01996: GRANT failed: password file 'string' is full
ORA-01997: GRANT failed: user 'string' is identified externally
ORA-01998: REVOKE failed: user SYS always has SYSOPER and SYSDBA
ORA-01999: password file cannot be updated in SHARED mode
Cause: The operation failed because the INIT.ORA parameter
REMOTE_LOGIN_PASSWORDFILE was set to SHARED.
Action: Set the INIT.ORA parameter to EXCLUSIVE.
ORA-02000: missing string keyword
ORA-02001: user SYS is not permitted to create indexes with freelist groups
Cause: user tried to create an index while running with sys authorization.
Action: n/a
ORA-02002: error while writing to audit trail
ORA-02003: invalid USERENV parameter
ORA-02004: security violation
Cause: This error code is never returned to a user. It is used as a value for column,
audit_trail.returncode, to signal that a security violation occurred.
Action: None
ORA-02005: implicit (-1) length not valid for this bind or define datatype
ORA-02006: invalid packed decimal format string
ORA-02007: can't use ALLOCATE or DEALLOCATE options with REBUILD
Cause: Allocate or deallocate storage and rebuild index are not compatible.
Action: Choose one or the other.
ORA-02008: non-zero scale specified for nonnumeric column
ORA-02009: the size specified for a file must not be zero
Cause: A value of zero was specified in a SIZE or RESIZE clause of a file specification.
Action: Use correct syntax, or, if allowed, omit the SIZE or RESIZE clause.
ORA-02010: missing host connect string
ORA-02011: duplicate database link name
ORA-02012: missing USING keyword
ORA-02013: missing CONNECT keyword
ORA-02014: cannot select FOR UPDATE from view with DISTINCT, GROUP BY,
etc.
Cause: An attempt was made to select FOR UPDATE from a view which had not been
merged because the view used syntax (for example, DISTINCT or GROUP BY)
preventing the merge, or because of initialization file parameter settings.
Action: Determine the reason the view will not merge and, if possible, make changes
so that it can.
ORA-02015: cannot select FOR UPDATE from remote table
Cause: An attempt was made to select FOR UPDATE on a remote table (directly, or
via a view) that had abstract data type columns, and the view or select list contained
abstract data type columns or non-column items.
Action: To attempt a select FOR UPDATE, use a view or select list that consists only
of base columns from the remote table, none of which may be abstract data type
columns.
ORA-02016: cannot use a subquery in a START WITH on a remote database
ORA-02017: integer value required
ORA-02018: database link of same name has an open connection
ORA-01500 to ORA-02098 60-41
ORA-02019: connection description for remote database not found

ORA-02020: too many database links in use
Cause: The current session has exceeded the INIT.ORA open_links maximum.
Action: Increase the open_links limit, or free up 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 tablename@remotedbname ...".
Action: To alter the remote database structure, you must connect to the remote
database with the appropriate privileges.
ORA-02022: remote statement has unoptimized view with remote object
Cause: The local view is unoptimized and contains references to objects at the remote
database and the statement must be executed at the remote database.
Action: Create a similar view on the remote database and modify the violating view
in the SQL statement with the new view@remote.
ORA-02023: START WITH or CONNECT BY predicate cannot be evaluated by
remote data base
ORA-02024: database link not found
Cause: Database link to be dropped is not found in dictionary
Action: Correct the database link name
ORA-02025: all tables in the SQL statement must be at the remote database
Cause: The user's SQL statement references tables from multiple databases. The
remote database is not Oracle V7 or above, and can perform updates only if it can
reference all tables in the SQL statement.
Action: n/a
ORA-02026: missing LINK keyword
ORA-02027: multi-row UPDATE of LONG column is not supported
Cause: A bind variable with length greater than 4000 bytes is being used to update a
column, and the update statement updates more than one row.
Action: You may only update a single row with such a bind variable.
ORA-02028: fetching an exact number of rows is not supported by the server
Cause: The server does not support UPIALL, so the fetch of an exact number of rows
cannot be emulated on the user side.
Action: Connect to a valid server or do not use an exact fetch.
ORA-02029: missing FILE keyword
ORA-02030: can only select from fixed tables/views

Cause: An attempt is being made to perform an operation other than a retrieval from
a fixed table/view.
Action: You may only select rows from fixed tables/views.
ORA-02031: no ROWID for fixed tables or for external-organized tables
Cause: An attempt is being made to access rowid from a fixed table or from a
external-organized table.
Action: Do not access ROWID from a fixed table or from a external-organized table.
ORA-02032: clustered tables cannot be used before the cluster index is built
Cause: User attempted to perform a DML statement on a clustered table for which no
cluster index has yet been created.
Action: Create the cluster index.
ORA-02033: a cluster index for this cluster already exists
Cause: A cluster index already exists for the cluster.
Action: None
ORA-02034: speed bind not permitted
Cause: Speed bind not allowed with supplied bind variables. Trapped internally by
the system.
Action: None
ORA-02035: illegal bundled operation combination
Cause: User requested that the UPI bundled execution call perform an an illegal
combination of operations.
Action: See documentation for legal operation combinations.
ORA-02036: too many variables to describe with automatic cursor open
Cause: User requested that the UPI bundled execution call perform automatic cursor
open and close on a describe operation. There were too many select-list items or bind
variables to do this.
Action: open and close cursor explicitly
ORA-02037: uninitialized speed bind storage
Cause: User attempted a UPI bundled execution call containing a standalone execute
operation without first performing a UPI bundled execution call containing a bind
operation.
Action: perform a UPI bundled execution call with bind before performing a bundled
execution call with execute
ORA-02038: define is not allowed for array type
Cause: User attempted to define a select list variable of type "array". Arrays may only
serve as host bind variables.
Action: n/a
ORA-02039: bind by value is not allowed for array type
Cause: User attempted to bind an array host variable by value. Arrays may only be
bound by reference.
Action: n/a
ORA-01500 to ORA-02098 60-43
ORA-02040: remote database string does not support two-phase commit

Cause: the database was potentially updated but does not support prepare to commit
(as determined by its logon transaction traits). The transaction was rolled back.
Action: Do not attempt to update the remote database unless it is the only database
updated in one transaction.
ORA-02041: client database did not begin a transaction
ORA-02042: too many distributed transactions
Cause: the distributed transaction table was full because too many distributed
transactions were active.
Action: Run fewer transactions. If you are sure you don't have too many concurrent
distributed transactions, this indicates an internal error and support should be
notified. Instance shutdown/restart would be a work-around.
ORA-02043: must end current transaction before executing string
Cause: a transaction is in progress and one of the following commands commands is
issued: COMMIT FORCE, ROLLBACK FORCE, or ALTER SYSTEM ENABLE
DISTRIBUTED RECOVERY in single process mode.
Action: COMMIT or ROLLBACK the current transaction and resubmit command.
ORA-02044: transaction manager login denied: transaction in progress
Cause: a remote transaction manager tried to log in while a distributed transaction is
in progress.
Action: end the current transaction (this is a protocol error from a remote transaction
manager)
ORA-02045: too many local sessions participating in global transaction
Cause: too many sessions at this site for this transaction.
Action: use an existing link so another session need not be created.
ORA-02046: distributed transaction already begun
Cause: internal error or error in external transaction manager. A server session
received a begin_tran RPC before finishing with a previous distributed tran.
Action: n/a
ORA-02047: cannot join the distributed transaction in progress
Cause: Either a transaction is in progress against a remote database that does not fully
support two phase commit, and an update is attempted on another database, or
updates are pending and and an attempt is made to update a different database that
does not fully support two phase commit.
Action: complete the current transaction and then resubmit the update request.
ORA-02048: attempt to begin distributed transaction without logging on
Cause: client program must issue a distributed transaction login.
Action: contact support.
ORA-02049: timeout: distributed transaction waiting for lock
Cause: exceeded INIT.ORA distributed_lock_timeout seconds waiting for lock.
Action: treat as a deadlock

ORA-02050: transaction string rolled back, some remote DBs may be in-doubt
Cause: network or remote failure in 2PC.
Action: Notify operations; remote DBs will automatically re-sync when the failure is
repaired.
ORA-02051: another session or branch in same transaction failed or finalized
Cause: A session at the same site with the same global transaction ID failed. The
failure could also be caused by an application error if an attempt was made to update
the database while another tightly coupled transaction branch with the same global
transaction ID was finalized or aborted.
Action: No action necessary as the transaction will be automatically recovered. In the
case of an application error, make sure there are no more updates to the database
once the transaction manager has started two-phase commit for tightly coupled
distributed transaction.
ORA-02052: remote transaction failure at string
Cause: error in remote transaction at given DBLINK
Action: retry
ORA-02053: transaction string committed, some remote DBs may be in-doubt
Action: Notify operations; remote DBs will automatically re-sync when the failure is
repaired.
ORA-02054: transaction string in-doubt
Action: Notify operations; DBs will automatically re-sync when the failure is repaired.
Monitor pending_trans$ for final outcome.
ORA-02055: distributed update operation failed; rollback required
Cause: a failure during distributed update operation may not have rolled back all
effects of the operation. Since some sites may be inconsistent, the transaction must roll
back to a savepoint or entirely
Action: rollback to a savepoint or rollback transaction and resubmit
ORA-02056: 2PC: string: bad two-phase command number string from string
Cause: two-phase commit protocol error.
Action: recovery of transaction attempted. Monitor pending_trans$ table to ensure
correct resolution. Contact support.
ORA-02057: 2PC: string: bad two-phase recovery state number string from string
Cause: internal error in two-phase recovery protocol
ORA-02058: no prepared transaction found with ID string
Cause: no transaction with local_tran_id or global_tran_id found in the pending_trans
$ table in prepared state.
Action: check the pending_trans$ table.
ORA-01500 to ORA-02098 60-45
ORA-02059: ORA-2PC-CRASH-TEST-string in commit comment

Cause: This is a special comment used to test the two phase commit.
Action: Don't use this special comment (%s a number 1-10)
ORA-02060: select for update specified a join of distributed tables
Cause: tables in a join with the for update clause must reside at the same DB.
Action: n/a
ORA-02061: lock table specified list of distributed tables
Cause: tables in a lock table statement must reside at the same DB.
Action: issue multiple lock table commands.
ORA-02062: distributed recovery received DBID string, expected string
Cause: a database link at a coordinator no longer points to the expected database.
Link may have been redefined, or a different DB mounted.
Action: restore link definition or remote database.
ORA-02063: preceding stringstring from stringstring
Cause: an Oracle error was received from a remote database link.
Action: refer to the preceding error message(s)
ORA-02064: distributed operation not supported
Cause: One of the following unsupported operations was attempted: 1. array execute
of a remote update with a subquery that references a dblink, or 2. an update of a long
column with bind variable and an update of a second column with a subquery that
both references a dblink and a bind variable, or 3. a commit is issued in a coordinated
session from an RPC procedure call with OUT parameters or function call.
Action: simplify remote update statement
ORA-02065: illegal option for ALTER SYSTEM
Cause: The option specified for ALTER SYSTEM is not supported
Action: refer to the user manual for option supported
ORA-02066: missing or invalid DISPATCHERS text
Cause: A character string literal was expected, but not found, following ALTER
SYSTEM SET DISPATCHERS
Action: place the string literal containing the dispatcher's specification after ALTER
SYSTEM SET DISPATCHERS
ORA-02067: transaction or savepoint rollback required
Cause: A failure (typically a trigger or stored procedure with multiple remote
updates) occurred such that the all-or-nothing execution of a previous Oracle call
cannot be guaranteed.
Action: rollback to a previous savepoint or rollback the transaction and resubmit.
ORA-02068: following severe error from stringstring
Cause: A severe error (disconnect, fatal Oracle error) received from the indicated
database link. See following error text.
Action: Contact the remote system administrator.
ORA-02069: global_names parameter must be set to TRUE for this operation

Cause: A remote mapping of the statement is required but cannot be achieved
because global_names should be set to TRUE for it to be achieved
Action: Issue alter session set global_names = true if possible
ORA-02070: database stringstring does not support string in this context
Cause: The remote database does not support the named capability in the context in
which it is used.
Action: Simplify the SQL statement.
ORA-02071: error initializing capabilities for remote database string
Cause: Could not load a remote-specified capability table.
Action: Contact support for the remote SQL*Connect product.
ORA-02072: distributed database network protocol mismatch
Cause: This should never happen between different PRODUCTION releases of
ORACLE, but may happen between alpha and beta releases, for example.
Action: Upgrade the older release.
ORA-02073: sequence numbers not supported in remote updates
Cause: Sequence numbers may not be used in INSERTS, UPDATES, or DELETES on
remote tables.
Action: n/a
ORA-02074: cannot string in a distributed transaction
Cause: A commit or rollback was attempted from session other than the parent of a
distributed transaction.
Action: Only commit or rollback from the parent session.
ORA-02075: another instance changed state of transaction string
Cause: A commit force or rollback force was issued from a session in another
instance.
Action: Check if another Oracle instance is performing recovery of pending
transactions. Query DBA_2PC_PENDING to determine the new state of the
transaction.
ORA-02076: sequence not co-located with updated table or long column
Cause: all referenced sequences must be co-located with the table with the long
column.
Action: n/a
ORA-02077: selects of long columns must be from co-located tables
Cause: if a select returns long columns from multiple tables, all the tables must be colocated
Action: n/a
ORA-02078: invalid setting for ALTER SYSTEM FIXED_DATE
ORA-02079: cannot join a committing distributed transaction
Cause: Once a transaction branch is prepared, no more new transaction branches are
allowed to start, nor is the prepared transaction branch allowed to be joined.
ORA-01500 to ORA-02098 60-47
Action: Check the application code as this is an XA protocol violation.

ORA-02080: database link is in use
Cause: a transaction is active or a cursor is open on the database link given in the alter
session close database link link command.
Action: commit or rollback, and close all cursors
ORA-02081: database link is not open
Cause: dblink given is not currently open.
Action: n/a
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: a loopback database link needs a trailing qualifier, for example
MYDB.EXAMPLE.COM@INST1 - the '@INST1' is the qualifier
ORA-02083: database name has illegal character 'string'
Cause: supplied database name can contain only A-Z, 0-9, '_', '#', '$' '.' and '@'
characters.
Action: n/a
ORA-02084: database name is missing a component
Cause: supplied database name cannot contain a leading '.', trailing '.' or '@', or two '.'
or '@' in a row.
Action: n/a
ORA-02085: database link string connects to string
Cause: a database link connected to a database with a different name. The connection
is rejected.
Action: create a database link with the same name as the database it connects to, or set
global_names=false.
ORA-02086: database (link) name is too long
Cause: database/database link name can have at most 128 characters.
Action: n/a
ORA-02087: object locked by another process in same transaction
Cause: A database link is being used in the cluster database environment that loops
back to the same instance. One session is trying to convert a lock that was obtained by
the other session.
Action: Get the more restrictive lock first. For example, if session 1 gets a share lock
and session 2 gets an exclusive lock on the same object, get the exclusive lock first. Or,
simply use the same session to access the object.
ORA-02088: distributed database option not installed
Cause: Remote and distributed updates and transactions are a separately priced
option in ORACLE V7.
Action: n/a
ORA-02089: COMMIT is not allowed in a subordinate session

Cause: COMMIT was issued in a session that is not the two-phase commit global
coordinator.
Action: Issue commit at the global coordinator only.
ORA-02090: network error: attempted callback+passthru
Cause: internal error.
Action: n/a
ORA-02091: transaction rolled back
Cause: Also see error 2092. If the transaction is aborted at a remote site then you will
only see 2091; if aborted at host then you will see 2092 and 2091.
Action: Add rollback segment and retry the transaction.
ORA-02092: out of transaction table slots for distributed transaction
Cause: The transaction is assigned to the system rollback segment and is trying to get
into the PREPARED state, but the required number of non-PREPARED slots are not
available, hence the transaction is rolled back.
Action: Add a rollback segment and retry the transaction.
ORA-02093: TRANSACTIONS_PER_ROLLBACK_SEGMENT(string) more than
maximum possible(string)
Cause: Value of parameter specified is greater than allowed on this port.
Action: Use default or reduce it to less than max.
ORA-02094: replication option not installed
Cause: The replication option was not installed at this site. Updatable materialized
views, deferred RPCs, and other replication features were, therefore, unavailable.
Action: Install the replication option. The replication option is not part of the Oracle
Server product and must be purchased separately. Contact an Oracle Sales
representative if the replication option needs to be purchased.
ORA-02095: specified initialization parameter cannot be modified
Cause: The specified initialization parameter is not modifiable
Action: n/a
ORA-02096: specified initialization parameter is not modifiable with this option
Cause: Though the initialization parameter is modifiable, it cannot be modified using
the specified command.
Action: Check the DBA guide for information about under what scope the parameter
may be modified
ORA-02097: parameter cannot be modified because specified value is invalid
Cause: Though the initialization parameter is modifiable, the modified value is not
acceptable to the parameter.
Action: Check the DBA guide for range of acceptable values for this parameter.
ORA-02098: error parsing index-table reference (:I)
Cause: An incorrect index-table (:I) syntax was encountered.
Action: This syntax is for oracle internal use only.
ORA-01500 to ORA-02098 60-49
61
ORA-02100 to ORA-04099
ORA-02100: PCC: out of memory (i.e., could not allocate)
ORA-02101: PCC: inconsistent cursor cache (uce/cuc mismatch)
ORA-02102: PCC: inconsistent cursor cache (no cuc entry for this uce)
ORA-02103: PCC: inconsistent cursor cache (out-of-range cuc ref)
ORA-02104: PCC: inconsistent host cache (no cuc available)
ORA-02105: PCC: inconsistent cursor cache (no cuc entry in cache)
ORA-02106: PCC: inconsistent cursor cache (OraCursor nr is bad)
ORA-02107: PCC: this pgm too old for run-time library: please re-PCC it
ORA-02108: PCC: invalid descriptor passed to run-time library
ORA-02109: PCC: inconsistent host cache (out-of-range sit ref)
ORA-02110: PCC: inconsistent host cache (invalid sqi type)
ORA-02111: PCC: heap consistency error
ORA-02112: PCC: SELECT..INTO returns too many rows
ORA-02140: invalid tablespace name
Cause: An identifier does not follow ALTER TABLESPACE.
Action: Specify a tablespace name following ALTER TABLESPACE.
ORA-02141: invalid OFFLINE option
Cause: An option other than NORMAL or IMMEDIATE follows OFFLINE.
Action: The user must either specify no option following OFFLINE or one of the
options NORMAL or IMMEDIATE.
ORA-02142: missing or invalid ALTER TABLESPACE option
Cause: A valid option was not present.
Action: Use one of the valid options: add, rename, default, online, offline, read only,
read write, begin, end, no, force, retention guarantee and retention noguarantee.
ORA-02143: invalid STORAGE option
Cause: An option other than INITIAL, NEXT, MINEXTENTS, MAXEXTENTS, or
PCTINCREASE was specified in the STORAGE clause.
ORA-02100 to ORA-04099 61-1
Action: Specify only valid options.

ORA-02144: no option specified for ALTER CLUSTER
Cause: No ALTER CLUSTER options are specified.
Action: Specify one or more of the following options: pctfree, pctused, size, storage.
ORA-02145: missing STORAGE option
Cause: No STORAGE options were specified following STORAGE (
Action: Specify one or more STORAGE option between the parentheses.
ORA-02146: SHARED specified multiple times
Cause: The SHARED option was specified in a CREATE DATABASE statement
multiple times.
Action: Only specify the SHARED option once.
ORA-02147: conflicting SHARED/EXCLUSIVE options
Cause: Both 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 in a CREATE DATABASE statement
multiple times.
Action: Only specify the EXCLUSIVE option once.
ORA-02149: Specified partition does not exist
Cause: Partition not found for the object.
Action: Retry with correct partition name.
ORA-02150: invalid new tablespace name
Cause: The new tablespace name specified in ALTER TABLESPACE RENAME TO
statement was invalid.
Action: Retry with a valid new tablespace name.
ORA-02151: invalid tablespace name: string
Cause: Oracle cannot create a tablespace whose name starts with '_$deleted$'.
Action: Try a different tablespace name.
ORA-02152: Invalid ALTER TABLESPACE ... RENAME option
Cause: An option other than DATAFILE or TO follows by ALTER TABLESPACE ...
RENAME.
Action: The user must specify either DATAFILE or TO following ALTER
TABLESPACE ... RENAME.
ORA-02153: invalid VALUES password string
Cause: An encoded password string does not follow the VALUES clause.
Action: Place a proper encoded password string after the VALUES clause.
ORA-02154: a tablespace with the name 'string' is found
Cause: An attempt to rename a tablespace to a new name failed because the new
name is already used by some other tablespace.
61-2 Error Messages
Action: Retry with a different new name.

ORA-02155: invalid DEFAULT tablespace identifier
Cause: An identifier does not follow DEFAULT TABLESPACE.
Action: Place a tablespace name after DEFAULT TABLESPACE.
ORA-02156: invalid TEMPORARY tablespace identifier
Cause: An identifier does not follow TEMPORARY TABLESPACE.
Action: Place a tablespace name after 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.
ORA-02159: installed DLM does not support releasable locking mode
Cause: The parameter file specified gc_* parameters that allow locks to be release by
the LCK process when not in use. This mode requires additional support from the
DLM that is not available.
Action: Specify configuration parameters that do not require the additional function.
ORA-02160: index-organized table can not contain columns of type LONG
Cause: A column of type LONG defined for index-organized table.
Action: Do not use columns of type LONG in index-organized tables.
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 FREELIST GROUPS
Cause: A number does not follow FREELIST 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 for CREATE DATABASE
Cause: An invalid CREATE DATABASE option is present.
Action: Specify only valid CREATE DATABASE options.
ORA-02100 to ORA-04099 61-3
ORA-02166: ARCHIVELOG and NOARCHIVELOG specified

Cause: Both ARCHIVELOG and NOARCHIVELOG are specified in a CREATE
DATABASE statement.
Action: Specify at most one of these two options.
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 not allowed
Cause: The user attempted to specify the FREELISTS storage option. This option may
only be specified during create table or create index.
Action: Remove these options and retry the statement.
ORA-02170: FREELIST GROUPS storage option not allowed
Cause: The user attempted to specify the FREELIST GROUPS storage option. This
option may only be specified during create table and when allow_freelist_groups
INIT.ORA is specified.
Action: Remove this option and retry the statement or set the allow_freelist_groups
INIT.ORA parameter.
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 appropriate for a disable thread
Cause: The PUBLIC keyword was specified for a disable.
Action: Remove the keyword and resubmit.
ORA-02173: invalid option for DROP TABLESPACE
Cause: Either a token other than INCLUDING was found following the tablespace
name or some text was found following INCLUDING CONTENTS.
Action: Place nothing or only INCLUDING CONTENTS after the tablespace name.
ORA-02174: Missing required thread number
Cause: Must specify thread number after THREAD keyword
Action: n/a
ORA-02175: invalid rollback segment name
Cause: In the CREATE or DROP ROLLBACK SEGMENT statements, an identifier
was not found following ROLLBACK SEGMENT.
Action: Place the segment name following ROLLBACK SEGMENT.
ORA-02176: invalid option for CREATE ROLLBACK SEGMENT
Cause: An invalid option was specified in a CREATE ROLLBACK SEGMENT
statement.
Action: Specify one of the valid options: TABLESPACE and STORAGE.
61-4 Error Messages
ORA-02177: Missing required group number

Cause: Must specify group number after GROUP keyword
Action: n/a
ORA-02178: correct syntax is: SET TRANSACTION READ { ONLY | WRITE }
Cause: There is a syntax error in the user's statement.
Action: Correct the syntax as indicated.
ORA-02179: valid options: ISOLATION LEVEL { SERIALIZABLE | READ
COMMITTED }
ORA-02180: invalid option for CREATE TABLESPACE
Cause: An invalid option appeared.
Action: Specify one of the valid options: DATAFILE, DEFAULT STORAGE, ONLINE,
OFFLINE, FORCE, RETENTION.
ORA-02181: invalid option to ROLLBACK WORK
Cause: A token other than TO follows ROLLBACK [WORK].
Action: Place nothing or TO SAVEPOINT name after ROLLBACK [WORK].
ORA-02182: savepoint name expected
Cause: An identifier does not follow ROLLBACK [WORK] TO [SAVEPOINT].
Action: Place a savepoint name following TO [SAVEPOINT].
ORA-02183: valid options: ISOLATION_LEVEL { SERIALIZABLE | READ
COMMITTED }
ORA-02184: resource quotas are not allowed in REVOKE
Cause: In a revoke statement, a resource quota was specified.
Action: Specify resource privilege without the quota.
ORA-02185: a token other than WORK follows COMMIT
Cause: A token other than WORK follows COMMIT.
Action: Place either nothing or WORK after COMMIT.
ORA-02186: tablespace resource privilege may not appear with other privileges
Cause: An attempt was made to grant or revoke a resource quota in the same
statement in which other privileges are granted or revoked.
Action: Use a separate grant or revoke statement for the resource quota privilege.
ORA-02187: invalid quota specification
Cause: In a grant or revoke statement, the user attempted to grant a tablespace quota
above the upper limit.
Action: Grant a smaller tablespace quota.
ORA-02188: Cannot enable instance publicly
Cause: An attempt was made to publicly enable a thread associated with an instance.
ORA-02100 to ORA-04099 61-5
Action: Leave out the PUBLIC keyword.

ORA-02189: ON tablespace required
Cause: In a grant or revoke statement, the user specified a tablespace quota but did
not follow it with the ON tablespace clause.
Action: Specify the tablespace on which the quota is to be applied with the ON
tablespace clause.
ORA-02190: keyword TABLES expected
Cause: The keyword TABLES is expected following DROP CLUSTER name
INCLUDING.
Action: Place TABLES after INCLUDING.
ORA-02191: correct syntax is: SET TRANSACTION USE ROLLBACK SEGMENT
rbs
ORA-02192: PCTINCREASE not allowed for rollback segment storage clauses
Cause: pctincrease was specified in a create or alter rollback segment
Action: reissue statement without the pctincrease clause
ORA-02194: event specification syntax error string (minor error string) near 'string'
Cause: There is a syntax error in an event specification.
ORA-02195: Attempt to create string object in a string tablespace
Cause: The object type is inconsistent with a tablespace contents.
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: n/a
ORA-02197: file list already specified
Cause: In CREATE TABLESPACE, more than one DATAFILE/TEMPFILE clause was
specified.
Action: Merge 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 of ONLINE or OFFLINE.
ORA-02199: missing DATAFILE/TEMPFILE clause
Cause: A CREATE TABLESPACE statement has no DATAFILE/TEMPFILE clause.
Action: Specify a DATAFILE/TEMPFILE clause.
ORA-02200: WITH GRANT OPTION not allowed for PUBLIC
Cause: An attempt was made to GRANT to PUBLIC WITH GRANT OPTION.
61-6 Error Messages
Action: Remove the WITH GRANT OPTION clause.

ORA-02201: sequence not allowed here
Cause: An attempt was made to reference a sequence in a from-list.
Action: A sequence can only be referenced in a select-list.
ORA-02202: no more tables permitted in this cluster
Cause: An attempt was made to create a table in a cluster which already contains 32
tables.
Action: Up to 32 tables may be stored per cluster.
ORA-02203: INITIAL storage options not allowed
Cause: The user attempted to alter the INITIAL storage option of a table, cluster,
index, or rollback segment. These options may only be specified when the object is
created.
Action: Remove these options and retry the statement.
ORA-02204: ALTER, INDEX and EXECUTE 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 ALTER, INDEX, or EXECUTE
privileges on views.
ORA-02205: only SELECT and ALTER privileges are valid for sequences
Cause: An attempt was made to grant or revoke an invalid privilege on a sequence.
Action: Do not attempt to grant or revoke DELETE, INDEX, INSERT, UPDATE,
REFERENCES or EXECUTE privilege on sequences.
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.
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 options specified for ALTER TABLE
Cause: No ALTER TABLE option was specified.
Action: Specify at least one alter table option.
ORA-02100 to ORA-04099 61-7
ORA-02211: invalid value for PCTFREE or PCTUSED

Cause: The specified value 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: PCTFREE option specified more than once.
Action: Specify PCTFREE at most once.
ORA-02213: duplicate PCTUSED option specification
Cause: PCTUSED option specified more than once.
Action: Specify PCTUSED at most once.
ORA-02214: duplicate BACKUP option specification
Cause: The BACKUP option to ALTER TABLE is specified more than once.
Action: Specify the option at most once.
ORA-02215: duplicate tablespace name clause
Cause: There is more than one TABLESPACE clause in the CREATE TABLE, CREATE
INDEX, or CREATE ROLLBACK SEGMENT statement.
Action: Specify at most one TABLESPACE clause.
ORA-02216: tablespace name expected
Cause: A tablespace name was not present where required by the syntax for the
failing statement.
Action: Specify a tablespace name where required by the syntax.
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
ORA-02219: invalid NEXT storage option value
ORA-02220: invalid MINEXTENTS storage option value
Cause: The specified value must be a positive integer less than or equal to
MAXEXTENTS.
Action: Specify an appropriate value.
ORA-02221: invalid MAXEXTENTS storage option value
Cause: The specified value must be a positive integer greater than or equal to
MINEXTENTS.
61-8 Error Messages
ORA-02222: invalid PCTINCREASE storage option value

Cause: The specified value must be a positive integer.
ORA-02223: invalid OPTIMAL storage option value
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 EXECUTE privilege on tables.
ORA-02225: only EXECUTE and DEBUG privileges are 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 privilege besides EXECUTE or DEBUG
on procedures, functions or packages.
ORA-02226: invalid MAXEXTENTS value (max allowed: string)
Cause: The MAXEXTENTS specified is too large for the database block size. This
applies only to SYSTEM rollback segment.
Action: Specify a smaller value.
ORA-02227: invalid cluster name
Cause: A cluster name of the form [ identifier . ] identifier is expected but not present.
Action: Enter an appropriate cluster name.
ORA-02228: duplicate SIZE specification
Cause: The SIZE option is specified more than once.
Action: Specify the SIZE option at most once.
ORA-02229: invalid SIZE option value
Cause: The specified value must be an integer number of bytes.
ORA-02230: invalid ALTER CLUSTER option
Cause: An option other than PCTFREE, PCTUSED, INITRANS, MAXTRANS,
STORAGE, or SIZE is specified in an ALTER CLUSTER statement.
Action: Specify only legal options.
ORA-02231: missing or invalid option to ALTER DATABASE
Cause: An option other than ADD, DROP, RENAME, ARCHIVELOG,
NOARCHIVELOG, MOUNT, DISMOUNT, OPEN, or CLOSE is specified in the
statement.
ORA-02232: invalid MOUNT mode
Cause: A mode other than SHARED or EXCLUSIVE follows the MOUNT keyword in
an ALTER DATABASE statement.
Action: Specify either SHARED, EXCLUSIVE, or nothing following MOUNT.
ORA-02100 to ORA-04099 61-9
ORA-02233: invalid CLOSE mode

Cause: A mode other than NORMAL or IMMEDIATE follows the CLOSE keyword in
an ALTER DATABASE statement.
Action: Specify either NORMAL, IMMEDIATE, or nothing following CLOSE.
ORA-02234: changes to this table are already logged
Cause: the log table to be added is a duplicate of another
Action: Don't add this change log to the system; check that the replication product's
system tables are consistent
ORA-02235: this table logs changes to another table already
Cause: the table to be altered is already a change log for another table
Action: Don't log changes to the specified base table to this table; check that the
replication product's system tables are consistent
ORA-02236: invalid file name
Cause: A character string literal was not used in the filename list of a LOGFILE,
DATAFILE, or RENAME clause.
ORA-02237: invalid file size
Cause: A non-integer value was specified in the SIZE or RESIZE clause.
ORA-02238: filename lists have different numbers of files
Cause: In a RENAME clause in ALTER DATABASE or TABLESPACE, the the
number of existing filenames does not equal the number of new filenames.
Action: Make sure there is a new filename to correspond to each existing filename.
ORA-02239: there are objects which reference this sequence
Cause: the sequence to be dropped is still referenced
Action: Make sure the sequence name is correct, or drop the referencing constraint/
object
ORA-02240: invalid value for OBJNO or TABNO
Cause: A number does not follow either OBJNO or TABNO.
Action: Specify a number after OBJNO or TABNO.
ORA-02241: must of form EXTENTS (FILE n BLOCK n SIZE n, ...)
Cause: bad extent storage clause
Action: respecify
ORA-02242: no options specified for ALTER INDEX
Cause: No options specified.
Action: Specify at least one of REBUILD, INITRANS, MAXTRANS, or STORAGE.
ORA-02243: invalid ALTER INDEX or ALTER MATERIALIZED VIEW 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
MATERIALIZED VIEW statement.
ORA-02244: invalid ALTER ROLLBACK SEGMENT option

Cause: The STORAGE option is expected but not found.
Action: Specify the STORAGE option.
ORA-02245: invalid ROLLBACK SEGMENT name
Cause: An identifier was expected, but not found, following ALTER [PUBLIC]
ROLLBACK SEGMENT.
Action: Place a rollback segment name following SEGMENT.
ORA-02246: missing EVENTS text
Cause: A character string literal was expected, but not found, following ALTER
SESSION SET EVENTS.
Action: Place the string literal containing the events text after EVENTS.
ORA-02247: no option specified for ALTER SESSION
Cause: The option SET EVENTS was expected, but not found, following ALTER
SESSION.
Action: Place the SET EVENTS option after ALTER SESSION.
ORA-02248: invalid option for ALTER SESSION
Cause: Obvious.
Action: see SQL Language Manual for legal options.
ORA-02249: missing or invalid value for MAXLOGMEMBERS
Cause: A valid number does not follow MAXLOGMEMBERS. The value specified
must be between 1 and the port-specific maximum number of log file members.
Action: Specify a valid number after MAXLOGMEMBERS.
ORA-02250: missing or invalid constraint name
Cause: The constraint name is missing or invalid.
Action: Specify a valid identifier name for the constraint name.
ORA-02251: subquery not allowed here
Cause: Subquery is not allowed here in the statement.
Action: Remove the subquery from the statement.
ORA-02252: check constraint condition not properly ended
Cause: The specified search condition for the check constraint is not properly ended.
Action: End the condition properly.
ORA-02253: constraint specification not allowed here
Cause: Constraint specification is not allowed here in the statement.
Action: Remove the constraint specification from the statement.
ORA-02254: DEFAULT expression not allowed here
Cause: Default value expression is not allowed for the column here in the statement.
Action: Remove the default value expression from the statement.
ORA-02255: obsolete 7.1.5
Cause: Was that defaults must not conflict with not null constraints
ORA-02100 to ORA-04099 61-11
Action: n/a
ORA-02256: number of referencing columns must match referenced columns
Cause: The number of columns in the foreign-key referencing list is not equal to the
number of columns in the referenced list.
Action: Make sure that the referencing columns match the referenced columns.
ORA-02257: maximum number of columns exceeded
Cause: The number of columns in the key list exceeds the maximum number.
Action: Reduce the number columns in the list.
ORA-02258: duplicate or conflicting NULL and/or NOT NULL specifications
Cause: Self-evident.
Action: Remove the duplicate or conflicting specification.
ORA-02259: duplicate UNIQUE/PRIMARY KEY specifications
Action: Remove the duplicate specification.
ORA-02260: table can have only one primary key
Action: Remove the extra primary key.
ORA-02261: such unique or primary key already exists in the table
Action: Remove the extra key.
ORA-02262: ORA-string occurs while type-checking column default value
expression
Cause: New column datatype causes type-checking error for existing column default
value expression.
Action: Remove the default value expression or don't alter the column datatype.
ORA-02263: need to specify the datatype for this column
Cause: The required datatype for the column is missing.
Action: Specify the required datatype.
ORA-02264: name already used by an existing constraint
Cause: The specified constraint name has to be unique.
Action: Specify a unique constraint name for the constraint.
ORA-02265: cannot derive the datatype of the referencing column
Cause: The datatype of the referenced column is not defined as yet.
Action: Make sure that the datatype of the referenced column is defined before
referencing it.
ORA-02266: unique/primary keys in table referenced by enabled foreign keys
Cause: An attempt was made to truncate a table with unique or primary keys
referenced by foreign keys enabled in another table. Other operations not allowed are
dropping/truncating a partition of a partitioned table or an ALTER TABLE
EXCHANGE PARTITION.
Action: Before performing the above operations the table, disable the foreign key
constraints in other tables. You can see what constraints are referencing a table by
issuing the following command: SELECT * FROM USER_CONSTRAINTS WHERE
TABLE_NAME = "tabnam";
ORA-02267: column type incompatible with referenced column type
Cause: The datatype of the referencing column is incompatible with the
Action: Select a compatible datatype for the referencing column.
ORA-02268: referenced table does not have a primary key
Cause: The referenced table does not have a primary key.
Action: Specify explicitly the referenced table unique key.
ORA-02269: key column cannot be of LONG datatype
Action: Change the datatype of the column, or remove the column from the key.
ORA-02270: no matching unique or primary key for this column-list
Cause: A REFERENCES clause in a CREATE/ALTER TABLE statement gives a
column-list for which there is no matching unique or primary key constraint in the
referenced table.
Action: Find the correct column names using the ALL_CONS_COLUMNS catalog
view
ORA-02271: table does not have such constraint
Action: Make sure the specified constraint name is correct.
ORA-02272: constrained column cannot be of LONG datatype
Action: Change the datatype of the column, or remove the constraint on the column.
ORA-02273: this unique/primary key is referenced by some foreign keys
Action: Remove all references to the key before the key is to be dropped.
ORA-02274: duplicate referential constraint specifications
ORA-02275: such a referential constraint already exists in the table
Action: Remove the extra constraint.
ORA-02276: default value type incompatible with column type
Cause: The type of the evaluated default expression is incompatible with the datatype
of the column.
Action: Change the type of the column, or modify the default expression.
ORA-02277: invalid sequence name
Cause: The specified sequence name is not a valid identifier name.
ORA-02100 to ORA-04099 61-13
Action: Specify a valid identifier name for the sequence name.

ORA-02278: duplicate or conflicting MAXVALUE/NOMAXVALUE specifications
ORA-02279: duplicate or conflicting MINVALUE/NOMINVALUE specifications
ORA-02280: duplicate or conflicting CYCLE/NOCYCLE specifications
ORA-02281: duplicate or conflicting CACHE/NOCACHE specifications
ORA-02282: duplicate or conflicting ORDER/NOORDER specifications
ORA-02283: cannot alter starting sequence number
Action: Don't alter it.
ORA-02284: duplicate INCREMENT BY specifications
ORA-02285: duplicate START WITH specifications
ORA-02286: no options specified for ALTER SEQUENCE
Action: The statement is meaningless without any options.
ORA-02287: sequence number not allowed here
Cause: The specified sequence number (CURRVAL or NEXTVAL) is inappropriate
here in the statement.
Action: Remove the sequence number.
ORA-02288: invalid OPEN mode
Cause: A token other than RESETLOGS appears following ALTER DATABASE name
OPEN.
Action: Either nothing or RESETLOGS should be placed following OPEN.
ORA-02289: sequence does not exist
Cause: The specified sequence does not exist, or the user does not have the required
privilege to perform this operation.
Action: Make sure the sequence name is correct, and that you have the right to
perform the desired operation on this sequence.
ORA-02290: check constraint (string.string) violated
Cause: The values being inserted do not satisfy the named check constraint.
Action: do not insert values that violate the constraint.
ORA-02291: integrity constraint (string.string) violated - parent key not found
Cause: A foreign key value has no matching primary key value.
Action: Delete the foreign key or add a matching primary key.
ORA-02292: integrity constraint (string.string) violated - child record found
Cause: attempted to delete a parent key value that had a foreign key dependency.
Action: delete dependencies first then parent or disable constraint.
ORA-02293: cannot validate (string.string) - check constraint violated
Cause: an alter table operation tried to validate a check constraint to a populated table
that had nocomplying values.
Action: Obvious
ORA-02294: cannot enable (string.string) - constraint changed during validation
Cause: While one DDL statement was attempting to enable this constraint, another
DDL changed this same constraint.
Action: Try again, with only one DDL changing the constraint this time.
ORA-02295: found more than one enable/disable clause for constraint
Cause: a create or alter table specified more than one enable and/or disable clause for
a given constraint.
Action: only one enable or disable may be specified for a given constraint.
ORA-02296: cannot enable (string.string) - null values found
Cause: an alter table enable constraint failed because the table contains values that do
not satisfy the constraint.
Action: Obvious
ORA-02297: cannot disable constraint (string.string) - dependencies exist
Cause: an alter table disable constraint failed becuase the table has foriegn keys that
are dpendent on this constraint.
Action: Either disable the foreign key constraints or use disable cascade
ORA-02298: cannot validate (string.string) - parent keys not found
Cause: an alter table validating constraint failed because the table has orphaned child
records.
Action: Obvious
ORA-02299: cannot validate (string.string) - duplicate keys found
Cause: an alter table validating constraint failed because the table has duplicate key
values.
Action: Obvious
ORA-02100 to ORA-04099 61-15
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: maximum number of OIDGENERATORS is 255
Cause: A number greater than 255 was specified for the value of OIDGENERATORS.
Action: Make sure 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 statement.
Action: Enter a valid type name in the statement and retry the operation.
ORA-02303: cannot drop or replace a type with type or table dependents
Cause: An attempt was made to drop or replace a type that has type or table
dependents.
Action: For DROP TYPE, drop all type(s) and table(s) depending on the type and then
retry the operation, or use the FORCE option. For CREATE TYPE, drop all type(s) and
table(s) depending on the type and then retry the operation, or drop all table(s)
depending on the type and retry with 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 either: - not a string of 32 hexadecimal characters - an object identifier that
already identifies an existing object - an object identifier different from the original
object identifier already assigned to the type
Action: Do not specify the object identifier clause or specify a 32 hexadecimalcharacter object identifier literal that is unique or identical to the originally assigned
object identifier. Then retry the operation.
ORA-02305: only EXECUTE, DEBUG, and UNDER privileges are valid for types
Cause: An attempt was made to GRANT or REVOKE an invalid privilege (not
EXECUTE, DEBUG, or UNDER) on a type.
Action: GRANT or REVOKE only the EXECUTE, DEBUG, or UNDER privilege on
types.
ORA-02306: cannot create a type that already has valid dependent(s)
Cause: An attempt was made to create a type that already has some valid
dependent(s) (these dependents depend on the fact that the type does not exist).
Action: Drop the dependents first before creating the type, or do not create the type.
ORA-02307: cannot alter with REPLACE option a type that is not valid
Cause: An attempt was made to ALTER with REPLACE option a type that is not
valid.
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.
Action: Remove the invalid option from column specification and retry the operation.
ORA-02309: atomic NULL violation

Cause: An attempt was made to acess the attributes of a NULL object instance.
Action: Ensure that the object instance is non-NULL before accessing.
ORA-02310: exceeded maximum number of allowable columns in table
Cause: The attributes in the object type column exceeded the maximum number of
columns allowed in a table.
Action: Specify fewer attributes for the object type and retry the operation.
ORA-02311: cannot alter with COMPILE option a valid type with type or table
dependents
Cause: An attempt was made to ALTER with COMPILE option a type that is valid
and has type or table dependents.
Action: No need to perform this operation.
ORA-02313: object type contains non-queryable type string attribute
Cause: The specified object type contains a nested attribute whose type is nonqueryable.
Action: Use an object type with queryable attribute types.
ORA-02314: illegal use of type constructor
Cause: The statement contains an illegal use of a type constructor.
Action: Refer to the SQL Reference manual for the correct statement syntax.
ORA-02315: incorrect number of arguments for default constructor
Cause: The number of arguments specified for the default constructor doesn't match
the number of attributes of the object type.
Action: Specify the correct number of arguments for the default constructor and retry
the operation.
ORA-02320: failure in creating 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 that follow for more details. If the situation they describe
can be corrected, do so; otherwise contact Oracle Support.
ORA-02322: failure in accessing storage table of the nested table column
Cause: An error occured while performing DML on the storage table of the nested
table column.
Action: If the situation described in the following messages can be corrected, do so;
ORA-02324: more than one column in the SELECT list of THE subquery
Cause: More than one column was selected in the THE subquery.
Action: Specify only one column in the SELECT list of the THE subquery and retry
the operation.
ORA-02327: cannot create index on expression with datatype string
Cause: An attempt was made to create an index on a non-indexable expression.
Action: Change the column datatype or do not create the index on an expression
whose datatype is one of VARRAY, nested table, object, LOB, or REF.
ORA-02100 to ORA-04099 61-17
ORA-02329: column of datatype string cannot be unique or a primary key

Cause: An attempt was made to place a UNIQUE or a PRIMARY KEY constraint on a
column of datatype VARRAY, nested table, object, LOB, FILE or REF.
Action: Change the column datatype or remove the constraint. Then retry the
operation.
ORA-02330: datatype specification not allowed
Cause: An attempt was made to specify the data type in the column constraint
specification of an object table.
Action: Remove data type specification and retry the operation.
ORA-02331: cannot create constraint on column of datatype string
Cause: An attempt was made to create a constraint on a column posessing a nonconstrainable datatype -- VARRAY, nested table, object, LOB, FILE, or REF.
Action: Change the column datatype, or remove the constraint.
ORA-02332: cannot create index on attributes of this column
Cause: An attempt was made to create an index on an attributes of an object type
column.
Action: 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 an object type
column.
Action: Remove the constraint or change the object type.
ORA-02334: cannot infer type for column
Cause: A datatype was not declared for this column (in the CREATE TABLE) and an
attempt was made to create a constraint on an attribute of this column.
Action: Declare a datatype for the column.
ORA-02335: invalid datatype for cluster column
Cause: An attempt was made to declare a CLUSTER column of datatype object, REF,
nested table, VARRAY, LOB, or FILE.
Action: Remove the CLUSTER column or change the datatype of the column.
ORA-02336: column attribute cannot be accessed
Cause: An attempt was made to extract an attribute of an object type column.
Action: Change the object type for the column and retry the operation.
ORA-02337: not an object type column
Cause: An attempt was made to use dotted notation on a non-ADT column; that is,
"a.b.c" where "a" is not an object type.
Action: Either 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.
Action: Remove the column specification or specify a column constraint. Then retry
the operation.
ORA-02339: invalid column specification

Cause: An attempt was made to specify the PACKED or UNPACKED keyword for a
non-object type column.
Action: Remove the PACKED or UNPACKED keyword in the column specification
ORA-02340: invalid column specification
Cause: An attempt was made to specify an UNPACKED column within a packed
table.
Action: Remove the UNPACKED keyword in the column specification.
ORA-02342: replacement type has compilation errors
Cause: The use of the ALTER...REPLACE statement on a valid type caused a
compilation error.
Action: Use the ALTER...REPLACE statement to replace the type with a valid type
which does not cause compilation errors.
ORA-02344: cannot revoke execute on a type with table dependents
Cause: An attempt was made to revoke execute on a type that has dependents.
Action: Drop all table(s) depending on the type, then retry the operation, or use the
FORCE option.
ORA-02345: cannot create a view with column 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 columns of an object table
Cause: An attempt was made to grant privileges on the columns of an object table.
Action: n/a
ORA-02348: cannot create VARRAY column with embedded LOB
Cause: An attempt was made to create a column of a VARRAY type which has an
embedded LOB attribute. The LOB could be an attribute of a subtype of the declared
type of VARRAY's element.
Action: Remove offending attribute from type. If it is a subtype attribute then declare
the VARRAY column NOT SUBSTITUTABLE.
ORA-02349: invalid user-defined type - type is incomplete
Cause: An attempt was made to use an incomplete type definition as a column or
table datatype.
Action: Complete the type definition and retry the operation.
ORA-02351: internal error: string\n
Cause: An unexpected error condition was detected.
Action: Make a note of the error number and message and contact Oracle Support
Services.
ORA-02352: error setting an OCI attribute: string\n
Cause: An OCI error has occurred.
ORA-02100 to ORA-04099 61-19
Action: The table or column referenced may not be accessible. Contact Oracle Support
Services if the problem cannot be resolved.
ORA-02353: error fetching an OCI attribute: string\n
Cause: An OCI error has occurred.
Action: The table or column referenced may not be accessible. Contact Oracle Support
Services if the problem cannot be resolved.
ORA-02354: error in exporting/importing data\nstring
Cause: An error has occurred in a stream export or import operation. This message
will be followed by another message giving more details about this error.
Action: See export/import documentation for an explanation of the second error
message.
ORA-02355: error opening file: string\n
Cause: An attempt to open the specified file for data export/import failed.
ORA-02356: The database is out of space. The load cannot continue
Cause: The load was discontinued due to space exhaustion in the database.
Action: Add space for the specified table.
ORA-02357: header in file string may not contain correct information\n
Cause: The header may be corrupted.
ORA-02358: error in exporting or importing data\n
Cause: An error has occurred in a stream export or import operation.
ORA-02359: database version in file string is not valid\n
Cause: The specified file could not be used for this load because its database version
was not compatible with the database version in the other files in the DUMPFILE
clause.
Action: Verify all the files in the DUMPFILE clause are from the same unload
operation.
ORA-02360: fatal error during data export/import initialization\n
Cause: An unexpected error occurred during initialization for data export/import.
ORA-02361: error while attempting to allocate number bytes of memory\n
Cause: An error occurred while trying to allocate memory. This is likely caused by
Action: Reconnect to the instance and retry the operation.
ORA-02362: error closing file: string\n
Cause: An attempt to close the specified file for data export/import failed.
ORA-02363: error reading from file: string\n

Cause: An attempt to read from the specified file for data export/import failed.
ORA-02364: error writing to file: string\n
Cause: An attempt to write to the specified file for data export or import failed.
ORA-02365: error seeking in file: string\n
Cause: An attempt to seek to the specified position in file failed.
ORA-02366: The following index(es) on table string were processed:
Cause: The table had some indexes which were loaded if there were no errors.
Action: None
ORA-02367: read ended but had expected more data from file string\n
Cause: A truncated or incomplete file was used for the load operation.
Action: Verify unload operation completed successfully and that the files had not
been accidentally truncated.
ORA-02368: the following file is not valid for this load operation\n
Cause: A file could not be used for this load. See the following message for more
information.
operation and that the unload was successful.
ORA-02369: internal number in header in file string is not valid\n
Cause: The specified file could not be used for this load because the internal number
in the header was not valid.
Action: If the dump files were transferred over, verify the transfer operation was done
correctly.
ORA-02370: internal metadata in file string is not valid\n
Cause: The specified file could not be used for this load because the internal metadata
stored in this file does not match the metadata stored in the first file piece set.
operation.
ORA-02371: Loader must be at least version string.string.string.string.string for
direct path
Cause: The loader being used is incompatible with this version of the kernel.
Action: Upgrade your loader to at least the specified version or use the conventional
path.
ORA-02372: data for row: string \n
Cause: A conversion error occurred while loading data into a table. The message
shows values for the field in the row that had the conversion error.
ORA-02100 to ORA-04099 61-21
Action: None. This is only an informational message.

ORA-02373: Error parsing insert statement for table string.
Cause: self-evident.
Action: Check the error given below this one.
ORA-02374: conversion error loading table string.string
not be loaded. To avoid this error, make sure the definition of the table being
imported matches the definition of the table being exported.
ORA-02375: conversion error loading table string.string partition string
not be loaded. To avoid this error, make sure the definition of the table being
imported matches the definition of the table being exported.
ORA-02376: invalid or redundant resource
Cause: a create, or alter profile command which names a resource not yet defined, or
try to specify same resource twice.
Action: define resource first
ORA-02377: invalid resource limit
Cause: specifying limit of 0
Action: specify limit > 0
ORA-02378: duplicate resource name string
ORA-02379: profile string already exists
Cause: Try to create a profile which already exist
Action: n/a
ORA-02380: profile string does not exist
Cause: Try to assign a user to a non-existant profile
Action: n/a
ORA-02381: cannot drop PUBLIC_DEFAULT profile
Cause: Try to drop PUBLIC_DEFAULT profile
Action: n/a
ORA-02382: profile string has users assigned, cannot drop without CASCADE
ORA-02383: illegal cost factor
Cause: Negative or UNLIMITED cost for this resourc
Action: n/a
ORA-02390: exceeded COMPOSITE_LIMIT, you are being logged off
ORA-02391: exceeded simultaneous SESSIONS_PER_USER limit

Cause: An attempt was made to exceed the maximum number of concurrent sessions
allowed by the SESSION_PER_USER clause of the user profile.
Action: End one or more concurrent sessions or ask the database administrator to
increase the SESSION_PER_USER limit of the user profile.
ORA-02392: exceeded session limit on CPU usage, you are being logged off
ORA-02393: exceeded call limit on CPU usage
ORA-02394: exceeded session limit on IO usage, you are being logged off
ORA-02395: exceeded call limit on IO usage
ORA-02396: exceeded maximum idle time, please connect again
Cause: as stated
Action: n/a
ORA-02397: exceeded PRIVATE_SGA limit, you are being logged off
Cause: Only when using TP monitor
Action: expand limit
ORA-02398: exceeded procedure space usage
Cause: Stored procedured used up too much space in SYSTEM Tablespace
Action: Use less stored procedure
ORA-02399: exceeded maximum connect time, you are being logged off
Cause: As stated
Action: n/a
ORA-02400: explain plan output buffer size limit exceeded
Cause: Internally this error is raised and caught to handle cases where the plan output
exceeds te buffer size. The output is truncated in cases.
Action: This error should never be seen externally.
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 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.
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 in an existing plan table.
ORA-02403: plan table does not have correct format
Cause: The explicit plan table does not have the appropriate field definitions.
Action: Redefine the plan table to have the appropriate field definitions.
ORA-02404: specified plan table not found
Cause: The specified plan table does cannot be found.
ORA-02100 to ORA-04099 61-23
Action: Create the specified plan table or use an existing plan table.
ORA-02405: invalid sql plan object provided
Cause: The user provided a NULL, empty, or malformed object of type
SQL_PLAN_TABLE_TYPE
Action: Provide a new, properly formed object to the function
ORA-02420: missing schema authorization clause
Cause: the AUTHORIZATION clause is missing from a create schema statement.
Action: Preceed the schema authorization identifier with the AUTHORIZATION
keyword.
ORA-02421: missing or invalid schema authorization identifier
Cause: the schema name is missing or is incorrect in an authorization clause of a
create schema statement.
Action: If the name is present, it must be the same as the current schema.
ORA-02422: missing or invalid schema element
Cause: A statement other than a create table, create view, or grant privilege appears in
a create schema statement.
Action: Self-evident.
ORA-02423: schema name does not match schema authorization identifier
Cause: a table definition with a schema name prepended to the table name does not
match the schema name provided in the authorization clause of a create schema
statement.
Action: make sure the schema names match.
ORA-02424: potential circular view references or unknown referenced tables
Cause: the create schema statement contains views that depend on other views in the
containing create schema statement or they contain references to unknown tables.
Action: create the dependent views in a separate create schema statement and make
sure all referenced tables are either defined in the create schema statement or exist
outside the statement.
ORA-02425: create table failed
Cause: a create table statement failed in the create schema statement.
Action: the cause for failure will be presented below this error message. Follow
appropriate action(s) as suggested by the subsequent error message.
ORA-02426: privilege grant failed
Cause: a grant privilege statement failed inthe create schema statement.
ORA-02427: create view failed
Cause: a create view statement failed in the create schema statement.
ORA-02428: could not add foreign key reference

Cause: could not add a foreign key reference because of error in declaration. Either
referenced table does not exist or table does not have an unique key.
Action: make sure referenced table exists and/or has unique key
ORA-02429: cannot drop index used for enforcement of unique/primary key
Cause: user attempted to drop an index that is being used as the enforcement
mechanism for unique or primary key.
Action: drop the constraint instead of the index.
ORA-02430: cannot enable constraint (string) - no such constraint
Cause: the named constraint does not exist for this table.
Action: Obvious
ORA-02431: cannot disable constraint (string) - no such constraint
Action: Obvious
ORA-02432: cannot enable primary key - primary key not defined for table
Cause: Attempted to enable a primary key that is not defined for the table.
Action: Need to add a primary key definition for the table.
ORA-02433: cannot disable primary key - primary key not defined for table
Cause: Attempted to disable a primary key tht is not defined for the table.
Action: None
ORA-02434: cannot enable unique(string) - unique key not defined for table
Cause: attempted to enable a unique key that is not defined for the table.
Action: None
ORA-02435: cannot disable unique(string) - unique key not defined for table
Cause: attempted to disable a unique key that is not deined for the table.
Action: None
ORA-02436: date or system variable wrongly specified 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 completely specified in a CREATE TABLE or
ALTER TABLE statement. For example, a date was specified without the century.
Action: Completely specify the date constant or system variable. Setting the event
10149 allows constraints like "a1 > '10-MAY-96'", which a bug permitted to be created
before version 8.
ORA-02437: cannot validate (string.string) - primary key violated
Cause: attempted to validate a primary key with duplicate values or null values.
Action: remove the duplicates and null values before enabling a primary key.
ORA-02438: Column check constraint cannot reference other columns
Cause: attempted to define a column check constraint that references another column.
Action: define it as a table check constriant.
ORA-02100 to ORA-04099 61-25
ORA-02439: Unique index on a deferrable constraint is not allowed

Cause: attempted to enable 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 not
deferrable.
ORA-02440: Create as select with referential constraints not allowed
Cause: create table foo (... ref. con. ...) as select ...;
Action: Create the table as select, then alter the table to add the constraints
afterwards.
ORA-02441: Cannot drop nonexistent primary key
Cause: alter table drop primary key - primary key does not exist.
Action: None
ORA-02442: Cannot drop nonexistent unique key
Cause: alter table drop unique (col list) - unique specification does not exist.
Action: make sure column list for unique constraint is correct.
ORA-02443: Cannot drop constraint - nonexistent constraint
Cause: alter table drop constraint <constraint_name>
Action: make sure you supply correct constraint name.
ORA-02444: Cannot resolve referenced object in referential constraints
Cause: attempted to define foreign key referencing an object which cannot be
resolved to a base table reference
Action: referential constraints can only be defined on objects which can be resolve to
base table reference
ORA-02445: Exceptions table not found
Cause: the explicity or implicity declared exceptions table does not exist.
Action: Create the table then issue 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 constraints.
ORA-02447: cannot defer a constraint that is not deferrable
Cause: An attempt was made to defer a nondeferrable constraint
Action: Drop the constraint and create a new one that is deferrable
ORA-02448: constraint does not exist
Cause: The named constraint does not exist
Action: Stop trying to do something with a nonexistant constraint
ORA-02449: unique/primary keys in table referenced by foreign keys
Cause: An attempt was made to drop a table with unique or primary keys referenced
by foreign keys in another table.
Action: Before performing the above operations the table, drop the foreign key
constraints in other tables. You can see what constraints are referencing a table by
issuing the following command: SELECT * FROM USER_CONSTRAINTS WHERE
TABLE_NAME = "tabnam";
ORA-02450: Invalid hash option - missing keyword IS
Cause: Missing IS keyword.
Action: Specify HASH IS option.
ORA-02451: duplicate HASHKEYS specification
Cause: The HASHKEYS option is specified more than once.
Action: Only specify the HASHKEYS option once.
ORA-02452: invalid HASHKEYS option value
Cause: The specified HASHKEYS option must be an integer value.
ORA-02453: duplicate HASH IS specification
Cause: The HASH IS option is specified more than once.
Action: only specify the HASH IS option once.
ORA-02454: Number of hash keys per block (string) exceeds maximum of string
Cause: The SIZE argument is too small.
Action: Increase the SIZE argument.
ORA-02455: The number of cluster key column must be 1
Cause: When specifing the HASH IS option, the number of key columns must be 1.
Action: Either do not specify the HASH IS option or reduce the number of key
columns.
ORA-02456: The HASH IS column specification must be NUMBER(*,0)
Cause: The column specification must specify an integer.
Action: 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: Hashkey value must be a positive integer
Cause: The value of the hash key was not a positive number.
Action: Specify a positive integer.
ORA-02460: Inappropriate index operation on a hash cluster
Cause: An attempt to create a cluster index was issued on a hash cluster.
Action: Do not attempt to create such an index.
ORA-02100 to ORA-04099 61-27
ORA-02461: Inappropriate use of the INDEX option

Cause: This option is only valid for non hash clusters.
Action: Do not specify this option.
ORA-02462: Duplicate INDEX option specified
Cause: The INDEX option is specified more than once.
Action: Only specify the INDEX option once.
ORA-02463: Duplicate HASH IS option specified
Cause: The HASH IS option is specified more than once.
Action: Only specify the HASH IS option once.
ORA-02464: Cluster definition can not be both HASH and INDEX
Cause: The cluster can either be a hash or indexed cluster - not both.
Action: Remove either the HASH IS or INDEX options.
ORA-02465: Inappropriate use of the HASH IS option
Cause: This option is only valid for clusters
Action: Do not specify this option
ORA-02466: The SIZE and INITRANS options cannot be altered for HASH
CLUSTERS.
Cause: An attempt was made to change the SIZE and INITRANS options after the
hash cluster was 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 cluster definition.
Action: Recreate the cluster and correct the error in hash expression.
ORA-02468: Constant or system variable wrongly specified in expression
Cause: A constant or system variable was specified in the hash expression.
ORA-02469: Hash expression does not return an Oracle Number.
Cause: Result of evaluating hash expression is not an Oracle Number.
ORA-02470: TO_DATE, USERENV, or SYSDATE incorrectly used in hash
expression.
Cause: An attempt was made to specify SYSDATE, UID, USER, ROWNUM, or LEVEL
in hash expression.
Action: Re-create the cluster and correct the error in hash expression.
ORA-02471: SYSDATE, UID, USER, ROWNUM, or LEVEL incorrectly used in hash
expression.
Cause: SYSDATE, UID, USER, ROWNUM, or LEVEL are not allowed in hash
expressions.
Action: Recreate 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: Recreate the cluster and remove the PL/SQL function.
ORA-02473: Error while evaluating the cluster's hash expression.
Cause: An error occurred while evaluating the clusters hash expression.
Action: Correct the query and retry.
ORA-02474: Fixed hash area extents used (string) exceeds maximum allowed
(string)
Cause: The number of extents required for creating the fixed hash area exceeds the
maximum number allowed.
Action: Reduce the number of extents required by increasing the extent allocation
sizes within the STORAGE clause.
ORA-02475: maximum cluster chain block count of string has been exceeded
Cause: The number of blocks in a cluster chain exceeds the maximum number
allowed.
Action: Increase SIZE parameter in CREATE CLUSTER statement or reconsider
suitability of cluster key.
ORA-02476: can not create index due to parallel direct load on table
Cause: A parallel direct load is occurring to the specified table.
Action: Retry statement after load is complete.
ORA-02477: can not perform parallel direct load on object string
Cause: A parallel direct load is not possible because an index is is being created on the
table.
Action: Retry load after index creation is complete.
ORA-02478: merge into base segment would overflow MAXEXTENTS limit
Cause: Merge of temporary segment into base segment failed because MAXEXTENTS
was larger than the total in the temp and base segments
Action: Use a larger value for MAXEXTENTS on the base segment or make the
extents in the temporary segments larger
ORA-02479: error while translating file name for parallel load
Cause: An invalid file name was specified to load data into.
Action: Specify a valid database file.
ORA-02481: Too many processes specified for events (max string)
Cause: Too many processes specified than allowed per event.
Action: Enter fewer processes by using ranges or wildcards if possible.
ORA-02482: Syntax error in event specification (string)
Cause: Illegal event string
Action: Enter a legal event string
ORA-02483: Syntax error in process specification (string)
Cause: Illegal process string
Action: Enter a legal process string
ORA-02100 to ORA-04099 61-29
ORA-02484: Invalid _trace_buffers parameter specification (string)

Cause: Bad process or size in _trace_buffers INIT.ORA parameter.
Action: n/a
ORA-02485: Invalid _trace_options parameter specification (string)
Cause: Bad syntax for _trace_options INIT.ORA parameter.
Action: n/a
ORA-02486: Error in writing trace file string
Cause: Error occurred in creating/writing the file.
Action: Check file name and make sure it is constructed properly. Also, check
permissions for directories.
ORA-02487: Error in converting trace data
Cause: Incompatible binary trace data was specified.
Action: Check the format of the input data.
ORA-02488: Error encountered when accessing file [string] for trace conversion
Cause: An attempt was made to open or access the trace file during a trace
conversion.
Action: Check the permissions for both input and output files. Also, check the file
compatibility for the trace conversion.
ORA-02490: missing required file size in RESIZE clause
Cause: No value was specified for the RESIZE clause.
ORA-02491: missing required keyword ON or OFF in AUTOEXTEND clause
Cause: The keyword ON or OFF was not specified for the AUTOEXTEND clause.
ORA-02492: missing required file block increment size in NEXT clause
Cause: No value was specified for the NEXT clause.
ORA-02493: invalid file increment size in NEXT clause
Cause: A non-integer value was used for the NEXT clause of the DATAFILE list.
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
smaller than the SIZE value.
ORA-02495: cannot 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.
Action: Change the tablespace to read/write and retry the resize operation.
ORA-02700: osnoraenv: error translating ORACLE_SID

Cause: Two-task driver could not find the value of ORACLE_SID in the environment.
Action: Make sure that the ORACLE_SID environment variable has been properly set
and exported.
ORA-02701: osnoraenv: error translating oracle image name
set and exported.
ORA-02702: osnoraenv: error translating orapop image name
set and exported.
ORA-02703: osnpopipe: pipe creation failed
Cause: The pipe driver failed to create pipes 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. Note the operating system error code and
contact your system administrator.
ORA-02704: osndopop: fork failed
Cause: The two-task driver could not fork orapop.
Action: Verify that 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 of communication channel failed
Cause: The pipe driver failed while polling the communications channel.
ORA-02706: osnshs: host name too long
Cause: The length of your host-string specified by the TWO_TASK environment
variable exceeds the ORACLE system-imposed limit.
ORA-02707: osnacx: cannot allocate context area
Cause: The invoked Unix two-task driver could not allocate heap space for the context
area.
ORA-02708: osnrntab: connect to host failed, unknown ORACLE_SID
Cause: The invoked Unix two-task driver failed to find an entry in oratab for the sid
you supplied.
Action: First, check whether you have read access to oratab, and see if the desired sid
is there. Add an entry to oratab for the desired sid, if necessary.
ORA-02709: osnpop: pipe creation failed
Cause: The pipe driver failed to create pipes for two-task communications with the
oracle shadow process.
ORA-02100 to ORA-04099 61-31
ORA-02710: osnpop: fork failed
Cause: The pipe driver could not fork the oracle shadow process.
ORA-02711: osnpvalid: write to validation channel failed
Cause: The pipe driver failed to write to the orapop process.
ORA-02712: osnpop: malloc failed
Cause: The pipe driver failed to allocate enough heap space for its context area
buffers.
ORA-02713: osnprd: message receive failure
Cause: The pipe driver failed to read a message from the communications channel.
ORA-02714: osnpwr: message send failure
Cause: The pipe driver failed to write a message to the communications channel.
ORA-02715: osnpgetbrkmsg: message from host had incorrect message type
Cause: The pipe driver received a message having an unrecognizable message type.
ORA-02716: osnpgetdatmsg: message from host had incorrect message type
Cause: The Pipe driver received a message having an unrecognizable message type.
ORA-02717: osnpfs: incorrect number of bytes written
Cause: The Pipe driver sent a message that was apparently successful, but the number
of bytes transmitted did not match the number of bytes furnished to the driver.
ORA-02718: osnprs: reset protocol error
Cause: The two-task driver could not reset the connection.
ORA-02719: osnfop: fork failed
Cause: The fast driver could not fork the oracle shadow process.
ORA-02720: osnfop: shmat failed

Cause: When the fast driver was invoked, processes failed to attach to the shared
memory buffer. You probably supplied an illegal shared memory attach address, or
the system ran out of data space to accomodate the buffer.
Action: Try invoking the Fast driver later, or use the default attach address.
ORA-02721: osnseminit: cannot create semaphore set
Cause: The Fast driver failed to get a semaphore set.
Action: The system-imposed limit on semaphores or semaphore identifiers may have
been exceeded. Read the returned operating system error code and check with your
system administrator.
ORA-02722: osnpui: cannot send break message to orapop
Cause: The Pipe driver could not send a break message to orapop.
ORA-02723: osnpui: cannot send break signal
Cause: The Pipe driver could not send a break message to the ORACLE shadow
process.
ORA-02724: osnpbr: cannot send break message to orapop
Cause: The Pipe driver could not send a break message to orapop.
ORA-02725: osnpbr: cannot send break signal
process.
Action: Kill system call failed. Check errno and contact customer support.
ORA-02726: osnpop: access error on oracle executable
Cause: The Pipe driver could not access the oracle executable.
Action: Check the permissions on the ORACLE executable and each component of the
ORACLE_HOME/bin path.
ORA-02727: osnpop: access error on orapop executable
Cause: The Pipe driver could not access the orapop executable.
Action: Check the permissions on the orapop executable and each component of the
ORA-02728: osnfop: access error on oracle executable
Cause: The Fast driver could not access the oracle executable.
ORA-02729: osncon: driver not in osntab
Cause: The driver you have specified is not supported.
Action: Check with your database administrator which drivers are supported.
ORA-02100 to ORA-04099 61-33
ORA-02730: osnrnf: cannot find user logon directory

Cause: The driver you have specified could not find your logon directory while
searching for your local .sqlnet file.
Action: Set and export the HOME environment variable to identify your home
directory. Check with your system administrator to make sure that your uid and
home directory are correct in the /etc/passwd file.
ORA-02731: osnrnf: malloc of buffer failed
Cause: The specified driver could not find enough heap space to malloc a buffer.
ORA-02732: osnrnf: cannot find a matching database alias
Cause: Database alias specified was not identified in either $HOME/.sqlnet or /etc/
sqlnet.
Action: Create the alias in a file called .sqlnet in your home directory for personal use
or ask your system administrator to create the alias in /etc/sqlnet for system-wide
use.
ORA-02733: osnsnf: database string too long
Cause: While converting a database alias to a database ID, the resulting database ID
string exceeded the ORACLE system-imposed limit.
ORA-02734: osnftt: cannot reset shared memory permission
Cause: The Fast driver was unable to reset shared memory permissions.
ORA-02735: osnfpm: cannot create shared memory segment
Cause: The Fast driver failed to create a shared memory segment for two-task
communication.
Action: Check whether the system-imposed limit on shared memory identifiers has
already been reached for your system.
ORA-02736: osnfpm: illegal default shared memory address
Cause: The Fast driver failed to establish a default shared memory address.
ORA-02737: osnpcl: cannot tell orapop to exit
Cause: The Pipe driver failed to send orapop the command to exit.
ORA-02738: osnpwrtbrkmsg: incorrect number of bytes written
Cause: The pipe driver apparently sent an imcomplete break message.
ORA-02739: osncon: host alias is 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 failed to create a shared memory file for two-task
communication.
Action: Check the permissions on the directory ?/dbs
ORA-02751: osnfsmmap: cannot map shared memory file
Cause: The Fast driver failed to map a shared memory file for two-task
communication.
ORA-02752: osnfsmmap: illegal shared memory address
Cause: The Fast driver failed to attach shared memory at the expected location.
ORA-02753: osnfsmmap: cannot close shared memory file
Cause: The Fast driver cannot close the shared memory file.
ORA-02754: osnfsmmap: cannot change shared memory inheritence
Cause: The Fast driver could not alter the inheritence attributes of the shared
memory.
ORA-02755: osnfsmcre: cannot create chared memory file ?/dbs/ftt_pid.dbf
Cause: The Fast driver failed to create a file for shared memory.
Action: Check the permissions on the directory ?/dbs
ORA-02756: osnfsmnam: name translation failure
Cause: The Fast driver encountered an error translating the shared memory
filename ?/dbs/ftt_pid.dbf.
ORA-02757: osnfop: fork_and_bind failed
Cause: The Fast driver failed to fork a process onto the desired cluster and node
number.
Action: Check the desired node number in sercose[0] and cluster ID in sercose[1]. If
these seem valid, contact customer support.
ORA-02758: Allocation of internal array failed
Cause: The package was unable to allocate memory for an array because the system
ran out of memory.
Action: Either reclaim memory by killing other processes or reboot the machine with
more memory.
ORA-02759: Not enough request descriptors available
Cause: All of the package's request descriptors are in use performing other requests.
Action: Either wait until enough requests are done, or shut the package down and reinitialize it with more request descriptors.
ORA-02760: Client close of file failed.
Cause: The client was unable to close a file after forking the servers.
ORA-02100 to ORA-04099 61-35
Action: This is a system problem - contact your System Administrator.

ORA-02761: File number to be canceled is negative.
Cause: The file number contained with the sfiov structure is less than zero.
Action: This may be a programming error. If it is not, contact ORACLE support.
ORA-02762: file number to be cancelled is greater than the maximum.
Cause: The file number contained with the sfiov structure is greater than the
maximum.
Action: This may be a programming error. If it is not, contact ORACLE support.
ORA-02763: Unable to cancel at least one request
Cause: No requests were found that could be cancelled.
Action: This error can occur if all the requests dealing with that file number have
already been filled.
ORA-02764: Invalid package mode
Cause: The mode of the package 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 given was less than or equal to zero.
Action: Use a number greater than zero.
ORA-02766: Invalid maximum 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 was allocated per server
Cause: The package requires that the number of request descriptors be greater than or
equal to the number of servers used.
Action: Use a higher number
ORA-02768: 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: Setting of handler for SIGTERM failed
Cause: The package was unable to set up handling by the server for the termination
signal. This is an internal error.
Action: Contact ORACLE support.
ORA-02770: Total number of blocks is invalid
Cause: The total number of blocks to be allocated for use by the package was not
greater than zero.
ORA-02771: Illegal request time out value
Cause: The number was not a positive number.
ORA-02772: Invalid maximum server idle time

Cause: The time given was not a positive number.
ORA-02773: Invalid maximum client wait time
ORA-02774: Invalid request list latch time out value
ORA-02775: Invalid request done signal
Cause: The signal number was not a positive number.
ORA-02776: Value for request done signal exceeds maximum
Cause: The value sent to the package for use as the "request done" signal exceeds the
maximum allowed by the operating system.
Action: n/a
ORA-02777: Stat failed on log directory
Cause: The package was unable to get information about the directory in which the
log files are to reside.
ORA-02778: Name given for the log directory is invalid
Cause: The name given for the directory in which the logs are to be kept does not
correspond to a directory.
ORA-02779: Stat failed on core dump directory
Cause: The package was unable to get information about the directory into which the
servers are to dump core in the event of an exception.
ORA-02780: Name given for the core dump directory is invalid
Cause: The name given for the directory in which the server processes are to dump
core in the event of an exception does not correspond to a directory.
ORA-02781: Invalid value given for the timing wanted flag
Cause: The value given was not TRUE or FALSE.
Action: n/a
ORA-02782: Both read and write functions were not specified
Cause: To ensure that the functions act symmetrically, pointers to both the read and
write functions must be given.
Action: Either specify both functions or specify neither. The package will supply its
own functions.
ORA-02100 to ORA-04099 61-37
ORA-02783: Both post and wait functions were not specified

Cause: To ensure that the functions act symmetrically, pointers to both the posting
and waiting functions must be given.
Action: Either specify both functions or specify neither. The package will supply its
own functions.
ORA-02784: Invalid shared memory ID specified
Cause: The ID of the segment specified for 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 given for the shared memory segment to be used as the shared buffer
region was less than or equal to zero.
ORA-02786: Size needed for shared region is greater than segment size
Cause: The size of the shared segment that was specified for the shared buffer region
is less than the number of bytes required. The first field of the "additional
information" field is the size needed. The second is the size of the segment.
Action: Use a larger size segment or let the package allocate its own.
ORA-02787: Unable to allocate memory for segment list
Cause: The package cannot allocate memory for an internal segment list because the
system has run out of memory. The "additional information" field is the amount of
memory that the package attempted to allocate.
Action: n/a
ORA-02788: Unable to find kernel process pointer in async process array
Cause: Internal error - Contact ORACLE support.
Action: n/a
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 re-initialize the package with a higher number.
ORA-02790: File name is too long
Cause: The length of the name of a file that is being opened for asynchronous I/O is
longer than the maximum. The "additional information" field is the maximum length.
Action: Use a shorter name.
ORA-02791: Unable to open file for use with asynchronous I/O
Cause: The package could not open file for some reason.
Action: Check the file name.
ORA-02792: Unable to fstat() a file being used for asynchronous I/O.
Cause: The fstat(2) call on a file being used for asynchronous I/O failed.
Action: Check the file name.
ORA-02793: Close of asynchronous I/O failed.

Cause: The client was unable to close a file being used for asynchronous I/O.
Action: Contact ORACLE support - this should not happen.
ORA-02794: Client unable to get key for shared memory
Cause: The client was unable to get a key so that it obtain shared memory for use with
shared memory.
Action: Contact ORACLE support - this is an internal error.
ORA-02795: Request list is empty
Cause: The client was signalled by a server that it was done with a request but the
"done" list was empty.
Action: Internal error - contact ORACLE support.
ORA-02796: Done request is not in correct state
Cause: A request is not in the right state.
ORA-02797: No requests available
Cause: No free request descriptors are available.
Action: Wait until some requests are filled and then retry the request, or shutdown
the servers and initialize the package with a higher number of requests.
ORA-02798: Invalid number of requests
Cause: The number of operations sent to either sfard() or sfawrite() is less than zero.
Action: This is a user programming error.
ORA-02799: Unable to arm signal handler
Cause: The arming of a signal handler for the "done" signal failed.
ORA-02800: Requests timed out
Cause: Some of the requests for asynchronous input or output were not serviced in
the required amount of time.
Action: If the load on the system is high, it is possible that the timeout limit is too low.
Reset it with sfainit(). If the server processes are dying due to unexpected signals, this
is an internal error, and ORACLE support should be contacted.
ORA-02801: Operations timed out
Cause: Some asynchronous operations timed out in kernel mode.
ORA-02802: No idle servers available in parallel mode
ORA-02803: Retrieval of current time failed
ORA-02100 to ORA-04099 61-39
ORA-02804: Allocation of memory failed for log file name

Cause: The client was unable to allocated a buffer for the name of the log file.
Action: Contact your System Administrator.
ORA-02805: Unable to set handler for SIGTPA
ORA-02806: Unable to set handler for SIGALRM
ORA-02807: Allocation of memory for I/O vectors failed.
Cause: The client was unable to allocate memory for the array of I/O vectors that the
servers are to use.
ORA-02808: Allocation of memory of open files array failed.
Cause: The client was unable to allocate memory for an array of flags that the servers
are to use.
ORA-02809: Jump buffer not valid
ORA-02810: Unable to make temporary file name for memory mapped file
ORA-02811: Unable to attach shared memory segment
ORA-02812: Bad attach address
ORA-02813: Unable to make temporary file name in order to get key
ORA-02814: Unable to get shared memory
Cause: Shmget(2) failed.
Action: Check the UNIX number. If you are unsure about what it means, contact
ORACLE customer support.
ORA-02815: Unable to attach shared memory
Cause: Shmat(2) failed.
Action: Check the UNIX number. If you are unsure about what it means, contact
ORACLE customer support.
ORA-02816: Unable to kill a process
Cause: A server did not die after being sent a kill signal.
Action: The process may be a runaway - contact ORACLE customer support.
ORA-02817: Read failed

Cause: A server could not read a 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 in.
ORA-02818: Less than the number of blocks requested was read in
Cause: A server could not read in the request amount of data. The first number in the
"additional information" field is the block number being read in. The second is the
actual number of bytes that was read in.
Action: This is a programming error.
ORA-02819: Write failed
Cause: A server was unable to perform a write. The number in the "additional
information" field is the starting block number of the data segment being written out.
The first number in the "additional information" field is the block number being
written out. The second is the actual number of bytes that was written out. The disk
may have filled up.
Action: Check the UNIX error number.
ORA-02820: Unable to write the requested number of blocks
Cause: A server could not write the requested amount of data out to disk. The disk
may have run out of space.
ORA-02821: Unable to read the requested number of blocks.
Cause: A server could not read the number of blocks that was requested. 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 seek to the designated block.
ORA-02823: Buffer is not aligned.
Cause: The buffer on which an I/O is being done is not on the correct boundary.
Action: Check the calling program.
ORA-02824: Request free list is empty
Cause: The list from which the package allocates request descriptors is empty because
all of the descriptors is in use.
Action: Wait until some become free, or initialize the package with a higher number
of request descriptors.
ORA-02825: Request on free list was not free
ORA-02826: Illegal block size
Cause: A negative number was given for the I/O block size to be used by the
asynchronous I/O package.
ORA-02100 to ORA-04099 61-41
Action: This is a programming error - use either a positive number or zero to get the
default value.
ORA-02827: Invalid file number
Cause: The file number upon which an operation is to done is either less than zero or
greater than the maximum number of files than can be open.
Action: This is a programming error. Since the calling program should not touch this
number, this is a programming error.
ORA-02828: Segment free list is empty
Cause: No segments are available to allocated.
Action: Free some segments or shut down the package and re-initialize it with a
higher number of segments.
ORA-02829: No segment of the proper size is available
Cause: No segment of the proper size is ready for use by the caller.
Action: Free some segments and try again.
ORA-02830: Segment could not be split - no free segments available
Cause: A segment that is larger than that desired could not be split because no free
segment was available.
Action: Free some segments and try again.
ORA-02831: Segment deallocation failed - empty segment list
Cause: The caller attempted to deallocate a segment but the "in use" list was empty.
This is a programming error.
ORA-02832: Segment deallocation failed - segment not on list
Cause: The caller attempted to deallocate a segment that was not on the "in use" list.
This is a programming error.
ORA-02833: Server was unable to close file
Cause: A server was unable to close a file being used for asynchronous I/O.
Action: See the UNIX error number for more information.
ORA-02834: Server unable to open file
Cause: The server was unable to open a file for use with asynchronous I/O.
Action: Check the UNIX error number for more information.
ORA-02835: Server unable to send signal to client
ORA-02836: Unable to create temporary key file
ORA-02837: Unable to unlink temporary file

ORA-02838: Unable to arm signal handler for the alarm signal
Cause: The arming of a signal handler for the alarmsignal failed.
ORA-02839: Sync of blocks to disk failed.
Cause: The server was unable to flush its writes out to disk.
ORA-02840: Open of log file by client failed
Cause: The client process was unable to open its log file.
Action: Check the UNIX error number for more information.
ORA-02841: Server died on start up
Cause: A server exited during its initialization process.
Action: Check the servers' logs for more information.
ORA-02842: Client unable to fork a server
Cause: The client could not spawn a server. A possible reason is that the operating
system has reached its limit on the number of processes that it can spawn.
Action: Either reduce the number of servers that are to be used, or reconfigure the
operating system so that it can handle more processes.
ORA-02843: Invalid value for kernel flag
Cause: An illegal value was given for the kernel flag in the information structure.
Only TRUE and FALSE are permitted.
Action: This is a programming error - check the calling routine.
ORA-02844: Invalid value for the leave open flag
Cause: A value was given for the flag that determines whether a file is to be left open
after the client checks it to see if the servers can use it. Only TRUE and FALSE are
supported.
ORA-02845: Invalid value for the timing wanted flag
Cause: A value was given for the flag that indicates that operations are to be timed
out. Only TRUE and FALSE are supported.
ORA-02846: Unkillable server
Cause: A server would not respond to the termination signal. The first number is the
number of the server. The second is its UNIX process number. This is an internal
problem.
Action: This is an operating system problem.
ORA-02847: Server did not terminate when posted
Cause: A server did not respond to a posted request to shutdown. The first number is
the number of the server. The second is its UNIX process number. This is an internal
problem.
ORA-02100 to ORA-04099 61-43
ORA-02848: Asynchronous I/O package is not running

Cause: An operation using the asynchronous I/O package was attempted without
first initializing the package using sfainit().
Action: Call sfainit() before using the package.
ORA-02849: Read failed because of an error
Cause: A server could not read the requested amount of data from disk.
ORA-02850: File is closed
Cause: A file upon which an asynchronous I/O operation is to be performed has
already been closed by the package.
Action: This is a programming error.
ORA-02851: Request list is empty when it should not be
Cause: This is an internal problem.
ORA-02852: Invalid critical-section time out value
ORA-02853: Invalid server list latch time out value
ORA-02854: Invalid number of request buffers
Cause: The value given for "db_slave_buffers" in your INIT.ORA file is less than 0.
Action: Use a number that is greater than or equal to 0.
ORA-02855: Number of requests is less than the number of slaves
Cause: The value given for 'db_slave_buffers' in the initialization parameter file was
less than the number specified for the number of slaves, 'db_slaves.'
Action: Specify a number that is greater than that given for 'db_slaves.' Alternatively,
specify 0. The kernel will supply the appropriate number.
ORA-02875: smpini: Unable to get shared memory for PGA
Cause: Stated in errno.
Action: Resolve the problem.
ORA-02876: smpini: Unable to attach to shared memory for PGA
Cause: Stated in errno.
Action: Resolve the problem.
ORA-02877: smpini: Unable to initialize memory protection
Cause: The adspcinit program has not been executed.
Action: Execute the adscpinit program as shown in your Installation and Users'
Guide. If the problem persists, try rebooting your computer.
ORA-02878: sou2o: Variable smpdidini overwritten
Cause: The variable smpdidini was overwritten, probably by client code.
Action: Verify client code, e.g. Pro*C, for illegal memory access. If the problem occurs
outside Single Task operation, contact your customer support representative.
ORA-02879: sou2o: Could not gain access to protected memory
Cause: This is an internal error, note error code in errno.
Action: Report to your customer support representative. Restarting your application
or your computer may cure the problem.
ORA-02880: smpini: Could not register PGA for protection
ORA-02881: sou2o: Could not revoke access to protected memory
ORA-02882: sou2o: Could not register SGA for protection
ORA-02899: smscre: Cannot create SGA with Extended Shared Memory feature
Cause: The environment variable EXTSHM was set before starting oracle.
Action: Unset the environment variable EXTSHM and startup oracle.
ORA-03001: unimplemented feature
Cause: This feature is not implemented.
Action: None
ORA-03002: operator not implemented
ORA-03007: obsolete feature
Cause: User attempted to use a feature which is no longer supported.
Action: None
ORA-03009: Incompatible OCI function call
Cause: An incompatible OCI function call was issued for new functionality.
Action: Do not use V7 OCI calls for this functionality.
ORA-03100: communication area cannot be allocated; insufficient memory
ORA-03105: internal protocol error
ORA-03106: fatal two-task communication protocol error
ORA-03107: oranet buffer underflow
ORA-03108: oranet: ORACLE does not support this interface version
ORA-02100 to ORA-04099 61-45
ORA-03109: oranet buffer overflow

ORA-03110: oranet: ORACLE does not support this SQL version
ORA-03111: break received on communication channel
ORA-03112: a server linked as single-task cannot use SQL*Net
Cause: A statement containing a SQL*Net connect string was issued to the single-task
server. For example, a database link was used in a SQL statement.
Action: Do not use SQL*Net connect strings in a single-task environment.
ORA-03113: end-of-file on communication channel
Cause: The connection between Client and Server process was broken.
Action: There was a communication error that requires further investigation. First,
check for network problems and review the SQL*Net setup. Also, look in the alert.log
file for any errors. Finally, test to see whether the server process is dead and whether
a trace file was generated at failure time.
ORA-03114: not connected to ORACLE
ORA-03115: unsupported network datatype or representation
ORA-03116: invalid buffer length passed to a conversion routine
ORA-03117: two-task save area overflow
ORA-03118: two-task coroutine has invalid state
ORA-03119: two-task detected inconsistent datatype specification
Cause: There was both a datatype, and an anonymous datatype declaration found.
Action: Correct the specification.
ORA-03120: two-task conversion routine: integer overflow
ORA-03121: no interface driver connected - function not performed
ORA-03122: attempt to close ORACLE-side window on user side
ORA-03123: operation would block
Cause: This is a status code that indicates that the operation cannot complete now.
Action: None; this is not an error. The operation should be retried again for
completion.
ORA-03124: two-task internal error
ORA-03125: client-server protocol violation
Cause: The application received a bad escape sequence from the server and may
indicate a problem with the client application user code.
ORA-03126: 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 default blocking operations or use a driver supporting non-blocking
operations.
ORA-03127: no new operations allowed until the active operation ends
Cause: An attempt was made to execute a new operation before the active nonblocking operation completed or a new operation was attempted before all the pieces
of a column were inserted or fetched.
Action: Execute the new operation after the non-blocking operation completes. If
piecewise binds/defines were done, execute the new operation after all the pieces
have been inserted or fetched.
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 appropriate OCI calls to change the
mode.
ORA-03129: the next piece to be inserted is required
Cause: The application performed a piecewise bind on a column.
Action: Provide the next piece of this bind variable.
ORA-03130: the buffer for the next piece to be fetched is required
Cause: The application performed a piecewise define on the column.
Action: Provide the next buffer for the next piece to be retrieved.
ORA-03131: an invalid buffer was provided for the next piece
Cause: The application either provided the length of the buffer for the next piece to be
zero or provided a null pointer.
Action: Verify if the buffer pointer for the next piece is null or if the length is zero.
ORA-03132: two-task default value overflow
Cause: The default value specified for a record field was too large.
Action: Change the default value to fit the field size.
ORA-03134: Connections to this server version are no longer supported.
Cause: An attempt was made to connect to an Oracle server of older version.
Action: Please refer to documentation for more details.
ORA-03135: connection lost contact
Cause: 1) Server unexpectedly terminated or was forced to terminate. 2) Server timed
out the connection.
Action: 1) Check if the server session was terminated. 2) Check if the timeout
parameters are set properly in sqlnet.ora.
ORA-03136: inbound connection timed out
Cause: Inbound connection was timed out by the server because user authentication
was not completed within the given time specified by
SQLNET.INBOUND_CONNECT_TIMEOUT or its default value
ORA-02100 to ORA-04099 61-47
Action: 1) Check SQL*NET and RDBMS log for trace of suspicious connections. 2)
Configure SQL*NET with a proper inbound connect timeout value if necessary.
ORA-03137: TTC protocol internal error : [string] [string] [string] [string] [string]
[string] [string] [string]
Cause: TTC protocol internal error.
ORA-03138: Connection terminated due to security policy violation
Cause: Connection was terminated due to a security policy violation.
Action: Contact the Database Administrator
ORA-03139: This OCI call has been disabled by the DBA
Cause: The SEC_DISABLE_OLDER_ORACLE_RPCS initialization parameter was
enabled.
Action: Contact the Database Administrator
ORA-03140: I/O operation in progress
Cause: The current I/O operation was not complete. The error is typically returned
from vectored and/or asynchronous I/O calls.
Action: Perform the necessary operation to complete or abort the current I/O.
ORA-03141: I/O request queue full
Cause: The I/O request queue was full and no more requests could be queued.
Action: Perform the proper operations to complete part or all of the current inprogress I/O requests.
ORA-03142: Session ID: number Serial number: number
Cause: Connection was lost for the specified session and serial number. This is either
due to session being killed or network problems.
Action: Reconnect and if error persists, contact Oracle Support Services.
ORA-03143: Process ID: string Thread ID: string
Cause: Connection was lost for the specified process ID and thread ID. This is either
due to session being killed or network problems.
ORA-03144: Process ID: string
Cause: Connection was lost for the specified process ID. This is either due to session
being killed or network problems.
ORA-03145: I/O streaming direction error
Cause: Attempted to PUT data when GET streaming was in progress or attempted to
GET data when PUT streaming was in progress.
Action: Complete current stream read or write I/O before attempting I/O in reverse
direction.
ORA-03146: Invalid buffer length for TTC field
Cause: A corrupt Two-Task Common (TTC) packet was received.
Action: This is a internal protocol error. Contact Oracle Support Services.
ORA-03147: Missing mandatory TTC field

Cause: A corrupt Two-Task Common (TTC) packet was received.
Action: This is an internal protocol error. Contact Oracle Support Services.
ORA-03148: OCI_ATTR_ROW_COUNT cannot return a row count exceeding
UB4MAXVAL. The actual row count is [string]
Cause: The row count was larger than UB4MAXVAL. OCI clients using
OCI_ATTR_ROW_COUNT cannot see row counts larger than UB4MAXVAL.
Action: Upgrade Oracle client to version 12 client libraries or higher and use
OCI_ATTR_UB8_ROW_COUNT instead.
ORA-03149: Invalid Oracle error code
Cause: An invalid Oracle error code was received by the server.
Action: This is an internal protocol error. Contact Oracle Support Services.
ORA-03150: end-of-file on communication channel for database link
Cause: The connection between the client and the remote server process was broken.
Action: Look in the alert.log file of the remote server for any errors. Also, check to see
whether the remote server process is dead and whether a trace file was generated at
failure time.
ORA-03160: An invalid client operation was requested by the server
Cause: You are using an Oracle client application linked with libraries with lower
version than the current server version.
Action: Upgrade client libraries to be same as or higher than the server version.
ORA-03170: deadlocked on readable physical standby (undo segment string)
Cause: A new undo segment was added. A query can occasionally deadlock when
issued around the time an undo segment is added and used immediately on the
primary.
Action: Retry the query. Avoid creating new undo segments when using standby as a
regular part of operation.
ORA-03171: Recovery was terminated during query execution
Cause: Recovery was terminated. A query can ocassionally deadlock when recovery
is terminated because it needs a block with changes that are made after the point at
which recovery was terminated.
Action: Retry the query. Avoid cancelling recovery on standby.
ORA-03172: STANDBY_MAX_DATA_DELAY of string seconds exceeded
Cause: Standby recovery fell behind the STANDBY_MAX_DATA_DELAY
requirement.
Action: Tune recovery and retry the query later, or switch to another standby
database within the data delay requirement.
ORA-03173: Standby may not be synced with primary
Cause: ALTER SESSION SYNC WITH PRIMARY did not work because either the
standby was not synchronous or in a data-loss mode with regard to the primary, or
the standby recovery was terminated.
Action: Make the standby synchronous and no-data-loss with regard to the primary.
Make the standby recovery active.
ORA-02100 to ORA-04099 61-49
ORA-03174: STANDBY_MAX_DATA_DELAY does not apply to SYS users

Cause: ALTER SESSION SET STANDBY_MAX_DATA_DELAY did not work for SYS
users.
Action: Issue ALTER SESSION SET STANDBY_MAX_DATA_DELAY for non-SYS
users.
ORA-03175: parameter string mismatch
Cause: The value of the %s parameter was not the same in all instances.
Action: Check %s in all instances.
ORA-03176: string only works on an open physical standby database
Cause: The database was not an open physical standby database.
Action: Issue the command on an open physical standby database.
ORA-03177: enable read-only violation logging
ORA-03178: duplicate SESSION or GLOBAL specifications
Cause: Duplicate SESSION or GLOBAL specifications were specified.
ORA-03179: NOCACHE or ORDER sequences cannot be accessed from Active Data
Guard standby
Cause: NOCACHE or ORDER sequences were not supported for Active Data Guard
standby.
Action: Alter the sequence properties.
ORA-03180: Sequence values cannot be allocated for Oracle Active Data Guard
standby.
Cause: Connection to the corresponding primary database failed. The primary
database might be down.
Action: Try again later.
ORA-03181: Sequence object no longer exists for Oracle Active Data Guard
standby.
Cause: The sequence object might have been dropped by the primary database.
Action: Check the sequence status on the primary database.
ORA-03182: The sequence object is no longer a global sequence for Oracle Active
Data Guard standby database.
Cause: The sequence object might have been altered by the primary database.
Action: Check the sequence status on the primary database.
ORA-03200: the segment type specification is invalid
Cause: segment type is not TABLE, INDEX, or CLUSTER
Action: use a correct segment type
ORA-03201: the group number specification is invalid
Cause: the freelist group number was either negative or larger than the the number of
freelist groups in the segment
Action: use a correct group number
ORA-03202: the scan limit specification is invalid

Cause: the scan limit did not have a positive integer value the number of freelist
groups in the segment
Action: use a correct scan limit
ORA-03203: concurrent update activity makes space analysis impossible
Cause: high volume of user updates interfere with the space analysis
Action: retry the command or lock the underlying objects
ORA-03204: the segment type specification should indicate partitioning
Cause: partition name is specified for the space analysis, but the object type does not
indicate parttitioning
Action: specify PARTITION in the segment type, if the object is partitioned,
otherwise, omit the partition name
ORA-03205: partition name is required when partitioned type is specified
Cause: partition name is not specified for the space analysis, but the object type
indicates parttitioning
Action: specify partition name, if the object is partitioned, otherwise, specify a nonpartitioned type
ORA-03206: maximum file size of (string) blocks in AUTOEXTEND clause is out of
range
Cause: The maximum file size for an autoextendable file has exceeded the maximum
number of blocks allowed.
Action: Reduce the size and retry.
ORA-03207: subpartitioned type must be specified for composite object
Cause: partition type is specified for the space analysis, but the object type indicates
composite partitioning
Action: specify subpartition name and subpartition type
ORA-03208: partitioned type must be specified for a non-composite object
Cause: subpartition type is specified for the space analysis, but the object type
indicates non-composite partitioning
Action: specify partition name and partition type
ORA-03209: DBMS_ADMIN_PACKAGE invalid file/block specification
Cause: The value of file number or block number is outside of limits or inconsistent
Action: Fix the file number/block number value
ORA-03210: DBMS_ADMIN_PACKAGE invalid option specification
Cause: The value of one of the option parameters is incorrect
Action: Fix the option value
ORA-03211: The segment does not exist or is not in a valid state
Cause: The segment specified in the DBMS_SPACE_ADMIN or DBMS_SPACE
operation does not exist or is not in a state appropriate for this operation
Action: Fix the segment specification, or put the segment in the appropriate state.
ORA-02100 to ORA-04099 61-51
ORA-03212: Temporary Segment cannot be created in locally-managed tablespace

Cause: Attempt to create a temporary segment for sort/hash/lobs in in permanent
tablespace of kind locally-managed
Action: Alter temporary tablespace of user to a temporary tablespace or a dictionarymanaged permanent tablespace
ORA-03213: Invalid Lob Segment Name for DBMS_SPACE package
Cause: The Lob Segment specified in the DBMS_SPACE operation does not exist.
Action: Fix the Segment Specification
ORA-03214: File Size specified is smaller than minimum required
Cause: File Size specified for add/resize datafile/tempfile does not allow for the
minimum required of one allocation unit.
Action: Increase the specification for file size
ORA-03215: File Size specified for resize is too small
Cause: File Size specified for resize datafile/tempfile causes bitmap control structures
to overlap
Action: Increase the specification for file size
ORA-03216: Tablespace/Segment Verification cannot proceed
Cause: Corruptions detected during verification whch cannot be dealt with
Action: Do manual verification
ORA-03217: invalid option for alter of TEMPORARY TABLESPACE
Cause: invalid option for alter of temporary tablespace was specified
Action: Specify one of the valid options: ADD TEMPFILE, TEMPFILE ONLINE,
TEMPFILE OFFLINE
ORA-03218: invalid option for CREATE/ALTER TABLESPACE
Cause: invalid option for create/alter tablespace of type locally-managed
Action: Specify one of the valid options.
ORA-03219: Tablespace 'string' is dictionary-managed, offline or temporary
Cause: Operation which is only applicable to permanent, online, locally-managed
tablespaces is specified for a tablespace which is either dictionary-managed, offline or
temporary
Action: Reissue operation for a different tablespace, mount the tablespace or do not
issue it at all, since it does not apply for the given tablespace
ORA-03220: DBMS_ADMIN_PACKAGE required parameter is NULL or missing
Cause: Some of the procedures was called with missing or NULL parameters
Action: Specify the missing parameter
ORA-03221: Temporary tablespaces and temporary segments must have standard
block size
Cause: An attempt was made to do one of the following : (1) create a temporary
tablespace with a non-standard block size or, (2) alter an existing permanent
tablespace of non-standard block size to a temporary tablespace or, (3) issue a DDL
statement that would result in the creation of a temporary segment in a tablespace of
non-standard block size.
Action: (1) If creating a temporary tablespace, do not specify a block size different
from the standard block size. (2) If altering an existing permanent tablespace to a
temporary tablespace, ensure that it is of standard block size. (3) Ensure that the
user's temporary tablespace is a tablespace having the standard block size.
ORA-03222: average row size and row count must be greater than zero
Cause: Either a bad value passed to dbms_space.create_table_cost() or explain plan
did not pass through size information.
Action: Check the row size parameter in dbms_space.create_table_cost(). For explain
plan, make sure statistics have been computed for all source tables in the CREATE
TABLE AS SELECT statement.
ORA-03223: Bitmap index block addressable limitation reached
Cause: The limitation of addressability of BMIB (Bitmap Index Block) was reached for
the current blocksize.
Action: If the segment size has grown greater than addressability of BMIB (Bitmap
Index Block), do the following: (1) Partition the table. (2) Move the segment to a
tablespace having bigger blocksize.
ORA-03230: segment only contains string blocks of unused space above high water
mark
Cause: Attempt to preserve too many blocks.
Action: reduce the KEEP amount.
ORA-03231: the INITIAL extent may not be deallocated
Cause: Attempt to deallocate space from the segment which was truncated prior to
the 7.3 release.
Action: increase the KEEP amount, or truncate the segment, and reissue the
command.
ORA-03233: unable to extend table string.string subpartition string by string in
tablespace string
Cause: Failed to allocate an extent for table subpartition segment in tablespace.
ORA-03234: unable to extend index string.string subpartition string by string in
tablespace string
Cause: Failed to allocate an extent for index subpartition segment in tablespace.
ORA-03235: max # extents (string) reached in table string.string subpartition string
Cause: A table subpartition tried to extend past maxextents
ORA-03236: max # extents (string) reached in index string.string subpartition string
Cause: An index subpartition tried to extend past maxextents
ORA-02100 to ORA-04099 61-53
ORA-03237: Initial Extent of specified size cannot be allocated in tablespace (string)

Cause: Too large a size for an initial extent due to freelist group specification
Action: Reduce number of freelist groups specified for segment
ORA-03238: unable to extend LOB segment string.string subpartition string by
string in tablespace string
Cause: An attempt was made to allocate an extent for LOB subpartition segment in
tablespace, but the extent could not be allocated because there is not enough space in
the tablespace indicated.
Action: Use the ALTER TABLESPACE ADD DATAFILE statement to add one or
more files to the tablespace indicated.
ORA-03239: maxextents (string) reached in LOB segment string.string subpartition
string
Cause: A LOB subpartition segment tried to extend past maxextents.
Action: If maxextents is less than the system maximum, raise it. Otherwise, recreate
the subpartition with larger INITIAL, NEXT, or PCTINCREASE parameters.
ORA-03240: User's temporary tablespace same as tablespace being migrated
Cause: Users default temporary tablespace must be different from the tablespace
being migrated.
Action: alter users default temporary tablespace to be different.
ORA-03241: Invalid unit size
Cause: User specified an invalid unit size for the tablespace
Action: Specify the correct unit size. To estimate unit size please refer to Oracle Server
Administrator's Guide.
ORA-03242: Tablespace migration retried 500 times
Cause: For migration to complete, temporary segments should not be present in the
tablespace at the time of migration.
Action: Avoid migrating the tablespace when there is heavy temporary segment
creation going on as with object drops.
ORA-03243: destination dba overlaps with existing control information
Cause: Cannot overlap control information during relocation
Action: Please chose another destination address
ORA-03244: No free space found to place the control information
Cause: During migration of tablespace found no place to put the control information.
If during bitmaps relocation, found no space at the specified destination.
Action: If during migration, add more space to the tablespace and retry migration. If
during bitmaps relocation, specify a destination address where there is enough free
space.
ORA-03245: Tablespace has to be dictionary managed, online and permanent to be
able to migrate
Cause: Tablespace was not dictionary managed or online or permanent.
Action: Make sure the tablespace is online, permanent and dictionary managed
ORA-03246: Invalid block number specified

Cause: Control information cannot be placed at the specified dba either because the
block number specified is beyond the file end or the file is not large enough to
accomodate the control information at that location
Action: specify a correct block number
ORA-03247: Invalid block number specified
Cause: Relocation of bitmaps to the said destination will make the tablespace self
descriptive
Action: Choose another destination dba.
ORA-03248: Too much of segment creation activity during migration
Cause: Temporary segments were attempted to be created during migration
Action: The error is signalled after retrying migration for 500 times. Run migration
when there is less of segment creation activity is going on.
ORA-03249: Uniform size for auto segment space managed tablespace should have
atleast string blocks
Cause: For the given blocksize, uniform size specified is insufficient
Action: Specify larger extent size and retry
ORA-03250: Cannot mark this segment corrupt
Cause: This segment cannot be marked corrupt because it contains data dictionary
objects
Action: Check the segment information and reissue the command.
ORA-03251: Cannot issue this command on SYSTEM tablespace
Cause: It is not permitted to migrate SYSTEM tablespace from locally managed
format to dictionary managed format or relocate bitmaps.
Action: Check the tablespace name and procedure name
ORA-03252: initial extent size not enough for LOB segment
Cause: Fatblock size of LOB segment is too big to fit into the initial extent.
Action: Specify a smaller fatblock size or create the LOB segment in other tablespaces
with bigger initial extent size.
ORA-03254: unable to execute the sql in read only database
Cause: Unable to create a consistent snapshot of the object in a read only database.
Transaction recovery must be performed before opening the database read only.
Action: Open the database read write, allow dead transaction recovery to complete
and then open the database read only.
ORA-03261: the tablespace string has only one file
Cause: Dropping file from ts which has a single file extent.
Action: Cannot make a tablespace fileless
ORA-03262: the file is non-empty
Cause: Trying to drop a non-empty datafile
Action: Cannot drop a non empty datafile
ORA-02100 to ORA-04099 61-55
ORA-03263: cannot drop the first file of tablespace string

Cause: Trying to drop the first datafile with which ts is created
Action: Cannot drop the first datafile with which ts is created
ORA-03264: cannot drop offline datafile of locally managed tablespace
Cause: Trying to drop offline datafile in lmts
Action: Try to drop file afetr making it online
ORA-03274: both ALLOCATE EXTENT and DEALLOCATE UNUSED options are
specified
Cause: The DEALLOCATE option and the ALLOCATE option are specified in the
same command.
Action: Choose one of the options or issue two separate commands.
ORA-03275: duplicate DEALLOCATE option specification
Cause: The DEALLOCATE UNUSED option to ALTER TABLE or ALTER INDEX is
ORA-03276: duplicate ALLOCATE EXTENT option specification
Cause: The ALLOCATE EXTENT option to ALTER TABLE or ALTER INDEX is
ORA-03277: invalid SIZE specified
ORA-03278: duplicate ALLOCATE EXTENT option specification
Cause: An option (DATAFILE, 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: invalid DATAFILE filename specified
Cause: A character string literal is expected, but not found.
Action: Specify filenames using character string literals.
ORA-03281: invalid ALLOCATE EXTENT option
Cause: An option other than DATAFILE, SIZE or INSTANCE was specified.
Action: Remove invalid option and retry the command.
ORA-03282: missing ALLOCATE EXTENT option
Cause: No ALLOCATE EXTENT options were specified.
Action: Specified one or more of the following options: DATAFILE, SIZE or
INSTANCE.
ORA-03283: specified datafile string does not exist

Cause: The datafile does not exist
Action: Retry the option with the correct datafile
ORA-03284: datafile or tempfile string is not a member of tablespace string
Cause: The specified datafile or tempfile did not belong to the tablespace that the
object resides in.
Action: Retry the option with the correct datafile or tempfile.
ORA-03286: ALLOCATE EXTENT not valid for HASH CLUSTERS
Cause: The cluster is a hash cluster, and can not use the allcoate extent option.
Action: n/a
ORA-03287: invalid FREELIST GROUP specified
Cause: The specified FREELIST GROUP number is invalid
Action: Choose a number between 1 and # freelist groups for this object
ORA-03288: both FREELIST GROUP and INSTANCE parameters may not be
specified
Cause: Both FREELIST GROUP and INSTANCE were specified in clause
Action: Remove one of the two parameters
ORA-03289: partition name and segment type do not match
Cause: Partition name and segment type specified for space analysis do not match
Action: Specify type PARTITION if the object is partitioned, specify SUBPARTITION
if the object is composite
ORA-03290: Invalid truncate command - missing CLUSTER or TABLE keyword
Cause: Invalid object specification given.
Action: Either specify TRUNCATE CLUSTER or TRUNCATE TABLE
ORA-03291: Invalid truncate option - missing STORAGE keyword
Cause: Expected STORAGE keyword
Action: Either specify DROP STORAGE or REUSE STORAGE
ORA-03292: Table to be truncated is part of a cluster
Cause: The table being truncated is a member of a cluster.
Action: Either use TRUNCATE CLUSTER or DROP TABLE
ORA-03293: Cluster to be truncated is a HASH CLUSTER
Cause: Only INDEX CLUSTERS can be truncated.
Action: Drop and recreate the HASH CLUSTER instead of using truncate.
ORA-03296: cannot resize datafile - file string not found
Cause: The specified datafile is not available for resizing.
Action: Ensure that the datafile name is valid, and if so, ensure the file is accessible.
ORA-03297: file contains used data beyond requested RESIZE value
Cause: Some portion of the file in the region to be trimmed is currently in use by a
database object
ORA-02100 to ORA-04099 61-57
Action: Drop or move segments containing extents in this region prior to resizing the
file, or choose a resize value such that only free space is in the trimmed.
ORA-03298: cannot shrink datafile - file string is under hot backup
Cause: Attempt to shrink a datafile while it is under hot backup. This is not allowed.
Action: Retry shrinking the file after the hot backup completes.
ORA-03299: cannot create dictionary table string
Cause: A dictionary table is created upon the first execution of the command 'alter
database datafile autoextend on' for a database. This operation did not succeed. The
most probable cause for this is insufficient space in the system tablespace.
Action: See action for next error message in 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 specifying values whose sum is <= 100
ORA-04001: sequence parameter string must be an integer
Cause: %s (a sequence parameter) specified was not an integer
Action: create the sequence, giving the specified parameter an integer value
ORA-04002: INCREMENT must be a non-zero integer
Cause: a sequence increment was specified to be zero
Action: specify the increment to be a non-zero value
ORA-04003: sequence parameter string exceeds maximum size allowed (string
digits)
Cause: %s (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 that is less than MAXVALUE
ORA-04005: INCREMENT must be less than MAXVALUE minus MINVALUE
Cause: the INCREMENT specified is >= MAXVALUE-MINVALUE
Action: specify an INCREMENT that is < MAXVALUE-MINVALUE
ORA-04006: START WITH cannot be less than MINVALUE
Cause: the given starting value is less than MINVALUE
Action: make sure that the starting value is >= MINVALUE
ORA-04007: MINVALUE cannot be made to exceed the current value
Cause: the given MINVALUE would be greater than the current value
Action: always make sure that MINVALUE is <= the current value
ORA-04008: START WITH cannot be more than MAXVALUE
Cause: the starting value would be larger than MAXVALUE
Action: make sure that the starting value is less than MAXVALUE
ORA-04009: MAXVALUE cannot be made to be less than the current value

Cause: the current value exceeds the given MAXVALUE
Action: make sure that the new MAXVALUE is larger than the current value
ORA-04010: the number of values to CACHE must be greater than 1
Cause: the value in the CACHE clause was one
Action: specify NOCACHE, or a value larger than one
ORA-04011: sequence string must range between string and string
Cause: the value specified for one of the sequence parameters exceeds limits
Action: specify parameter within these limits
ORA-04012: object is not a sequence
Cause: the object specified cannot have sequence ddl's performed on it
Action: re-enter the statement being careful with the spelling of the name
ORA-04013: number to CACHE must be less than one cycle
Cause: number to CACHE given is larger than values in a cycle
Action: enlarge the cycle, or cache fewer values
ORA-04014: descending sequences that CYCLE must specify MINVALUE
Cause: sequences that cycle must have their wrap-wrap specified
Action: re-create the sequence, specifying its wrap-value
ORA-04015: ascending sequences that CYCLE must specify MAXVALUE
Cause: sequences that cycle must have their wrap-wrap specified
Action: re-create the sequence, specifying its wrap-value
ORA-04016: sequence string no longer exists
Cause: sequence was dropped while processing its next value.
Action: re-create the sequence
ORA-04017: invalid value string (length = string) for parameter
MAX_DUMP_FILE_SIZE
Cause: The string supplied for the parameter MAX_DUMP_FILE_SIZE was not an
integer, an integer followed by 'K', 'M', or 'G', nor the special value UNLIMITED.
Action: Provide a proper value for this parameter.
ORA-04020: deadlock detected while trying to lock object
Cause: While trying to lock a library object, a deadlock is detected.
ORA-04021: timeout occurred while waiting to lock object
Cause: While waiting to lock a library object, a timeout occurred.
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.
ORA-02100 to ORA-04099 61-59

ORA-04023: Object stringstringstringstringstring could not be validated or
authorized
Cause: A number of attempts were made to validate or authorize an object but failed.
Action: Please report this error to Oracle Support Services.
ORA-04024: self-deadlock detected while trying to mutex pin cursor string
Cause: While trying to mutex pin a cursor, a self-deadlock is detected.
ORA-04025: maximum allowed library object lock allocated for
Cause: Too many active locks for the object has been allocated. This error can be a
result of too many cursors kept open per session.
Action: Close cursors, reduce session_cached_cursors value.
ORA-04027: self-deadlock during automatic validation for object string.string
Cause: An attempt was made to validate an invalidated object but it failed because of
a self-deadlock.
Action: Identify the root cause of the self-deadlock and take corrective action, e.g.
compile the invalidated object separately.
ORA-04028: cannot generate diana for object stringstringstringstringstring
Cause: Cannot generate diana for an object because of lock conflict.
Action: Please report this error to your support representative.
ORA-04029: error ORA-string occurred when querying stringstringstring
Cause: The table or view being queried might be missing. The error number indicates
the error.
ORA-04030: out of process memory when trying to allocate string bytes
(string,string)
Cause: Operating system process private memory was exhausted.
Action: n/a
ORA-04031: unable to allocate string bytes of shared memory
("string","string","string","string")
Cause: More shared memory is needed than was allocated in the shared pool or
Streams pool.
Action: If the shared pool is out of memory, either use the DBMS_SHARED_POOL
package to pin large packages, reduce your use of shared memory, or increase the
amount of available shared memory by increasing the value of the initialization
parameters SHARED_POOL_RESERVED_SIZE and SHARED_POOL_SIZE. If the
large pool is out of memory, increase the initialization parameter
LARGE_POOL_SIZE. If the error is issued from an Oracle Streams or XStream
process, increase the initialization parameter STREAMS_POOL_SIZE or increase the
capture or apply parameter MAX_SGA_SIZE.
ORA-04032: pga_aggregate_target must be set before switching to auto mode

Cause: attempt to set workarea_size_policy to AUTO while pga_aggregate_target is
not specified
Action: before setting workarea_size_policy, set pga_aggregate_target to a value
representing the total private memory available to the instance. This total is generally
the total physical memory available in the system minus what is needed for the SGA
minus what is needed for the operating system (e.g. 500MB)
ORA-04033: Insufficient memory to grow pool
Cause: The system had insufficient memory to grow the pool to the specified size.
Action: Specify a smaller value to grow the pool.
ORA-04034: unable to shrink pool to specified size
Cause: The pool could not shrink to the specified size as it could not free memory.
Action: Specify a larger value to which to shrink the pool to.
ORA-04035: unable to allocate string bytes of shared memory in shared object cache
"string" of size "string"
Cause: More shared memory is needed than was allocated in the shared object cache.
Action: n/a
ORA-04036: PGA memory used by the instance exceeds
PGA_AGGREGATE_LIMIT
Cause: Private memory across the instance exceeded the limit specified in the
PGA_AGGREGATE_LIMIT initialization parameter. The largest sessions using
Program Global Area (PGA) memory were interrupted to get under the limit.
Action: Increase the PGA_AGGREGATE_LIMIT initialization parameter or reduce
memory usage.
ORA-04041: package specification must be created first before creating package
body
Cause: Attempt to create a package body before creating its package specification.
Action: Create the package specification first before creating the package body.
ORA-04042: procedure, function, package, or package body does not exist
Cause: Attempt to access a procedure, function, package, or package body that does
not exist.
Action: Make sure the name is correct.
ORA-04043: object string does not exist
Cause: An object name was specified that was not recognized by the system. There
are several possible causes: - An invalid name for a table, view, sequence, procedure,
function, package, or package body was entered. Since the system could 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 a cluster, or some other object that
cannot be renamed.
Action: Check the spelling of the named object and rerun the code. (Valid names of
tables, views, functions, etc. can be listed by querying the data dictionary.)
ORA-02100 to ORA-04099 61-61
ORA-04044: procedure, function, package, or type is not allowed here

Cause: A procedure, function, or package was specified in an inappropriate place in a
statement.
Action: Make sure the name is correct or remove it.
ORA-04045: errors during recompilation/revalidation of string.string
Cause: This message indicates the object to which the following errors apply. The
errors occurred during implicit recompilation/revalidation of the object.
Action: Check the following errors for more information, and make the necessary
corrections to the object.
ORA-04046: results of compilation are too large to support
Cause: Attempt to compile and store a large stored procedure that results in
compilation data that is too large for the system to support or store.
Action: Reduce the size of the store procedure by splitting it into smaller stored
procedures.
ORA-04047: object specified is incompatible with the flag specified
Cause: The object type implied by the flag does not match the type of object specified.
Action: Specify the correct object, or use the appropriate flag
ORA-04050: invalid or missing procedure, function, or package name
Cause: The required procedure, function, or package name is invalid or missing.
ORA-04051: user string cannot use database link string.string
Cause: During forwarding of a remote object access, an attempt was made to use a
non-existent database link or one owned by a user other than the logon user or
PUBLIC.
Action: Change your database link structure so that all indirect remote accesses are
done from the same userid that originates the request.
ORA-04052: error occurred when looking up remote object
Cause: An error occurred when trying to look up a remote object.
Action: Fix the error. Make sure the remote database system has run CATRPC.SQL to
create necessary views used for querying or looking up objects stored in the database.
ORA-04053: error occurred when validating remote object
Cause: An error occurred when trying to validate a remote object.
Action: Fix the error. Make sure the remote database system has run CATRPC.SQL to
create necessary views used for querying or looking up objects stored in the database.
ORA-04054: database link string does not exist
Cause: During compilation of a PL/SQL block, an attempt was made to use a nonexistent database link.
Action: Either use a different database link or create the database link.
ORA-04055: Aborted: "string" formed a non-REF mutually-dependent cycle with

"string".
Cause: This compilation was aborted because the library unit that was compiled
would have formed a non-REF mutually-dependent cycle with some other library
units. This happens when an attempt is made to compile types that have attributes of
other types that may participate in a cycle with this type. Example: create type t1;
create type t2 (a t1); create type t1 (a t2);
Action: Break the cycle (possibly by adding a REF or by using another type).
ORA-04060: insufficient privileges to execute string
Cause: Attempt to execute a stored procedure without sufficient privileges.
Action: Get necessary privileges.
ORA-04061: existing state of string has been invalidated
Cause: Attempt to resume the execution of a stored procedure using the existing state
which has become invalid or inconsistent with the stored procedure because the
procedure has been altered or dropped.
Action: Try again; this error should have caused the existing state of all packages to
be re-initialized.
ORA-04062: string of string has been changed
Cause: Attempt to execute a stored procedure to serve an RPC stub which specifies a
timestamp or signature that is different from the current timestamp/signature of the
procedure.
Action: Recompile the caller in order to pick up the new timestamp.
ORA-04063: string has errors
Cause: Attempt to execute a stored procedure or use a view that has errors. 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's defining query
to a non-existent table. Can also be a table which has references to non-existent or
inaccessible types.
Action: Fix the errors and/or create referenced objects as necessary.
ORA-04064: not executed, invalidated string
Cause: Attempt to execute a stored procedure that has been invalidated.
Action: Recompile it.
ORA-04065: not executed, altered or dropped string
Cause: Attempt to execute a stored procedure that has been altered or dropped thus
making it not callable from the calling procedure.
Action: Recompile its dependents.
ORA-04066: non-executable object, string
Cause: Attempt to execute a non-procedure.
ORA-04067: not executed, string does not exist
Cause: Attempt to execute a non-existent stored procedure.
ORA-02100 to ORA-04099 61-63
ORA-04068: existing state of packagesstringstringstring has been discarded

Cause: One of errors 4060 - 4067 when attempt to execute a stored procedure.
Action: Try again after proper re-initialization of any application's state.
ORA-04069: cannot drop or replace a library with table dependents
Cause: An attempt was made to drop or replace a library that has dependents. There
could be a table which depends on type which depends on the library being dropped.
Action: Drop all table(s) depending on the type, then retry.
ORA-04070: invalid trigger name
Cause: An invalid trigger name was specified.
Action: Verify that trigger name is not a reserved keyword.
ORA-04071: missing BEFORE, AFTER or INSTEAD OF keyword
Cause: The trigger statement is missing the BEFORE/AFTER/INSTEAD OF clause.
Action: Specify either BEFORE, AFTER or INSTEAD OF.
ORA-04072: invalid trigger type
Cause: An invalid trigger type was given.
Action: Specify either INSERT, UPDATE or DELETE.
ORA-04073: column list not valid for this trigger type
Cause: A column list was specified for a non-update trigger type.
Action: Remove the column list.
ORA-04074: invalid REFERENCING name
Cause: An invalid name was given in the referencing clause.
Action: Verify the referencing name is not a reserved word.
ORA-04075: invalid trigger action
Cause: An statement was given for the trigger action.
Action: Re-specify the trigger action.
ORA-04076: invalid NEW or OLD specification
Cause: An invalid NEW or OLD specification was given for a column.
Action: Re-specify 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.
Action: Remove the when clause or specify for each row.
ORA-04078: OLD and NEW values cannot be identical
Cause: The referencing clause specifies identical values for NEW and OLD.
Action: Re-specify either the OLD or NEW referencing value.
ORA-04079: invalid trigger specification
Cause: The create TRIGGER statement is invalid.
Action: Check the statement for correct syntax.
ORA-04080: trigger 'string' does not exist

Cause: The TRIGGER name is invalid.
Action: Check the trigger name.
ORA-04081: trigger 'string' already exists
Cause: The TRIGGER name or type already exists.
Action: Use a different trigger name or drop the trigger which is of 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 any new or old references.
ORA-04083: invalid trigger variable 'string'
Cause: The variable referenced in the trigger body is invalid.
Action: See the manual for valid trigger variable types.
ORA-04084: cannot change NEW values for this trigger type
Cause: New trigger variables can only be changed in before row insert or update
triggers.
Action: Change the trigger type or remove the variable reference.
ORA-04085: cannot change the value of an OLD reference variable
Cause: Old values can only be read and not changed.
Action: Do not attempt to change an old variable.
ORA-04086: trigger description too long, move comments into triggering code
Cause: The 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 large comment, move that
ORA-04087: cannot change the value of ROWID reference variable
Cause: Rowid's can only be read and not changed.
Action: Do not attempt to change an rowid value.
ORA-04088: error during execution of trigger 'string.string'
Cause: A runtime error occurred during execution of a trigger.
Action: Check the triggers which 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.
ORA-04090: 'string' specifies same table, event and trigger time as 'string'
Cause: Trigger is of duplicate event and trigger time.
Action: Combine the triggering information into one trigger which is fired at the
given time.
ORA-02100 to ORA-04099 61-65
ORA-04091: table string.string is mutating, trigger/function may not see it

Cause: A trigger (or a user defined plsql function that is referenced in this statement)
attempted to look at (or modify) a table that was in the middle of being modified by
the statement which fired it.
Action: Rewrite the trigger (or function) so it does not read that table.
ORA-04092: cannot string in a trigger
Cause: A trigger attempted to commit or rollback.
Action: Rewrite the trigger so it does not commit or rollback.
ORA-04093: references to columns of type LONG are not allowed in triggers
Cause: A trigger attempted to reference a long column in the triggering table.
Action: Do not reference the long column.
ORA-04094: table string.string is constraining, trigger may not modify it
Cause: A trigger attempted to modify a table that was constraining for some
referential constraint of a parent SQL statement.
Action: n/a
ORA-04095: trigger 'string' already exists on another table, cannot replace it
Cause: Cannot replace a trigger which already exists on a different table than the one
being replaced.
Action: Drop the trigger with the same name and re-create it.
ORA-04096: trigger 'string' has a WHEN clause which is too large, limit 2K
Cause: A trigger's 'when' clause is limited to 2K for dictionary storage reasons. The
trigger being created exceeded that size.
Action: Use a smaller 'when' clause. Note, the trigger body could be used to perform
the same limiting action as the 'when' clause.
ORA-04097: DDL conflict while trying to drop or alter a trigger
Cause: An attempt was made to concurrently perform two DDL operations on a
trigger or trigger table.
Action: Investigate the new state of the trigger and retry the DDL operation, if still
appropriate.
ORA-04098: trigger 'string.string' is invalid and failed re-validation
Cause: A trigger was attempted to be retrieved for execution and was found to be
invalid. This also means that compilation/authorization failed for the trigger.
Action: Options are to resolve the compilation/authorization errors, disable the
trigger, or drop the trigger.
ORA-04099: trigger 'string' is valid but not stored in compiled form
Cause: A trigger was attempted to be retrieved for execution and was found to be
valid, but not stored. This may mean the an upgrade was done improperly from a
non-stored trigger release.
Action: Alter compile the trigger to create the trigger in stored form. Also, you may
want to review that a proper upgrade was done.
62
ORA-04930 to ORA-07499
ORA-04930: open sequence number failed or initial state is valid
Cause: Either Shared Sequence Number OS component was not installed properly, or
an MC hardware failure may have occurred or a previous instance was not shut down
properly.
Action: Verify that there are no background or foreground Oracle processes from a
previous instance on this node using the OS command ps -ef|grep <instance_name>.
Verify that there are no shared memory segments belonging to the user which owns
the Oracle installation by isuing the ipcs -b OS command. If there are shared memory
segments or processes still on the system, use svrmgrl to shutdown the instance with
the abort option. If the instance is not up, verify that the cluster software and/or the
hardware is installed and working. Log in as superuser and issue the cnxshow
command. Are all of the nodes in the cluster listed? Are they members of the cluster?
Is the communications between nodes okay? If the answer to any of these questions is
false, contact Digital's customer support organization.
ORA-04931: unable to set initial sequence number value
Cause: A call to the SSN failed to set the sequence number to its initial value, possibly
caused by an MC hardware problem.
Action: Verify that the MC hardware is functioning properly. If it is not, contact
Digital's customer support organization. If it is, contact Oracle support.
ORA-04932: increment or adjust of sequence number failed
Cause: A call to the SSN failed to increment the sequence number.
Action: Verify that the MC hardware is functioning properly. If it is not, contact
Digital's customer support organization. If it is, contact Oracle support.
ORA-04933: initial service identifier is non-zero
Cause: A valid service identifier existed before the sequence number service was
opened.
Action: Verify that the instance is completely shut down.
ORA-04934: unable to obtain the current sequence number
Cause: A call to the SSN failed to return its current value. Either there are many errors
occurring on the MC hardware, or the sequence number has become invalid and
cannot be validated.
Action: Verify that the MC hardware is functioning properly. If it is, contact Oracle
Support.
ORA-04935: unable to get/convert SCN recovery lock
Cause: A process has timed out trying to get or convert the SCN recovery lock.
Another process probably has the lock in EX or SHR mode, but is not releasing it.
ORA-04930 to ORA-07499 62-1

ORA-04940: unsupported optimization of Oracle binary, check alert log for more
info
Cause: ORACLE binary has been optimized with unsupported options or a required
option has not been used.
Action: Check the documentation for a list of supported and required flags for the
optimizing utility that you used to optimize ORACLE. Shutdown the instance,
optimize ORACLE again with supported combination of options and restart the
instance.
ORA-04941: required operating system patch needs to be applied
Cause: The operating system could not return the start time of a process.
Action: Check that the operating system kernel has been patched to return process
start time. Apply the required operating system patch and restart the instance.
ORA-06000: NETASY: port open failure
Cause: Autologin unable to open port
Action: Check log file for OS-specific error code
ORA-06001: NETASY: port set-up failure
Cause: Autologin unable to change port attributes
ORA-06002: NETASY: port read failure
Cause: Autologin unable to read from port
ORA-06003: NETASY: port write failure
Cause: Autologin unable to write to port
ORA-06004: NETASY: dialogue file open failure
Cause: Autologin unable to open dialogue file
Action: Check connect string for accuracy/typos
ORA-06005: NETASY: dialogue file read failure
Cause: Autologin unable to read dialogue file
ORA-06006: NETASY: dialogue execute failure
Cause: Expected response never received
Action: None
ORA-06007: NETASY: bad dialogue format
Cause: Dialogue file contains syntax error
Action: Correct the dialogue file
ORA-06009: NETASY: dialogue filename too long
Cause: Full file spec for dialogue file exceeds 64 bytes
Action: Amend connect string accordingly
62-2 Error Messages
ORA-06010: NETASY: dialogue file too long

Cause: Dialogue file exceeds 768 bytes in length
Action: Simplify dialogue (e.g. remove comments, redundant white space), or split
into two and link with "more" command
ORA-06011: NETASY: dialogue too long
Cause: One of two: 1. Dialogue contains more than 24 exchange blocks 2. Dialogue
send string exceeds 84 bytes in length
Action: Simplify dialogue or split into two and link with "more" command
ORA-06017: NETASY: message receive failure
Cause: Async driver gets I/O error while doing network read operation
Action: Check log file for OS-specific error code and contact your customer support
representative.
ORA-06018: NETASY: message send failure
Cause: Async driver gets I/O error while doing network write operation
Action: Check log file for OS-specific error code and contact your customer support
representative.
ORA-06019: NETASY: invalid login (connect) string
Cause: Syntax error in login string.
Action: Resubmit with correct string.
ORA-06020: NETASY: initialisation failure
Cause: Async driver unable to complete initialisation
ORA-06021: NETASY: connect failed
Cause: Async driver unable to establish connection with partner
ORA-06022: NETASY: channel open failure
Cause: no free channel [should never happen]
ORA-06023: NETASY: port open failure
Cause: Async driver unable to open port
ORA-06024: NETASY: VTM error
Cause: Virtual Terminal Manager unable to read/write to port
ORA-06025: NETASY: Configuration error
Cause: Async driver genned for server-only, but client service requested
ORA-06026: NETASY: port close failure
Cause: Async driver unable to close port
ORA-04930 to ORA-07499 62-3
ORA-06027: NETASY: channel close failure

Cause: Async driver unable to close channel
ORA-06028: NETASY: unable to intialise for logging
Cause: Async driver unable to initialise for logging I/O
ORA-06029: NETASY: port assignment failure
Cause: Async driver unable to assign port to channel [should never happen]
ORA-06030: NETDNT: connect failed, unrecognized node name
Cause: Node name specified in host string is unknown (probably misspelled)
Action: Retry with correct node name
ORA-06031: NETDNT: connect failed, unrecognized object name
Cause: Host string contains reference to object (which doesn't exist): @d:node-obj =>
object is ORDNobj; when node is VMS, the object is ORDNobj.COM when node is
UNIX, the object is ORDNobj @d:node::"task=obj" => object is obj; when node is VMS,
the object is obj.COM when node is UNIX, the object is obj
Action: Retry with correct object name or create the required object on host node
ORA-06032: NETDNT: connect failed, access control data rejected
Cause: Host string contains invalid username/password
Action: Retry with correct username/password
ORA-06033: NETDNT: connect failed, partner rejected connection
Cause: Connection with partner was made but was rejected.
Action: Contact your network administrator.
ORA-06034: NETDNT: connect failed, partner exited unexpectedly
Cause: Connection with host node was made but partner aborted
Action: Make sure object (see 06031, above) is working (for VMS run the command
file and make sure that the ORACLE server process starts up); sometimes happens
when the network/node is under stress - in this case a retry often works.
ORA-06035: NETDNT: connect failed, insufficient resources
Cause: Insufficient system resources are available to complete the connection; for
example, all DECnet channels are in use.
ORA-06036: NETDNT: connect failed, no response from object
ORA-06037: NETDNT: connect failed, node unreachable
Cause: Host node is down.
ORA-06038: NETDNT: connect failed, network driver not loaded
62-4 Error Messages
ORA-06039: NETDNT: connect failed

Cause: Connect failed for unexpected reason (see OSD error).
ORA-06040: NETDNT: invalid login (connect) string
Action: Resubmit with correct string.
ORA-06041: NETDNT: disconnect failed
Cause: Driver gets error while doing network close operation
ORA-06042: NETDNT: message receive failure
Cause: Driver gets I/O error while doing network read operation
ORA-06043: NETDNT: message send failure
Cause: Driver gets I/O error while doing network write operation
ORA-06044: NETDNT: connect failed, byte count quota exceeded
Cause: Connect failed because of insufficient byte count quota.
Action: Increase byte count quota.
ORA-06102: NETTCP: cannot allocate context area
Cause: Insufficient dynamic memory available for connection context area.
ORA-06105: NETTCP: remote host is unknown
Cause: Host name specified in the login (connect) string is unknown.
Action: Check spelling; make sure name is in the TCP/IP HOST file.
ORA-06106: NETTCP: socket creation failure
Cause: Process open file quota probably exceeded.
ORA-06107: NETTCP: ORACLE network server not found
Cause: No entry in SERVICES file for ORACLE server.
Action: Add ("orasrv") entry to the TCP/IP SERVICES file.
ORA-06108: NETTCP: connect to host failed
Cause: Connection attempt to remote host has failed. Probably means that the
SQL*Net TCP/IP server on the remote host is not up, or the host itself is not up (check
the latter by targeting it with Telnet).
Action: Start the SQL*Net TCP/IP server process on the remote host.
ORA-06109: NETTCP: message receive failure
Cause: I/O error occurred while attempting network read operation.
ORA-04930 to ORA-07499 62-5
ORA-06110: NETTCP: message send failure

Cause: I/O error occurred while attempting network write operation.
ORA-06111: NETTCP: disconnect failure
Cause: Error occurred while closing a socket.
ORA-06112: NETTCP: invalid buffer size
Cause: The buffer size specified in the login string exceeds the allowed maximum (of
4096).
Action: Re-submit with valid buffer size.
ORA-06113: NETTCP: Too many connections
Cause: The maximum no. of concurrently open connections has been reached.
Action: Exit an application with an open connection which is no longer required.
ORA-06114: NETTCP: SID lookup failure
Cause: From the remote host's SQL*Net TCP/IP server: the database SID, specified in
the login (connect) 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: unable to create ORACLE logicals
Cause: The host's SQL*Net TCP/IP server was unable to create the necessary logicals
required by the ORACLE server process. See the SQL*Net TCP/IP server log file for
more details.
ORA-06116: NETTCP: unable to create ORASRV process
Cause: The host's SQL*Net TCP/IP server was unable to create the ORACLE server
process. See the SQL*Net TCP/IP server log file for more details.
ORA-06117: NETTCP: unable to create ORASRV: quota exceeded
Cause: The host's SQL*Net TCP/IP server was unable to create the ORACLE server
process because of quota depletion.
Action: Increase quota allocations to the SQL*Net TCP/IP server process.
ORA-06118: NETTCP: unable to complete handshake with ORASRV
Cause: The ORACLE server process was started but failed to complete its
initialization.
ORA-06119: NETTCP: spurious client request
Cause: The host's SQL*Net TCP/IP server was unable to recognize this connection
request. See the SQL*Net TCP/IP server log file for more details.
ORA-06120: NETTCP: network driver not loaded
Cause: The TCP/IP network driver is not loaded.
62-6 Error Messages
Action: Check that the TCP/IP driver is loaded correctly.

ORA-06121: NETTCP: access failure
Cause: The host's SQL*Net TCP/IP server was unable to test the accessibility 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.
ORA-06122: NETTCP: setup failure
Cause: The host's SQL*Net TCP/IP server was unable to set up the appropriate
environment to service this connection request. See the SQL*Net TCP/IP server log
file for more details.
ORA-06123: NETTCP: cannot set KEEPALIVE
Cause: The host's SQL*Net TCP/IP server was unable to set the socket KEEPLIVE
option. See the SQL*Net TCP/IP server log file for more details.
ORA-06124: NETTCP: timeout waiting for ORASRV
Cause: The ORACLE server process was started but failed to respond after N secs.
Action: For heavily loaded systems this is not an uncommon occurrence. Increase the
value of N (the default is 30) by placing the following entry in the CONFIG.ORA file:
SQLNET ORASRV_WAIT = <no. of secs> which will come into effect the next time
the SQL*Net TCP/IP server is started.
ORA-06125: NETTCP: ORASRV exited unexpectedly
Cause: The ORACLE server process was started but exited unexpectedly. Possible
causes: 1. Insufficient quotas to run ORASRV 2. 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 of the form: ORA_SRVTnn_SID.OUT
Action: If appropriate action is not obvious from the ORASRV output file then contact
your customer support representative.
ORA-06126: NETTCP: ORASRV unable to open network connection
Cause: The ORACLE server process was started but was unable to open the socket
passed to it by TCPSRV.
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 username is unknown (to the host OS).
Action: Create new user account on host.
ORA-06128: NETTCP: unable to create mailbox
Cause: The host's SQL*Net TCP/IP server was unable to create a mailbox (needed for
IPC communication with the ORACLE server process). See the SQL*Net TCP/IP
server log file for more details.
ORA-04930 to ORA-07499 62-7
ORA-06129: NETTCP: unable to transfer socket ownership to ORASRV

Cause: The host's SQL*Net TCP/IP server was unable to transfer the network
communication handle to the ORACLE server process. See the SQL*Net TCP/IP
server log file for more details.
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 privilege - as determined by the contents of the Valid
Node Table (VNT), a component of the host's CONFIG.ORA.
Action: To grant access, add appropriate entry to the host's VNT.
ORA-06131: NETTCP: user access denied
Cause: The host's SQL*Net TCP/IP server rejected this connection request because the
client user(name) does not have access privilege - as determined by the contents of the
Username Mapping Table (UMT), a component of the host's CONFIG.ORA.
Action: To grant access, add appropriate entry to the host's UMT.
ORA-06132: NETTCP: access denied, wrong password
Cause: The host SQL*Net TCP/IP server rejected this connection request because the
client password did not match the host password.
Action: To grant access, get passwords in sync.
ORA-06133: NETTCP: file not found
Cause: The host's SQL*Net TCP/IP server could not find the SID mapping file
(specified in CONFIG.ORA) associated with this connection request.
Action: Check CONFIG.ORA for spelling; make correct entry.
ORA-06134: NETTCP: file access privilege violation
Cause: The host's SQL*Net TCP/IP server did not have READ/ EXECUTE
permission for the SID mapping file (specified in CONFIG.ORA) associated with this
connection request.
Action: Change protection on SID mapping file.
ORA-06135: NETTCP: connection rejected; server is stopping
Cause: The host's SQL*Net TCP/IP server rejected this connection request because it
is in the process of stopping.
Action: Re-start SQL*Net TCP/IP server.
ORA-06136: NETTCP: error during connection handshake
Cause: Network I/O failure occurred while communicating with the host's SQL*Net
TCP/IP server. See the SQL*Net TCP/IP server log file for more details.
62-8 Error Messages

ORA-06140: NETTCP: no such user
Cause: A proxy login connect attempt failed because the client username has no
counterpart on the host.
Action: n/a
ORA-06141: NETTCP: no privilege for user
Cause: A proxy login connect attempt failed because the SQL*Net TCP/IP server had
insufficient privileges to access the proxy account.
Action: Change account protection; change server privilges.
ORA-06142: NETTCP: error getting user information
Cause: A proxy login connect attempt failed because the SQL*Net TCP/IP server was
unable to access the proxy account. See the SQL*Net TCP/IP server log file for more
details.
ORA-06143: NETTCP: maximum connections exceeded
Cause: The connect failed because the maximum conncurrent connections supported
by the host's SQL*Net TCP/IP server has already been reached.
Action: Wait for a short period and re-try.
ORA-06144: NETTCP: SID (database) is unavailable
Cause: The database administrator on the host has varied the SID offline.
Action: Wait for it to be varied back on-line.
ORA-06145: NETTCP: unable to start ORASRV: images not installed
Cause: The host's SQL*Net TCP/IP server was unable to start the ORACLE server
process because the ORACLE protected images were not installed.
Action: Install the images.
ORA-06200: TWOTASK: connect failed, can't create mailbox
ORA-06201: TWOTASK: connect failed, can't attach to mailbox
ORA-06202: TWOTASK: connect failed, can't spawn ORASRV process
ORA-06203: TWOTASK: connect failed, handshake failure
ORA-06204: TWOTASK: connect failed, can't access ORASRV2.COM
ORA-06205: TWOTASK: connect failed, can't create logical name
ORA-06206: TWOTASK: message receive failure
ORA-06207: TWOTASK: message send failure
ORA-06208: TWOTASK: invalid login (connect) string
ORA-04930 to ORA-07499 62-9
ORA-06209: TWOTASK: connect failed, mailbox already exists

ORA-06210: TWOTASK: connect failed, ORASRV exited unexpectedly
ORA-06211: TWOTASK: connect failed, timeout waiting for ORASRV
ORA-06212: TWOTASK: connect failed, logical name table is full
ORA-06213: TWOTASK: connect failed
ORA-06214: TWOTASK: connect failed, insufficient quotas to create ORASRV
ORA-06215: TWOTASK: connect failed, ORASRV protected image not installed
ORA-06216: TWOTASK: connect failed, can't find ORASRV image file
ORA-06250: NETNTT: cannot allocate send and receive buffers
Cause: Two-task driver could not allocate data buffers.
Action: There is insufficient memory to run your program. Kill off other processes to
free up memory.
ORA-06251: NETNTT: cannot translate address file name
set and exported.
ORA-06252: NETNTT: cannot open address file
Cause: The NTT two-task driver could not open a file containing address information.
set and exported. Make sure the instance you are attempting to connect to is actually
up and running.
ORA-06253: NETNTT: cannot read arguments from address file
Cause: The NTT two-task driver could not read addressing information from its
addressing file.
up and running.
ORA-06254: NETNTT: cannot share connection to cube
Cause: The NTT two-task driver could not share a connection to the cube.
up and running.
ORA-06255: NETNTT: cannot read pid of remote process
Cause: An error occurred while reading the NTT communications link.
ORA-06256: NETNTT: remote fork failed
Cause: The Oracle listener process on the cube could not fork off a shadow process.
Action: The instance you are trying to connect to probably doesn't have enough
memory to run another shadow process. Ask someone else to log off, or connect to a
different instance.
ORA-06257: NETNTT: cannot send command line to shadow process
Cause: An error occurred while writing the NTT communications link.
ORA-06258: NETNTT: cannot allocate context area
free up memory.
ORA-06259: NETNTT: cannot read from remote process
Cause: An error occurred while reading the NTT communications link.
ORA-06260: NETNTT: cannot write to remote process
Cause: An error occurred while writing the NTT communications linke.
ORA-06261: NETNTT: nrange() failed
Cause: The call to 'nrange()' failed while attempting to establish a connection.
ORA-06262: NETNTT: nfconn() failed
Cause: The call to 'nfconn()' failed while attempting to establish a connection.
ORA-06263: NETNTT: out of memory in pi_connect
free up memory.
ORA-06264: NETNTT: data protocol error
Cause: The NTT two-task driver received an unexpected message type."
ORA-06265: NETNTT: break protocol error
Cause: The NTT two-task driver received an unexpected message type."
ORA-06266: NETNTT: bad write length
Cause: The NTT two-task driver failed on an internal consistency check.
ORA-06267: NETNTT: bad state
Cause: The NTT two-task driver failed on an internal consistency check.
ORA-04930 to ORA-07499 62-11
ORA-06268: NETNTT: cannot read /etc/oratab

Cause: The NTT two-task driver could not read configuration information from /etc/
oratab.
Action: Make sure /etc/oratab exists and is readable. This error may occur if the file
is incorrectly formatted. It also may occur if the driver has run out of memory.
ORA-06300: IPA: Disconnect failure
Cause: A fatal error occurred during the disconnect from the server. This was
probably caused by inaccessible message queues.
Action: If there is no message queue, restart the SQL*Net IPA servers using ipactl.
Otherwise contact your customer support representative.
ORA-06301: IPA: Cannot allocate driver context
Cause: The memory pool is exhausted.
Action: Check the circumstances and try to allocate less memory in your program or
adjust the init parameters in your INIT.ORA file and retry.
ORA-06302: IPA: Cannot connect to remote host
Cause: The cause may be one of the following: - there is no ADI server defined to
reflect a connection to the specified host. - the remote host is not known by the local
system. - the ORACLE kernel on the remote host is not generated with the IPA driver
Action: Check sequentially for the above causes and eliminate the actual cause found.
ORA-06303: IPA: Message send error
Cause: The SQL*Net IPA driver could not write the message into the message queue.
Action: Make sure that the message queue exists and is accessible. If necessary rerun
ipactl.
ORA-06304: IPA: Message receive error
Cause: The SQL*Net IPA driver could not read a message from the message queue.
Action: Make sure that the message queue exists and is accessible. If necessary rerun
ipactl.
ORA-06305: IPA: Illegal message type
Cause: The communication between user and ORACLE is out of synchronization.
This message should not normally be issued.
ORA-06306: IPA: Message write length error
Cause: The IPA driver tried to write a message in the queue that was too big for the
queue.
ORA-06307: IPA: Cannot reset connection
Cause: A fatal error occurred during the resetting of the connection.
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 off.
ORA-06309: IPA: No message queue available

Cause: The SQL*Net IPA servers have not been started.
Action: Run ipactl.
ORA-06310: IPA: Environment variable(s) not set
Cause: Environment variable(s) not set correctly.
Action: Check and correct.
ORA-06311: IPA: Maximum number of servers reached
Cause: Maximum number of servers reached.
Action: Shutdown and restart with an increased maximum number of servers. Note
that database links consume one server per link. Be sure to start up enough servers to
support database links.
ORA-06312: IPA: Incorrect outgoing service name supplied
Cause: Incorrect outgoing service name supplied.
Action: Check and correct the service name.
ORA-06313: IPA: Shared memory failed to initialise
Cause: The shared memory has not been set up correctly.
Action: Contact your system manager.
ORA-06314: IPA: Event set up failure
Cause: Fatal interprocess communication error.
ORA-06315: IPA: Invalid connect string
Cause: The connect string is malformed.
Action: Check and correct.
ORA-06316: IPA: Invalid database SID
Cause: The SID is unknown at the remote side.
Action: Either the database does not exist, is not running, or there are no reserved
servers for that SID.
ORA-06317: IPA: Local maximum number of users exceeded
Cause: The maximum number of simultaneous users of SQL*Net IPA has been
exceeded on the local side.
Action: Wait for free connections to become available. If the problem persists, contact
your system manager.
ORA-06318: IPA: Local maximum number of connections exceeded
Cause: The maximum number of simultaneous connections that SQL*Net IPA can
handle to different hosts has been exceeded on the local side.
ORA-06319: IPA: Remote maximum number of users exceeded
Cause: The maximum number of simultaneous users of SQL*Net IPA has been
exceeded on the remote side.
ORA-04930 to ORA-07499 62-13
ORA-06320: IPA: Remote maximum number of connections exceeded
Cause: The maximum number of simultaneous connections that SQL*Net IPA can
handle from different hosts has been exceeded on the remote side.
ORA-06321: IPA: Cannot reach the remote side
Cause: There has been a timeout on an attempt to connect to a remote server the
reason for which is most likely to be the remote SQL*Net IPA software is not running.
An alternative reason could be that the remote initiator service name is incorrect.
Action: Check and start the remote SQL*Net software. Check that it is started with the
correct service names supplied.
ORA-06322: IPA: Fatal shared memory error
Cause: An internal error has occurred in the shared memory handling.
ORA-06323: IPA: Cause event error
Cause: Fatal interprocess communication error.
ORA-06400: NETCMN: No default host string specified
Cause: There was no default host string specified in the configuration and the user
didn't specify any explicit connect string.
Action: Either reconfigure the system specifying a default connect string or use an
explicit connect string.
ORA-06401: NETCMN: invalid driver designator
Cause: The login (connect) string contains an invalid driver designator.
Action: Correct the string and re-submit.
ORA-06402: NETCMN: error receiving break message
Cause: Error occurred while attempting to read a break message.
ORA-06403: Unable to allocate memory.
Cause: System unable to allocate needed virtual memory.
Action: Configure more memory, reduce load, or simply try again.
ORA-06404: NETCMN: invalid login (connect) string
Action: Correct string and re-submit.
ORA-06405: NETCMN: reset protocol error
Cause: Unable to reset out of break state.
ORA-06406: NETCMN: error sending break message

Cause: Error occurred while attempting to send a break message.
ORA-06407: NETCMN: unable to set up break handling environment
Cause: Error occurred while attempting to set up asynchronous handlers for incoming, out-of-band break messages.
ORA-06408: NETCMN: incorrect message format
Cause: Message from partner contains bad header.
ORA-06413: Connection not open.
Cause: Unable to establish connection.
Action: Use diagnostic procedures to ascertain exact problem.
ORA-06416: NETCMN: error on test
Cause: Error occurred while testing I/O status of the network connection.
ORA-06419: NETCMN: server can not start oracle
Cause: The remote server was unable to start an ORACLE process on behalf of the
client.
Action: Make sure permissions on the remote ORACLE program are correctly set.
Contact your system administrator.
ORA-06420: NETCMN: SID lookup failure
Cause: From the remote host's server: the database SID, specified in the login
(connect) string, was not recognized.
Action: Add the appropriate SID entry to the CONFIG.ORA or oratab file on the
remote host (restarting the remote server may be needed).
ORA-06421: NETCMN: Error detected in the read-in data
Cause: Error found during recomputation of checksum or CRC.
Action: Possible hardware failures of communication nodes. Contact system
administrator immediately.
ORA-06422: NETCMN: Error in sending data
Cause: Unable to transmit data to remote host.
Action: Try reconnect to remote host, and contact your system administrator.
ORA-06423: NETCMN: Error in receiving data
Cause: Unable to receive data from remote host.
Action: Try reconnect to remote host, and contact your system administrator.
ORA-06430: ssaio: Seals do not match
Cause: A function was called with an invalid argument.
Action: Contact your Oracle Customer Support Representative.
ORA-04930 to ORA-07499 62-15
ORA-06431: ssaio: Invalid Block number

Cause: The file block number is out of range of the file. The additional information
returns the block number.
Action: Verify that the block number is correct. Run dbfsize and check if the block
number is in that range. Contact your Oracle Customer Support Representative.
ORA-06432: ssaio: Buffer Not Aligned
Cause: The I/O buffer was not aligned on a 2K boundary.
Action: Contact your Oracle Customer Support Representative.
ORA-06433: ssaio: LSEEK error, unable to seek to requested block.
Cause: The additional information returns the block number
Action: Look up the additional information returned in your operating system
reference manual. Verify that the block number is correct.
ORA-06434: ssaio: read error, unable to read requested block from database file.
Cause: The read system call returned an error.
Action: The additional information indicates the block number. Look up the
additional information returned in your operating system manual.
ORA-06435: ssaio: write error, unable to write requested block to database file.
Cause: The write system call returned an error.
ORA-06436: ssaio: asynchronous I/O failed due to incorrect parameters.
Cause: The Asynchronous I/O system call returned an error.
ORA-06437: ssaio: the asynchronous write was unable to write to the database file.
ORA-06438: ssaio: the asynchronous read was unable to read from the database file.
ORA-06439: ssaio: the asynchronous write returned incorrect number of bytes
Cause: This write call may have been truncated. The additional information returns
the block number and number of bytes.
Action: Verify that the block number and the number of bytes written are correct.
ORA-06440: ssaio: the asynchronous read returned incorrect number of bytes
Cause: This read call may have been truncated. The additional information returns
the block number and number of bytes.
Action: Verify that the block number and the number of bytes read are correct.
ORA-06441: ssvwatev: Incorrect parameter passed to function call

Cause: Either the ORACLE process id, or wait time or event ID is invalid.
Action: The additional information indicates the process id, time and event id.
ORA-06442: ssvwatev: Failed with unexpected error number.
Cause: Some system problems may exists on your system, please check error logs.
Action: The additional information indicates the error number. Look up the
ORA-06443: ssvpstev: Incorrect parameter passed to function call
Cause: An invalid event ID is passed in to this routine.
Action: The additional information indicates the event id.
ORA-06444: ssvpstev: Failed with unexpected error number.
Cause: Some system problems may exist on your system, please check error logs.
ORA-06445: ssvpstevrg: Incorrect parameters passed to function call
Cause: An invalid event id, or the low and high event ID do not exist.
Action: The additional information indicates the error number. It also contains the
event id, low boundary and high boundary.
ORA-06446: ssvpstevrg: Failed with unexpected error number.
Cause: Some system problems may exist on your system, please check error logs.
ORA-06447: ssvpstp: Incorrect parameter passed to function call
Cause: Invalid oracle process ID is passed in to this routine.
Action: The additional information indicates the process id.
ORA-06448: ssvpstp: Failed with unexpected error number.
Cause: Some system problems may exists on your system, please check error logs.
ORA-06449: The list IO or the 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 linked in.
Action: Set use_sysvendor=false in INIT.ORA, if you don't want to use this interface
or link the UNIX kernel with this interface so that ORACLE can use it.
ORA-06500: PL/SQL: storage error
Cause: PL/SQL was unable to allocate additional storage. This message normally
appears with an ORA-4030 or ORA-4031 error which gives additional information.
Sometimes this error can be caused by runaway programs.
Action: 1) Ensure there are no issues or bugs in your PL/SQL program which are
causing excessive amounts of memory to be used. 2) Programmatically cause unused
ORA-04930 to ORA-07499 62-17
objects to be freed (e.g. by setting them to NULL). 3) Increase the amount of shared or
process memory (as appropriate) available to you.
ORA-06501: PL/SQL: program error
Cause: This is an internal error message. An error has been detected in a PL/SQL
program.
ORA-06502: PL/SQL: numeric or value errorstring
Cause: An arithmetic, numeric, string, conversion, or constraint error occurred. For
example, this error occurs if an attempt is made to assign the value NULL to a
variable declared NOT NULL, or if an attempt is made to assign an integer larger
than 99 to a variable declared NUMBER(2).
Action: Change the data, how it is manipulated, or how it is declared so that values
do not violate constraints.
ORA-06503: PL/SQL: Function returned without value
Cause: A call to PL/SQL function completed, but no RETURN statement was
executed.
Action: Rewrite PL/SQL function, making sure that it always returns a value of a
proper type.
ORA-06504: PL/SQL: Return types of Result Set variables or query do not match
Cause: Number and/or types of columns in a query does not match declared return
type of a result set variable, or declared types of two Result Set variables do not
match.
Action: Change the program statement or declaration. Verify what query the variable
actually refers to during execution.
ORA-06505: PL/SQL: variable requires more than 32767 bytes of contiguous
memory
Cause: A PL/SQL variable was declared with a constraint which required more than
32767 bytes of memory. PL/SQL does not currently support allocations of contiguous
memory greater than 32767 bytes.
Action: Consider reducing the constraint in the variable declaration. If that is not
possible, try changing the database or national character set to such, that requires less
memory for the same constraint. Note: changing the character set will impact
execution of all PL/SQL code.
ORA-06508: PL/SQL: could not find program unit being calledstring
ORA-06509: PL/SQL: ICD vector missing for this package
ORA-06510: PL/SQL: unhandled user-defined exception
Cause: A user-defined exception was raised by PL/SQL code, but not handled.
Action: Fix the problem causing the exception or write an exception handler for this
condition. Or you may need to contact your application administrator or DBA.
ORA-06511: PL/SQL: cursor already open
Cause: An attempt was made to open a cursor that was already open.
Action: Close cursor first before reopening.
ORA-06512: at stringline string

Cause: Backtrace message as the stack is unwound by unhandled exceptions.
ORA-06513: PL/SQL: index for PL/SQL table out of range for host language array
Cause: An attempt is being made to copy a PL/SQL table to a host language array.
But an index in the table is either less than one or greater than the maximum size of
the host language array. When copying PL/SQL tables to 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, etc. If an table entry has not been assigned
then the corresponding element in the host language array is set to null.
Action: Increase size of host language array, or decrease size of PL/SQL table. Also
make sure that you don't use index values less than 1.
ORA-06514: PL/SQL: The remote call cannot be handled by the server
Cause: The remote call has parameters that are cursor variables or lob variables. This
cannot be handled by stored procedures on your server.
Action: Avoid using cursor variables or lob variables as parameters for stored
procedures on this server or upgrade your server to a version that supports this.
ORA-06515: PL/SQL: unhandled exception string
Cause: An exception was raised by PL/SQL code, but not handled. The exception
number is outside the legal range of Oracle errors.
ORA-06516: PL/SQL: the Probe packages do not exist or are invalid
Cause: A Probe operation, probably an attempt to initialize the ORACLE server to
debug PL/SQL, could not be completed because the Probe packages were not loaded
or have become invalid.
Action: DBA should load the Probe packages. This can be done by running the
pbload.sql script supplied with the RDBMS.
ORA-06517: PL/SQL: Probe error - string
Cause: An error occurred while passing a Probe operation to the server for execution.
Action: Refer to the entry for the embedded error message.
ORA-06518: PL/SQL: Probe version string incompatible with version string
Cause: The current version of Probe is incompatible with the version on the ORACLE
server.
Action: Refer to the documentation to ensure that this degree of compatibility is
supported.
ORA-06519: active autonomous transaction detected and rolled back
Cause: Before returning from an autonomous PL/SQL block, all autonomous
transactions started within the block must be completed (either committed or rolled
back). If not, the active autonomous transaction is implicitly rolled back and this error
is raised.
Action: Ensure that before returning from an autonomous PL/SQL block, any active
autonomous transactions are explicitly committed or rolled back.
ORA-04930 to ORA-07499 62-19
----------------------------------------------------------------------- 06520 through 06529 reserved

for Foreign function errors
ORA-06520: PL/SQL: Error loading external library
Cause: An error was detected by PL/SQL trying to load the external library
dynamically.
Action: Check the stacked error (if any) for more details.
ORA-06521: PL/SQL: Error mapping function
Cause: An error was detected by PL/SQL trying to map the mentioned function
dynamically.
Action: Check the stacked error (if any) for more details.
ORA-06522: string
Cause: ORA-06520 or ORA-065211 could stack this error with a system specific error
string.
Action: This error string should give the cause for errors ORA-06520 or ORA-065211
ORA-06523: Maximum number of arguments exceeded
Cause: There is an upper limit on the number of arguments that one can pass to the
external function.
Action: Check the port specific documentation on how to calculate the upper limit.
ORA-06524: Unsupported option : string
Cause: The option specified is an unsupported feature for external procedures.
Action: 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 illegal value. This can
happen if you have requested requested a PL/SQL INOUT, OUT or RETURN raw
variable to be passed as a RAW with no corresponding length variable. This error can
also happen if there is a mismatch in the length value set in the length variable and
the length in the orlvstr or orlraw.
Action: Correct the external procedure code and set the length variable correctly.
ORA-06526: Unable to load PL/SQL library
Cause: PL/SQL was unable to instantiate the library referenced by this referenced in
the EXTERNAL syntax. This is a serious error and should normally not happen.
Action: Report this problem to customer support.
ORA-06527: External procedure SQLLIB error: string
Cause: An error occurred in sqllib during execution of a Pro* external procedure.
Action: The message text indicates the actual SQLLIB error that occurred. Consult the
Oracle Error Messages and Codes manual for a complete description of the error
message and follow the appropriate action.
ORA-06528: Error executing PL/SQL profiler
Cause: An error occurred in during execution of 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 in the server implementing the profiler.
Action: Run the package profload.sql in $ORACLE_HOME/rdbms/admin to load the
correct version of the PL/SQL profiler packages
ORA-06530: Reference to uninitialized composite
Cause: An object, LOB, or other composite was referenced as a left hand side without
having been initialized.
Action: Initialize the composite with an appropriate constructor or whole-object
assignment.
ORA-06531: Reference to uninitialized collection
Cause: An element or member function of a nested table or varray was referenced
(where an initialized collection is needed) without the collection having been
initialized.
Action: Initialize the collection with an appropriate constructor or whole-object
assignment.
ORA-06532: Subscript outside of limit
Cause: A subscript was greater than the limit of a varray or non-positive for a varray
or nested table.
Action: Check the program logic and increase the varray limit if necessary.
ORA-06533: Subscript beyond count
Cause: An in-limit subscript was greater than the count of a varray or too large for a
nested table.
Action: Check the program logic and explicitly extend if necessary.
ORA-06534: Cannot access Serially Reusable package string
Cause: The program attempted to access a Serially Reusable package in PL/SQL
called from SQL context (trigger or otherwise). Such an access is currently
unsupported.
Action: Check the program logic and remove any references to Serially Reusable
packages (procedure, function or variable references) which might happen in PL/SQL
called from sql context (trigger or otherwise).
ORA-06535: statement string in string is NULL or 0 length
Cause: The program attempted to use a dynamic statement string that was either
NULL or 0 length.
Action: Check the program logic and ensure that the dynamic statement string is
properly initialized.
ORA-06536: IN bind variable bound to an OUT position
Cause: The program attempted to bind an IN bind variable to a statement that was
expecting an OUT bind variable at that position.
Action: Make sure that an OUT or IN OUT bind mode is specified for the bind
argument.
ORA-04930 to ORA-07499 62-21
ORA-06537: OUT bind variable bound to an IN position

Cause: The program attempted to bind an OUT bind variable to a statement that was
expecting an IN bind variable at that position.
Action: Make sure that an IN or IN OUT bind mode is specified for the bind
argument.
ORA-06538: statement violates string RESTRICT_REFERENCES pragma
Cause: The program attempted to execute a dynamic statement which does not meet
the purity level specified (in the pragma RESTRICT_REFERENCES 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.
Action: Ensure that the OPEN cursor operation is done on a dynamic query
statement. -------------------------------------------------------- 06540 through 06549 reserved
for pl/sql error handling
ORA-06540: PL/SQL: compilation error
Cause: A pl/sql compilation error occurred. However, the user generally will not see
this error message. Instead, there will be accompanying PLS-nnnnn error messages.
Action: See accompanying PLS-nnnnn error messages.
ORA-06541: PL/SQL: compilation error - compilation aborted
Cause: A pl/sql compilation error occurred and the compilation was aborted; but the
compilation unit was written out to the backing store. However, unlike ora-06545, the
user generally will not see this error message. Instead, there will be accompanying
PLS-nnnnn error messages.
ORA-06542: PL/SQL: execution error
ORA-06543: PL/SQL: execution error - execution aborted
ORA-06544: PL/SQL: internal error, arguments: [string], [string], [string], [string],
Cause: A pl/sql internal error occurred.
Action: Report as a bug; the first argument is the internal error nuber.
ORA-06545: PL/SQL: compilation error - compilation aborted
Cause: A pl/sql compilation error occurred and the compilation was aborted
completely without the compilation unit being written out to the backing store.
Unlike ora-06541, the user will always see this error along with the accompaning PLSnnnnn error messages.
ORA-06546: DDL statement is executed in an illegal context
Cause: DDL statement is executed dynamically in illegal PL/SQL context. - Dynamic
OPEN cursor for a DDL in PL/SQL - Bind variable's used in USING clause to
EXECUTE IMMEDIATE a DDL - Define variable's used in INTO clause to EXECUTE

IMMEDIATE a DDL
Action: Use EXECUTE IMMEDIATE without USING and INTO clauses to execute the
DDL statement.
ORA-06547: RETURNING clause must be used with INSERT, UPDATE, or
DELETE statements
Cause: EXECUTE IMMEDIATE with a RETURNING clause is used to execute
dynamic UPDATE, INSERT, or DELETE statements only.
Action: use RETURNING clause in EXECUTE IMMEDIATE for INSERT, UPDATE, or
DELETE statements only. For other statements, use USING clause instead.
ORA-06548: no more rows needed
Cause: The caller of a pipelined function did not need more rows to be produced by
the pipelined function.
Action: Do not catch the NO_DATA_NEEDED exception in an exception handling
block.
ORA-06549: PL/SQL: failed to dynamically open shared object (DLL): string:string
Cause: One possible cause might be there are too many DLLs open at the same time.
Action: -------------------------------------------------------ORA-06550: line string, column string:\nstring
Cause: Usually a PL/SQL compilation error.
Action: n/a
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: The DBMS specific extensions to PL/SQL's package "STANDARD" are in
package "DBMS_STANDARD". This package must be created before using PL/SQL.
Action: Create package "DBMS_STANDARD". The source for this PL/SQL stored
package is provided with the distribution.
ORA-06555: this name is currently reserved for use by user SYS
Cause: You tried to create a package named "STANDARD", "DBMS_STANDARD" or
"DEBUG_IO". These are currently reserved for use by user SYS.
Action: Choose another name for your package.
ORA-06556: the pipe is empty, cannot fulfill the unpack_message request
Cause: There are no more items in the pipe.
Action: Check that the sender and receiver agree on the number and types of items
placed on the pipe.
ORA-06557: null values are not allowed for any parameters to pipe icd's
Cause: Internal error from the dbms_pipe package.
Action: n/a
ORA-04930 to ORA-07499 62-23
ORA-06558: buffer in dbms_pipe package is full. No more items allowed

Cause: The pipe buffer size has been exceeded.
Action: n/a
ORA-06559: wrong datatype requested, string, actual datatype is string
Cause: The sender put different datatype on the pipe than that being requested
(package 'dbms_pipe'). The numbers are: 6 - number, 9 - char, 12 - date.
Action: Check that the sender and receiver agree on the number and types of items
placed on the pipe.
ORA-06560: pos, string, is negative or larger than the buffer size, string
Cause: Internal error from the dbms_pipe package.
Action: n/a
ORA-06561: given statement is not supported by package DBMS_SQL
Cause: Attempting to parse an unsupported statement using procedure PARSE
provided by package DBMS_SQL.
Action: Only statements which begin with SELECT, DELETE, INSERT, UPDATE,
LOCK, BEGIN, DECLARE or << (PL/SQL label delimiter) are supported.
ORA-06562: type of out argument must match type of column or bind variable
Cause: Attempting to get the value of a column or a bind variable by calling
procedure COLUMN_VALUE or VARIABLE_VALUE of package DBMS_SQL but the
type of the given out argument where to place the value is different from the type of
the column or bind variable that was previously defined by calling procedure
DEFINE_COLUMN (for defining a column) or BIND_VARIABLE (for binding a bind
variable) of package DBMS_SQL.
Action: Pass in an out argument of the correct type when calling procedure
COLUMN_VALUE or VARIABLE_VALUE. The right type is the type that was
provided when defining the column or binding the bind variable.
ORA-06563: name has too many parts
Cause: The name to be resolved was specified as one of the following: - With three
parts (A.B.C) but the A.B parts resolved to an object that did not expose visible nested
procedures; the C part could not be resolved. - With two parts (A.B) and the A part
resolved to an object that did not expose visible nested procedures; the B part could
not be resolved.
Action: Specify the valid name of an object or of a packaged procedure or function
without specifying any additional trailing parts.
ORA-06564: object string does not exist
Cause: The named object could not be found. Either it does not exist or you do not
have permission to access it.
Action: Create the object or get permission to access it.
ORA-06565: cannot execute string from within stored procedure
Cause: The named procedure cannot be executed from within a stored procedure,
function or package. This function can only be used from pl/sql anonymous blocks.
Action: Remove the procedure from the calling stored procedure.
ORA-06566: invalid number of rows specified

Cause: An invalid number of rows was specified in a call to the procedure
DEFINE_COLUMN in the package DBMS_SQL. For a given parsed statement in a
given cursor, all columns must be defined to have the same number of rows, so all the
calls to DEFINE_COLUMN must specify the same number of rows.
Action: Specify a number that matches that for previously defined columns.
ORA-06567: invalid number of values specified
Cause: An invalid number of values to be bound was specified in a call to the
procedure BIND_VARIABLE in the package DBMS_SQL. In order to execute a given
parsed statement in a given cursor, the same number of values must have been bound
for all bind variables, so when EXECUTE is called, the latest calls to
BIND_VARIABLE must must have specified the same number of values to be bound
for all bind variables.
Action: Make sure that the same number of values have been bound for all of the bind
variables.
ORA-06568: obsolete ICD procedure called
Cause: An obsolete ICD procedure was called by a PL/SQL program. The PL/SQL
program was probably written for an eralier release of RDBMS.
Action: Make sure that all PL/SQL programs have been upgraded to the latest release
of the RDBMS. This can be accomplished by following upgrade instructions in the
README file, or by running the catproc.sql script supplied with the RDBMS.
ORA-06569: Collection bound by bind_array contains no elements
Cause: A collection with zero elements was bound to a bind variable in a call to
procedure BIND_ARRAY in the package DBMS_SQL. In order to execute a bind of a
collection, the collection must contain at least one element. If no elements are present
then at execute time there will be no value for this bind and the statement is
meaningless.
Action: Fill the collection with the elements you want to bind and try the bind call
again.
ORA-06570: shared pool object does not exist, cannot be pinned/purged
Cause: The specified shared pool shared cursor could not be found, therefore it
cannot be pinned/purged.
Action: Make sure that a correct shared cursor name is given. Names are a string of
the form 'HHHHHHHH,SDDDDDDDDDD' where the H's are an 8 digit hex number
from the 'address' column of v$sqlarea, and the D's are a 1 to 10 digit decimal number
with an optional leading sign (from the 'hash_value' column) Remove the procedure
from the calling stored procedure.
ORA-06571: Function string does not guarantee not to update database
Cause: There are two possible causes for this message: * A SQL statement references a
packaged, PL/SQL function that does not contain a pragma that prevents the
database from being updated. * A SQL statement references a stand-alone, PL/SQL
function that contains an instruction to update the database.
Action: If the referenced function is a packaged, PL/SQL function: Recreate the
PL/SQL function with the required pragma; be certain to include the 'Write No
Database State' (WNDS) argument in the argument list of the pragma. If the
referenced function is a stand-alone, PL/SQL function: Do not use the function.
ORA-04930 to ORA-07499 62-25
ORA-06572: Function string has out arguments

Cause: A SQL statement references either a packaged, or a stand-alone, PL/SQL
function that contains an OUT parameter in its argument list. PL/SQL functions
referenced by SQL statements must not contain the OUT parameter.
Action: Recreate the PL/SQL function without the OUT parameter in the argument
list.
ORA-06573: Function string modifies package state, cannot be used here
Cause: There are two possible causes for this message: * A SQL statement references a
packaged, PL/SQL function that does not contain a pragma containing the 'Write no
Package State' (WNPS). * A SQL statement references a stand-alone, PL/SQL function
that modifies a package state. A stand-alone, PL/SQL function referenced by a SQL
statement cannot modify a package state.
Action: If the function is a packaged, PL/SQL function: Recreate the function and
include a pragma containing the 'Write no Package State' (WNPS). If the function is a
stand-alone, PL/SQL function: Delete the function from the SQL statement.
ORA-06574: Function string references package state, cannot execute remotely
Cause: There are two possible causes for this message: * A remote, packaged function
or a remote-mapped, local, packaged function that does not contain a pragma with
the 'Write no Package State' (WNPS) and 'Read no Package State' (RNPS) arguments
references a package state. * A remote, stand-alone function or a remote-mapped,
local, stand-alone function contains a reference to a package state (reads or writes a
package variable). Only local functions that are referenced in a SELECT list, VALUES
clause of an INSERT statement, or SET clause of an UPDATE statement can modify a
package state.
Action: If the function is a packaged function: Recreate the function and include a
pragma containing the 'Write no Package State' (WNPS) and 'Read no Package State'
(RNPS) arguments. If the function is a stand-alone function: Do not call the function.
ORA-06575: Package or function string is in an invalid state
Cause: A SQL statement references a PL/SQL function that is in an invalid state.
Oracle attempted to compile the function, but detected errors.
Action: Check the SQL statement and the PL/SQL function for syntax errors or
incorrectly assigned, or missing, privileges for a referenced object.
ORA-06576: not a valid function or procedure name
Cause: Could not find a function (if an INTO clause was present) or a procedure (if
the statement did not have an INTO clause) to call.
Action: Change the statement to invoke a function or procedure
ORA-06577: output parameter not a bind variable
Cause: The argument corresponding to an IN/OUT or OUT parameter for a function
or a procedure or a function return value in a CALL statement must be a bind
variable.
Action: Change the argument to a bind variable
ORA-06578: output parameter cannot be a duplicate bind
Cause: The bind variable corresponding to an IN/OUT or OUT parameter for a
function or a procedure or a function return value in a CALL statement cannot be a
duplicate bind variable.
Action: Change the bind variable to be unique
ORA-06579: Bind variable not big enough to hold the output value
Cause: The bind variable specified by the user is not large enough to hold the output
returned by the function or a procedure.
Action: Specify a bind variable of larger size.
ORA-06580: Hash Join ran out of memory while keeping large rows in memory
Cause: Hash Join reserves 3 slots (each slot size = DB_BLOCK_SIZE *
HASH_JOIN_MULTIBLOCK_IO_COUNT) for a row. If a row is larger than that, this
error will be raised.
Action: Increase HASH_JOIN_MULTIBLOCK_IO_COUNT so that each joined row
fits in a slot. HASH_AREA_SIZE may also need to be increaed.
ORA-06592: CASE not found while executing CASE statement
Cause: A CASE statement must either list all possible cases or have an else clause.
Action: Add all missing cases or an else clause.
ORA-06593: string is not supported with natively compiled PL/SQL modules
Cause: Specified feature is not yet supported for natively compiled PL/SQL modules
yet.
Action: Recompile the relevant PL/SQL modules in non-native mode by setting the
parameter plsql_compiler_flags to INTERPRETED.
ORA-06595: REF CURSOR parameters are not supported in forwarded RPC calls
Cause: An attempt was made to make a forwarded RPC call with a REF CURSOR
parameter.
Action: Either call the remote function directly (i.e., not by way of forwarding), or
move the remote function to a database where it can be called directly.
ORA-06596: object cannot be purged, object is permanently kept in shared pool
Cause: The specified object was permanently kept, therefore, cannot be purged.
Action: Use DBMS_SHARED_POOL.UNKEEP procedure to unkeep the object and
then purge it.
ORA-06597: Failed to increase the session's call stack memory to string bytes at a
depth of string calls. (The current maximum is string bytes.)
Cause: PL/SQL program execution used more call stack memory than permitted.
Action: * Ask your DBA to increase the maximum allowed call stack memory. *
Decrease the amount of call stack used by the program. This may be accomplished by
using fewer, smaller local variables, or by limiting the depth of function call nesting.
ORA-06598: insufficient INHERIT PRIVILEGES privilege
Cause: An attempt was made to run an AUTHID CURRENT_USER function or
procedure, or to reference a BEQUEATH CURRENT_USER view, and the owner of
that function, procedure, or view lacks INHERIT PRIVILEGES privilege on the calling
user.
Action: Either do not call the function or procedure or reference the view, or grant the
owner of the function, procedure, or view INHERIT PRIVILEGES privilege on the
calling user.
ORA-04930 to ORA-07499 62-27
ORA-06599: unsupported LOB operation in RPC call

Cause: An attempt was made to perform certain large object (LOB) date type
operations (for example, deep copying of a temporary or abstract LOB on the client
side) while performing a remote procedural call (RPC). This is not currently
supported.
Action: Perform the LOB operation in question before starting the RPC. Or, perform
those LOB operations on the server side instead of the client side.
ORA-06600: LU6.2 Driver: SNA software is not loaded
Cause: The SNA software is not running.
Action: Start the SNA software and try again.
ORA-06601: LU6.2 Driver: Invalid database ID string
Cause: The database string in the connect was invalid.
Action: Provide a valid database string, as defined in documentation.
ORA-06602: LU6.2 Driver: Error allocating context area
Cause: Context area failure.
Action: Contact your local service representative.
ORA-06603: LU6.2 Driver: Error allocating memory
Cause: Operating system refused request for memory.
Action: Contact you local service representative.
ORA-06604: LU6.2 Driver: Unable to allocate session with remote LU
Cause: Allocate system call failed.
Action: Ensure that the SNA software is running and that sessions are free. If this is
the case, then check your SNA configuration data for errors. You may have entered an
incorrect parameter.
ORA-06605: LU6.2 Driver: Unexpected line turnaround
Cause: SNA software switched from send to receive unexpectedly.
Action: Check the SNA configuration data, particularly parameters associated with a
session.
ORA-06606: LU6.2 Driver: Unexpected response from SNA
Cause: A parameter in an SNA call returned an unexpected value.
Action: Attempt to reproduce problem, debug and record the value of the 'what' data
parameter at the time of error. Then contact your service representative.
ORA-06607: LU6.2 Driver: Reset occurred in send state
Cause: A reset was issued whilst in send state.
Action: Check the SNA LOG data, if relevent, for further information.
ORA-06608: LU6.2 Driver: Reset occurred in receive state
Cause: A reset was received from the partner whilst in receive state. This may be
because the partner deallocated.
Action: Check the SNA LOG data, if relevent, for further information.
ORA-06610: LU6.2 Driver: Failed during deallocation
Cause: LU6.2 driver was unable to deallocate gracefully.
Action: Check the reason for deallocation. Consult the SNA LOG data.
ORA-06611: LU6.2 Driver: Request to send error
ORA-06612: LU6.2 Driver: Send data error
ORA-06613: LU6.2 Driver: Receive and wait error
ORA-06614: LU6.2 Driver: Receive Immediate error
ORA-06615: LU6.2 Driver: Send error
ORA-06616: LU6.2 Driver: Attach to LU failed
Cause: The SQL*Net LU6.2 driver was unable to attach to the LU specified in the
connect string, or was unable to attach to the default LU.
Action: Check that the LU name specified in the connect string, or the default LU
name if no LU was specified, is correctly configured and operational.
ORA-06617: LU6.2 Driver: Attach to PU failed
ORA-06618: LU6.2 Driver: Activation of subnetwork failed
ORA-06619: LU6.2 Driver: Unable to activate remote partner
ORA-06620: LU6.2 Driver: Invalid remote partner
ORA-06621: LU6.2 Driver: Allocation error
ORA-06622: LU6.2 Driver: Unable to attach to SNA
Cause: The SQL*Net LU6.2 driver could not attach to the SNA software on your
machine. The most likely cause is that the SNA software is not operational.
Action: Check the status of the SNA software, ensure that it is operational and then
try again.
ORA-06700: TLI Driver: incorrect message type from host
Cause: TLI received a message with an unrecognizable message type.
ORA-06701: TLI Driver: incorrect number of bytes written
Cause: TLI sent a message that was apparently successful, but the number of bytes
transmitted did not match the number of bytes supplied to the driver.
ORA-06702: TLI Driver: cannot allocate context area
Cause: TLI could not allocate heap space for the context area.
ORA-06703: TLI Driver: send break message failed
Cause: TLI failed to send a break message across the connection.
ORA-06704: TLI Driver: receive break message failed
Cause: TLI failed to receive an expected break message.
ORA-04930 to ORA-07499 62-29

ORA-06705: TLI Driver: remote node is unknown
Cause: TLI could not find your remote host information.
Action: Make sure you specified the hostname correctly on the command line. (Also,
check your capitalization and spelling.)
ORA-06706: TLI Driver: service not found
Cause: TLI could not find service information for the specified service name.
Action: If you specified the service name on the command line or with the
environment variable TLI_SERVER, make sure you specified it correctly. If the service
name is not in the SERVICES file for your protocol, ask your system adminstrator to
add it.
ORA-06707: TLI Driver: connection failed
Cause: TLI failed to establish the connection to a SQL*Net TCP/IP server due to an
error encountered by the remote server, which has supplied a string describing the
remote error.
Action: See the SQL*Net TCP/IP User's Guide section "orasrv Messages" for the
specific cause and action.
ORA-06708: TLI Driver: message receive failure
Cause: TLI encountered an error receiving a message from the communication
channel.
ORA-06709: TLI Driver: message send failure
Cause: TLI encountered an error sending a message across the communication
channel.
ORA-06710: TLI Driver: send interrupt break message failed
Cause: TLI failed to send a break message while handling an interrupt signal from the
user.
ORA-06711: TLI Driver: error on bind
Cause: TLI failed to assign a network address to the communication channel.
ORA-06712: TLI Driver: error on accept
Cause: TLI failed to accept a connection request from the client.
ORA-06713: TLI Driver: error on connect
Cause: TLI failed to connect the client to the remote server. The network line to the
remote host may be down.
Action: Use other network login programs to make sure that the remote host is
accessible.
ORA-06720: TLI Driver: SID lookup failure

Cause: The database SID supplied in the database login string was not recognized by
the remote host.
Action: Ask your system administrator to add the appropriate SID entry to oratab on
the remote host.
ORA-06721: TLI Driver: spurious client req
Cause: The remote TLI server received an undefined request.
ORA-06722: TLI Driver: connection setup failure
Cause: The remote TLI server rejected the connection request, and the client was
unable to retrieve an error code or message.
ORA-06730: TLI Driver: unable to open clone device
Cause: TLI failed to open the Streams clone device associated with the transport
provider.
ORA-06731: TLI Driver: cannot alloc t_call
Cause: TLI cannot allocate space for the client's connection information.
ORA-06732: TLI Driver: cannot alloc t_discon
Cause: TLI cannot allocate space for the client's disconnection information.
ORA-06733: TLI Driver: failed to receive disconnect
Cause: TLI failed to receive an expected disconnection message during connection
release.
ORA-06734: TLI Driver: cannot connect
Cause: TLI failed to connect the client to the remote server.
Action: Check that the remote TLI server is running.
ORA-06735: TLI Driver: client failed to close error conn
Cause: TLI failed to properly close a connection after an error was received.
ORA-06736: TLI Driver: server not running
Cause: TLI timed out while attempting to connect to the remote TLI server.
Action: Check that the remote TLI server is running with the status utility for the
transport provider you are using. If it is not, ask your system adminstrator to start it.
ORA-06737: TLI Driver: connection failed
Cause: TLI could not establish a connection to the remote TLI server.
Action: Check that the remote TLI server is running with the status utility for the
transport provider you are using.
ORA-04930 to ORA-07499 62-31
ORA-06741: TLI Driver: unable to open protocol device

Cause: The TLI server failed to open the Streams device associated with the transport
provider.
ORA-06742: TLI Driver: cannot alloc t_bind
Cause: The TLI server cannot allocate space for its requested network address.
ORA-06743: TLI Driver: cannot alloc t_bind
Cause: The TLI server cannot allocate space for its actual network address.
ORA-06744: TLI Driver: listener cannot bind
Cause: The TLI server failed to assign the correct network address on which to listen
for connections.
ORA-06745: TLI Driver: listener already running
Cause: The network address on which the TLI server awaits connection requests is in
use, possibly because the server is already running.
Action: Ensure that the TLI server is not already running. If it is not running and this
error message recurs, contact your customer support representative.
ORA-06746: TLI Driver: cannot alloc t_call
Cause: TLI cannot allocate space for the TLI server's connection information.
ORA-06747: TLI Driver: error in listen
Cause: The TLI server encountered an error while listening for connection requests.
ORA-06748: TLI Driver: cannot allocate t_discon
Cause: TLI cannot allocate space for the TLI server's disconnection information.
ORA-06749: TLI Driver: option not allowed across network
Cause: The requested TLI server command must be issued from the same host on
which the server is running.
Action: Log in to the remote host and try again.
ORA-06750: TLI Driver: sync failed
Cause: The ORACLE process started by the TLI server was unable to synchronize its
inherited connection.
ORA-06751: TLI Driver: bound addresses unequal
Cause: The osn check server address failed. The bound server address was not the
same as the requested binding address.
ORA-06752: TLI: error in signal setup

Cause: A call to sigaction() returned with a system error.
ORA-06753: TLI Driver: name-to-address mapping failed
Cause: For SVR4, the netdir_getbyname() call failed for some unknown reason.
Action: Contact your custumer service representative.
ORA-06754: TLI Driver: unable to get local host address
Cause: The name of the remote host to connect to was not specified, and the name of
the local host cannot be retrieved from the HOSTS file.
ORA-06755: TLI Driver: cannot close transport endpoint
Cause: The TLI server was unable to close a connection after passing it to an ORACLE
process.
ORA-06756: TLI Driver: cannot open oratab
Cause: The TLI server could not open the file used to define the locations of remotely
accessible databases.
Action: Ask your system administrator to check that the file exists and has the correct
permissions.
ORA-06757: TLI Driver: server got bad command
Cause: The TLI server received an invalid command.
ORA-06760: TLI Driver: timeout reading orderly release
Cause: TLI was not able to retreive an expected disconnect message while closing the
communication channel.
ORA-06761: TLI Driver: error sending orderly release
Cause: TLI encountered an error sending a disconnect message closing the
ORA-06762: TLI Driver: error reading orderly release
Cause: TLI encountered an error receiving an expected disconnect message while
closing the communication channel.
ORA-06763: TLI Driver: error sending disconnect
Cause: TLI encountered an error sending a disconnect message closing the
ORA-06764: TLI Driver: error reading disconnect
Cause: TLI was not able to retreive an expected disconnect message while closing the
ORA-04930 to ORA-07499 62-33

ORA-06765: TLI Driver: error awaiting orderly release
Cause: TLI encountered an error awaiting a disconnect message while closing the
ORA-06766: TLI Driver: close failed during release
Cause: TLI failed to close the communication channel after receiving a disconnect
message.
ORA-06767: TLI Driver: alloc failed during release
Cause: TLI cannot allocate space for disconnection information while closing the
ORA-06770: TLI Driver: error sending version
Cause: TLI encountered an error while sending its version information during
connection establishment.
ORA-06771: TLI Driver: error reading version
Cause: TLI encountered an error while awaiting the expected version information
during connection establishment.
ORA-06772: TLI Driver: error sending command
Cause: TLI encountered an error while sending a command message during
ORA-06773: TLI Driver: error reading command
Cause: TLI encountered an error while awaiting the expected command message
ORA-06774: TLI Driver: error sending break mode
Cause: TLI encountered an error while sending break-mode message during
ORA-06775: TLI Driver: error reading break mode
Cause: TLI encountered an error while awaiting the expected break-mode message
ORA-06776: TLI Driver: error sending parms
Cause: TLI encountered an error while sending the connection parameters during
ORA-06777: TLI Driver: error reading parms

Cause: TLI encountered an error while awaiting the expected connection parameter
message during connection establishment.
ORA-06778: TLI Driver: error sending ccode
Cause: TLI encountered an error while sending the completion status message during
ORA-06779: TLI Driver: error reading ccode
Cause: TLI encountered an error while awaiting the expected completion status
message during connection establishment.
ORA-06780: TLI Driver: recv error code failed
Cause: TLI encountered an error while awaiting an expected error message during
ORA-06781: TLI Driver: error reading negotation string
Cause: TLI encountered an error while awaiting the expected negotiation message
ORA-06790: TLI Driver: poll failed
Cause: TLI was unable to poll the communication channel for possible incoming
messages.
ORA-06791: TLI Driver: poll returned error event
Cause: TLI received an unexpected event while polling the communication channel
for possible incoming messages.
ORA-06792: TLI Driver: server cannot exec oracle
Cause: The remote TLI server was unable to start an ORACLE process on behalf of the
client.
Action: Note the operating system error message or number and contact your system
adminstrator. The permissions on the remote ORACLE program may be set
incorrectly.
ORA-06793: TLI Driver: server cannot create new process
Cause: The remote TLI server was unable to start an ORACLE process on behalf of the
client.
Action: Note the operating system error message or number and contact your system
adminstrator. The remote host may be unable to create any new processes due to a
full process table.
ORA-04930 to ORA-07499 62-35
ORA-06794: TLI Driver: shadow process could not retrieve protocol info
Cause: The ORACLE process either failed to allocate memory to store the protocol
information record, or the protocol rejected the request for some unknown reason.
ORA-06800: TLI Driver: SQL*Net SPX client went away during reconnect
Cause: The client process was aborted by the system or the user, and was unable to
complete the connection establishment with the server listener process.
Action: Determine cause of client exit, and reattempt connection.
ORA-06801: TLI Driver: listen for SPX server reconnect failed
Cause: An unknown event occurred on the client's listening socket.
ORA-06802: TLI Driver: could not open the /etc/netware/yellowpages file
Cause: The /etc/netware/yellowpages file does not exist, or is not readable by the
TLI listener process.
Action: Insure the file exists and is readable. Make sure that the server machine's node
name, network number, ethernet address, and listening socket number are encoded in
the file.
ORA-06803: TLI Driver: the IPX device file could not be opened
Cause: The /dev/ipx file does not exist, or the driver has not been installed in the
kernel correctly.
Action: Reinvoke the Oracle root installation. If problem continues, contact your
customer support representative.
ORA-06804: TLI Driver: could not bind an IPX address at initialization
Cause: The IPX driver has not been correctly installed.
ORA-06805: TLI Driver: could not send datagram SAP packet for SPX
Cause: The socket endpoint for sending SAP packet was corrupted for some unknown
reason.
ORA-06806: TLI Driver: could not complete protocol initialization for SPX
Cause: A step in the SPX/IPX protocol initialization failed.
Action: Check the previous error reported, and follow corrective action.
ORA-06807: TLI Driver: could not open ethernet device driver file
Cause: The file /dev/eth does not exist, or the driver it references could not be
opened.
Action: The system's real ethernet device file, for example /dev/wd, for the Western
Digital ethernet driver, should be linked to the file /dev/eth. If this has been done,
insure that the ethernet driver has been installed by completing the TCP/IP
installation on your system, and testing a connection. If problem continues, contact
your customer support representative for a list of supported ethernet drivers.
ORA-06808: TLI Driver: could not link IPX and ethernet streams
Cause: Either the ethernet driver has not been installed in the system correctly, or the
ethernet driver is not supported.
Action: Insure that the ethernet driver has been installed by completing the TCP/IP
installation on your system, and testing a connection. If problem continues, contact
your customer support representative for a list of supported ethernet drivers.
ORA-06809: TLI Driver: could not clear the IPX ethernet SAP at init
ORA-06810: TLI Driver: could not set the IPX ethernet SAP at init
ORA-06811: TLI Driver: could not set the IPX network number at init
Cause: The IPX driver has not been correctly installed, or the network number
encoded in the /etc/netware/yellowpages file is invalid.
Action: The network number in the yellowpages file should match the four-byte
network number of your Novell file server. If this is configured correctly, reinvoke the
Oracle root installation. If problem continues, contact your customer support
representative.
ORA-06812: TLI Driver: could not read the ethernet driver's node address
Cause: The ethernet driver is not installed correctly, or does not support this
operation.
Action: Contact your customer support representative for a list of supported ethernet
drivers.
ORA-06813: TLI Driver: the configured ethernet address is incorrect
Cause: The node address read from the ethernet driver does not match the value
encoded in the /etc/netware/yellowpages file for this server.
Action: Confirm the correct ethernet node address for your LAN card, and enter this
value in the yellowpages file.
ORA-06814: TLI Driver: the SPX device file could not be opened
Cause: The /dev/nspxd file does not exist, or the driver has not been installed in the
kernel correctly.
ORA-06815: TLI Driver: could not link SPX and IPX streams
Cause: The SPX driver has not been correctly installed.
ORA-06816: TLI Driver: could not set the SPX SAP address
Cause: The SPX driver has not been correctly installed.
ORA-04930 to ORA-07499 62-37
ORA-06817: TLI Driver: could not read the Novell network address
Cause: The file $ORACLE_HOME/spx/address could not be opened for reading and
writing.
Action: Make sure ORACLE_HOME is set, and the permissions on the
ORACLE_HOME are read, write. If this file has been unintentially deleted, run spxctl
(net option) to reset the configured Novell network number for SQL*Net SPX.
ORA-06900: CMX: cannot read tns directory
Cause: CMX is not started on your system.
Action: Install and/or start CMX on your system.
ORA-06901: CMX: no local name assigned to local application
Cause: Local application oracmx has no local name assigned
Action: Enter unique local name for oracmx in the tns directory
ORA-06902: CMX: cannot attach to cmx subsystem
Cause: ccp-xxxx is not started
Action: start your ccp software on the communication controller
ORA-06903: CMX: cannot read transport address of remote application
Cause: remote application not entered in tns directory
Action: enter remote application in tns directory
ORA-06904: CMX: no transport address available for remote application
Cause: no local name assigned to remote application
Action: assign local name to remote application
ORA-06905: CMX: connect error
Cause: remote partner not listening
Action: make sure remote node has CMX installed and running make sure oracmx is
running on remote host
ORA-06906: CMX: cannot get maximum packet size from CMX
Cause: internal error in CMX
Action: contact your customer support representative
ORA-06907: CMX: error during connect confirmation
Cause: remote partner aborted
ORA-06908: CMX: error during transfer of ORACLE_SID
ORA-06909: CMX: error during acknowledge of ORACLE_SID
ORA-06910: CMX: Cannot start oracle process on remote machine
Cause: oracle process not found or wrong mode (should be 4751)
Action: change /etc/oratab or set mode to 4751
ORA-06911: CMX: t_event returns ERROR

ORA-06912: CMX: write error in datarq
ORA-06913: CMX: error during redirection of connection
Cause: oracmx has been stopped, or user process has been aborted
ORA-06914: CMX: unexepected event during start of oracle
Cause: connect sequence out of sync
ORA-06915: CMX: unknown t_event in datarq
ORA-06916: CMX: error in data read (t_datain)
ORA-06917: CMX: error in data read (too many bytes read)
ORA-06918: CMX: T_NOEVENT during wait for read event
ORA-06919: CMX: error during write request (unknown event)
ORA-06920: CMX: getbrkmsg illegal datatype
Cause: received packets are corrupted
ORA-06921: CMX: getdatmsg illegal datatype
ORA-06922: CMX: bad write length
ORA-06923: CMX: illegal break condition
Cause: break handling out of sync
ORA-04930 to ORA-07499 62-39

ORA-06924: CMX: wrong break message length
ORA-06925: CMX: disconnect during connect request
Cause: partner is not responding
Action: make sure partner is up and running and reachable
ORA-06926: CMX: T_ERROR during read data
ORA-06927: CMX: T_DATAIN received before all data written
ORA-06928: CMX: wrong ORACLE_SID
Cause: ORACLE_SID is not entered in remote oratab
Action: add ORACLE_SID to remote oratab
ORA-06929: CMX: error when sending ORACLE_SID
ORA-06930: CMX: error when checking ORACLE_SID
ORA-06931: CMX: error during read_properties for server
ORA-06932: CMX: error in local name
ORA-06933: CMX: error during attach
ORA-06950: No error
Cause: SQL*Net AppleTalk error codes base. This is not an error.
Action: None
ORA-06951: Operating system call error
Cause: AppleTalk API received error in VMS system service.
Action: Contact Oracle Customer Support representative.
ORA-06952: Remote end of the communication issued a forward-reset packet.

Cause: Peer program may have aborted
Action: Investigate network problems and try again.
ORA-06953: Not enough virtual memory
Cause: Not enough memory available.
Action: Check VMS process quotas and/or sysgen parameters
ORA-06954: Illegal file name
Cause: Erroneous file name
Action: Check path name for server output file, or SQL*Net Appletalk Logical names
and symbols.
ORA-06955: Number of database servers exceed limit
Cause: Too many database connections.
Action: Check ATKSRV_MAXCONparameter in configuration file.
ORA-06956: Failed to get local host name
Cause: Unable to get Appletalk host name.
Action: Check Appletalk configuration.
ORA-06957: No SID is currently available
Cause: Incoming SQL*Net connection specified invalid SID name.
Action: Specify correct SID in connect string and retry.
ORA-06958: Failed to access configuration file
Cause: Unable to access CONFIG.ATK
Action: Check file protections.
ORA-06959: Buffer I/O quota is too small
Cause: Buffered I/O quota exceeded.
Action: Increase BIOlm using AUTHORIZE utility and retry.
ORA-06960: Failed to access log file
Cause: SQL*Net Appletalk listener could not create log file.
Action: Check directory path and protections.
ORA-06961: Insufficient privilege for attempted operation
ORA-06970: X.25 Driver: remote host is unknown
Cause: Host name specified in the login (connect string) is unknown.
Action: Check spelling; make sure name is in the X.25 HOST file.
ORA-06971: X.25 Driver: error while receiving data
ORA-06972: X.25 Driver: error while sending data
ORA-06973: X.25 Driver: invalid buffer size
Cause: The buffer size specified in the login string must be between 5 and 4096.
Action: Re-submit with valid buffer size.
ORA-04930 to ORA-07499 62-41
ORA-06974: X.25 Driver: SID lookup failure

Cause: From the remote host's SQL*Net X.25 server: the database SID, specified in the
login (connect) string, was not recognized.
Action: Add the appropriate SID entry to the CONFIG.ORA file on the remote host
(and restart the SQL*Net X.25 server).
ORA-06975: X.25 Driver: connect to host failed
Cause: Connection attempt to remote host has failed. Probably means that the
SQL*Net X.25 server on the remote host is not up, or the host itself is not up.
Action: Start the SQL*Net X.25 server process on the remote host.
ORA-06976: X.25 Driver: endpoint creation failure
Cause: Process open file quota probably exceeded.
ORA-06977: X.25 Driver: X.25 Level 2 failure
Cause: X.25 level 2 is down. X.25 link is not working.
Action: Run system checks to verify functioning of X.25 software. Contact your
hardware vendor.
ORA-06978: X.25 Driver: Too many callback tries
Cause: Call back address probably same as called address.
Action: Verify that callback address and called address are different.
ORA-06979: X.25 Driver: server cannot start oracle
Cause: The remote X.25 server was unable to start an ORACLE process on behalf of
the client.
Action: Make sure permissions on the remote ORACLE program are correctly set.
Contact your system administrator.
ORA-07200: slsid: oracle_sid not set.
Cause: The environment variable $(ORACLE_SID) is not set.
Action: Set ORACLE_SID environment variable.
ORA-07201: slhom: oracle_home variable not set in environment.
Cause: $(ORACLE_HOME) environment variable not set.
Action: Set ORACLE_HOME.
ORA-07202: sltln: invalid parameter to sltln.
Cause: The sltln name translation routine was called with invalid arguments. The
input, or output stings were either NULL or 0 length.
Action: Probable internal oracle error. Contact customer support.
ORA-07203: sltln: attempt to translate a long environment variable.
Cause: A string was passed to sltln containing a long environment variable. sltln
accepts environment names of 30 or less characters.
Action: Shorten environment variable name to less than 30 characters.
ORA-07204: sltln: name translation failed due to lack of output buffer space.
Cause: The sltln routine is given a maximum length buffer to expand the name into.
An overflow of this buffer occurred.
Action: Possible internal error. Check output buffer length stored in sercose[0].
Pathnames are limited to 255 characters.
ORA-07205: slgtd: time error, unable to obtain time.
Cause: Time() system call returned an error. Possible OS error.
Action: Check additional information returned. Contact customer support.
ORA-07206: slgtd: gettimeofday error, unable to obtain time.
Cause: Gettimeofday() system call returned an error. Possible OS error.
ORA-07207: sigpidu: process ID string overflows internal buffer.
Cause: The sigpidu routine is given a maximum length buffer to hold process ID
string. An overflow of this buffer occurred.
Action: Internal error. Contact customer support.
ORA-07208: sfwfb: failed to flush dirty buffers to disk.
Cause: The fsync system call returned an error. Possible OS error.
ORA-07209: sfofi: file size limit was exceeded.
Cause: The size of the file to be opened exceeded the OS limit imposed on this
process.
Action: Run osh to increase the file size limit.
ORA-07210: slcpu: getrusage error, unable to get cpu time.
Cause: Getrusage system call returned an error. Possible OS error.
ORA-07211: slgcs: gettimeofday error, unable to get wall clock.
Cause: Gettimeofday system call returned an error. Possible OS error.
Action: Check additional information returned in OS reference manual. Contact
customer support.
ORA-07212: slcpu: times error, unable to get cpu time.
Cause: times system call returned an error. Possible OS error.
ORA-07213: slgcs: times error, unable to get wall clock.
customer support.
ORA-07214: slgunm: uname error, unable to get system information.
Cause: uname system call returned an error. Possible OS error.
customer support.
ORA-07215: slsget: getrusage error.
Cause: Getrusage system call returned an error. Possible OS error.
ORA-04930 to ORA-07499 62-43
Action: Check additional information returned. Look for information in OS reference.

Contact customer support.
ORA-07216: slghst: gethostname error, unable to get name of current host.
Cause: gethostname system call returned an error. Possible OS error.
customer support.
ORA-07217: sltln: environment variable cannot be evaluated.
Cause: getenv call returned a null pointer.
Action: Set the environment variable and try again.
ORA-07218: slkhst: could not perform host operation
Cause: Unix system() call failed
Action: Examine system error message
ORA-07219: slspool: unable to allocate spooler argument buffer.
Cause: Malloc failed to allocate space to hold spooler arguments.
Action: Check additional information returned in OS reference manual. The process
may have run out of heap space. Contact customer support.
ORA-07220: slspool: wait error.
Cause: Wait returned an error, when waiting for spool job to complete. Possible
spooler program error.
Action: Check additional information returned. Refer to OS reference manual. Contact
customer support.
ORA-07221: slspool: exec error, unable to start spooler program.
Cause: Exec failed when starting line printer spooler command. Likely that either the
default line printer command, or ORACLE_LPPROG, is incorrectly set.
Action: Verify default line printer command and ORACLE_LPPROG are set correctly.
Set ORACLE_LPPROG to working line printer spooler.
ORA-07222: slspool: line printer spooler command exited with an error.
Cause: The line printer spooler exited with a non-zero return value. This probably
indicates an error in spooling file.
Action: Verify that line printer spooler is up. Verify that ORACLE_LPPROG, and
ORACLE_LPARG are set properly. Check exit value returned as additional
informatin.
ORA-07223: slspool: fork error, unable to spawn spool process.
Cause: Fork system call failed to create additional process. Probable resource limit
reached.
Action: Check additional information returned. Retry operation. Contact system
administrator.
ORA-07224: sfnfy: failed to obtain file size limit; errno = string.
Cause: The ulimit system call returned an error.
Action: Check errno and contact customer support.
ORA-07225: sldext: translation error, unable to expand file name.
Cause: Additional information returned is error returned from sltln.
Action: Check additional information.

ORA-07226: rtneco: unable to get terminal mode.
Cause: The ioctl call returned an error. Possible OS error.
Action: Check additional information for errno. Contact customer support.
ORA-07227: rtneco: unable to set noecho mode.
ORA-07228: rtecho: unable to restore terminal to echo mode.
ORA-07229: slcpuc: error in getting number of CPUs.
Cause: error in mpcntl system call
Action: check errno and contact system administrator
ORA-07230: slemcr: fopen error, unable to open error file.
Cause: Fopen failed to open file.
Action: Try to determine which file was not opened. Check that file exists and is
accessible.
ORA-07231: slemcc: invalid file handle, seals do not match.
Cause: Function was called with an invalid argument. The file handle used was not
obtained be slemcr.
ORA-07232: slemcc: fclose error.
Cause: An error was encountered when closing the file. Possible OS error.
Action: Contact system administator.
ORA-07233: slemcw: invalid file handle, seals do not match.
Cause: Function was called with an invalid file handle. File handle was not obtained
by slemcr.
ORA-07234: slemcw: fseek error.
Cause: Unable to seek to desired position in file. Possible OS error. Possible internal
error.
Action: Verify that error message file is intact. Try to regenerate error message file.
ORA-07235: slemcw: fwrite error.
Cause: Unable to write item to file. Possible OS error. Possible permissions problem.
Action: Retry operation.
ORA-07236: slemop: open error.
Cause: Unable to open error file. Possible permissions problem.
Action: Verify permission on error message file. Check additional information for
errno.
ORA-04930 to ORA-07499 62-45
ORA-07237: slemcl: invalid file handle, seals do not match.

Cause: Function was called with an invalid file handle. Handle was not obtained by
previous call to slemop.
ORA-07238: slemcl: close error.
Cause: Unable to close file. Possible OS error.
Action: Contact system administator. Check additional information for errno.
ORA-07239: slemrd: invalid file handle, seals do not match.
Cause: Function was called with invalid file handle. Handle was not obtained by call
to slemop.
ORA-07240: slemrd: seek error.
Cause: Unable to seek to desired position in file. Possible OS error.
Action: Check that error file is still intact. Verify space on device. Contact system
administrator. Check additional information for errno.
ORA-07241: slemrd: read error.
Cause: Unable to read file. Possible OS error.
Action: Verify that error file is intact. Regenerate error message file. Contact customer
support. Check additional information for errno.
ORA-07242: slembfn: translation error, unable to translate error file name.
Cause: Additional information indicates error returned from sltln.
ORA-07243: supplied buffer not big enough to hold entire line
Cause: supplied buffer was not big enough
Action: Internal error. Contact customer support. Additional information indicates
how big the supplied buffer was.
ORA-07244: ssfccf: create file failed, file size limit reached.
Cause: An attempt was made to create a file that exceeds the process's file size limit.
Action: Run osh to raise the file size limit.
ORA-07245: sfccf: unable to lseek and write the last block.
Cause: An attempt was made to move and write to a bad device address.
Action: Check errno. Possible lack of space on device.
ORA-07246: sfofi: open error, unable to open database file.
Cause: sfofi returns an error.
Action: This is an oracle internal error.
ORA-07247: skgfrfms, skgfrnms: read error, unable to read block from database file
Cause: The ioctl() system call returned an error doing VOL_READ_MIRRORS.
Action: Check errno.
ORA-07248: sfwfb: write error, unable to write database block.
Cause: sfwfb returns an error.

ORA-07249: slsget: open error, unable to open /proc/pid.
Cause: The open() system call returned an error.
Action: Check that /proc has the right permissions.
ORA-07250: spcre: semget error, unable to get first semaphore set.
Cause: An error occurred when trying to get first semaphore set.
Action: Check errno. Verify that system is configured to have semaphores. Verify that
enough semaphores are available. Additional information indicates how many
semaphores were requested.
ORA-07251: spcre: semget error, could not allocate any semaphores.
Cause: Semget failed to even allocate a single semaphore. Either they are all in use or
the system is not configured to have any semaphores.
Action: Check to see if all semaphores are in use. Check to see if system is configured
to have semaphores. Check errno.
ORA-07252: spcre: semget error, could not allocate semaphores.
Cause: Semget system call returned an error. Possible resource limit problem.
Action: Check errno. Verify that enough semaphores are available in system. If
additional errors occur in destroying the semaphore sets then sercose[0] will be nonzero. If this occurs, remove the semaphore sets using ipcrm.
ORA-07253: spdes: semctl error, unable to destroy semaphore set.
Cause: Semctl system call returned an error.
Action: Check semaphore sets. May require manual cleanup. Check additional
information returned. Consult OS reference manual.
ORA-07254: spdcr: translation error while expanding ?/bin/oracle.
Cause: An error occurred while translating the name of the oracle executable.
Action: Check sercose[0] for error returned from sltln. Perhaps $(ORACLE_HOME) is
not set correctly.
ORA-07255: spini: cannot set up signal handler.
Cause: System failed to set up signal handler.
Action: Check errno and sercose[0] for the signal number that failed.
ORA-07256: sptrap: cannot set up signal handler to catch exceptions.
Cause: System failed to set up signal handler to catch exceptions.
ORA-07257: spdcr: translation error expanding program name.
Cause: Error ocurred when expanding program name ora_PNAME_@. The result of
this translation is put in argv[0] of oracle process.
Action: Check error returned by sltln returned in sercose[0].
ORA-07258: spdcr: fork error, unable to create process.
Cause: An error occurred when creating a new process.
Action: Check errno. Perhaps a system limit on the number of processes has been
exceeded.
ORA-04930 to ORA-07499 62-47
ORA-07259: spdcr: exec error, detached process failed in startup.

Cause: An oracle detached process died shortly after startup. Wait() indicated that a
child process terminated.
Action: Check ?/dbs directory for trace or core files. Check errno.
ORA-07260: spdcr: wait error.
Cause: Wait system call returned an error.
ORA-07261: spdde: kill error, unable to send signal to process.
Cause: Kill system call returned an error. Possibly an attempt to destroy an already
gone process.
ORA-07262: sptpa: sptpa called with invalid process id.
ORA-07263: sptpa: kill error.
Cause: Kill system call returned an error. Possible OS error.
Action: Check errno. Additional information indicates the process ID tested.
ORA-07264: spwat: semop error, unable to decrement semaphore.
Cause: Semop system call returned an error. Semaphore set may not exist.
Action: Check errno. Semaphore ID is returned in sercose[0]. Verify semaphore set
exists. A possible cause for this error is that a "shutdown abort" was done while this
process was running.
ORA-07265: sppst: semop error, unable to increment semaphore.
Cause: Semop system call returned an error. Semaphore set may not exist.
Action: Check errno. Semaphore ID is returned in sercose[0]. Check semaphore set
existence. A possible cause for this error is that a "shutdown abort" was done while
this process was running.
ORA-07266: sppst: invalid process number passed to sppst.
Cause: Function was passed an invalid oracle process id.
ORA-07267: spwat: invalid process number.
Action: Internal error. Additional information indicates the invalid process id.
ORA-07268: szguns: getpwuid error.
Cause: Getpwuid() could not find an entry in the passwd file for a user.
Action: Add an entry for the user in the passwd file.
ORA-07269: spdcr: detached process died after exec.
Cause: Detached process succesfully execed, but died shortly thereafter. Additional
information indicates exit code, and termination status.
Action: Check termination code for information as to why process exited. Check for
core dump or trace file.
ORA-07270: spalck: setitimer error, unable to set interval timer.

Cause: An error occurred while trying to set an interval timer. Probable porting
problem.
ORA-07271: spwat: invalid oracle process number.
Cause: Function was called with an invalid oracle process number (0).
Action: Internal oracle error.
ORA-07272: spwat: invalid semaphore set id.
Cause: Semaphore ID fetched from SGA was not initialized to valid value. Additional
information returned is semaphore set index, and oracle process number.
Action: Oracle internal error. Check semaphore set index. Check oracle process
number.
ORA-07273: sppst: invalid semaphore id.
Cause: Semaphore ID fetched from SGA contained an invalid value. Additional
information returned is semaphore set index, and oracle process number.
Action: Oracle internal error. Check semaphore set index. Check oracle process
number.
ORA-07274: spdcr: access error, access to oracle denied.
Cause: Unable to access "oracle" program. Verify ?/bin/oracle or $ORABCKPRG
exist, and are executable.
Action: Check errno returned.
ORA-07275: unable to send signal to process
Cause: The kill system call returned an error. Possibly an attempt to signal a process
which does not exist.
ORA-07276: no dba group in /etc/group.
Cause: A group has not been set up for dba users.
Action: Contact system administrator. Set up dba group in /etc/group.
ORA-07277: spdde: illegal pid passed as argument.
Cause: A 0 pid was passed to spdde.
Action: Internal error. .
ORA-07278: splon: ops$username exceeds buffer length.
Cause: Splon constructed an ops$username logon which exceeded the alloted buffer
space.
Action: Use a shorter Unix username, or use an oracle username. Contact customer
support.
ORA-07279: spcre: semget error, unable to get first semaphore set.
Cause: An error occurred when trying to get first semaphore set.
Action: Check errno. Verify that system is configured to have semaphores. Verify that
enough semaphores are available. Additional information indicates how many
semaphores were requested.
ORA-04930 to ORA-07499 62-49
ORA-07280: slsget: unable to get process information.

ORA-07281: slsget: times error, unable to get cpu time.
ORA-07282: sksaprd: string overflow.
Cause: The internal buffer is not big enough to hold the archive control string.
Action: Internal restriction. Try a shorter archive control string.
ORA-07283: sksaprd: invalid volume size for archive destination.
Cause: An invalid volume size was specified.
Action: Specify a valid volume size in archive control string.
ORA-07284: sksaprd: volume size specification not terminated properly.
Cause: Some non-numeric text follows the volume size specification.
Action: Enter a correct archive control string.
ORA-07285: sksaprd: volume size should not be specified for a disk file.
Cause: Volume size was specified for a disk file.
Action: If you are archiving to a disk file, do not specify its volume size.
ORA-07286: sksagdi: cannot obtain device information.
Cause: Stat on the log archiving device failed.
Action: Check the returned OSD error for the reason of failure.
ORA-07287: sksagdi: unsupported device for log archiving.
Cause: Log archiving to this device is unsupported.
Action: Try log archiving to a supported device.
ORA-07290: sksagdi: specified directory for archiving does not exist.
Cause: The specified pathname is not a directory.
Action: Verify that the archive destination directory exists.
ORA-07303: ksmcsg: illegal database buffer size.
Cause: The database buffer size must be a multiple of the database block size, and less
than the maximum block size.
Action: Verify that the db_block_size parameter is correct in INIT.ORA.
ORA-07304: ksmcsg: illegal redo buffer size.
Cause: The redo buffer size must be a multiple of machine block size.
Action: Verify that the log_buffer INIT.ORA parameter is correctly set.
ORA-07305: ksmcsg: illegal database buffer size.
Cause: The database buffer size must be a multiple of the extended cache mapping
size for indirect data buffers to be used.
Action: Verify that the db_block_size parameter is correct in INIT.ORA, or disable the
use_indirect_data_buffers parameter.
ORA-07324: smpall: malloc error while allocating pga.

Cause: Malloc library routine returned an error.
Action: Check errno. Possibly out of swap space.
ORA-07327: smpdal: attempt to destroy pga when it was not mapped.
Cause: Smpdal was called when the PGA had not been previously created.
ORA-07339: spcre: maximum number of semaphore sets exceeded.
Cause: The internal buffer is not big enough to hold the number of semaphore set
identifiers requested.
Action: Reconfigure OS to have more semaphores per set.
ORA-07345: The datafile name must not contain the string '..'.
Cause: The specified datafile name contains '..'.
Action: Correct the datafile name and retry the operation.
ORA-07346: slnrm: normalized file name is too long
Cause: After normalizing the specified file name, the resulting file name was too long.
Action: Specify the shorter file name and retry the operation.
ORA-07390: sftopn: translate error, unable to translate file name.
Cause: An error occurred while expanding the file name to open. Additional
information returns error generated in translation routine.
Action: Lookup additional error code for further information.
ORA-07391: sftopn: fopen error, unable to open text file.
Cause: Fopen library routine returned an error.
Action: Verify existence and permissions.
ORA-07392: sftcls: fclose error, unable to close text file.
Cause: Fclose library routine returned an error.
Action: Possible internal oracle error.
ORA-07393: unable to delete text file
Cause: An error occurred while deleting a text file.
Action: Verify that the file exists and check additional errors.
ORA-07394: unable to append string to text file
Cause: An error occurred while performing a string put operation.
Action: This is an internal error. Check additional information.
ORA-07400: slemtr: translated name for the message file is too long.
Cause: The name for the message file overflows internal buffer.
Action: Try making the complete path-name of the message file shorter by
reorganizing the directory hierarchy.
ORA-07401: sptrap: cannot restore user exception handlers.
Cause: The system failed to restore user exception handlers.
ORA-04930 to ORA-07499 62-51
ORA-07402: sprst: cannot restore user signal handler.

Cause: The system failed to restore user signal handlers.
ORA-07403: sfanfy: db_writers parameter not valid.
Cause: The db_writers parameter in INIT.ORA exceeds the system-dependent
maximum or is less than 0.
Action: Change the db_writers parameter in INIT.ORA.
ORA-07404: sfareq: Timeout occurred waiting for request to complete.
Cause: The master database writer timed out waiting for a write or close to complete.
One of the database writers may have stopped running.
Action: Check all database writer trace files. Shut down the database and try to warm
start.
ORA-07405: sptrap: cannot setup alternate signal stack.
Cause: The system failed to setup an alternate signal stack.
Action: Check errno and sercose[0] for the location where it failed.
ORA-07406: slbtpd: invalid number.
Cause: An impossible request for binary to decimal conversion was made.
Action: This conversion cannot be performed.
ORA-07407: slbtpd: invalid exponent.
Cause: An impossible request for binary to decimal conversion was made
ORA-07408: slbtpd: overflow while converting to packed decimal.
Cause: An impossible request for binary to decimal conversion was made.
ORA-07409: slpdtb: invalid packed decimal nibble.
Cause: An impossible request for decimal to binary conversion was made.
ORA-07410: slpdtb: number too large for supplied buffer.
Cause: An impossible request for decimal to binary conversion was made.
ORA-07411: slgfn: full path name too big for supplied buffer.
Cause: The supplied buffer is not big enough to hold the full path name.
Action: The construction of the full path name cannot be performed.
ORA-07412: sfaslv: Error getting entry in asynchronous write array.
Cause: One of the database writer processes could not locate its entry in the SGA.
ORA-07415: slpath: allocation of memory buffer failed.
Cause: Malloc() failed to allocate buffer for storing ORACLE_PATH.
Action: System has run out of heap space. Additional information indicates errno.
ORA-07416: slpath: pathname construction failed; lack of output buffer space.

Cause: The slpath routine is given a maximum length buffer to expand the name into.
An overflow of this buffer occurred.
Action: Possible internal error. Check output buffer length stored in sercose[0] and
constructed pathname length in sercose[1].
ORA-07417: sfareq: One or more database writers not active.
Cause: One or more of the database writer processes is no longer running.
Action: Check the trace files for the database writers. Shut down the database and try
to warm start.
ORA-07418: sfareq: Database writer got error in timing function.
Cause: An error occurred when the database writer called the system timing function.
Action: Check the database writer trace file. Shut down database and try to warm
start.
ORA-07419: sfareq: Database writer got error in timing function.
Cause: An error occurred when the database writer called the system timing function.
Action: Check the database writer trace file. Shut down database and try to warm
start.
ORA-07425: sdpri: error string in translating dump file location.
Cause: An oracle error occurred when translating the location of the dump file.
Action: Check the oracle error code.
ORA-07426: spstp: cannot obtain the location of dbs directory.
Cause: An oracle error occurred when translating the location of the dbs directory.
Action: Check additional information for the error returned from sltln.
ORA-07427: spstp: cannot change directory to dbs.
Cause: Chdir system call returned an error. Possible permission problems.
Action: Check additional information for the OS error code.
ORA-07431: fork failed
Cause: The server process was unable to fork a child process.
ORA-07432: unable to perform nested sleep
Cause: An attempt was made to make a process sleep when it was already sleeping.
This platform does not support this capability.
Action: Try the SLEEP command when the process is not sleeping.
ORA-07440: WMON process terminated with error
Cause: The wakeup monitor process died.
ORA-07441: function address must be aligned on string byte boundary
Cause: An improperly aligned function address was specified.
Action: Use a properly aligned function address.
ORA-04930 to ORA-07499 62-53
ORA-07442: function address must be in the range string to string

Cause: An invalid function address was specified.
Action: Use a valid function address.
ORA-07443: function string not found
Cause: An invalid function name was specified.
Action: Use a valid function name.
ORA-07444: function address string is not readable
Cause: An invalid function name/address was specified.
Action: Use a valid function name/address.
ORA-07445: exception encountered: core dump [string] [string] [string] [string]
[string] [string]
Cause: An operating system exception occurred which should result in the creation of
a core file. This is an internal error.
Action: Visit My Oracle Support to access the ORA-07445 Lookup tool (reference Note
7445.1) for more information regarding the specific ORA-07445 error encountered. An
Incident has been created for this error in the Automatic Diagnostic Repository
(ADR). When logging a service request, use the Incident Packaging Service (IPS) from
the Support Workbench or the ADR Command Interpreter (ADRCI) to automatically
package the relevant trace information (reference My Oracle Support Note 411.1). The
following information should also be gathered to help determine the root cause: changes leading up to the error - events or unusual circumstances leading up to the
error - operations attempted prior to the error - conditions of the operating system
and databases at the time of the error Note: The cause of this message may manifest
itself as different errors at different times. Be aware of the history of errors that
occurred before this internal error.
ORA-07446: sdnfy: bad value 'string' for parameter string.
Cause: The directory specified as the value for the stated parameter could not be
used.
Action: Make sure the directory you have specified is a valid directory/file
specification.
ORA-07447: ssarena: usinit failed.
Cause: Oracle failed to create a shared arena file.
Action: Use sercerrno field to determine cause of failure.
ORA-07448: ssarena: maximum number of shared arenas exceeded.
Cause: Oracle attempted to create more shared arena files than permitted.
Action: Raise the value for max_arena in INIT.ORA.
ORA-07449: sc: usnewlock failed.
Cause: Oracle failed to acquire a shared arena lock.
Action: Check result code in sercerrno to determine the cause of failure.
ORA-07451: slskstat: unable to obtain load information.
Cause: kstat library returned an error. Possible OS failure
Action: Check result code in sercose[0] for more information.
ORA-07452: specified resource manager plan does not exist in the data dictionary
Cause: User tried to load a resource manager plan that does not exist.
Action: Use a resource manager plan that exists in the data dictionary.
ORA-07453: requested resource manager plan schema does not contain
OTHER_GROUPS
Cause: User tried to load a resource manager plan schema that does not contain the
OTHER_GROUPS group.
Action: Use a resource manager plan schema that contains the OTHER_GROUPS
group.
ORA-07454: queue timeout, string second(s), exceeded
Cause: User session queued for longer than maximum specified queue queue
duration time for consumer group.
Action: Re-submit job at a later time or increase queue timeout.
ORA-07455: estimated execution time (string secs), exceeds limit (string secs)
Cause: User attempted to execute an operation whose estimated execution time
exceeds the limit specified for the consumer group.
Action: Execute job on behalf of another group, or increase limit.
ORA-07456: cannot set RESOURCE_MANAGER_PLAN when database is closed
Cause: An attempt was made to turn on the Resource Manager when the database
was closed.
Action: Open the database and try again.
ORA-07457: cannot set _INTERNAL_RESOURCE_MANAGER_PLAN because of
FORCE
Cause: An attempt was made to set the
_INTERNAL_RESOURCE_MANAGER_PLAN parameter, however this failed
because the current RESOURCE_MANAGER_PLAN has the FORCE prefix.
Action: Remove the FORCE prefix from the RESOURCE_MANAGER_PLAN
parameter.
ORA-07458: cannot set the RESOURCE_MANAGER_PLAN parameter
Cause: An attempt was made to set the RESOURCE_MANAGER_PLAN parameter,
however, this failed because the database was quiesced.
Action: Unquiesce the database.
ORA-07459: cannot restore the RESOURCE_MANAGER_PLAN parameter
Cause: An attempt was made to internally restore the
RESOURCE_MANAGER_PLAN parameter to the value before it was internally set.
This failed because the current plan was set by the user and therefore did not need to
be restored.
ORA-07460: cannot set the RESOURCE_MANAGER_PLAN parameter
Cause: An attempt was made to internally set the RESOURCE_MANAGER_PLAN
parameter, however, this failed because the current RESOURCE_MANAGER_PLAN
has the FORCE prefix.
ORA-04930 to ORA-07499 62-55
Action: Remove the FORCE prefix from the RESOURCE_MANAGER_PLAN

parameter.
ORA-07468: spwat: mset error, unable to set semaphore.
Cause: The mset routine returned an error. Semaphore may not exist.
Action: Check result code in sercerrno. Semaphore number returned in sercose[0].
ORA-07469: sppst: mclear error, unable to clear semaphore.
Cause: The mclear routine returned an error. Semaphore may not exist.
Action: Check result code in sercerrno. Semaphore number returned in sercose[0].
ORA-07470: snclget: cannot get cluster number.
Cause: The cluster_status system call failed to get status information for the current
cluster.
Action: Check result code in sercose[0]. Possible operating system failure.
ORA-07471: snclrd: name translation error of sgadef.dbf file name.
Cause: Unable to expand out ?/dbs/sgadef@.dbf file name.
Action: Verify $(ORACLE_HOME) and $(ORACLE_SID) are properly set. Check
error number returned from sltln in sercose[0].
ORA-07472: snclrd: open error when opening sgadef.dbf file.
Cause: open failed when opening the file ?/dbs/sgadef@.dbf
Action: Check errno. Possible permission problem. Verify that the file ?/dbs/
sgadef@.dbf exists.
ORA-07473: snclrd: read error when trying to read sgadef.dbf file.
Cause: Read had an error when reading sgadef.dbf file.
Action: Check errno. Verify file exists, and is correct size.
ORA-07474: snclrd: close error, unable to close sgadef.dbf file.
Cause: An error occurred in close, while closing the file "?/dbs/sgadef@.dbf"
Action: Check errno. Possible operating system error.
ORA-07475: slsget: cannot get vm statistics.
Cause: The vm_statistics system call failed to get virtual memory statistics.
Action: Check result code in sercerrno. Possible operating system failure.
ORA-07476: slsget: cannot get mapped memory statistics.
Cause: The vm_mapmem system call failed to get mapped memory statistics.
Action: Check result code in sercerrno. Possible operating system failure.
ORA-07477: scgcmn: lock manager not initialized.
Cause: Lock manager must be initialized before converting locks.
Action: Check result code in sercerrno. Possible lock manager failure.
ORA-07478: scgcmn: cannot get lock status.
Cause: lm_stat_lock failed.
ORA-07479: scgcmn: cannot open or convert lock.

Cause: lm_open or lm_open_convert failed.
ORA-07480: snchmod: cannot change permissions on ?/dbs/sgalm.dbf.
Cause: When creating an instance, snlmini could not change the permissions
on ?/dbs/sgalm.dbf
ORA-07481: snlmatt: cannot attach to lock manager instance.
Cause: lm_attach failed to attach to lock manager instance.
ORA-07482: snlmini: cannot create lock manager instance.
Cause: lm_create failed to create lock manager instance.
Action: Check permissions on ?/dbs, and remove ?/dbs/sgalm.dbf if it exists, then
retry.
ORA-07483: snlkget: cannot convert(get) lock.
Cause: lm_convert failed to convert(get) lock.
ORA-07484: snlkput: cannot convert(put) lock.
Cause: lm_convert failed to put lock value.
ORA-07485: scg_get_inst: cannot open instance number lock.
Cause: lm_open failed.
ORA-07486: scg_get_inst: cannot convert(get) instance number lock.
Cause: lm_convert failed to get lock value.
ORA-07487: scg_init_lm: cannot create lock manager instance.
Cause: lm_create failed.
ORA-07488: scgrcl: lock manager not initialized.
Cause: Lock manager must be initialized before releasing locks.
ORA-07489: scgrcl: cannot get lock status.
Cause: lm_stat_lock failed during lock release/cancel.
ORA-07490: scgrcl: cannot convert lock.
Cause: lm_convert failed during lock release/cancel.
ORA-04930 to ORA-07499 62-57
ORA-07491: scgrcl: cannot cancel lock request.

Cause: lm_cancel failed during lock release/cancel.
ORA-07492: scgrcl: cannot close lock.
Cause: lm_close failed during lock release/cancel.
ORA-07493: scgrcl: lock manager error.
Cause: An error was encountered releasing the lock.
ORA-07494: scgcm: unexpected error.
Cause: Unknown or unexpected error code.
ORA-07495: spwat: lm_wait failed.
Cause: lm_wait failed.
ORA-07496: sppst: lm_post failed.
Cause: lm_post failed.
ORA-07497: sdpri: cannot create trace file 'string'; errno = string.
Cause: 1. The trace file could not be created for writing. 2. The trace file is a symbolic
link.
Action: 1. Check if the dump directory exists and whether it is writable. 2. Remove the
symbolic link.
ORA-07498: spstp: Unable to open /dev/resched.
Cause: The rescheduling driver /dev/resched is not found or is not working
properly.
Action: Check installation of the ORACLE rescheduling driver in the AIX kernel.
ORA-07499: spglk: Cannot reschedule.
Cause: The rescheduling driver /dev/resched is not open. This is an internal error
and should not occur.
63
ORA-07500 to ORA-09859
ORA-07500: scglaa: $cantim unexpected return
Cause: VMS system service $CANTIM returned an unexpected value
Action: Check for system error message and refer to VMS documentation
ORA-07501: scgtoa: $deq unexpected return
Cause: VMS system service $DEQ returned an unexpected value
ORA-07502: scgcmn: $enq unexpected return
Cause: VMS system service $ENQ returned an unexpected value
ORA-07503: scgcmn: $setimr unexpected return
Cause: VMS system service $SETIMR returned an unexpected value
ORA-07504: scgcmn: $hiber unexpected return
Cause: VMS system service $HIBER returned an unexpected value
ORA-07505: scggt: $enq parent lock unexpected return
ORA-07506: scgrl: $deq unexpected return on lockid string
ORA-07507: scgcm: unexpected lock status condition
Cause: A global locking system service returned an unexpected value.
Action: Check for system error message (if any) and refer to VMS documentation, or
contact your customer support representative.
ORA-07508: scgfal: $deq all unexpected return
ORA-07509: scgfal: $deq parent lock unexpected return
ORA-07500 to ORA-09859 63-1
ORA-07510: scgbrm: $getlki unexpected return on lockid string

Cause: VMS system service $GETLKI returned an unexpected value
ORA-07511: sscggtl: $enq unexpected return for master termination lock
ORA-07512: sscggtl: $enq unexpected return for client termination lock
ORA-07513: sscgctl: $deq unexpected return on cancel of term. lock
ORA-07514: scgcan: $deq unexpected return while canceling lock
ORA-07534: scginq: $getlki unexpected return on lockid string
Cause: VMS system service $GETLKI returned an unexpected value
ORA-07548: sftopn: Maximum number of files already open
Cause: Too many test files open
Action: This is an internal error, please report to Oracle
ORA-07549: sftopn: $OPEN failure
Cause: VMS system service $OPEN failed
Action: Examine system error message and refer to VMS documentation
ORA-07550: sftopn: $CONNECT failure
ORA-07551: sftcls: $CLOSE failure
Cause: VMS system service $CLOSE failed
ORA-07552: sftget: $GET failure
Cause: VMS system service $GET failed
ORA-07561: szprv: $IDTOASC failure
Cause: VMS system service $IDTOASC failed
ORA-07562: sldext: extension must be 3 characters
Cause: An extension was found but it is of improper length
63-2 Error Messages

ORA-07563: sldext: $PARSE failure
Cause: VMS system service $PARSE failed
ORA-07564: sldext: wildcard in filename or extension
Cause: A wildcard was used in the file name
Action: Reenter the file name completely
ORA-07565: sldext: $SEARCH failure
Cause: VMS system service $SEARCH failed
ORA-07568: slspool: $OPEN failure
ORA-07569: slspool: $CLOSE failure
ORA-07570: szrfc: $IDTOASC failure
Cause: VMS system service $IDTOASC failed
ORA-07571: szrfc: $FIND_HELD failure
Cause: VMS system service $FIND_HELD failed
ORA-07572: szrfc: insufficient rolename buffer space
Cause: An OS role name was too long.
Action: Re-define the role name to be of correct length.
ORA-07573: slkhst: could not perform host operation
Cause: VMS system service LIB$SPAWN failed
ORA-07574: szrfc: $GETUAI failure
Cause: VMS system service $GETUAI failed
ORA-07576: sspexst: $GETJPIW failure on process ID string
Cause: VMS system service $GETJPIW failed
ORA-07577: no such user in authorization file
Cause: An attempt was made to set an INTERNAL password (for either DBA or
OPER privilege), but the corresponding VMS account (either ORA_sid_DBA or
ORA_sid_OPER) hasn't been created yet.
ORA-07500 to ORA-09859 63-3
Action: Add a VMS account for ORA_sid_DBA and/or ORA_sid_OPER before trying
to set a password for them.
ORA-07578: szprv: $FIND_HELD failure
Cause: VMS system service $FIND_HELD failed
ORA-07579: spini: $DCLEXH failure
ORA-07580: spstp: $GETJPIW failure
ORA-07581: spstp: cannot derive SID from unexpected process name
Cause: A background process did not have name of correct form
Action: If the job name was changed, restore it, otherwise this is an internal error,
please report to Oracle.
ORA-07582: spstp: ORA_SID has illegal value
Cause: The ORA_SID must exist and be less than 6 characters
Action: Consult the VMS Installation guide for information on setting the SID.
ORA-07584: spdcr: invalid value for ORA_sid_(proc_)PQL$_item
Cause: A logical name used to set a detached process quota value has an invalid value
(probably non-numeric).
Action: Examine the values of these logical names, correct the one in error, and retry.
ORA-07585: spdcr: $PARSE failure
ORA-07586: spdcr: $SEARCH failure
Cause: VMS system service $SEARCH failed
ORA-07587: spdcr: $CREPRC failure
Cause: VMS system service $CREPRC failed
ORA-07588: spdcr: $GETJPIW get image name failure
ORA-07589: spdde: system ID not set
Cause: The logical name ORA_SID doesn't translate to a valid value.
Action: Check the value of ORA_SID in the process that gets the error, and correct the
installation or command procedures that caused ORA_SID to be set incorrectly.
63-4 Error Messages
ORA-07590: spdde: $DELPRC failure

Cause: VMS system service $DELPRC failed
ORA-07591: spdde: $GETJPIW failure
ORA-07592: sspgprv: Error obtaining required privileges
Cause: While obtaining needed privileges, an error was returned from SYS$SETPRV.
Action: This is an internal error. Please report to Oracle
ORA-07593: ssprprv: Error release privileges
Cause: While releasing privileges, an error was returned from SYS$SETPRV.
Action: This is an internal error. Please report to Oracle
ORA-07594: spiip: $GETJPIW failure
ORA-07595: sppid: $GETJPIW failure
ORA-07596: sptpa: $GETJPIW failure
ORA-07597: spguns: $GETJPIW failure
ORA-07598: spwat: $SETIMR failure
ORA-07599: spwat: $SCHDWK failure
Cause: VMS system service $SCHDWK failed
ORA-07600: slkmnm: $GETSYIW failure
Cause: VMS system service $GETSYIW failed
ORA-07601: spguno: $GETJPIW failure
ORA-07602: spgto: $GETJPIW failure
ORA-07500 to ORA-09859 63-5

ORA-07605: szprv: $ASCTOID failure
Cause: VMS system service $ASCTOID failed
ORA-07606: szprv: $CHKPRO failure
Cause: VMS system service $CHKPRO failed
ORA-07607: szaud: $SNDOPR failure
Cause: VMS system service $SNDOPR failed
ORA-07608: szprv: $GETUAI failure
ORA-07609: szprv: $HASH_PASSWORD failure
Cause: VMS system service $HASH_PASSWORD failed
ORA-07610: $GETJPIW failed in retrieving the user's MAC priviledges
ORA-07612: $GETUAI failed in retrieving the user's clearance level
ORA-07613: $GETJPIW failed in retrieving the user's process label
ORA-07614: $CHANGE_CLASS failed in retrieving the user's process label
Cause: VMS system service $CHANGE_CLASS failed
Action: Examine system error message and refer to SEVMS documentation
ORA-07615: $CHANGE_CLASS failed in retrieving the specified file label
Cause: VMS system service $CHANGE_CLASSS failed
ORA-07616: $CHANGE_CLASS failed in retrieving the specified device label
Cause: VMS system service $CHANGE_CLASS failed
ORA-07617: $FORMAT_CLASS failed translating the binary label to a string
Cause: VMS system service $FORMAT_CLASS failed because the given binary
classification was not valid.
63-6 Error Messages
ORA-07618: $IDTOASC failed translating a secrecy level

Cause: VMS system service $IDTOASC failed while looking up the string
representation in the rights database of a secrecy level.
Action: Define the entry in the rights database which the binary label you specified
references.
ORA-07619: $IDTOASC failed translating an integrity level
representation in the rights database of an integrity level.
references.
ORA-07620: smscre: illegal database block size
Cause: An illegal database block size was specified in the parameter file. It must be
positive, a multiple of 512, and less than the maximum physical i/o data size.
Action: Change db_block_size in the parameter file to conform to these limits.
ORA-07621: smscre: illegal redo block size
Cause: An illegal redo log buffer size was specified in the parameter file. It must be
positive and a multiple of 512.
Action: Change log_buffer in the parameter file to conform to these limits.
ORA-07622: smscre: $CREATE failure
Cause: While creating the system global area (SGA) backing file, VMS system service
$CREATE failed.
Action: Examine the system error message and refer to VMS documentation.
ORA-07623: smscre: $CRMPSC failure
Cause: While creating the system global area (SGA), VMS system service $CRMPSC
failed.
ORA-07624: smsdes: $DGBLSC failure
Cause: While deleting the system global area (SGA), VMS system service $DGBLSC
failed.
ORA-07625: smsget: $MGBLSC failure
Cause: While mapping the system global area (SGA) during logon, VMS system
service $MGBLSC failed. The usual reason is that Oracle has not been started up.
Action: Examine the system error message and refer to VMS documentation. Start up
Oracle if it is not already started.
ORA-07626: smsget: sga already mapped
Cause: An attempt to map the SGA during logon failed because it was already
mapped. This is an internal error.
Action: Exit your program and try again, and report this to your customer support
representative.
ORA-07500 to ORA-09859 63-7
ORA-07627: smsfre: $CRETVA failure

Cause: While unmapping the system global area (SGA) during logoff, VMS system
service $CRETVA failed.
ORA-07628: smsfre: sga not mapped
Cause: An attempt to unmap the SGA during logoff failed because it was not
mapped. This is an internal error.
Action: Exit your program and try again, and report this to your customer support
representative.
ORA-07629: smpall: $EXPREG failure
Cause: While extending the program global area (PGA), VMS system service
$EXPREG failed. This often happens when the virtual memory page count quota is
exceeded.
ORA-07630: smpdal: $DELTVA failure
Cause: While deleting the program global area (PGA) during logoff, VMS system
service $DELTVA failed.
ORA-07631: smcacx: $EXPREG failure
Cause: While creating or extending a context area, VMS system service $EXPREG
failed. This often happens when the virtual memory page count quota is exceeded.
ORA-07632: smsrcx: $DELTVA failure
Cause: While deleting a context area, VMS system service $DELTVA failed.
ORA-07633: smsdbp: illegal protection value
Cause: The buffer debug function was called with an illegal value. This is an internal
error.
ORA-07634: smsdbp: $CRETVA failure
Cause: While attempting to set protection in the database buffer debug mechanism,
VMS system service $CRETVA failed.
ORA-07635: smsdbp: $SETPRT failure
VMS system service $SETPRT failed.
ORA-07636: smsdbp: $MGBLSC failure
VMS system service $MGBLSC failed.
63-8 Error Messages
ORA-07637: smsdbp: buffer protect option not specified when sga created
Cause: Trying to change the buffer protect mode when the SGA was not created with
buffer protect debug option. This is an internal error.
ORA-07638: smsget: SGA pad area not large enough for created SGA
Cause: An attempt was made to map an SGA with software in which the SGA pad
area isn't large enough.
Action: Create a smaller SGA, or relink the software with a larger pad.
ORA-07639: smscre: SGA pad area not large enough (string bytes required)
Cause: An attempt was made to create an SGA with software in which the SGA pad
area isn't large enough.
Action: Create a smaller SGA, or relink the software with a larger pad.
ORA-07640: smsget: SGA not yet valid. Initialization in progress
Cause: An attempt was made to map to the SGA while it was being initialized.
Action: Wait until initialization is complete, and try again.
ORA-07641: smscre: Unable to use the system pagefile for the SGA
Cause: The system global area (SGA) backing file could not be allocated using the
system pagefile because the system-wide limit on global pages has been exceeded.
Action: Either increase the VMS system parameter GBLPAGFIL or use a disk file as
the SGA backing file.
ORA-07642: smprtset: $CMKRNL failure
Cause: While attempting to set the protection of a region of memory, an error was
returned from the $CMKRNL system service.
ORA-07643: smsalo: SMSVAR is invalid
Cause: an internal error
Action: Report this error to Oracle Support Services, provide your INIT.ORA file.
ORA-07645: sszfsl: $CHANGE_CLASS failure
Cause: While attempting to set the label on a file, SEVMS service $CHANGE_CLASS
failed.
Action: Examine the system message and refer to SEVMS system documentation.
ORA-07646: sszfck: $CREATE failure
Cause: While attempting to create a file, VMS system service $CREATE failed.
Action: Examine the system message and refer to VMS system documentation.
ORA-07647: sszfck: $OPEN failure
Cause: While attempting to reopen a file, VMS system service $OPEN failed.
Action: Examine the system message and refer to VMS system documentation.
ORA-07650: sigunc: $GETJPIW failure
Cause: While attempting to get the user's terminal device name, user name, user
program name, or process name during logon, VMS system service $GETJPIW failed.
ORA-07500 to ORA-09859 63-9
ORA-07655: slsprom:$TRNLOG failure

Cause: While attempting to translate SYS$INPUT during a prompt for a password,
VMS system service $TRNLOG failed.
ORA-07656: slsprom:$GETDVI failure
Cause: While attempting to get device characteristics during a prompt for a password,
VMS system service $GETDVI failed.
ORA-07657: slsprom:$ASSIGN failure
Cause: While prompting for a password, VMS system service $ASSIGN failed.
ORA-07658: slsprom:$QIOW read failure
Cause: While prompting for a password, VMS system service $QIOW failed.
ORA-07665: ssrexhd: recursive exception encountered string string string string
string string
Cause: A VMS exception occurred while executing in the Oracle exception handler.
The message includes the signal number, first and second signal arguments, and
exception PC, PSL and R0. This is an internal error.
ORA-07670: $IDTOASC failed translating a secrecy category
representation in the rights database of a secrecy category.
references.
ORA-07671: $IDTOASC failed translating an integrity category
representation in the rights database of an integrity category.
references.
ORA-07672: $PARSE_CLASS failed translating the string into a binary label
Cause: SEVMS system service $PARSE_CLASS failed because the given string did not
represent a valid classification.
Action: Examine system error message and refer to SEVMS documentation.
ORA-07680: sou2os: another call to Oracle currently executing
Cause: A call to the Oracle shared image entry point occurred from within the shared
image. This is an internal error.
ORA-07681: sou2os: An error occurred while initializing Oracle
Cause: While attempting to set up the dispatch vectors for the shared image, an error
occurred. This is an internal error.
ORA-07682: sou2os: set kernel dispatch fail err

Cause: During Oracle shared image entry, a dispatch to kernel mode failed.
Action: Make sure that your shared image is installed with the CMKRNL privilege,
then contact your customer support representative.
ORA-07683: sou2os: $SETPRV reset error
Cause: During an attempt to restore user privileges at Oracle shared image exit, VMS
system service $SETPRV failed. This is an internal error.
ORA-07684: sou2os: supervisor stack reset error
Cause: During an attempt to restore the supervisor-mode stack at Oracle shared
image exit, VMS system service $SETSTK failed. This is an internal error.
ORA-07685: sou2os: supervisor stack set error
Cause: During an attempt to set the Oracle supervisor-mode stack at Oracle shared
image entry, VMS system service $SETSTK failed. This is an internal error.
ORA-07700: sksarch: interrupt received
Cause: An interrupt was received while archiving the logs
Action: Retry operation
ORA-07701: sksatln: internal exception: output buffer too small
Cause: Overflow of buffer for parsing archive control text string
ORA-07702: unrecognized device type in archive text
Cause: Unrecognized device type in archive text
ORA-07703: error in archive text: need '/' after device type
Cause: The archive control text in the ARCHIVE command is invalid; the device type
(to indicate a file or tape) must be followed by a '/'.
Action: Refer to the SQLDBA Guide for the proper syntax of the text.
ORA-07704: error in archive text: need ':' after device name
Cause: The archive control text in the ARCHIVE command is invalid; the device name
must be followed by a ':'.
ORA-07705: sksaprs: device name buffer too small
Cause: The buffer supplied for the device name is too small. This is an internal error.
ORA-07706: error in archive text: need disk file name
Cause: The archive control text in the ARCHIVE command is invalid; the disk file
name is missing.
ORA-07500 to ORA-09859 63-11
ORA-07707: error in archive text: need tape label name

Cause: The archive control text in the ARCHIVE command is invalid; the tape label
name is missing.
ORA-07708: sksaprs: tape label name buffer too small
Cause: The buffer supplied for the tape label is too small. This is an internal error.
ORA-07709: sksaprs: archiving to a remote host is not allowed
Cause: The user specified a remote disk for archiving via DECnet.
Action: Archive to a disk on the local host.
ORA-07710: sksaprs: file name buffer too small
Cause: The buffer supplied for the file name is too small. This is an internal error.
ORA-07713: sksamtd: could not mount archival device (SYS$MOUNT failure)
Cause: VMS system service SYS$MOUNT failed
ORA-07715: sksadtd: could not dismount archival device (SYS$DISMNT failure)
Cause: VMS system service SYS$DISMNT failed
ORA-07716: sksachk: invalid device specification for ARCHIVE
Cause: VMS system service SYS$GETDVI failed"
Action: Specify a valid device in ARCHIVE control string
ORA-07717: sksaalo: error allocating memory
Cause: VMS system service LIB$GET_VM failed"
ORA-07718: sksafre: error freeing memory
Cause: VMS system service LIB$FREE_VM failed
ORA-07721: scgcm: not enough OS resource to obtain system enqueue
Cause: A call to sys$enq returned an error indicating that the operating system lacked
the resources necessary to create a lock. This is caused by the messages SS
$_EXENQLM or SS$_INSFMEM.
Action: Free up some of the required resource to allow the creation of the required
lock.
ORA-07740: slemop: incorrect handle size (programming error)
Cause: structures used for reading error message files do not match
Action: this is an internal error, please report to Oracle
ORA-07741: slemop: $OPEN failure
ORA-07742: slemop: $CONNECT failure

Cause: VMS system service $CONNECT failed
ORA-07743: slemop: incorrect error file attributes
Cause: An error message file is of incorrect format
Action: Unless an error file has been changed, report this to Oracle
ORA-07744: slemcl: invalid error message file handle
Cause: seal in passed in handle does not match correct value
ORA-07745: slemcl: $CLOSE failure
Action: Check system error and refer to VMS documentation
ORA-07746: slemrd: invalid error message file handle
Cause: seal in passed in handle does not match correct value
ORA-07747: slemrd: $READ failure
Cause: VMS system service $READ failed
ORA-07750: slemcr: fopen failure
Cause: An attempt to create a message file failed. This is an internal error.
ORA-07751: slemcr: malloc failure
Cause: An attempt to allocate a cache for a newly-created message file failed. This is
an internal error.
ORA-07753: slemcf: fseek before write failure
Cause: An attempt to seek before writing a message file cache element failed. This is
an internal error.
ORA-07754: slemcf: fwrite failure
Cause: An attempt to write a message file cache element failed. This is an internal
error.
ORA-07755: slemcf: fseek before read failure
Cause: An attempt to seek before reading a message file cache element failed. This is
an internal error.
ORA-07756: slemcf: fread failure
Cause: An attempt to read a message file cache element failed. This is an internal
error.
ORA-07500 to ORA-09859 63-13

ORA-07757: slemcc: invalid handle
Cause: The seal in a passed-in handle does not match correct value. This is an internal
error.
ORA-07758: slemcw: invalid handle
Cause: The seal in a passed-in handle does not match correct value. This is an internal
error.
ORA-07759: slemtr: invalid destination
Cause: The destination string provided to the function is too short This is an internal
error.
ORA-07760: slemtr: $open failure
Cause: the $open service failed. This is an internal error
ORA-07800: slbtpd: invalid number
ORA-07801: slbtpd: invalid exponent
ORA-07802: slbtpd: overflow while converting to packed decimal
ORA-07803: slpdtb: invalid packed decimal nibble
Cause: An impossible request for decimal to binary conversion was made
ORA-07804: slpdtb: number too large for supplied buffer
Cause: An impossible request for decimal to binary conversion was made
ORA-07820: sspscn: SYS$CRELNM failure
Cause: An error was returned from the SYS$CRELNM function
ORA-07821: sspsdn: SYS$DELLNM failure
Cause: An error was returned from the SYS$DELLNM function
ORA-07822: sspscm: SYS$CREMBX failure

Cause: An error was returned from the SYS$CREMBX function while trying to create
the process dump mailbox.
ORA-07823: sspsqr: $QIO failure
Cause: An error was returned from $QIO while trying to queue a read to the process
dump mailbox.
ORA-07824: sspain: $SETIMR failure
Cause: An error was returned from SYS$SETIMR while trying to queue a process
spin-watch timer.
ORA-07825: sspsck: $QIO failure at AST level
Cause: An error was returned from SYS$QIO while trying to read the process dump
mailbox.
ORA-07826: sspscm: SYS$GETDVIW failure
Cause: An error was returned from SYS$GETDVIW while trying to get information
about the process dump mailbox.
ORA-07840: sllfop: LIB$GET_VM failure
Cause: An error was returned from LIB$GET_VM while attempting to allocate
memory for an i/o vector.
ORA-07841: sllfop: SYS$OPEN failure
Cause: An error was returned from SYS$OPEN while attempting to open the data file
for reading
ORA-07842: sllfcl: SYS$CLOSE failure
Cause: An error was returned from SYS$CLOSE while attempting to close the input
data file
ORA-07843: sllfcl: LIB$FREE_VM failure
Cause: An error was returned from LIB$FREE_VM while attempting to free the
memory for the i/o vector
ORA-07844: sllfop: LIB$GET_VM failure
Cause: An error was returned from LIB$GET_VM while attempting to allocate
memory for data and index buffers
ORA-07500 to ORA-09859 63-15
ORA-07845: sllfcl: LIB$FREE_VM failue

Cause: An error was returned from LIB$FREE_VM while attempting to free memory
used by data and index buffers
ORA-07846: sllfop: string byte record too big for string byte user buffer
Cause: The longest record in the file will not fit into the largest data buffer that can be
allocated
Action: Modify the RMS file to have smaller records
ORA-07847: sllfop: $CONNECT failure
Cause: An error was returned by SYS$CONNECT while attempting to open the data
file
ORA-07848: sllfrb: $GET failure
Cause: An error was returned by SYS$GET while attempting to read the data file
ORA-07849: sllfsk: $GET failure
Cause: An error was returned by SYS$GET while attempting to skip records in the
input file
ORA-07850: sllfop: bad option
Cause: You are using a bad option to loader Fixed= is one legal option. Check
documentation for others.
Action: Check documentation
ORA-07860: osnsoi: error setting up interrupt handler
Cause: An error occurred while setting up the control interrupt handler
Action: This is an internal error. Contact your Oracle representative.
ORA-07880: sdopnf: internal error
Cause: A list of all files open by this process could not be obtained.
Action: This is an internal error. Contact your customer support representative.
ORA-08000: maximum number of session sequence lists exceeded
Cause: the sequence parent state objects for this session are all used
Action: an internal error; quit the session and begin a new one
ORA-08002: sequence string.CURRVAL is not yet defined in this session
Cause: sequence CURRVAL has been selected before sequence NEXTVAL
Action: select NEXTVAL from the sequence before selecting CURRVAL
ORA-08003: sequence string.NEXTVAL exceeds internal limits
Cause: The sequence was created with unsafe values for some of the parameters. The
calculation of NEXTVAL cannot be made because it exceeds the legal represention
size.
Action: Alter or recreate the sequence number with legal limits.
ORA-08004: sequence string.NEXTVAL string stringVALUE and cannot be

instantiated
Cause: instantiating NEXTVAL would violate one of MAX/MINVALUE
Action: alter the sequence so that a new value can be requested
ORA-08005: specified row does not exist
Cause: A row with the given rowid does not exist in any of the tables given
Action: check the query for misspellings of table names and the rowid
ORA-08006: specified row no longer exists
Cause: the row has been deleted by another user since the operation began
Action: re-try the operation
ORA-08007: Further changes to this block by this transaction not allowed
Cause: Max locks have been reached for this transaction in this block
Action: Commit changes
ORA-08008: another instance is mounted with USE_ROW_ENQUEUES = string
Cause: the shared instance being started does not have the same value for
use_row_enqueues as already running instances
Action: ensure that all instances' INIT.ORA files specify the same value for the
parameter 'use_row_enqueues'
ORA-08100: index is not valid - see trace file for diagnostics
Cause: Validate Index detected an inconsistency in its argument index
Action: Send trace file to your customer support representative
ORA-08101: index key does not exist file string: (root string, node string) blocks
(string)
Cause: Internal error: possible inconsistency in index
Action: Send trace file to your customer support representative, along with
information on reproducing the error
ORA-08102: index key not found, obj# string, file string, block string (string)
Cause: Internal error: possible inconsistency in index
information on reproducing the error
ORA-08103: object no longer exists
Cause: The object has been deleted by another user since the operation began, or a
prior incomplete recovery restored the database to a point in time during the deletion
of the object.
Action: Delete the object if this is the result of an incomplete recovery.
ORA-08104: this index object string is being online built or rebuilt
Cause: the index is being created or rebuild or waited for recovering from the online
(re)build
Action: wait the online index build or recovery to complete
ORA-08105: Oracle event to turn off smon cleanup for online index build
Cause: set this event only under the supervision of Oracle development
ORA-07500 to ORA-09859 63-17
Action: debugging only

ORA-08106: cannot create journal table string.string
Cause: The online index builder could not create its journal table
Action: Rename the conflicting table or rerun the SQL statement. There * may be a
concurrent online index rebuild on the same object. rename your table in conflict or
rerun the SQL statement * there may be a concurrent online index rebuild on the same
object.
ORA-08108: may not build or rebuild this type of index online
Cause: only support normal index or IOT top-level index
Action: change your index type
ORA-08109: nosort is not a supported option for online index build
Cause: may not specify nosort for online index build
Action: get rid of nosort in the index creation command
ORA-08110: Oracle event to test SMON cleanup for online index build
Cause: Oracle Kernel test only
Action: Donot set this event(for test only)
ORA-08111: a partitioned index may not be coalesced as a whole
Cause: User attempted to coalesce a partitioned index using ALTER INDEX
COALESCE statement, which is illegal
Action: Coalesce the index a (sub)partition at a time (using ALTER INDEX MODIFY
(sub)PARTITION COALESCE)
ORA-08112: a composite partition may not be coalesced as a whole
Cause: User attempted to coalesce a composite partition
Action: Coalesce the index a subpartition at a time (using ALTER INDEX MODIFY
SUBPARTITION COALESCE)
ORA-08113: composite partition index may not be compressed
Cause: User attempted to compress a composite partition index
Action: create uncompressed composite partition index
ORA-08114: can not alter a fake index
Cause: User attempted to alter a fake index
Action: drop fake index
ORA-08115: can not online create/rebuild this index type
Cause: User attempted to create index type that online doesnot support
Action: use offline index create/rebuild command
ORA-08116: can not acquire dml enough lock(S mode) for online index build
Cause: User attempted to create index online without allowing DML Share lock
Action: allow DML share lock on the base table
ORA-08117: Index Organized Table operation released its block pin
Cause: Block maintenance forced the release of a block pin
Action: Contact your customer support representative
ORA-08118: Deferred FK constraints cannot be enforced, index too big (string)

Cause: Deferred Foreign Key constraints cannot be enforced due to the index key
being too big and built on a non-default DB_BLOCK_SIZE.
Action: First try to drop the Foreign Key and then the primary key.
ORA-08119: The new initrans will make the index too big
Cause: Specifying the initrans need additional space to hold the index key which
might make the index too big
Action: Try giving a smaller initrans value
ORA-08120: Need to create SYS.IND_ONLINE$ table in order to (re)build index
Cause: Alter index Build/Rebuild online require existing of SYS.IND_ONLINE$
table.
Action: User/DBA needs to create sys.ind_online$ before alter the index /rdbms/
admin/catcio.sql contains script to create ind_online$.
ORA-08121: Number of indexes need to be maintained offline exceeds limit for
DML
Cause: Too many indexes needed to be maintained. The limit is 2^16 indexes for each
DML statement
Action: Make sure the index maintainance is online. If indexes need to be maintained
offline, drop some indexes.
ORA-08122: Online (re)build of index rolled back due to DML conflict
Cause: The online (re)build journal is inconsistent with ongoing DML and cannot be
used successfully to complete the online index (re)build.
Action: Reissue the online (re)build operation, after performing any cleanup, if
needed.
ORA-08175: discrete transaction restriction violated (string)
Cause: An attempt was made to perform an action that is not currently supported in a
discrete transaction.
Action: Rollback the transaction, and retry it as a normal transaction.
ORA-08176: consistent read failure; rollback data not available
Cause: Encountered data changed by an operation that does not generate rollback
data : create index, direct load or discrete transaction.
Action: In read/write transactions, retry the intended operation. Read only
transactions must be restarted.
ORA-08177: can't serialize access for this transaction
Cause: Encountered data changed by an operation that occurred after the start of this
serializable transaction.
Action: In read/write transactions, retry the intended operation or transaction.
ORA-08178: illegal SERIALIZABLE clause specified for user INTERNAL
Cause: Serializable mode is not supported for user INTERNAL.
Action: Reconnect as another user and retry the SET TRANSACTION command.
ORA-07500 to ORA-09859 63-19
ORA-08179: concurrency check failed

Cause: Encountered data changed by an operation that occurred after a specific
snapshot. This is usually used to indicate that a particular cached copy of a datablock
is stale. This is used for internal use for now.
Action: refresh the cached copy of the datablock and retry operation.
ORA-08180: no snapshot found based on specified time
Cause: Could not match the time to an SCN from the mapping table.
Action: try using a larger time.
ORA-08181: specified number is not a valid system change number
Cause: supplied scn was beyond the bounds of a valid scn.
Action: use a valid scn.
ORA-08182: operation not supported while in Flashback mode
Cause: user tried to do dml or ddl while in Flashback mode
Action: disable Flashback and re-attempt the operation
ORA-08183: Flashback cannot be enabled in the middle of a transaction
Cause: user tried to do Flashback in the middle of a transaction
Action: do a commit
ORA-08184: attempting to re-enable Flashback while in Flashback mode
Cause: as stated above
Action: disable first before re-enabling
ORA-08185: Flashback not supported for user SYS
Cause: user logged on as SYS
Action: logon as a different (non SYS) user.
ORA-08186: invalid timestamp specified
Cause: as stated above
Action: enter a valid timestamp
ORA-08187: snapshot expression not allowed here
Cause: A snapshot expression using AS OF was specified when not allowed.
Action: Do not use the AS OF clause
ORA-08189: cannot flashback the table because row movement is not enabled
Cause: An attempt was made to perform Flashback Table operation on a table for
which row movement has not been enabled. Because the Flashback Table does not
preserve the rowids, it is necessary that row movement be enabled on the table.
Action: Enable row movement on the table
ORA-08190: restore point string is from a different incarnation of the database
Cause: An attempt was made to perform Flashback Table operation using a restore
point from a different incarnation of the database
Action: Provide a restore point from the current database incarnation
ORA-08191: Flashback Table operation is not supported on remote tables

Cause: An attempt was made to perform Flashback Table operation on a remote table.
This is not permitted.
Action: Do not perform a Flashback Table operation on remote tables.
ORA-08192: Flashback Table operation is not allowed on fixed tables
Cause: An attempt was made to perform Flashback Table operation on a fixed table.
Action: Do not perform a Flashback Table operation on fixed tables.
ORA-08193: Flashback Table operation is not allowed on temporary tables
Cause: An attempt was made to perform Flashback Table operation on a temporary
table. This is not permitted.
Action: Do not perform a Flashback Table operation on temporary tables.
ORA-08194: Flashback Table operation is not allowed on materialized views
Cause: An attempt was made to perform Flashback Table operation on a materialized
view. This is not permitted.
Action: Do not perform a Flashback Table operation on materialized views or
snapshot logs.
ORA-08195: Flashback Table operation is not supported on partitions
Cause: An attempt was made to perform Flashback Table operation on a partition.
Action: Do not perform a Flashback Table operation on partitions.
ORA-08196: Flashback Table operation is not allowed on AQ tables
Cause: An attempt was made to perform Flashback Table operation on AQ tables.
Action: Do not perform a Flashback Table operation on AQ tables.
ORA-08197: Flashback Table operation is not supported on clustered tables
Cause: An attempt was made to perform Flashback Table operation on a clustered
table. This is not permitted.
Action: Do not perform a Flashback Table operation on clustered tables.
ORA-08198: Flashback Table is not supported on object tables, nested tables
Cause: An attempt was made to perform Flashback Table operation on a object table
or a nested table or a table with nested table column. This is not permitted.
Action: Do not perform a Flashback Table operation on such tables.
ORA-08199: Flashback Table operation is not supported on this object
Cause: An attempt was made to perform Flashback Table operation on an object on
which the operation is not supported.
Action: Do not perform a Flashback Table operation on such objects.
ORA-08205: ora_addr: $ORACLE_SID not set in environment
Cause: The environment variable ORACLE_SID is not set.
Action: Set the ORACLE_SID environment variable.
ORA-07500 to ORA-09859 63-21
ORA-08206: ora_addr: cannot translate address file name

Cause: Cannot translate $ORACLE_HOME/dbs/sgadef$ORACLE_SID.dbf.
Action: Ensure that ORACLE_HOME and ORACLE_SID are properly set.
ORA-08207: ora_addr: cannot open address file
Cause: The address file could not be opened.
Action: Check that ORACLE is up. Check that the file $(ORACLE_HOME)/dbs/
sgadef$(ORACLE_SID).dbf exists and has correct permissions.
ORA-08208: ora_addr: cannot read from address file
Cause: The address file could not be read.
Action: Check that the file $(ORACLE_HOME)/dbs/sgadef$(ORACLE_SID).dbf
exists and contains a single line of text.
ORA-08209: scngrs: SCN not yet initialized
Cause: The System Commit Number has not yet been initialized.
ORA-08210: Requested I/O error
Cause: Oracle requested that an I/O error be returned for this operation.
Action: This should not occur in normal Oracle operation. Contact support.
ORA-08230: smscre: failed to allocate SGA
Cause: The n_core system call failed, maybe due to insufficient memory.
Action: Specify a smaller number of buffers. Check INIT.ORA parameters.
ORA-08231: smscre: unable to attach to SGA
Cause: The process cannot attach to the SGA. This can happen if either the listener
can't attach, or the process cannot communicate with the listener.
Action: Verify that the instance is up and running. Contact your customer support
representative.
ORA-08232: smsdes: cannot detach from SGA
Cause: Probably, the listener process has died.
ORA-08233: smsdes: cannot unmap SGA
Cause: The n_core system call failed while detaching from the SGA.
Action: Note nCX error returned; contact your customer support representative.
ORA-08234: smsget: cannot get instance listener address
Cause: The instance listener address cannot be read from the sgadef file.
Action: Verify $(ORACLE_HOME) and $(ORACLE_SID) are set correctly. Additional
information gives error return from ora_addr.
ORA-08235: smsget: listener not on this node
Cause: A process wishing to attach to the SGA is on a different node from its
instance's listener.
Action: Verify $(ORACLE_HOME) and $(ORACLE_SID) are set correctly. Contact
your customer support representative.
ORA-08236: smsget: cannot share subcube with listener

Cause: The n_share call failed, probably because the listener has died.
Action: Check if the listener is running, and contact your customer support
representative.
ORA-08237: smsget: SGA region not yet created
Cause: Attempting to attach to an SGA which has not yet been created.
Action: Verify that the instance is running. Contact your customer support
representative.
ORA-08238: smsfre: cannot detach from SGA
Cause: The n_core system call failed while detaching from the SGA.
Action: Check nCX error, and contact your customer support representative.
ORA-08243: recursive audit operation attempted
Cause: A recursive operation requiring audit was attempted in the middle of an
auditing operation. The most likely reason is space management operations needed to
free up space in the audit tablespace.
Action: Check space in the tablespace for SYS.AUD$ and correct the problem.
ORA-08260: ora_addr: cannot open nameserver
Cause: A process could not connect to the nameserver.
Action: Make sure the nameserver is up and running. Additional information gives
nameserver's returned status.
ORA-08261: ora_addr: cannot find name in nameserver
Cause: The listener nameserver entry for an instance could not be found.
ORA-08263: ora_addr: cannot free listener address
Cause: The listener nameserver entry could not be freed
Action: Additional information gives nameserver's returned status. Contact your
ORA-08264: ora_addr: cannot close nameserver
Cause: The connection to the nameserver could not be closed.
ORA-08265: create_ora_addr: cannot open nameserver
Cause: A process could not connect to the nameserver.
ORA-08266: create_ora_addr: cannot register name in nameserver
Cause: The listener's addressing information could not be registered.
ORA-07500 to ORA-09859 63-23
ORA-08267: destroy_ora_addr: cannot close nameserver

ORA-08268: create_ora_addr: cannot close nameserver
ORA-08269: destroy_ora_addr: cannot destroy name
Cause: The listener's addressing information could not be removed.
ORA-08270: sksachk: Illegal archival control string
Cause: Archive files cannot be created with the given archival control string.
Action: Check that the volume exists
ORA-08271: sksabln: Buffer size not large enough for archive control string
Cause: The given archival control string expands into too many characters.
Action: Reduce archive control string length.
ORA-08274: Out of memory for environment variable
Cause: There is insufficient memory to return the requested value
Action: Reduce memory usage and retry.
ORA-08275: Environment variable unset
Cause: The requested environment variable is not set
Action: Ensure that the variable name requested is correct.
ORA-08276: No room in nameserver for pid
Cause: There is no room to record the pid for a background process
Action: Shutdown abort and restart the database.
ORA-08277: Cannot set environment variable
Cause: There is insufficient memory to expand the environment.
Action: Reduce memory usage and retry.
ORA-08278: Cannot get CPU statistics
Cause: Could not retrieve CPU times because n_stat failed.
ORA-08308: sllfop: Cannot open file
Cause: Oracle could not open a file.
Action: Check the Unix errno returned as additional information.
ORA-08309: sllfop: Cannot fstat file
Cause: Oracle could not obtain information about an open file.
ORA-08310: sllfop: Bad value for recsize

Cause: An illegal value for the record size was specified.
Action: Specify a value for the recsize option that is greater than 0.
ORA-08311: sllfop: bad value for maxrecsize
Cause: An illegal value for the maximum record size was specified.
Action: Specify a value for the maxrecsize option that is greater than 0.
ORA-08312: sllfop: unrecognized processing option
Cause: An unrecognized processing option was specified.
Action: Check the Oracle for nCUBE 2 User's Guide for valid options.
ORA-08313: sllfop: could not allocate buffers
Cause: Memory for the load buffers could not be allocated.
Action: Reduce the maximum record size. Eliminate any unnecessary processes on
your current node before running SQL*Loader again.
ORA-08314: sllfcf: Error closing file
Cause: An error occurred trying to close a file.
ORA-08315: sllfrb: Error reading file
Cause: An error occurred trying to read from a file.
ORA-08316: sllfsk: Error seeking in file.
Cause: The lseek system call returned an error.
ORA-08317: sllfsk: Error seeking in file.
Cause: The lseek system call returned an error.
ORA-08318: sllfsk: Error reading file
ORA-08319: sllfsk: Error reading file
ORA-08320: scnget: Call to scnget before scnset or scnfnd.
Cause: An internal error
ORA-08321: scnmin: NOT IMPLEMENTED YET
Cause: An internal error
ORA-07500 to ORA-09859 63-25
ORA-08322: scnmin: open/convert of bias lock failed

Cause: A call to the lkmgr failed to open and convert the bias lock
Action: Check to make sure the lkmgr is up.
ORA-08323: scnmin: close of bias lock failed
Cause: A call to the lkmgr failed to close the bias lock
Action: Check to make sure the lkmgr is up.
ORA-08330: Printing not supported
Cause: An attempt was made to automatically spool a file to the printer
Action: None
ORA-08331: Wait operation timed out
Cause: Oracle timed out waiting for an event
Action: Contact your Oracle support representative
ORA-08332: rollback segment #string specified not available
Cause: (same as 1545)
Action: (same as 1545). Also, make sure you have created enough rollback segments
for the number of instances you are trying to start.
ORA-08340: This command not allowed on nCUBE, only one thread is ever used.
Cause: An illegal command was executed for the nCUBE platform.
Action: There is no need to issue this command.
ORA-08341: On nCUBE, this command can only be executed from instance 1.
Cause: A command that can only be issued on instance 1 was issued elsewhere.
Action: Log on to instance 1 and repeat the command.
ORA-08342: sropen: failed to open a redo server connection
Cause: An error occurred trying to connect to the redo server.
Action: The OS specific error message should tell you what to do.
ORA-08343: srclose: failed to close a redo server connection
Cause: An error occurred trying to close the redo server connection.
ORA-08344: srapp: failed to send redo data to the redo server
Cause: An error occurred trying to send redo to the redo server.
ORA-08401: invalid compiler name: string
Cause: An invalid compiler name compname was passed to a UTL_PG conversion
routine.
Action: Correct the compiler name parameter in the PL/SQL code that called the
conversion routine.
ORA-08412: error encountered in WMSGBSIZ, size for WMSGBLK is not big

enough for warning message
Cause: The WMSGBSIZ is the maximun size for warning message block, it is
recommanded to be 1024 bytes to 8 kbytes.
Action: Defined WMSGBLK of size between 1k to 8k bytes and update the
WMSGBSIZ to the sizeof(WMSGBLK).
ORA-08413: invalid compiler type in FORMAT parameter at string
Cause: An invalid compiler type is defined in format control block. The format
control block is invalid.
Action: Check to be sure that the format parameter was built by
MAKE_RAW_TO_NUMBER_FORMAT or MAKE_NUMBER_TO_RAW_FORMAT,
and that it was not accidentally overwritten or modified by the PL/SQL procedure.
ORA-08414: error encountered in string
Cause: The function routine returned an error. Where routine may be:
RAW_TO_NUMER NUMBER_TO_RAW RAW_TO_NUMBER_FORMAT
NUMBER_TO_RAW_FORMAT MAKE_NUMBER_TO_RAW_FORMAT
MAKE_RAW_TO_NUMBER_FORMAT
Action: This message will be preceded by messages providing details about the error.
Check those messages to determine what action to take.
ORA-08429: raw data has invalid digit in display type data
Cause: The input raw buffer passed to a UTL_PG RAW_TO_NUMBER conversion
routine contained invalid data. The picture mask parameter specified a digit, but the
corresponding input from the raw data did not contain a valid digit.
Action: Either the input data is incorrect, or the picture mask is incorrect. Correct the
appropriate item.
ORA-08430: raw data missing leading sign
routine had no leading sign, but the mask options parameter specified a leading sign.
Action: Correct the input raw data or the mask options so that they match.
ORA-08431: raw data missing zero as defined in picture
Cause: The picture mask parameter passed to a UTL_PG RAW_TO_NUMBER
conversion routine contained a zero, but the corresponding input from the raw data
was not a zero.
appropriate item.
ORA-08432: raw data has invalid floating point data
Cause: The input raw data passed to a UTL_PG RAW_TO_NUMBER conversion
routine contained invalid floating point data.
Action: Correct the input raw data.
ORA-08433: invalid picture type in convert raw to number
Cause: The picture mask parameter passed to a UTL_PG RAW_TO_NUMBER
conversion routine contained non-numeric characters, but the conversion was to a
numeric data type.
Action: Correct the picture mask parameter.
ORA-07500 to ORA-09859 63-27
ORA-08434: raw data has invalid trailing sign

routine had no trailing sign, but the mask options parameter specified a trailing sign.
ORA-08435: PICTURE MASK missing the leading sign when SIGN IS LEADING
specified
Cause: The input MASK passed to a UTL_PG RAW_TO_NUMBER conversion
routine had no leading sign, but the mask options parameter specified a leading sign.
ORA-08436: raw data has invalid sign digit
routine had an invalid sign digit in the position where the picture mask specified a
sign.
Action: Correct the input raw data or the picture mask so that they match.
ORA-08437: invalid picture type in picture mask
Cause: The picture mask parameter passed to a UTL_PG NUMBER_TO_RAW
conversion routine contained non-numeric characters, but the conversion was to a
numeric data type.
ORA-08440: raw buffer is too short to hold converted data
Cause: The output raw buffer passed to a UTL_PG NUMBER_TO_RAW conversion
routine was not large enough to contain the results of the conversion based on the
picture mask.
Action: Increase the raw buffer size to the size necessary to hold the entire result of
the conversion.
ORA-08441: closed parenthesis missing in picture mask
Cause: A closed parenthesis was missing from the picture mask passed to a UTL_PG
conversion routine.
Action: Correct the picture mask.
ORA-08443: syntax error in BLANK WHEN ZERO clause in mask options
Cause: A syntax error was found in the BLANK WHEN ZERO clause in the mask
options parameter passed to a UTL_PG conversion routine. Valid specifications are:
BLANK ZERO BLANK ZEROS BLANK ZEROES BLANK WHEN ZERO BLANK
WHEN ZEROS BLANK WHEN ZEROES
Action: Correct the mask options parameter.
ORA-08444: syntax error in JUSTIFIED clause in mask options
Cause: A syntax error was found in the JUSTIFIED clause in the mask options
parameter passed to a UTL_PG conversion routine. Valid specifications are: JUST
JUST RIGHT JUSTIFIED JUSTIFIED RIGHT
ORA-08445: syntax error in SIGN clause in mask options
Cause: A syntax error was found in the SIGN clause in the mask options parameter
passed to a UTL_PG conversion routine. Valid specifications are: SIGN LEADING
SIGN LEADING SEPARATE SIGN LEADING SEPARATE CHARACTER SIGN
TRAILING SIGN TRAILING SEPARATE SIGN TRAILING SEPARATE

CHARACTER SIGN IS LEADING SIGN IS LEADING SEPARATE SIGN IS
LEADING SEPARATE CHARACTER SIGN IS TRAILING SIGN IS TRAILING
SEPARATE SIGN IS TRAILING SEPARATE CHARACTER
ORA-08446: syntax error in SYNCHRONIZED clause in mask options
Cause: A syntax error was found in the SYNCHRONIZED clause in the mask options
parameter passed to a UTL_PG conversion routine. Valid specifications are: SYNC
SYNC LEFT SYNC RIGHT SYNCHRONIZED SYNCHRONIZED LEFT
SYNCHRONIZED RIGHT
ORA-08447: syntax error in USAGE clause in mask options
Cause: A syntax error was found in the USAGE clause in the mask options parameter
passed to a UTL_PG conversion routine. Valid specifications are: USAGE DISPLAY
USAGE COMP USAGE COMP-3 USAGE COMP-4 USAGE COMPUTATIONAL
USAGE COMPUTATIONAL-3 USAGE COMPUTATIONAL-4 USAGE IS DISPLAY
USAGE IS COMP USAGE IS COMP-3 USAGE IS COMP-4 USAGE IS
COMPUTATIONAL USAGE IS COMPUTATIONAL-3 USAGE IS
COMPUTATIONAL-4
ORA-08448: syntax error in DECIMAL-POINT environment clause
Cause: A syntax error was found in the DECIMAL-POINT environment clause
parameter passed to a UTL_PG conversion routine. Valid specifications are:
DECIMAL-POINT IS COMMA
Action: Correct the environment clause parameter.
ORA-08449: invalid numeric symbol found in picture mask
Cause: An invalid numeric symbol was found in the picture mask parameter passed
to a UTL_PG conversion routine.
ORA-08450: invalid specification of CR in picture mask
Cause: The CR suffix was incorrectly specified in the picture mask parameter passed
to a UTL_PG conversion routine. The CR suffix can only appear at the end of a picture
mask.
ORA-08451: invalid specification of DB in picture mask
Cause: The DB suffix was incorrectly specified in the picture mask parameter passed
to a UTL_PG conversion routine. The DB suffix can only appear at the end of a
picture mask.
ORA-08452: specification of E in picture mask is unsupported
Cause: The floating point exponent symbol 'E' was specified in the picture mask
parameter passed to a UTL_PG conversion routine. The floating point data type is
currently not supported by the UTL_PG conversion routines.
Action: Correct the picture mask parameter, and the data, if necessary.
ORA-07500 to ORA-09859 63-29
ORA-08453: more than one V symbol specified in picture mask

Cause: The picture mask passed to a UTL_PG conversion routine contained more
than one decimal point indicator ('V'). Only one decimal point indicator is allowed in
the picture mask.
ORA-08454: more than one S symbol specified in picture mask
Cause: The picture mask passed to a UTL_PG conversion routine contained more
than one operational sign indicator ('S'). Only one operational sign indicator is
allowed in the picture mask.
ORA-08455: syntax error in CURRENCY SIGN environment clause
Cause: A syntax error was found in the CURRENCY SIGN environment clause
parameter passed to a UTL_PG conversion routine. Valid specifications are:
CURRENCY SIGN IS x where x is a valid currency sign
Action: Correct the environment clause parameter.
ORA-08456: no sign in picture mask but SIGN clause in mask options
Cause: The picture mask parameter passed to a UTL_PG conversion routine
contained no sign symbol ('S', '+', or '-'), but the mask options parameter contained a
SIGN clause. A sign symbol is required in the picture mask parameter when the mask
options parameter contains a SIGN clause.
Action: Correct the picture mask parameter or the mask options parameter.
ORA-08457: syntax error in SEPARATE CHARACTER option of SIGN clause
Cause: A syntax error was found in the SEPARATE CHARACTER option of the SIGN
clause in the mask options parameter passed to a UTL_PG conversion routine. Valid
specifications are: SEPARATE SEPARATE CHARACTER
ORA-08458: invalid format parameter
Cause: The format parameter passed to a UTL_PG conversion routine was invalid.
The format parameter should have been built by a prior call to either
MAKE_RAW_TO_NUMBER_FORMAT or MAKE_NUMBER_TO_RAW_FORMAT.
ORA-08459: invalid format parameter length
Cause: The format parameter passed to a UTL_PG conversion routine was not the
correct length. Format parameters must be 2048 bytes in length.
ORA-08460: invalid environment clause in environment parameter
Cause: The environment parameter passed to a UTL_PG conversion routine
contained an unsupported or invalid environment clause. Only the CURRENCY
SIGN and the DECIMAL-POINT IS COMMA environment clauses are supported.
Action: Correct the environment parameter.
ORA-08462: raw buffer contains invalid decimal data

routine contains invalid decimal data.
Action: Correct the input data.
ORA-08463: overflow converting decimal number to Oracle number
Cause: The output variable passed to a UTL_PG RAW_TO_NUMBER was not large
enough to hold the Oracle number resulting from the input decimal number.
Action: Be sure that the input decimal number is valid, and besure that the output
variable is large enough to hold the Oracle number value.
ORA-08464: input raw decimal data contains more than 42 digits
routine contained more than 42 digits. This exceeds the maximum size of an Oracle
number.
Action: Correct the raw input buffer.
ORA-08465: input mask contains more than 32 characters
Cause: The input mask passed to UTL_PG numeric conversion routine contained
more the 32 characters.
Action: Correct the mask input buffer.
ORA-08466: raw buffer length string is too short for string
routine was less than %s bytes long, but the picture mask parameter specified that %s
bytes of input data were to be converted.
appropriate item.
ORA-08467: error converting Oracle number to string
Cause: An error occurred when converting an Oracle number to a COBOL type of:
DISPLAY COMP-3 or character variable. The Oracle number was not in the correct
format.
Action: Correct the call to the conversion routine. The input must be a valid Oracle
number variable.
ORA-08468: mask option string is not supported
Cause: The mask option clause was passed to a UTL_PG conversion routine, but is not
supported by UTL_PG. The clause can be: USAGE IS POINTER USAGE IS INDEX
USAGE IS COMP-1 USAGE IS COMP-2 POINTER
Action: Remove the clause from the mask options parameter in the PL/SQL call to
UTL_PG.
ORA-08469: must use the SIGN IS SEPARATE clause in mask options
Cause: A signed numeric entry with DISPLAY usage was converted using a nondefaulted character set and its PICTURE character-string contains an S. In these
circumstances, a SIGN IS SEPARATE clause must be specified in the mask options.
Action: Either specify a valid SIGN IS SEPARATE clause in the mask options, use the
defaulted character set, or don't specify an S in the PICTURE character-string.
ORA-07500 to ORA-09859 63-31
ORA-08498: Warning: picture mask 'string' overrides picture mask option 'USAGE
IS string' to 'USAGE IS DISPLAY'
Cause: Picture mask USAGE option was overridden by the picture mask.
Action: This is an informational message only. The message may be eliminated by
changing the USAGE option to match the picture mask.
ORA-08499: Warning: picture mask options 'string' ignored by UTL_PG
Cause: Picture mask options such as OCCUR, SYNC and others are not processed by
the UTL_PG numeric conversion routines.
Action: This is an informational message only. The message may be eliminated by
removing the unnecessary picture mask options from the parameter list passed to the
UTL_PG routine.
ORA-09200: sfccf: error creating file
Cause: Could be out of disk space
Action: See OSD error accompanying this message
ORA-09201: sfcopy: error copying file
Cause: Block sizes may not match
ORA-09202: sfifi: error identifying file
Cause: db_block_size specified in init.ora could be incorrect
ORA-09203: sfofi: error opening file
Cause: File attributes may have changed
ORA-09204: sfotf: error opening temporary file
Cause: Incorrect path may have been specified for the file
ORA-09205: sfqio: error reading or writing to disk
Cause: File may have been truncated or corrupted
ORA-09206: sfrfb: error reading from file
ORA-09207: sfsrd: error reading from file
ORA-09208: sftcls: error closing file
Cause: File may have been corrupted
ORA-09209: sftget: error reading from file

ORA-09210: sftopn: error opening file
Cause: Incorrect path may have been specified for the file
ORA-09211: sfwfb: error writing to file
ORA-09212: sfwfbmt: error writing to file
ORA-09213: slgfn: error fabricating file name
Cause: Filename may be too long
ORA-09214: sfdone: I/O error detected
ORA-09215: sfqio: error detected in IOCompletionRoutine
ORA-09216: sdnfy: bad value 'string' for parameter string
Cause: The directory specified as the value for the stated parameter could not be
used.
Action: Make sure the directory you have specified is a valid directory/file
specification.
ORA-09217: sfsfs: failed to resize file
Cause: Could be out of disk space
ORA-09218: sfrfs: failed to refresh file size
Cause: File may be corrupted or truncated
ORA-09240: smpalo: error allocating PGA memory
Cause: Could be out of memory
ORA-09241: smsalo: error allocating SGA memory
ORA-09242: smscre: error creating SGA
ORA-07500 to ORA-09859 63-33
ORA-09243: smsget: error attaching to SGA

Cause: SGA may not have been created (database not started)
ORA-09244: smprset: error setting memory protections
ORA-09245: smcstk: error switching stacks
ORA-09246: sfsmap: unable to map SGA
ORA-09247: smsdes: error destroying the SGA
ORA-09260: sigpidu: error obtaining process id
Cause: May be out of resources
ORA-09261: spdcr: error creating detached (background) process
Cause: Could be out of resources
ORA-09262: spdde: error terminating detached (background) process
ORA-09263: spini: error initializing process
ORA-09264: sptpa: error flagging process
ORA-09265: spwat: error temporarily suspending process
ORA-09266: spawn: error starting an Oracle process
Cause: Could be out memory
ORA-09270: szalloc: error allocating memory for security
ORA-09271: szlon: error verifying user name
Cause: Username may be too long
ORA-09272: remote os logon is not allowed
Cause: Remote os login attempted when not allowed.
ORA-09273: szrfc: error verifying role name

Cause: An OS error was returned when verifying the role name.
ORA-09274: szrfc: insufficient role name buffer space
Cause: An OS role name was too long.
ORA-09275: CONNECT INTERNAL is not a valid DBA connection
Cause: CONNECT INTERNAL is no longer supported for DBA connections.
Action: Please try to connect AS SYSDBA or AS SYSOPER.
ORA-09276: All bequeath database links must be loopback database links
Cause: A non-loopback bequeath connect string was supplied for a database link.
Action: Please use a connect string with a different transport protocol, or specify a
loopback connect string (one that points to the instance for the current session) using
"(PROGRAM=<this instance's ORACLE_HOME>/bin/oracle)" and, optionally,
"(ENVS=''ORACLE_SID=<this instance's ORACLE_SID>'')".
ORA-09280: sllfcf: error closing file
Cause: File may be corrupted
ORA-09281: sllfop: error opening file
Cause: Possibly incorrect path specified to the file
ORA-09282: sllfrb: error reading records
Cause: File could be corrupted
ORA-09283: sllfsk: error skipping records
Cause: File could be corrupted
ORA-09284: sllfop: cannot allocate read buffer
Cause: malloc() system call returned an error. The system might have run out of heap
space
Action: Check additional information for the OS error.
ORA-09285: sllfop: unrecognizable processing option, incorrect format
Cause: Processing option passed is of incorrect format
Action: Consult your IUG for permissible formats
ORA-09290: sksaalo: error allocating memory for archival
ORA-09291: sksachk: invalid device specified for archive destination
Cause: Unable to access directory
Action: Specify a valid device in ARCHIVE control string
ORA-07500 to ORA-09859 63-35
ORA-09292: sksabln: unable to build archive file name

Cause: Bad directory or format specified
Action: Specify a valid directory in 'log_archive_format' and a valid format string in
'log_archive_format' in init.ora
ORA-09293: sksasmo: unable to send message to console
Cause: An error was returned while attempting to send a message to the console
operator
ORA-09300: osncon: unable to connect, DPMI not available
Cause: Unable to detect the presence of DPMI
Action: Restart Windows and retry
ORA-09301: osncon: local kernel only supported in standard mode
Cause: An attempt was made to connect to S: while in enhanced mode
Action: Restart Windows in standard mode
ORA-09310: sclgt: error freeing latch
ORA-09311: slsleep: error temporarily suspending process
ORA-09312: slspool: error spooling file to printer
ORA-09313: slsprom: error prompting user
ORA-09314: sltln: error translating logical name
Cause: Internal buffer may have overflowed
ORA-09315: sql2tt: two-task error translating ORACLE_EXECUTABLE
ORA-09316: szrpc: unable to verify password for role
Cause: OS roles may not be supported for this platform
ORA-09317: szprv: insufficient privileges
Cause: The password specified is invalid
ORA-09318: slkhst: unable to host out to operating system

Cause: There might not be enough memory for the command or hosting out may not
be supported on this platform
ORA-09319: slgtd: unable to obtain the current date and time
Cause: The system time might be set incorrectly
ORA-09320: szrfc: unable to obtain the list of valid OS roles
Cause: OS roles may not be supported on this platform
ORA-09321: slzdtb: unable to convert zoned decimal to binary
ORA-09322: slpdtb: unable to convert packed decimal to binary
ORA-09330: Session terminated internally by Oracle or by an Oracle DBA
Cause: A client workstation that is abnormally disconnected would cause Oracle to
terminate that session after about a minute. This message also appears in the trace file
if a shutdown abort is performed.
Action: n/a
ORA-09340: Specified ORACLE_SID is either invalid or too long
Cause: ORACLE_SID must be at the most 4 alphanumeric characters.
Action: n/a
ORA-09341: scumnt: unable to mount database
Cause: Another instance is currently mounting the database
Action: n/a
ORA-09342: Detached process terminated by Oracle during shutdown abort
Cause: The user performed a shutdown abort.
Action: n/a
ORA-09344: spsig: error signalling thread
Cause: This function may not be implemented.
Action: n/a
ORA-09350: Windows 32-bit Two-Task driver unable to allocate context area
Cause: See OSD error accompanying this message
Action: n/a
ORA-09351: Windows 32-bit Two-Task driver unable to allocate shared memory
Action: n/a
ORA-07500 to ORA-09859 63-37
ORA-09352: Windows 32-bit Two-Task driver unable to spawn new ORACLE task
Action: n/a
ORA-09353: Windows 32-bit Two-Task driver unable to open event semaphore
Action: n/a
ORA-09354: Windows 32-bit Two-Task driver: ORACLE task unexpectedly died
Action: n/a
ORA-09360: Windows 3.1 Two-Task driver unable to allocate context area
Action: n/a
ORA-09361: Windows 3.1 Two-Task driver unable to lock context area
Action: n/a
ORA-09362: Windows 3.1 Two-Task driver unable to deallocate context area
Action: n/a
ORA-09363: Windows 3.1 Two-Task driver invalid context area
Action: n/a
ORA-09364: Windows 3.1 Two-Task driver unable to create hidden window
Action: n/a
ORA-09365: Windows 3.1 Two-Task driver unable to destroy hidden window
Action: n/a
ORA-09366: Windows 3.1 Two-Task driver unable to allocate shared memory
Action: n/a
ORA-09367: Windows 3.1 Two-Task driver unable to deallocate shared memory
Action: n/a
ORA-09368: Windows 3.1 Two-Task driver unable to spawn ORACLE
Action: n/a
ORA-09369: Windows 3.1 Two-Task driver bad instance handle
Action: n/a
ORA-09370: Windows 3.1 Two-Task driver ORACLE task timed out
Action: n/a
ORA-09700: sclin: maximum number of latches exceeded
Cause: ORACLE wants to use more latches then available.
Action: increase INIT.ORA parameter latch_pages or decrease the amount of shared
memory you are using.
ORA-09701: scnfy: maximum number of processes exceeded
Cause: PROCESSES INIT.ORA parameter exceeded.
Action: Decrease the PROCESSES parameter and restart.
ORA-09702: sem_acquire: cannot acquire latch semaphore
Cause: The semaphore used for accessing latches could not be seized
information on reproducing the error.
ORA-09703: sem_release: cannot release latch semaphore
Cause: The semaphore used for accessing latches could not be released
ORA-09704: sstascre: ftok error in creating test and set pages.
Cause: the ftok() library call failed in sstastcre().
Action: Verify that tasdef@.dbf file exists. If it does then this is a possible system
failure. Perhaps System V compatibility is not enabled.
ORA-09705: spcre: cannot initialize latch semaphore
Cause: The semaphore used for accessing latches could not be initialized
ORA-09706: slsget: get_process_stats error.
Cause: get_process_stats system call returned an error. Possible OS error.
Action: Check additional information returned. Look for information in OS reference.
ORA-09708: soacon: failed to bind socket to port.
Cause: The bind system call failed on the socket.
Action: Check additional information for OS error. Try connecting again.
ORA-09709: soacon: failed to accept a connection.
Cause: The accept system call failed on the socket.
Action: Check additional information for OS error. Try connecting again.
ORA-09710: soarcv: buffer overflow.
Cause: The internal buffer is not big enough to hold the message read.
Action: Internal error. Contact customer support representative.
ORA-07500 to ORA-09859 63-39
ORA-09711: orasrv: archmon already connected.

Cause: An existing connection has already been made from archmon to orasrv.
Action: Stop trying to connect.
ORA-09712: orasrv: log archiver already connected.
Cause: An existing connection has already been made from log archiver to orasrv.
Action: Stop trying to connect.
ORA-09714: Two Task interface: cannot obtain puname
Cause: The TXIPC driver cannot obtain the name of the PU. (Possible OS error)
Action: Check if the PUs are named (consistend).
ORA-09715: orasrv: cannot obtain puname
Cause: Orasrv cannot obtain the name of the PU. (Possible OS error)
Action: Check if the PUs are named (consistend).
ORA-09716: kslcll: Unable to fix in-flux lamport latch.
Cause: One Oracle process died while still holding a lamport latch.
Action: Exit (kill) all Oracle user processes. Shutdown (abort) and restart Oracle
RDBMS kernel.
ORA-09717: osnsui: maximum number of user interrupt handlers exceeded.
Cause: The internal limit on the number of user interrupt handlers has been exceeded.
Action: Reduce the number of simulataneous logons or reduce the number of user
interrupt handlers.
ORA-09718: osnsui: cannot set up user interrupt handler.
Cause: Malloc() failed to allocate space to hold user interrupt handler.
Action: Possible memory resource shortage.
ORA-09719: osncui: invalid handle.
Cause: The handle passed to osncui is out of the valid range.
Action: Use a valid handle.
ORA-09740: slsget: cannot get virtual memory region statistics.
Cause: The vm_region system call failed to get virual memory region statistics.
Action: Check return code in sercerrno. Possible operating system failure.
ORA-09741: spwat: error waiting for a post.
Cause: Msg_receive system call returned an error. Internal error.
Action: Check return code in sercerrno. Port name is returned in sercose[0].
ORA-09742: sppst: error during a post.
Cause: Msg_send system call returned an error. Internal error.
Action: Check return code in sercerrno. Port name is returned in sercose[0].
ORA-09743: smscre: could not attach shared memory.
Cause: The mmap or write system call returned an error. Internal error.
ORA-09744: smsget: mmap returned an error.

Cause: The mmap system call returned an error. Internal error.
ORA-09745: smscre: vm_allocate error, unable to create shared memory.
Cause: Error in system call vm_allocate. Failed to create SGA as a single shared
memory segment.
Action: Check result code returned in sercerrno. Verify that the SGA attach address is
valid.
ORA-09746: smscre: shared memory attach address incorrect.
Cause: The vm_allocate system call attached the SGA at an incorrect location.
Action: Verify that the SGA attach address is valid.
ORA-09747: pw_detachPorts: server call pws_detach failed.
Cause: The call pws_detach to (Oracle helper) failed.
Action: Make sure the server is still active. Check the error code returned in sercerrno,
and look for error messages in the server log file.
ORA-09748: pws_look_up: fork failed
Cause: The pws_look_up call could not fork the (Oracle helper) process.
ORA-09749: pws_look_up: port lookup failure
Cause: The pws_look_up could not find a port to (Oracle helper).
Action: Make sure the (Oracle helper) server has been started correctly by
pws_look_up, and that the network name server is still running.
ORA-09750: pw_attachPorts: port_rename failed.
Cause: The port_rename system call failed; possible internal error.
Action: Check return code in sercerrno, report to Oracle customer support.
ORA-09751: pw_attachPorts: server call pws_attach failed.
Cause: The call pws_attach to (Oracle helper) failed.
ORA-09752: pw_attachPorts: port_allocate failed.
Cause: The port_allocate system call failed; possible resource exhaustion.
Action: Check return code in sercerrno, report to Oracle customer support.
ORA-09753: spwat: invalid process number.
Action: Internal error. Additional information indicates the invalid process id.
ORA-09754: sppst: invalid process number passed to sppst.
Action: Internal error. Contact Oracle support.
ORA-07500 to ORA-09859 63-41
ORA-09755: osngpn: port allocation failure.

Cause: The port_allocate system call failed.
Action: Possible system resource shortage; check the error code in sercerrno.
ORA-09756: osnpns: no port in the name server.
Cause: osnpns could not find the given named port in the name server.
Action: Check the error code in sercerrno. Make sure the shadow process and
network name server are still running.
ORA-09757: osnipn: port allocation failure.
Cause: The port_allocate system call failed.
Action: Possible system resource shortage; check the error code in sercerrno.
ORA-09758: osnipn: could not check port in name server.
Cause: The netname_check_in call failed.
Action: Check the error code in sercerrno. Make sure the network name server is
running.
ORA-09759: osnsbt: bad message received.
Cause: The msg_receive system call failed, or received a bad message.
Action: Internal error. Report the error code returned in sercerrno.
ORA-09760: osnpui: cannot send break message
process break thread.
ORA-09761: pw_destroyPorts: server call pws_stop_instance failed.
Cause: The call pws_stop_instance to (Oracle helper) failed.
ORA-09762: sNeXT_instanceName: translation error.
Cause: A failure was detected while translating the value of ORACLE_SID.
Action: Make sure ORACLE_SID is defined, and that it is of legal length.
ORA-09763: osnmpx: send/receive error exchanging Mach ports.
Cause: The Mach driver failed to exchange port information with the other side of the
connection. Either msg_send (sercose[0] == 1) or msg_receive (sercose[0] == 2) failed.
Action: Check return code in sercerrno. Make sure both sides of the connection are
still running.
ORA-09764: osnmop: access error on oracle executable
Cause: The Mach driver could not access the oracle executable.
ORA-09765: osnmop: fork failed
Cause: The Mach driver could not fork the oracle shadow process.
ORA-09766: osnmop: buffer allocation failure.
Cause: The Mach driver failed to allocate enough vm space for its I/O buffers.
Action: Decrease the value of buffer_size parameter in the Two-Task driver
hoststring.
ORA-09767: osnmfs: bad return code from msg_send.
Cause: The msg_send system call failed while flushing the Mach driver's send buffer.
Action: Internal error. Contact your customer support representative.
ORA-09768: osnmgetmsg: could not read a message
Cause: The msg_receive system call returned a failure code while waiting for a
message in the Mach driver.
ORA-09769: osnmbr: cannot send break message
Cause: The Mach driver could not send a break message to the ORACLE shadow
ORA-09770: pws_look_up: translation failure.
Cause: The pws_look_up routine failed to translate the name of the (Oracle helper)
executable.
Action: Make sure ORACLE_SID and ORACLE_HOME are set and correct.
Additional information gives the translation error code.
ORA-09771: osnmwrtbrkmsg: bad return code from msg_send.
Cause: The msg_send sytem call failed while sending a Mach driver break.
ORA-09772: osnpmetbrkmsg: message from host had incorrect message type
Cause: The Mach driver received a message having an unrecognizable message type.
ORA-09773: osnmgetdatmsg: message from host had incorrect message type
Cause: The Mach driver received a message having an unrecognizable message type.
ORA-09774: osnmui: cannot send break message
Cause: The Mach driver could not send a break message to the ORACLE shadow
ORA-09775: osnmrs: reset protocol error
Cause: The Mach two-task driver could not reset the connection.
ORA-07500 to ORA-09859 63-43
ORA-09776: pws_look_up: access error on (Oracle helper) executable

Cause: The pws_look_up call could not access the (Oracle helper) executable.
Action: Check the permissions on the (Oracle helper) executable and each component
of the ORACLE_HOME/bin path.
ORA-09777: osnpbr: cannot send break message
Cause: The pipe driver could not send a break message to the ORACLE shadow
ORA-09778: snynfyport: failure allocating the notify port.
Cause: The routine failed to allocate or set the task's notify port.
Action: Possible operating system error. Contact Oracle support.
ORA-09779: snyGetPort: failure to allocate a port.
Cause: The port_allocate system call failed; system resources might be exhausted.
ORA-09786: sllfop: open error, unable to open file.
Cause: Open system call returned an error.
ORA-09787: sllfop: unrecognizable processing option, incorrect format.
Cause: Processing option passed is of incorrect format.
Action: Consult your IUG for permissible formats.
ORA-09788: sllfrb: unable to read file.
Cause: Read system call returned an error.
Action: Check errno. Verify file exists.
ORA-09789: sllfsk: unable to read file.
Cause: Read system call returned an error.
Action: Check errno. Verify file exists.
ORA-09790: sllfcf: unable to close file.
Cause: Close system call returned an error.
ORA-09791: slembdf: translation error, unable to translate error file name.
Cause: Additional information indicates error returned from sltln.
ORA-09792: sllfop: cannot allocate read buffer.
Cause: Malloc system call returned an error. The system might have run out of heap
space.
Action: Check additional information for the OS error.
ORA-09793: szguns: length of user name is greater than buffer.
Cause: The length of the name of the user being looked up is longer than size of the
buffer provided by the calling routine.
ORA-09794: szrbuild: length of role name is greater than buffer.

Cause: The length of the name of the role being looked up is longer than size of the
buffer provided by the calling routine.
ORA-09795: szrbuild: malloc of role structure failed.
Cause: The allocation of memory for an internal structure used to hold a role
descriptor failed.
Action: Check the UNIX error number for a possible operating system failure.
ORA-09796: szrbuild: malloc of role name failed.
Cause: The allocation of memory for an internal buffer used to hold the name of a role
failed.
Action: Check the UNIX error number for a possible operating system failure.
ORA-09797: Failed to get O/S MAC privileges.
Cause: The operating system would not allow the retrieval of this process' privileges.
Action: Check the UNIX error number for a possible operating system failure. If there
is no error, contact Oracle Support Services.
ORA-09798: Label comparison failed.
Cause: The comparison of two binary labels failed.
ORA-09799: File label retrieval failed.
Cause: ORACLE was unable to get a label attached to a file.
ORA-09800: Process sensitivity label retrieval failed.
Cause: ORACLE was unable to get the sensitivity label for a process.
ORA-09801: Unable to get user ID from connection
Cause: ORACLE was unable to retrieve the user's ID number from the SQL*Net
connection.
Action: Check the UNIX error number for a possible operating system error. Also
check the "additional information" field for the SQL*Net error. If there is no error,
ORA-09802: Conversion of binary label to string failed.
Cause: ORACLE was unable to convert a binary label to a string.
ORA-09803: Allocation of string buffer failed.
Cause: a buffer used to hold the name of the file for which a label was to be obtained
could not be allocated.
ORA-07500 to ORA-09859 63-45
is no error, contact Oracle Support Services. The number of bytes that ORACLE
attempted to allocate is in the "Additional Information" field.
ORA-09804: Class conversion from binary to ORACLE failed.
Cause: ORACLE was unable to convert a class component from binary format to
ORACLE format.
ORA-09805: conversion of category number to string failed.
Cause: ORACLE was unable to translate a category number to its corresponding
string representation failed.
is no error, contact Oracle Support Services. The category number is contained in the
"Additional information" field.
ORA-09806: Allocation of label string buffer failed.
Cause: a temporary buffer used to hold a label could not be allocated.
is no error, contact Oracle Support Services. The number of bytes that ORACLE
attempted to allocate is in the "Additional Information" field.
ORA-09807: Conversion of label from string to binary failed.
Cause: ORACLE was unable to convert the string representation of a label to binary
format.
Action: Re-enter a valid label.
ORA-09808: Could not obtain user clearance.
Cause: ORACLE was unable to get a user's clearance level.
ORA-09809: Unable to get user's group ID from connection
Cause: ORACLE was unable to retrieve the user's group ID number from the
SQL*Net connection.
ORA-09810: Unable to get process ID from connection
Cause: ORACLE was unable to retrieve the user's process ID number from the
SQL*Net connection.
ORA-09811: Unable to initialize package.
Cause: ORACLE was unable to initialize the library used to obtain security
information.
ORA-09812: Unable to get user clearance from connection

Cause: ORACLE was unable to retrieve the user's operating system session clearance
from the SQL*Net connection.
ORA-09813: Unable to get directory status
Cause: ORACLE was unable to determine if a directory is multilevel.
Action: Check the UNIX error number for a possible operating system error. If there is
no error, contact Oracle Support Services.
ORA-09814: Unable to expand file name
Cause: ORACLE was unable to expand the name of a file that resides in multilevel
directory.
ORA-09815: File name buffer overflow
Cause: The buffer that ORACLE uses to hold the expanded name of a too small.
ORA-09816: Unable to set effective privileges
ORA-09817: Write to audit file failed.
Cause: ORACLE was unable to write an entry to the file used as the audit trail.
ORA-09818: Number is too large
Cause: ORACLE was unable to convert a component string to a number because the
number is larger than the largest possible value for an integer. The additional
information field specifies the maximum.
Action: Correct the string and repeat the conversion.
ORA-09819: Number exceeds maximum legal value
Cause: the number specified for a component was greater than the maximum value
allowed for that component.
Action: Change the component to a value less than the maximum and repeat the
conversion. The maximum component number is contained in the "Additional
information" field.
ORA-09820: Conversion of class string to numeric representation failed.
Cause: ORACLE was unable to convert a class string to a number because all of the
characters in the string were not numeric.
Action: Change the string to be either all numbers or all non-numeric characters and
repeat the conversion.
ORA-09821: Numeric label is not valid
Cause: A label specified in ORACLE numeric format was found not to be valid.
Action: Re-enter a valid label. Consult your system's encodings for valid numeric
component values.
ORA-07500 to ORA-09859 63-47
ORA-09822: Translation of audit file name failed.

Cause: Oracle was unable to translate the value of the AUDIT_FILE_DEST
initialization parameter.
ORA-09823: device name is too long
Cause: The name of a device was too long to fit into an internal buffer. The additional
information field contains the length of the device name.
ORA-09824: Unable to enable allowmacaccess privilege.
Cause: ORACLE was not able to turn on allowmacaccess privilege so that it could do
a label comparison.
Action: Check the UNIX error number. If it indicates that ORACLE does not have the
allowmacaccess privilege, add the allowmacaccess privilege to the potential privilege
set of $ORACLE_HOME/bin/oracle using chpriv (1M). If the executable already has
the allowmacaccess privilege, contact Oracle Support Services.
ORA-09825: Unable to disable allowmacaccess privilege.
Cause: ORACLE was not able to turn off the allowmacaccess privilege after doing a
label comparison.
ORA-09826: SCLIN: cannot initialize atomic latch.
Cause: System call atomic_op() return error.
Action: Check additional information in the trace file.
ORA-09827: SCLGT: atomic latch return unknown error.
Cause: System call atomic_op() return unexpected error.
ORA-09828: SCLFR: atomic latch return error.
Cause: System call atomic_op() return unexpected error.
ORA-09829: pw_createPorts: server call pws_start_instance failed.
Cause: The call pws_start_instance to (Oracle helper) failed; system resources might
be exhausted.
ORA-09830: snyAddPort: failed to perform a remote procedure call.
Cause: The msg_rpc system call returned an error.
ORA-09831: snyStartThread: failed to build the server port set.
Cause: The routine failed to build a port set on which to listen for requests.
Action: Possible operating system failure. Contact Oracle support.
ORA-09832: infoCallback: bad message format.

Cause: The routine received an incorrectly formatted request.
ORA-09833: addCallback: bad message format.
ORA-09834: snyGetPortSet: failed to collect info on a port.
Cause: The port_status system called failed.
ORA-09835: addCallback: callback port is already in a set.
Cause: The port to be added to the callback list is already in a port set.
ORA-09836: addCallback: could not add a port to the callback set.
Cause: The port_set_add system called failed.
ORA-09837: addCallback: could not add allocate a callback link.
Cause: The malloc library call failed to allocate space for a callback link.
ORA-09838: removeCallback: failure removing the callback port.
Cause: The port port_set_remove system call failed.
ORA-09839: removeCallback: callback port is not in the callback set.
Cause: The port to be removed to the callback list is not in the callback port set.
ORA-09840: soacon: Name translation failure.
Cause: sltln() could not translate the named pipe ?/dbs/mon2arch_@.
Action: Make sure that the ORACLE_HOME specified for this ORACLE_SID in
oratab is correct.
ORA-09841: soacon: Name translation failure.
Cause: sltln() could not translate the named pipe ?/dbs/arch2mon_@.
Action: Make sure that the ORACLE_HOME specified for this ORACLE_SID in
oratab is correct.
ORA-09842: soacon: Archmon unable to create named pipe.
Cause: mknod() failed to create named pipe ?/dbs/mon2arch_@.
Action: Your current OS login may lack write permission for the
ORACLE_HOME/dbs directory. Only userids in the dba group of a given instance
can run archmon for that ORACLE_SID. Make sure that the ORACLE_HOME
directory is correct in oratab.
ORA-09843: soacon: Archmon unable to create named pipe.
Cause: mknod() failed to create named pipe ?/dbs/arch2mon_@.
ORA-07500 to ORA-09859 63-49
Action: Your current OS login may lack write permission for the
ORACLE_HOME/dbs directory. Only userids in the dba group of a given instance
can run archmon for that ORACLE_SID. Make sure that the ORACLE_HOME
directory is correct in oratab.
ORA-09844: soacon: Archmon unable to open named pipe.
Cause: open() failed to open named pipe ?/dbs/mon2arch_@.
Action: Only the oracle dba can run archmon. Make sure that your current OS login
has owner or group search permission for the ORACLE_HOME/dbs directory. The
max number of open files may have been exceeded.
ORA-09845: soacon: Archmon unable to open named pipe.
Cause: open() failed to open named pipe ?/dbs/arch2mon_@.
Action: Only the oracle dba can run archmon. Make sure that your current OS login
has owner or group search permission for the ORACLE_HOME/dbs directory. The
max number of open files may have been exceeded.
ORA-09846: soacon: ARCH unable to open named pipe.
Cause: open() failed to open named pipe ?/dbs/mon2arch_@.
Action: Make sure that the OS userid of the currently running database has search
permission for the ORACLE_HOME/dbs directory. The max number of open files
may have been exceeded.
ORA-09847: soacon: ARCH unable to open named pipe.
Cause: open() failed to open named pipe ?/dbs/arch2mon_@.
Action: Make sure that the OS userid of the currently running database has search
permission for the ORACLE_HOME/dbs directory. The max number of open files
may have been exceeded.
ORA-09848: soawrt: Unable to write to named pipe.
ORA-09849: soarcv: Unable to read from named pipe.
ORA-09850: soacon: Archmon unable to lock named pipe.
Cause: fcntl() failed to set write lock on named pipe ?/dbs/arch2mon_@.
Action: Make sure that archmon is not already active on another terminal for this
ORACLE_SID. Only one archmon session is allowed at a time for a given instance.
ORA-09851: soacon: Archmon unable to lock named pipe.
Cause: fcntl() failed to set read lock on named pipe ?/dbs/mon2arch_@.
Action: Make sure that archmon is not already active on another terminal for this
ORACLE_SID. Only one archmon session is allowed at a time for a given instance.
ORA-09853: snyRemovePort: bad return code from request.
Cause: The request to remove a port from the callback set returned a failure code.
ORA-09854: snyPortInfo: bad return code from request.
Cause: The request to collect info on a port in the callback set returned a failure code.
ORA-09855: removeCallback: bad message format.

ORA-09856: smpalo: vm_allocate error while allocating pga.
Cause: The vm_allocate system call returned an error.
Action: Check returned error. Possibly out of system resources.
ORA-09857: smprset: vm_protect error while protecting pga.
Cause: The vm_protect system call returned an error.
ORA-09858: sfngat: the input file name is not in the OMF format
Cause: The function sfngat() received a filename which is not an OMF file name.
ORA-09859: sfngat: the input file name is not in the autobackup OMF format
Cause: The function sfngat() received a filename which is not an autobackup OMF file
name.
ORA-07500 to ORA-09859 63-51
64
ORA-09870 to ORA-12100
ORA-09870: spini: failure initializing maximum number of open files.
Cause: ulimit system call returned an error.
ORA-09871: TASDEF_NAME: translation error while expanding ?/dbs/tasdef@.dbf.
Cause: Failure of sltln(?/tasdef@.dbf) while creating test and set pages.
Action: Check additional return error for more information.
ORA-09872: TASDEF_CREATE: create failure in creating ?/dbs/tasdef@.dbf.
Cause: Create() failed when trying to create the tasdef file.
Action: Verify permissions on $(ORACLE_HOME)/dbs directory.
ORA-09873: TASDEF_OPEN: open error when opening tasdef@.dbf file.
Cause: Unable to open tasdef@.dbf file.
Action: Check errno. Possible permission problem. Verify that tasdef@.dbf file exists.
ORA-09874: TASDEF_READ: read error, unable to read tasdef@.dbf file.
Cause: Read system call returned an error when attempting to read ?/dbs/
tasdef@.dbf.
Action: Check errno returned. Sgadef file may be corrupted or incompatible with
oracle version.
ORA-09875: TASDEF_WRITE: write error when writing ?/dbs/tasdef@.dbf file.
Cause: Write call failed.
Action: Check errno returned. Possibly out of space on device.
ORA-09876: TASDEF_CLOSE: unable to close ?/dbs/tasdef@.dbf file.
Cause: Close system call returned an error.
Action: Check errno returned. Possible operating system failure.
ORA-09877: sstascre: shmget error, unable to get a shared memory segment.
Cause: Error in shmget.
Action: Check errno returned. Verify that enough shared memory is available on the
system.
ORA-09878: sstascre/sstasat: shmat error, unable to attach tas write page
Cause: Error in shmat.
Action: Check errno returned.Verify that enough shared memory is available on the
system.
ORA-09870 to ORA-12100 64-1
ORA-09879: sstascre/sstasat: shmat error, unable to attach tas read page

Cause: Error in shmat.
Action: Check errno returned.Verify that enough shared memory is available on the
system.
ORA-09880: sstasfre/sstasdel: shmdt error, unable to detach tas write page
Cause: Error in shmdt.
ORA-09881: sstasfre/sstasdel: shmdt error, unable to detach tas read page
Cause: Error in shmdt.
ORA-09882: sstasfre/sstasdel: shmctl error, unable to remove tas shm page
Cause: Error in shmctl.
ORA-09883: Two Task interface: oratab file does not exist
Cause: The oratab file does not exist.
Action: Install oracle before you use it or recreate the oratab file.
ORA-09884: Two Task interface: SID doens't match current PU
Cause: You are trying to start oracle on another PU than you configured oracle on or
there is no entry for this SID in oratab file.
Action: Start oracle with this SID on its designated PU (see oratab file). Or install the
new database with SID.
ORA-09885: osnTXtt: cannot create TXIPC channel
Cause: The TXIPC driver failed to create pipes for two-task communications with the
oracle shadow process.
ORA-09886: osnTXtt: translation error while expanding txipc@.trc.
Cause: Failure of sltln(txipc@.trc) while creating debug channel.
ORA-09887: osnTXtt: Failed to create/open debug channel.
ORA-09888: osnTXtt: txipc channel creation failed
Cause: The txipc driver failed to create channels for two-task communications with
the oracle shadow process.
per user or the system file table operating system error code and contact your system
administrator.
ORA-09889: osnTXtt: access error on oracle executable
Cause: The txipc driver could not access the oracle executable.
64-2 Error Messages
ORA-09890: osnTXtt: malloc failed

Cause: The txipx driver failed to allocate enough heap space for its context area
buffers.
ORA-09908: slkmnm: gethostname returned error code.
Cause: The system call gethostname returned an error.
Action: This is most likely an internal error. Make sure gethostname is successful in
other contexts, and if so contact Oracle support.
ORA-09909: Malloc of scratch buffer failed.
Cause: Memory needed for a temporary buffer could not be allocated. The additional
information field contains the number of bytes that ORACLE attempted to allocate.
Action: Check the UNIX error number. It is probable that the system has run out of
memory. If there is no error, contact ORACLE support.
ORA-09910: Unable to find ORACLE password file entry for user.
Cause: No entry exists for the user in the ORACLE password file.
Action: Have the database administrator install a password entry by running
orapasswd.
ORA-09911: Incorrect user password.
Cause: The password entered by the user was incorrect.
Action: Enter the correct password.
ORA-09912: Malloc of name buffer(s) failed.
Cause: ORACLE was unable to allocate memory for one or both of the buffers that are
used to hold the name of DBA and the operator users.
ORA-09913: Malloc of dummy name failed.
Cause: ORACLE was unable to allocate memory for the user name that is to to be
used in the encryption of the user's password.
ORA-09914: Unable to open the ORACLE password file.
Cause: ORACLE could not open the password file for reading.
Action: Check the UNIX error number. If the error number indicates that the file does
not exist, have the database administrator create the file by running orapasswd. If the
error number indicates insufficient permissions, ask the database administrator to
change the permissions. Otherwise, contact ORACLE customer support.
ORA-09915: Password encryption failed.
Cause: ORACLE was unable to encrypt a password.
Action: This is an internal error - contact ORACLE customer support.
ORA-09916: Required password was not specified.
Cause: A user attempted to connect as "internal," but did not specify a password.
Action: Connect as internal again and specify a password.
ORA-09870 to ORA-12100 64-3
ORA-09918: Unable to get user privileges from SQL*Net

Cause: ORACLE was unable to retrieve the user's privilege set from the SQL*Net
connection.
contact ORACLE support.
ORA-09919: Unable to set label of dedicated server
Cause: ORACLE was unable to set the label of the dedicated to server to the required
value.
Action: Check the UNIX error number for a possible operating system error. Also,
check the privileges on the oracle executable. It should have at least "allowmacaccess"
privilege.
ORA-09920: Unable to get sensitivity label from connection
Cause: ORACLE was unable to retrieve the user's sensitivity label from the SQL*Net
connection.
ORA-09921: Unable to get information label from connection
Cause: ORACLE was unable to retrieve the user's information label from the SQL*Net
connection.
ORA-09922: Can't spawn process - background log directory not created properly
Cause: ORACLE was unable to spawn a background process because the directory
that will hold trace files of the background processes was not created properly.
Action: Examine the directory pointed to by the initialization parameter
"background_dump_dest". Make sure that all of the following is true: 1. The directory
exists. 2. The name indeed points to a directory, and is not a file. 3. The directory is
accessible and writable to the ORACLE user.
ORA-09923: Can't spawn process - user log directory not created properly
that holds the trace files of the dedicated server processes was not created properly.
"user_dump_dest". Make sure that all of the following is true: 1. The directory exists.
2. The name indeed points to a directory, and is not a file. 3. The directory is
ORA-09924: Can't spawn process - core dump directory not created properly
that holds the core dumps produced by ORACLE processes in the event of exceptions
was not created properly.
"core_dump_dest". Make sure that all of the following is true: 1. The directory exists.
2. The name indeed points to a directory, and is not a file. 3. The directory is
64-4 Error Messages
ORA-09925: Unable to create audit trail file

Cause: ORACLE was not able to create the file being used to hold audit trail records.
no error, contact ORACLE customer support.
ORA-09926: Unable to set effective privilege set of the server
Cause: A dedicated server was unable to set it's own privilege set.
Action: Check the privileges granted to the ORACLE executable. It must have at least
"allowmacacess" privilege.
ORA-09927: Unable to set label of server
Cause: ORACLE was not able to set the label of a server to a new value.
Action: Check the privileges on $ORACLE_HOME/bin/oracle. Make sure that it has
"allowmacaccess" privilege.
ORA-09928: Unable to restore the label of server
Cause: ORACLE was unable to restore the label of the server to the value that it had
before raising it to database high.
Action: This is an internal error - contact ORACLE support.
ORA-09929: GLB of two labels is invalid
Cause: The result of a greatest lower bound operation on two labels was not valid.
Action: Repeat the operation with two different labels. Consult the system encoding
file for the values of valid labels.
ORA-09930: LUB of two labels is invalid
Cause: The result of a least upper bound operation on two labels was not valid.
Action: Repeat the operation with two different labels. Consult the system encoding
file for the values of valid labels.
ORA-09931: Unable to open ORACLE password file for reading
Cause: An attempt to open a password file for reading failed.
Action: Make sure that the permissions on the file have not been changed so that the
ORACLE user cannot open it.
ORA-09932: Close of ORACLE password file failed.
Cause: An attempt to close a password file failed.
Action: Check the UNIX error number for the specific reason.
ORA-09933: Deletion of old password file failed.
Cause: The removal of the old password file failed.
ORA-09934: Link of current password file to old failed.
Cause: ORACLE was unable to create a link so that the old password file could be
saved.
ORA-09935: Unlink of current password file failed.
Cause: ORACLE was unable to complete the saving of the current password file.
ORA-09870 to ORA-12100 64-5
ORA-09936: Open of ORACLE password file for write failed.

Cause: ORACLE was unable to create a password file.
ORA-09937: Chmod of ORACLE password file failed.
Cause: ORACLE was unable to change a password file to be readonly.
ORA-09938: Save of signal handlers failed.
Cause: ORACLE was unable to save the previous values of selected signal handlers.
Action: This is an internal error. Contact ORACLE support.
ORA-09939: Restoration of signal handlers failed.
Cause: ORACLE was unable to restore the previous values of selected signal
handlers.
Action: This is an internal error. Contact ORACLE support.
ORA-09940: ORACLE password file header is corrupt
Cause: The header of one of the password files was not in the format that ORACLE
expected.
Action: Check the headers of both files. The header should be in the format "FILE
VERSION: N.N.N.N.N EXECUTABLE VERSION: N.N.N.N.N" where N is a number.
Remove the corrupt file(s) and re-run "orapasswd".
ORA-09941: Version of orapasswd or installer is older than file.
Cause: The version of orapasswd or installer that is being run is older than that of the
ORACLE password file. Since the file version is only changed when the format is
changed, this error means that the executable is using a different format than that
with which the file was created.
Action: Run a version of the installer or orapasswd whose version is the same or later
than that of the file.
ORA-09942: Write of ORACLE password file header failed.
Cause: The attempt to write out the header of the ORACLE password file failed.
Action: Check the operating system error number. It is possible that the file system
became full.
ORA-09943: Allocation of memory for password list component failed.
Cause: When it is building a list of password file entries, ORACLE allocates memory
for various components. One of the allocations failed.
Action: Check the operating system error number. The system has probably run out
of memory.
ORA-09944: Password entry is corrupt.
Cause: An entry in an ORACLE password file was not in the format that ORACLE
expected.
Action: Removed the corrupt file(s) and re-run "orapasswd."
ORA-09945: Unable to initialize the audit trail file
Cause: ORACLE unable to write header information to the file being used as the audit
trail.
64-6 Error Messages
no error, contact ORACLE customer support.
ORA-09946: File name too long for buffer
Cause: The buffer that was to be used to hold a file name was determined to be too
short for the generated name. This will happen if the translated name for either a
trace file or an audit file is longer than the maximum allowed, which on many ports is
256 characters.
Action: Use a shorter file name.
ORA-09947: Unable to allocate connection attributes structure
Cause: ORACLE was not able to allocate the memory needed to hold the attributes of
the SQL*Net connection. The "Additional Information" field holds the number of
bytes that ORACLE attempted to allocate.
memory. If there is no error, contact ORACLE customer support.
ORA-09948: Process information label retrieval failed.
Cause: ORACLE was unable to get the information label for a process.
is no error, contact ORACLE support.
ORA-09949: Unable to get client operating system privileges
Cause: ORACLE was unable to get the operating system privileges for the client
process.
ORA-09950: Unable to get server operating system privileges
Cause: ORACLE was unable to get its privileges from the operating system.
Action: This is an error that should never happen. Contact ORACLE customer
support.
ORA-09951: Unable to create file
Cause: ORACLE was unable to create a file.
ORA-09952: scgcmn: lk_open_convert unexpected return: open failed
Cause: The distributed lock manager returned an unexpected value
Action: Check for system error message and refer to the distributed lock manager
documentation or contact your customer support representative.
ORA-09953: scggc: unexpected return of a lock convert
Action: Check for lock manager error message and refer to DLM documentation refer
to the distributed lock manager documentation or contact your customer support
representative.
ORA-09954: scgcc: unexpected return status to callback of lock close
ORA-09870 to ORA-12100 64-7
Action: Check for lock manager error message and refer to DLM documentation refer
to the distributed lock manager documentation or contact your customer support
representative.
ORA-09955: scgcan: unexpected return status when canceling a lock
Cause: DLM system service x returned an unexpected value
Action: Check for system error message and refer to DLM documentation refer to the
distributed lock manager documentation or contact your customer support
representative.
ORA-09956: scgcm: unexpected lock status condition
Cause: A global locking system service returned an unexpected value.
Action: Check for system error message (if any) and refer to refer to the distributed
lock manager documentation or contact your customer support representative.
ORA-09957: Unable to send termination request to IMON
Cause: The attempt to send a termination signal to IMON failed.
Action: This is an internal error, contact ORACLE support.
ORA-09958: IMON: two processes with the same ORACLE pid are active
Cause: The IMON process was unable to add an entry for a server process because
another active process occupies the slot.
ORA-09959: IMON: deletion of a process failed.
Cause: The IMON process was unable to delete a server process from its process ID
array because no entry for the process could be found.
ORA-09960: Unable to establish signal handler for termination signal
Cause: ORACLE was unable to set up a handler for the signal used to notify it that the
instance was shutting down.
ORA-09961: Unable to restore termination signal handler
Cause: ORACLE failed to set the handler for the termination signal to its previous
value.
ORA-09962: lk_group_create error in scggrc
ORA-09963: lk_group_attach error in scggra
ORA-09964: lk_group_detach error in scggrd
ORA-09966: falure in translation while expanding ?/dbs/lk for lock file
Cause: Oracle failed to translate ?/dbs/lk, when creating a file name for the database
mount lock or the instance startup/shutdown lock.
Action: Check additional return errors for more information.
64-8 Error Messages
ORA-09967: unable to create or open lock file

Cause: Oracle failed, when making an open system call, inorder to acquire a file lock
used by the database mount lock or the instance startup/shutdown lock.
Action: Check errno for more information.
ORA-09968: unable to lock file
Cause: The system call for locking a file returned an error when trying to acquire a
database mount lock or the instance startup/shutdown lock.
ORA-09969: unable to close or remove lock file
Cause: The close system call or unlink system call returned an error.
ORA-09974: skxfidini: Error Initializing SDI Channel
Cause: The process was unable to initialize the SDI channel properly.
Action: Correct the operating system error and retry the operation.
ORA-09975: kxfspini: Error Initializing SDI Process
Cause: The process was unable to attach to the SDI channel.
Action: Verify that the SDI process specific limits correctly configured. Correct the
operating system error and retry the operation.
ORA-09976: skxfqdini: Error Creating Port
Cause: The process was unable to create a communications endpoint.
Action: Verify that the SDI port specific limits correctly configured. Correct the
operating system error and retry the operation.
ORA-09977: skxfqhini: Error Connecting
Cause: The process was unable to connect to another endpoint.
Action: Verify that the SDI port specific limits correctly configured. Check that the
other node(s) is part of the cluster and operating properly. Correct the operating
system error and retry the operation.
ORA-09978: skxfqhdel: Error Disconnecting from another endpoint.
Cause: The process was unable to disconnect cleanly from another endpoint.
Action: Check that the other node(s) are part of the cluster and operating properly.
Check the instance and processes on the other node(s). Correct the operating system
error and retry the operation.
ORA-09979: skxfqhsnd: Error Sending a message to another endpoint
Cause: The process was unable to send a message to an existing endpoint.
ORA-09980: skxfqdrcv: Error Receiving a message from another endpoint
Cause: The process encountered an error while trying to receive a message.
ORA-09870 to ORA-12100 64-9
ORA-09981: skxfqdreg: Error Adding a page to the SDI buffer pool

Cause: The process was unable to add a page to the SDI buffer pool.
ORA-09982: skxfqddrg: Error Removing a page from the SDI buffer pool
Cause: The process was unable to remove a page to the SDI buffer pool.
ORA-09983: skxfidsht: Error shutting down SDI channel
Cause: The process was unable shut down the SDI channel
Action: Check the SDI persistent resources using SDI tools. Verify that all processes
exited cleanly and the instance is safely shut down. Delete any remaining SDI channel
IDs associated with the current instance.
ORA-09984: SGA file $ORACLE_HOME/dbs/sgadef$ORACLE_SID.dbf does not
exist
Cause: file does not exist or is not accessible
Action: Restart the instance to create the SGA definition file.
ORA-09985: SGA definition file could not be read
Cause: UNIX read() operation failed
Action: check errno and take appropriate action.
ORA-09986: wrong number of bytes read from SGA definition file
Cause: Struct skgmsdef size differs from no. of bytes read from SGA file
Action: Compare the two struct definitions and ensure that they are identical in size
and structure.
ORA-09987: unable to attach to SGA in READ-ONLY mode
Cause: The instance is not up, or SGA segments are not read-accessible
Action: Verify that the instance is up and read permissions for the SGA segments are
set.
ORA-09988: error while detaching SGA
Cause: skgmsdef struct is corrupted and/or segment addresses are modified
Action: Safely shut down instance and mount SGA segments again.
ORA-09989: attempt to use invalid skgmsdef struct pointer
Cause: Pointer to skgmsdef struct used without validating it
Action: Assign a valid address to the skgmsdef struct pointer before using it.
ORA-10010: Begin Transaction
ORA-10011: End Transaction
ORA-10012: Abort Transaction
ORA-10013: Instance Recovery
ORA-10014: Roll Back to Save Point
ORA-10015: Undo Segment Recovery
ORA-10016: Undo Segment extend

ORA-10017: Undo Segment Wrap
ORA-10018: Data Segment Create
ORA-10019: Turn off data/space search cache
ORA-10020: partial link restored to linked list (KSG)
ORA-10021: KST event to trace control file header writes and reads
ORA-10022: trace ktsgsp
ORA-10023: Create Save Undo Segment
ORA-10024: Write to Save Undo
ORA-10026: Apply Save Undo
ORA-10027: Specify Deadlock Trace Information to be Dumped
ORA-10028: Dump trace information during lock / resource latch cleanup
ORA-10029: session logon (KSU)
ORA-10030: session logoff (KSU)
ORA-10033: sort run information (SRD*/SRS*)
ORA-10034: access path analysis (APA*)
ORA-10035: Write parse failures to alert log file
ORA-10036: create remote row source (QKANET)
ORA-10037: allocate remote row source (QKARWS)
ORA-10038: dump row source tree (QBADRV)
ORA-10039: type checking (OPITCA)
ORA-10040: disable result-cache
ORA-10041: dump undo records skipped
ORA-10042: file header reads return youngest mirror
ORA-10043: check consistency of owner/waiter/converter lists in KSQ
ORA-10044: free list undo operations
ORA-10045: free list update operations - ktsrsp, ktsunl
ORA-10046: enable SQL statement timing
ORA-10047: trace switching of sessions
ORA-09870 to ORA-12100 64-11
ORA-10048: Undo segment shrink

ORA-10049: protect library cache memory heaps
ORA-10050: sniper trace
ORA-10051: trace OPI calls
ORA-10052: don't clean up obj$
ORA-10053: CBO Enable optimizer trace
ORA-10054: CBO Enable optimizer trace for recursive statement (RPI)
ORA-10056: dump analyze stats (kdg)
ORA-10057: suppress file names in error messages
ORA-10058: use table scan cost in tab$.spare1
ORA-10059: simulate error in logfile create/clear
ORA-10060: CBO Enable predicate dump
ORA-10061: disable SMON from cleaning temp segment
ORA-10062: disable usage of OS Roles in osds
ORA-10063: disable usage of DBA and OPER privileges in osds
ORA-10074: default trace function mask for kst
ORA-10075: CBO Disable outer-join to regular join conversion
ORA-10076: CBO Enable cartesian product join costing
ORA-10077: CBO Disable view-merging optimization for outer-joins
ORA-10078: CBO Disable constant predicate elimination optimization
ORA-10079: trace data sent/received via SQL*Net
ORA-10080: dump a block on a segment list which cannot be exchanged
ORA-10081: segment High Water Mark has been advanced
ORA-10082: free list head block is the same as the last block
ORA-10084: free list becomes empty
ORA-10085: free lists have been merged
ORA-10086: CBO Enable error if kko and qka disagree on oby sort
ORA-10091: CBO Disable constant predicate merging
ORA-10092: CBO Disable hash join
ORA-10093: CBO Enable force hash joins

ORA-10102: switch off anti-joins
ORA-10103: CBO Disable hash join swapping
ORA-10104: dump hash join statistics to trace file
ORA-10105: CBO Enable constant pred trans and MPs w WHERE-clause
ORA-10106: CBO Disable evaluating correlation pred last for NOT IN
ORA-10107: CBO Always use bitmap index
ORA-10108: CBO Don't use bitmap index
ORA-10109: CBO Disable move of negated predicates
ORA-10110: CBO Try index rowid range scans
ORA-10111: Bitmap index creation switch
ORA-10115: CBO Bitmap optimization use maximal expression
ORA-10116: CBO Bitmap optimization switch
ORA-10117: CBO Disable new parallel cost model
ORA-10118: CBO Enable hash join costing
ORA-10119: QKA Disable GBY sort elimination
ORA-10120: generate relative file # different from absolute
ORA-10121: CBO Don't sort bitmap chains
ORA-10122: Disable transformation of count(col) to count(*)
ORA-10124: Force creation of segmented arrays by kscsAllocate
ORA-10125: Disable remote sort elimination
ORA-10126: Debug oracle java xa
ORA-10127: Disable remote query block operation
ORA-10128: Dump Partition Pruning Information
ORA-10129: Alter histogram lookup for remote queries
ORA-10130: sort disable readaheads
ORA-09870 to ORA-12100 64-13
ORA-10132: dump plan after compilation

ORA-10133: testing for SQL Memory Management
ORA-10134: tracing for SQL Memory Management for session
ORA-10135: CBO do not count 0 rows partitions
ORA-10136: CBO turn off fix for bug 1089848
ORA-10141: CBO disable additional keys for inlist in bitmap optimization
ORA-10142: CBO turn off advanced OR-expansion checks
ORA-10143: CBO turn off hints
ORA-10144: CBO turn off cost based selection of bji over bsj subquery
ORA-10145: test auditing network errors
ORA-10146: enable Oracle TRACE collection
ORA-10147: enable join push through UNION view
ORA-10149: allow the creation of constraints with illegal date constants
ORA-10152: CBO don't consider function costs in plans
ORA-10153: Switch to use public synonym if private one does not translate
ORA-10154: Switch to disallow synonyms in DDL statements
ORA-10155: CBO disable generation of transitive OR-chains
ORA-10156: CBO disable index fast full scan
ORA-10157: CBO disable index access path for in-list
ORA-10158: CBO preserve predicate order in post-filters
ORA-10159: CBO disable order-by sort pushdown into domain indexes
ORA-10160: CBO disable use of join index
ORA-10161: CBO recursive semi-join on/off-switch
ORA-10162: CBO join-back elimination on/off-switch
ORA-10163: CBO join-back elimination on/off-switch
ORA-10164: CBO disable subquery-adjusted cardinality fix

ORA-10166: trace long operation statistics updates
ORA-10167: CBO use old index MIN/MAX optimization
ORA-10168: CBO disable single-table predicate predicate generation
ORA-10169: CBO disable histograms for multi partitions
ORA-10170: CBO use old bitmap costing
ORA-10171: CBO disable transitive join predicates
ORA-10172: CBO force hash join back
ORA-10173: Dynamic Sampling time-out error
ORA-10174: view join-back elimination switch
ORA-10175: CBO star transformation switch
ORA-10176: CBO colocated join switch
ORA-10177: CBO colocated join switch
ORA-10178: CBO turn off hash cluster filtering through memcmp
ORA-10179: CBO turn off transitive predicate replacement
ORA-10180: temp table transformation print error messages
ORA-10181: CBO disable multi-column in-list processing
ORA-10182: CBO disable generation of implied predicates
ORA-10183: CBO disable cost rounding
ORA-10184: CBO disable OR-exp if long inlist on bitmap column
ORA-10185: CBO force index joins
ORA-10186: CBO disable index join
ORA-10187: CBO additional index join switch
ORA-10188: CBO additional index join switch
ORA-10189: CBO turn off FFS null fix
ORA-10190: Analyze use old frequency histogram collection and density
ORA-10191: Avoid conversion of in-lists back to OR-expanded form
ORA-10192: nopushdown when number of groups exceed number of rows
ORA-10193: Force repeatable sampling with specified seed
ORA-09870 to ORA-12100 64-15
ORA-10194: CBO disable new LIKE selectivity heuristic

ORA-10195: CBO don't use check constraints for transitive predicates
ORA-10196: CBO disable index skip scan
ORA-10197: CBO force index skip scan
ORA-10199: set parameter in session
ORA-10200: consistent read buffer status
ORA-10201: consistent read undo application
ORA-10202: consistent read block header
ORA-10203: block cleanout
ORA-10204: signal recursive extend
ORA-10205: row cache debugging
ORA-10206: transaction table consistent read
ORA-10207: consistent read transactions' status report
ORA-10208: consistent read loop check
ORA-10209: enable simulated error on control file
ORA-10210: check data block integrity
ORA-10212: check cluster integrity
ORA-10213: crash after control file write
ORA-10214: simulate write errors on control file
ORA-10215: simulate read errors on control file
ORA-10216: dump control file header
ORA-10217: debug sequence numbers
ORA-10218: dump uba of applied undo
ORA-10219: monitor multi-pass row locking
ORA-10220: show updates to the transaction table
ORA-10221: show changes done with undo
ORA-10222: row cache
ORA-10223: transaction layer - turn on verification codes
ORA-10224: index block split/delete trace
ORA-10225: free/used extent row cache

ORA-10226: trace CR applications of undo for data operations
ORA-10227: verify (multi-piece) row structure
ORA-10228: trace application of redo by kcocbk
ORA-10229: simulate I/O error against datafiles
ORA-10230: KSFD block repair test event
ORA-10231: skip corrupted blocks on _table_scans_
ORA-10232: dump corrupted blocks symbolically when kcbgotten
ORA-10233: skip corrupted blocks on index operations
ORA-10235: check memory manager internal structures
ORA-10237: simulate ^C (for testing purposes)
ORA-10238: instantiation manager
ORA-10239: multi-instance library cache manager
ORA-10240: dump dba's of blocks that we wait for
ORA-10241: remote SQL execution tracing/validation
ORA-10242: suppress OER 2063 (for testing distrib w/o different error log)
ORA-10243: simulated error for test string of K2GTAB latch cleanup
Cause: levels 1..6 for insert, 7..11 for delete
Action: n/a
ORA-10244: make tranids in error msgs print as 0.0.0 (for testing)
Cause: also makes "alter system enable distributed recovery" synchronous
Action: n/a
ORA-10245: Testing event used by server I/O ksfd/ksfq module
ORA-10246: print trace of PMON actions to trace file
ORA-10247: Turn on scgcmn tracing. (VMS ONLY)
ORA-10248: turn on tracing for dispatchers
ORA-10249: turn on tracing for multi-stated servers
ORA-10250: Trace all allocate and free calls to the topmost SGA heap
ORA-10251: check consistency of transaction table and undo block
ORA-10252: shared IO pool error simulation
ORA-09870 to ORA-12100 64-17
ORA-10253: limit SQL text returned from X$KGLNA[1]

ORA-10254: trace cross-instance calls
ORA-10255: pl/sql parse checking
ORA-10257: trace shared server load balancing
ORA-10258: force shared servers to be chosen round-robin
ORA-10259: get error message text from remote using explicit call
Cause: for npigem coverage testing (normally called only for V5 remote)
Action: n/a
ORA-10260: limit size (string) of the PGA heap set by event 10261 exceeded
Cause: The PGA memory use exceeded the limit set by the event 10261.
Action: Check event 10261 settings.
ORA-10261: limit the size of the PGA heap
Cause: The limit was one kilobyte times the level of the event. If the PGA grows
bigger than this, signal an external error.
Action: n/a
ORA-10262: Don't check for memory leaks
Cause: Setting this event to level one causes memory leak checking to be disabled.
Setting this event to any other non-zero number allows that number to be used as a
threshold value when checking for memory leaks in the PGA, SGA, and UGA heaps.
Action: n/a
ORA-10263: Don't free empty PGA heap extents
Cause: This is useful for debugging since watchpoints are lost on free
Action: n/a
ORA-10265: Keep random system generated output out of error messages
Cause: so test system files don't diff
Action: n/a
ORA-10266: Trace OSD stack usage
Cause: Porters should implement this to help them debug their stack
implementations. It should be used in at least smcstk().
Action: n/a
ORA-10267: Inhibit KSEDMP for testing
Cause: Some tests may generate internal or fatal errors on purpose.
Action: LEVEL used by KSEDMP is one less than level of this event.
ORA-10268: Don't do forward coalesce when deleting extents
Cause: setting this event keeps kts from coalescing forward at each extent when
dropping a temp segment.
Action: n/a
ORA-10269: Don't do coalesces of free space in SMON

Cause: setting this event prevents SMON from doing free space coalesces
Action: n/a
ORA-10270: Debug shared cursors
Cause: Enables debugging code in shared cursor management modules
Action: n/a
ORA-10271: distributed transaction after COLLECT
ORA-10272: distributed transaction before PREPARE
ORA-10273: distributed transaction after PREPARE
ORA-10274: distributed transaction before COMMIT
ORA-10275: distributed transaction after COMMIT
ORA-10276: distributed transaction before FORGET
ORA-10277: Cursor sharing (or not) related event (used for testing)
ORA-10278: Internal testing
ORA-10279: Simulate block corruption in kdb4chk
ORA-10280: Internal testing - segmentation fault during crash recovery
ORA-10281: maximum time to wait for process creation
Cause: used to override the default SPMXWAIT, level = timeout in sec.
Action: n/a
ORA-10282: Inhibit signalling of other backgrounds when one dies
Cause: Used in KSB
Action: n/a
ORA-10284: simulate zero/infinite asynch I/O buffering
Cause: Used in KCF, level=1 out of space (red), level=2 infinite (green)
Action: n/a
ORA-10285: Simulate control file header corruption
ORA-10286: Simulate control file open error
ORA-10287: Simulate archiver error
ORA-10288: Do not check block type in ktrget
ORA-10289: Do block dumps to trace file in hex rather than fromatted
ORA-10290: Internal sequence tracing event
ORA-10291: die in tbsdrv to test control file undo
ORA-09870 to ORA-12100 64-19
ORA-10294: ksrpc tracing

ORA-10296: disable ORA-379
ORA-10298: ksfd i/o tracing
ORA-10299: Trace prefetch tracking decisions made by CKPT
ORA-10301: Enable LCK timeout table consistency check
ORA-10319: Trace PGA statistics maintenance
ORA-10320: Enable data layer (kdtgrs) tracing of space management calls
ORA-10322: CBO don't simplify inlist predicates
ORA-10323: before committing an add datafile command
ORA-10324: Enable better checking of redo logs errors
ORA-10336: Do remote object transfer using remote SQL
ORA-10338: CBO don't use inlist iterator with function-based indexes
ORA-10339: CBO disable DECODE simplification
ORA-10341: Simulate out of PGA memory in DBWR during object reuse
ORA-10342: Raise unknown exception in ACQ_ADD when checkpointing
ORA-10343: Raise an out of memory exception-OER 4031 in ACQ_ADD
ORA-10345: validate queue when linking or unlinking a buffer
ORA-10346: check that all buffers for checkpoint have been written
ORA-10347: dump active checkpoint entries and checkpoint buffers
ORA-10349: do not allow ckpt to complete
ORA-10350: Simulate more than one object & tsn id in object reuse
ORA-10351: size of slots
ORA-10352: report direct path statistics
ORA-10353: number of slots
ORA-10354: turn on direct read path for parallel query
ORA-10355: turn on direct read path for scans
ORA-10356: turn on hint usage for direct read
ORA-10357: turn on debug information for direct path
ORA-10358: Simulate out of PGA memory in cache advisory reset
ORA-10359: turn off updates to control file for direct writes

ORA-10365: turn on debug information for adaptive direct reads
ORA-10366: kgnfs tracing
ORA-10367: kgodm tracing
ORA-10368: maximum number of internal errors a process will tolerate
ORA-10369: test SQL monitoring feature
ORA-10375: turn on checks for statistics rollups
ORA-10376: enable archive compression loads
ORA-10378: force hard process/range affinity
ORA-10380: kxfp latch cleanup testing event
ORA-10381: kxfp latch cleanup testing event
ORA-10383: auto parallelization testing event
ORA-10384: parallel dataflow scheduler tracing
ORA-10385: parallel table scan range sampling method
ORA-10386: parallel SQL hash and range statistics
ORA-10390: Trace parallel query slave execution
ORA-10391: trace PX granule allocation/assignment
ORA-10392: parallel query debugging bits
ORA-10393: print parallel query statistics
ORA-10394: generate a fake load to test adaptive and load balancing
ORA-10395: adjust sample size for range table queues
ORA-10397: suppress verbose parallel coordinator error reporting
ORA-10398: enable timeouts in parallel query threads
ORA-10399: trace buffer allocation
ORA-10400: turn on system state dumps for shutdown debugging
ORA-10401: turn on IPC (ksxp) debugging
ORA-10402: turn on IPC (skgxp) debugging
ORA-10403: fake CPU number for default degree of parallelism
ORA-10404: crash dbwr after write
ORA-09870 to ORA-12100 64-21
ORA-10405: emulate broken mirrors

ORA-10406: enable datetime TIMESTAMP, INTERVAL datatype creation
ORA-10407: enable datetime TIME datatype creation
ORA-10408: disable OLAP builtin window function usage
ORA-10409: enable granule memset and block invalidation at startup
ORA-10450: signal ctrl-c in kdddca (drop column) after n rows
ORA-10451: Force heap segment compression bypassing compatibility checks
ORA-10452: Cannot do block media recovery; media recovery session may be in
progress
Cause: A media recovery, RMAN, or flashback database session may have been in
progress when an attempt was made to perform block media recovery on the standby
database.
Action: Check for and cancel any conflicting recovery session and perform block
media recovery on the standby database.
ORA-10456: cannot open standby database; media recovery session may be in
progress
Cause: A media recovery, RMAN, or flashback database session may have been in
progress on a mounted instance of a standby database when an attempt was made to
open the standby database.
Action: Check for and cancel any conflicting recovery session and open the standby
database.
ORA-10457: cannot close standby database due to active media recovery
Cause: A media recovery session was in progress on a standby database when an
attempt was made to close the standby database.
Action: Cancel the media recovery session and close the standby database.
ORA-10458: standby database requires recovery
Cause: A standby database was in a state requiring media recovery when an attempt
was made to open the standby database.
Action: Perform the necessary recovery and open the standby database.
ORA-10459: cannot start media recovery on standby database; conflicting state
detected
Cause: An attempt was made to perform media recovery on a standby database while
another instance was performing recovery on the standby database, had the standby
database open, or a data file move operation was in progress.
Action: Close the standby on all other instances, cancel any conflicting recovery
session or data file move operation, and perform manual recovery.
ORA-10460: Perform backward tablescans for consistent read reduction
ORA-10461: Simulate control file corruption during write operation
ORA-10462: enable recovery debug module
ORA-10469: error creating control file backup, no checkpoint

Cause: The control file being backed up did not contain a valid control file checkpoint.
Therefore the control file could not be backed up, as such a backup would not be
usable later for recovery. A common cause for this situation is that you executed
CREATE CONTROLFILE, which mounts the database, but not ALTER DATABASE
OPEN, to open the database. The latter operation generates a valid control file
checkpoint.
Action: Open the database with ALTER DATABASE OPEN ..., which results in a
valid control file checkpoint. Run the backup operation again.
ORA-10481: Backup data block for data file has an unlogged change
Cause: Flashback was enabled for the data file when the backup data block used for
block media recovery had an unlogged change.
Action: Remove the data file from the flashback set or use a backup block that does
not contain an unlogged change to perform block media recovery.
ORA-10482: Automatic block repair cannot repair an offline or read-only data file
Cause: Automatic block repair failed when trying to repair an offline or read-only
data file.
Action: Bring the data file online in read/write mode.
ORA-10485: Real-Time Query cannot be enabled while applying migration redo.
Cause: The Real-Time Query feature was enabled when an attempt was made to
recover through migration redo generated during primary upgrades or downgrades.
Action: Close the standby database in order to recover through migration redo.
Reenable the Real-Time Query feature afterwards.
ORA-10493: Return empty define buffers on 1422
ORA-10496: Turn off fix for bug 2554178
ORA-10498: Trim blank characters including contol characters
ORA-10501: periodically check selected heap
ORA-10502: CBO disable the fix for bug 2098120
ORA-10503: enable user-specified graduated bind lengths
ORA-10504: CBO disable the fix for bug 2607029
ORA-10505: CBO enable dynamic sampling dump to table
ORA-10506: Disable fix for bug 2588217
ORA-10507: Trace bind equivalence logic
ORA-10508: Enable fix for bug 14772545
ORA-10509: Check kghu subheaps at call boundaries
ORA-10510: turn off SMON check to offline pending offline rollback segment
ORA-10511: turn off SMON check to cleanup undo dictionary
ORA-09870 to ORA-12100 64-23
ORA-10512: turn off SMON check to shrink rollback segments

ORA-10515: turn on event to use physical cleanout
ORA-10519: enable ALTER TYPE RESET support
ORA-10520: recreate view only if definition has changed
ORA-10522: turn off wrap source compression
ORA-10523: force recreate package even if definition is unchanged
ORA-10525: Disable automatic object validation for describe
ORA-10526: enables lightweight thread tracing
Cause: Used in ksolt.
Action: Set this event only under the supervision of Oracle Support Services.
ORA-10527: enables defer SGA allocation tracing
Cause: Used for deferred SGA allocation.
ORA-10528: enables ksmg tracing
Cause: Used in ksmg module.
ORA-10530: Lightweight thread spawn failed, error stack:
Cause: Check alert/trace files for more information
Action: n/a
ORA-10531: Lightweight thread unit test failure error
Cause: Check alert/trace files for more information
Action: n/a
ORA-10546: Cannot perform block media recovery; standby database does not have
requisite redo.
Cause: An attempt was made to perform block media recovery on the standby
database when the necessary redo was not available.
Action: Wait until the necessary redo is available and reattempt block media recovery.
ORA-10547: Cannot perform block media recovery; standby database is not caught
up with primary.
Cause: An attempt was made to perform block media recovery on the standby
database up to scn %s, which is greater than the highest scn of %s yet applied at the
standby.
Action: Recover the standby up to scn %s and reattempt block media recovery.
ORA-10548: Cannot perform block media recovery on a read-only plugged-in
datafile.
Cause: An attempt was made to perform block media recovery on a read-only
plugged-in datafile.
Action: Convert the plugged-in datafile to read/write and reattempt block media
recovery.
ORA-10549: Cannot perform block media recovery using a read-only plugged-in
backup datafile.
Cause: An attempt was made to perform block media recovery using a backup of a
read-only plugged-in datafile.
Action: Reattempt block media recovery using a backup taken after the plugged-in
datafile has been converted to read/write.
ORA-10550: signal error during create as select/create index after n rows
ORA-10551: Internal testing for ORA-1551 error handling
ORA-10553: Incompatible UNTIL CONSISTENT clause
Cause: RECOVER UNTIL CONSISTENT required database-level recovery with a
backup control file.
Action: Omit the UNTIL CONSISTENT clause and retry recovery.
ORA-10554: Media recovery failed to bring datafile string to a consistent point
Cause: Media recovery couldn't recover database to a consistent point due to the
specified datafile.
Action: Restore a backup of the datafile.
ORA-10555: Disable redo dumping
ORA-10560: block type 'string'
Cause: Report block type for details of another error.
ORA-10561: block type 'string', data object# string
Cause: Report block type and data object number for details of another error.
ORA-10562: Error occurred while applying redo to data block (file# string, block#
string)
Cause: See other errors on error stack.
Action: Investigate why the error occurred and how important is the data block.
Media and standby database recovery usually can continue if user allows recovery to
corrupt this data block.
ORA-10563: Test recovery had to corrupt data block (file# string, block# string) in
order to proceed
Cause: Test recovery completed.
Action: No action is needed. Test recovery has ended successfully. See other messages
on error stack for a summary of the result of the test recovery.
ORA-10564: tablespace string
Cause: Report tablespace name for details of another error.
ORA-09870 to ORA-12100 64-25
ORA-10565: Another test recovery session is active

Cause: There can only be one test recovery session at any time. Another test recovery
session is active.
Action: Wait till the other test recovery session completes.
ORA-10566: Test recovery has used all the memory it can use
Cause: Test recovery tests redo in memory. It can no longer proceed because it has
consumed all the memory it can use.
on error stack for a summary result of the test recovery.
ORA-10567: Redo is inconsistent with data block (file# string, block# string, file
offset is string bytes)
Cause: There are two possible causes of this error: (1) A write issued by Oracle was
lost by the underlying OS or storage system. (2) an Oracle internal error.
Action: Investigate why the error occurred and how important is the data block.
Media and standby database recovery usually can continue if user allows recovery to
corrupt this data block.
ORA-10568: Failed to allocate recovery state object: out of SGA memory
Cause: out of SGA memory
Action: Restart the instance. If problem persists, call Oracle support.
ORA-10570: Test recovery complete
Cause: Test recovery completed.
on error stack for a summary result of the test recovery.
ORA-10571: Test recovery canceled
Cause: User canceled test recovery.
on error stack for a summary of the result of the test recovery.
ORA-10572: Test recovery canceled due to errors
Cause: See other errors on the error stack.
Action: See other messages on error stack. It is possible that no action is needed. See
other messages on error stack for a summary of the result of the test recovery so far.
ORA-10573: Test recovery tested redo from change string to string
Cause: This message show the range of test recovery have tested.
Action: No action is needed. See other messages on error stack.
ORA-10574: Test recovery did not corrupt any data block
Cause: This message summarizes test recovery result.
Action: No action is needed. See other messages on error stack.
ORA-10575: Give up restoring recovered datafiles to consistent state: out of
memory
Cause: There were not enough memory to restore recovered datafiles to consistent
state
Action: This error is just a warning: You may not be able to open the database with
resetlogs immediately after this error. However, you may continue media/standby
recovery, and that may make the datafiles recovered consistent again.
ORA-10576: Give up restoring recovered datafiles to consistent state: some error
occurred
Cause: See alert file or other errors on the stack for a cause of the problem.
Action: This error is just a warning: You may not be able to open the database with
resetlogs immediately after this error. However, you may continue media/standby
recovery, and that may make the datafiles recovered consistent again.
ORA-10577: Can not invoke test recovery for managed standby database recovery
Cause: Test recovery option is used for managed standby database recovery.
Action: Either remove the test recovery option or invoke manual test standby
database recovery.
ORA-10578: Can not allow corruption for managed standby database recovery
Cause: You used the allow corruption option for managed standby database recovery.
Action: Either remove the allow corruption option or invoke manual standby
database recovery.
ORA-10579: Can not modify control file during test recovery
Cause: To proceed with recovery, test recovery needs to modify the control file. But
test recovery is not allowed to modify control file.
Action: No action is needed. Test recovery has ended successfully. It can only go so
far in the redo stream.
ORA-10580: Can not modify datafile header during test recovery
Cause: To proceed with recovery, test recovery needs to modify a datafile header. But
test recovery is not allowed to modify datafile headers.
ORA-10581: Can not modify redo log header during test recovery
Cause: To proceed with recovery, test recovery needs to modify a redo log header.
But test recovery is not allowed to modify redo log headers.
ORA-10582: The control file is not a backup control file
Cause: User requested backup control file test recovery, but the control file is not a
backup control file.
Action: Use a backup control file, or do not use USING BACKUP CONTROLFILE
option.
ORA-10583: Can not recovery file string renamed as missing during test recovery
Cause: One of the files to be recovered is renamed as missing.
Action: Rename the file to the correct file or offline it.
ORA-10584: Can not invoke parallel recovery for test recovery
Cause: Both test recovery and parallel recovery are requested.
Action: Drop either one of the two recovery options.
ORA-09870 to ORA-12100 64-27
ORA-10585: Test recovery can not apply redo that may modify control file
Cause: Test recovery has encountered a special redo that may modify control file.
Action: No action is needed. Test recovery has proceeded successfully as far as it
could from its starting point.
ORA-10586: Test recovery had to corrupt 1 data block in order to proceed
Cause: This message summarizes test recovery result: Oracle may have to corrupt one
block in order to apply the range of redo tested.
Action: See alert log for details of the problem.
ORA-10587: Invalid count for ALLOW n CORRUPTION option
Cause: The number specified in the ALLOW n CORRUPTION option is too big.
Action: Use a smaller number.
ORA-10588: media recovery file header validation
ORA-10589: Test recovery had to corrupt string data blocks in order to proceed
Cause: This message summarizes test recovery result: Oracle may have to corrupt a
number of data blocks as specified in the message in order to apply the range of redo
tested.
Action: See alert log for details of the problems.
ORA-10590: kga (argus debugger) test flags
ORA-10600: check cursor frame allocation
ORA-10601: turn on debugging for cursor_sharing (literal replacement)
ORA-10603: cause an error to occur during truncate (for testing purposes)
ORA-10604: trace parallel create index
ORA-10605: enable parallel create index by default
ORA-10606: trace parallel create index
ORA-10607: trace index rowid partition scan
ORA-10608: trace create bitmap index

ORA-10609: trace for array index insertion
ORA-10610: trace create index pseudo optimizer
ORA-10611: causes migration to fail - testing only
ORA-10612: prints debug information for auto-space managed segments
ORA-10613: prints debug information for auto-space managed segments
ORA-10614: Operation not allowed on this segment
Cause: This procedure can be used only on segments in tablespaces with AUTO
SEGMENT SPACE MANAGEMENT
Action: Recheck the segment name and type and re-issue the statement
ORA-10615: Invalid tablespace type for temporary tablespace
Cause: Tablespace with AUTO SEGMENT SPACE MANAGENEMT specified cannot
be used as a temporary tablespace
Action: Recheck the tablespace name and re-issue the statement
ORA-10616: Operation not allowed on this tablespace
Cause: Cannot perform the operation on tablespace with AUTO SEGMENT SPACE
MANAGEMENT
ORA-10617: Cannot create rollback segment in dictionary managed tablespace
Cause: Rollback segments cannot be created in dictionary managed tablespaces when
SYSTEM tablespace is locally managed
Cause: This DBMS_SPACE operation is not permitted on segments in tablespaces
with AUTO SEGMENT SPACE MANAGEMENT
Action: Recheck the segment name and type and re-issue the statement
ORA-10619: Avoid assertions when possible
Cause: A bug (or upgrade) hits unicode assertions (csid, csform, bfc)
Action: Event makes RDBMS skip assertions and patch up datastructures
Cause: Cannot alter freelist storage parameter for segments in tablespaces with AUTO
SEGMENT SPACE MANAGEMENT
Action: Recheck the segment name and re-issue the statement
ORA-10621: specify retry count for online index build cleanup DML lock get
ORA-10624: Disable UJV invalidation on drop index
ORA-10625: Turn off redo log dump for the index when OERI 12700
ORA-10626: specify timeout for online index rebuild to wait for DML
ORA-09870 to ORA-12100 64-29
ORA-10627: Dump the content of the index leaf block

Cause: Generate a complete index tree dump, not just an overview during alter
session set events immediate trace name treedump
Action: This event is recommended only for small table/index since it
ORA-10628: Turn on sanity check for kdiss index skip scan state
Cause: Will do sanity checking on the kdiss state.
Action: set this event only under the supervision of Oracle development
ORA-10629: force online index build to backoff and retry DML lock upgrade
ORA-10630: Illegal syntax specified with SHRINK clause
Cause: An illegal option was specified with the SHRINK clause
Action: Verify the SQL Reference Manual and reissue the command
ORA-10631: SHRINK clause should not be specified for this object
Cause: It is incorrect to issue shrink on the object
Action: Verify the object name and type and reissue the command
ORA-10632: Invalid rowid
Cause: Segment Highwatermark was overwritten due to shrink and space reused
Action: Reissue this command.
ORA-10634: Segment is already being shrunk
Cause: Only one invocation of shrink can be in progress on a segment at any time
Action: Reissue the command after the first shrink is over
ORA-10635: Invalid segment or tablespace type
Cause: Cannot shrink the segment because it is not in auto segment space managed
tablespace or it is not a data, index or lob segment.
Action: Check the tablespace and segment type and reissue the statement
ORA-10636: ROW MOVEMENT is not enabled
Cause: To shrink a data segment, row movement must be enabled.
Action: Enable row movement and reissue this command.
ORA-10637: The segment does not exist
Cause: Segment to be shrunk has been dropped
Action: n/a
ORA-10638: Index status is invalid
Cause: Cannot shrink an index which is being rebuilt or disabled is an unusable state.
Action: n/a
ORA-10639: Dump library cache during reparse loops
Cause: During this error a library cache dump is necessary , so enable librarycache
dump if event is set.
Action: Dump a library cache if this event is set when reparse error.
ORA-10640: Operation not permitted during SYSTEM tablespace migration
Cause: SYSTEM tablespace is being migrated to locally managed format.
Action: Reissue this command once SYSTEM tablespace migration is over.

ORA-10641: Cannot find a rollback segment to bind to
Cause: SYSTEM tablespace migration requires rollback segment in locally managed
tablespace.
Action: Drop rollback segments in dictionary managed tablespaces other than
SYSTEM and create rollback segments in locally managed tablespace and retry
migration.
ORA-10642: Found rollback segments in dictionary managed tablespaces
Cause: When SYSTEM tablespace is migrated found rollback segments in dictionary
managed tablespaces.
Action: Drop the rollback segments in dictionary managed tablespaces and reissue
the command
ORA-10643: Database should be mounted in restricted mode and Exclusive mode
Cause: When SYSTEM tablespace is being migrated database should be mounted in
Exclusive mode and in Restricted mode.
Action: Reissue this command after mounting the database in right mode.
ORA-10644: SYSTEM tablespace cannot be default temporary tablespace
Cause: When SYSTEM tablespace is being migrated no user should have SYSTEM as
the default temporary tablespace.
Action: Reissue this command after altering the default temporary tablespace setting
for all users.
ORA-10645: Recursive Extension in SYSTEM tablespace during migration
Cause: When SYSTEM tablespace is being migrated, dictionary tables tried to extend
recursively. Must be caught and processed internally. Should not be thrown to the
user.
Action: Report the error as a bug.
ORA-10646: Too many recursive extensions during SYSTEM tablespace migration
Cause: When SYSTEM tablespace is being migrated, dictionary tables tried to extend
recursively more than 1000 times.
Action: If SYSTEM tablespace is very large, then simply reissue the tablespace
migration command.
ORA-10647: Tablespace other than SYSTEM, string, string not found in read only
mode
Cause: When SYSTEM tablespace is being migrated, tablespaces other than the three
should be ALTERed to read only.
Action: Alter the tablespace status to read only and retry migration.
ORA-10648: Tablespace SYSAUX is not offline
Cause: The SYSAUX tablespace was online while SYSTEM tablespace was being
migrated.
Action: Alter the SYSAUX tablespace status to offline and retry migration.
ORA-10649: Turn off/trace lob index freelist coalesce
Cause: Will turn off or trace lob index freelist coalescing
Action: set this event only under the supervision of Oracle development
ORA-09870 to ORA-12100 64-31
ORA-10650: disable cache-callback optimisation

ORA-10651: incorrect file number block number specified
Cause: The dba specified is not valid
Action: Check if the dba specified belongs to the segment and is under the segment
HWM and reissue the statement
ORA-10652: Object has on-commit materialized views
Cause: It is illegal to issue shrink on an object with on-commit materialized views
Action: n/a
ORA-10653: Table is in a cluster
Cause: It is illegal to shrink a table belonging to a cluster
Action: n/a
ORA-10654: Table is of type temporary or external
Cause: It is illegal to shrink a temporary table or an external table
Action: n/a
ORA-10655: Segment can be shrunk
Cause: Error message returned when called in probe mode by OEM
Action: n/a
ORA-10656: Table is in unusable state due to incomplete operation
Cause: ALTER TABLE SHRINK operation was tried on the table which is in unusable
state because of previously failed/incomplete operation.
Action: If the previous operation was - DROP COLUMN, resubmit DROP COLUMN
CONTINUE - DROP TABLE, resubmit DROP TABLE table PURGE
ORA-10657: Lob column to be shrunk does not exist
Cause: Shrink was issued on a lob segment that did not exist
Action: n/a
ORA-10658: Lob column to be shrunk is marked unused
Cause: Shrink was issued on a lob segment that is marked as unused
Action: n/a
ORA-10659: Segment being shrunk is not a lob
Cause: Shrink was issued on a segment that should be a first class lob or other data
type stored in lob
Action: n/a
ORA-10660: Segment is a shared lob segment
Cause: Shrink was issued on a segment that was being shared by multiple lob
columns
Action: n/a
ORA-10661: Invalid option specified
Cause: Check option can be specified for one segment only
Action: n/a
ORA-10662: Segment has long columns

Cause: Shrink was issued on a segment with long columns. This is not supported.
Action: n/a
ORA-10663: Object has rowid based materialized views
Cause: Shrink was issued on an object with rowid based materialized views.
Action: Drop the rowid based materialized views and issue shrink on the object
ORA-10664: Table has bitmap join indexes
Cause: SHRINK was issued on a table with bitmap join indexes.
Action: Drop bitmap join indexes and reissue SHRINK on the object.
ORA-10665: Inject Evil Literals
Cause: Event 10665 is set to some number > 0, causing 1/(value-1) of all literals to be
replaced by 2000 letter 'A's. A value of 1 does not corrupt anything.
Action: never set this event
ORA-10666: Do not get database enqueue name
ORA-10667: Cause sppst to check for valid process ids
ORA-10668: Inject Evil Identifiers
Cause: event 10668 is set to some number > 0, causing 1/(value-1) of all identifiers to
be replaced by a maximum amount of x's. It is common for an identifier to be parsed
once with a max of 30 bytes, then reparsed later with a max of 4000, so it may not be
possible to inject such an identifier without the aid of this event. A value of 1 causes
no identifiers to be corrupted.
Action: never set this event
ORA-10690: Set shadow process core file dump type (Unix only)
Cause: Control core file size for shadow processes
Action: Level 1: Detach SGA before dumping core Level 2: Do not produce any core
ORA-10691: Set background process core file type (Unix only)
Cause: Control core file size file for background processes
Action: Level 1: Detach SGA before dumping core
ORA-10700: Alter access violation exception handler
Cause: Use this event to control what the VMS exception handler does when it
encounters an access violation.
Action: Level: >=10 Suspend current process on access violation *** SET THIS EVENT
ONLY UNDER THE SUPERVISION OF ORACLE DEVELOPMENT ***
ORA-10701: Dump direct loader index keys
Cause: Dumps index keys at various points in a direct load based on the value of this
event.
Action: n/a
ORA-10702: Application continuity debugging was not enabled
Cause: Enable application continuity debugging
ORA-09870 to ORA-12100 64-33
Action: Level indicates details. Level: 0x0001: Transaction intention debugging

0x1000: Failure injection testing 0x2000: Failure injection testing 0x4000: Failure
injection testing
ORA-10704: Print out information about what enqueues are being obtained
Cause: When enabled, prints out arguments to calls to ksqcmi and ksqlrl and the
return values.
Action: Level indicates details: Level: 1-4: print out basic info for ksqlrl, ksqcmi 5-9:
also print out stuff in callbacks: ksqlac, ksqlop 10+: also print out time for each line
ORA-10706: Print out information about global enqueue manipulation
Cause: When enabled, prints out activity in ksi routines.
Action: INternal system parameter (_ksi_trace) can be used in addition to setting this
event to limit output information on selected set of global enqueue server enqueue
type(s) For example: _ksi_trace = RTXA output information only for RT and XA lock
types. Level indicates details: 0-4: show args for each main call 5-9: also indicate
callbacks 10+: also printout time for each line
ORA-10707: Simulate process death for instance registration
Cause: When enabled, process commits suicide to test instance registration recovery
code.
Action: Level indicates where the process will die
ORA-10709: enable parallel instances in create index by default
ORA-10710: trace bitmap index access
ORA-10711: trace bitmap index merge
ORA-10712: trace bitmap index or
ORA-10713: trace bitmap index and
ORA-10714: trace bitmap index minus
ORA-10715: trace bitmap index conversion to rowids
ORA-10716: trace bitmap index compress/decompress
ORA-10717: trace bitmap index compaction trace for index creation
ORA-10718: event to disable automatic compaction after index creation
ORA-10719: trace bitmap index dml
ORA-10720: trace db scheduling
ORA-10721: Internal testing - temp table transformation
ORA-10722: trace server level database scheduling
ORA-10723: Internal testing - release buffer for buffer cache shrink
ORA-10724: trace cross-instance broadcast
ORA-10725: bitmap index version control

ORA-10726: frequent itemset counting
ORA-10728: set parameters for CPU frequency calculation (debug)
ORA-10731: dump SQL for CURSOR expressions
ORA-10736: buffer cache pin history dump
ORA-10740: disables fix for bug 598861
ORA-10750: test rollback segment blksize guessing for index array insert
ORA-10751: override for remote row source maximum buffer size
ORA-10752: override for the Exponential Moving Average factor
ORA-10753: enforce deterministic behaviour for prefetching row source
ORA-10754: disable fix for bug 14173995 for multi-table select for update
ORA-10804: reserved for ksxb
ORA-10806: Switch to 7.3 mode when detaching sessions
ORA-10807: Disable user id check when switching to a global transaction
ORA-10808: Enable assert when waiting without a reason
ORA-10828: memory allocator error
Cause: Error in the memory allocator
Action: Check the trace files and other relevant output
ORA-10830: Trace group by sort row source
ORA-10831: Trace group by rollup row source
ORA-10832: Trace approximate NDV row source
ORA-10833: Runtime distribution keys for adaptive partial rollup
ORA-10834: Runtime behavior control for adaptive partial rollup
ORA-10841: Default un-inintialized charact set form to SQLCS_IMPLICIT
Cause: client side, such as JDBC-THIN 8i client sends 0 as charset form
Action: This event sets charset form as SQLCS_IMPLICIT when it is 0
ORA-10842: Event for OCI Tracing and Statistics Info
Cause: This event is meant for tracing OCI Calls and getting statistics
Action: This event sets tracing OCI Calls and gets statistics info
ORA-10844: turn on Native Net IPC debugging (skgxp)
ORA-09870 to ORA-12100 64-35
ORA-10845: Enable Director tracing

Cause: N/A
Action: Enable tracing of director/workload manager packages
ORA-10848: OCI Non Blocking not supported with string
Cause: Attempt made to set connection as non-blocking with another feature that
does not support non-blocking.
Action: Use blocking connection.
ORA-10849: Internal OCI event number
Cause: N/A
Action: Set this event only under the supervision of Oracle Support or Development.
This event enable compatible behavior with sending describe information when a
cursor rebuilt.
ORA-10850: Enable time manager tracing
ORA-10862: resolve default queue owner to current user in enqueue/dequeue
Cause: resolve default queue owner to current user in enqueue/dequeue.
Action: turn on if client wish to resolve the default queue owner to the current user. If
not turned on, the default queue owner will be resolved to the login user.
ORA-10873: file string needs to be either taken out of backup mode or media
recovered
Cause: An attempt was made to open a database after an instance failure or
SHUTDOWN ABORT interrupted an online backup.
Action: If the indicated file is not a restored backup, then issue the ALTER
DATABASE END BACKUP command and open the database. If the file is a restored
online backup, then apply media recovery to it and open the database.
ORA-10877: error signaled in parallel recovery slave string
Cause: A parallel recovery logmerger reached an exception condition.
Action: Check the following error message for the cause, and consult your error
manual for the appropriate action.
ORA-10878: parallel recovery slave died unexpectedly
Cause: A parallel recovery slave died unexpectedly, PMON cleaning up the process.
Action: Check your system for anomalies and reissue the statement. If this error
persists, contact Oracle Support Services. See trace file for more details.
ORA-10879: error signaled in parallel recovery slave string
Cause: A parallel recovery slave reached an exception condition.
ORA-10883: Event for Fast Application Notification tracing
Cause: This event sets tracing for Fast Application Notification (FAN).
Action: Level 5 - Set this level to dump out all FAN High Availability related
messages to trace files. This includes event payloads and error messages. 10 - Set this
level to dump out FAN Runtime Load Balancing related messages. This includes RLB
payloads and error messages.
ORA-10900: extent manager fault insertion event #string

Cause: causes faults to be generated in instrumented extent code
Action: this should only be enabled for internal testing
ORA-10901: disable the fix for bug 1230798
ORA-10902: disable seghdr conversion for ro operation
Cause: causes seghdr conversion to be turned off for ro ops(#555856)
Action: this should be enabled only if determined that bug 555856 has occured. Table
needs to be exported subsequently
ORA-10906: Unable to extend segment after insert direct load
Cause: This is a restriction with insert direct load transactions.
Action: When a segment has been insert direct loaded, avoid DMLs that could cause
more space to be consumed.
ORA-10911: Locally managed SYSTEM tablespace bitmaps can be modified only
under the supervision of Oracle Support
Cause: N/A
Action: n/a
ORA-10912: Used to perform admin operations on locally managed SYSTEM
tablespace
Cause: N/A
Action: The event should be used only under the supervision of Oracle Support
ORA-10914: invalid TABLESPACE GROUP clause
Cause: An invalid option appears for TABLESPACE GROUP clause.
Action: Specify a valid tablespace group name.
ORA-10915: TABLESPACE GROUP cannot be specified for this type of tablespace
Cause: In CREATE/ALTER TABLESPACE, the TABLESPACE GROUP clause was
used while creating/altering a tablespace that is not TEMPORARY.
Action: Remove the TABLESPACE GROUP clause.
ORA-10916: TABLESPACE GROUP already specified
Cause: In CREATE/ALTER TABLESPACE, the TABLESPACE GROUP option was
Action: Remove all but one of the TABLESPACE GROUP specifications.
ORA-10917: TABLESPACE GROUP cannot be specified
Cause: The tablespace name specified in the command is actually the name of a
tablespace group.
Action: Please specify an appropriate tablespace name.
ORA-10918: TABLESPACE GROUP name cannot be the same as tablespace name
Cause: The tablespace group name specified in the command is the same as the
tablespace being CREATEd/ALTERed.
Action: Please specify an appropriate tablespace group name.
ORA-09870 to ORA-12100 64-37
ORA-10919: Default temporary tablespace group must have at least one tablespace
Cause: An attempt was made to move the only tablespace in the default database
temporary tablespace group to another tablespace group.
Action: Either change the database default temporary tablespace or add another
tablespace to the group that this tablespace belongs to.
ORA-10920: Cannot offline tablespace belonging to default temporary tablespace
group
Cause: An attempt was made to offline a tablespace in the default database temporary
tablespace group.
Action: Either change the database default temporary tablespace or change the
tablespace group of this tablespace.
ORA-10921: Cannot drop tablespace belonging to default temporary tablespace
group
Cause: An attempt was made to drop a tablespace in the default database temporary
tablespace group.
Action: Either change the database default temporary tablespace or change the
tablespace group of this tablespace.
ORA-10922: Temporary tablespace group is empty
Cause: An attempt was made to allocate a temporary segment in a group, which now
no longer has any members.
Action: Either add some temporary tablespaces or change the temporary tablespace
for this user.
ORA-10923: prints debug information for object space server manageability
ORA-10924: import storage parse error ignore event
Cause: causes server to ignore specific error associated with freelists and freelist
groups when parsing
Action: this should be enabled by import code only
ORA-10925: trace name context forever
Cause: When enabled, turns off bugfix 237911
Action: set this event ONLY if necessary - after reading the README for this release
or under supervision of Oracle Support.
Cause: When enabled, provides V7 behavior for fixed char binds
Cause: When enabled, allows normal packages to be compiled with standard
extensions like "<ADT_1>"
Action: Set this event only for a short amount of time. Once the packages are
compiled, this event should be turned off. Level 1 - Turn the event on Level > 1 - Turn
the event off
Cause: When enabled, disables one or more features or bug fixes available only in
version 8.x.
version 8.x.
version 11.x.
Action: Set this event only if necessary - after reading the README for this release or
under supervision of Oracle Support Services.
Cause: When enabled, disables one or more features or bug fixes available in versions
7.x and 8.x.
Cause: Size of the PL/SQL tracing circular buffer, in kilobytes.
Action: Set this event in concert with the 10938 event and the
_PLSQL_DUMP_BUFFER_EVENTS init.ora parameter, under supervision of Oracle
Support.
Cause: When enabled, turns on PL/SQL profiler
ORA-09870 to ORA-12100 64-39
version 8.x.
Cause: When enabled, allows or controls PL/SQL OPT code gen project. available
only in version 8.2+.
Action: set this event ONLY for development of the OPT project. This is not for
general use or deployment.
Cause: When enabled, disables the behaviour change introduced by the fix for bug
822764, which traps and handles invalidations of packages whereas the previous
behaviour was to use stale invalidated instantiations of the stateful package body.
version 10.x.
Cause: When enabled, causes various PL/SQL warnings related debugging info to be
written in a trace file. Useful for debugging varous Oracle processes. available only in
version 10.x.
ORA-10949: Disable autotune direct path read for full table scan
ORA-10970: backout event for bug 2133357
Cause: 2133357 dynamically sets the varying width flag and character width. Lob data
which is not migrated during migration from single byte to multibyte charater set will
be displayed as special characters.
Action: To help migrate lob data which was not migrated during migration by
backing out 2133357, so lob data can be selected and moved to multibyte character set.
ORA-10973: backout evet for 2619509
Cause: 2619509 catches offsets when not reading/writing on full character boundary.
To facilitate backward compatiblity event is being introduced.
Action: To help upgrade/migrate issues which already have corrupt data
ORA-10979: trace flags for join index implementation
Cause: This is an informational message.
Action: Values are as follows: LEVEL ACTION

--------------------------------------------------------------------------- > 1 Dump refresh
expressions (SQL) to trace file. > 999 If a complete refresh is invoked, it will not be
performed but the system will assume that a complete refresh was done, causing the
view to be VALID and updating timestamps. This should be used only under Oracle
Support supervision.
ORA-10990: dump spreadsheet info
ORA-10992: event to enable dbms_job instead of dbms_scheduler
ORA-10993: Runtime enable IOQ batching
ORA-10994: Compiletime enable IOQ batching
ORA-10997: another startup/shutdown operation of this instance inprogress
Cause: An Oracle Instance startup or shutdown operation failed to procure the
serialization primitive. Another foreground process may have attempted startup or
shutdown operation in parallel.
Action: Check additional error messages in the alert log and the process trace file.
ORA-10999: do not get database enqueue name
ORA-12000: a materialized view log already exists on table 'string'
ORA-12001: cannot create log: table 'string' already has a trigger
Cause: Materialized view logs are filled by a trigger on the master table. That trigger
cannot be created.
Action: To create a materialized view log, drop the current trigger on the master.
ORA-12002: there is no materialized view log on table "string"."string"
Cause: There was no materialized view log on the master table.
Action: Create a materialized view log on the master table.
ORA-12003: materialized view or zonemap "string"."string" does not exist
Cause: The database object with the given owner and name was not found.
Action: Verify input and retry.
ORA-12004: REFRESH FAST cannot be used for materialized view "string"."string"
Cause: The materialized view log does not exist or cannot be used. PCT refresh is also
not enabled on the materialized view
Action: Use just REFRESH, which will reinstantiate the entire table. If a materialized
view log exists and the form of the materialized view allows the use of a materialized
view log or PCT refresh is possible after a given set of changes, REFRESH FAST will
be available starting the next time the materialized view is refreshed.
ORA-12005: may not schedule automatic refresh for times in the past
Cause: An attempt was made to schedule an automated materialized view refresh for
a time in the past.
Action: Choose a time in the future instead.
ORA-09870 to ORA-12100 64-41
ORA-12007: materialized view reuse parameters are inconsistent

Cause: The CREATE MATERIALIZED VIEW .. or CREATE MATERIALIZED VIEW
LOG .. REUSE command was given inconsistent parameters immediately after the
REUSE.
Action: Examine the other messages on the stack to find the problem.
ORA-12008: error in materialized view refresh path
Cause: Table SNAP$_<mview_name> reads rows from the view MVIEW
$_<mview_name>, which is a view on the master table (the master may be at a
remote site). Any error in this path will cause this error at refresh time. For fast
refreshes, the table <master_owner>.MLOG$_master is also referenced.
Action: Examine the other messages on the stack to find the problem. See if the objects
SNAP$_<mview_name>, MVIEW$_<mview_name>, mowner.master@dblink,
mowner.MLOG$_master@dblink still exist.
ORA-12009: materialized views may not contain long columns
ORA-12010: cannot create materialized view log on table owned by SYS
Cause: An attempt was made to create a materialized view log on the table owned by
SYS. CREATE MATERIALIZED VIEW LOG attempts to create a trigger on the table,
but triggers can not be created on SYS tables.
Action: Do not create a materialized view log on SYS tables.
ORA-12011: execution of string jobs failed
Cause: An error was caught in dbms_ijob.run from one or more jobs which were due
to be run.
Action: Look at the alert log for details on which jobs failed and why.
ORA-12012: error on auto execute of job string
Cause: An error was caught while doing an automatic execution of a job.
Action: Look at the accompanying errors for details on why the execute failed.
ORA-12013: updatable materialized view must be simple enough and have a
materialized view log on its master table to do fast refresh
Cause: The updatable materialized view query contained a JOIN, SUBQUERY,
UNION, CONNECT BY, ORDER BY, or GROUP BY clause, or the master table did
not have a materialized view log.
Action: Make the materialized view simpler. If a join is really needed, make multiple
simple materialized views then put a view on top of them. Make sure a materialized
view log is created for the master table.
ORA-12014: table 'string' does not contain a primary key constraint
Cause: The CREATE MATERIALIZED VIEW LOG command was issued with the
WITH PRIMARY KEY option and the master table did not contain a primary key
constraint or the constraint was disabled.
Action: Reissue the command using only the WITH ROWID option, create a primary
key constraint on the master table, or enable an existing primary key constraint.
ORA-12015: cannot create a fast refresh materialized view from a complex query
Cause: Neither ROWIDs and nor primary key constraints are supported for complex
queries.
Action: Reissue the command with the REFRESH FORCE or REFRESH COMPLETE
option or create a simple materialized view.
ORA-12016: materialized view does not include all primary key columns
Cause: The query that instantiates the materialized view did not include all of the
columns in the master's primary key constraint.
Action: Include all of the master's primary key columns in the materialized view
query or create a ROWID materialized view.
ORA-12017: cannot alter primary key mview 'string' to a rowid mview
Cause: An attempt was made to convert the primary key of a materialized view to a
ROWID materialized view.
Action: Conversion of a primary key materialized view to a ROWID materialized
view is not supported. Create a new materialized view with ROWIDs or drop and
recreate the materialized view with ROWIDs.
ORA-12018: following error encountered during code generation for
"string"."string"
Cause: The refresh operations for the indicated materialized view could not be
regenerated due to errors.
Action: Correct the problem indicated in the following error messages and repeat the
operation.
ORA-12019: master table is a synonym to a remote object
Cause: An attempt was made to create a materialized view or a materialized view log
on a remote synonym which is unsupported.
Action: Do not create a materialized view or materialized view log on a remote
synonym.
ORA-12020: materialized view string is not registered
Cause: An attempt was made to unregister a materialized view that is not registered.
ORA-12021: materialized view "string"."string" is corrupt
Cause: The materialized view indicated is no longer valid.
ORA-12022: materialized view log on "string"."string" already has rowid
Cause: Materialized view log on the indicated table already has ROWID information.
ORA-12023: missing index on materialized view "string"."string"
Cause: The specified ROWID materialized view did not have the required index on
the ROWID column of its underlying table.
Action: Drop and recreate the materialized view.
ORA-12024: materialized view log on "string"."string" does not have primary key
columns
Cause: Materialized view log on the indicated table does not have primary key
information.
Action: Add primary keys to the materialized view log using the ALTER
MATERIALIZED VIEW command.
ORA-09870 to ORA-12100 64-43
ORA-12025: materialized view log on "string"."string" already has primary keys

Cause: Materialized view log on the indicated table already has primary key columns.
ORA-12026: invalid filter column detected
Cause: One or more of the specified filter columns did not exist or was a primary key
column or a primary key based object identifier.
Action: Ensure that all specified filter columns exist in the master table and ensure
that primary key columns or primary key based object identifiers are not included in
the list of filter columns.
ORA-12027: duplicate filter column
Cause: One or more of the specified filter columns were already being recorded in the
materialized view log.
Action: Describe the materialized view log table and reissue the SQL command with
the filter columns that are already being recorded in the materialized view log.
ORA-12028: materialized view type is not supported by master site string
Cause: Pre-Oracle8 master sites are not able to support primary key or subquery
materialized views that are able to perform a fast refresh.
Action: Create a ROWID materialized view or use a master table from an Oracle8 site.
ORA-12029: LOB columns may not be used as filter columns
Cause: An attempt was made to use LOB columns as filter columns.
Action: Remove LOB columns from the filter columns list and retry command.
ORA-12030: cannot create a fast refresh materialized view
Cause: The materialized view log did not exist or did not log the information needed
by the materialized view to perform a fast refresh.
Action: Ensure that the materialized view log exists and logs the necessary
information. - For ROWID materialized views, the master table's ROWID must be
logged. - For primary key materialized views, the master table's primary key columns
must be logged. - For subquery materialized views, the filter columns, primary key,
and ROWID values must be logged. - For object materialized views, object id must be
logged.
ORA-12031: cannot use primary key columns from materialized view log on
"string"."string"
Cause: The materialized view log either did not have primary key columns logged, or
the timestamp associated with the primary key columns was more recent than the last
refresh time.
Action: A complete refresh is required before the next fast refresh. Add primary key
columns to the materialized view log, if required.
ORA-12032: cannot use rowid column from materialized view log on
"string"."string"
Cause: The materialized view log either does not have ROWID columns logged, or
the timestamp associated with the ROWID columns is more recent than the last
refresh time.
Action: A complete refresh is required before the next fast refresh. Add ROWID
columns to the materialized view log, if required.
ORA-12033: cannot use filter columns from materialized view log on

"string"."string"
Cause: The materialized view log either did not have filter columns logged, or the
timestamp associated with the filter columns was more recent than the last refresh
time.
Action: A complete refresh is required before the next fast refresh. Add filter columns
to the materialized view log, if required.
ORA-12034: materialized view log on "string"."string" younger than last refresh
Cause: The materialized view log was younger than the last refresh.
Action: A complete refresh is required before the next fast refresh.
ORA-12035: could not use materialized view log on "string"."string"
Cause: The materialized view log did not exist or could not be used.
Action: Use just REFRESH, which will reinstantiate the entire table. If a materialized
view log exists and the form of the materialized view allows the use of a materialized
view log, REFRESH FAST will be available starting the next time the materialized
view is refreshed.
ORA-12036: updatable materialized view log is not empty, refresh materialized
view
Cause: The updatable materialized view log was not empty. The updatable
materialized view log must be empty before an updatable rowid materialized view
can be altered to a primary key materialized view.
Action: Ensure that updatable materialized view log is empty by refreshing the
materialized view before converting the updatable ROWID materialized view to a
primary key materialized view.
ORA-12037: unknown export format
Cause: An attempt was made to import a materialized view exported by an unknown
export version (e.g., from a newer release than the importing site)
Action: Re-export the file using a version of export known by the importing site.
ORA-12038: string literal has unexpected length
ORA-12039: unable to use local rollback segment "string"
Cause: A local rollback segment was specified in the CREATE MATERIALIZED
VIEW command, but automatic refresh parameters were not specified. Therefore a
refresh group was not created to automatically refresh the materialized view and the
local rollback segment can't be registered for future use.
Action: Either supply the automatic refresh parameters so that a refresh group will be
created or do not specify a local rollback segment.
ORA-12040: master rollback segment option not support by master site string
Cause: An attempt was made to specify master rollback segment in the current
operation. The master site of the current materialized view does not allow users to
specify a rollback segment to be used for materialized view operations. This feature is
only supported by Oracle8 or later master sites.
Action: Do not specify a master rollback segment in the current operation or choose a
new master site.
ORA-09870 to ORA-12100 64-45
ORA-12041: cannot record ROWIDs for index-organized table "string"."string"

Cause: Index-organized tables do not have ROWIDs. Therefore a materialized view
log that records the ROWIDs of an index-organized table could not be created.
Action: Do not include the WITH ROWID option when using the CREATE
MATERIALIZED VIEW command and do not include the ADD ROWID option when
using the ALTER MATERIALIZED VIEW command if the master table is indexorganized.
ORA-12042: cannot alter job_queue_processes in single process mode
Cause: An attempt was made to alter job_queue_processes in single process mode.
Action: Do not attempt to set job_queue_processes in single process mode.
ORA-12043: invalid CREATE MATERIALIZED VIEW option
Cause: An invalid option was used in a CREATE MATERIALIZED VIEW statement.
ORA-12044: invalid CREATE MATERIALIZED VIEW LOG option
Cause: An invalid option was used in a CREATE MATERIALIZED VIEW LOG
statement.
ORA-12045: invalid ALTER MATERIALIZED VIEW LOG option
Cause: An invalid option was used in an ALTER MATERIALIZED VIEW LOG
statement.
ORA-12046: cannot use trusted constraints for refreshing remote MV
Cause: REFRESH USING TRUSTED CONSTRAINTS specified in ALTER
MATERIALIZED VIEW or CREATE MATERIALIZED VIEW of a remote materialized
view
Action: remove this attribute from ALTER/ CREATE MATERIALIZED VIEW DDL
ORA-12047: PCT FAST REFRESH cannot be used for materialized view
"string"."string"
Cause: PCT refresh is either not enabled on this materialized view or not possible
after set of the base table changes since last refresh.
Action: Use just REFRESH FORCE, which will reinstantiate the entire table and try to
pick the best refresh method on the materialized view Do explain_mview to look at
the cause why PCT refresh is not possible on this materialized view
ORA-12048: error encountered while refreshing materialized view "string"."string"
Cause: Some problem occurs during refresh of multiple materialized views in atomic
mode. The materialized view whose refresh failed has raised this error.
Action: Examine the other messages on the stack to find the refresh problem.
ORA-12051: ON COMMIT attribute is incompatible with other options
Cause: ON COMMIT refresh attribute, incompatible with other refresh options such
as automatic periodic refresh, was specified.
ORA-12052: cannot fast refresh materialized view string.string

Cause: Either ROWIDs of certain tables were missing in the definition or the inner
table of an outer join did not have UNIQUE constraints on join columns.
Action: Specify the FORCE or COMPLETE option. If this error is got during creation,
the materialized view definition may have be changed. Refer to the documentation on
materialized views.
ORA-12053: this is not a valid nested materialized view
Cause: The list of objects in the FROM clause of the definition of this materialized
view had some dependencies upon each other.
Action: Refer to the documentation to see which types of nesting are valid.
ORA-12054: cannot set the ON COMMIT refresh attribute for the materialized
view
Cause: The materialized view did not satisfy conditions for refresh at commit time.
ORA-12055: materialized view definition contains cyclic dependencies with
existing materialized views
Cause: The materialized view query definition introduced a cyclic dependency with
existing materialized view.
Action: Modify the materialized view query definition.
ORA-12056: invalid REFRESH method
Cause: The NEVER REFRESH option may not be used under the following
conditions: * The materialized view is updatable * The materialized view refreshes
ON COMMIT * Automatic refresh options are specified
Action: For updatable materialized views, reissue the SQL command using REFRESH
FORCE, REFRESH FAST, or REFRESH COMPLETE. For read-only materialized
views, reissue the SQL command using ON DEMAND.
ORA-12057: materialized view or zonemap "string"."string" is invalid and must use
complete refresh
Cause: The status of the materialized view or zonemap was invalid and an attempt
was made to fast refresh it.
Action: Perform a complete refresh of the materialized view or zonemap.
ORA-12058: materialized view cannot use prebuilt table
Cause: An attempt was made to use the prebuilt tables.
Action: Reissue the SQL command using BUILD IMMEDIATE or BUILD DEFERRED.
ORA-12059: prebuilt table "string"."string" does not exist
Cause: The specified prebuilt table did not exist.
Action: Reissue the SQL command using BUILD IMMEDIATE, BUILD DEFERRED,
or ensure that the prebuilt table exists.
ORA-12060: shape of prebuilt table does not match definition query
Cause: The number of columns or the type or the length semantics of a column in the
prebuilt table did not match the materialized view definition query.
Action: Reissue the SQL command using BUILD IMMEDIATE, BUILD DEFERRED,
or ensure that the prebuilt table matches the materialized view definition query.
ORA-09870 to ORA-12100 64-47
ORA-12061: invalid ALTER MATERIALIZED VIEW option

Cause: An invalid option was used in an ALTER MATERIALIZED VIEW statement.
ORA-12062: transaction string received out of sequence from site string
Cause: A transaction from the client site was received out of sequence. This implies
that one or more transactions were missing.
Action: Ensure that the transaction queue at the client site is valid and has not been
corrupted.
ORA-12063: unable to apply transaction from site string
Cause: The current transaction from the client site could not be applied to the master
site.
Action: Ensure that the client site is still valid and that it has not been dropped from
the master site.
ORA-12064: invalid refresh sequence number: string
Cause: The client site was attempting to perform a refresh with an invalid refresh
sequence.
Action: Perform a complete refresh to synchronize the refresh sequence number.
ORA-12065: unknown refresh group identifier string
Cause: The specified refresh group did not exist at the master site.
Action: Ensure that the client site is still valid and that it has not been dropped from
the master site.
ORA-12066: invalid CREATE MATERIALIZED VIEW command
Cause: The Replication API does not support the following options and types of
materialized view: o ROWID materialized views o REFRESH ON COMMIT o ON
PREBUILT TABLE o BUILD DEFERRED o NEVER REFRESH o ENABLE QUERY
REWRITE
Action: Create a PRIMARY KEY materialized view using REFRESH WITH PRIMARY
KEY and/or remove the invalid options.
ORA-12067: empty refresh groups are not allowed
Cause: The refresh group being instantiated did not contain any materialized views.
Action: Modify the template to include at least one materialized view.
ORA-12068: updatable mview log for mview "string"."string" does not exist
Cause: The updatable materialized view was missing the updatable materialized view
log required to track updates made to the materialized view.
Action: Create the updatable materialized view log.
ORA-12069: invalid object for offline instantiation
Cause: Only materialized views can be offline instantiated. The object being offline
instantiated was not a valid materialized view.
Action: Remove the object from the template or replace the object with a valid
materialized view.
ORA-12070: cannot offline instantiate materialized view "string"."string"

Cause: Offline instantiation does not support materialized views using the following
options: o ON PREBUILT TABLE o BUILD DEFERRED
Action: Remove the invalid options.
ORA-12071: definition query of "string"."string" is invalid for offline instantiation
Cause: Offline instantiation requires materialized view definition queries to observe
the following constraints: o The database link that will be used by the materialized
view site to connect to the master site must be included with each master table
referenced in the query. o All master tables referenced must be located at the local
site. References to other sites are not allowed.
Action: Modify the materialized view definition query.
ORA-12072: updatable materialized view log data for "string"."string" cannot be
created
Cause: The updatable materialized view was missing the updatable materialized view
log required to track updates made to the materialized view.
Action: Create an updatable materialized view log.
ORA-12073: request cannot be processed
Cause: An out-of-sequence request was made and it cannot be processed.
Action: Try again with a valid request.
ORA-12074: invalid memory address
Cause: An attempt was made to access an invalid memory region.
Action: Reconnect and try the command again.
ORA-12075: invalid object or field
Cause: An attempt was made to access an invalid field or object in the Java Virtual
Memory.
Action: Retry the request.
ORA-12076: invalid threshold value
Cause: The result set threshold or LOB threshold value is not supported.
Action: Specify a threshold value below 64K.
ORA-12077: temporary updatable materialized view log does not exist
Cause: Temporary updatable materialized view log was not created or was dropped.
Action: Re-create the temporary updatable materialized view log. Warning: This will
cause a complete refresh of the materialized view.
ORA-12078: fast refresh of refresh group ID string failed
Cause: Refresh result set sent through client method REFRESH_REQ_RESULT
returned an unknown value.
Action: Re-issue the refresh request.
ORA-12079: do not invalidate result cache created during materialized view refresh
Cause: Result cache created during materialized view refresh was not invalidated at
end.
Action: Do not set this as an event.
ORA-09870 to ORA-12100 64-49
ORA-12080: Buffer cache miss for IOQ batching

ORA-12081: update operation not allowed on table "string"."string"
Cause: An attempt was made to update a read-only materialized view.
Action: No action required. Only Oracle is allowed to update a read-only materialized
view.
ORA-12082: "string"."string" cannot be index organized
Cause: An attempt was made to create an index-organized materialized aggregate
view or an index-organized updatable ROWID materialized view. This is not
supported.
Action: Try to create the materialized view without the index organization clause.
ORA-12083: must use DROP MATERIALIZED VIEW to drop "string"."string"
Cause: An attempt was made to drop a materialized view using a command other
than DROP MATERIALIZED VIEW.
Action: Use the DROP MATERIALIZED VIEW command.
ORA-12084: must use ALTER MATERIALIZED VIEW to alter "string"."string"
Cause: An attempt was made to alter a materialized view using a command other
than ALTER MATERIALIZED VIEW.
Action: Use the ALTER MATERIALIZED VIEW command.
ORA-12085: materialized view log on "string"."string" already has object id
Cause: Materialized view log on the indicated table already has object id information.
ORA-12086: table "string"."string" is not an object table
Cause: The CREATE MATERIALIZED VIEW LOG command was issued with the
WITH OBJECT ID option and the master table is not an object table.
Action: Either specify the name of an object table, or remove the WITH OBJECT ID
clause.
ORA-12087: online redefinition not allowed on tables owned by "string"
Cause: An attempt was made to online redefine a table owned by SYS or SYSTEM.
Action: Do not attempt to online redefine a table owned by SYS or SYSTEM.
ORA-12088: cannot online redefine table "string"."string" with unsupported
datatype
Cause: An attempt was made to online redefine a table containing a LONG column,
an ADT column, or a FILE column.
Action: Do not attempt to online redefine a table containing a LONG column, an ADT
column, or a FILE column.
ORA-12089: cannot online redefine table "string"."string" with no primary key
Cause: An attempt was made to online redefine a table that does not have a primary
key defined on it.
Action: Do not attempt to online redefine a table that does not have a primary key
defined on it.
ORA-12090: cannot online redefine table "string"."string"

Cause: An attempt was made to online redefine a table that is either a temporary
table, an IOT overflow table, a table with fine-grained access control or row-level
security enabled, a CDC change table, or a table with a CDC change table defined on
it.
Action: Do not attempt to online redefine a table that is not supported by online
redefinition.
ORA-12091: cannot online redefine table "string"."string" with materialized views
Cause: An attempt was made to online redefine a table that had materialized views
defined on it or had a materialized view log defined on it or is a master.
Action: Drop all materialized views and materialized view logs before attempting to
online redefine the table.
ORA-12092: cannot online redefine replicated table "string"."string"
Cause: An attempt was made to online redefine a table that is either a materialized
view or a replicated table.
Action: Do not attempt to online redefine a table that is either a materialized view or a
replicated table.
ORA-12093: invalid interim table "string"."string"
Cause: The table is not the interim table of the corresponding table to be online
redefined.
Action: Pass in the valid interim table.
ORA-12094: error during online redefinition
Cause: There was an error during the online redefinition process.
Action: Abort the online redefinition process.
ORA-12096: error in materialized view log on "string"."string"
Cause: There was an error originating from this materialized view log. One possible
cause is that schema redefinition has occurred on the master table and one or more
columns in the log is now a different type than corresponding master column(s).
Another possible cause is that there is a problem accessing the underlying
materialized view log table.
Action: Check further error messages in stack for more detail about the cause. If there
has been schema redefinition, drop the materialized view log and recreate it.
ORA-12097: changes in the master tables during refresh, try refresh again
Cause: There are some changes (i.e., conventional DML, direct load, partition
maintenance operation) in the master tables during materialized view refresh.
Action: Refresh the affected materialized views again.
ORA-12098: cannot comment on the materialized view
Cause: An attempt was made to issue a COMMENT ON TABLE statement on a
materialized view.
Action: Issue a COMMENT ON MATERIALIZED VIEW statement instead.
ORA-12099: Don't go into fast table scan (kdst) mode
ORA-12100: materialized view log on "string"."string" already has sequence
Cause: Materialized view log on the indicated table already has sequence information.
ORA-09870 to ORA-12100 64-51
65
ORA-12150 to ORA-12236
ORA-12150: TNS:unable to send data
Cause: Unable to send data. Connection probably disconnected.
Action: Reestablish connection. If the error is persistent, turn on tracing and reexecute
the operation.
ORA-12151: TNS:received bad packet type from network layer
Action: Not normally visible to the user. For further details, turn on tracing and
reexecute the operation. If error persists, contact Worldwide Customer Support.
ORA-12152: TNS:unable to send break message
Cause: Unable to send break message. Connection probably disconnected.
Action: Reestablish connection. If the error is persistent, turn on tracing and reexecute
the operation.
ORA-12153: TNS:not connected
Cause: Not currently connected to a remote host.
Action: Reestablish connection.
ORA-12154: TNS:could not resolve the connect identifier specified
Cause: A connection to a database or other service was requested using a connect
identifier, and the connect identifier specified could not be resolved into a connect
descriptor using one of the naming methods configured. For example, if the type of
connect identifier used was a net service name then the net service name could not be
found in a naming method repository, or the repository could not be located or
reached.
Action: - If you are using local naming (TNSNAMES.ORA file): - Make sure that
"TNSNAMES" is listed as one of the values of the NAMES.DIRECTORY_PATH
parameter in the Oracle Net profile (SQLNET.ORA) - Verify that a TNSNAMES.ORA
file exists and is in the proper directory and is accessible. - Check that the net service
name used as the connect identifier exists in the TNSNAMES.ORA file. - Make sure
there are no syntax errors anywhere in the TNSNAMES.ORA file. Look for
unmatched parentheses or stray characters. Errors in a TNSNAMES.ORA file may
make it unusable. - If you are using directory naming: - Verify that "LDAP" is listed as
one of the values of the NAMES.DIRETORY_PATH parameter in the Oracle Net
profile (SQLNET.ORA). - Verify that the LDAP directory server is up and that it is
accessible. - Verify that the net service name or database name used as the connect
identifier is configured in the directory. - Verify that the default context being used is
correct by specifying a fully qualified net service name or a full LDAP DN as the
connect identifier - If you are using easy connect naming: - Verify that
"EZCONNECT" is listed as one of the values of the NAMES.DIRETORY_PATH
ORA-12150 to ORA-12236 65-1
parameter in the Oracle Net profile (SQLNET.ORA). - Make sure the host, port and
service name specified are correct. - Try enclosing the connect identifier in quote
marks. See the Oracle Net Services Administrators Guide or the Oracle operating
system specific guide for more information on naming.
ORA-12155: TNS:received bad datatype in NSWMARKER packet
Cause: Internal error during break handling.
ORA-12156: TNS:tried to reset line from incorrect state
Cause: Internal error during break handling.
ORA-12157: TNS:internal network communication error
Cause: Internal error during network communication.
ORA-12158: TNS:could not initialize parameter subsystem
Cause: Unable to locate parameter file.
Action: Verify that a valid parameter file exists, and is readable.
ORA-12159: TNS:trace file not writeable
Cause: The trace file to be generated is not writeable by this user.
Action: If the user does not have write permissions in the directory to which the trace
file will be written, contact an administrator to get the proper permissions or set the
TRACE_DIRECTORY_CLIENT parameter in the net profile (SQLNET.ORA file) to a
directory the user can write to.
ORA-12160: TNS:internal error: Bad error number
Cause: Corrupt error reporting subsystem.
ORA-12161: TNS:internal error: partial data received
Cause: The connection may be terminated.
Action: Reconnect and try again. For further details, turn on tracing and reexecute the
operation. If error persists, contact Worldwide Customer Support.
ORA-12162: TNS:net service name is incorrectly specified
Cause: The connect descriptor corresponding to the net service name in
TNSNAMES.ORA or in the directory server (Oracle Internet Directory) is incorrectly
specified.
Action: If using local naming make sure there are no syntax errors in the
corresponding connect descriptor in the TNSNAMES.ORA file. If using directory
naming check the information provided through the administration used for
directory naming.
65-2 Error Messages
ORA-12163: TNS:connect descriptor is too long

Cause: The connect descriptor corresponding to the net service name specified as the
connect identifier is too long. The maximum length for a connect descriptor is 512
bytes and this limit has been exceeded.
Action: Check the net service name's connect descriptor in the local naming file
(TNSNAMES.ORA) or in the directory server (Oracle Internet Directory). Use a
smaller connect descriptor. If this is not possible, contact Worldwide Customer
Support.
ORA-12164: TNS:Sqlnet.fdf file not present
Cause: The sqlnet.fdf file doesn't exist in $ORACLE_HOME/network/admin.
Action: The sqlnet.fdf file is required for Oracle Tracing to occur. Either install the
sqlnet.fdf file in $ORACLE_HOME/network/admin or turn off tracing in your ORA
file.
ORA-12165: TNS:Trying to write trace file into swap space.
Cause: Oracle Trace doesn't allow writing trace information into your swap space.
Action: Oracle Trace cannot write trace information into swap space so either disable
tracing or redirect trace files to be written to another area of your disk.
ORA-12166: TNS:Client can not connect to HO agent.
Cause: NVstring contained DESCRIPTION/HO.
Action: Call HO agent from integrating server.
ORA-12168: TNS:Unable to contact LDAP Directory Server
Cause: Cannot contact LDAP directory server to get Oracle Net configuration.
Action: Verify that the directory server is up and accessible from the network. Verify
that directory access configuration is correct. For more information see the Oracle
Internet Directory Administrators Guide or the Oracle Net Administrators Guide.
ORA-12169: TNS:Net service name given as connect identifier is too long
Cause: The net service name you are attempting to resolve is too long.
Action: The maximum length of a net service name is 255 bytes; this limit has been
exceeded. Use a smaller net service name. If this is not possible, contact Worldwide
Customer Support.
ORA-12170: TNS:Connect timeout occurred
Cause: The server shut down because connection establishment or communication
with a client failed to complete within the allotted time interval. This may be a result
of network or system delays; or this may indicate that a malicious client is trying to
cause a Denial of Service attack on the server.
Action: If the error occurred because of a slow network or system, reconfigure one or
all of the parameters SQLNET.INBOUND_CONNECT_TIMEOUT,
SQLNET.SEND_TIMEOUT, SQLNET.RECV_TIMEOUT in sqlnet.ora to larger values.
If a malicious client is suspected, use the address in sqlnet.log to identify the source
and restrict access. Note that logged addresses may not be reliable as they can be
forged (e.g. in TCP/IP).
ORA-12171: TNS:could not resolve connect identifier: string
Cause: A connection to a database or other service was requested using a connect
identifier, and the connect identifier specified could not be resolved into a connect
descriptor using one of the naming methods configured. For example, if the type of
ORA-12150 to ORA-12236 65-3
connect identifier used was a net service name then the net service name could not be
found in a naming method repository, or the repository could not be located or
reached.
Action: - If you are using local naming (TNSNAMES.ORA file): - Make sure that
"TNSNAMES" is listed as one of the values of the NAMES.DIRECTORY_PATH
parameter in the Oracle Net profile (SQLNET.ORA) - Verify that a TNSNAMES.ORA
file exists and is in the proper directory and is accessible. - Check that the net service
name used as the connect identifier exists in the TNSNAMES.ORA file. - Make sure
there are no syntax errors anywhere in the TNSNAMES.ORA file. Look for
unmatched parentheses or stray characters. Errors in a TNSNAMES.ORA file may
make it unusable. - If you are using directory naming: - Verify that "LDAP" is listed as
one of the values of the NAMES.DIRETORY_PATH parameter in the Oracle Net
profile (SQLNET.ORA). - Verify that the LDAP directory server is up and that it is
accessible. - Verify that the net service name or database name used as the connect
identifier is configured in the directory. - Verify that the default context being used is
correct by specifying a fully qualified net service name or a full LDAP DN as the
connect identifier - If you are using easy connect naming: - Verify that
"EZCONNECT" is listed as one of the values of the NAMES.DIRETORY_PATH
parameter in the Oracle Net profile (SQLNET.ORA). - Make sure the host, port and
service name specified are correct. - Try enclosing the connect identifier in quote
marks. See the Oracle Net Services Administrators Guide or the Oracle operating
system specific guide for more information on naming.
ORA-12196: TNS:received an error from TNS
Cause: The navigation layer received an error from TNS.
Action: See the error log file for the specific TNS error.
ORA-12197: TNS:keyword-value resolution error
Cause: The navigation layer received an error while trying to look up a value for a
keyword.
Action: Check the syntax of the connect descriptor.
ORA-12198: TNS:could not find path to destination
Cause: Could not navigate a path through Interchanges to the destination. This error
occurs if an invalid community is in the address string, or the address includes a
protocol that is not available or the TNSNAV.ORA file does not have a correct
CMANAGER address specified or the Interchange is down.
Action: Assure that Interchanges necessary to get to the desired destination are up
and have available capacity for an additional connection. Also check that the correct
community and protocol have been specified in the CMANAGER address used.
ORA-12200: TNS:could not allocate memory
Cause: Out of memory on machine.
Action: Reconfigure machine to have more storage or run fewer applications while
the Interchange is running.
ORA-12201: TNS:encountered too small a connection buffer
Cause: TNS connection buffer supplied by the application was too small to retrieve
the data sent back.
Action: Supply a larger connection buffer. If problem persists, call Worldwide
Customer Support.
65-4 Error Messages
ORA-12202: TNS:internal navigation error

Cause: Internal navigation error.
Action: Not normally visible to the user. For further details contact Worldwide
Customer Support.
ORA-12203: TNS:unable to connect to destination
Cause: Invalid address specified or destination is not listening. This error can also
occur because of underlying network or network transport problems.
Action: Verify that the net service name you entered was correct. Verify that the
ADDRESS portion of the connect descriptor which corresponds to the net service
name is correct. Ensure that the destination process (for example the listener) is
running at the remote node.
ORA-12204: TNS:received data refused from an application
Cause: The application using Connection Manager refused the connection at the
listener.
Action: Make sure that the application listener at the destination is functioning
correctly. If it is and the problem persists, contact Worldwide Customer Support.
ORA-12205: TNS:could not get failed addresses
Cause: Internal navigation error.
Action: Not normally visible to the user. For further details contact Worldwide
Customer Support.
ORA-12206: TNS:received a TNS error during navigation
Cause: Internal navigation error because of an unexpected TNS error.
Action: Look at the log file to find the TNS error. If necessary, turn on tracing and
repeat the operation.
ORA-12207: TNS:unable to perform navigation
Cause: Improperly configured navigation file TNSNAV.ORA.
Action: Check the syntax of the TNSNAV.ORA file on the application`s machine, and
verify that it lists the correct communities.
ORA-12208: TNS:could not find the TNSNAV.ORA file
Cause: Either the ORACLE environment is not set up correctly, or the TNSNAV.ORA
file is not present.
Action: Ensure that the ORACLE environment is set up appropriately on your
platform and that a TNSNAV.ORA file is present.
ORA-12209: TNS:encountered uninitialized global
Cause: Application calling navigation routine has not properly configured the global
variables. There are no TNSNAV.ORA files available, or they are defective.
ORA-12210: TNS:error in finding Navigator data
Cause: Application calling navigation routine has not properly configured the
TNSNAV.ORA file.
Action: Check the syntax of the TNSNAV.ORA file.
ORA-12150 to ORA-12236 65-5
ORA-12211: TNS:needs PREFERRED_CMANAGERS entry in TNSNAV.ORA

Cause: TNSNAV.ORA does not have a PREFERRED_CMANAGERS defined.
Action: Add a PREFERRED_CMANAGERS entry to the TNSNAV.ORA file.
ORA-12212: TNS:incomplete PREFERRED_CMANAGERS binding in
TNSNAV.ORA
Cause: The PREFERRED_CMANAGERS binding in the client's TNSNAV.ORA file
does not have a CMANAGER_NAME specified.
Action: Define the CMANAGER_NAME as part of the PREFERRED_CMANAGERS
binding. Use of the Oracle Network Manager should eliminate this error.
ORA-12213: TNS:incomplete PREFERRED_CMANAGERS binding in
TNSNAV.ORA
Cause: The PREFERRED_CMANAGERS binding in the client's TNSNAV.ORA file
does not have an ADDRESS specified.
Action: Define the ADDRESS as part of the PREFERRED_CMANAGERS binding.
ORA-12214: TNS:missing local communities entry in TNSNAV.ORA
Cause: There is no LOCAL_COMMUNITIES entry in TNSNAV.ORA.
Action: Define the LOCAL_COMMUNITIES for this node in the TNSNAV.ORA file.
ORA-12215: TNS:poorly formed PREFERRED_NAVIGATORS Addresses in
TNSNAV.ORA
Cause: Address binding for PREFERRED_NAVIGATORS entry is improperly
entered. entry.
Action: Check your PREFERRED_NAVIGATORS entry and fix it in TNSNAV.ORA
ORA-12216: TNS:poorly formed PREFERRED_CMANAGERS addresses in
TNSNAV.ORA
Cause: Address binding for the PREFERRED_CMANAGERS entry in the client's
TNSNAV.ORA file is improperly entered.
Action: Define the ADDRESS as part of the PREFERRED_CMANAGERS binding.
ORA-12217: TNS:could not contact PREFERRED_CMANAGERS in TNSNAV.ORA
Cause: There is a syntax error in the PREFERRED_CMANAGERS entry, or addresses
specified are wrong, or the intended Connection Managers are unavailable.
Action: Check the PREFERRED_CMANAGERS entries in the client's TNSNAV.ORA
file and correct them or talk with your network administrator to determine if the
specified Connection Managers are available. Verify that the Interchanges are active
by using the INTCTL STATUS command.
ORA-12218: TNS:unacceptable network configuration data
Cause: Poorly formed network configuration data. For example, a
PREFERRED_CMANAGERS entry may have an incorrect CMANAGER_NAME in
the client's TNSNAV.ORA file. Or an Interchange downtime parameter
(TIMEOUT_INTERVAL) on the Navigator may be set to zero in INTCHG.ORA.
Action: Check the entries in TNSNAV.ORA and the Interchange configuration files
and correct them. If necessary, talk with your network administrator to determine if
the specified Interchanges (Connection Managers) are available and properly
configured. Use the Oracle Network Manager to generate the configuration files if
necessary.
65-6 Error Messages
ORA-12219: TNS:missing community name from address in ADDRESS_LIST

Cause: This error occurs when an ADDRESS_LIST has some ADDRESSes in it that
have no COMMUNITY component and others that do have a COMMUNITY
component.
Action: Check that in the connect descriptors you are using either all the ADDRESSes
have a COMMUNITY component or all do not.
ORA-12221: TNS:illegal ADDRESS parameters
Cause: An illegal set of protocol adapter parameters was specified. In some cases, this
error is returned when a connection cannot be made to the protocol transport.
Action: Verify that the destination can be reached using the specified protocol. Check
the parameters within the ADDRESS section of TNSNAMES.ORA or in the directory.
Legal ADDRESS parameter formats may be found in the Oracle operating system
specific documentation or the Oracle Net Administrator's Guide. Protocols that
resolve names at the transport layer are vulnerable to this error if not properly
configured or names are misspelled.
ORA-12222: TNS:no support is available for the protocol indicated
Cause: The protocol requested in the ADDRESS portion of the connect descriptor
identified through the net service name is not available. If the supplied ADDRESS is
typographically correct then support for that protocol is not installed.
Action: Install support for the protocol or correct typographical error, as appropriate.
Note: if the supplied address was derived from resolving the net service name, check
the address in the appropriate file (TNSNAMES.ORA, LISTENER.ORA) or in the
directory server.
ORA-12223: TNS:internal limit restriction exceeded
Cause: Too many TNS connections open simultaneously.
Action: Wait for connections to close and re-try.
ORA-12224: TNS:no listener
Cause: The connection request could not be completed because the listener is not
running.
Action: Ensure that the supplied destination address matches one of the addresses
used by the listener - compare the TNSNAMES.ORA entry with the appropriate
LISTENER.ORA file (or TNSNAV.ORA if the connection is to go by way of an
Interchange). Start the listener on the remote machine.
ORA-12225: TNS:destination host unreachable
Cause: Contact can not be made with remote party.
Action: Make sure the network driver is functioning and the network is up.
ORA-12226: TNS:operating system resource quota exceeded
Cause: The current user has exceeded the allotted resource assigned in the operating
system.
Action: Acquire more operating system resource, or perform a different function.
ORA-12227: TNS:syntax error
Cause: The supplied connect descriptor contains illegal syntax.
Action: Check the syntax of the connect descriptor in TNSNAMES.ORA.
ORA-12150 to ORA-12236 65-7
ORA-12228: TNS:protocol adapter not loadable

Cause: On some platforms (such as Windows) protocol support is loaded at run-time.
If the shared library (or DLL) for the protocol adapter is missing or one of its
supporting libraries is missing then this error is returned.
Action: For further details, turn on tracing and reexecute the operation. The trace file
will include the name of the shared library (or DLL) that could not be loaded.
ORA-12229: TNS:Interchange has no more free connections
Cause: One or more Interchanges along the path to the destination desired has no
more free connections available to be used for this call.
Action: Try again later when the Interchanges are less busy, or contact your network
administrator to have him determine which interchange it is, and increase the number
of connections available on that interchange.
ORA-12230: TNS:Severe Network error occurred in making this connection
Cause: This error is reported by an interchange which fails to make contact with the
destination due to a physical network error while calling a destination.
Action: Try again later when the network service may have been fixed or report the
problem to your Network Administrator so that he may fix the problem.
ORA-12231: TNS:No connection possible to destination
Cause: This error is reported by an interchange which fails to find a possible
connection along the path to the destination.
Action: Report the problem to your Network Administrator so that he may fix the
problem.
ORA-12232: TNS:No path available to destination
Cause: This error is reported by an interchange which fails to find a possible path to
the destination.
problem.
ORA-12233: TNS:Failure to accept a connection
Cause: This error is reported by an interchange which fails to accept a connection due
to a redirect failure.
Action: Report the problem to your Network Administrator so that he may isolate the
interchange problem.
ORA-12234: TNS:Redirect to destination
Cause: This error is reported by an interchange which determines that this
interchange is not the right gateway and needs to redirect the connection to another
gateway along the path to the destination.
Action: None
ORA-12235: TNS:Failure to redirect to destination
Cause: This error is reported by an interchange which fails to redirect a connection to
another interchange along the path to the destination.
problem.
65-8 Error Messages
ORA-12236: TNS:protocol support not loaded

Cause: On some platforms (such as Windows) protocol support is loaded at run-time.
If the shared library (or DLL) for the protocol adapter has not been loaded, then this
error is returned.
will have the name of the shared library (or DLL) that has not been loaded.
ORA-12150 to ORA-12236 65-9
66
ORA-12315 to ORA-12354
ORA-12315: database link type is invalid for the ALTER DATABASE statement
Cause: The database link name you specified on the ALTER DATABASE statement is
not an ROM: link. You must specify an ROM: link when using the ALTER
DATABASE statement to mount or open a secondary database.
Action: Re-issue the ALTER DATABASE statement using a valid ROM: link to the
database you want to mount or open. If a valid ROM: link does not exist, create one
using the CREATE DATABASE LINK command. See the Trusted ORACLE RDBMS
Guide to Security Features for more information about creating database links using
the ROM: link type.
ORA-12316: syntax error in database link's connect string
Cause: The connect string in the CREATE DATABASE LINK statement has a
syntactical error.
Action: Drop the database link and recreate it using valid syntax. See the SQL
Language Reference Manual for more information about the connect string portion of
the CREATE DATABASE LINK statement.
ORA-12317: logon to database (link name string) denied
Cause: There are several possible causes for this error. First, you can get this error if
your username (and password, if you are using database instead of operating system
authentication) in the secondary database are not identical to your username (and
password) in the primary database. Second, you can get this error if your username in
the secondary database is invalid (has not been created). Third, you can get this error
if the username/password combination specified in the connect string of the database
link definition is invalid (either not created or has an invalid password).
Action: In the first case, ensure that the secondary database contains a username (and
password, if you are using database authentication) identical to the one you are using
in the primary database. In general, you should always use operating system
authentication in Trusted ORACLE (see the Trusted ORACLE RDBMS Guide to
Security Features for more information about the advantages of OS authentication). In
the second case, ensure that your username in the secondary database has been
created. In the third case, ensure that the username specified in the connect string has
been created in the secondary database.
ORA-12318: database (link name string) is already mounted
Cause: You are attempting to mount a secondary database that has already been
mounted by your instance.
Action: The database is already mounted, so you need not take additional action to
mount it. To establish access, use the ALTER DATABASE linkname OPEN command
to open the database.
ORA-12315 to ORA-12354 66-1
ORA-12319: database (link name string) is already open

Cause: You are attempting to open a secondary database that is already open.
Action: The database is open and you need not take additional action to establish
access.
ORA-12321: database (link name string) is not open and
AUTO_MOUNTING=FALSE
Cause: The secondary database that your instance is attempting to mount is not open
and automatic mounting has not been enabled.
Action: Manually mount and open the secondary database using ALTER DATABASE
linkname with the OPEN and MOUNT options. Alternately, to allow your instance to
automatically mount and open secondary databases, set the AUTO_MOUNTING
parameter in the parameter file to TRUE.
ORA-12322: unable to mount database (link name string)
Cause: This message should be accompanied by additional error messages that
indicate the cause of the problem.
Action: Follow the steps outlined in the accompanying error messages to resolve the
problem.
ORA-12323: unable to open database (link name string)
Cause: This message should be accompanied by additional error messages that
indicate the cause of the problem.
Action: Follow the steps outlined in the accompanying error messages to resolve the
problem.
ORA-12324: cannot use the ROM: link type on a private database link
Cause: You can only specify the ROM: link type on a public, not a private, database
link.
Action: Determine if there is an existing public database link to the secondary
database. If not, and if you wish to establish public access to the secondary database,
create a public database link to the secondary database using the CREATE
DATABASE LINK command.
ORA-12326: database string is closing immediately; no operations are permitted
Cause: The database you attempted to access is closing, so your operation has been
terminated.
Action: Wait until the database has been reopened, or contact the database
adminstrator.
ORA-12329: database string is closed; no operations are permitted
Cause: The database you attempted to access is closed, so your operation has been
terminated.
Action: Wait until the database is reopened, or contact the database administrator.
ORA-12333: database (link name string) is not mounted
Cause: You attempted to open a database that has not been mounted.
Action: Mount the database with the ALTER DATABASE linkname MOUNT
command, then re-attempt to open the database.
66-2 Error Messages
ORA-12334: database (link name string) is still open

Cause: You attempted to dismount a database that is still open.
Action: Close the database with the ALTER DATABASE linkname CLOSE command,
then re-attempt to dismount the database.
ORA-12335: database (link name string) is not open
Cause: You attempted to close a database that is not open.
Action: The database is closed; you can proceed with dismounting it.
ORA-12336: cannot login to database (link name string)
Cause: You are tyring to login while another user is mounting or dismounting the
same database.
Action: Check to see if the database is in the middle of being mounted or opened and
try your login again once the database is accessible.
ORA-12341: maximum number of open mounts exceeded
Cause: The number specified on the OPEN_MOUNTS parameter in the parameter file
exceeds the maximum allowed (255).
Action: Change the value of this parameter so that it reflects the actual number of
possible open mounts to secondary databases. This must be less than 255.
ORA-12342: open mounts exceeds limit set on the OPEN_MOUNTS parameter
Cause: The number of currently open mounts exceeds the value you specified on the
OPEN_MOUNTS parameter.
Action: Increase the value of the OPEN_MOUNTS parameter so that it accommodates
the maximum possible number of open mounts to secondary databases.
ORA-12345: user string lacks CREATE SESSION privilege in database link
(linkname string)
Cause: There are several possible causes for this message: First, you will get this
message if your username in the second database specified was not granted the
CREATE SESSION system privilege. Second, you will get this message if the
username specified in the connect string of the database link definition was not
granted the CREATE SESSION system privilege.
Action: The action you take depends upon the cause of the message: In the first case,
ensure that your username in the secondary database was granted the CREATE
SESSION system privilege. In the second case, ensure the username specified in the
connect string of the database link definition was granted the CREATE SESSION
system privilege in the secondary database.
ORA-12350: database link being dropped is still mounted
Cause: An attempt was made to drop a ROM: database link that was still mounted
and/or opened.
Action: Close and dismount the database and then re-issue the drop statement.
ORA-12351: cannot create view using a remote object which has a remote object
reference
Cause: You tried to create a view which references a remote object which, in turn,
references an object on another database. Since the view that you tried to create
references a remote object, that object cannot reference an object on another database.
Action: Choose a different object to reference in your view or change the remote
object so that it does not reference another database.
ORA-12315 to ORA-12354 66-3
ORA-12352: object string.string@string is invalid

Cause: An attempt was made to reference (compile against) an object of a secondary
database but the object is invalid and the system cannot validate or recompile it
because it is in a secondary database.
Action: Manually recompile the invalid object in the secondary database.
ORA-12353: secondary stored object cannot reference remote object
Cause: You tried to either select from a remote view or execute a remote procedure
which references an object on another database. Since the remote view or procedure is
on a secondary database, an additional reference to another database cannot be done.
Action: Choose a different object to reference or change the remote view or procedure
so that it does not reference another database.
ORA-12354: secondary object being dropped
Cause: You tried to access a object (for example, a table or view) on a secondary
database that was in the process of being dropped.
Action: Repeat the operation. If you receive this message again, try to access the object
from the secondary database. If you receive an internal error or a trace file, contact
Oracle WorldWide Technical Support.
66-4 Error Messages
67
ORA-12400 to ORA-12498
ORA-12400: invalid argument to facility error handling
Cause: An argument to a facility error handling function exceeded a maximum limit
or referred to an invalid product/facility.
Action: Specify a valid facility error handling parameter value.
ORA-12401: invalid label string: string
Cause: The policy could not convert the label string to a valid internal label.
Action: Correct the syntax of the label string.
ORA-12402: invalid format string: string
Cause: The format string is not supported by the policy.
Action: Correct the syntax of the format string.
ORA-12403: invalid internal label
Cause: An internal label could not be converted to a valid label for the policy.
Action: Analyze any additional messages on the error stack and consult the policy
documentation.
ORA-12404: invalid privilege string: string
Cause: The policy could not interpret the privilege string.
Action: Specify a privilege string that is supported by the policy.
ORA-12405: invalid label list
Cause: The policy determined that the label list was invalid for its intended use.
Action: Check the policy constraints on the specific list of labels.
ORA-12406: unauthorized SQL statement for policy string
Cause: The policy did not authorize the database session to perform the requested
SQL statement.
Action: Grant the user or program unit the necessary policy privilege or additional
authorizations.
ORA-12407: unauthorized operation for policy string
Cause: The policy did not authorize the database session to perform the requested
operation.
Action: Grant the user or program unit the necessary policy privilege or additional
authorizations.
ORA-12408: unsupported operation: string
Cause: The specified policy does not support the requested operation.
ORA-12400 to ORA-12498 67-1
Action: Consult the policy documentation to determine the supported access

mediation operations.
ORA-12409: policy startup failure for string policy
Cause: The policy encountered an error during startup processing; access to the data
protected by the policy is prohibited.
Action: Check the alert log for additional information, correct the policy error, and
restart the instance.
ORA-12410: internal policy error for policy: string\n Error: string
Cause: The policy enforcement encountered an internal error.
Action: Consult the policy documentation for details.
ORA-12411: invalid label value
Cause: The specified label value does not exist.
Action: Check the data dictionary views for the policy to identify valid labels.
ORA-12412: policy package string is not installed
Cause: The policy package does not exist in the database.
Action: Check that the policy package name is correct or install the required policy
package.
ORA-12413: labels do not belong to the same policy
Cause: The labels being compared belong to different policies.
Action: Only compare labels that belong to the same policy.
ORA-12414: internal LBAC error: string\n Error: string
Cause: An internal label policy framework error occurred.
ORA-12415: A column of another datatype exists on the specified table
Cause: The datatype of the column present in the table is different from the datatype
set for the policy column.
Action: Drop the column on the table or change the datatype for policy column.
ORA-12416: policy string not found
Cause: The specified policy does not exist in the database.
Action: Enter the correct policy name or create the policy.
ORA-12417: database object "string" not found
Cause: The specified object was not in the database.
Action: Enter the correct name for the database object.
ORA-12418: user string not found
Cause: The specified user does not exist in the database.
Action: Correct the user name or create the user.
ORA-12419: null binary label value
Cause: A null value was provided for a binary label operation.
Action: Provide a valid binary label for the operation.
67-2 Error Messages
ORA-12420: required procedures and functions not in policy package "string"

Cause: The policy package did not contain all of the procedures and functions
necessary to enforce the policy.
Action: Consult the label framework documentation for a list of required procedures
and functions for a policy package.
ORA-12421: different size binary labels
Cause: The label sizes for the binary label operation were not equal.
Action: Provide binary labels with the same lengths for the operation.
ORA-12422: max policies exceeded
Cause: You tried to create a new policy, but the maximum number of policies for the
instance had already been created.
Action: Increase the size of the MAX_LABEL_POLICIES initialization parameter and
restart the server.
ORA-12423: invalid position specified
Cause: The position specified for a binary label operation was invalid.
Action: Provide a position that is within the label size limits.
ORA-12424: length exceeds binary label size
Cause: The length specified for a binary label operation exceeded the the size of the
binary label.
Action: Provide a bit or byte length that is within the label size limits.
ORA-12425: cannot apply policies or set authorizations for system schemas
Cause: You tried to either apply a policy to the SYS, SYSTEM, or LBACSYS schema or
to set user labels/privileges for the SYS, SYSTEM, or LBACSYS user.
Action: Apply policies and set authorizations only for non-system users.
ORA-12426: invalid audit option
Cause: The option specified was not a valid audit option for the specified policy.
Action: Enter a correct audit option.
ORA-12427: invalid input value for string parameter
Cause: An input parameter was specified incorrectly.
Action: Correct the parameter value.
ORA-12428:
ORA-12429: label list range exceeded
Cause: The specified index value was not between 1 and 6.
Action: Correct the index value for the label list operation.
ORA-12430: invalid privilege number
Cause: The specified privilege number was not between 1 and 32.
Action: Correct the privilege number.
ORA-12431: invalid audit action
Cause: The specified audit action was not a valid audit action.
Action: Correct the audit action number.
ORA-12400 to ORA-12498 67-3
ORA-12432: LBAC error: string

Cause: LBAC enforcement resulted in an error.
Action: Correct the problem identified in the error message.
ORA-12433: create trigger failed, policy not applied
Cause: The policy could not be applied due to errors during the creation of a DML
trigger.
Action: Correct the SQL syntax of the label function specification.
ORA-12434: invalid audit type: string
Cause: The audit type must be BY ACCESS or BY SESSION.
Action: Correct the audit type value.
ORA-12435: invalid audit success: string
Cause: The audit success parameter must be SUCCESSFUL or NOT SUCCESSFUL.
Action: Correct the audit success value.
ORA-12436: no policy options specified
Cause: A NULL option string was specified, but no default schema or policy option
string was found.
Action: Enter a valid option string, or alter the schema or policy to have a valid
default option string.
ORA-12437: invalid policy option: string
Cause: A value that was not a valid policy option was entered.
Action: Correct the policy option value.
ORA-12438: repeated policy option: string
Cause: A policy option was entered more than once in the option string.
Action: Remove the duplicate policy option value.
ORA-12439: invalid combination of policy options
Cause: A set of contradictory policy options was entered.
Action: Provide a set of compatible policy options.
ORA-12440: insufficient authorization for the SYSDBA package
Cause: The use of the SYSDBA package requires the LBAC_DBA role.
Action: Grant the LBAC_DBA role to the database user.
ORA-12441: policy string already exists
Cause: You tried to create a policy with the same name as an existing one.
Action: Use a different name or drop the existing policy.
ORA-12442: policy column "string" already used by an existing policy
Cause: You tried to create a policy with the same policy column name as an existing
policy.
Action: Use a different name for the policy column or drop the existing policy.
67-4 Error Messages
ORA-12443: policy not applied to some tables in schema

Cause: You applied a policy to a schema, and some of the tables in the schema already
had the policy applied.
Action: No action necessary; the policy was applied to the remaining tables.
ORA-12444: policy already applied to table
Cause: You tried to apply a policy to a table that was already protected by the policy.
Action: To change the policy options, predicate, or label function, remove the policy
from the table and re-apply it.
ORA-12445: cannot change HIDDEN property of column
Cause: You tried to specify a different HIDE option for a table with an existing policy
column.
Action: Drop the column from the table and reapply the policy with the new HIDE
option.
ORA-12446: Insufficient authorization for administration of policy string
Cause: You tried to perform an administrative function for a policy, but you have not
been granted the policy_DBA role.
Action: Grant the user the policy_DBA role for the specified policy.
ORA-12447: policy role already exists for policy string
Cause: The role named policy_DBA already exists.
Action: Correct the policy name or delete the existing policy.
ORA-12448: policy string not applied to schema string
Cause: You tried to alter a schema policy that was not applied.
Action: Correct the policy name or schema name.
ORA-12449: Labels specified for user must be of type USER
Cause: You tried to set labels for a user, but the labels in the list were not all
designated as USER labels.
Action: Alter the labels to be USER labels.
ORA-12450: LOB datatype disabled in LBAC initialization file
Cause: You tried to specify a LOB datatype for a column or attribute, but the use of
the LOB datatype has been disabled.
Action: Change the LBAC initialization file to allow the creation of LOB columns and
attributes.
ORA-12451: label not designated as USER or DATA
Cause: A label is either a DATA label, a USER label, or both DATA and USER.
Action: Enter TRUE for at least DATA or USER.
ORA-12452: label tag string already exists
Cause: The label tag value you entered is already in use for another label.
Action: Enter a different value for the label tag.
ORA-12453: label string already exists
Cause: The label value you entered already exists.
Action: No action necessary; alter the label to change its tag or type.
ORA-12400 to ORA-12498 67-5
ORA-12454: label string does not exist for policy string

Cause: The label tag or value you entered did not identify a label for the policy.
Action: Enter a label value or tag that is in use by the policy.
ORA-12455: internal error in Label Security MMON cleanup task
Cause: An internal error occurred in the Label Security MMON cleanup task.
ORA-12456: label security startup in progress
Cause: You attempted to connect to the database before the Oracle Label Security
component was fully initialized.
Action: Wait until the database is fully open before attempting to connect.
ORA-12457: security label exceeded maximum allowable length
Cause: An operation attempted to materialize a security label greater than 4000 bytes
in length.
Action: Consult the Oracle Label Security documentation for information on how the
length of a security label is calculated. Re-submit the operation once the problem has
been corrected.
ORA-12458: Oracle Label Security not enabled
Cause: A Label Security operation was attempted without enabling Oracle Label
Security.
Action: Consult the Oracle Label Security documentation for information on how to
enable Oracle Label Security.
ORA-12459: Oracle Label Security not configured
Cause: An administrative operation was attempted without configuring Oracle Label
Security.
Action: Consult the Oracle Label Security documentation for information on how to
configure Oracle Label Security.
ORA-12460: cannot disable Oracle Label Security when Database Vault is enabled
Cause: An attempt was made to disable Oracle Label Security when Database Vault
was enabled.
Action: Disable Database Vault and bounce the database before attempting to disable
Oracle Label Security.
ORA-12461: undefined level string for policy string
Cause: The specified level is not defined for the policy.
Action: Correct the level identifier value.
ORA-12462: undefined compartment string for policy string
Cause: The specified compartment is not defined for the policy.
Action: Correct the compartment identifier value.
ORA-12463: undefined group string for policy string
Cause: The specified group is not defined for the policy.
Action: Correct the group identifier value.
67-6 Error Messages
ORA-12464: invalid characters in label component string

Cause: Label components can contain only alphanumeric characters, blanks, and
underscores.
Action: Correct syntax of the label component.
ORA-12465: not authorized for read or write on specified groups or compartments
Cause: Groups or compartments were included that were not in the user's list of
groups and compartments authorized for read or write access.
Action: Include groups or compartments authorized for read or write access in the
user's list of groups and compartments.
ORA-12466: default level is greater than the user's maximum
Cause: The default level cannot be greater than the user's maximum.
Action: Enter an authorized level.
ORA-12467: minimum label can contain a level only
Cause: You included compartments or groups in the minimum label.
Action: Enter only an authorized minimum level as the label.
ORA-12468: max write level does not equal max read level
Cause: The level in the max write label must equal the level in the max read label.
Action: Enter max read and max write labels with the same level component.
ORA-12469: no user levels found for user string and policy string
Cause: No levels have been specified for the user.
Action: Enter the maximum and minimum labels for the user.
ORA-12470: NULL or invalid user label: string
Cause: The label entered is NULL or not within the user's authorizations.
Action: Enter the authorized labels for the user.
ORA-12471: Specified compartment or group is not authorized for user
Cause: The specified compartment or group is not in user's authorizations or the user
does not have read on compartment or group specified for write.
Action: Enter an authorized compartment or group.
ORA-12472: policy string is being used
Cause: The policy which was being dropped due to event propagation from OID was
applied to some table or schema.
Action: Drop a policy in OID only if it is not used in any of the databases using the
policy.
ORA-12473: The procedure is disabled when Label Security is used with OID.
Cause: Using Label Security with OID disabled this procedure.
Action: Do not use OID with Label Security if this procedure is required to function.
ORA-12474: cannot change column name for a policy in use
Cause: An attempt was made to change a column name for a policy that was applied
on user schemas or tables.
Action: Disable the policy for all user schemas and tables before changing the column
name.
ORA-12400 to ORA-12498 67-7
ORA-12475: incompatible Oracle Label Security configuration

Cause: An attempt was made to configure Oracle Label Security with OID in a
pluggable database when Oracle Label Security without OID is configured in another
pluggable database or vice-versa.
Action: Use similar configurations of Oracle Label Security in all pluggable databases.
ORA-12476: least upper bound resulted in an invalid OS label
Cause: You tried to do an operation that generated a least upper bound (LUB) label
which is not a valid label on your operating system.
Action: Consult your OS label management documentation for information on invalid
label generation.
ORA-12477: greatest lower bound resulted in an invalid OS label
Cause: You tried to do an operation that generated a greatest lower bound (GLB) label
which is not a valid label on your operating system.
Action: Consult your OS label management documentation for information on invalid
label generation.
ORA-12479: file label string must equal DBHIGH string
Cause: A database file had an OS label that did not match DBHIGH. Either DBHIGH
was altered or the OS file was relabeled.
Action: Relabel the file so that its label matches DBHIGH, or alter DBHIGH so that it
matches the label on the file.
ORA-12480: specified clearance labels not within the effective clearance
Cause: You specified a clearance range that was not within your authorized clearance;
you can only specify clearance ranges that are within your clearance.
Action: Specify clearance labels that are within your own clearance range.
ORA-12481: effective label not within program unit clearance range
Cause: The effective label when the program unit was invoked was not within the
range authorized for the program unit.
Action: Modify the program unit clearance range or invoke the program unit from a
session with an authorized effective clearance.
ORA-12482: internal MLS error: string\n Error: string
Cause: An internal MLS policy error occurred.
ORA-12483: label not in OS system accreditation range
Cause: The specified label is above the OS maximum label or below the OS minimum
label.
Action: Use a label that is within the accreditation range for the host OS.
ORA-12484: invalid OS label
Cause: The specified label does not exist in the OS host's label definition file.
Action: Use the OS label management tools to define the label.
ORA-12485: new effective label not within effective clearance
Cause: You attempted to enter a value for an effective label that did not dominate the
effective min label or was not dominated by the effective max label.
67-8 Error Messages
Action: Enter a value between the min and the max labels.
ORA-12486: effective max labels and min labels cannot be changed
Cause: You attempted to enter a value for an effective min label or effective max label,
but these labels cannot be changed.
Action: Enter NULL values for the effective minimum and maximum labels.
ORA-12487: clearance labels not between DBHIGH and DBLOW
Cause: You attempted to enter a value for a clearance label that was not dominated by
DBHIGH or did not dominate DBLOW.
Action: Enter clearance label values between DBHIGH and DBLOW.
ORA-12488: maximum label does not dominate minimum label
Cause: You attempted to enter a value for a clearance label that did not preserve the
dominance relationship between the minimum and maximum labels.
Action: Enter label values that preserves the dominance relationship between the
minimum and maximum.
ORA-12489: default label not within clearance range
Cause: You attempted to enter a value for a default label that did not dominate the
minimum clearance or was not dominated by the maximum clearance.
Action: Enter a default label value within the clearance range.
ORA-12490: DBHIGH cannot be lowered
Cause: You attempted to enter a value for DBHIGH that did not dominate the existing
value of DBHIGH.
Action: Enter a value for DBHIGH that dominates the old value.
ORA-12491: DBHIGH value does not dominate DBLOW
Cause: You attempted to enter a value for DBHIGH that did not dominate DBLOW.
Action: Enter a value for DBHIGH that dominates DBLOW.
ORA-12492: DBLOW cannot be changed
Cause: You attempted to change the value of DBLOW after it had been set to any
initial value. DBLOW can only be set once after initial database creation.
Action: To change DBLOW, you have to create a new database, set DBLOW to the
new value, and import your data into the new database.
ORA-12493: invalid MLS binary label
Cause: The MLS binary label contained an invalid value, was not the correct size, or
contained a level, category, or release category that was not enabled.
Action: Check the DBA_MLS_LABELS view for the valid MLS labels.
ORA-12494: cannot insert or delete a level, category, or release category
Cause: You attempted to insert or delete a level, category, or release category
definition.
Action: If the label definition is no longer valid, change its name to one that identifies
it as invalid. When any labels are converted to character strings, the new label
definition will be used.
ORA-12400 to ORA-12498 67-9
ORA-12495: cannot disable an enabled level, category, or release category

Cause: You attempted to disable a level, category, or release category that had
previously been enabled. An enabled label definition may be exist in some database
label, so cannot be disabled.
Action: If the label definition is no longer valid, change its name to one that identifies
it as invalid. When any labels are converted to character strings, the new label
definition will be used.
ORA-12496: cannot change existing level, category, or release numbers
Cause: You attempted to change the number assigned to level, category or
releasability category.
Action: Change the character string representations, not the numbers.
ORA-12497: maximum combined categories exceeds string
Cause: The maximum number of descriptive categories plus release categories
supported by the MLS policy was exceeded.
Action: Enter numbers that do not add up to more than the maximum.
ORA-12498:
68
ORA-12500 to ORA-12699
ORA-12500: TNS:listener failed to start a dedicated server process
Cause: The process of starting up a dedicated server process failed. The executable
could not be found or the environment may be set up incorrectly.
Action: Turn on tracing at the ADMIN level and reexecute the operation. Verify that
the ORACLE Server executable is present and has execute permissions enabled.
Ensure that the ORACLE environment is specified correctly in LISTENER.ORA. The
Oracle Protocol Adapter that is being called may not be installed on the local hard
drive. Please check that the correct Protocol Adapter are successfully linked. If error
persists, contact Oracle Customer Support.
ORA-12502: TNS:listener received no CONNECT_DATA from client
Cause: No CONNECT_DATA was passed to the listener.
Action: Check that the service name resolved from TNSNAMES.ORA has the
CONNECT_DATA component of the connect descriptor.
ORA-12503: TNS:listener received an invalid REGION from client
Cause: Invalid REGION was passed to the listener.
Action: Check the REGION name specified in the CONNECT_DATA component of
the connect descriptor.
ORA-12504: TNS:listener was not given the SERVICE_NAME in
CONNECT_DATA
Cause: The listener was not configured with a default service and SERVICE_NAME
was missing from the CONNECT_DATA received by the listener.
Action: Possible solutions are: - Configure DEFAULT_SERVICE parameter in
LISTENER.ORA with a valid service name. Reload the listener parameter file using
reload [<listener_name>]. This should be done by the LISTENER administrator. - If
using a service name, Check that the connect descriptor corresponding to the service
name in TNSNAMES.ORA has a SERVICE_NAME or SID component in the
CONNECT_DATA.
ORA-12505: TNS:listener does not currently know of SID given in connect
descriptor
Cause: The listener received a request to establish a connection to a database or other
service. The connect descriptor received by the listener specified a SID for an instance
(usually a database instance) that either has not yet dynamically registered with the
listener or has not been statically configured for the listener. This may be a temporary
condition such as after the listener has started, but before the database instance has
registered with the listener.
Action: - Wait a moment and try to connect a second time. - Check which instances
are currently known by the listener by executing: lsnrctl services listener name - Check
ORA-12500 to ORA-12699 68-1
that the SID parameter in the connect descriptor specifies an instance known by the
listener. - Check for an event in the listener.log file.
ORA-12508: TNS:listener could not resolve the COMMAND given
Cause: The COMMAND given to listener is not supported.
Action: This is not seen in normal use of Oracle Net.
ORA-12509: TNS:listener failed to redirect client to service handler
Cause: The dispatcher terminated unexpectedly
Action: Attempt to connect again and if the same error occurs, contact the DBA to
check the state of the dispatchers for this SID. If the problem persists, turn on tracing
in the listener to determine the TNS error caused by the redirect.
ORA-12510: TNS:database temporarily lacks resources to handle the request
Cause: The dispatchers appear to be busy handling other requests.
Action: Attempt the connection again. If error persists, ask the DBA to increase the
number of dispatchers and/or dispatchers' limit on number of connections/sessions
that they can accept.
ORA-12511: TNS:service handler found but it is not accepting connections
Cause: The dispatchers notified the listener that they temporarily do not accept new
connections.
Action: Attempt the connection again. If error persists, contact the DBA to check the
state of the dispatchers and/or ask him to increase the number of dispatchers.
ORA-12513: TNS:service handler found but it has registered for a different protocol
Cause: The dispatchers registered for this service are connected to the listener by way
of a different network protocol than that of the client.
Action: Contact the DBA to register a dispatcher on your protocol.
ORA-12514: TNS:listener does not currently know of service requested in connect
descriptor
service. The connect descriptor received by the listener specified a service name for a
service (usually a database service) that either has not yet dynamically registered with
the listener or has not been statically configured for the listener. This may be a
temporary condition such as after the listener has started, but before the database
instance has registered with the listener.
Action: - Wait a moment and try to connect a second time. - Check which services are
currently known by the listener by executing: lsnrctl services listener name - Check that
the SERVICE_NAME parameter in the connect descriptor of the net service name
used specifies a service known by the listener. - If an easy connect naming connect
identifier was used, check that the service name specified is a service known by the
listener. - Check for an event in the listener.log file.
ORA-12515: TNS:listener could not find a handler for this presentation
Cause: None of the listener's known service handlers are registered as supporting the
presentation protocol required by the connecting client.
Action: Check that the destination service is configured to accept the presentation
protocol.
68-2 Error Messages
ORA-12516: TNS:listener could not find available handler with matching protocol
stack
Cause: None of the known and available service handlers for the given
SERVICE_NAME support the client's protocol stack: transport, session, and
presentation protocols.
Action: Check to make sure that the service handlers (e.g. dispatchers) for the given
SERVICE_NAME are registered with the listener, are accepting connections, and that
they are properly configured to support the desired protocols.
ORA-12518: TNS:listener could not hand off client connection
Cause: The process of handing off a client connection to another process failed.
Action: Turn on listener tracing and re-execute the operation. Verify that the listener
and database instance are properly configured for direct handoff. If problem persists,
call Oracle Support.
ORA-12519: TNS:no appropriate service handler found
Cause: The listener could not find any available service handlers that are appropriate
for the client connection.
Action: Run "lsnrctl services" to ensure that the instance(s) have registered with the
listener, and are accepting connections.
ORA-12520: TNS:listener could not find available handler for requested type of
server
Cause: None of the known and available service handlers for requested type of server
(dedicated or shared) are appropriate for the client connection.
Action: Run "lsnrctl services" to ensure that the instance(s) have registered with the
listener and that the appropriate handlers are accepting connections.
ORA-12521: TNS:listener does not currently know of instance requested in connect
descriptor
service. The connect descriptor received by the listener specified in addition to the
service name an instance name for an instance (usually a database instance) that
either has not yet dynamically registered with the listener or has not been statically
configured for the listener. This may be a temporary condition such as after the
listener has started, but before the database instance has registered with the listener.
Action: - Wait a moment and try to connect a second time. - Check which instances
are currently known by the listener by executing: lsnrctl services listener name - Check
that the INSTANCE_NAME parameter in the connect descriptor specifies an instance
name known by the listener. - Check for an event in the listener.log file.
ORA-12522: TNS:listener could not find available instance with given
INSTANCE_ROLE
Cause: There are not any available and appropriate database instances registered with
the listener, that are part of the service identified by SERVICE_NAME given in the
connect descriptor and that have the specified INSTANCE_ROLE (and
INSTANCE_NAME, if specified).
Action: Check to make sure that the INSTANCE_ROLE specified is correct. Run
"lsnrctl services" to ensure that the instance(s) have registered with the listener and
that they are ready to accept connections.
ORA-12500 to ORA-12699 68-3
ORA-12523: TNS:listener could not find instance appropriate for the client
connection
Cause: The listener could not find any available (database) instances, that are
appropriate for the client connection.
Action: Run "lsnrctl services" to ensure that the instance(s) are registered with the
listener, and have status READY.
ORA-12524: TNS:listener could not resolve HANDLER_NAME given in connect
descriptor
Cause: The HANDLER_NAME in the CONNECT_DATA was not found in the
listener's tables for the specified SERVICE_NAME and INSTANCE_NAME.
Action: Check to make sure that the HANDLER_NAME specified is correct.
ORA-12525: TNS:listener has not received client's request in time allowed
Cause: The listener disconnected the client because the client failed to provide the
necessary connect information within the allowed time interval. This may be a result
of network or system delays; or this may indicate that a malicious client is trying to
cause a Denial of Service attack on the listener.
Action: If the error occurred because of a slow network or system, reconfigure
INBOUND_CONNECT_TIMEOUT to a larger value. If a malicious client is
suspected, use the address in listener.log to identify the source and restrict access.
Turn on tracing for more information.
ORA-12526: TNS:listener: all appropriate instances are in restricted mode
Cause: Database instances supporting the service requested by the client were in
restricted mode. The Listener does not allow connections to instances in restricted
mode. This condition may be temporary, such as during periods when database
administration is performed.
Action: Attempt the connection again. If error persists, then contact the database
administrator to change the mode of the instance, if appropriate.
ORA-12527: TNS:listener: all instances are in restricted mode or blocking new
connections
Cause: All appropriate database instances supporting the service requested by the
client reported that they either were in restricted mode or were blocking the new
connections. The Listener does not allow connections to such instances. This condition
may be temporary, such as at instance startup.
Action: Attempt the connection again. If error persists, then contact the database
administrator to check the status of the instances.
ORA-12528: TNS:listener: all appropriate instances are blocking new connections
Cause: All instances supporting the service requested by the client reported that they
were blocking the new connections. This condition may be temporary, such as at
instance startup.
Action: Attempt the connection again. If error persists, then contact the administrator
to check the status of the instances.
ORA-12529: TNS:connect request rejected based on current filtering rules
Cause: Connection Manager and its listener were configured with filtering rules
specifying that the connect request be rejected.
Action: If this connect request should be allowed, then contact the administrator to
modify the filtering rules.
68-4 Error Messages
ORA-12531: TNS:cannot allocate memory

Cause: Sufficient memory could not be allocated to perform the desired activity.
Action: Either free some resource for TNS, or add more memory to the machine. For
further details, turn on tracing and reexecute the operation.
ORA-12532: TNS:invalid argument
Cause: An internal function received an invalid parameter.
reexecute the operation. If error persists, contact Oracle Customer Support.
ORA-12533: TNS:illegal ADDRESS parameters
Cause: An illegal set of protocol adapter parameters was specified. In some cases, this
error is returned when a connection cannot be made to the protocol transport.
Action: Verify that the destination can be reached using the specified protocol. Check
the parameters within the ADDRESS section of TNSNAMES.ORA. Legal ADDRESS
parameter formats may be found in the Oracle operating system specific
documentation for your platform. Protocols that resolve names at the transport layer
(such as DECnet object names) are vulnerable to this error if not properly configured
or names are misspelled.
ORA-12534: TNS:operation not supported
Cause: An internal function received a request to perform an operation that is not
supported (on this machine).
ORA-12535: TNS:operation timed out
Cause: The requested operation could not be completed within the time out period.
Action: Look at the documentation on the secondary errors for possible remedy. See
SQLNET.LOG to find secondary error if not provided explicitly. Turn on tracing to
gather more information.
ORA-12536: TNS:operation would block
Cause: An internal operation did not commence because to do so would block the
current process and the user has requested that operations be non-blocking.
Action: None needed; this is an information message.
ORA-12537: TNS:connection closed
Cause: "End of file" condition has been reached; partner has disconnected.
Action: None needed; this is an information message.
ORA-12538: TNS:no such protocol adapter
Cause: The protocol adapter requested (by way of the "(PROTOCOL=..)" keywordvalue pair in a TNS address) is unknown. If the supplied address is typographically
correct then the protocol adapter is not installed.
Action: Install the protocol adapter or correct typographically error, as appropriate.
Note: if the supplied address was derived from resolving the service name, check the
address in the appropriate file (TNSNAMES.ORA, LISTENER.ORA or
SQLNET.ORA).
ORA-12539: TNS:buffer over- or under-flow
Cause: Buffer too small for incoming data or too large for outgoing data.
ORA-12500 to ORA-12699 68-5
Action: This restriction (which is associated with CONNECT DATA) is not normally
visible to the user. For further details, turn on tracing and reexecute the operation;
contact Oracle Customer Support.
ORA-12540: TNS:internal limit restriction exceeded
Cause: Too many TNS connections open simultaneously.
Action: Wait for connections to close and re-try.
ORA-12541: TNS:no listener
Cause: The connection request could not be completed because the listener is not
running.
Action: Ensure that the supplied destination address matches one of the addresses
used by the listener - compare the TNSNAMES.ORA entry with the appropriate
LISTENER.ORA file (or TNSNAV.ORA if the connection is to go by way of an
Interchange). Start the listener on the remote machine.
ORA-12542: TNS:address already in use
Cause: Specified listener address is already being used.
Action: Start your listener with a unique address.
ORA-12543: TNS:destination host unreachable
Cause: Contact can not be made with remote party.
Action: Make sure the network driver is functioning and the network is up.
ORA-12544: TNS:contexts have different wait/test functions
Cause: Two protocol adapters have conflicting wait/test functions.
ORA-12545: Connect failed because target host or object does not exist
Cause: The address specified is not valid, or the program being connected to does not
exist.
Action: Ensure the ADDRESS parameters have been entered correctly; the most likely
incorrect parameter is the node name. Ensure that the executable for the server exists
(perhaps "oracle" is missing.) If the protocol is TCP/IP, edit the TNSNAMES.ORA file
to change the host name to a numeric IP address and try again.
ORA-12546: TNS:permission denied
Cause: User has insufficient privileges to perform the requested operation.
Action: Acquire necessary privileges and try again.
ORA-12547: TNS:lost contact
Cause: Partner has unexpectedly gone away, usually during process startup.
Action: Investigate partner application for abnormal termination. On an Interchange,
this can happen if the machine is overloaded.
ORA-12548: TNS:incomplete read or write
Cause: A data send or receive failed.
68-6 Error Messages
ORA-12549: TNS:operating system resource quota exceeded

Cause: The current user has exceeded the allotted resource assigned in the operating
system.
Action: Acquire more operating system resource, or perform a different function.
ORA-12550: TNS:syntax error
Cause: The supplied connect descriptor contains illegal syntax.
Action: Check the syntax of the connect descriptor in TNSNAMES.ORA.
ORA-12551: TNS:missing keyword
Cause: The supplied connect descriptor is missing one or more TNS keywords.
Action: Check the syntax, and ensure all required keywords are present.
ORA-12552: TNS:operation was interrupted
Cause: An internal operation was interrupted and could not complete.
ORA-12554: TNS:current operation is still in progress
Cause: An internal operation is still in progress.
ORA-12555: TNS:permission denied
Cause: User has insufficient privileges to perform the requested operation.
Action: Acquire necessary privileges and try again.
ORA-12556: TNS:no caller
Cause: TNS detected an incoming connect request but there was no caller.
ORA-12557: TNS:protocol adapter not loadable
Cause: On some platforms (such as OS/2) protocol adapters are loaded at run-time. If
the shared library (or DLL) for the protocol adapter is missing or one of its supporting
libraries is missing then this error is returned.
will include the name of the shared library (or DLL) that could not be loaded.
ORA-12558: TNS:protocol adapter not loaded
Cause: On some platforms (such as OS/2) protocol adapters are loaded at run-time. If
the shared library (or DLL) for the protocol adapter has not been loaded, then this
error is returned.
will have the name of the shared library (or DLL) that has not been loaded.
ORA-12560: TNS:protocol adapter error
Cause: A generic protocol adapter error occurred.
Action: Check addresses used for proper protocol specification. Before reporting this
error, look at the error stack and check for lower level transport errors. For further
ORA-12500 to ORA-12699 68-7
details, turn on tracing and reexecute the operation. Turn off tracing when the
operation is complete.
ORA-12561: TNS:unknown error
Cause: A generic protocol error occurred.
Action: For further details, turn on tracing and reexecute the operation.
ORA-12562: TNS:bad global handle
Cause: Internal error - bad 'gbh' argument passed to TNS from caller. System may
have been linked with old libraries.
Action: Not normally visible to the user, contact Oracle Customer Support.
ORA-12564: TNS:connection refused
Cause: The connect request was denied by the remote user (or TNS software).
reexecute the operation.
ORA-12566: TNS:protocol error
Cause: An unexpected TNS protocol error has occurred.
Action: For further details, turn on tracing and reexecute the operation. If error
ORA-12569: TNS:packet checksum failure
Cause: The data received is not the same as the data sent.
Action: Attempt the transaction again. If the error is persistent, turn on tracing and
reexecute the operation.
ORA-12570: TNS:packet reader failure
Cause: An error occurred during a data receive.
ORA-12571: TNS:packet writer failure
Cause: An error occurred during a data send.
ORA-12574: TNS:redirection denied
Cause: The connect request failed because it would have required redirection and the
caller has requested no redirections.
ORA-12575: TNS:dhctx busy
Cause: The handoff over a dhctx failed as dhctx was already busy with an ongoing
handoff.
ORA-12576: TNS:handoff not supported for this session
Cause: Handoff of a established session was attempted which either had tcps as its
transport or NA options were enabled for this session.
68-8 Error Messages
Action: Check the transport setting as well as NA options. If error persists, contact
ORA-12578: TNS:wallet open failed
Cause: An error was encountered while trying to open the specified wallet.
Action: For further details, turn on tracing and re-execute the operation.
ORA-12582: TNS:invalid operation
Cause: An internal function received an invalid request.
ORA-12583: TNS:no reader
Cause: A send operation has been requested but partner has already disconnected.
ORA-12585: TNS:data truncation
Cause: A receive operation has completed with insufficient data to satisfy the user's
request.
ORA-12589: TNS:connection not bequeathable
Cause: An attempt to hand-off a connection from one process to another has failed
because the protocol provider does not support it.
ORA-12590: TNS:no I/O buffer
Cause: An attempt to perform an I/O operation failed because no buffer was
available.
ORA-12591: TNS:event signal failure
Cause: The TNS software is unable to signal an event occurrence.
ORA-12592: TNS:bad packet
Cause: An ill-formed packet has been detected by the TNS software.
ORA-12593: TNS:no registered connection
Cause: An attempt to solicit network event activity has failed because no connections
are registered for event notification.
ORA-12500 to ORA-12699 68-9
ORA-12595: TNS:no confirmation

Cause: TNS is unable to get requested confirmation acknowledgment from remote
partner.
ORA-12596: TNS:internal inconsistency
Cause: TNS has detected an internal inconsistency.
reexecute the operation and contact Oracle Customer Support.
ORA-12597: TNS:connect descriptor already in use
Cause: Internal error - illegal use of connect descriptor.
ORA-12598: TNS:banner registration failed
Cause: The registration of a product banner with the Oracle server failed.
Action: This is an error which is not normally visible externally. Enable tracing and
attempt to repeat the error. If it occurs again, contact Oracle Customer Support.
ORA-12599: TNS:cryptographic checksum mismatch
Cause: The data received is not the same as the data sent.
Action: Attempt the transaction again. If error persists, check (and correct) the
integrity of your physical connection.
ORA-12600: TNS: string open failed
Cause: The creation of a string in ORACLE NLS format failed.
Action: This is an internal error, enable tracing and attempt to repeat the error. If it
occurs again, contact Oracle Customer Support.
ORA-12601: TNS:information flags check failed
Cause: The TNS information flags set by the process prior to connection negotiation
were not present after the negotiation was finished.
Action: This is an internal error. Enable tracing and attempt to repeat the error. If it
ORA-12602: TNS: Connection Pooling limit reached
Cause: The operation failed because maximum active current connections has been
reached. It may not be a real error when the Connection Pooling feature is enabled. It
is possible that the application later reissues the operation and successfully grabs the
connection pool slot and proceeds.
Action: This is an internal error. Enable tracing and attempt to repeat the error. If it
ORA-12606: TNS: Application timeout occurred
Cause: A network session did not reach an application-defined stage within the
allowed time interval.
Action: This is an error which does not normally appear at the high level. The action
to take is application specific, and is detailed in the higher level error description.
ORA-12607: TNS: Connect timeout occurred

Cause: A network session did not reach a predefined connect stage within the
allowed time interval.
Action: This is an error which does not normally appear at the high level. The action
to take is application specific, and is detailed in the higher level error description.
ORA-12608: TNS: Send timeout occurred
Cause: The send or write operation did not complete within the allowed time interval.
Action: Check if the peer host is available. Increase the send timeout value if
necessary.
ORA-12609: TNS: Receive timeout occurred
Cause: The receive or read operation did not complete within the allowed time
interval.
Action: Check if the peer host is available. Increase the receive timeout value if
necessary.
ORA-12611: TNS:operation is not portable
Cause: Attempted operation is not portable.
ORA-12612: TNS:connection is busy
Cause: Attempted operation failed because it conflicts with an ongoing action or
status of the connection.
ORA-12615: TNS:preempt error
Cause: A request to service an event failed because no event notification has yet been
posted.
ORA-12616: TNS:no event signals
Cause: The operation failed because the type of data specified is unknown.
ORA-12618: TNS:versions are incompatible
Cause: The two machines are running incompatible versions of TNS.
Action: Check the version numbers, and upgrade the machine with the smaller one.
ORA-12619: TNS:unable to grant requested service
Cause: The connect request failed because requested service could not be provided by
the local TNS software.
Action: If appropriate, reexecute with reduced service requirements.
ORA-12620: TNS:requested characteristic not available
Cause: The connect request failed because a requested transport characteristic could
not be supported by the remote TNS software.
ORA-12500 to ORA-12699 68-11
Action: If appropriate, reexecute with reduced requirements.

ORA-12622: TNS:event notifications are not homogeneous
Cause: An attempt to register a connection for event notification failed because the
event notification type conflicts with existing registrations.
ORA-12623: TNS:operation is illegal in this state
Cause: Connection is half-duplex and a full-duplex operation was attempted.
ORA-12624: TNS:connection is already registered
connection is already registered.
ORA-12625: TNS:missing argument
Cause: An operation failed because an argument was missing"
ORA-12626: TNS:bad event type
event type is unknown.
ORA-12628: TNS:no event callbacks
Cause: An attempt to register a connection for event notification failed because
asynchronous callbacks are not available.
ORA-12629: TNS:no event test
ability to test for events is not available.
ORA-12630: Native service operation not supported
Cause: An operation requested by a user is not supported by the native services
component.
Action: This may be an internal error if the operation should have been supported.
ORA-12631: Username retrieval failed
Cause: The authentication service failed to retrieve the name of a user.
Action: Enable tracing to determine which routine is failing.
ORA-12632: Role fetch failed

Cause: The authentication service failed to retrieve one of the user's roles.
Action: Enable tracing to determine which routine is failing.
ORA-12633: No shared authentication services
Cause: The list of authentication services specified by the user does not match those
supported by the process.
Action: Either specify another list or relink the executable with the desired services.
ORA-12634: Memory allocation failed
Cause: Process was unable to allocate memory.
Action: Terminate other processes in order to reclaim needed memory.
ORA-12635: No authentication adapters available
Cause: The executable was not linked with any authentication service adapters but
the sqlnet.ora parameter that determines whether or not authentication is required
was set to true.
Action: Either disable the parameter or relink the executable with service adapters.
ORA-12636: Packet send failed
Cause: A process was unable to send a packet to another process. Possible causes are:
1. The other process was terminated. 2. The machine on which the other process is
running went down. 3. Some other communications error occurred.
Action: If the cause is not obvious, contact Oracle Customer Support.
ORA-12637: Packet receive failed
Cause: A process was unable to receive a packet from another process. Possible causes
are: 1. The other process was terminated. 2. The machine on which the other process
is running went down. 3. Some other communications error occurred.
Action: If the cause is not obvious, contact Oracle Customer Support.
ORA-12638: Credential retrieval failed
Cause: The authentication service failed to retrieve the credentials of a user.
Action: Enable tracing to determine the exact error.
ORA-12639: Authentication service negotiation failed
Cause: No match was found between the types of authentication services that the
client supports and those that the server is using.
Action: Possible solutions: 1. Change the entry in sqlnet.ora that determines which
services are to be used. 2. Relink the client with at least one of the authentication
service adapters that the server supports. 3. Relink the server with at least one of the
authentication service adapters that the client supports. 4. Disable authentication on
both the client and server.
ORA-12640: Authentication adapter initialization failed
Cause: The function specified in the authentication table entry for the service failed.
ORA-12641: Authentication service failed to initialize
Cause: The authentication service failed during initialization.
ORA-12500 to ORA-12699 68-13
ORA-12642: No session key

Cause: A process has no session key associated with it because the authentication
service being used does not use one.
Action: If a session key is required, use another authentication service.
ORA-12643: Client received internal error from server
Cause: The client process received an error from the server that indicated that an
internal Oracle Net native services error had occurred.
Action: Enable tracing on both processes and attempt to recreate the problem. If
successful in recreating the problem, contact Oracle Customer Support.
ORA-12645: Parameter does not exist.
Cause: A sqlnet.ora parameter from which a value was needed does not exist.
Action: Set the parameter in the parameter file.
ORA-12646: Invalid value specified for boolean parameter
Cause: The value specified for a parameter was set to a value other than true/false or
on/off.
Action: Correct the value of the parameter.
ORA-12647: Authentication required
Cause: The parameter that controls whether authentication is required was set to true,
but the executable does not have an authentication service linked in.
Action: Either re-link the executable with an authentication service adapter or disable
the parameter.
ORA-12648: Encryption or data integrity algorithm list empty
Cause: A list-of-algorithms parameter was empty, e.g. "()".
Action: Change the list to contain the name of at least one installed algorithm, or
remove the list entirely if every installed algorithm is acceptable.
ORA-12649: Unknown encryption or data integrity algorithm
Cause: A list-of-algorithms parameter included an algorithm name that was not
recognized.
Action: Either remove that algorithm name, correct it if it was misspelled, or install
the driver for the missing algorithm.
ORA-12650: No common encryption or data integrity algorithm
Cause: The client and server have no algorithm in common for either encryption or
data integrity or both.
Action: Choose sets of algorithms that overlap. In other words, add one of the client's
algorithm choices to the server's list or vice versa.
ORA-12651: Encryption or data integrity algorithm unacceptable
Cause: The algorithm the server chose to use for encryption or data integrity was not
one of the choices acceptable to the client. This is either the result of an internal error,
of a network data transmission error, or of deliberate tampering with the transmitted
data.
Action: For further details, turn on tracing, re-execute the operation, and contact
ORA-12652: String truncated

Cause: Not enough memory was allocated for a string so it had to be truncated
Action: If it is OK that the string is truncated, then it is not an error. Otherwise, call
the routine that reported the error again with a larger string buffer.
ORA-12653: Authentication control function failed
Cause: The control function utilized by the authentication service driver failed.
ORA-12654: Authentication conversion failed
Cause: The authentication service was unable to convert the credentials of a user from
the format specific to the format into the ORACLE format.
ORA-12655: Password check failed
Cause: The authentication service being used was unable to verify the provided
password.
ORA-12656: Cryptographic checksum mismatch
Cause: The cryptographic checksum received with a packet of incoming data didn't
match the checksum computed by the receiving end. This indicates that the packet
was tampered with or otherwise corrupted in transit.
Action: Look for sources of data corruption, perhaps including deliberate tampering.
ORA-12657: No algorithms installed
Cause: The near side of the connection required the use of a service (either encryption
or checksumming) when no algorithms for that service were installed.
Action: Remove the "ON" requirement for that service.
ORA-12658: ANO service required but TNS version is incompatible
Cause: A client process that is running an earlier version of TNS attempted to connect
but the connection failed because the server process required that an ANO service
(authentication, encryption, etc.) be used.
Action: Relink the calling executable and retry the connection or eliminate the
requirement that the service be used on the server side.
ORA-12659: Error received from other process
Cause: An error was received by one or more services from the process on the other
side of the connection.
Action: Enable tracing to determine the exact error(s). The error(s) is (are) not
returned directly because an error generated by a server may not make sense on the
client side and vice-versa.
ORA-12660: Encryption or crypto-checksumming parameters incompatible
Cause: One side of the connection specified "REQUIRED" for encryption or cryptochecksumming, while the other side specified "REJECTED".
Action: Change the "REQUIRED" side to "REQUESTED" if the you want encryption or
crypto-checksumming to be optional, or change the "REJECTED" side to
"ACCEPTED" if you do not want the service to be optional.
ORA-12500 to ORA-12699 68-15
ORA-12661: Protocol authentication to be used

Cause: The authentication service has determined that the Oracle Net transport
protocol in use is to be utilized to authenticate a user's identity.
Action: This error is used solely to communicate information between the
authentication service and the Oracle Net session layer and should not normally be
visible. If the error is seen, contact Oracle Worldwide Support.
ORA-12662: proxy ticket retrieval failed
Cause: The authentication adapter used by Oracle Net failed to retrieve the
credentials needed to authenticate a database link.
ORA-12663: Services required by client not available on the server
Cause: Service(s) that was (were) required by the client process were not available on
the server process.
Action: Configure the server with the services required by the client (best solution) or
delete the requirement from the configuration file of the client (least secure).
ORA-12664: Services required by server not available on the client
Cause: Service(s) that was (were) required by the server process were not available on
the client process.
Action: Configure the client with the services required by the server (best solution) or
delete the requirement from the configuration file of the server (least secure).
ORA-12665: NLS string open failed
Cause: A native service was unable to make a string available for use by the National
Language Support component.
Action: Make sure the National Language Support component has been properly. If it
has, enable tracing and report the problem to Customer Support.
ORA-12666: Dedicated server: outbound transport protocol different from inbound
Cause: The protocol specified for an externally-identified outbound connection from a
dedicated server (database link) was not the same as that used for the inbound
connection. It is not possible for Oracle Net to authenticate a proxy connection that
uses a protocol that is different from that which was used for the connection to the
dedicated server.
Action: Specify the same protocol in the Oracle Net connect descriptor for the
outbound connection as that used for the inbound connection.
ORA-12667: Shared server: outbound transport protocol different from inbound
Cause: The protocol specified for an externally-identified outbound connection from a
shared server (database link) was not the same as as that used for the inbound
connection. It is not possible for Oracle Net to authenticate a proxy connection that
uses a protocol that is different from that which was used for the connection to the
shared server.
Action: Specify the same protocol in the Oracle Net connect descriptor for the
outbound connection as that used for the inbound connection
ORA-12668: Dedicated server: outbound protocol does not support proxies
Cause: The protocol specified to perform an externally-identified proxy connection
(database link) from a dedicated server does not support proxy connections.
Action: Specify a protocol in the Oracle Net connect descriptor used for the
connection that does support externally-authenticated proxy connections. NOTE:
Because of a limitation in Oracle Net, the protocol used for the proxy connection must
the same as that used for the connection from the client to the server.
ORA-12669: Shared server: outbound protocol does not support proxies
Cause: The protocol specified to perform an externally-identified proxy connection
(database link) from a shared server does not support proxy connections.
Action: Specify a protocol in the Oracle Net connect descriptor used for the
connection that does support externally-authenticated proxy connections. NOTE:
Because of a limitation in Oracle Net, the protocol used for the proxy connection must
the same as that used for the connection from the client to the server.
ORA-12670: Incorrect role password
Cause: A password supplied for a role could not be validated by the authentication
service.
Action: Supply the correct password.
ORA-12671: Shared server: adapter failed to save context
Cause: The adapter for the authentication service failed when it tried to save the data
needed for proxy connections (database links) through the shared server.
Action: Enable tracing to determine the exact error. Contact Oracle Customer Support
if the reason is not obvious.
ORA-12672: Database logon failure
Cause: The authentication service adapter in use encountered an error it attempted to
validate the logon attempt of a user.
Action: Enable tracing to determine the exact error encountered by the adapter.
ORA-12673: Dedicated server: context not saved
Cause: A connection was marked as being a proxy connection (database link) from a
dedicated server but no inbound context was present.
Action: This error should not normally be visible to the user. Contact Oracle
Customer Support.
ORA-12674: Shared server: proxy context not saved
Cause: A connection was marked as being a proxy connection (database link) from a
shared server but no inbound context was present.
Action: This error should not normally be visible to the user. Contact Oracle
Customer Support.
ORA-12675: External user name not available yet
Cause: The authentication service in use was not able to return the external name of a
user of the ORACLE server because it is not available to the service yet.
Action: This is just an informational message and should not normally be visible to
the user. If the error does appear, contact Oracle Customer Support.
ORA-12676: Server received internal error from client
Cause: The server process received an error from the client which indicated that an
internal Oracle Net native services error had occurred.
Action: Enable tracing on both processes and attempt to recreate the problem. If the
problem recurs, contact Oracle Customer Support.
ORA-12500 to ORA-12699 68-17
ORA-12677: Authentication service not supported by database link

Cause: The authentication service used by the proxy process (database link) was
unable to find the adapter being used by the client in its list of authentication
mechanisms.
Action: Specify an authentication adapter that is shared by the client and the server
being used for the database link.
ORA-12678: Authentication disabled but required
Cause: The configuration parameters that control whether authentication is disabled
or required were both set to TRUE.
Action: Set one or both of the parameters to FALSE.
ORA-12679: Native services disabled by other process but required
Cause: The remote process has disabled native services but the local process requires
them.
Action: Enable native services on the remote process or disable them locally.
ORA-12680: Native services disabled but required
Cause: The process has disabled native services but at least one service is required.
Action: Enable native services or change the configuration file so that none of the
available services are required.
ORA-12681: Login failed: the SecurID card does not have a pincode yet
Cause: The SecurID card that is used to logon to Oracle, does not have a pincode
assigned to it.
Action: Use one of the programs supplied by Security Dynamics to assign a pincode
to the card.
ORA-12682: Login failed: the SecurID card is in next PRN mode
Cause: The SecurID card and the SecurID server are out of sync and the server
requires the next cardcode to resynchronize the card.
Action: Use one of the programs supplied by Security Dynamics to resynchronize the
SecurID card.
ORA-12683: encryption/crypto-checksumming: no Diffie-Hellman seed
Cause: The "sqlnet.crypto_seed" parameter is missing from the SQLNET.ORA
parameters file.
Action: Add this line to SQLNET.ORA: sqlnet.crypto_seed = "randomly-chosen text"
ORA-12684: encryption/crypto-checksumming: Diffie-Hellman seed too small
Cause: The "sqlnet.crypto_seed" parameter in the SQLNET.ORA parameter file is too
small.
Action: Add more randomly-chosen text to it, perhaps using Network Manager.
ORA-12685: Native service required remotely but disabled locally
Cause: A native service is required by the remote process but native services have
been disabled locally.
Action: Enable native services locally or change the configuration parameters on the
remote host so that no native services are required.
ORA-12686: Invalid command specified for a service

Cause: An operation which does not exist was specified for a native service.
Action: This is a programming error and should not normally be visible to the user. If
the error does appear, contact Oracle Customer Support.
ORA-12687: Credentials expired.
Cause: The credentials that are used to authenticate the user for the requested
connection have expired.
Action: Renew your credentials. Refer to the documentation specific for your
Network Authentication Adapter on how to do this.
ORA-12688: Login failed: the SecurID server rejected the new pincode
Cause: There are a number of reasons why the SecurID server would refuse a
pincode: - The user might not have permission to make up his own pincode. - The
pincode was either too short or too long. Valid pincodes consist of minimal four, but
no more than eight characters. - The pincode contains any non alphanumeric
characters.
Action: Reexecute the operation and make sure to use a pincode that satisfies the
above requirements. If the problem persists, turn on tracing at the Oracle Server side
of the connection and examine the trace file for the exact error.
ORA-12689: Server Authentication required, but not supported
Cause: Server Authentication is required for this connection, but not supported by
both sides of the connection.
Action: Make sure both sides of the connection have the correct version of Advanced
Networking Option, and that the Authentication Adapter supports Server
Authentication.
ORA-12690: Server Authentication failed, login cancelled
Cause: Server Authentication is required, but the server's credentials were found
invalid by the client.
Action: Make sure that the server has a valid set of credentials. Refer to your
authentication adapter specific documentation on how to do this.
ORA-12696: Double Encryption Turned On, login disallowed
Cause: The user is using a Secure Protocol Adapter that has Encryption turned ON as
well as ANO Encryption.
Action: Turn OFF either ANO Encryption or the Protocol Adapter Encryption if
possible. Refer to the Administrator's Guide on how to do this.
ORA-12699: Native service internal error
Cause: An internal error occurred in the native services component.
Action: Enable tracing to determine the exact error. Contact Oracle Customer
Support.
ORA-12500 to ORA-12699 68-19
69
ORA-12700 to ORA-19400
ORA-12700: invalid NLS parameter value (string)
Cause: An invalid or unknown NLS configuration parameter was specified.
Action: n/a
ORA-12701: CREATE DATABASE character set is not known
Cause: The character set specified when creating the database is unknown.
Action: n/a
ORA-12702: invalid NLS parameter string used in SQL function
Cause: An unknown parameter name or invalid value is specified in a NLS parameter
string.
Action: n/a
ORA-12703: this character set conversion is not supported
Cause: The requested conversion between two character sets in the CONVERT
function is not implemented
Action: n/a
ORA-12704: character set mismatch
Cause: One of the following: - The string operands(other than an nlsparams
argument) to an operator or built-in function do not have the same character set. - An
nlsparams operand is not in the database character set. - String data with character set
other than the database character set is passed to a built-in function not expecting it. The second argument to CHR() or CSCONVERT() is not CHAR_CS or NCHAR_CS. A string expression in the VALUES clause of an INSERT statement, or the SET clause
of an UPDATE statement, does not have the same character set as the column into
which the value would be inserted. - A value provided in a DEFAULT clause when
creating a table does not have the same character set as declared for the column. - An
argument to a PL/SQL function does not conform to the character set requirements of
the corresponding parameter.
Action: n/a
ORA-12705: Cannot access NLS data files or invalid environment specified
Cause: Either an attempt was made to issue an ALTER SESSION command with an
invalid NLS parameter or value; or the environment variable(s) NLS_LANG,
ORA_NLSxx, or ORACLE_HOME was incorrectly specified, therefore the NLS data
files cannot be located.
Action: Check the syntax of the ALTER SESSION command and the NLS parameter,
correct the syntax and retry the statement, or specify the correct directory path/
values in the environment variables.
ORA-12700 to ORA-19400 69-1
ORA-12706: this CREATE DATABASE character set is not allowed

Cause: It is not allowed to create a database on a native ASCII-based machine using
an EBCDIC-based character set, and vice versa.
Action: n/a
ORA-12707: error while getting create database NLS parameter string
Action: n/a
ORA-12708: error while loading create database NLS parameter string
Action: n/a
ORA-12709: error while loading create database character set
Action: n/a
ORA-12710: CREATE CONTROLFILE character set is not known
Cause: The character set specified when creating the control file is unknown.
Action: n/a
ORA-12711: this CREATE CONTROLFILE character set is not allowed
Cause: It is not allowed to create a control file on a native ASCII-based machine using
an EBCDIC-based character set, and vice versa.
Action: n/a
ORA-12712: new character set must be a superset of old character set
Cause: When you ALTER DATABASE ... CHARACTER SET, the new character set
must be a superset of the old character set. For example, WE8ISO8859P1 is not a
superset of the WE8DEC.
Action: Specify a superset character set.
ORA-12713: Character data loss in NCHAR/CHAR conversion
Cause: When character set conversion happens between CHAR and NCHAR either
implicitly or explicitly, some characters are lost due to no mapping characters in the
destination character set.
Action: Make sure all the characters can be mapped to destination character set or set
NLS_NCHAR_CONV_EXCP to be FALSE.
ORA-12714: invalid national character set specified
Cause: Only UTF8 and AL16UTF16 are allowed to be used as the national character
set
Action: Ensure that the specified national character set is valid
ORA-12715: invalid character set specified
Cause: The character set specified is not allowed for this operation or is invalid
Action: Ensure that the specified character set is valid
69-2 Error Messages
ORA-12716: Cannot ALTER DATABASE CHARACTER SET when CLOB data

exists
Cause: CLOB data changes representation to Unicode when converting to a multibyte
character set and must be migrated
Action: Remove CLOB data as listed in the alert file. CLOB data can be migrated by
methods such as import/export
ORA-12717: Cannot issue ALTER DATABASE NATIONAL CHARACTER SET
when NCLOB, NCHAR or NVARCHAR2 data exists
Cause: NCLOB, NCHAR or NVARCHAR2 data changed the representation to
Unicode when converting to a multibyte character set and must be migrated.
Action: Remove NCLOB, NCHAR or NVARCHAR2 data as listed in the alert file. The
above type data can be migrated by methods such as import/export.
ORA-12718: operation requires connection as SYS
Cause: This command can only be run when connecting as SYS
Action: Connect as SYS to run this command
ORA-12719: operation requires database is in RESTRICTED mode
Cause: This command can only be run when the database is in RESTRICTED mode
Action: Ensure that the system is in RESTRICTED mode
ORA-12720: operation requires database is in EXCLUSIVE mode
Cause: This command can only be run when the database is in EXCLUSIVE mode
Action: Ensure that the system is in EXCLUSIVE mode
ORA-12721: operation cannot execute when other sessions are active
Cause: This command can only be run when there are no other sessions active
Action: Ensure there are no other connections to the database
ORA-12722: regular expression internal error
Cause: A regular expression internal error occurred.
ORA-12723: regular expression too complex
Cause: The regular expression was too complex and could not be parsed.
ORA-12724: regular expression corrupt
Cause: The regular expression contained an incorrect sequence of metacharacters.
Action: Ensure the metacharacters are correctly positioned.
ORA-12725: unmatched parentheses in regular expression
Cause: The regular expression did not have balanced parentheses.
Action: Ensure the parentheses are correctly balanced.
ORA-12726: unmatched bracket in regular expression
Cause: The regular expression did not have balanced brackets.
Action: Ensure the brackets are correctly balanced.
ORA-12700 to ORA-19400 69-3
ORA-12727: invalid back reference in regular expression

Cause: A back references was found before a sub-expression.
Action: Ensure a valid sub-expression is being referenced.
ORA-12728: invalid range in regular expression
Cause: An invalid range was found in the regular expression.
Action: Ensure a valid range is being used.
ORA-12729: invalid character class in regular expression
Cause: An unknown character class was found in the regular expression.
Action: Ensure a valid characters class is being used.
ORA-12730: invalid equivalence class in regular expression
Cause: An unknown equivalence class was found in the regular expression.
Action: Ensure a valid equivalence class is being used.
ORA-12731: invalid collation class in regular expression
Cause: An unknown collation class was found in the regular expression.
Action: Ensure a valid collation class is being used.
ORA-12732: invalid interval value in regular expression
Cause: An invalid interval value was found in the regular expression.
Action: Ensure a valid interval value is being used.
ORA-12733: regular expression too long
Cause: The operation failed because the regular expression it used exceeds the
maximum supported size.
Action: Use a shorter regular expression.
ORA-12734: Instant Client Light: unsupported client national character set string
set. Instant Client Light has only minimal character sets.
Action: Do not use Instant Client Light for this character set
ORA-12735: Instant Client Light: unsupported client character set string
Cause: The character set specified is not allowed for this operation or is invalid.
Instant Client Light has only minimal character sets.
ORA-12736: Instant Client Light: unsupported server national character set string
set. Instant Client Light has only minimal character sets.
ORA-12737: Instant Client Light: unsupported server character set string
Instant Client Light has only minimal character sets.
69-4 Error Messages
ORA-12738: Express Instant Client: unsupported client national character set string
set. Instant Client has only minimal character sets.
Action: Do not use Express Instant Client for this character set
ORA-12739: Express Instant Client: unsupported client character set string
Express Instant Client has only minimal character sets.
ORA-12740: Express Instant Client: unsupported server national character set string
set. Instant Client has only minimal character sets.
ORA-12741: Express Instant Client: unsupported server character set string
Express Instant Client has only minimal character sets.
Action: Do not use Express Instant Light for this character set
ORA-12742: unable to create the collation key
Cause: The character argument of a collation-sensitive operator was too long or it had
too many decomposable characters to create a collation key for it in the available
buffer space.
Action: Shorten the argument value or, if using a UCA-based collation, increase the
ratio of characters with short or no Unicode decomposition to characters with long
Unicode decomposition in the value.
ORA-12743: internal LX error code, arguments: [string], [string], [string]
Cause: This is an internal error in a globalization support function.
ORA-12744: Character set string is not allowed as a database character set.
Cause: An attempt was made to create or alter a database using a client-only or
conversion-only character set.
Action: Specify a supported database character set.
ORA-12752: An instance-critical process has terminated.
Cause: An unexpected error was encountered by an instance-critical process.
ORA-12753: The Oracle home user ID does not match the effective user ID of the
local client which connected to the Oracle instance.
Cause: The user ID that is the owner of the Oracle home directory was not the same as
the effective user ID of the local client that connected to the Oracle instance.
Action: Run the local client that connects to Oracle instance with the same user ID as
the owner of the Oracle home.
ORA-12800: system appears too busy for parallel query execution
Cause: load on system is too high to perform parallel queries.
Action: re-execute serially or wait until system load is reduced.
ORA-12700 to ORA-19400 69-5
ORA-12801: error signaled in parallel query server string

Cause: A parallel query server reached an exception condition.
ORA-12802: parallel query server lost contact with coordinator
Cause: A parallel query server lost contact with the foreground (coordinator)
process/thread.
ORA-12803: parallel query server lost contact with another server
Cause: A parallel query server lost contact with another server.
ORA-12804: parallel query server appears to have died
Cause: Cannot find process information for a parallel query server thread.
ORA-12805: parallel query server died unexpectedly
Cause: A parallel query server died unexpectedly, PMON cleaning up the process.
persists, contact Oracle Support Services. See trace file for more details.
ORA-12806: could not get background process to hold enqueue
Action: This error should not normally occur. If it persists, contact Oracle Support
Services.
ORA-12807: process queue could not receive parallel query message
Services.
ORA-12808: cannot set string_INSTANCES greater than number of instances string
Cause: An attempt was made to set SCAN_INSTANCES or CACHE_INSTANCES
using the ALTER SYSTEM command to a value larger than the number of available
instances.
Action: See the accompanying message for the current allowable maximum value, or
set SCAN_INSTANCES / CACHE_INSTANCES to ALL.
ORA-12809: cannot set string_INSTANCES when mounted in exclusive mode
Cause: An attempt was made to set SCAN_INSTANCES or CACHE_INSTANCES
using the ALTER SYSTEM command while the database was mounted in exclusive
mode.
Action: SCAN_INSTANCES / CACHE_INSTANCES may not be set unless running
Oracle Real Application Clusters mounted in CLUSTER_DATABASE mode.
69-6 Error Messages
ORA-12810: PARALLEL_MAX_SERVERS must be less than or equal to string

Cause: An attempt was made to set the PARALLEL_MAX_SERVERS parameter to a
value higher than the maximum allowed by the system.
Action: Set PARALLEL_MAX_SERVERS to a value less than or equal to the
maximum specified in the accompanying message and retry.
ORA-12811: PARALLEL_MIN_SERVERS must be less than or equal to
PARALLEL_MAX_SERVERS, string
Cause: An attempt was made to set the PARALLEL_MIN_SERVERS parameter to a
value higher than PARALLEL_MAX_SERVERS.
Action: Set PARALLEL_MIN_SERVERS to a value less than or equal to
PARALLEL_MAX_SERVERS (indicated in the accompanying message) and retry.
ORA-12812: only one PARALLEL or NOPARALLEL clause may be specified
Cause: PARALLEL was specified more than once, NOPARALLEL was specified more
than once, or both PARALLEL and NOPARALLEL were specified in a CREATE
TABLE, CLUSTER, or INDEX or in an ALTER TABLE or CLUSTER statement, or in a
RECOVER command.
Action: Remove all but one of the PARALLEL or NOPARALLEL clauses and reissue
the statement.
ORA-12813: value for PARALLEL or DEGREE must be greater than 0
Cause: PARALLEL 0 or DEGREE 0 was specified in a CREATE TABLE, CLUSTER, or
INDEX or in an ALTER TABLE or CLUSTER statement.
Action: Specify a degree of parallelism greater than 0 or specify default parallelism
using PARALLEL with no degree or using DEGREE DEFAULT within a PARALLEL
clause.
ORA-12814: only one CACHE or NOCACHE clause may be specified
Cause: CACHE was specified more than once, NOCACHE was specified more than
once, or both CACHE and NOCACHE were specified in a CREATE TABLE or
CLUSTER, or in an ALTER TABLE or CLUSTER statement.
Action: Remove all but one of the CACHE or NOCACHE clauses and reissue the
statement.
ORA-12815: value for INSTANCES must be greater than 0
Cause: PARALLEL parameter specifying number of instances must be a positive
integer or DEFAULT
Action: specify a positive integer or DEFAULT for INSTANCES if parallelism across
instances is desired.
ORA-12816: parallel create index fastpath operation
ORA-12817: parallel query option must be enabled
Cause: A parallel query option feature has been invoked but this option has not been
enabled.
Action: Enable the parallel query option.
ORA-12818: invalid option in PARALLEL clause
Cause: an unrecognized option was used within a PARALLEL clause.
Action: specify any combination of DEGREE { n | DEFAULT } and INSTANCES { n |
DEFAULT } within the PARALLEL clause.
ORA-12700 to ORA-19400 69-7
ORA-12819: missing options in PARALLEL clause

Cause: PARALLEL clause cannot be empty.
Action: specify any combination of DEGREE { n | DEFAULT } and INSTANCES { n |
DEFAULT } within the PARALLEL clause.
ORA-12820: invalid value for DEGREE
Cause: invalid value for DEGREE was specified within a PARALLEL clause.
Action: specify a positive integer or DEFAULT for the DEGREE option within a
PARALLEL clause.
ORA-12821: invalid value for INSTANCES
Cause: invalid value for INSTANCES was specified within a PARALLEL clause.
Action: specify a positive integer or DEFAULT for the INSTANCES option within a
PARALLEL clause.
ORA-12822: duplicate option in PARALLEL clause
Cause: DEGREE or INSTANCES was specified more than once within a PARALLEL
clause.
Action: specify each desired PARALLEL clause option only once.
ORA-12823: default degree of parallelism may not be specified here
Cause: the PARALLEL keyword was used alone or DEGREE DEFAULT was specified
in the PARALLEL clause of an ALTER DATABASE RECOVER command.
Action: respecify with an explicit degree of parallelism.
ORA-12824: INSTANCES DEFAULT may not be specified here
Cause: INSTANCES DEFAULT was specified in the PARALLEL clause of an ALTER
DATABASE RECOVER command
Action: respecify with an explicit value for INSTANCES or omit the INSTANCES
option if single instance recovery is desired.
ORA-12825: explicit degree of parallelism must be specified here
Cause: the DEGREE option was omitted from an ALTER DATABASE RECOVER
command.
Action: respecify with an explicit degree of parallelism.
ORA-12826: hung parallel query server was killed
Cause: parallel query server was hung and subsequently killed.
Action: re-execute query and report suspicious events in trace file to Oracle Support
Services if error persists.
ORA-12827: insufficient parallel query slaves (requested string, available string,
parallel_min_percent string)
Cause: PARALLEL_MIN_PERCENT parameter was specified and fewer than the
minimum number of slaves were acquired
Action: Either reexecute the query with a lower PARALLEL_MIN_PERCENT or wait
until some running queries are completed, thus freeing up slaves
ORA-12828: Can't start parallel transaction at a remote site
Cause: PDML transaction cannot be started because we are not in the coordinator site
of the distributed transaction.
69-8 Error Messages
Action: Do not use PDML at remote sites.

ORA-12829: Deadlock - itls occupied by siblings at block string of file string
Cause: parallel statement failed because all itls in the current block are occupied by
siblings of the same transaction.
Action: increase MAXTRANS of the block or reduce the degree of parallelism for the
statement. Reexecute the statement. Report suspicious events in trace file to Oracle
Support Services if error persists.
ORA-12830: Must COMMIT or ROLLBACK after executing parallel INSERT/
UPDATE/DELETE
Cause: After executing a parallel INSERT/UPDATE/DELETE statement, a command
other than COMMIT or ROLLBACK was issued.
Action: Execute COMMIT or ROLLBACK before issuing another SQL command.
ORA-12831: Must COMMIT or ROLLBACK after executing INSERT with APPEND
hint
Cause: After executing an INSERT statement with an APPEND hint, a command
other than COMMIT or ROLLBACK was issued.
Action: Execute COMMIT or ROLLBACK before issuing another SQL command.
ORA-12832: Could not allocate slaves on all specified instances
Cause: After executing a query on a global v$ fixed view, one or more instances failed
to allocate a slave to process query
Action: To allow results to be returned by sucessfully allocated slaves, execute ALTER
SESSION SET ALLOW_PARTIAL_SN_RESULTS=TRUE statement, or check
parameters of instances
ORA-12833: Coordinator's instance not a member of parallel_instance_group
Cause: The coordinator's instance must be a member of the parallel_instance_group in
which this operation will be run.
Action: Either add the coordinator's instance to the current parallel_instance_group or
change parallel_instance_group.
ORA-12834: Instance group name, 'string', too long, must be less than string
characters
Cause: The instance group name is too long.
Action: Either shorten the name or get rid of the instance group.
ORA-12835: No instances are active in the GLOBAL_VIEW_ADMIN_GROUP
Cause: There must be at least one instance in the GLOBAL_VIEW_ADMIN_GROUP
in order to execute a query on global views
Action: Change the value of GLOBAL_VIEW_ADMIN_GROUP
ORA-12838: cannot read/modify an object after modifying it in parallel
Cause: Within the same transaction, an attempt was made to add read or modification
statements on a table after it had been modified in parallel or with direct load. This is
not permitted.
Action: Rewrite the transaction, or break it up into two transactions: one containing
the initial modification and the second containing the parallel modification operation.
ORA-12700 to ORA-19400 69-9
ORA-12839: cannot modify an object in parallel after modifying it

Cause: Within the same transaction, an attempt was made to perform parallel
modification operations on a table after it had been modified. This is not permitted.
Action: Rewrite the transaction or break it up into two transactions: one containing
the parallel modification and the second containing the initial modification operation.
ORA-12840: cannot access a remote table after parallel/insert direct load txn
Cause: Within a transaction, an attempt was made to perform distributed access after
a PDML or insert direct statement had been issued.
Action: Commit/rollback the PDML transaction first, and then perform the
distributed access, or perform the distributed access before the first PDML statement
in the transaction.
ORA-12841: Cannot alter the session parallel DML state within a transaction
Cause: Transaction in progress
Action: Commit or rollback transaction and then re-execute
ORA-12842: Cursor invalidated during parallel execution
Cause: The cursor was invalidated during the parse phase of deferred parallel
processing, e.g. when set operands are parallelized.
Action: Depends on why the cursor was invalidated. Possible causes include DDL on
a schema object and shared pool being flushed.
ORA-12843: pdml lock not held properly on the table
Cause: The coodinator crashed or released the lock on the partition which the slave is
trying to aquire currently.
Action: Check if the coordinator or some of the other slaves died. Also check that the
lock has not been corrupted. Issue the pdml again.
ORA-12845: failed to receive interinstance parallel execution message
Cause: OS or interconnect problem receiving interinstance message
Action: Check OS specific diagnostics
ORA-12850: Could not allocate slaves on all specified instances: string needed,
string allocated
Cause: When executing a query on a gv$ fixed view, one or more instances failed to
allocate a slave to process query.
Action: Check trace output for instances on which slaves failed to start. GV$ query
can only proceed if slaves can be allocated on all instances.
ORA-12851: PARALLEL_MAX_SERVERS must be greater than or equal to
PARALLEL_MIN_SERVERS, string
Cause: An attempt was made to set the PARALLEL_MAX_SERVERS parameter to a
value less than PARALLEL_MIN_SERVERS.
Action: Set PARALLEL_MAX_SERVERS to a value greater than or equal to
PARALLEL_MIN_SERVERS value specified in the accompanying message and retry.
ORA-12852: PARALLEL_MIN_SERVERS must be less than PROCESSES, string
Cause: An attempt was made to set the PARALLEL_MIN_SERVERS parameter to a
value higher than PROCESSES.
Action: Set PARALLEL_MIN_SERVERS to a value less than PROCESSES value

specified in the accompanying message and retry.
ORA-12853: insufficient memory for PX buffers: current stringK, max needed
stringK
Cause: Insufficient SGA memory for PX buffers
Action: Reconfigure sga to include at least (max - current) bytes of additional memory
ORA-12854: Parallel query is not supported on temporary LOBs
Cause: The parallel query statement produced a temporary LOB.
Action: Turn off parallelism for the query or underlying table
ORA-12855: cannot run parallel or insert direct load in a loopback
Cause: A loopback was created in the transaction before this operation.
Action: Do not use loopback when using pdml or insert direct load.
ORA-12856: cannot run parallel query on a loopback connection
Cause: A table or index in a parallel query is referenced via a loopback connection.
Action: Do not use loopback connection when running a query in parallel.
ORA-12872: First slave parse gave different plan
Cause: First hard parse on slave given QC-supplied environment and parameters
gave different plan from QC. Try again with outline.
Action: No external action. Internally used for outline-based reparse.
ORA-12874: parallel execution monitor terminated with error
Cause: The parallel execution monitor process died.
Action: Wait for the process to restart.
ORA-12899: value too large for column string (actual: string, maximum: string)
Cause: An attempt was made to insert or update a column with a value which is too
wide for the width of the destination column. The name of the column is given, along
with the actual width of the value, and the maximum allowed width of the column.
Note that widths are reported in characters if character length semantics are in effect
for the column, otherwise widths are reported in bytes.
Action: Examine the SQL statement for correctness. Check source and destination
column data types. Either make the destination column wider, or use a subset of the
source column (i.e. use substring).
ORA-12900: must specify a default temporary tablespace for a locally managed
database
Cause: a locally managed database must have a temporary tablespace other than
SYSTEM tablespace
Action: specify the default temporary tablespace when creating a locally managed
database
ORA-12901: default temporary tablespace must be of TEMPORARY type
Cause: in a locally managed database, default temporary tablespace must be
TEMPORARY type
Action: n/a
ORA-12700 to ORA-19400 69-11
ORA-12902: default temporary tablespace must be SYSTEM or of TEMPORARY

type
Cause: in a dictionary managed database, default temporary tablespace must be
SYSTEM or TEMPORARY type
Action: n/a
ORA-12903: default temporary tablespace must be an ONLINE tablespace
ORA-12904: default temporary tablespace cannot be altered to PERMANENT type
ORA-12905: default temporary tablespace cannot be brought OFFLINE
ORA-12906: cannot drop default temporary tablespace
ORA-12907: tablespace string is already the default temporary tablespace
ORA-12908: cannot specify SYSTEM as default temporary tablespace when
creating database
ORA-12909: TEMPORARY keyword expected
ORA-12910: cannot specify temporary tablespace as default tablespace
Cause: attempt to assign a temporary tablespace to be a user's default tablespace
Action: assign a permanent tablespace to be the default tablespace
ORA-12911: permanent tablespace cannot be temporary tablespace
Cause: attempt to assign a permanent tablespace to be a user's temporary tablespace
Action: assign a temporary tablespace to be user's temporary tablespace
ORA-12912: Dictionary managed tablespace specified as temporary tablespace
Cause: attempt to assign a dictionary managed tablespace to be a user's temporary
tablespace
Action: Assign a locally managed temporary tablespace to be user's temporary
tablespace
ORA-12913: Cannot create dictionary managed tablespace
Cause: Attemp to create dictionary managed tablespace in database which has system
tablespace as locally managed
Action: Create a locally managed tablespace.
ORA-12914: Cannot migrate tablespace to dictionary managed type
Cause: Attemp to migrate locally managed tablespace to dictionary managed type
when the database has locally managed system tablespace.
Action: Command cannot be issued.
ORA-12915: Cannot alter dictionary managed tablespace to read write
Cause: Attemp to alter dictionary managed tablespace to read write in database
which has system tablespace as locally managed. This tablespace can only be
dropped.
Action: Command cannot be issued.
ORA-12916: cannot shrink permanent or dictionary managed tablespace

Cause: An attempt was made to shrink a permanent tablespace or a dictionary
managed tablespace.
Action: Check the tablespace type and issue the statement only on locally managed
temporary tablespaces.
ORA-12917: Invalid option specified for default permanent tablespace
ORA-12918: Invalid tablespace type for default permanent tablespace
Cause: The tablespace is either dropped, temporary or undo
Action: Check the tablespace type and reissue the statement
ORA-12919: Can not drop the default permanent tablespace
Cause: An attemp was made to drop the default permanent tablespace
Action: Make a different tablespace as the default permanent tablespace and reissue
the drop
ORA-12920: database is already in force logging mode
Cause: ALTER DATABASE FORCE LOGGING command failed because the database
is already in force logging mode.
Action: n/a
ORA-12921: database is not in force logging mode
Cause: ALTER DATABASE NO FORCE LOGGING command failed because the
database is not in force logging mode.
Action: n/a
ORA-12922: concurrent ALTER DATABASE [NO] FORCE LOGGING command is
running
Cause: There is a concurrent ALTER DATABASE FORCE LOGGING or ALTER
DATABASE NO FORCE LOGGING command running in the system.
Action: Contact the database administrator who is responsible for the concurrent
command.
ORA-12923: tablespace string is in force logging mode
Cause: An attempt to alter the specified tablespace temporary failed because the
tablespace is in force logging mode.
Action: Put the tablespace out of force logging mode by ALTER TABLESPACE NO
FORCE LOGGING command.
ORA-12924: tablespace string is already in force logging mode
Cause: An attempt to alter the specified tablespace into force logging mode failed
because it is already in force logging mode.
Action: n/a
ORA-12925: tablespace string is not in force logging mode
Cause: An attempt to alter the specified tablespace out of force logging mode failed
because it is not in force logging mode.
Action: n/a
ORA-12700 to ORA-19400 69-13
ORA-12926: FORCE LOGGING option already specified

Cause: In CREATE TABLESPACE, the FORCE LOGGING option was specified more
than once.
Action: Remove all but one of the FORCE LOGGING options.
ORA-12927: RETENTION option already specified
Cause: In CREATE TABLESPACE, the RETENTION option was specified more than
once.
Action: Remove all but one of the RETENTION options.
ORA-12928: ENCRYPTION option already specified
Cause: In CREATE TABLESPACE, the ENCRYPTION option was specified more than
once.
Action: Remove all but one of the ENCRYPTION options.
ORA-12931: FORCE LOGGING or SET STANDBY NOLOGGING already
specified
Cause: FORCE LOGGING or SET STANDBY NOLOGGING options were specified
more than once.
Action: Remove all but one of the FORCE LOGGING or SET STANDBY
NOLOGGING options.
ORA-12940: Not enough space in DBVerify text buffer
Cause: DBVerify ran out of text buffer. The error was trapped internally by the
system. DBVerify would return the result in text buffer and then resume checking.
Action: None
ORA-12941: DBVerify exception
Cause: DBVerify encountered run-time error. The error signal was trapped internally
by the system.
Action: None
ORA-12950: SYSTEM tablespace specified as default permanent tablespace
Cause: SYSTEM tablespace was specified as the default permanent during database
creation.
Action: If default permanent tablespace is not specified,then SYSTEM will implicitly
become the default permanent tablespace. Specify an alternate tablespace or omit the
default tablespace clause and reissue the CREATE DATABASE statement
ORA-12951: Attempt to change default permanent tablespace to temporary
Cause: It is incorrect to alter the default permanent tablespace of a database to
temporary type
Action: n/a
ORA-12952: Control space growth in ASSM segment under concurrency
ORA-12980: checkpoint option not allowed with SET UNUSED
Cause: An attempt was made to specify checkpoint option with SET UNUSED.
Action: Remove checkpoint option.
ORA-12981: cannot drop column from an object type table

Cause: An attempt was made to drop a column from an object type table.
Action: This action is not allowed.
ORA-12982: cannot drop column from a nested table
Cause: An attempt was made to drop a column from a nested table.
ORA-12983: cannot drop all columns in a table
Cause: An attempt was made to drop all columns in a table.
Action: Make sure at least one column remains in the table after the drop column
operation.
ORA-12984: cannot drop partitioning column
Cause: An attempt was made to drop a column used as the partitioning key.
ORA-12985: tablespace 'string' is read only, cannot drop column
Cause: An attempt was made to drop column from a partition/subpartition on a read
only tablespace.
Action: Set the tablespace to read write and resubmit statement.
ORA-12986: columns in partially dropped state. Submit ALTER TABLE DROP
COLUMNS CONTINUE
Cause: An attempt was made to access a table with columns in partially dropped state
(i.e., drop column operation was interrupted).
Action: Submit ALTER TABLE DROP COLUMNS CONTINUE to complete the drop
column operation before accessing the table.
ORA-12987: cannot combine drop column with other operations
Cause: An attempt was made to combine drop column with other ALTER TABLE
operations.
Action: Ensure that drop column is the sole operation specified in ALTER TABLE.
ORA-12988: cannot drop column from table owned by SYS
Cause: An attempt was made to drop a column from a system table.
Action: This action is not allowed
ORA-12989: invalid value for checkpoint interval
Cause: An invalid checkpoint interval specified in statement. Checkpoint interval
must be between 0 and (2^31-1).
Action: Correct checkpoint interval and resubmit statement
ORA-12990: duplicate option specified
Cause: Duplicate option specified in statement.
Action: Remove the duplicate option and resubmit statement.
ORA-12991: column is referenced in a multi-column constraint
Cause: An attempt was made to drop a column referenced by some constraints.
Action: Drop all constraints referencing the dropped column or specify CASCADE
CONSTRAINTS in statement.
ORA-12700 to ORA-19400 69-15
ORA-12992: cannot drop parent key column

Cause: An attempt was made to drop a parent key column.
Action: Drop all constraints referencing the parent key column, or specify CASCADE
CONSTRAINTS in statement.
ORA-12993: tablespace 'string' is offline, cannot drop column
Cause: An attempt was made to drop a column from a partition/subpartition on an
offline tablespace.
Action: Bring the tablespace online and resubmit statement.
ORA-12994: drop column option only allowed once in statement
Cause: An attempt was made to repeat the drop column option in a single statement.
Action: Separate drop column options into different statements and resubmit
statements.
ORA-12995: no columns in partially dropped state
Cause: An attempt was made to submit DROP COLUMNS CONTINUE statement
while there are no partially dropped columns.
Action: Cannot submit this statement.
ORA-12996: cannot drop system-generated virtual column
Cause: An attempt was made to drop a virtual column generated by the system.
Action: n/a
ORA-12997: cannot drop primary key column from an index-organized table
Cause: An attempt was made to drop a primary key column from an index- organized
table.
ORA-12998: Ignore errors during drop column from atb.c
ORA-12999: cannot DROP or SET UNUSED a column that has been set unused
Cause: An attempt was made to DROP or SET UNUSED a column that has already
been 'set unused'.
Action: Use the DROP UNUSED COLUMNS option to remove the column.
ORA-13000: dimension number is out of range
Cause: The specified dimension is either smaller than 1 or greater than the number of
dimensions encoded in the HHCODE.
Action: Make sure that the dimension number is between 1 and the maximum
number of dimensions encoded in the HHCODE.
ORA-13001: dimensions mismatch error
Cause: The number of dimensions in two HHCODEs involved in a binary HHCODE
operation do not match.
Action: Make sure that the number of dimensions in the HHCODEs match.
ORA-13002: specified level is out of range
Cause: The specified level is either smaller than 1 or greater than the maximum level
encoded in an HHCODE.
Action: Verify that all levels are between 1 and the maximum number of levels
encoded in the HHCODE.
ORA-13003: the specified range for a dimension is invalid
Cause: The specified range for a dimension is invalid.
Action: Make sure that the lower bound (lb) is less than the upper bound (ub).
ORA-13004: the specified buffer size is invalid
Cause: The buffer size for a function is not valid.
ORA-13005: recursive HHCODE function error
Cause: An error occurred in a recursively called HHCODE function.
ORA-13006: the specified cell number is invalid
Cause: The cell identifier is either less than 0 or greater than (2^ndim - 1).
Action: Make sure that the cell identifier is between 0 and (2^ndim - 1).
ORA-13007: an invalid HEX character was detected
Cause: A character that is not in the range [0-9] or [A-F a-f] was detected.
Action: Verify that all characters in a string are in [0-9] or [A-F a-f].
ORA-13008: the specified date format has an invalid component
Cause: Part of specified date format is invalid.
Action: Verify that the date format is valid.
ORA-13009: the specified date string is invalid
Cause: The specified date string has a bad component or does not match the specified
format string.
Action: Make sure that the components of the date string are valid and that the date
and format strings match.
ORA-13010: an invalid number of arguments has been specified
Cause: An invalid number of arguments was specified for an SDO function.
Action: Verify the syntax of the function call.
ORA-13011: value is out of range
Cause: A specified dimension value is outside the range defined for that dimension.
Action: Make sure that all values to be encoded are within the defined dimension
range.
ORA-13012: an invalid window type was specified
Cause: An invalid window type was specified.
Action: Valid window types are RANGE, PROXIMITY, POLYGON.
ORA-13013: the specified topology was not INTERIOR or BOUNDARY
Cause: A topology was specified that was not INTERIOR or BOUNDARY.
Action: Make sure that INTERIOR or BOUNDARY is used to describe an HHCODE's
topology.
ORA-12700 to ORA-19400 69-17
ORA-13014: a topology identifier outside the range of 1 to 8 was specified

Cause: A topology identifier outside the range of 1 to 8 was specified.
Action: Specify a topology in the range of 1 to 8.
ORA-13015: the window definition is not valid
Cause: The number of values used to define the window does not correspond to the
window type.
Action: Verify that the number of values used to defined the window is correct for the
window type and number of dimensions.
ORA-13016: specified topology [string] is invalid
Cause: The specified topology did not exist in the database, or some components of
the topology were missing from the database.
Action: Check the specified topology by executing the SDO_TOPO.validate_topology
function.
ORA-13017: unrecognized line partition shape
Cause: The shape of a 2-D line partition could not be determined.
ORA-13018: bad distance type
Cause: The specified distance type is invalid.
Action: The only supported distance functions are EUCLID and MANHATTAN.
ORA-13019: coordinates out of bounds
Cause: Vertex coordinates lie outside the valid range for specified dimension.
Action: Redefine vertex coordinates within specified boundaries.
ORA-13020: coordinate is NULL
Cause: A vertex coordinate has a NULL value.
Action: Redefine vertex coordinate to have non-NULL value.
ORA-13021: element not continuous
Cause: The coordinates defining a geometric element are not connected.
Action: Redefine coordinates for the geometric element.
ORA-13022: polygon crosses itself
Cause: The coordinates defining a polygonal geometric element represent crossing
segments.
Action: Redefine coordinates for the polygon.
ORA-13023: interior element interacts with exterior element
Cause: An interior element of a geometric object interacts with the exterior element of
that object.
Action: Redefine coordinates for the geometric elements.
ORA-13024: polygon has less than three segments
Cause: The coordinates defining a polygonal geometric element represent less than
three segments.
Action: Redefine the coordinates for the polygon.
ORA-13025: polygon does not close

Cause: The coordinates defining a polygonal geometric element represent an open
polygon.
Action: Redefine the coordinates of the polygon.
ORA-13026: unknown element type for element string.string.string
Cause: The SDO_ETYPE column in the layer_SDOGEOM table contains an invalid
geometric element type value.
Action: Redefine the geometric element type in the layer_SDOGEOM table for the
specified geometric element using one of the supported SDO_ETYPE values. See the
Oracle Spatial documentation for an explanation of SDO_ETYPE and its possible
values.
ORA-13027: unable to read dimension definition from string
Cause: There was a problem reading the dimension definition from the
layer_SDODIM table.
Action: Verify that the layer_SDODIM table exists and that the appropriate privileges
exist on the table. Address any other errors that might appear with the message.
ORA-13028: Invalid Gtype in the SDO_GEOMETRY object
Cause: There is an invalid SDO_GTYPE in the SDO_GEOMETRY object.
Action: Verify that the geometries have valid gtypes.
ORA-13029: Invalid SRID in the SDO_GEOMETRY object
Cause: There is an invalid SDO_SRID in the SDO_GEOMETRY object. The specified
SRID may be outside the valid SRID range.
Action: Verify that the geometries have valid SRIDs.
ORA-13030: Invalid dimension for the SDO_GEOMETRY object
Cause: There is a mismatch between the dimension in the SDO_GTYPE and
dimension in the SDO_GEOM_METADATA for the SDO_GEOMETRY object.
Action: Verify that the geometries have valid dimensionality.
ORA-13031: Invalid Gtype in the SDO_GEOMETRY object for point object
Cause: There is an invalid SDO_GTYPE in the SDO_GEOMETRY object where the
VARRAYs are NULL but the SDO_GTYPE is not of type POINT.
Action: Verify that the geometries have valid gtypes.
ORA-13032: Invalid NULL SDO_GEOMETRY object
Cause: There are invalid SDO_POINT_TYPE or SDO_ELEM_INFO_ARRAY or
SDO_ORDINATE_ARRAY fields in the SDO_GEOMETRY object.
Action: Verify that the geometries have valid fields. To specify a NULL geometry,
specify the whole SDO_GEOMETRY as NULL instead of setting each field to NULL.
ORA-13033: Invalid data in the SDO_ELEM_INFO_ARRAY in SDO_GEOMETRY
object
Cause: There is invalid data in the SDO_ELEM_INFO_ARRAY field of the
SDO_GEOMETRY object. The triplets in this field do not make up a valid geometry.
Action: Verify that the geometries have valid data.
ORA-12700 to ORA-19400 69-19
ORA-13034: Invalid data in the SDO_ORDINATE_ARRAY in SDO_GEOMETRY

object
Cause: There is invalid data in the SDO_ORDINATE_ARRAY field of the
SDO_GEOMETRY object. The coordinates in this field do not make up a valid
geometry. There may be NULL values for X or Y or both.
ORA-13035: Invalid data (arcs in geodetic data) in the SDO_GEOMETRY object
Cause: There is invalid data in the SDO_ELEM_INFO_ARRAY field of the
SDO_GEOMETRY object. There are arcs in a geometry that has geodetic coordinates.
ORA-13036: Operation [string] not supported for Point Data
Cause: The specified geometry function is not supported for point data.
Action: Make sure that the specified geometry function is not called on point data.
ORA-13037: SRIDs do not match for the two geometries
Cause: A Spatial operation is invoked with two geometries where one geometry has
an SRID and the other geometry does not have an SRID.
Action: Make sure that the spatial operations are invoked between two geometries
with compatible SRIDs.
ORA-13039: failed to update spatial index for element string.string.string
Cause: Another error will accompany this message that will indicate the problem.
Action: Correct any accompanying errors. If no accompanying error message appears,
ORA-13040: failed to subdivide tile
Action: Note any accompanying errors and contact Oracle Support Services.
ORA-13041: failed to compare tile with element string.string.string
Cause: The spatial relationship between a generated tile and the specified element
could not be determined.
Action: This is an internal error. Verify the geometry using the
VALIDATE_GEOMETRY_WITH_CONTEXT procedure. If the procedure does not
return any errors, note any errors that accompany ORA-13041 and contact Oracle
Support Services.
ORA-13042: invalid SDO_LEVEL and SDO_NUMTILES combination
Cause: An invalid combination of SDO_LEVEL and SDO_NUMTILES values was
read from the layer_SDOLAYER table. The most likely cause is that the columns are
NULL.
Action: Verify the that SDO_LEVEL and SDO_NUMTILES columns contain valid
integer values as described in the Oracle Spatial documentation. Then retry the
operation.
ORA-13043: failed to read metadata from the layer_SDOLAYER table
Cause: An error was encountered reading the layer metadata from the
layer_SDOLAYER table.
Action: This error is usually the result of an earlier error which should also have been
reported. Address this accompanying error and retry the current operation. If no
accompanying error was reported, contact Oracle Support Services.
ORA-13044: the specified tile size is smaller than the tolerance
Cause: The tile size specified for fixed size tessellation is smaller than the tolerance as
specified in the layer metadata.
Action: See the Oracle Spatial documentation for an explanation of tiling levels, tile
size, and tiling resolution. Ensure that the tiling parameters are set such that any
generated tile is always larger than or equal to a tile at the maximum level of
resolution. This can be achieved by using a fewer number of tiles per geometric object
or specifying a smaller tile size value than the current one.
ORA-13045: invalid compatibility flag
ORA-13046: invalid number of arguments
Cause: An invalid number of arguments were specified for an SDO_GEOM function.
Action: See the Oracle Spatial documentation for a description of the syntax and
semantics of the relevant SDO_GEOM function.
ORA-13047: unable to determine ordinate count from table layer_SDOLAYER
Cause: An SDO_GEOM function was unable to determine the number of ordinates for
the SDO layer layer.
Action: Verify that the layer_SDOLAYER table has a valid value for the column
SDO_ORDCNT. Then retry the operation.
ORA-13048: recursive SQL fetch error
ORA-13049: unable to determine tolerance value from table layer_SDODIM
Cause: An SDO_GEOM function was unable to determine the tolerance value for the
SDO layer layer.
Action: Verify that the layer_SDODIM table has a valid value for the column
SDO_TOLERANCE.
ORA-13050: unable to construct spatial object
ORA-13051: failed to initialize spatial object
ORA-13052: unsupported geometric type for geometry string.string
Cause: The geometry type for a specific instance in a layer_SDOGEOM table is not
among the set of geometry types supported by Oracle Spatial.
Action: Check the Oracle Spatial documentation for the list of supported geometry
types and workarounds that permit the storage and retrieval of non-supported
geometric types with the SDO schema.
ORA-12700 to ORA-19400 69-21
ORA-13053: maximum number of geometric elements in argument list exceeded

Cause: The maximum number of geometric elements that can be specified in the
argument list for an SDO_GEOM function was exceeded.
Action: Check the Oracle Spatial documentation for the syntax of the SDO_GEOM
function and use fewer arguments to describe the geometry, or check the description
of the SDO_WINDOW package for a workaround that permits storing the object in a
table and then using it in as an argument in a call to the SDO_GEOM function.
ORA-13054: recursive SQL parse error
ORA-13055: Oracle object string does not exist in specified table
Cause: The requested object is not present in the specified table.
Action: Verify the syntax of the function or procedure that reported this error and
verify that the object does indeed exist in the specified table. Then retry the operation.
ORA-13060: topology with the name string already exists
Cause: The specified topology name was not unique in the database.
Action: Verify that the CREATE_TOPOLOGY call specifies the correct topology name
and that the procedure is invoked from the correct schema.
ORA-13061: topology with the name string does not exist
Cause: The specified topology did not exist in the database.
Action: Verify that the current procedure/function call specifies the correct schema
and topology name.
ORA-13062: topology IDs do not match in the feature table and the topology
Cause: The specified topology ID in the feature table did not match the topology ID
stored in the topology metadata.
Action: Verify that the specified topology ID matches the topology ID stored in the
topology metadata.
ORA-13063: relationship information table is missing data for feature table [string]
Cause: The topology relationship information table (xxx_RELATION$) did not have
the matching partition corresponding to the feature table.
Action: Make sure the correct topology IDs and names are specified in the call to
register the feature table with the topology.
ORA-13064: relationship information table has inconsistent data for feature table
[string]
Cause: The topology_id, tg_layer_id values stored in the feature table did not match
the values stored in the topology relationship information table (xxx_RELATION$).
Action: Make sure that the correct feature tables are specified in the call to register the
feature table with the topology.
ORA-13065: cannot delete a child layer with a parent layer
Cause: A call was made to delete a feature layer which has a dependent layer defined
on it.
Action: Make sure that all dependent feature layers are deleted before deleting the
current feature layer.
ORA-13066: wrong feature geometry or element type

Cause: The SDO_TOPO_GEOMETRY object had the wrong geometry and/or element
type.
Action: Correct the geometry and/or element type in the SDO_TOPO_GEOMETRY
object.
ORA-13067: operator requires both parameters from the same topology
Cause: Both SDO_TOPO_GEOMETRY parameters did not come from the same
topology.
Action: Make sure both the parameters to the operator are from the same topology. If
this is not possible, consider using a signature of the operator that does not use two
SDO_TOPO_GEOMETRY parameters.
ORA-13068: wrong table or column name in SDO_TOPO_GEOMETRY constructor
Cause: An SDO_TOPO_GEOMETRY constructor was invoked with incorrect
parameters for table name and/or column name.
Action: Fix the parameters in the call and try again.
ORA-13069: incorrect degree value for SDO_GEOMETRY object
Cause: An incorrect degree value <=1 was passed for a Non-Uniform Rational BSpline curve.
Action: Correct the degree value for the Non-Uniform Rational B-Spline curve.
ORA-13070: incorrect number of control points for SDO_GEOMETRY object
Cause: An incorrect number of control points was passed for a Non-Uniform Rational
B-Spline curve.
Action: Correct the number of control points for the Non-Uniform Rational B-Spline
curve.
ORA-13071: incorrect control points, degree for SDO_GEOMETRY object
Cause: An incorrect number of control points and degree was passed for a NonUniform Rational B-Spline curve.
Action: Ensure that the number of control points is greater than the degree for a NonUniform Rational B-Spline curve.
ORA-13072: incorrect number of knots for SDO_GEOMETRY object
Cause: An incorrect number of knot values was passed for a Non-Uniform Rational BSpline curve.
Action: Correct the number of knot values passed for the Non-Uniform Rational BSpline curve.
ORA-13073: incorrect control point weight value for a SDO_GEOMETRY object
Cause: An incorrect value was passed for the weight of a control point of a NonUniform Rational B-Spline curve.
Action: Ensure all weight values for control points are positive.
ORA-13074: incorrect knot value for SDO_GEOMETRY object
Cause: An incorrect knot value was passed for a Non-Uniform Rational B-Spline
curve.
Action: Ensure the knot values passed for the Non-Uniform Rational B-Spline curve
are in non-decreasing order.
ORA-12700 to ORA-19400 69-23
ORA-13075: incorrect knot value sequence for SDO_GEOMETRY object

Cause: An incorrect knot value sequence was passed for a Non-Uniform Rational BSpline curve.
Action: Ensure the knot values passed for the Non-Uniform Rational B-Spline curve
have no more than a sequence of 'k' consecutive identical values or no more than 'k +
1' consecutive same values at the beginning or end of Non-Uniform Rational B-Spline
curve.
ORA-13076: incorrect knot value sequence for SDO_GEOMETRY object
Cause: An incorrect knot value sequence was passed for a Non-Uniform Rational BSpline curve.
Action: Ensure the knot value sequence passed for the Non-Uniform Rational BSpline curve is a normalized vector beginning at zero and ending at one.
ORA-13077: incorrect start or end point for subelement of a compound curve
Cause: The end point of a subelement for a compound curve was not equal to the start
point of the next subelement, or the start point of a subelement was not equal to the
end point of the previous subelement and one of the subelements was a NURBS
curve.
Action: Ensure that the end point of each subelement is equal to the start point of the
next subelement and that the start point of each subelement is equal to the end point
of the previous subelement when one of the subelements is a NURBS curve.
ORA-13107: operation not supported for Non-Uniform Rational B-Spline type
Cause: This operation cannot be executed for Non-Uniform Rational B-Spline curves.
Action: Specify a geometry that does not contain a Non-Uniform Rational B-Spline
curve type.
ORA-13108: spatial table string not found
Cause: The specified spatial table does not exist.
Action: Check the Spatial data dictionary to make sure that the table is registered.
ORA-13109: spatial table string exists
Cause: The specified spatial table is registered in the Spatial data dictionary.
Action: Remove the existing table from the Spatial data dictionary or use a different
name.
ORA-13110: cannot drop topology with associated topo_geometry tables
Cause: The drop_topology procedure was invoked for a topology that has assocated
topo_geometry layers with it.
Action: Delete the topo_geometry layers from the topology before dropping the
topology. Use SDO_TOPO.delete_topo_geometry_layer to delete topo_geometry
layers from the topology.
ORA-13111: cannot add topo_geometry layer [string] to topology
Cause: It was not possible to add the specified topo_geometry layer to the topology.
Action: Make sure the topo_geometry layer table exists in the database.
ORA-13112: cannot delete topo_geometry layer [string] from topology
Cause: It was not possible to delete the specified topo_geometry layer from the
topology.
Action: Check USER_SDO_TOPO_METADATA to see if the specified topo_geometry

layer is part of the topology. Only those topo_geometry layers which are part of the
topology can be deleted from it.
ORA-13113: invalid tg_layer_id in sdo_topo_geometry constructor
Cause: An invalid layer_id was passed to the SDO_TOPO_GEOMETRY constructor.
Action: Valid layer_ids are obtained by adding a topo_geometry layer to the
topology. Check USER_SDO_TOPO_METADATA to find out the layer_id for an
existing topo_geometry layer.
ORA-13114: [string]_NODE$ table does not exist
Cause: The NODE$ table for the topology did not exist in the database.
Action: There is a severe corruption of the topology. Call Oracle Support Services
with the error number.
ORA-13115: [string]_EDGE$ table does not exist
Cause: The EDGE$ table for the topology did not exist in the database.
ORA-13116: [string]_FACE$ table does not exist
Cause: The FACE$ table for the topology did not exist in the database.
ORA-13117: [string]_RELATION$ table does not exist
Cause: The RELATION$ table for the topology did not exist in the database.
ORA-13118: invalid node_id [string]
Cause: A topology node operation was invoked with an invalid node_id.
Action: Check the topology node$ table to see if the specified node_id exists in the
topology.
ORA-13119: invalid edge_id [string]
Cause: A topology edge operation was invoked with an invalid edge_id.
Action: Check the topology edge$ table to see if the specified edge_id exists in the
topology.
ORA-13120: invalid face_id [string]
Cause: A topology face operation was invoked with an invalid face_id.
Action: Check the topology face$ table to see if the specified face_id exists in the
topology.
ORA-13121: layer type type mismatch with topo_geometry layer type
Cause: The tg_type in SDO_TOPO_GEOMETRY constructor did not match the type
specified for the layer.
Action: Check the USER_SDO_TOPO_METADATA view to see the layer type for the
layer and use it in the constructor.
ORA-12700 to ORA-19400 69-25
ORA-13122: invalid topo_geometry specified

Cause: The SDO_TOPO_GEOMETRY object passed into the function/operator was
not valid.
Action: Check the SDO_TOPO_GEOMETRY object and verify that it is a valid
topo_geometry object.
ORA-13123: invalid TOPOLOGY name specified
Cause: The create_topo operation requires a unique TOPOLOGY name, that already
does not exist in the database.
Action: Check to see if there is already an entry in the
USER_SDO_TOPO_METADATA (or the MDSYS.SDO_TOPO_METADATA_TABLE)
with this topology name.
ORA-13124: unable to determine column id for column string
ORA-13125: partition key is already set
Cause: A partition key is already set for the spatial table.
Action: Only one partition key can be specified per spatial table.
ORA-13126: unable to determine class for spatial table string
ORA-13127: failed to generate target partition
ORA-13128: current tiling level exceeds user specified tiling level
ORA-13129: HHCODE column string not found
Cause: The specified spatial column does not exist.
Action: Verify that the specified column is a spatial column by checking the Spatial
data dictionary.
ORA-13135: failed to alter spatial table
ORA-13136: null common code generated
ORA-13137: failed to generate tablespace sequence number
ORA-13138: could not determine name of object string

ORA-13139: could not obtain column definition for string
ORA-13140: invalid target type
Cause: The specified target type is not valid.
Action: Substitute a valid target type. Valid target types are TABLE and VIEW.
ORA-13141: invalid RANGE window definition
Cause: The RANGE window specified is not correctly defined.
Action: A RANGE window is defined by specifying the lower and upper boundary of
each dimension as a pair of values (e.g.:
lower_bound1,upper_bound1,lower_bound2,upper_bound2,...). There should be an
even number of values.
ORA-13142: invalid PROXIMITY window definition
Cause: The PROXIMITY window specified is not correctly defined.
Action: A PROXIMITY window is defined by specifying a center point and a radius.
The center point is defined by ND values. There should be ND+1 values.
ORA-13143: invalid POLYGON window definition
Cause: The POLYGON window specified is not correctly defined.
Action: A POLYGON window is defined by specifying N pairs of values that
represent the vertices of the polygon. There should be an even number of values.
ORA-13144: target table string not found
ORA-13145: failed to generate range list
ORA-13146: could not find table substitution variable string
Cause: The partition name substitution variable %s was not found in the SQL filter.
Action: The substitution variable %s must be in the SQL filter to indicate where that
partition name should be placed.
ORA-13147: failed to generate MBR
ORA-13148: failed to generate SQL filter
ORA-12700 to ORA-19400 69-27
ORA-13149: failed to generate next sequence number for spatial table string
ORA-13150: failed to insert exception record
Cause: Operation failed to insert a record into the exception table.
Action: Fix any other errors reported.
ORA-13151: failed to remove exception record
Cause: Operation failed to remove a record from the exception table.
Action: Fix any other errors reported.
ORA-13152: invalid HHCODE type
Cause: Specified HHCODE type is not valid.
Action: Substitute a valid HHCODE type. Valid HHCODE types are POINT and
LINE.
ORA-13153: invalid high water mark specified
Cause: The high water mark must be greater than or equal to zero.
Action: Make sure that the high water mark is an integer greater than or equal to zero.
ORA-13154: invalid precision specified
Cause: The precision specified is out of range.
Action: The precision must be an integer greater than or equal to zero.
ORA-13155: invalid number of dimensions specified
Cause: The number of dimensions specified is out of range.
Action: The number of dimension must be between 1 and 32.
ORA-13156: table to be registered string.string is not empty
Cause: The specified table has rows in it.
Action: Make sure that the table to be registered is empty.
ORA-13157: Oracle error ORAstring encountered while string
Cause: The specified Oracle error was encountered.
Action: Correct the Oracle error.
ORA-13158: Oracle object string does not exist
Cause: The specified object does not exist.
Action: Verify that the specified object exists.
ORA-13159: Oracle table string already exists
Cause: The specified table already exists.
Action: Drop the specified table.
ORA-13181: unable to determine length of column string_SDOINDEX.SDO_CODE
Cause: The length of the SDO_CODE column in the layer_SDOINDEX table could not
be determined.
Action: Make sure that the layer_SDOINDEX table exists with the SDO_CODE
column. Verify that the appropriate privileges exist on the table. Then retry the
operation.
ORA-13182: failed to read element string.string.string
Cause: The specified element could not be read from the layer_SDOGEOM table.
Action: Verify that the specified element exists in the table. Then retry the operation.
ORA-13183: unsupported geometric type for geometry string.string
Cause: The geometry type in the layer_SDOGEOM table is unsupported.
Action: Modify the geometry type to be one of the supported types.
ORA-13184: failed to initialize tessellation package
Cause: Initialization of the tessellation package failed.
Action: Record the error messages that are returned and contact Oracle Support
Services.
ORA-13185: failed to generate initial HHCODE
Services.
ORA-13186: fixed tile size tessellation failed
Services.
ORA-13187: subdivision failed
Services.
ORA-13188: cell decode failed
Services.
ORA-13189: recursive SQL parse failed
Services.
ORA-13190: recursive SQL fetch failed
Services.
ORA-13191: failed to read SDO_ORDCNT value
Services.
ORA-12700 to ORA-19400 69-29
ORA-13192: failed to read number of element rows

Services.
ORA-13193: failed to allocate space for geometry
Cause: There was insufficient memory to read the geometry from the database.
Action: Validate the geometry. Record the error messages that are returned and
ORA-13194: failed to decode supercell
ORA-13195: failed to generate maximum tile value
Services.
ORA-13196: failed to compute supercell for element string.string.string
Cause: The system was unable to compute the minimum bounding HHCODE or
supercell for the geometry.
Action: Another error might accompany this error. Correct the accompanying error.
Also, validate the geometry for correctness.
ORA-13197: element string.string.string is out of range
Cause: Tessellation did not generate any tiles for this element. This error could be
caused if the geometry definition puts the geometry outside the domain defined in
the layer_SDODIM table.
Action: Verify that the geometry is valid and within the defined domain.
ORA-13198: Spatial error: string
Cause: Internal error in some Oracle Spatial stored procedure.
Action: Record the sequence of procedure calls or events that preceded this error, and
contact Oracle Support Services if the error message text does not clearly specify the
cause of the error.
ORA-13199: string
ORA-13200: internal error [string] in spatial indexing.
Action: Contact Oracle Support Services with the exact error text.
ORA-13201: invalid parameters supplied in CREATE INDEX statement
Cause: An error was encountered while trying to parse the parameters clause for the
spatial CREATE INDEX statement.
Action: Check the Oracle Spatial documentation for the number, syntax, and
semantics of expected parameters for spatial index creation.
ORA-13202: failed to create or insert into the SDO_INDEX_METADATA table

Cause: An error was encountered while trying to create the
SDO_INDEX_METADATA table or insert data into it.
Action: Verify that the current user has CREATE TABLE privilege and that the user
has sufficient quota in the default or specified tablespace.
ORA-13203: failed to read USER_SDO_GEOM_METADATA view
Cause: An error encountered while trying to read the
USER_SDO_GEOM_METADATA view.
Action: Check that USER_SDO_GEOM_METADATA has an entry for the current
geometry table.
ORA-13204: failed to create spatial index table
Cause: An error was encountered while trying to create the index table.
Action: Check that user has CREATE TABLE privilege in the current schema and that
the user has sufficient quota in the default or specified tablespace.
ORA-13205: internal error while parsing spatial parameters
Cause: An internal error was encountered while parsing the spatial parameters.
Action: Check that the parameters passed in the parameter string are all valid.
ORA-13206: internal error [string] while creating the spatial index
Cause: An internal error was encountered while creating the spatial index.
ORA-13207: incorrect use of the [string] operator
Cause: An error was encountered while evaluating the specified operator.
Action: Check the parameters and the return type of the specified operator.
ORA-13208: internal error while evaluating [string] operator
Cause: An internal error was encountered.
ORA-13209: internal error while reading SDO_INDEX_METADATA table
Cause: An internal error was encountered while trying to read the
SDO_INDEX_METADATA table.
Action: Contact Oracle Support Services. Note this and accompanying error numbers.
ORA-13210: error inserting data into the index table
Cause: An error was encountered while trying to insert data into the index table.
Likely causes are: - Insufficient quota in the current tablespace - User does not
appropriate privileges
Action: Check the accompanying error messages.
ORA-13211: failed to tessellate the window object
Cause: An internal error was encountered while trying to tessellate the window
object.
Action: Verify the geometric integrity of the window object using the
VALIDATE_GEOMETRY_WITH_CONTEXT procedure.
ORA-12700 to ORA-19400 69-31
ORA-13212: failed to compare tile with the window object

Cause: The spatial relationship between a generated tile and the specified window
object could not be determined.
Action: This is an internal error. Verify the geometry using the
return any errors, note any accompanying errors and contact Oracle Support Services.
ORA-13213: failed to generate spatial index for window object
Cause: Another error, indicating the real cause of the problem, should accompany this
error.
ORA-13214: failed to compute supercell for window object
Cause: The system was unable to compute the minimum bounding tile or supercell
for the geometry.
ORA-13215: window object is out of range
Cause: Tessellation did not generate any tiles for this geometry. This error could be
caused if the geometry definition puts the geometry outside the domain defined in
the USER_SDO_GEOM_METADATA view.
Action: Verify that the geometry is valid and within the defined domain.
ORA-13216: failed to update spatial index
Cause: Another error will accompany this message that will indicate the problem.
ORA-13217: invalid parameters supplied in ALTER INDEX statement
Cause: An error was encountered while trying to parse the parameters clause for the
spatial ALTER INDEX statement.
Action: Check the Oracle Spatial documentation for the number, syntax, and
semantics of expected parameters for the spatial ALTER INDEX statement.
ORA-13218: max number of supported index tables reached for [string] index
Cause: An add_index parameter was passed to ALTER INDEX when the number of
existing index tables is already at maximum.
Action: Delete one of the index tables before adding another index table.
ORA-13219: failed to create spatial index table [string]
Cause: An error was encountered while trying to create the index table.
Action: There is a table in the index's schema with the specified name. The CREATE
INDEX statement will try to create an index table with this name. Either rename this
table or change the name of the index.
ORA-13220: failed to compare tile with the geometry
Cause: The spatial relationship between a generated tile and the specified geometry
could not be determined.
Action: This is an internal error. Validate the geometry using the

return any errors, note any errors that accompany ORA-13220 and contact Oracle
Support Services.
ORA-13221: unknown geometry type in the geometry object
Cause: The SDO_GTYPE attribute in the geometry object contains an invalid value
Action: Redefine the geometric type in the geometry table using one of the supported
SDO_GTYPE values. See the Oracle Spatial documentation for an explanation of
SDO_GTYPE and its possible values.
ORA-13222: failed to compute supercell for geometry in string
Cause: The system was unable to compute the minimum bounding tile or supercell
for a geometry in the specified table.
ORA-13223: duplicate entry for string in SDO_GEOM_METADATA
Cause: There are duplicate entries for the given table and column value pair in the
Action: Check that the specified table and geometry column names are correct. There
should be only one entry per table, geometry column pair in the
ORA-13224: zero tolerance specified for layer in USER_SDO_GEOM_METADATA
Cause: A tolerance of zero or NULL is supplied for a layer in
Action: Check the tolerance specified to make sure it is a positive value.
ORA-13225: specified index table name is too long for a spatial index
Cause: An index table name is specified which is longer than the supported length of
the spatial index table name.
Action: Check the supported size of the index table name and reduce the size of the
index name.
ORA-13226: interface not supported without a spatial index
Cause: The geometry table does not have a spatial index.
Action: Verify that the geometry table referenced in the spatial operator has a spatial
index on it.
ORA-13227: SDO_LEVEL values for the two index tables do not match
Cause: The SDO_LEVEL values for the two index tables used in the spatial join
operator do not match.
Action: Verify that two compatible indexes are used for the spatial join operator.
Quadtree indexes are compatible if they have the same SDO_LEVEL and
SDO_NUMTILES values
ORA-13228: spatial index create failed due to invalid type
Cause: An Attempt was made to create a spatial index on a column of type other than
SDO_GEOMETRY.
Action: Make sure that the index is created on a column of type SDO_GEOMETRY.
ORA-12700 to ORA-19400 69-33
ORA-13230: failed to create temporary table [string] during R-tree creation

Cause: The specified temporary table either already exists or there is not enough
tablespace.
Action: Delete the table if it already exists and verify if the current user has CREATE
TABLE privileges and has sufficient space in the default or specified tablespace.
ORA-13231: failed to create index table [string] during R-tree creation
Cause: The specified index table either already exists or there is not enough
tablespace.
Action: Delete the table if it already exists and verify if the current user has CREATE
TABLE privileges and has sufficient space in the default or specified tablespace. If
that fails to correct the problem, contact Oracle Support Services.
ORA-13232: failed to allocate memory during R-tree creation
Cause: This feature assumes a minimum of 64K memory for bulk creation.
Action: Create the index for a small subset of the data. Then, use transactional insert
operations for the rest of the data.
ORA-13233: failed to create sequence number [string] for R-tree
Cause: The specified sequence number exists.
Action: Delete the sequence object, or contact Oracle Support Services.
ORA-13234: failed to access R-tree-index table [string]
Cause: The index table is either deleted or corrupted.
Action: Rebuild the index or contact Oracle Support Services with accompanying
error messages.
ORA-13236: internal error in R-tree processing: [string]
Cause: An internal error occurred in R-tree processing.
Action: Contact Oracle Support Services with the message text.
ORA-13237: internal error during R-tree concurrent updates: [string]
Cause: An inconsistency is encountered during concurrent updates, possibly due to
the use of serializable isolation level.
Action: Change the isolation level to "read committed" using the ALTER SESSION
statement, or contact Oracle Support Services with the message text.
ORA-13239: sdo_dimensionality not specified during n-d R-tree creation
Cause: An error occurred in reading the dimensionality parameter
Action: Check the documentation for a valid range, and specify the dimensionality as
a parameter.
ORA-13240: specified dimensionality greater than that of the query mbr
Cause: An error occurred because of too few values in the query minimum bounding
rectangle (MBR).
Action: Omit the dimensionality, or use the dimensionality of the query.
ORA-13241: specified dimensionality does not match that of the data
Cause: An error occurred because the dimensionality specified in the CREATE
INDEX statement does not match that of the data.
Action: Change the statement to reflect the data dimensionality.
ORA-13243: specified operator is not supported for 3- or higher-dimensional R-tree

Cause: Currently, an R-tree index with three or more index dimensions can be used
only with the SDO_FILTER operator.
Action: Use the SDO_FILTER operator, and check the documentation for the
querytype parameter for SDO_FILTER; or contact Oracle Support Services.
ORA-13249: string
Cause: An internal error was encountered in the extensible spatial index component.
The text of the message is obtained from some other server component.
ORA-13250: insufficient privileges to modify metadata table entries
Cause: The user requesting the operation does not have the appropriate privileges on
the referenced tables.
Action: Check that the specified feature and geometry table names are correct, and
then verify that the current user has at least SELECT privilege on those tables.
ORA-13251: duplicate entry string in metadata table
Cause: The specified entry already exists in the metadata table.
Action: Check that the specified feature and geometry table names are correct. A
feature-geometry table association should be registered only once.
ORA-13260: layer table string does not exist
Cause: Data migration source table layer_SDOGEOM does not exist.
Action: Ensure that the specified layer name is correct and that the corresponding
spatial layer tables exist in the current schema.
ORA-13261: geometry table string does not exist
Cause: The specified geometry table does not exist in the current schema.
Action: Create a table containing a column of type SDO_GEOMETRY and a column of
type NUMBER for the GID values.
ORA-13262: geometry column string does not exist in table string
Cause: The specified table does not have a column of type SDO_GEOMETRY.
Action: Alter or re-create the table such that it includes a column of type
SDO_GEOMETRY and a column of type NUMBER.
ORA-13263: column string in table string is not of type SDO_GEOMETRY
Cause: The column intended for storing the geometry is not of type
SDO_GEOMETRY.
Action: Alter the column definition to be of type SDO_GEOMETRY.
ORA-13264: geometry identifier column string does not exist in table string
Cause: The specified table does not contain a GID column.
Action: Confirm that the GID column name was correctly specified and that it exists
in the specified table.
ORA-13265: geometry identifier column string in table string is not of type
NUMBER
Cause: GID column is not of type NUMBER.
ORA-12700 to ORA-19400 69-35
Action: Alter the table definition such that the column containing the geometry
identifier (GID) is of type NUMBER.
ORA-13266: error inserting data into table string
Cause: An OCI error occurred, or the user has insufficient quota in the active
tablespace, or the rollback segments are too small.
Action: There should be an accompanying error message that indicates the cause of
the problem. Take appropriate action to correct the indicated problem.
ORA-13267: error reading data from layer table string
Cause: There was an error reading the geometry data from the layer_SDOGEOM
table.
Action: Verify that layer_SDOGEOM and layer_SDODIM exist. If they do exist, run
VALIDATE_LAYER_WITH_CONTEXT on the specified layer.
ORA-13268: error obtaining dimension from USER_SDO_GEOM_METADATA
Cause: There is no entry in the USER_SDO_GEOM_METADATA view for the
specified geometry table.
Action: Insert an entry for the destination geometry table with the correct dimension
information.
ORA-13269: internal error [string] encountered when processing geometry table
Action: Contact Oracle Support Services with the exact error message text.
ORA-13270: OCI error \nstring
Cause: An OCI error occurred while processing the layer or geometry tables.
Action: Take the appropriate steps to correct the OCI-specific error.
ORA-13271: error allocating memory for geometry object
Cause: Insufficient memory.
Action: Make more memory available to the current session/process.
ORA-13272: geometric object string in table string is invalid
Cause: The specified object failed the geometric integrity checks performed by the
validation function.
Action: Check the Oracle Spatial documentation for information about the geometric
integrity checks performed by VALIDATE_GEOMETRY_WITH_CONTEXT and
correct the geometry definition if required.
ORA-13273: dimension metadata table string does not exist
Cause: The layer_SDODIM table does not exist.
Action: Verify that the specified layer name is correct and that the layer_SDODIM
table exists in the current schema.
ORA-13274: operator invoked with non-compatible SRIDs
Cause: A Spatial operator was invoked with a window geometry with an SRID but
the layer has no SRID; or the window has no SRID but the layer has an SRID.
Action: Make sure that the layer and window both have an SRID or that they both do
not have an SRID.
ORA-13275: spatial index creation failure on unsupported type

Cause: An attempt was made to create a spatial index create on a column that is not of
type SDO_GEOMETRY.
Action: A spatial index can only be created on a column of type SDO_GEOMETRY.
Make sure the indexed column is of type SDO_GEOMETRY.
ORA-13276: internal error [string] in coordinate transformation
Cause: OCI internal error.
ORA-13278: failure to convert SRID to native format
ORA-13281: failure in execution of SQL statement to retrieve WKT
Cause: OCI internal error, or SRID does not match a table entry.
Action: Check that a valid SRID is being used.
ORA-13282: failure on initialization of coordinate transformation
Cause: Parsing error on source or destination coordinate system WKT, or
incompatible coordinate systems.
Action: Check the validity of the WKT for table entries, and check if the requested
transformation is valid.
ORA-13283: failure to get new geometry object for conversion in place
ORA-13284: failure to copy geometry object for conversion in place
ORA-13285: Geometry coordinate transformation error
Cause: A coordinate pair was out of valid range for a conversion/projection.
Action: Check that data to be transformed is consistent with the desired conversion/
projection.
ORA-13287: can't transform unknown gtype
Cause: A geometry with a gtype of <= 0 was specified for transformation. Only a
gtype >= 1 is allowed.
Action: Check the Oracle Spatial documentation for SDO_GTYPE values, and specify
a value whose last digit is 1 or higher.
ORA-13288: point coordinate transformation error
Cause: An internal error occurred while transforming points.
ORA-13290: the specified unit is not supported
Cause: An Oracle Spatial function was called with an unknown UNIT value.
Action: Check Spatial documentation for the supported units, and call the function
with the correct UNIT parameter.
ORA-12700 to ORA-19400 69-37
ORA-13291: conversion error between the specified unit and standard unit
Cause: Cannot convert the specified unit from/to standard unit for linear distance,
angle, or area.
Action: Check the unit specification and respecify it.
ORA-13292: incorrect ARC_TOLERANCE specification
Cause: When a SDO_BUFFER or SDO_AGGR_BUFFER function is called on a
geodetic geometry, or SDO_ARC_DENSIFY is called, ARC_TOLERANCE must be
specified, and it should not be less than the tolerance specified for the geometry.
Action: Check ARC_TOLERANCE specification and make sure it is correct.
ORA-13293: cannot specify unit for geometry without a georeferenced SRID
Cause: An Oracle Spatial function with a UNIT parameter was called on a geometry
without a georeferenced SRID.
Action: Make sure that spatial functions with UNIT parameters are only called on
geometries with georeferenced SRIDs.
ORA-13294: cannot transform geometry containing circular arcs
Cause: It is impossible to transform a 3-point representation of a circular arc without
distortion.
Action: Make sure a geometry does not contain circular arcs.
ORA-13295: geometry objects are in different coordinate systems
Cause: An Oracle Spatial function was called with two geometries that have different
SRIDs.
Action: Transform geometry objects to be in the same coordinate system and call the
spatial function.
ORA-13296: incorrect coordinate system specification
Cause: Wrong numbers in WKT for Earth radius or flattening for the current SRID.
Action: Check WKT in the MDSYS.CS_SRS table for Earth radius and inverse
flattening.
ORA-13300: single point transform error
Cause: Low-level coordinate transformation error trap.
ORA-13303: failure to retrieve a geometry object from a table
ORA-13304: failure to insert a transformed geometry object in a table
ORA-13330: invalid MASK
Cause: The MASK passed to the RELATE function is not valid.
Action: Verify that the mask is not NULL. See the Oracle Spatial documentation for a
list of supported masks.
ORA-13331: invalid LRS segment

Cause: The given LRS segment was not a valid line string.
Action: A valid LRS geometric segment is a line string geometry in Oracle Spatial. It
could be a simple or compound line string (made of lines or arcs, or both). The
dimension information must include the measure dimension as the last element in the
Oracle Spatial metadata. Currently, the number of dimensions for an LRS segment
must be greater than 2 (x/y or longitude/latitude, plus measure)
ORA-13332: invalid LRS point
Cause: The specified LRS point was not a point geometry with measure information.
Action: Check the given point geometry. A valid LRS point is a point geometry in
Oracle Spatial with an additional dimension for measure.
ORA-13333: invalid LRS measure
Cause: The given measure for linear referencing was out of range.
Action: Redefine the measure.
ORA-13334: LRS segments not connected
Cause: The specified geometric segments are not connected.
Action: Check the start/end points of the given geometric segments.
ORA-13335: LRS measure information not defined
Cause: The measure information of a geometric segment was not assigned (IS NULL).
Action: Assign/define the measure information. An LRS geometric segment is
defined if its start and end measure are assigned (non-null).
ORA-13336: failure in converting standard diminfo/geometry to LRS dim/geom
Cause: There is no room for the measure dimension in the given diminfo, or the
specified standard geometry is not a point a line string.
Action: Check if the diminfo dimensions are less than 3 or if the geometry type is
point or line string.
ORA-13337: failure in concatenating LRS polygons
Cause: LRS concatenation involving LRS polygons is not supported.
Action: Check the geometry and element types to make sure the concatenate
operation is not called with a polygon type.
ORA-13338: failure in reversing LRS polygon/collection geometry
Cause: Reversing an LRS polygon/collection geometry produces an invalid geometry.
Action: Check the geometry type to make sure this operation is called on non-polygon
geometries.
ORA-13339: LRS polygon clipping across multiple rings
Cause: Clipping (dynseg) a polygon across multiple rings is not allowed.
Action: Polygon clipping is allowed only for a single ring.
ORA-13340: a point geometry has more than one coordinate
Cause: A geometry, specified as being a point, has more than one coordinate in its
definition.
ORA-12700 to ORA-19400 69-39
Action: A point has only one coordinate. If this geometry is intended to represent a
point cluster, line, or polygon, set the appropriate SDO_GTYPE or SDO_ETYPE value.
If this is a single point object, remove the extraneous coordinates from its definition.
ORA-13341: a line geometry has fewer than two coordinates
Cause: A geometry, specified as being a line, has fewer than two coordinates in its
definition.
Action: A line must consist of at least two distinct coordinates. Correct the geometric
definition, or set the appropriate SDO_GTYPE or SDO_ETYPE attribute for this
geometry.
ORA-13342: an arc geometry has fewer than three coordinates
Cause: A geometry, specified as being an arc, has fewer than three coordinates in its
definition.
Action: An arc must consist of at least three distinct coordinates. Correct the
geometric definition, or set the appropriate SDO_GTYPE or SDO_ETYPE attribute for
this geometry.
ORA-13343: a polygon geometry has fewer than four coordinates
Cause: A geometry, specified as being a polygon, has fewer than four coordinates in
its definition.
Action: A polygon must consist of at least four distinct coordinates. Correct the
geometric definition, or set the appropriate SDO_GTYPE or SDO_ETYPE attribute for
this geometry.
ORA-13344: an arcpolygon geometry has fewer than five coordinates
Cause: A geometry, specified as being an arcpolygon, has fewer than five coordinates
in its definition.
Action: An arcpolygon must consist of at least five coordinates. An arcpolygon
consists of an ordered sequence of arcs, each of which must be described using three
coordinates. Since arcs are connected the end-point of the first is the start of the
second and does not have to be repeated. Correct the geometric definition, or set the
appropriate SDO_GTYPE or SDO_ETYPE attribute for this geometry.
ORA-13345: a compound polygon geometry has fewer than five coordinates
Cause: A geometry, specified as being a compound polygon, has fewer than five
coordinates in its definition.
Action: A compound polygon must contain at least five coordinates. A compound
polygon consists of at least one arc and one line, each of which must be described
using three and at least two distinct coordinates respectively. Correct the geometric
definition, or set the appropriate SDO_GTYPE or SDO_ETYPE attribute for this
geometry.
ORA-13346: the coordinates defining an arc are collinear
Cause: Invalid definition of an arc. An arc is defined using three non-collinear
coordinates.
Action: Alter the definition of the arc, or set the SDO_ETYPE or SDO_GTYPE to the
line type.
ORA-13347: the coordinates defining an arc are not distinct
Cause: Two or more of the three points defining an arc are the same.
Action: Alter the definition of the arc to ensure that three distinct coordinate values
are used.
ORA-13348: polygon boundary is not closed

Cause: The boundary of a polygon does not close.
Action: Alter the coordinate values or the definition of the SDO_GTYPE or
SDO_ETYPE attribute of the geometry.
ORA-13349: polygon boundary crosses itself
Cause: The boundary of a polygon intersects itself.
Action: Correct the geometric definition of the object.
ORA-13350: two or more rings of a complex polygon touch
Cause: The inner or outer rings of a complex polygon touch.
Action: All rings of a complex polygon must be disjoint. Correct the geometric
definition of the object.
ORA-13351: two or more rings of a complex polygon overlap
Cause: The inner or outer rings of a complex polygon overlap.
Action: All rings of a complex polygon must be disjoint. Correct the geometric
definition of the object.
ORA-13352: the coordinates do not describe a circle
Cause: The set of coordinates used to describe a circle are incorrect.
Action: Confirm that the set of coordinates actually represent points on the
circumference of a circle.
ORA-13353: ELEM_INFO_ARRAY not grouped in threes
Cause: The ELEM_INFO_ARRAY in an SDO_GEOMETRY definition has more or
fewer elements than expected.
Action: Confirm that the number of elements in ELEM_INFO_ARRAY is divisible by
3.
ORA-13354: incorrect offset in ELEM_INFO_ARRAY
Cause: The offset field in ELEM_INFO_ARRAY of an SDO_GEOMETRY definition
references an invalid array subscript in SDO_ORDINATE_ARRAY.
Action: Confirm that the offset is a valid array subscript in
SDO_ORDINATE_ARRAY.
ORA-13355: SDO_ORDINATE_ARRAY not grouped by number of dimensions
specified
Cause: The number of elements in SDO_ORDINATE_ARRAY is not a multiple of the
number of dimensions supplied by the user.
Action: Confirm that the number of dimensions is consistent with data representation
in SDO_ORDINATE_ARRAY.
ORA-13356: adjacent points in a geometry are redundant
Cause: There are repeated points in the sequence of coordinates.
Action: Remove the redundant point.
ORA-13357: extent type does not contain 2 points
Cause: Extent type should be represented by two points: lower left and upper right.
Action: Confirm that there are only two points for an extent type.
ORA-12700 to ORA-19400 69-41
ORA-13358: circle type does not contain 3 points

Cause: Circle type should be represented by three distinct points on the
circumference.
Action: Confirm that there are only three points for a circle type.
ORA-13359: extent does not have an area
Cause: The two points representing the extent are identical.
Action: Confirm that the two points describing the extent type are distinct.
ORA-13360: invalid subtype in a compound type
Cause: This subtype is not allowed within the ETYPE specified.
Action: Check the Oracle Spatial documentation for type definitions.
ORA-13361: not enough sub-elements within a compound ETYPE
Cause: The compound type declare more sub-elements than actually defined.
Action: Confirm that the number of sub-elements is consistent with the compound
type declaration.
ORA-13362: disjoint sub-element in a compound polygon
Cause: Compound polygon must describe an enclosed area.
Action: Confirm that all sub-elements are connected.
ORA-13363: no valid ETYPE in the geometry
Cause: None of the ETYPEs within the geometry is supported.
Action: Confirm that there is at least one valid ETYPE.
ORA-13364: layer dimensionality does not match geometry dimensions
Cause: The spatial layer has a geometry with a different dimensions than the
dimensions specified for the layer.
Action: Make sure that all geometries in a layer have the same dimensions and that
they match the dimensions in the SDO_DIM_ARRAY object for the layer in the
ORA-13365: layer SRID does not match geometry SRID
Cause: The spatial layer has a geometry with a different SRID than the SRID specified
for the layer.
Action: Make sure that all geometries in a layer have the same SRID and that the
SRIDs match the SRID for the layer in the USER_SDO_GEOM_METADATA view.
ORA-13366: invalid combination of interior exterior rings
Cause: In an Oracle Spatial geometry, interior and exterior rings are not used
consistently.
Action: Make sure that the interior rings corresponding to an exterior ring follow the
exterior ring in the ordinate array.
ORA-13367: wrong orientation for interior/exterior rings
Cause: In an Oracle Spatial geometry, the exterior and/or interior rings are not
oriented correctly.
Action: Be sure that the exterior rings are oriented counterclockwise and the interior
rings are oriented clockwise.
ORA-13368: simple polygon type has more than one exterior ring
Cause: In a polygon geometry there is more than one exterior ring.
Action: Set the type to be multipolygon if more than one exterior ring is present in the
geometry.
ORA-13369: invalid value for etype in the 4-digit format
Cause: A 4-digit etype for a non-polygon type element is used, or the orientation is
not a valid orientation for interior/exterior rings of the polygon.
Action: Correct the geometry definition.
ORA-13370: failure in applying 3D LRS functions
Cause: Only non-geodetic 3D line string geometries (made of line segments) are
supported for 3D LRS functions.
Action: Check the geometry and element types and the SRID values.
ORA-13371: invalid position of measure dimension
Cause: LRS measure dimension has to be after spatial dimensions. The position has to
be either 3rd or 4th in the dim_info_array.
Action: Check the geometry's gtype and its position in the dim_info_array.
ORA-13372: failure in modifying metadata for a table with spatial index
Cause: Modifying the metadata after the index is created will cause an inconsistency
between the geometry's gtype and diminfo.
Action: Modify (or Prepare) metadata before creating an index on the
SDO_GEOMETRY column.
ORA-13373: invalid line segment in geodetic data
Cause: A geodetic line segment was not less than half of a great circle.
Action: Densify the line by adding points.
ORA-13374: SDO_MBR not supported for geodetic data
Cause: The SDO_MBR functionality is not supported for geodetic data.
Action: Find an alternative function that can be used in this context.
ORA-13375: the layer is of type [string] while geometry inserted has type [string]
Cause: The layer has a type that is different or inconsistent with the type of the
current geometry.
Action: Change the geometry type to agree with the layer type, or change the layer
type to agree with the geometry type.
ORA-13376: invalid type name specified for layer_gtype parameter
Cause: An invalid type name is specified for the layer_gtype constraint.
Action: See the Spatial documentation for of valid keywords that can be used in
defining a layer_gtype constraint.
ORA-13377: invalid combination of elements with orientation
Cause: An element of the geometry has orientation specified while some other
element has no orientation specified (4-digit etype).
Action: Make sure all the polygon elements have orientation specified using the 4digit etype notation.
ORA-12700 to ORA-19400 69-43
ORA-13378: invalid index for element to be extracted

Cause: An invalid (or out of bounds) index was specified for extracting an element
from a geometry.
Action: Make sure the parameters to the extract function are in the valid range for the
geometry.
ORA-13379: invalid index for sub-element to be extracted
Cause: An invalid (or out of bounds) index was specified for extracting a sub-element
from a geometry.
Action: Make sure the parameters to the extract function are in the valid range for the
geometry.
ORA-13380: network not found
Cause: The specified network was not found in the network metadata.
Action: Insert the network information in the USER_SDO_NETWORK_METADATA
view.
ORA-13381: table:string not found in network:string
Cause: The specified table was not found in the network metadata.
Action: Insert the table information in the USER_SDO_NETWORK_METADATA
view.
ORA-13382: geometry metadata (table:string column:string) not found in spatial
network:string
Cause: The specified geometry metadata was not found in the spatial network
metadata.
Action: Insert the spatial metadata information in the
USER_SDO_NETWORK_METADATA view.
ORA-13383: inconsistent network metadata: string
Cause: There was an inconsistency between the network metadata and the node/link
information.
Action: Check the network metadata and the node/link information.
ORA-13384: error in network schema: string
Cause: The network table(s) did not have required column(s)
Action: Check the network schema.
ORA-13385: error in network manager: [string]
Cause: There was an internal error in network manager.
Action: Contact Oracle Customer Support for more help.
ORA-13386: commit/rollback operation error: [string]
Cause: The index-level changes were not fully incorporated as part of the commit or
rollback operation.
Action: Correct the specified error and use the following statement: ALTER INDEX
index-name PARAMETERS ('index_status=synchronize');
ORA-13387: sdo_batch_size for array inserts should be in the range
[number,number]
Cause: The specified value for sdo_batch_size was too high or too low.
Action: Change the value to be in the specified range.

ORA-13388: invalid value for dst_spec parameter
Cause: The dst_spec parameter was specified in the wrong format.
Action: Check the documentation for this parameter.
ORA-13389: unable to compute buffers or intersections in analysis function
Cause: There was an internal error in computing the buffers or intersections in the
specified spatial analysis function.
Action: Modify the tolerance value in the USER_SDO_GEOM_METADATA view
before invoking the spatial analysis function.
ORA-13390: error in spatial analysis and mining function: [string]
Cause: There was an internal error in the specified analysis function.
Action: Contact Oracle Customer Support for more help.
ORA-13391: string
Cause: An attempt was made to violate GeoRaster management restrictions.
Action: Check the documentation for more detailed information.
ORA-13392: status report error: string
Cause: There was an error on status report related operation.
Action: Check the error message for details.
ORA-13393: null or invalid string parameter
Cause: The operation failed because the input parameter was null or invalid.
Action: Correct the parameter and try again.
ORA-13397: different dimension sizes in the input GeoRaster objects
Cause: The two input GeoRaster objects had different dimension sizes.
Action: Check the documentation and make sure the dimension size is same for both
input GeoRaster objects.
ORA-13398: invalid expression parameter: string
Cause: The expression parameter was not a valid math expression.
Action: Check the documentation and make sure the expression parameter is correct.
ORA-13399: invalid condition parameter: string
Cause: The condition parameter was not a valid boolean expression.
Action: Check the documentation and make sure the condition parameter is correct.
ORA-13400: duplicate entry for string in USER_SDO_GEOR_SYSDATA view
Cause: The current operation caused a duplicate RASTER_DATA_TABLE and
RASTER_ID combination to be inserted into the USER_SDO_GEOR_SYSDATA view.
Action: Ensure that the RASTER_DATA_TABLE and RASTER_ID combination to be
inserted into the USER_SDO_GEOR_SYSDATA view is unique.
ORA-13401: duplicate entry for string in USER_SDO_GEOR_SYSDATA view
Cause: The RASTER_DATA_TABLE and RASTER_ID columns contained the same
information in two or more rows in the USER_SDO_GEOR_SYSDATA view.
ORA-12700 to ORA-19400 69-45
Action: Ensure that the RASTER_DATA_TABLE and RASTER_ID columns in the

USER_SDO_GEOR_SYSDATA view contain the correct information, and that the
value pair is unique for each row.
ORA-13402: the rasterType is null or not supported
Cause: The specified rasterType was null or not supported.
Action: Check the documentation for the rasterType number and/or formats
supported by GeoRaster.
ORA-13403: invalid rasterDataTable specification: string
Cause: Each GeoRaster object must have an associated raster data table whose name
is unique among raster data table names in the database. If the GeoRaster object is not
empty and not blank, the raster data table must exist, be visible in the current schema,
be defined in the same schema as the GeoRaster data table, and be an object table of
SDO_RASTER type. However, one or more of these requirements were not met.
Action: Check the rasterDataTable specification and ensure that all relevant raster
data table requirements are met.
ORA-13404: invalid ultCoordinate parameter
Cause: The ultCoordinate array parameter had the wrong length or contained an
invalid value.
Action: Check the documentation, and make sure the ultCoordinate parameter is
correct.
ORA-13405: null or invalid dimensionSize parameter
Cause: The dimensionSize array parameter was null, had the wrong length, or
contained an invalid value.
Action: Check the documentation, and make sure the dimensionSize parameter is
correct.
ORA-13406: null or invalid GeoRaster object for output
Cause: The GeoRaster object for output was null or invalid.
Action: Make sure the GeoRaster object for output has been initialized properly.
ORA-13407: invalid storage parameterstring
Cause: The storage parameter contained an invalid specification.
Action: Check the documentation, and make sure the storage parameter is correct.
ORA-13408: invalid blockSize storage parameter
Cause: The blockSize storage parameter had the wrong length or contained invalid
value.
Action: Check the documentation, and make sure the blockSize storage parameter is
correct.
ORA-13409: null or invalid pyramidLevel parameter
Cause: The specified pyramidLevel parameter was null or invalid.
Action: Make sure the pyramidLevel parameter specifies a valid pyramid level value
for the GeoRaster object.
ORA-13410: invalid layerNumbers or bandNumbers parameter
Cause: The layerNumbers or bandNumbers parameter was invalid.
Action: Check the documentation and make sure the layerNumbers or bandNumbers
parameter is valid.
ORA-13411: subset results in null data set
Cause: The intersection of cropArea and source GeoRaster object was null.
Action: Check the documentation, and make sure the cropArea parameter is correct.
ORA-13412: invalid scale parameterstring
Cause: The scale parameter contained an invalid specification.
Action: Check the documentation, and make sure the scale parameter is correct.
ORA-13413: null or invalid resampling parameter
Cause: The resampling parameter was null or invalid.
Action: Check the documentation, and make sure the resampling parameter is correct.
ORA-13414: invalid pyramid parameter
Cause: The pyramid parameter was invalid.
Action: Check the documentation, and make sure the pyramid parameter is correct.
ORA-13415: invalid or out of scope point specification
Cause: The point position specified by the <ptGeom, layerNumber> or <rowNumber,
colNumber, bandNumber> parameter combination was invalid or out of scope.
Action: Make sure the parameter(s) specify a valid point that is or can be translated
into a cell position inside the cell space of the GeoRaster object.
ORA-13416: invalid geometry parameter
Cause: The geometry parameter did not specify a valid single-point geometry.
Action: Specify a valid single-point geometry.
ORA-13417: null or invalid layerNumber parameter
Cause: The layerNumber parameter was null or out of scope.
Action: Specify a valid layerNumber parameter.
ORA-13418: null or invalid parameter(s) for set functions
Cause: A parameter for set metadata operations was null or invalid.
Action: Check the documentation for information about the parameters.
ORA-13419: cannot perform mosaic operation: string
Cause: An attempt to perform a mosaic operation failed.
ORA-13420: the SRID of the geometry parameter was not null
Cause: The input geometry must be in the GeoRaster cell space, which has a null
SRID value.
Action: Make sure the geometry parameter has a null SRID.
ORA-13421: NULL or invalid cell value
Cause: The cell value was NULL or out-of-scope.
Action: Make sure the cell value is not NULL and is in the range as designated by the
cellDepth definition of the specified GeoRaster object.
ORA-12700 to ORA-19400 69-47
ORA-13422: invalid model coordinate parameter

Cause: The model coordinate array parameter had the wrong length or had null
ordinate element(s).
Action: Make sure the model coordinate parameter is valid.
ORA-13423: invalid cell coordinate parameter
Cause: The cell coordinate array parameter had the wrong length or had null ordinate
element(s).
Action: Make sure the cell coordinate parameter is valid.
ORA-13424: the GeoRaster object is not spatially referenced
Cause: The GeoRaster object was not spatially referenced.
Action: Make sure the GeoRaster object is spatially referenced.
ORA-13425: invalid background filling value parameter
Cause: The background filling value parameter was invalid either because the array
had the wrong size or because some of the element values were invalid.
Action: Make sure the parameter that specifies the background filling value is valid.
The size of the array must equal to either 1 (the value is for all bands) or the exact
band dimension size. The element values must be valid cell values as determined by
the cell depth.
ORA-13426: invalid window parameter
Cause: The specified window parameter was invalid.
Action: Specify a valid window parameter. Check the documentation for details.
ORA-13427: invalid bitmap mask
Cause: The bitmap mask was not a valid 1BIT GeoRaster object, or it had the wrong
dimension sizes.
Action: Make sure the bitmap mask is a valid 1BIT GeoRaster object with only one
band, and the row and column dimension sizes of the bitmap mask are the same as
those of the target GeoRaster object.
ORA-13428: invalid modelCoordinateLocation
Cause: The program [or user] specified a modelCoordinateLocation that is not
supported, or the modelCoordinateLocation of the GeoRaster object was wrong.
Action: Set or specify the modelCoordinateLocation to be CENTER (0) or
UPPERLEFT (1).
ORA-13429: invalid xCoefficients or yCoefficients parameter(s)
Cause: An attempt to perform a georeference operation failed. Possible reasons
include xCoefficients or yCoefficients having the wrong number of coefficients or
invalid coefficients.
Action: Check the documentation for supported coefficient specifications.
ORA-13430: the GeoRaster object has null attribute(s)
Cause: The metadata or rasterType of the GeoRaster object was null.
Action: This object may only be used as an output parameter of procedures or
functions. It is not valid for other purposes.
ORA-13431: GeoRaster metadata rasterType error

Cause: The rasterType in the metadata of the GeoRaster object was inconsistent with
the GeoRaster rasterType attribute.
Action: Make sure the rasterType in the metadata of the GeoRaster object and the
GeoRaster rasterType attribute have the same value.
ORA-13432: NULL or invalid blankCellValue
Cause: The blankCellValue element could not be found in the metadata of a blank
GeoRaster object, or the specified blankCellValue element value was NULL or
invalid.
Action: Call SDO_GEOR.setBlankCellValue to add blankCellValue to the metadata
whenever the isBlank element value is TRUE, and make sure that the specified
blankCellValue element value is not NULL and is in the range as designated by the
cellDepth definition of the GeoRaster object.
ORA-13433: GeoRaster metadata default RGB error
Cause: At least one of the defaultRed, defaultGreen, and defaultBlue values (logical
layer numbers) was zero, negative, or out of range.
Action: Check the documentation for details.
ORA-13434: GeoRaster metadata cellRepresentation error
Cause: The cellRepresentation type was not supported.
Action: Check the documentation for supported cellRepresentation types.
ORA-13435: GeoRaster metadata dimension inconsistent
Cause: The specification of dimensions or totalDimensions was inconsistent with
rasterType, or vice versa.
Action: Make sure dimension specifications are consistent.
ORA-13436: GeoRaster metadata dimensionSize error
Cause: Either the dimensionSize for each dimension was not specified, or an
extraneous dimensionSize was specified.
Action: Add a dimsenionSize for each dimension of the GeoRaster object and delete
extra dimensionSize elements.
ORA-13437: GeoRaster metadata blocking error
Cause: Either the wrong block number(s) or block size(s) along dimensions were
specified, or the block numbers and sizes when taken together were not consistent.
Action: Check the documentation for details.
ORA-13438: GeoRaster metadata pyramid type error
Cause: The specified pyramid type was not supported.
Action: Check the documentation for supported pyramid types.
ORA-13439: GeoRaster metadata pyramid maxLevel error
Cause: The specified maxLevel exceeded the maximum level allowed by the specified
pyramid type.
Action: Check the documentation for supported pyramid types and their total level
limitations.
ORA-12700 to ORA-19400 69-49
ORA-13440: GeoRaster metadata compression type error

Cause: The specified compression type was not supported.
Action: Check the documentation for supported compression types.
ORA-13441: GeoRaster metadata SRS error: string
Cause: The specified error relates to the polynomialModel element in the Spatial
Reference System (SRS) metadata.
Action: Check the documentation and make sure that a valid polynomial model is
specified.
ORA-13442: GeoRaster object not registered: string
Cause: There was no sysdata entry for the specified GeoRaster object.
Action: Make sure that a sysdata entry has been inserted for the specified GeoRaster
object.
ORA-13443: null or invalid values in string
Cause: There were null or invalid component values in the specified metadata.
Action: Check the documentation and make sure that all the component values are
valid.
ORA-13444: cannot perform mergeLayers operation
Cause: The two GeoRaster objects whose layers are to be combined together either
had different row or column dimension sizes, or their georeferencing information did
not match.
Action: Make sure the objects have the same row and column dimension sizes. If
neither is georeferenced, their ULTCoordinate values must be the same. Otherwise,
they must be both georeferenced and cover the same area in the model space.
ORA-13445: NULL or invalid NODATA value or value range
Cause: There was invalid NODATA value or value range in the metadata, or the
specified NODATA value or value range was invalid.
Action: Make sure the NODATA value or value range is not NULL and is completely
contained in the range as designated by the cellDepth definition of the specified
GeoRaster object.
ORA-13446: GeoRaster metadata TRS error
Cause: The GeoRaster Temporal Reference System was not supported.
Action: Set isReferenced to FALSE.
ORA-13447: GeoRaster metadata BRS error
Cause: The GeoRaster Band Reference System was not supported.
Action: Set isReferenced to FALSE.
ORA-13448: GeoRaster metadata BRS error
Cause: The GeoRaster spectral extent specification was incorrect.
Action: The MIN value must be less than the MAX value in the spectralExtent
element.
ORA-13449: GeoRaster metadata ULTCoordinate error
Cause: The GeoRaster rasterInfo ULTCoordinate was not correct.
Action: Check the documentation for restrictions.
ORA-13450: GeoRaster metadata layerInfo error

Cause: The GeoRaster had more than one layerInfo element, or the layerDimension
value was not supported.
Action: The current release only supports one layerInfo element; layer can only be
defined along one dimension, and this dimension must be BAND.
ORA-13451: GeoRaster metadata scaling function error
Cause: The scaling function had a zero denominator.
Action: Make sure the scaling function denominator is not zero.
ORA-13452: GeoRaster metadata BIN function error
Cause: The bin function data did not match its type.
Action: For EXPLICIT type, provide a binTableName element; otherwise, provide a
binFunctionData element.
ORA-13453: GeoRaster metadata layer error
Cause: Too many subLayers were defined for the GeoRaster object, or layerNumber
or layerDimensionOrdinate was not assigned correctly.
Action: The total number of logical layers cannot exceed the total number of physical
layers, and each logical layer must be assigned a valid physical layer number
following the same order. Check the documentation for more details.
ORA-13454: GeoRaster metadata is invalid
Cause: The GeoRaster metadata was invalid against its XML Schema.
Action: Run the schemaValidate routine to find the errors.
ORA-13455: GeoRaster metadata TRS error
Cause: The beginDateTime value was later than the endDateTime value.
Action: Make sure that the beginDateTime value is not later than the endDateTime
value.
ORA-13456: GeoRaster cell data error: string
Cause: There was an error in the original GeoRaster cell data or in the cell data of the
pyramids.
Action: If the error is related to the original GeoRaster cell data, the GeoRaster object
is invalid and has to be deleted or manually repaired. If the error is related to
pyramids, delete the pyramids and regenerate them.
ORA-13457: bitmap mask cell data error: string
Cause: There was an error in the cell data of an original bitmap mask or in the cell
data of the pyramids of a bitmap mask.
Action: If the error is related to an original bitmap mask, remove the bitmap mask. If
the error is related to the pyramids of a bitmap mask, delete the pyramids and
regenerate them.
ORA-13458: GeoRaster metadata SRS error
Cause: The polynomial model did not match the requirements of a rectified
GeoRaster object.
Action: Check the documentation for the requirements of the polynomial model for a
rectified GeoRaster object, or set isRectified to be false.
ORA-12700 to ORA-19400 69-51

Cause: The polynomial model was not an six-parameter transformation, or the sixparameter transformation was not valid.
Action: Check the documentation and make sure the polynomial model is a valid sixparameter affine transformation.
Cause: The referenced GeoRaster object had a zero model space SRID or the specified
model space SRID was zero.
Action: Set or specify the model space SRID to be a nonzero number.
ORA-13461: the interleaving type is not supported
Cause: The interleaving type of the GeoRaster object was not supported.
Action: Check the documentation for the interleaving types supported by GeoRaster.
Use SDO_GEOR.changeFormatCopy to transform the image to a supported
interleaving type.
ORA-13462: invalid blocking specification
Cause: The specified blocking configuration was invalid.
Action: Check the documentation for the blocking specification supported by
GeoRaster.
ORA-13463: error retrieving GeoRaster data: string
Cause: An internal error occurred while retrieving GeoRaster data from the database.
ORA-13464: error loading GeoRaster data: string
Cause: An internal error occurred while loading GeoRaster data into the database.
ORA-13465: null or invalid table or column specification
Cause: The specified table or column did not exist, or the column was not a GeoRaster
column.
Action: Make sure the specified table exists and the specified column is a GeoRaster
column.
ORA-13466: format not appropriate for specified compression method: string
Cause: The operation failed because the GeoRaster object had an inappropriate type
or format for the specified compression method. The GeoRaster type or format is not
supported for the specified compression.
Action: Check the error message for details. Check the documentation for the
appropriate GeoRaster types and formats for each compression method. Use
SDO_GEOR.changeFormatCopy to transform the GeoRaster object to an appropriate
format, or apply another compression method.
ORA-13467: unsupported GeoRaster metadata specification: string
Cause: The GeoRaster metadata specification is not supported.
Action: Check the documentation for the supported GeoRaster metadata
specifications.
ORA-13468: invalid blockMBR

Cause: Invalid blockMBR geometries were stored in the raster data table.
Action: Make sure the blockMBR geometries stored in the raster data table are valid,
or call SDO_GEOR.generateBlockMBR() to regenerate the blockMBR geometries.
ORA-13469: cannot perform updateRaster operation
Cause: The data of the source GeoRaster object could not be used to update that of the
target GeoRaster object.
Action: Make sure the source and the target GeoRaster objects have the same cell
depth, and that both objects are either georeferenced or not georeferenced at all. If
both are georeferenced, they should be in the same coordinate system and have the
same spatial resolutions.
ORA-13470: target and source layers or bands mismatched
Cause: The number of specified target layers or bands and source layers or bands did
not match.
Action: When updating layers or bands of a target GeoRaster object to reflect the
associated layers or bands of the source GeoRaster object, specify the same number of
layers or bands for both the source and the target objects. Check the documentation
for details.
ORA-13471: unable to determine the owner of string
Cause: The owner of the specified raster data table could not be determined.
Action: Make sure the GeoRaster object that refers to the raster data table has been
registered by inserting the object into a GeoRaster table.
ORA-13472: invalid geometry parameter
Cause: The geometry parameter did not specify a valid geometry.
Action: Specify a valid 2D or 3D geometry. If the model SRID is null or indicates a 2D
coordinate system, the geometry must be 2D. If the model SRID indicates a 3D
coordinate system, the geometry must either be a 3D geometry or a 2D geometry that
can be converted to 3D with the specified vertical axis (or vertical SRID) and
ellipsoidal parameters.
ORA-13473: invalid rasterSpec parameter
Cause: The rasterSpec parameter contained an invalid specification.
Action: Check the documentation and make sure the rasterSpec parameter contains
only valid keywords and values.
ORA-13474: invalid rasterDataTable name: string
Cause: The rasterDataTable name was not a valid nonquoted identifier, it contained a
period separator, or not all of the alphanumeric characters were uppercase.
Action: Ensure that the table name is a valid nonquoted identifier without any period
separators, and that all the alphanumeric characters are uppercase.
ORA-13475: invalid GeoRaster object for output
Cause: The output GeoRaster object had the same RASTER_DATA_TABLE and
RASTER_ID combination as that of an input GeoRaster object.
Action: Ensure that the output GeoRaster object is different from any of the input
GeoRaster objects.
ORA-12700 to ORA-19400 69-53
ORA-13476: invalid or out of scope point specification

Cause: The point position specified by the point geometry parameter or the
rowNumber/colNumber parameter combination was null or out of scope.
Action: Ensure that the parameters specify a valid point that translates or can be
translated into a cell position inside the cell space of the GeoRaster object.
ORA-13477: invalid GCP georeferencing specification: string
Cause: The specified functional fitting method was not supported, the number of
GCPs was insufficient, some GCPs were invalid, or the distribution of the GCPs led to
no solution or an unstable solution.
Action: Check the GeoRaster documentation for the supported functional fitting
methods and the requirements of GCPs.
ORA-13478: the target SRID is the same as the source GeoRaster object's SRID
Cause: The target SRID was not different from the source GeoRaster object's SRID.
Action: Specify a different valid SRID for the target GeoRaster object.
ORA-13479: cannot reproject
Cause: Reprojection from source to destination projection produced a large distortion.
Action: Check the destination projection and make sure it is suitable for the area
covered by the source GeoRaster object. Check the GeoRaster documentation for
more information about reprojection.
ORA-13480: the Source Type is not supported
Cause: The specified source type was not supported.
Action: Check the documentation for the source types (such as FILE and HTTP)
supported by GeoRaster.
ORA-13481: the destination type is not supported
Cause: The specified destination type was not supported.
Action: Check the documentation for the destination types (such as FILE) supported
by GeoRaster.
ORA-13482: GeoRaster object is not initialized for the image
Cause: No GeoRaster object has been initialized for the specified image.
Action: Initialize a GeoRaster object to hold this image before loading it into the
database. Check the documentation for details.
ORA-13483: insufficient memory for the specified GeoRaster data
Cause: There was insufficient memory to hold the specified GeoRaster data for this
operation.
Action: Use SDO_GEOR.subset to isolate a subset of the GeoRaster data, or reblock
the GeoRaster data into smaller sized blocks. Check the documentation for details.
ORA-13484: the file format or compression type is not supported: string
Cause: The file format or compression type was not supported.
Action: Check the documentation for formats that are currently supported by
GeoRaster.
ORA-13485: error occurred during compression or decompression: string

Cause: The operation could not be completed because an error occurred during
compression or decompression. Check the error message for details.
Action: Check that the GeoRaster object is valid, that its metadata is valid for the
specified compression format, and that valid parameters are passed into the
compression or decompression operation.
ORA-13486: invalid or insufficient GeoTIFF metadata to georeference the
GeoRaster object: string
Cause: The GeoTIFF metadata of the specified input image contained invalid or
insufficient information to georeference the GeoRaster object.
ORA-13487: SRID not found for source coordinate system metadata
Cause: No SRID was found in the Oracle Spatial CS_SRS table to match the source
coordinate system metadata.
Action: Add a user-defined coordinate reference system for this coordinate system, as
explained in the Oracle Spatial documentation.
ORA-13488: cannot perform transformation: string
Cause: An attempt to perform a transformation operation failed.
ORA-13497: string
Cause: This is an internal GeoRaster error.
Action: Contact Oracle Support Services. You may want to make sure the GeoRaster
object is valid before you do so.
ORA-13498: string
Cause: An error related to an external plugin was encountered in the GeoRaster
component.
Action: Check the documentation for the external plugin, or contact the plugin
provider and supply the exact error text.
ORA-13499: string
Cause: This is an internal Spatial error.
ORA-13500: SYSAUX DATAFILE clause specified more than once
Cause: The CREATE DATABASE command contains more than one SYSAUX
DATAFILE clause.
Action: Specify at most one SYSAUX DATAFILE clause.
ORA-13501: Cannot drop SYSAUX tablespace
Cause: Tried to drop SYSAUX tablespace
Action: None
ORA-13502: Cannot rename SYSAUX tablespace
Cause: An attempt to rename the SYSAUX tablespace failed.
ORA-12700 to ORA-19400 69-55
ORA-13503: Creating SYSAUX tablespace with invalid attributes

Cause: An attempt to create the SYSAUX tablespace with invalid attributes.
Action: Create SYSAUX tablespace with ONLINE, PERMANENT, EXTENT
MANAGEMENT LOCAL, SEGMENT SPACE MANAGEMENT AUTO attributes.
ORA-13504: No SYSAUX datafile clause specified
Cause: If Create Database has the datafile clause, then SYSAUX datafile clause has to
be specified, unless using OMF.
Action: Specify the SYSAUX datafile clause.
ORA-13505: SYSAUX tablespace can not be made read only
Cause: Attempting to set the SYSAUX tablespace to read only. The SYSAUX
tablespace must remain read write for database operation.
Action: Leave SYSAUX tablespace read write.
ORA-13506: operation failed due to invalid snapshot range (string, string)
Cause: An attempt was made to perform operation with an invalid Start/End
Snapshot Pair.
Action: Choose a valid Start/End Snapshot Pair.
ORA-13509: error encountered during updates to a AWR table
Cause: An update error occurred during OCI operation due to an underlying error.
Action: Check associated OCI error. Correct problem and retry the operation.
ORA-13510: invalid RETENTION string, must be in the range (string, string)
Cause: The user has specified a RETENTION setting that is not in the supported
range of (MIN, MAX).
Action: Choose a valid RETENTION setting and retry the operation.
ORA-13511: invalid INTERVAL string, must be in the range (string, string)
Cause: The user has specified a INTERVAL setting that is not in the supported range
of (MIN, MAX).
Action: Choose a valid INTERVAL setting and retry the operation.
ORA-13514: Metric Capture too close to last capture, group string
Cause: The metric capture cannot be executed because it is too close to the last capture
(within 1 centi-second).
Action: add some delay and reissue command to retry.
ORA-13515: Error encountered during Database Usage Statistics capture
Cause: Error occurred during OCI operation due to underlying error.
ORA-13516: AWR Operation failed: string
Cause: The operation failed because AWR is not available. The possible causes are:
AWR schema not yet created; AWR not enabled; AWR schema not initialized; or
database not open or is running in READONLY or STANDBY mode.
Action: check the above conditions and retry the operation.
ORA-13517: Baseline (id = string) does not exist

Cause: The operation failed because the specified baseline ID does not exist in the
Workload Repository.
Action: check the baseline id and retry the operation.
ORA-13518: Invalid database id (string)
Cause: The operation failed because the specified database ID does not exist in the
Action: check the database id and retry the operation.
ORA-13519: Database id (string) exists in the workload repository
Cause: The operation failed because the specified database ID already exists in the
ORA-13520: Database id (string) not registered, Status = string
Cause: The operation failed because the specified database ID was not registered in
the Workload Repository properly.
Action: check the status of database id and retry the operation.
ORA-13521: Unregister operation on local Database id (string) not allowed
Cause: The operation failed because the local database ID cannot be unregistered
from the Workload Repository.
ORA-13523: unable to allocate required space for return type
Cause: Out of memory to allocate the space for the return variable for an external
procedure.
Action: Try operation again.
ORA-13524: error encountered while retrieving baseline information
Cause: A read error occurred during the OCI operation to retrieve the baseline
information
Action: Check associated error. Correct problem and retry the operation.
ORA-13525: error with computing space usage for sysaux occupant
ORA-13526: baseline (string) does not exist
Cause: The operation failed because the specified baseline name does not exist in the
Action: check the baseline name and retry the operation.
ORA-13527: invalid baseline name
Cause: The operation failed because the specified baseline name is invalid.
ORA-13528: name (string) is already used by an existing baseline
Cause: The operation failed because the specified baseline name already exists in the
ORA-12700 to ORA-19400 69-57

ORA-13529: Error occurred when flushing AWR table group
Cause: An error occurred during the flushing of a table group. Because of the error in
the group, we are unable to flush this table.
Action: Check the error associated with the table group.
ORA-13530: invalid TOPNSQL string, must be in the range (string, string)
Cause: The user has specified a TOPNSQL setting that is not in the supported range
of (MIN, MAX).
Action: Choose a valid TOPNSQL setting and retry the operation.
ORA-13531: SQL Text was purged from AWR before the operation completed
Cause: A SQL was purged from AWR before the operation completed.
ORA-13532: SQL ID [string] already exists
Cause: The operation failed because the specified SQL ID already existed in the
repository.
Action: Check the SQL ID and retry the operation.
ORA-13533: invalid SQL ID
Cause: The operation failed because the specified SQL ID was invalid.
Action: Check the SQL ID and retry the operation.
ORA-13534: Current SQL count(string) reached maximum allowed (string)
Cause: The operation failed because the maximum allowed colored SQL was
exceeded.
Action: Check the count for colored SQL.
ORA-13535: name (string) is already used by an existing baseline template
Cause: The operation failed because the specified baseline template name already
existed in the Workload Repository.
Action: Check the baseline template name and retry the operation.
ORA-13536: baseline template (string) does not exist
Cause: The operation failed because the specified baseline template name did not
exist in the Workload Repository.
ORA-13537: invalid input for create baseline template (string, string)
Cause: Invalid input was specified for the create baseline template routine.
Action: Check the argument displayed in the error message text.
ORA-13538: invalid value for baseline expiration (string)
Cause: An invalid value was specified for the expiration of a baseline. The expiration
is specified in number of days, and the expiration must be at least one day.
Action: Check the value for expiration.
ORA-13539: invalid input for modify baseline window size (string, string)
Cause: Invalid input was specified for the modify baseline window size routine.

ORA-13540: operation not allowed on system moving window baseline (string)
Cause: The requested operation was not allowed on the system moving window
baseline.
Action: Retry the operation with another baseline name.
ORA-13541: system moving window baseline size (string) greater than retention
(string)
Cause: The system moving window baseline size must be less than the retention
setting. The specified window size or retention violate this.
Action: Check the moving window baseline size or retention.
ORA-13542: baseline ID (string) does not exist
Cause: The operation failed because the specified baseline ID did not exist in the
Action: Check the baseline ID and retry the operation.
ORA-13543: error encountered while retrieving baseline template information
Cause: A read error occurred during the OCI operation to retrieve the baseline
template information.
Action: Check associated error. Correct problem and retry the operation.
ORA-13544: error encountered while automatically generating a baseline
Cause: An error occurred while automatically generating a baseline based on the
template information.
Action: Look in the trace file for more error information.
ORA-13545: invalid baseline template name
Cause: The operation failed because the specified baseline template name was an
invalid identifier.
ORA-13546: Error encountered during maintenance of Adaptive Thresholds
ORA-13547: Unable to drop baseline since it is in use by string
Cause: The system is not able to drop the baseline since the baseline is in use by a
functionality that depends on its existence.
Action: Note the name of the functionality using the baseline, and check if the
functionality still needs the baseline.
ORA-13548: Unable to find valid snapshot IDs for the inputted baseline time range
Cause: The system is not able to find valid snapshot IDs for the inputted time range
while attempting to create a baseline.
Action: Check that the inputted time range has at least two valid snapshots. The
dba_hist_snapshot displays the snapshot id and time information.
ORA-13549: invalid input for create baseline with time range (string)
Cause: Invalid time input was specified for the create baseline routine.
ORA-12700 to ORA-19400 69-59
ORA-13550: value "string" of length (string) exceeded maximum length (string) for
parameter [string]
Cause: An invalid parameter was specified for the Automatic Workload Repository
(AWR) registration routine.
ORA-13551: source database same [string] not found in AWR
(AWR) operation.
ORA-13552: parameter [string] of value [string] mismatched with AWR registered
value [string]
(AWR) operation.
ORA-13553: operation failed - missing parameter [string]
Cause: The required parameter was missing for the Automatic Workload Repository
(AWR) operation.
Action: Check the parameter name displayed in the error message text.
ORA-13554: failed to stop report capture on all instances
Cause: The API 'finish_report_capture' ran successfully on %d instances only.
Action: Check if all instances are active and running.
ORA-13600: error encountered in Advisor\nstring
Cause: An error occurred in the Advisor. This message will be followed by a second
message giving more details about the nature of the error.
Action: See the Advisor documentation for an explanation of the second error
message.
ORA-13601: The specified Advisor string does not exist.
Cause: The user specified an advisor name that has not be defined in the advisor
repository.
Action: Correct the advisor name and retry the operation.
ORA-13602: The specified parameter string is not valid for task or object string.
Cause: The user attempted to access a task parameter that does not exist for the
specified advisor object. The parameter may be misspelled or the user has selected a
parameter that is not supported by the particular advisor.
Action: Validate the parameter name and retry the operation.
ORA-13603: The specified parameter string cannot be fetched as a numeric value
for task or object string.
Cause: The user attempted to retrieve a string parameter as a numeric value.
Action: Check the datatype for the task parameter and retry the operation.
ORA-13604: The specified parameter string cannot be fetched as a SQL table.
Cause: The user attempted to retrieve a non-table parameter as a table name.
Action: Check the datatype for the task parameter and retry the operation.
ORA-13605: The specified task or object string does not exist for the current user.
Cause: The user attempted to reference an advisor task or object using a name that
does not exist in the Advisor repository.
Action: Adjust the name and retry the operation.
ORA-13606: the specified task parameter element string is out of range for
parameter string.
Cause: The user attempted to reference an invalid parameter element.
Action: Adjust the element offset and retry the operation.
ORA-13607: The specified task or object string already exists
Cause: The user attempted to create the specified task or object using a name that
already exists in the Advisor repository. Task names must be unique to the database
user.
ORA-13608: The specified name string is invalid.
Cause: An attempt was made to specify a name for a task, object, execution or
directive instance, which contained invalid characters or an invalid wildcard specifier.
ORA-13609: The specified task string must be executing to be cancelled or
interrupted.
Cause: The user attempted to cancel or interrupt a task that is not currently executing.
Action: Check the status of the task and retry the operation.
ORA-13610: The directive string does not exist for task string.
Cause: The user attempted to access a task directive that does not exist.
Action: Validate the directive and retry the operation.
ORA-13611: The command string is not a valid advisor command.
Cause: The user attempted to specify a command that does not exist.
Action: Validate the command and retry the operation.
ORA-13612: The recommendation action string,string is not valid for task string.
Cause: The user attempted to access a recommendation action that does not exist in
the task.
Action: Validate the recommendation-action and retry the operation.
ORA-13613: The requested operation is not supported for this advisor object.
Cause: The user attempted to perform an operation that is not supported for the
particular advisor or task type.
Action: Validate the task or object and retry the operation.
ORA-13614: The template string is not compatible with the current advisor.
Cause: The user attempted to create a new task or object using an existing task or
object that was not created by the same advisor.
Action: Validate the template and retry the operation.
ORA-12700 to ORA-19400 69-61
ORA-13615: The task or object string is greater than the maximum allowable length
of 30 characters.
Cause: The user attempted to create a new task or object using a name that is too long.
Action: Shorten the name and retry the operation.
ORA-13616: The current user string has not been granted the ADVISOR privilege.
Cause: The user attempted an advisor operation that requires privilege.
Action: Adjust the user's privileges and retry the operation.
ORA-13617: The specified task string already executing
Cause: The user attempted to execute a task that is currently executing.
Action: Wait for the task to finish before attempting any further task activities.
ORA-13618: The specified value is not a valid value for procedure argument string.
Cause: The user executed a procedure but failed to provide correct values for the
argument.
Action: Correct the procedure arguments and retry the operation.
ORA-13619: The procedure argument string is greater than the maximum allowable
length of string characters.
Cause: The user attempted to pass a character argument that is too long.
Action: Shorten the specified character argument and retry the operation.
ORA-13620: The task or object string is read-only and cannot be deleted or
modified.
Cause: The user attempted to perform an operation that will update or delete a readonly task or object.
Action: Adjust the READ_ONLY property for the object and retry the operation.
ORA-13621: The task_or object string is marked as a template and cannot perform
the requested operation.
Cause: The user attempted perform an unsupported operation on a task or object that
is identified as a template.
Action: Choose a different object and retry the operation.
ORA-13622: invalid recommendation annotation
Cause: The user attempted to mark a recommendation using an invalid annotation.
Valid annotation actions are ACCEPT, REJECT and IGNORE.
Action: Correct the action and retry the operation.
ORA-13623: The recommendation string is not valid for task string.
Cause: The user attempted to access a recommendation that does not exist in the task.
Action: Validate the recommendation and retry the operation.
ORA-13624: The task string is executing and cannot be deleted or modified.
Cause: The user attempted to access a task that currently executing.
Action: Wait for the task to complete and retry the operation.
ORA-13625: string is an invalid advisor object type.
Cause: The user has specified an invlaid object type.
Action: Refre to dba_advisor_object_types for all valid object types
ORA-13626: The specified object string is not valid for task string.
Cause: The user specified an non-existent object for the task
Action: Choose a different object and retry the operation.
ORA-13627: Setting of parameter string is disallowed until the task is reset.
Cause: The user attempted to set the value of a parameter before the task was reset.
This parameter cannot be changed until the task is reset.
Action: Reset the task and retry the operation.
ORA-13628: Insufficient privileges to access the task belonging to the specified
user
Cause: The user could not access dba_* views.
Action: Retry operation as owner of the task or after granting new privileges.
ORA-13629: The task or object string is being used by another operation.
Cause: The user attempted to access a task or object that is locked by another session.
Action: Wait for the task or object activity to complete and retry the operation.
ORA-13630: The task string contains execution results and cannot be executed.
Cause: The user attempted to execute a task that already contains execution results.
Action: Reset the task to its initial state and retry the operation.
ORA-13631: The most recent execution of task string contains no results.
Cause: The user attempted to create a report or script from a task that has not
successfully completed an execution.
Action: Execute the task and then retry the operation
ORA-13632: The user cancelled the current operation.
Cause: The user signaled a cancel during a task or object operation.
Action: None
ORA-13633: The task string was interrupted and needs to be resumed.
Cause: The user attempted to execute a task that was interrupted.
Action: Resume the execution of the task via the RESUME_TASK API.
ORA-13634: The task string needs to be reset before being re-executed.
Cause: The task must be in an inital state to be executed.
Action: Reset the task to its initial state and retry the operation.
ORA-13635: The value provided for parameter string cannot be converted to a
number.
Cause: A numeric parameter was incorrectly supplied in string form.
Action: Retry by supplying valid numeric value.
ORA-13636: The specified value provided for parameter string is not valid for this
advisor.
Cause: The user supplied an invalid parameter value.
Action: Retry by supplying valid value.
ORA-12700 to ORA-19400 69-63
ORA-13637: Executing or modifying task string is disallowed until the task is reset
to its initial state.
Cause: The user attempted to execute or modify the task that is in not in its INITIAL
state.
Action: Reset the task and retry the operation.
ORA-13638: The user interrupted the current operation.
Cause: The user signaled an interrupt during a task or object operation.
Action: None
ORA-13639: The current operation was interrupted because it timed out.
Cause: The task or object operation timed out.
Action: None
ORA-13640: The current operation was cancelled because it timed out, and was not
in interruptible mode.
Cause: The task or object operation timed out.
Action: None
ORA-13641: Task cannot be interrupted yet. You may cancel it instead.
Cause: The user attempted to interrupt a task that has not reached interruptible mode.
Action: Wait until the task reaches interruptible mode, or cancel the task execution.
ORA-13642: The specified string string provided for string cannot be converted to a
date. The acceptable date format is string.
Cause: The user supplied a date value in an incorrect format.
Action: Retry by supplying valid value.
ORA-13643: The task can not be interrupted or cancelled.
Cause: Request to interrupt or cancel task execution can not be granted because the
task has not reached the appropriate mode.
Action: User should wait for a few seconds and try again.
ORA-13644: The user "string" is invalid.
Cause: Invalid user name specified to advisor framework
Action: User should specify a correct, case-sensitive, name
ORA-13645: The specified execution string does not exist for this task.
Cause: You attempted to reference an advisor task execution using a name that did
not exist.
ORA-13646: The specified execution string already exists
Cause: You attempted to perform a new execution using a name that already exists
for the specified task. Execution names must be unique within the same task.
ORA-13647: Setting of parameter string is disallowed during task execution.
Cause: You attempted to set the value of a parameter while the task was being
executed. This parameter cannot be changed until the task finishes its execution.
Action: Verify the status of the task and retry the operation.
ORA-13648: The specified execution type does not exist for this advisor.
Cause: You attempted to use an advisor task execution type using a name that did not
exist.
ORA-13649: The type of execution is not specified for this advisor or task.
Cause: You attempted to execute a task for a multi-execution task advisor without
specifying the type of execution to perform.
Action: Set the execution type and retry the operation.
ORA-13650: The specified object does not exist for this execution.
Cause: You attempted to associate an object to a task execution that id not contain the
object.
Action: Adjust the execution name and object ID, and then retry the operation.
ORA-13651: The specified list of execution parameters is invalid.
Cause: The list did not include pairs of (parameter_name, parameter_value) where
every parameter is a valide task parameter. Duplicates are not allowed.
Action: Adjust the content of the list, and then retry the operation.
ORA-13652: Cannot set execution parameters for this advisor
Cause: You attempted to set execution parameters for an advisor that did not support
multiple executions of its tasks.
Action: Adjust the property of the advisor, and then retry the operation.
ORA-13653: The directive with definition id string was not found.
Cause: An invalid directive identifier was specified to advisor framework.
Action: User should specify a correct identifier number and retry the operation.
ORA-13654: The directive with instance id of string was not found.
Cause: An invalid instance identifier was specified to advisor framework.
Action: User should specify a correct instance identifier number and retry the
operation.
ORA-13655: The directive document contains a syntax error and cannot be loaded.
Cause: An attempt was made to load an XML-based directive that does not conform
to the documented DTD.
Action: Reformat the directive according the documented DTD.
ORA-13656: The parameter was not found in directive string.
Cause: The specified parameter name could not be located within the directive XML
document.
Action: Verify the existence of the parameter in the specified directive.
ORA-13657: The filter Xpath specification has invalid syntax.
Cause: The specified filter could not be compiled within the directive XML document.
Action: Verify the syntax of the filter and retry the operation.
ORA-13658: The specified directive already has an instance
Cause: An attempt was made to create multiple instances of a directive when not
permitted
ORA-12700 to ORA-19400 69-65
Action: Verify the parent directive identifier and the instance name.
ORA-13659: A directive with domain "string" and name "string" already exists for
advisor string.
Cause: The specified directive is not unique among the directives.
Action: Choose a directive name and domain that is distinct for the associated
advisor.
ORA-13660: A directive instance with the name "string" already exists.
Cause: The specified directive instance is not unique among instances for this
directive.
Action: Choose an instance name that is distinct for the associated directive.
ORA-13661: A directive instance with the name "string" was not found.
Cause: An attempt was made to update or delete a non-existent directive instance.
Action: Verify the parent directive identifier and the instance name.
ORA-13662: The specified value provided for parameter string is not valid for this
task.
Cause: The supplied parameter value was not valid for the current task configuration.
Action: Retry by supplying valid value. Check the current task configuration.
ORA-13663: The task string contains no results for execution string.
Cause: An attempt was made to create a report or script from an execution that had
not been successfully completed.
Action: Run a new execution and then retry the operation.
ORA-13664: A task-managed "SQL Tuning Set" already exists for task "string".
Cause: An attempt was made to create a task-managed SQL Tuning Set for a task that
already had one.
Action: Create a new task to use a different SQL Tuning Set.
ORA-13665: Execution names are not correctly ordered.
Cause: The supplied execution names were not properly ordered by execution start
date.
Action: Retry by supplying a valid order.
ORA-13666: Task ID string does not exist.
Cause: The supplied task ID was invalid.
Action: Check the task ID and try again.
ORA-13667: Execution ID string does not exist.
Cause: The supplied execution ID was invalid.
Action: Check the execution ID and try again.
ORA-13668: The current operation was aborted because it was blocking another
session.
Cause: The task or object operation interrupted itself when it detected that it was
blocking some other session.
Action: Retry the operation when the conflicting operations are not running.
ORA-13669: Execution provided has type "string", expected "string".

Cause: An execution was provided whose type did not match the one expected by the
API.
Action: Check the execution name, and try again.
ORA-13670: No execution of type string exists for task provided.
Cause: No execution of the required type existed for the given advisor task.
Action: Check the task, and try again.
ORA-13699: Advisor feature is not currently implemented.
Cause: An attempt was made to execute an unsupported advisor operation.
Action: Verify the availability of the operation.
ORA-13700: Reserved for ADDM tracing.
ORA-13701: Snapshot pair [string, string] seems to be specified in reverse order.
Cause: The start snapshot id was greater than the end snapshot id.
Action: Swap the start and end snapshot ids.
ORA-13702: Snapshot IDs specified by the range [string, string] are equal.
Cause: The start snapshot id and end snapshot id were identical.
Action: Provide different start and end snapshot ids.
ORA-13703: The snapshot pair [string, string] for database_id string and
instance_id string are not found in the current repository.
Cause: The snapshot ids or the database id or the instance id was invalid or the
specified snapshots have already been purged.
Action: Set valid snapshot ids and retry.
ORA-13704: Invalid value "string" specified for parameter "string".
Cause: The parameter was not set before executing the ADDM.
Action: Set the parameter to a valid value and retry.
ORA-13705: There was a instance shutdown/startup between the snapshots in the
range [string, string].
Cause: Instance was shut down and restarted between the two specified snapshots.
Action: Specify start and end snapshot ids that does not have a shutdown/startup in
between them.
ORA-13706: Invalid value "string" specified for parameter "string" in "string"
analysis mode.
Cause: The parameter was not set to an acceptable value for this particular mode of
analysis.
ORA-13707: Either the start snapshot string or the end snapshot string is incomplete
or missing key statistics.
Cause: Either the start or the end snaphots was missing or purged or had encountered
errors while creating them.
Action: Verify that AWR is done taking these two snapshots, or Look in
DBA_HIST_SNAP_ERROR to find what tables are missing in the start/end
ORA-12700 to ORA-19400 69-67
snapshots. Use the ERROR_NUMBER column in that view together with the alert log
to identify the reason for failure and take necessary action to prevent such failures in
the future. Try running ADDM on a different snapshot range that has valid start and
end snapshots.
ORA-13708: Some snapshots in the range [string, string] were purged before the
analysis was complete.
Cause: One or both of the snapshots have been purged from AWR.
Action: Verify that the AWR auto purging is not trying to purge these snapshots and
re-run ADDM.
ORA-13709: Required parameter "string" must be set before execution.
Cause: The parameter needs to be set before running the ADDM
ORA-13710: Parameter "string" must have a higher value than parameter "string".
The values supplied were "string" and "string" respectively.
Cause: Invalid interaction between two parameter values.
Action: Set at least one of the values so the value of the first parameter is higher than
the value of the second parameter.
ORA-13711: Some snapshots in the range [string, string] are missing key statistics.
Cause: Some AWR tables encountered errors while creating one or more snapshots in
the given range. The data present in one or more of these missing tables is necessary
to perform an ADDM analysis.
Action: Look in DBA_HIST_SNAP_ERROR to find what tables are missing in the
given snapshot range. Use the ERROR_NUMBER column in that view together with
the alert log to identify the reason for failure and take necessary action to prevent
such failures in the future. Try running ADDM on a different snapshot range that
does not include any incomplete snapshots.
ORA-13712: Cannot perform ADDM analysis on AWR snapshots from previous
releases. Snapshot version "string" do not match the database version "string".
Cause: ADDM analysis can only be performed on AWR snapshots taken in the
current release.
Action: One can still generate AWR and ASH reports using ?/rdbms/admin/awrrpt
and ?/rdbms/admin/ashrpt on these snapshots to analyze the data in them.
ORA-13713: Finding name "string" does not exist. Look in
DBA_ADVISOR_FINDING_NAMES for all valid values
Cause: Attempt to refer to an advisor's finding name that does not exist.
Action: Specify a valid value. The list of all valid values is in
DBA_ADVISOR_FINDING_NAMES
ORA-13714: "string" is not a valid SQL_ID value
Cause: The specified value of SQL_ID was not properly formatted.
Action: Specify a valid value consisting of a 13 character string with characters from
'0' to '9' and from 'a' to 'z'.
ORA-13715: "string" is not recognized by ADDM as a parameter name
Cause: The specified value for a system parameter was not recognized by ADDM.
Action: Specify a value that appears in the NAME column of V$PARAMETER.
ORA-13716: Diagnostic Package License is needed for using this feature.

Cause: The specified value for system parameter
CONTROL_MANAGEMENT_PACK_ACCESS indicated that the Diagnostic Package
was disabled.
Action: Modify the parameter value if the Diagnostic Package License was purchased.
ORA-13717: Tuning Package License is needed for using this feature.
Cause: The specified value for system parameter
CONTROL_MANAGEMENT_PACK_ACCESS indicated that the Tuning Package
was disabled.
Action: Modify the parameter value if the Tuning Package License was purchased.
ORA-13718: Tuning Package License or Real Application Testing Option is needed
for using this feature.
Cause: The specified package license and option were not installed.
Action: Consider purchasing and installing either the missing package licence or
option. If the tuning package license was purchased, then check the value of system
parameter CONTROL_MANAGEMENT_PACK_ACCESS.
ORA-13719: Imported AWR snapshots are from a database with an incompatible
character set.
Cause: ADDM analysis was attempted on imported Automatic Workload Repository
(AWR) snapshots with incompatible character set.
Action: Perform ADDM analysis using a database with the same version and
character set as the original database.
ORA-13720: dimension name provided is too long
Cause: Active Session History (ASH) dimension name provided was longer than the
limit of 30 characters.
Action: Correct the dimension name and retry the operation.
ORA-13721: dimension name provided is invalid
Cause: Active Session History (ASH) dimension name provided was invalid.
Action: Correct the dimension name and retry the operation.
ORA-13750: User "string" has not been granted the "ADMINISTER SQL TUNING
SET" privilege.
Cause: The user attempted an SQL Tuning Set operation that requires a specific
privilege.
ORA-13751: "SQL Tuning Set" "string" does not exist for owner "string" or user
"string" does not have permission to access the "SQL Tuning Set".
Cause: The user attempted to access a SQL Tuning Set that does not exist or the user
does have permission to access the SQL Tuning Set
Action: Check the existence of the "SQL Tuning Set" or adjust the user's privileges and
ORA-12700 to ORA-19400 69-69
ORA-13752: User "string" must be SYS or must have the "ADMINISTER ANY SQL
TUNING SET" privilege.
Cause: The attempted to create a SQL Tuning Set in another schema without having
the right privilege.
Action: Connect as SYS or adjust the user's privilege and retry the operation.
ORA-13753: "SQL Tuning Set" "string" already exists for user "string".
Cause: The user attempted to create a "\SQL Tuning"\ Set using a name that already
exists for that owner.
Action: Change the name of the SQL Tuning Set and retry the operation.
ORA-13754: "SQL Tuning Set" "string" does not exist for user "string".
Cause: The user attempted to access a SQL Tuning Set that does not exist.
Action: Check the speelling of the SQL Tuning Set name and retry the operation.
ORA-13755: invalid "SQL Tuning Set" name
Cause: The user attempted to specify a SQL Tuning Set name that is invalid. A name
must not contain wildcards and its length must be less than 30 characters.
ORA-13756: Cannot update attribute "string".
Cause: The user attempted to update an attribute element that cannot be modified.
The only string attributes that can be updated are MODULE, ACTION,
PARSING_SCHEMA_NAME, PRIORITY, and OTHER.
Action: Adjust the attribute name and retry the operation.
ORA-13757: "SQL Tuning Set" "string" owned by user "string" is active.
Cause: The user attempted to update an active SQL Tuning Set.
Action: Remove all reference to the SQL Tuning Set and retry the operation.
ORA-13758: "SQL Tuning Set" "string" owned by user "string" is in use.
Cause: The user attempted to modify a SQL Tuning Set or to add a reference to a SQL
Tuning Set which is in use.
Action: Wait until the end of the previous operation and retry.
ORA-13759: User "string" cannot remove reference "string".
Cause: The user attempted to remove a SQL Tuning Set reference that does not exist.
The user might not own the reference.
Action: Check the reference ID and the reference owner and retry the operation.
ORA-13761: invalid filter
Cause: The user attempted to select data from a data source using an invalid filter. A
filter is a WHERE clause on data source content.
Action: Correct the filter and retry the operation.
ORA-13762: The string ranking measure is invalid.
Cause: The user attempted to select data from a data source using an invlaid ranking
measure. A ranking measure must represent a valid numerical expression.
Action: Correct the ranking measure and retry the operation.
ORA-13763: illegal ranking attribute "string"

Cause: The user attempted to use an attribute element that is not allowed in a ranking
measure.
Action: Check the attribute in the ranking measure and retry the operation.
ORA-13764: Value "string" is illegal as a result percentage.
Cause: The user attempted to select data from a SQL Tuning Set using an invalid
result percentage. The result percentage must be between 0 and 1.
Action: Correct the result percentage value and retry the operation.
ORA-13765: Value "string" is illegal for a result limit.
Cause: The user attempted to select data from a SQL Tuning Set using an invalid
result limit. A result limit must be a positive interger.
Action: Correct the result limit value and retry the operation.
ORA-13766: A ranking measure is required.
Cause: The user attempted to select data from a SQL Tuning Set using a percentage
argument without specifying a ranking measure.
Action: Add a ranking measure or remove the percentage argument and retry the
operation.
ORA-13767: End snapshot ID must be greater than begin snapshot ID.
Cause: The user attempted to select data from the workload repository using an
invalid snaphot ID range.
Action: Adjust the snapshot ID range and retry the operation.
ORA-13768: Snapshot ID must be between string and string.
Cause: The user attempted to select data from the workload repository using a
snaphot ID which does not exist.
Action: Adjust the snapshot ID and retry the operation.
ORA-13769: Snapshots string and string do not exist.
Cause: The user attempted to select data from the workload repository using
snapshots that do not exist.
Action: Check the snapshot identifiers and retry the operation.
ORA-13770: Baseline "string" does not exist.
Cause: The user attempted to access a baseline that does not exsit.
Action: Check the speelling of the baseline name and retry the operation.
ORA-13771: cannot obtain exclusive lock string on "SQL Tuning Set" "string"
owned by user "string"
Cause: Unexpected error from DBMS_LOCK.REQUEST.
Action: This error should not normally occur. Check your system for anomalies and
retry the operation. If this error persists, contact Oracle Support Services.
ORA-13772: unexpected deadlock on "SQL Tuning Set" "string" owned by user
"string"
Cause: Unexpected error from DBMS_LOCK.REQUEST
Action: This error should not normally occur. Check your system for anomalies and
retry the operation. If this error persists, contact Oracle Support Services.
ORA-12700 to ORA-19400 69-71
ORA-13773: insufficient privileges to select data from the cursor cache

Cause: The user attempted to perform an operation without having the appropriate
privileges on V$SQL and V$SQL_BIND_CAPTURE.
ORA-13774: insufficient privileges to select data from the workload repository
Cause: The user attempted to perform an operation without having the appropriate
privileges on views DBA_HIST_BASELINE, DBA_HIST_SQLTEXT,
DBA_HIST_SQLSTAT, DBA_HIST_SQLBIND, DBA_HIST_OPTIMIZER_ENV, and
DBA_HIST_SNAPSHOT.
ORA-13775: inconsistent datatype in input cursor
Cause: The user attempted to load a SQL Tuning Set using an invalid input cursor.
All rows in the cursor must match type SQLSET_ROW.
Action: Check the rows type in the cursor and retry the operation.
ORA-13776: User "string" has not been granted the "SELECT" privilege on the "SQL
tuning set" DBA views.
Cause: The user attempted to read a SQL tuning set belonging to someone else
without having SELECT privilege on the DBA views
Action: User should be granted the privilege or only access his own STS
ORA-13777: invalid list of attribute names
Cause: The user specified an attribute element that is not valid. The only attributes
that can be selected are NULL, BASIC, TYPICAL, ALL or a comma separated list of
the names including EXECUTION_STATISTICS, OBJECT_LIST, BIND_LIST and
SQL_PLAN.
Action: Adjust the attribute list and retry the operation.
ORA-13778: no new name or owner specified for "SQL Tuning Set"
Cause: The user attempted to call remap_stgtab_sqlset without specifying either a
new SQL tuning set name or a new SQL tuning set owner
Action: Specify at least one or the other argument as non-NULL
ORA-13779: invalid load option
Cause: The user attempted to call load_sqlset with a load option that is different than
INSERT, UPDATE and MERGE.
Action: Adjust the load option and retry the operation.
ORA-13780: SQL statement does not exist.
Cause: The user attempted to tune a SQL statement that does not exist.
Action: Verify the sql_id and the plan hash value of the statement and retry the
operation.
ORA-13781: cannot perform test-execute and explain plan operations on the
automatic SQL tuning task
Cause: The user attempted to test-execute or generate explain plans for a SQL
workload using the automatic SQL tuning task.
Action: Verify the name of the tuning task and retry the operation.
ORA-13783: invalid tuning scope

Cause: The user attempted to specify a tuning task scope that is invalid. The possible
values are LIMITED or COMPREHENSIVE.
Action: Check the scope value and retry the operation.
ORA-13784: cannot accept SQL profiles for all statements in the "string"
Cause: An attempt was made to accept SQL profiles for all statements in the input
workload.
Action: Provide the object identifier corresponding to a statement in the workload
ORA-13785: missing target object for tuning task "string"
Cause: The user attempted to perform an operation on a task without specifying a
target object or by using an invalid object identifier.
Action: Check the identifier of the object and retry the operation.
ORA-13786: missing SQL text of statement object "string" for tuning task "string"
Cause: The user attempted to accept SQL profile for an object that has not a SQL text
associated to it.
ORA-13787: missing SQL profile for statement object "string" for tuning task
"string"
Cause: The user attempted to accept a SQL profile for an object that has not a SQL
profile associated to it.
ORA-13788: invalid recommendation type
Cause: The user passed an invalid recommendation type in the rec_type argument to
script_tuning_task. Possible values are ALL or any subset of a comma-separated list
of PROFILES, STATISTICS and INDEXES.
Action: Check the rec_type arg and retry the operation.
ORA-13789: invalid process action
Cause: The user passed an invalid action to process a SQL statement. Possible value is
any subset of a comma-seperated list of EXECUTE and EXPLAIN_PLAN.
Action: Check the action argument and retry the operation.
ORA-13790: invalid value for time limit
Cause: The user passed an invalid value for the time limit argument.
Action: Check the argument specified value and retry the operation.
ORA-13791: cannot resume a task created to process a single statement
Cause: An attempt was made to resume a task that was created for a single SQL
statement. A task can be resumed only if it is used for a SQL Tuning Set.
ORA-13793: invalid comparison metric
Cause: An invalid metric to compare SQL performance was specified.
Action: Use execution statistics to compare the result of two executions and
optimizer_cost to analyze performance of two explain plan actions.
ORA-12700 to ORA-19400 69-73
ORA-13794: execution type mismatch

Cause: An attempt was made to analyze the performance of a SQL workload using
two executions that were generated using two different actions.
Action: check the name and type of task executions to analyze and retry the
operation.
ORA-13795: missing task execution
Cause: An insufficient number of valid task executions to analyze the performance of
a SQL workload were specified.
Action: run the task to generate two executions of the same type and retry the
operation.
ORA-13796: invalid value string specified for problem type
Cause: An invalid problem type was specified to the SQL diagnosis advisor. Problem
type should be one of the PROBLEM_TYPE_* defined in 'admin/dbmsdiag.sql'.
Action: Specify valid problem type.
ORA-13797: invalid SQL Id specified, string
Cause: Invalid SQL Id specified for conversion.
Action: Specify valid SQL Id.
ORA-13798: Parameter string cannot be NULL.
Cause: A call to GET_THRESHOLD procedure was made without a required
parameter.
Action: Specify a valid value for this parameter.
ORA-13799: threshold not found
Cause: No threshold was found with the specified threshold key.
ORA-13800: concurrent DDL failure on SQL repository objects
Cause: A SQL repository object was the target of two concurrent DDL operations.
Action: Check the current state of the object and retry the operation that failed.
ORA-13801: invalid value for SQLTUNE_CATEGORY parameter
Cause: An invalid Oracle identifier was used as the value of the parameter.
Action: Specify the parameter conforming to the rules for Oracle identifiers.
ORA-13802: failed to purge SQL Tuning Base entry from sql$
Cause: An error occured while try to delete a SQL Tuning Base object.
Action: Look at the underlying error(s) on the error stack.
ORA-13810: FORCE_TRACKING parameter can only be values of
NO_FORCE_TRACKING or FORCE_TRACKING
Cause: The wrong value was passed in for the parameter.
Action: Check the value and input the correct value.
ORA-13811: error encountered during the start of the operation
Cause: An internal error was encountered.
Action: Check the alert log and report to Oracle Support Services.
ORA-13812: current session does not have database operation monitored

Cause: An attempt was made to end a database operation that did not exist.
Action: Check if the database operation is being monitored.
ORA-13813: database operation name or execution ID does not match
Cause: The database operation name or execution ID did not match.
Action: Call the interface with the right database operation name and execution ID.
ORA-13825: missing SQL statement text
Cause: No SQL text was provided to the create SQL profile or patch operation.
Action: Retry with properly specified SQL text.
ORA-13826: empty SQL profile or patch not allowed
Cause: No attributes were specified to the create SQL profile or patch operation.
Action: Retry with at least one hint specified.
ORA-13827: null or zero length attribute not allowed
Cause: One of the attributes within the SQL profile or patch was not properly
specified.
Action: Retry with a fully specified SQL profile or patch.
ORA-13828: generated SQL profile or patch name string already exists
Cause: A SQL profile or patch already exists with the name generated by the system.
Action: Retry the operation as the generated name is time sensitive.
ORA-13829: SQL profile or patch named string already exists
Cause: A SQL profile or patch already exists with the name specified.
Action: Specify a different name or drop the existing SQL profile or patch.
ORA-13830: SQL profile or patch with category string already exists for this SQL
statement
Cause: A SQL profile or patch already exists for the given SQL statement and
category.
Action: Drop or update the existing SQL profile or patch.
ORA-13831: SQL profile or patch name specified is invalid
Cause: An invalid SQL profile or patch name was specified.
Action: Look for the underlying error on the error message stack.
ORA-13832: category name specified is invalid
Cause: An invalid category name swas pecified.
Action: Look for the underlying error on the error message stack.
ORA-13833: SQL profile or patch named string doesn't exist
Cause: A SQL profile or patch name was specified that doesn't exist.
Action: Verify the name of the SQL profile or patch.
ORA-13834: name of SQL profile or patch to be cloned must be provided
Cause: A SQL profile or patch name was not provided as the from target of a clone
SQL profile or patch operation.
ORA-12700 to ORA-19400 69-75
Action: Provide the name of the SQL profile or patch being cloned.
ORA-13835: invalid attribute name specified
Cause: An invalid attribute name was specified for an alter SQL profile or patch
operation.
Action: Verify the name of the attribute.
ORA-13836: invalid attribute value specified
Cause: An invalid attribute value was specified for an alter SQL profile or patch
operation.
Action: Verify the attribute value.
ORA-13837: invalid HASH_VALUE
Cause: An invalid HASH_VALUE was passed to a create SQL profile operation
Action: Verify the HASH_VALUE.
ORA-13838: invalid ADDRESS value
Cause: An invalid ADDRESS value was passed to a create SQL profile operation.
Action: Verify the ADDRESS value.
ORA-13839: V$SQL row doesn't exist with given HASH_VALUE and ADDRESS.
Cause: A HASH_VALUE and ADDRESS combination passed to the create SQL
profile operation doesn't coorespond to an existing V$SQL entry.
Action: Verify the HASH_VALUE and ADDRESS in V$SQL.
ORA-13840: Concurrent DDL Error in create SQL profile operation.
Cause: A concurrent DDL operation was performed during a create or replace sql
profile operation.
Action: Try operation again
ORA-13841: SQL profile named string already exists for a different signature/
category pair
Cause: A SQL profile already exists with the name specified under a different
signature/category pair so it cannot be replaced, even with FORCE specified.
Action: Specify a different name or drop the existing SQL profile.
ORA-13842: no SELECT privilege on DBA_SQL_PROFILES
Cause: A user has tried to perform an operation that requires SELECT privileges on
the DBA_SQL_PROFILES view.
Action: Either perform the operation as another user or get the privilege
ORA-13843: no SQL profile with name like "string" exists for category like "string"
Cause: A user tried to perform an operation by specifying a profile name/ category
filter that did not target any profiles
Action: Try a different filter after checking the profile name/category
ORA-13844: no new SQL profile name or category specified.
Cause: A user called remap_stgtab_sqlprof without specifying new values for the sql
profile name or category. At least one is required.
Action: Specify either a new profile name, or a new category, or both
ORA-13845: invalid SQL profile XML specification provided

Cause: The supplied XML specification for the SQL profile did not adhere to the
proper schema.
Action: Check the syntax and try again.
ORA-13846: Cannot create SQL plan baseline on the given plan
Cause: There are either multiple plans exist for the given value or the plan is not
reproducible.
Action: Call Oracle Support.
ORA-13847: The plan with plan hash value string does not exist
Cause: The give plan does not exist.
Action: Check the available plans.
ORA-13850: Tracing for client identifier string is not enabled
Cause: Attempt to disable a client identifier tracing which was never enabled
Action: Supply correct client identifier
ORA-13851: Tracing for client identifier string is already enabled
Cause: Attempt to enable a client identifier tracing which has been already enabled
Action: Supply correct client identifier, or disable and re-enable tracing with different
bind/wait options
ORA-13852: Tracing for service(module/action) string is not enabled
Cause: Attempt to disable a service-level tracing which was never enabled
Action: Supply correct service(module/action) name
ORA-13853: Tracing for service (module/action) string is already enabled
Cause: Attempt to enable a service-level tracing which has been already enabled
Action: Supply correct service(module/action), or disable and re-enable tracing with
different bind/wait options
ORA-13854: Tracing for service(module/action) string on instance string is not
enabled
Cause: Attempt to disable a service-level tracing which was never explicitly enabled
on a specific instance
ORA-13855: Tracing for service (module/action) string on instance string is already
enabled
Cause: Attempt to enable a service-level tracing which has been already enabled on a
specific instance
Action: Supply correct service(module/action), or disable and re-enable tracing with
different bind/wait options
ORA-13856: Service name must be specified
Cause: Omitting service name while enabling/disabling tracing or aggregation
Action: Supply the service name
ORA-13857: Invalid module name
Cause: Module name is too long (exceeding 48 characters)
ORA-12700 to ORA-19400 69-77
Action: Supply correct name

ORA-13858: Invalid action name
Cause: Action name is too long (exceeding 32 characters)
ORA-13859: Action cannot be specified without the module specification
Cause: Action name is specified, but the module name is not
Action: Supply the module name
ORA-13860: Invalid service name
Cause: Service name is too long (exceeding 64 characters)
ORA-13861: Statistics aggregation for client identifier string is already enabled
Cause: Attempt to enable a client identifier aggregation which has been already
enabled
ORA-13862: Statistics aggregation for client identifier string is not enabled
Cause: Attempt to disable a client identifier statistics aggregation which was never
enabled
ORA-13863: Statistics aggregation for service(module/action) string is not enabled
Cause: Attempt to disable a service-level statistics aggregation which was never
enabled
ORA-13864: Statistics aggregation for service (module/action) string is already
enabled
Cause: Attempt to enable a service-level statistics aggregation which has been already
enabled
Action: Supply correct service(module/action)
ORA-13865: Module name must be specified
Cause: Attempt to enable/disable a service-level statistics aggregation without a
module specification
Action: Supply module name
ORA-13866: Client identifier must be specified
Cause: Omitting client identifier while enabling/disabling tracing or aggregation
Action: Supply the client identifier
ORA-13867: Database-wide SQL tracing is already enabled
Cause: Attempt to enable a database-level tracing which has been already enabled
Action: Disable and re-enable tracing with different bind/wait options
ORA-13868: Instance-wide SQL tracing on instance string is not enabled
Cause: Attempt to disable a service-level tracing which was never explicitly enabled
on a specific instance
Action: No action required

ORA-13869: Instance-wide SQL tracing on instance string is already enabled
Cause: Attempt to enable an instance-level tracing which has been already enabled on
a specific instance
Action: Disable and re-enable tracing with different bind/wait options
ORA-13870: Database-wide SQL tracing is not enabled
Cause: Attempt to disable a database-level tracing which was never enabled
ORA-13871: Invalid instance name
Cause: Instance name is too long (exceeding 16 characters)
ORA-13900: missing or invalid parameter string
Cause: A call to SET_THRESHOLD procedure was either missing a parameter, or the
parameter was invalid.
ORA-13901: Object string was not found.
Cause: An object name was passed to SET_THRESHOLD procedure that did not map
to a valid object.
Action: Specify a valid object name.
ORA-13902: The specified file string is not a data file.
Cause: The object name was passed to a SET_THRESHOLD procedure that did not
map to a valid data file.
Action: Specify a valid data file name.
ORA-13903: Invalid combination of string threshold value and operator.
Cause: A non-positive number was used for "Blocked User Session Count" metrics
while operator contains equal.
Action: Use a positive number for the threshold value or use "greater than" operator.
ORA-13904: The file has been dropped and recreated during the procedure call.
Cause: The file on which threshold is specified was dropped and recreated during the
procedure call.
Action: Retry this operation.
ORA-13905: Critical or warning threshold have incorrect values
Cause: The tablespace threshold values can be in the range 0 to 100 only.
Action: Check the threshold values
ORA-13906: The tablespace is not of the right type.
Cause: An attempt was made to set a threshold on dictionary-managed tablespaces.
Action: Check the tablespace type and reissue the command.
ORA-13907: Threshold value is invalid.
Cause: An attempt was made to specify an invalid value for critical or warning
thresholds.
ORA-12700 to ORA-19400 69-79
Action: Use non-negative integers only for threshold values.

ORA-13908: Invalid combination of metrics id and object type parameters.
Cause: An attempt was made to specify an invalid combination of metrics id // and
object type parameters.
Action: Specify a valid combination of metrics id and object type parameters.
ORA-13909: Invalid combination of threshold value and operator.
Cause: An attempt was made to specify an invalid combination of threshold value
and operator.
Action: Check the operator and threshold values and reissue statement.
ORA-13910: Parameter string cannot be NULL.
Cause: An attempt was made to call GET_THRESHOLD procedure without a
required parameter.
ORA-13911: Threshold not found
Cause: The threshold did not exist with the specified threshold key.
ORA-13912: Critical threshold value is less than warning threshold value.
Cause: An attempt was made to call SET_THRESHOLD procedure with the critical
threshold value less than the warning threshold value.
Action: Check the threshold values and reissue the statement.
ORA-13913: The threshold cannot be set when SYSAUX is offline.
Cause: SET_THRESHOLD procedure was called when SYSAUX tablespace was
offline.
Action: Call SET_THRESHOLD procedure when SYSAUX is online.
ORA-13914: Threshold notification failed.
Cause: An error occurred when sending notification for this threshold.
Action: Make sure you have enough space on SYSAUX tablespace and retry this
operation.
ORA-13915: Critical byte based free space threshold value is greater than warning
threshold value.
Cause: An attempt was made to call SET_THRESHOLD procedure with the bytes
based critical threshold value greater than the warning threshold value.
Action: Check the threshold values and reissue the statement.
ORA-13916: Invalid value "string" specified for parameter "string"
Cause: An invalid value was specified for the the given parameter.
Action: Correct the value being specified for the parameter.
ORA-13917: Posting system alert with reason_id string failed with code [string]
[string]
Cause: Connection to the database is dead, or invalid parameter to alert routine.
Action: If this condition repeats, please contact Oracle Support.
ORA-13918: Updating system alert with reason_id string failed; previous alert not
found
Cause: System Error: An attempt to update a system alert failed. The alert was
improperly cleared from WRI$_ALERT_OUTSTANDING.
Action: Do not delete from WRI$_ALERT_OUTSTANDING. If this condition repeats,
please contact Oracle Support.
ORA-13919: Cannot specify values for parameter "string" and for parameter "string"
Cause: Can only specify a value for one or the other.
Action: Pass just one of the parameters.
ORA-13920: Threshold cannot be set when database is in read-only mode.
Cause: SET_THRESHOLD procedure was called when database was open in readonly mode.
Action: Call SET_THRESHOLD procedure when database is open in read/write
mode.
ORA-13951: MMON sub-action time limit exceeded
Cause: MMON sub-action did not complete within the system specified time frame.
Action: None
ORA-13970: Invalid name of "string" given
Cause: Passed an invalid component, report, or transformation name to the
framework. Names must be alphanumeric and can contain the underscore (_)
character.
Action: Try again with a valid name
ORA-13971: string "string" unknown
Cause: Passed an unknown component, report, or transformation to the framework.
Action: Give a different name
ORA-13972: string "string" unknown for string "string"
Cause: An object with the first name is unknown within the naming scope of the
second name
Action: Change the parameters passed in or register the proper object
ORA-13973: string unknown for string "string"
Cause: An object is unknown within the given naming scope
Action: Change the parameters passed in or register the proper object
ORA-13974: string with name "string" already exists
Cause: An object with the given name already exists
ORA-13975: string with name "string" already exists for string "string"
Cause: An object with the first name already exists within the naming scope of the
second name
ORA-13976: Improperly-formed report tag
Cause: The top-level report tag was not built properly
ORA-12700 to ORA-19400 69-81
Action: Make sure that the report tag is built using the common tag library function
ORA-13977: Invalid content type
Cause: An invalid content type was passed to the register format API
Action: Correct your code to use the values in dbmsrep.sql
ORA-13978: Invalid reference string parameter or value
Cause: An invalid parameter/value was passed to a dbms_report API
Action: Ensure that the parameter names and values are alphanumeric.
ORA-13979: Filename too long
Cause: An invalid file name was passed to STORE_FILE
Action: Ensure that the filename is less than 500 bytes
ORA-13980: Invalid file URL
Cause: A URL with invalid syntax was provided, either directly to the function or via
an XML IMPORT or INCLUDE.
ORA-13981: Invalid file URL or path prefix
Cause: Either a URL or path prefix with invalid syntax was provided.
Action: Check the URL
ORA-13982: Could not find file at URL provided
Cause: The file requested could not be found in the given location.
Action: Check the URL provided.
ORA-13983: Missing body tag from HTML
Cause: An HTML document was passed to the function missing its body tag.
Action: Check the HTML source.
ORA-13984: Invalid reference string
Cause: The given reference string could not be parsed.
Action: Check the reference string syntax.
ORA-13985: Invalid URL provided to servlet
Cause: An invalid URL was provided to the servlet.
ORA-13986: Error \string received from XPath engine
Cause: An error was received from the xpath library during an xpath operation.
Action: Check xmlerr.h to understand the cause of the error.
ORA-13987: Invalid input to build common <string> tag
Cause: Invalid input was given when attempting to build a common tag.
Action: Check the function input to make sure all necessary information is given.
ORA-13988: Invalid input given to variable argument list report function.
Cause: An invalid parameter was provided to one of the report framework variable
argument list functions.
Action: Check the function input and try again.
ORA-13989: Invalid input given to structured argument list report function.

Cause: An invalid parameter was provided to one of the report framework structured
argument list functions.
Action: Check the function input and try again.
ORA-13990: Invalid tag name given to common tag callout function.
Cause: This is an internal Server Manageability Error
ORA-14000: only one LOCAL clause may be specified
Cause: CREATE INDEX statement contained more than one LOCAL clause
Action: Specify LOCAL option at most once
ORA-14001: LOCAL clause contradicts previosly specified GLOBAL clause
Cause: CREATE INDEX statement contained a GLOBAL clause and a LOCAL clause
Action: Specify LOCAL or GLOBAL clause, but not both
ORA-14002: only one GLOBAL clause may be specified
Cause: CREATE INDEX statement contained more than one GLOBAL clause
Action: Specify GLOBAL option at most once
ORA-14003: GLOBAL clause contradicts previosly specified LOCAL clause
Cause: CREATE INDEX statement contained a LOCAL clause and a GLOBAL clause
Action: Specify GLOBAL or LOCAL clause, but not both
ORA-14004: missing PARTITION keyword
Cause: keyword PARTITION missing
ORA-14005: missing RANGE keyword
Cause: keyword RANGE missing
ORA-14006: invalid partition name
Cause: a partition name of the form identifier is expected but not present.
Action: enter an appropriate partition name.
ORA-14007: missing LESS keyword
Cause: keyword LESS missing
ORA-14008: missing THAN keyword
Cause: keyword THAN missing
ORA-14009: partition bound may not be specified for a LOCAL index partition
Cause: while parsing a CREATE INDEX statement to create a LOCAL partitioned
index, partition-description of one of partitions was found to contain VALUES LESS
THAN clause which is illegal since a LOCAL index inherits partition bounds from its
base table
ORA-12700 to ORA-19400 69-83
Action: remove all VALUES LESS THAN clauses from descriptions of LOCAL index
partitions
ORA-14010: this physical attribute may not be specified for an index partition
Cause: unexpected option was encountered while parsing physical attributes of an
index partition; valid options for Range or Composite Range partitions are
INITRANS, MAXTRANS, TABLESPACE, STORAGE, PCTFREE; only TABLESPACE
may be specified for Hash partitions
Action: remove invalid option(s) from the list of physical attributes of an index
partition
ORA-14011: names assigned to resulting partitions must be distinct
Cause: Names of partitions resulting from splitting of an existing table or index
partition are not distinct
Action: rename resulting partition(s) to ensure that their names are distinct and
different from those of any other partition of the table or index
ORA-14012: resulting partition name conflicts with that of an existing partition
Cause: Name of a partition resulting from splitting of an existing table or index
partition is identical to that of some other existing partition of that table or index
Action: rename resulting partition(s) to ensure that their names are distinct and
different from those of any other partition of the table or index
ORA-14013: duplicate partition name
Cause: Name of a partition of a table or index being created is not unique
Action: rename partition(s) to ensure that their names are unique among partitions of
the table or index being created
ORA-14014: maximum number of partitioning columns is 16
Cause: number of columns in a partitioning column list exceeded the legal limit of 16
Action: modify partitioning column list so that it consists of at most 16 columns
ORA-14015: too many partition descriptions
Cause: CREATE TABLE or CREATE INDEX contained too many partition
descriptions; maximum number of partitions is 1048575 (1024K-1).
Action: Reduce number of partitions to not exceed 1048575 (1024K -1).
ORA-14016: underlying table of a LOCAL partitioned index must be partitioned
Cause: User attempted to create a LOCAL partitioned index on a non-partitioned
table which is illegal. Only GLOBAL indices (partitioned or otherwise) may be
created on a non-partitioned table.
Action: Correct the statement and reenter
ORA-14017: partition bound list contains too many elements
Cause: Partition bound list contained more elements than there are partitioning
columns
Action: Ensure that the number of elements in partition bound list is equal to the
number of partitioning columns of the table or index
ORA-14018: partition bound list contains too few elements
Cause: Partition bound list contained fewer elements than there are partitioning
columns
ORA-14019: partition bound element must be one of: string, datetime or interval
literal, number, or MAXVALUE
Cause: Partition bound list contained an element of invalid type (i.e. not a number,
non-empty string, datetime or interval literal, or MAXVALUE)
Action: Ensure that all elements of partition bound list are of valid type
ORA-14020: this physical attribute may not be specified for a table partition
Cause: unexpected option was encountered while parsing physical attributes of a
table partition; valid options for Range or Composite Range partitions are INITRANS,
MAXTRANS, TABLESPACE, STORAGE, PCTFREE, and PCTUSED; only
TABLESPACE may be specified for Hash partitions
Action: remove invalid option(s) from the list of physical attributes of a table partition
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: Ensure that VALUES LESS THAN clause for the last partition of a GLOBAL
index has MAXVALUE specified for all columns
ORA-14022: creation of LOCAL partitioned cluster indices is not supported
Cause: An attempt was made to create a LOCAL partitioned cluster index, which is
currently illegal
Action: Remove LOCAL along with partition descriptions, if any, from the CREATE
INDEX statement.
ORA-14023: creation of GLOBAL partitioned cluster indices is not supported
Cause: An attempt was made to create a GLOBAL partitioned cluster index, which is
currently illegal
Action: Remove PARTITION BY RANGE clause along with partition descriptions from
the CREATE INDEX statement.
ORA-14024: number of partitions of LOCAL index must equal that of the
underlying table
Cause: User attempted to create a LOCAL partitioned index with a number of
partitions which is different from that of the underlying table.
Action: Correct the CREATE INDEX statement to specify a correct number of
partitions
ORA-14025: PARTITION may not be specified for a materialized view or a
materialized view log
Cause: PARTITION option was encountered while parsing a definition of a
materialized view or a materialized view log
Action: Ensure that a definition of a MATERIALIZED VIEW does not include invalid
options
ORA-14026: PARTITION and CLUSTER clauses are mutually exclusive
Cause: definition of a table contained both PARTITION and CLUSTER clauses which
is illegal
Action: Remove one of the conflicting clauses
ORA-12700 to ORA-19400 69-85
ORA-14027: only one PARTITION clause may be specified

Cause: CREATE TABLE statement contained more than one PARTITION clause
Action: Specify PARTITION option at most once
ORA-14028: missing AT or VALUES keyword
Cause: keyword AT or VALUES missing
ORA-14029: GLOBAL partitioned index must be prefixed
Cause: partitioning columns of a global partitioned index must form a prefix of the
index' key columns
Action: Ensure that the GLOBAL partitioned index being created is prefixed
ORA-14030: non-existent partitioning column in CREATE TABLE statement
Cause: Partitioning column specified in CREATE TABLE statement is not one of
columns of the table being created.
Action: Ensure that all columns in the partitioning column list are columns of the
table being created.
ORA-14031: partitioning column may not be of type LONG or LONG RAW
Cause: Partitioning column specified by the user was of type LONG or LONG RAW,
which is illegal.
Action: Ensure that no partitioning column is of type LONG or LONG RAW.
ORA-14032: partition bound of partition number string is too high
Cause: High bound of the partition whose number (partitions are numbered starting
with 1) is displayed in this message did not collate lower than that of the following
partition, which is illegal.
Action: Ensure that high bound of every partition (except for the last one) collates
lower than that of a following partition.
ORA-14036: partition bound value too large for column
Cause: Length of partition bound value is longer than that of the corresponding
partitioning column.
Action: Ensure that lengths of high bound values do not exceed those of
corresponding partitioning columns
ORA-14037: partition bound of partition "string" is too high
Cause: High bound of the partition whose name (explicitly specified by the user) is
displayed in this message did not collate lower than that of the following partition,
which is illegal.
Action: Ensure that high bound of every partition (except for the last one) collates
lower than that of a following partition.
ORA-14038: GLOBAL partitioned index must be prefixed
Cause: User attempted to create a GLOBAL non-prefixed partitioned index which is
illegal
Action: If the user, indeed, desired to create a non-prefixed index, it must be created
as LOCAL; otherwise, correct the list of key and/or partitioning columns to ensure
that the index is prefixed
ORA-14039: partitioning columns must form a subset of key columns of a UNIQUE

index
Cause: User attempted to create a UNIQUE partitioned index whose partitioning
columns do not form a subset of its key columns which is illegal
Action: If the user, indeed, desired to create an index whose partitioning 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 partitioning columns to ensure that the index'
partitioning columns form a subset of its key columns
ORA-14041: partition bound may not be specified for resulting partitions
Cause: while parsing an ALTER {TABLE|INDEX} SPLIT PARTITION statement,
partition-description of a resulting partition was found to contain VALUES LESS
THAN clause which is illegal
Action: remove VALUES LESS THAN clause from the description(s) of partitions
resulting from splitting an existing table or index partition
ORA-14042: partition bound may not be specified for a partition being moved,
modified or rebuilt
Cause: while parsing an ALTER {TABLE|INDEX} MODIFY PARTITION, ALTER
TABLE MOVE PARTITION, or ALTER INDEX REBUILD PARTITION statement,
description of new physical attributes of the partition being moved, modified, or
rebuilt was found to contain VALUES LESS THAN clause which is illegal
Action: remove VALUES LESS THAN clause from the description of new attributes of
the partition being moved, modified, or rebuilt
ORA-14043: only one partition may be added
Cause: ALTER TABLE ADD PARTITION contained descriptions of more than one
partition to be added
Action: Ensure that the statement contains exactly one partition definition and that it
does not contain any commas
ORA-14044: only one partition may be moved
Cause: ALTER TABLE MOVE PARTITION contained descriptions of more than one
partition to be moved
Action: Ensure that the statement describes exactly one partition to be moved and that
it does not contain any commas
ORA-14045: only one partition may be modified
Cause: ALTER TABLE|INDEX MODIFY PARTITION contained descriptions of more
than one partition to be modified
Action: Ensure that the statement describes exactly one partition to be modified and
that it does not contain any commas
ORA-14046: a partition may 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 was to be
split
Action: Ensure that the statement describes exactly two partition into which an
existing partition is to be split
ORA-12700 to ORA-19400 69-87
ORA-14047: ALTER TABLE|INDEX RENAME may not be combined with other

operations
Cause: ALTER TABLE or ALTER INDEX statement attempted to combine a
RENAME operation with some other operation which is illegal
Action: Ensure that RENAME operation is the sole operation specified in ALTER
TABLE or ALTER INDEX statement;
ORA-14048: a partition maintenance operation may not be combined with other
operations
Cause: ALTER TABLE or ALTER INDEX statement attempted to combine a partition
maintenance operation (e.g. MOVE PARTITION) with some other operation (e.g.
ADD PARTITION or PCTFREE which is illegal
Action: Ensure that a partition maintenance operation is the sole operation specified
in ALTER TABLE or ALTER INDEX statement; operations other than those dealing
with partitions, default attributes of partitioned tables/indices or specifying that a
table be renamed (ALTER TABLE RENAME) may be combined at will
ORA-14049: invalid ALTER TABLE MODIFY PARTITION option
STORAGE, BACKUP, ALLOCATE EXTENT, or DEALLOCATE UNUSED was
specified in an ALTER TABLE MODIFY PARTITION statement for a Range or
Composite Range partition.
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.
ORA-14051: invalid ALTER MATERIALIZED VIEW option
STORAGE, or BACKUP was specified in an ALTER MATERIALIZED VIEW
statement.
ORA-14052: partition-extended table name syntax is disallowed in this context
Cause: User attempted to use partition-extended table name syntax in illegal context
(i.e. not in FROM-clause or INSERT, DELETE, or UPDATE statement)
Action: Avoid use of partition-extended table name in contexts other those mentioned
above.
ORA-14053: illegal attempt to modify string in string statement
Cause: Certain attributes of objects (e.g. tables) may be specified at creation time, but
may not be modified using ALTER statement. Unfortunately, user specified one of
such attributes.
Action: Ensure that ALTER statement specifies new values only for attributes which
may be changed once an object has been created
ORA-14054: invalid ALTER TABLE TRUNCATE PARTITION option
Cause: Name of the partition to be truncated may be followed by DROP STORAGE or
REUSE STORAGE
Action: Ensure that no options besides DROP STORAGE or REUSE STORAGE are
specified with ALTER TABLE TRUNCATE PARTITION
ORA-14055: keyword REBUILD in ALTER INDEX REBUILD must immediately
follow index name
Cause: ALTER INDEX statement contained REBUILD keyword following some index
attributes (e.g. INITRANS.)
Action: Ensure that keyword REBUILD immediately follows the name of the index
being altered
ORA-14056: partition number string: sum of PCTUSED and PCTFREE may not
exceed 100
Cause: the sum of PCTUSED and PCTFREE for a partition whose number (partitions
are numbered starting with 1) is displayed in this message exceeds 100. Note that if
PCTUSED and/or PCTFREE values for this partition were not specified explicitly,
default values for the partitioned table or index would be used. If, in turn, default
PCTUSED and/or PCTFREE values for the partitioned table or index were not
specified, system defaults would be used.
Action: ensure that a sum of PCTUSED and PCTFREE for the partition does not
exceed 100
ORA-14057: partition "string": sum of PCTUSED and PCTFREE may not exceed 100
Cause: the sum of PCTUSED and PCTFREE for a partition whose name (explicitly
specified by the user) is displayed in this message exceeds 100. Note that if PCTUSED
and/or PCTFREE values for this partition were not specified explicitly, default values
for the partitioned table or index would be used. If, in turn, default PCTUSED and/or
PCTFREE values for the partitioned table or index were not specified, system defaults
would be used.
Action: ensure that a 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: Value of INITRANS was found to be greater than that of MAXTRANS for a
partition whose number (partitions are numbered starting with 1) is displayed in this
message. Note that if INITRANS and/or MAXTRANS values for this partition were
not specified explicitly, default values for the partitioned table or index would be
used. If, in turn, default INITRANS and/or MAXTRANS values for the partitioned
table or index were not specified, system defaults would be used.
Action: ensure that value of INITRANS (whether specified explcitly or derived from
the default value for the partitioned table or index) is no greater than that of
MAXTRANS
ORA-14059: partition "string": INITRANS value must be less than MAXTRANS
value
partition whose name (explicitly specified by the user) is displayed in this message.
Note that if INITRANS and/or MAXTRANS values for this partition were not
specified explicitly, default values for the partitioned table or index would be used. If,
in turn, default INITRANS and/or MAXTRANS values for the partitioned table or
index were not specified, system defaults would be used.
ORA-12700 to ORA-19400 69-89
Action: ensure that value of INITRANS (whether specified explcitly or derived from
the default value for the partitioned table or index) is no greater than that of
MAXTRANS
ORA-14060: data type or length of a table partitioning column may not be changed
Cause: User issued ALTER TABLE statement attempting to modify data type and/or
length of a column used to partition the table named in ALTER TABLE statement,
which is illegal
Action: Avoid modifying data type and/or length of table partitioning column(s)
ORA-14061: data type or length of an index partitioning column may not be
changed
length of a column used to partition some index defined on the table named in
ALTER TABLE statement, which is illegal
Action: Avoid modifying data type and/or length of index partitioning column(s)
ORA-14062: one or more of table's partitions reside in a read-only tablespace
Cause: User issued ALTER TABLE statement attempting to modify an existing
VARCHAR2 (or VARCHAR) column to be of type CHAR (or CHARACTER), increase
length of an existing CHAR (or CHARACTER) column, or add a column with userspecified default for a table one or more partitions of which reside in read-only
tablespaces, which is illegal
Action: Avoid performing aformentioned operations on a partitioned table one or
more partitions of which reside in read-only tablespaces
ORA-14063: Unusable index exists on unique/primary constraint key
Cause: User attempted to add or enable a primary key/unique constraint on
column(s) of a table on which there exists an index marked Index Unusable.
Action: Drop the existing index or rebuild it using ALTER INDEX REBUILD
ORA-14064: Index with Unusable partition exists on unique/primary constraint key
Cause: User attempted to add or enable a primary key/unique constraint on
column(s) of a table on which there exists an index one or more partitions of which
are marked Index Unusable.
Action: Drop the existing index or rebuild unusable partitions it using ALTER INDEX
REBUILD PARTITION
ORA-14065: ALLOCATE STORAGE may not be specified for a partitioned table
Cause: User specified ALLOCATE STORAGE clause in ALTER TABLE statement
issued against a partitioned table which is illegal.
Action: Remove the illegal option. If it is desired to add storage to individual
partitions, ALLOCATE STORAGE clause may be specified with ALTER TABLE
MODIFY PARTITION statement.
ORA-14066: illegal option for a non-partitioned index-organized table
Cause: An attempt was made to issue a CREATE or ALTER TABLE command on a
non-partitioned IOT, but the command contains an option that is legal only for
partitioned index-organized tables. Such options are: ENABLE ROW MOVEMENT
and DISABLE ROW MOVEMENT.
Action: Remove the illegal option(s) from the command.
ORA-14067: duplicate TABLESPACE_NUMBER specification

Cause: TABLESPACE_NUMBER clause was specified more than once for an table,
index or an index partition
Action: Correct the code generating text of CREATE INDEX statement sent to the
slaves
ORA-14068: TABLESPACE and TABLESPACE_NUMBER may not be both
specified
Cause: Both TABLESPACE and TABLESPACE_NUMBER clauses were specified for a
table, index or an index partition
slaves
ORA-14069: invalid TABLESPACE_NUMBER value
Cause: The TABLESPACE_NUMBER value is not an integer between 0 and
0x7FFFFFFF
slaves
ORA-14070: option may be specified only for partitioned indices or with REBUILD
Cause: User issued ALTER INDEX statament containing an option which is legal only
for partitioned indices or in conjunction with REBUILD against a non-partitioned
index. Such options are: PCTFREE, TABLESPACE, [NO]PARALLEL and INITIAL,
FREELISTS, and FREELIST GROUPS inside STORAGE clause
Action: Remove illegal option(s).
ORA-14071: invalid option for an index used to enforce a constraint
Cause: An option other than COMPRESS, NOCOMPRESS, PCTFREE, INITRANS,
MAXTRANS, STORAGE, TABLESPACE, PARALLEL, NOPARALLEL,
RECOVERABLE, UNRECOVERABLE, LOGGING, NOLOGGING, LOCAL, or
GLOBAL was specified for an index used to enforce a constraint.
Action: Choose one of the valid index options.
ORA-14072: fixed table may not be truncated
Cause: User attempted to truncate a fixed table which is illegal.
Action: Ensure that the table being truncated is not a fixed table.
ORA-14073: bootstrap table or cluster may not be truncated
Cause: User attempted to truncate a bootstrap table or cluster which is illegal
Action: Ensure that the table (or cluster) being truncated is not a bootstrap table (or
cluster)
ORA-14074: partition bound must collate higher than that of the last partition
Cause: Partition bound specified in ALTER TABLE ADD PARTITION statement did
not collate higher than that of the table's last partition, which is illegal.
Action: Ensure that the partition bound of the partition to be added collates higher
than that of the table's last partition.
ORA-14075: partition maintenance operations may only be performed on
partitioned indices
Cause: Index named in ALTER INDEX partition maintenance operation is not
partitioned, making a partition maintenance operation, at best, meaningless
ORA-12700 to ORA-19400 69-91
Action: Ensure that the index named in ALTER INDEX statement specifying a
partition maintenance operation is, indeed, partitioned
ORA-14076: submitted alter index partition/subpartition operation is not valid for
local partitioned index
Cause: User attempted to either drop, split, add or coalesce a partition or a
subpartition of a local index which is illegal.
Action: Ensure that the index named in such statement is a global partitioned index.
ORA-14078: you may not drop the highest partition of a GLOBAL index
Cause: User attempted to drop highest partition of a GLOBAL index, which is illegal.
Action: Ensure that the partition specified in ALTER INDEX DROP PARTITION
statement is not the highest partition of the index.
ORA-14079: illegal option for a partition marked Index Unusable
Cause: ALTER INDEX MODIFY PARTITION statement against an index partition
marked Index Unusable contained STORAGE and/or DEALLOCATE SPACE clauses
which is illegal
Action: Ensure that only valid optins are specified
ORA-14080: partition cannot be split along the specified high bound
Cause: User attempted to split a partition along a bound which either collates higher
than that of the partition to be split or lower than that of a partition immediately
preceding the one to be split
Action: Ensure that the bound along which a partition is to be split collates lower than
that of the partition to be split and higher that that of a partition immediately
preceding the one to be split
ORA-14081: new partition name must differ from the old partition name
Cause: User entered ALTER TABLE/INDEX RENAME PARTITION specifying newpartition-name which is identical to the name of the partition being renamed
Action: Ensure that the new partition name is different from the name of any
(including the one being renamed) existing partition of a given table or index
ORA-14082: new partition name must differ from that of any other partition of the
object
Cause: User entered ALTER TABLE/INDEX RENAME PARTITION specifying newpartition-name which is identical to the name of some existing partition of the object
Action: Ensure that the new partition name is different from the name of any
(including the one being renamed) existing partition of a given table or index
ORA-14083: cannot drop the only partition of a partitioned table
Cause: A drop partition command is being executed when there is only one partition
in the table
Action: Ensure that there is at least one partition. Drop table to remove all partitions
ORA-14084: you may specify TABLESPACE DEFAULT only for a LOCAL index
Cause: User attempted to specify TABLESPACE DEFAULT for an object other than a
LOCAL index, which is illegal.
Action: Reenter the statement without TABLESPACE DEFAULT clause.
ORA-14085: partitioned table cannot have column with LONG datatype

Cause: User tried to create a partitioned table with a LONG datatype or tried to add a
LONG datatype column to a partitioned table.
Action: LONG data types are not supported with partitioned tables. Create table
without LONG column or change table to not partitioned. If adding column, do not
use LONG datatype. If modifying attributes of a column to change data type to
LONG, it has to be a non partitioned table.
ORA-14086: a partitioned index may not be rebuilt as a whole
Cause: User attempted to rebuild a partitioned index using ALTER INDEX REBUILD
statement, which is illegal
Action: Rebuild the index a partition at a time (using ALTER INDEX REBUILD
PARTITION) or drop and recreate the entire index
ORA-14094: invalid ALTER TABLE EXCHANGE PARTITION option
Cause: Name of the table to be EXCHANGED has to be followed by [{INCLUDING|
EXCLUDING} INDEX][{WITH|WITHOUT} VALIDATION]
Action: Ensure that no options besides INCLDING INDEX or EXCLUDING INDEX
are specified with ALTER TABLE EXCHANGE PARTITION
ORA-14095: ALTER TABLE EXCHANGE requires a non-partitioned, non-clustered
table
Cause: The table in the EXCHANGE operation is either clustered or partitioned
Action: Ensure that the table with which the partition is being exchanged for is not
partitioned or clustered.
ORA-14096: tables in ALTER TABLE EXCHANGE PARTITION must have the
same number of columns
Cause: The two tables specified in the EXCHANGE have different number of columns
Action: Ensure that the two tables have the same number of columns with the same
type and size.
ORA-14097: column type or size mismatch in ALTER TABLE EXCHANGE
PARTITION
Cause: The corresponding columns in the tables specified in the ALTER TABLE
EXCHANGE PARTITION are of different type or size
type and size.
ORA-14098: index mismatch for tables in ALTER TABLE EXCHANGE
PARTITION
Cause: The two tables specified in the EXCHANGE have indexes which are not
equivalent
Action: Ensure that the indexes for the two tables have indexes which follow this rule
For every non partitioned index for the non partitioned table, there has to be an
identical LOCAL index on the partitioned table and vice versa. By identical, the
column position, type and size have to be the same.
ORA-14099: all rows in table do not qualify for specified partition
Cause: There is at least one row in the non partitioned table which does not qualify
for the partition specified in the ALTER TABLE EXCHANGE PARTITION
ORA-12700 to ORA-19400 69-93
Action: Ensure that all the rows in the segment qualify for the partition. Perform the
alter table operation with the NO CHECKING option. Run ANALYZE table
VALIDATE on that partition to find out the invalid rows and delete them.
ORA-14100: partition extended table name cannot refer to a remote object
Cause: User attempted to use partition-extended table name syntax in conjunction
with remote object name which is illegal
ORA-14101: partition extended table name cannot refer to a synonym
Cause: User attempted to use partition-extended table name syntax in conjunction
with synonym name which is illegal
ORA-14102: only one LOGGING or NOLOGGING clause may 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 may not be combined with
RECOVERABLE/UNRECOVERABLE
Cause: A statement contained both [NO]LOGGING and [UN]RECOVERABLE clauses
which is disallowed.
Action: Remove one of the offending clauses. [UN]RECOVERABLE is being
deprecated in V8 and will be obsoleted in V9. To duplicate semantics of
UNRECOVERABLE clause, create an object with NOLOGGING option and then
ALTER it specifying LOGGING. To duplicate semantics of RECOVERABLE clause,
create an object with LOGGING option.
ORA-14104: RECOVERABLE/UNRECOVERABLE may not be specified for
partitioned tables/indices
Cause: CREATE TABLE/INDEX statement used to create a partitioned table/index
contained RECOVERABLE or UNRECOVERABLE clause which is illegal
Action: Remove offending clause. [UN]RECOVERABLE is being deprecated in V8
and will be obsoleted in V9. To duplicate semantics of UNRECOVERABLE clause,
create an object with NOLOGGING option and then ALTER it specifying LOGGING.
To duplicate semantics of RECOVERABLE clause, create an object with LOGGING
option.
ORA-14105: RECOVERABLE/UNRECOVERABLE may not be specified in this
context
Cause: RECOVERABLE/UNRECOVERABLE clause is not allowed in this context.
Action: Remove offending clause. RECOVERABLE/UNRECOVERABLE may only be
specified in CREATE TABLE/INDEX statement describing a non-partitioned table or
index and ALTER INDEX REBUILD statement. [UN]RECOVERABLE is being
deprecated in V8 and will be obsoleted in V9. To duplicate semantics of
UNRECOVERABLE clause, create an object with NOLOGGING option and then
ALTER it specifying LOGGING. To duplicate semantics of RECOVERABLE clause,
create an object with LOGGING option.
ORA-14106: LOGGING/NOLOGGING may not be specified for a clustered table

Cause: User attempted to specify LOGGING or NOLOGGING clausein CREATE
TABLE or ALTER TABLE statement involving a clustered table
Action: Remove offending clause.
ORA-14107: partition specification is required for a partitioned object
Cause: parameter which supplies partition name is missing. This parameter is
optional for non-partitioned objects, but is required for partitioned objects.
Action: supply missing parameter
ORA-14108: illegal partition-extended table name syntax
Cause: Partition to be accessed may only be specified using its name. User attempted
to use a partition number or a bind variable.
Action: Modify statement to refer to a partition using its name
ORA-14109: partition-extended object names may only be used with tables and
editioning views
Cause: An attempt was made to use a partition-extended object name with an object
which was not a table or an editioning view.
Action: Avoid using partition-extended name syntax with objects which are not tables
or editioning views
ORA-14110: partitioning column may not be of type ROWID
Cause: Partitioning column specified by the user was of type ROWID, which is illegal.
Action: Ensure that no partitioning column is of type ROWID.
ORA-14111: creation of a GLOBAL partitioned index 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 PARTITION BY RANGE/HASH clause along with any partition
descriptions to create a GLOBAL non-partitioned index on a clustered table
ORA-14112: RECOVERABLE/UNRECOVERABLE may not be specified for a
partition or subpartition
Cause: Description of a partition or subpartition found in CREATE TABLE/INDEX
statement contained RECOVERABLE or UNRECOVERABLE clause which is illegal
Action: Remove offending clause. Use LOGGING or NOLOGGING instead.
ORA-14113: partitioned table cannot have column with LOB datatype
Cause: User tried to create a partitioned table with a LOB datatype or tried to add a
LOB datatype column to a partitioned table.
Action: LOB data types are not supported with partitioned tables. Create table
without LOB column or change table to not partitioned. If adding column, do not use
LOB datatype. If modifying attributes of a column to change data type to LOB, it has
to be a non partitioned table.
ORA-14114: partitioned table cannot have column with object, REF, nested table,
array datatype
Cause: User tried to create a partitioned table with a object datatype (object, REF,
nested table, array) or tried to add a object datatype column to a partitioned table.
ORA-12700 to ORA-19400 69-95
Action: object data types are not supported with partitioned tables. Create table
without object column or change table to not partitioned. If adding column, do not
use object datatypes. If modifying attributes of a column to change data type to object,
it has to be a non partitioned table.
ORA-14115: partition bound of partition number string is too long
Cause: Length of linear key representation of a high bound of the partition whose
number (partitions are numbered starting with 1) is displayed in this message
exceeded the legal limit (4K).
Action: Change representation of a partition high bound to bring its length within
legal limit.
ORA-14116: partition bound of partition "string" is too long
Cause: Length of linear key representation of a high bound of the partition whose
name (explicitly specified by the user) is displayed in this message exceeded the legal
limit (4K).
legal limit.
ORA-14117: partition resides in offlined tablespace
Cause: User attempted an operation requiring that we access data in a partition which
resides in a tablespace which was taken offline. Such operations include trying to
drop a tablespace of a table which has indices defined on it or is referenced by a
constraint.
Action: Bring tablespace online before attempting the operation.
ORA-14118: CHECK constraint mismatch in ALTER TABLE EXCHANGE
PARTITION
EXCHANGE PARTITION statement have CHECK constraint defined on them.
Action: Ensure that the two tables do not have CHECK constraint defined on any
column
ORA-14119: specified partition bound is too long
Cause: Length of a linear key representation of a high bound of a table partition being
added or along which an existing table or index partition is being split exceeded the
legal limit (4K).
legal limit.
ORA-14120: incompletely specified partition bound for a DATE column
Cause: An attempt was made to use a date expression whose format does not fully
(i.e. day, month, and year (including century)) specify a date as a partition bound for
a DATE column. The format may have been specified explicitly (using TO_DATE()
function) or implicitly (NLS_DATE_FORMAT).
Action: Ensure that date format used in a partition bound for a DATE column
supports complete specification of a date (i.e. day, month, and year (including
century)). If NLS_DATE_FORMAT does not support complete (i.e. including the
century) specification of the year, use TO_DATE() (e.g. TO_DATE('01-01-1999', 'MMDD-YYYY') to fully express the desired date.
ORA-14121: MODIFY DEFAULT ATTRIBUTES may not be combined with other

operations
Cause: ALTER TABLE or ALTER INDEX statement attempted to combine MODIFY
DEFAULT ATTRIBUTES with some other operation (e.g. ADD PARTITION or
PCTFREE) which is illegal
Action: Ensure that MODIFY DEFAULT ATTRIBUTES is the sole operation specified
ORA-14122: only one REVERSE or NOREVERSE clause may be specified
Cause: Both REVERSE and NOREVERSE were specified in CREATE INDEX
statement.
Action: Remove all but one of the REVERSE or NOREVERSE clauses and reissue the
statement.
ORA-14123: duplicate NOREVERSE clause
Cause: NOREVERSE was specified more than once in ALTER INDEX statement.
Action: Remove all but one of the NOREVERSE clauses and reissue the statement.
ORA-14124: duplicate REVERSE clause
Cause: REVERSE was specified more than once in ALTER INDEX or CREATE INDEX
statements.
Action: Remove all but one of the REVERSE clauses and reissue the statement.
ORA-14125: REVERSE/NOREVERSE may not be specified in this context
Cause: REVERSE/NOREVERSE clause is not allowed in this context.
Action: Remove offending clause. REVERSE may be specified as an attribute of an
index (not of an individual partition, if creating a partitioned index) in CREATE
INDEX statement and ALTER INDEX REBUILD statement. NOREVERSE may be
specified only in ALTER INDEX REBUILD statement.
ORA-14126: only a parallel clause may follow description(s) of resulting partitions
Cause: Descriptions of partition(s) resulting from splitting of a table or index partition
may be followed by an optional parallel clause which applies to the entire statement
and which, in turn, may not be followed by any other clause.
Action: Ensure that all partition attributes appear within the parenthesized list of
descriptions of resulting partitions in ALTER TABLE/INDEX SPLIT PARTITION
statement.
ORA-14128: FOREIGN KEY constraint mismatch in ALTER TABLE EXCHANGE
PARTITION
EXCHANGE PARTITION statement have different FOREIGN KEY constraints.
Action: Ensure that the two tables do not have FOREIGN KEY constraints defined on
any column or disable all FOREIGN KEY constraints on both tables. Then retry the
operation.
ORA-12700 to ORA-19400 69-97
ORA-14129: INCLUDING INDEXES must be specified as tables have enabled

UNIQUE constraints
Cause: Matching UNIQUE constraints in both table are enabled and validated but
INCLUDING INDEXES is not specified in ALTER TABLE EXCHANGE PARTITION|
SUBPARTITION command.
Action: Disable currently enabled matching UNIQUE constraints on both tables or
ensure that INCLUDING INDEXES option is used.
ORA-14130: UNIQUE constraints mismatch in ALTER TABLE EXCHANGE
PARTITION
Cause: One of the tables named in the ALTER TABLE EXCHANGE PARTITION
command has a UNIQUE constraint for which no matching (vis-a-vis key columns)
constraint is defined on the other table or a matching constraint is defined on the
other table, but it differs from that defined on the first table vis-a-vis being enabled
and/or validated.
Action: Ensure that for every UNIQUE constraint defined on one of the tables named
in the ALTER TABLE EXCHANGE PARTITION statement there is a matching (vis-avis key columns and being enabled and/or validated) UNIQUE constraint defined on
the other table. If UNIQUE constrains are enabled, UNIQUE constraints on the
partitioned table should be enforced using local indexes.
ORA-14131: enabled UNIQUE constraint exists on one of the tables
Cause: One of the tables referenced in the ALTER TABLE EXCHANGE PARTITION|
SUBPARTITION statement has enabled UNIQUE constraint(s) defined on it, which
prevents EXCHANGE from proceeding.
Action: Disable constraints defined on tables referenced in the ALTER TABLE
EXCHANGE PARTITION|SUBPARTITION statement and retry the statement.
ORA-14132: table cannot be used in EXCHANGE
Cause: An attempt was made to issue an ALTER TABLE EXCHANGE PARTITION |
SUBPARTITION command, but the non-partitioned table cannot be used in the
EXCHANGE because one or more of the following apply: - it is a typed table - it is a
temporary table - it contains ADT columns - it contains nested-table columns - it
contains REF columns - it contains array columns - it is an index-organized table - it
contains LOB columns - it is a nested table - it is created with row dependency and
the partitioned table is not - it is created without row dependency and the partitioned
table is
Action: Make sure the non-partitioned table does not violate any of the above
restrictions for the 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 ALTER TABLE
statement;
ORA-14134: indexes cannot use both DESC and REVERSE
Cause: An attempt was made to make a reverse index with some index columns
marked DESC.
Action: Do not use DESC in reverse indexes. The rule-based optimizer can scan
indexes backwards, which allows a normal reverse index to simulate a reverse index
with columns marked DESC.
ORA-14135: a LOB column cannot serve as a partitioning column

Cause: An attempt was made to specify a column of type BLOB or CLOB as a
partitioning or subpartitioning column.
Action: Ensure that no partitioning or subpartitioning column is of type BLOB or
CLOB.
ORA-14136: ALTER TABLE EXCHANGE restricted by fine-grained security
Cause: User doing exchange does not have full table access due to VPD policies.
Action: Grant exempt priviliges to this user.
ORA-14137: Table in partially dropped state, submit DROP TABLE PURGE
Cause: An attempt was made to access a partitioned table in a partially dropped state.
Action: Submit DROP TABLE table PURGE to drop the table.
ORA-14138: An unexpected error encountered during drop table operation
Cause: Drop table encountered an unexpected error.
Action: a. Submit drop table table purge, or b. If the situation described in the next
error on the stack can be corrected, do so. c. Contact Oracle Support.
ORA-14139: table string.string is already in read-only mode
Cause: an attempt was made to set a read-only table in read-only mode
Action: this DDL can only be executed on a read/write table
ORA-14140: table string.string is already in read/write mode
Cause: an attempt was made to set a read/write table in read/write mode
Action: this DDL can only be executed on a read-only table
ORA-14141: ALTER INDEX VISIBLE|INVISIBLE may not be combined with other
operations
Cause: ALTER INDEX statement attempted to combine a VISIBLE|INVISIBLE
operation with some other operation which is illegal
Action: Ensure that VISIBLE|INVISIBLE operation is the sole operation specified in
ALTER INDEX statement
ORA-14142: ALTER INDEX VISIBLE|INVISIBLE may not be used with certain
types of index
Cause: Using the ALTER INDEX VISIBLE|INVISIBLE statement on certain types of
indexes (IOT-TOP, Cluster indexes) is illegal.
Action: Remove the option VISIBLE|INVISIBLE.
ORA-14143: CREATE INDEX INVISIBLE may not be used with this type of index
Cause: Certain types of indexes (IOT-TOP, Cluster indexes) cannot be created
invisible.
Action: Remove the option INVISIBLE
ORA-14145: only one UNUSABLE clause may be specified
Cause: UNUSABLE was specified more than once.
Action: Remove all but one of the UNUSABLE clauses and reissue the statement.
ORA-14146: Old CONNECT BY does not support partitioned tables
Cause: The query used the old CONNECT BY clause on a partitioned object.
ORA-12700 to ORA-19400 69-99
Action: Disable old CONNECT BY by disabling the _old_connect_by_enabled

parameter.
ORA-14147: There is an existing VISIBLE index defined on the same set of
columns.
Cause: An attempt was made to define more than one VISIBLE index on the same set
of columns. There can be only one VISIBLE index on the same set of columns. Hence
ALTER INDEX VISIBLE was not supported on this index.
Action: Make all the indexes defined on the same set of columns as INVISIBLE and
then reexecute this DDL.
ORA-14148: DML and DDL operations are not directly allowed on the guardcolumn.
Cause: An attempt was made to execute a DML or a DDL directly on the guardcolumn.
Action: This is not supported.
ORA-14150: missing SUBPARTITION keyword
Cause: keyword SUBPARTITION missing
ORA-14151: invalid table partitioning method
Cause: Invalid partitioning method was specified in CREATE TABLE statement. A
table may be partitioned by RANGE, HASH, LIST, SYSTEM, or Composite RangeHash/List/Range (R+H/L/R).
Action: Specify one of valid partitioning methods
ORA-14152: invalid number of partitions specified in PARTITIONS clause
Cause: number-of-partitions clause contained in CREATE TABLE or CREATE INDEX
statement specified a number of partitions outside of legal range (1-1048575)
Action: Specify a number between 1 and 1024K-1 in the number-of-partitions clause
ORA-14153: only one of STORE IN or partition-description clause may be specified
Cause: both STORE IN and partition-description clauses were specified in a CREATE
TABLE|INDEX command
Action: Remove one of offending clauses
ORA-14154: only one of STORE IN or subpartition-description clause may be
specified
Cause: both 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 Composite Range partitioned object
Action: Remove one of offending clauses
ORA-14155: missing PARTITION, PARTITIONS, SUBPARTITION, or
SUBPARTITIONS keyword
Cause: The keyword PARTITION,PARTITIONS, SUBPARTITION, or
SUBPARTITIONS was expected but none were supplied.
Action: Supply the missing keyword.
ORA-14156: invalid number of subpartitions specified in [SUBPARTITIONS |

SUBPARTITION TEMPLATE] clause
Cause: number-of-subpartitions clause contained in CREATE TABLE or CREATE
INDEX statement specified a number of subpartitions outside of legal range
(1-1048575)
Action: Specify a number between 1 and 1024K-1 in the number-of-subpartitions
clause
ORA-14157: invalid subpartition name
Cause: a subpartition name of the form identifier is expected but 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; maximum number of subpartitions is 1048575.
Action: Reduce number of subpartitions to not exceed 1024K-1.
ORA-14159: duplicate subpartition name
Cause: Name of a subpartition of a table or index being created is not unique
Action: rename subpartition(s) to ensure that their names are unique among
subpartitions of the table or index being created
ORA-14160: this physical attribute may not be specified for a table subpartition
table subpartition; TABLESPACE is the only valid option
Action: remove invalid option(s)
ORA-14161: subpartition number string: sum of PCTUSED and PCTFREE may not
exceed 100
Cause: the sum of PCTUSED and PCTFREE for a subpartition whose number
(subpartitions are numbered starting with 1) is displayed in this message exceeds 100.
Note that if PCTUSED and/or PCTFREE values for this subpartition were not
specified explicitly, default values at partition-level would be used. If, in turn, default
PCTUSED and/or PCTFREE values at partition-level were not specified, default
values for the partitioned table or index would be used. If those values were also not
specified explicitly, system defaults would be used.
Action: ensure that a sum of PCTUSED and PCTFREE for the subpartition does not
exceed 100
ORA-14162: subpartition "string": sum of PCTUSED and PCTFREE may not exceed
100
Cause: the sum of PCTUSED and PCTFREE for a subpartition whose name (explicitly
specified by the user) is displayed in this message exceeds 100. Note that if PCTUSED
and/or PCTFREE values for this subpartition were not specified explicitly, default
values at partition-level would be used. If, in turn, default PCTUSED and/or
PCTFREE values at partition-level were not specified, default values for the
partitioned table or index would be used. If those values were also not specified
explicitly, system defaults would be used.
Action: ensure that a sum of PCTUSED and PCTFREE for the subpartition does not
exceed 100
ORA-12700 to ORA-19400 69-101
ORA-14163: subpartition number string: INITRANS value must be less than

MAXTRANS value
subpartition whose number (subpartitions are numbered starting with 1) is displayed
in this message. Note that if INITRANS and/or MAXTRANS values for this
subpartition were not specified explicitly, default values at partition-level would be
used. If, in turn, default INITRANS and/or MAXTRANS values at partition-level
were not specified, default values for the partitioned table or index would be used. If
those values were also not specified explicitly, system defaults would be used.
Action: ensure that value of INITRANS (whether specified explicitly or derived from
the default value at partition-level, table-level or index-level) is no greater than that of
MAXTRANS
ORA-14164: subpartition "string": INITRANS value must be less than MAXTRANS
value
subpartition whose name (explicitly specified by the user) is displayed in this
message. Note that if INITRANS and/or MAXTRANS values for this subpartition
were not specified explicitly, default values at partition-level would be used. If, in
turn, default INITRANS and/or MAXTRANS values at partition-level were not
specified, default values for the partitioned table or index would be used. If those
values were also not specified explicitly, system defaults would be used.
Action: ensure that value of INITRANS (whether specified explicitly or derived from
the default value at partition-level, table-level or index-level) is no greater than that of
MAXTRANS
ORA-14165: MODIFY DEFAULT ATTRIBUTES FOR PARTITION may not be
combined with other operations
Cause: ALTER TABLE or ALTER INDEX statement attempted to combine MODIFY
DEFAULT ATTRIBUTES OF PARTITION with some other operation (e.g. ADD
PARTITION or PCTFREE) which is illegal
Action: Ensure that MODIFY DEFAULT ATTRIBUTES is the sole operation specified
ORA-14166: missing INTO keyword
Cause: keyword INTO missing
ORA-14167: only one subpartition may be moved
Cause: ALTER TABLE MOVE SUBPARTITION contained descriptions of more than
one subpartition to be moved
Action: Ensure that the statement describes exactly one subpartition to be moved and
ORA-14168: only one subpartition may be modified
Cause: ALTER TABLE|INDEX MODIFY SUBPARTITION contained descriptions of
more than one subpartition to be modified
Action: Ensure that the statement describes exactly one subpartition to be modified
and that it does not contain any commas
ORA-14169: invalid ALTER TABLE MODIFY SUBPARTITION option

STORAGE, was specified in an ALTER TABLE MODIFY SUBPARTITION statement.
ORA-14170: cannot specify <(sub)partition-description> clause in CREATE TABLE
or CREATE INDEX
Cause: A request was made to generate default partition description(s) (possibly via
PARTITIONS number-of-partitions) while at the same time specified <(sub)partitiondescription> clause which is illegal.
Action: Remove one of offending clauses.
ORA-14171: cannot specify subpartition-description clause in CREATE|ALTER
TABLE
Cause: User requested to generate default subpartition description(s) (possibly via
SUBPARTITIONS) while at the same time specified subpartition-description clause
which is illegal
Action: Remove one of offending clauses.
ORA-14172: invalid ALTER TABLE EXCHANGE SUBPARTITION option
Cause: Name of the table to be EXCHANGED has to be followed by [{INCLUDING|
EXCLUDING} INDEX][{WITH|WITHOUT} VALIDATION]
Action: Ensure that no options besides INCLDING INDEX or EXCLUDING INDEX
are specified with ALTER TABLE EXCHANGE SUBPARTITION
ORA-14173: illegal subpartition-extended table name syntax
Cause: Subpartition to be accessed may only be specified using its name. User
attempted to use a subpartition number or a bind variable.
Action: Modify statement to refer to a subpartition using its name
ORA-14174: only a parallel clause may follow COALESCE PARTITION|
SUBPARTITION
Cause: ALTER TABLE COALESCE PARTITION|SUBPARTITION may be followed
by an optional parallel clause. No partition/subpartition attributes may be specified
Action: Ensure that no partition/subpartition attribute was specified.
ORA-14175: a subpartition maintenance operation may not be combined with other
operations
Cause: ALTER TABLE or ALTER INDEX statement attempted to combine a
subpartition maintenance operation (e.g. MOVE SUBPARTITION) with some other
operation (e.g. MODIFY PARTITION ADD SUBPARTITION or PCTFREE) which is
illegal
Action: Ensure that a subpartition maintenance operation is the sole operation
specified in ALTER TABLE or ALTER INDEX statement; operations other than those
dealing with subpartitions, default attributes of partitioned tables/indices or
specifying that a table be renamed (ALTER TABLE RENAME) may be combined at
will
ORA-14176: this attribute may not be specified for a hash partition
Cause: An invalid option was encountered while parsing physical attributes of a
partition of an object partitioned using the HASH method. The TABLESPACE option
is the only valid option for such partitions.
ORA-12700 to ORA-19400 69-103
Action: Remove the invalid option(s).

ORA-14177: STORE-IN (Tablespace list) can only be specified for a LOCAL index
on a Hash or Composite Range Hash table
Cause: STORE-IN (Tablespace list) clause was used while creating a local index on a
range/list/composite range list partitioned table
Action: Do not use the STORE_IN (Tablespace list) clause while creating a local index
on range/list/composite range list partitioned table
ORA-14178: STORE IN (DEFAULT) clause is not supported for hash partitioned
global indexes
Cause: STORE IN (DEFAULT) is valid only for local indexes.
Action: a) Specify a tablespace list in place of DEFAULT, or b) Remove STORE IN
clause and specify tablespaces individually for each index partition.
ORA-14179: An unsupported partitioning method was specified in this context.
Cause: An attempt was made to specify an unsupported partitioning method in this
context.
Action: Remove the invalid option.
ORA-14183: TABLESPACE DEFAULT can be specified only for Composite LOCAL
index
Cause: User attempted 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
local index partition; valid options for Range or Composite Range partitions are
INITRANS, MAXTRANS, TABLESPACE, STORAGE, PCTFREE, PCTUSED,
LOGGING and TABLESPACE; but only TABLESPACE may be specified for Hash
partitions STORE IN () is also disallowed for all but Composite Range partitions
Action: remove invalid option(s) from the list of physical attributes of an index
partition
ORA-14186: number of sub-partitions of LOCAL index must equal that of the
underlying table
Cause: User attempted to create a LOCAL partitioned index with a number of subpartitions which is different from that of the underlying table.
Action: Correct the CREATE INDEX statement to specify a correct number of subpartitions
ORA-14187: partitioning method for LOCAL index is inconsistent with that of the
underlying table
Cause: User attempted to create a LOCAL partitioned index that is not equipartitioned with the underlying table. The partitioning types are mismatched.
Action: Correct the CREATE INDEX statement to ensure that the index partitionining
method is consistent with that of the base table
ORA-14188: sub-partitioning columns must form a subset of key columns of a

UNIQUE index
Cause: User attempted to create a UNIQUE partitioned index whose sub-partitioning
columns do not form a subset of its key columns which is illegal
Action: If the user, indeed, desired to create an index whose subpartitioning 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 subpartitioning columns to ensure that the
index' subpartitioning columns form a subset of its key columns
ORA-14189: this physical attribute may not be specified for an index subpartition
Cause: unexpected option was encountered while parsing physical attributes of an
index subpartition; TABLESPACE is the only valid option
Action: remove invalid option(s)
ORA-14190: only one ENABLE/DISABLE ROW MOVEMENT clause can be
specified
Cause: One of three possible actions caused the error: 1) ENABLE ROW MOVEMENT
was specified more than once. 2) DISABLE ROW MOVEMENT was specified more
than once. 3) Both ENABLE ROW MOVEMENT and DISABLE ROW MOVEMENT
were specified.
Action: Remove all but one of the ENABLE ROW MOVEMENT or DISABLE ROW
MOVEMENT clauses; then, reissue the command.
ORA-14191: ALLOCATE EXTENT may not be specified for composite partitioned
object
Cause: User specified ALLOCATE STORAGE clause in ALTER TABLE/ALTER
INDEX statement issued against a composite partitioned index which is illegal.
Action: Remove the illegal option. If you want to add storage to individual
[sub]partitions,the ALLOCATE EXTENT clause may be specified with ALTER TABLE
OR INDEX MODIFY [SUB]PARTITION statement.
ORA-14192: cannot modify physical index attributes of a Hash index partition
Cause: User attempted to modify one of INITRANS/MAXTRANS/LOGGING/
STORAGE clause for an index partition of a Hash partitioned index
Action: Remove the physical attributes one is 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.
ORA-14194: only one subpartition may be rebuilt
Cause: ALTER INDEX REBUILD SUBPARTITION contained descriptions of more
than one subpartition to be rebuilt
Action: Ensure that the statement describes exactly one subpartition to be rebuilt and
ORA-14195: ALLOCATE STORAGE may not be specified for RANGE or LIST
partitioned object
Cause: User specified ALLOCATE STORAGE clause in ALTER TABLE/ALTER
INDEX statement issued against a range-partitioned index which is illegal.
ORA-12700 to ORA-19400 69-105

partitions, ALLOCATE STORAGE clause may be specified with ALTER TABLE/
INDEX MODIFY PARTITION statement.
ORA-14196: Specified index cannot be used to enforce the constraint.
Cause: The index specified to enforce the constraint is unsuitable for the purpose.
Action: Specify a suitable index or allow one to be built automatically.
ORA-14201: specified subpartition bound is too long
Cause: Length of a linear key representation of a high bound of a table subpartition
being added or along which an existing table or index subpartition is being split
exceeded the legal limit (4K).
Action: Change the representation of a subpartition high bound to bring its length
within legal limit.
ORA-14202: subpartition bound of subpartition "string" is too high
Cause: High bound of the specified subpartition displayed in this message did not
collate lower than that of the subsequent subpartition.
Action: Ensure that high bound of every subpartition (except for the last one) collates
lower than that of a subsequent subpartition.
ORA-14203: subpartition bound of subpartition "string" is too long
Cause: Length of linear key representation of a high bound of the specified
subpartition displayed in this message exceeded the legal limit (4K).
within legal limit.
ORA-14204: subpartition bound of subpartition number string is too high
Cause: High bound of the specified subpartition displayed in this message did not
collate lower than that of the subsequent subpartition.
Action: Ensure that high bound of every subpartition (except for the last one) collates
lower than that of a subsequent subpartition.
ORA-14205: subpartition bound of subpartition number string is too long
Cause: Length of linear key representation of a high bound of the specified
subpartition displayed in this message exceeded the legal limit (4K).
within legal limit.
ORA-14206: table is not subpartitioned by List or Range methods
Cause: A subpartition maintenance operation such as ALTER TABLE DROP|SPLIT|
MERGE SUBPARTITION can only be performed on List or Range subpartitioned
objects
Action: Issue the command only against a List or Range subpartitioned object.
ORA-14207: maximum number of subpartitioning columns is 16
Cause: number of columns in a subpartitioning column list exceeded the legal limit of
16
Action: modify subpartitioning column list so that it consists of at most 16 columns
ORA-14208: lower-bound subpartition must be specified first

Cause: A higher-bound subpartition was specified before the lower-bound
subpartition in ALTER TABLE MERGE SUBPARTITIONS statement.
Action: Specify lower-bound subpartition first and then higher-bound subpartition
ORA-14209: subpartitions being merged are not adjacent
Cause: Attempted to merge two subpartitions that are not adjacent to each other.
Action: Specify two subpartitions that are adjacent
ORA-14210: cannot reuse lower-bound subpartition as resulting subpartition
Cause: Attempted to reuse the lower-bound subpartition of the subpartitions being
merged.
Action: Specify new resulting subpartition name or reuse the higher-bound
subpartition only
ORA-14211: subpartition bound must collate higher than that of the last
subpartition
Cause: Subpartition bound specified in ALTER TABLE MODIFY PARTITION ADD
SUBPARTITION statement did not collate higher than that of the partition's last
subpartition.
Action: Ensure that the subpartition bound of the subpartition to be added collates
higher than that of the table partition's last subpartition.
ORA-14212: subpartition cannot be split along the specified high bound
Cause: Attempted to split a subpartition along a bound which either collates higher
than that of the subpartition to be split or lower than that of a subpartition
immediately preceding the one to be split
Action: Ensure that the bound along which a subpartition is to be split collates lower
than that of the subpartition to be split and higher than that of a subpartition
immediately preceding the one to be split
ORA-14213: VALUES LESS THAN or AT clause cannot be used for List
subpartitioned tables
Cause: VALUES LESS THAN or AT clause was used for List subpartitioned tables
Action: Use VALUES (value list) clause for List subpartitioned tables
ORA-14214: VALUES (value list) cannot be used for Range subpartitioned tables
Cause: VALUES (value list) clause was used for Range subpartitioned tables
Action: Use VALUES LESS THAN or AT clause with Range subpartitioned tables
ORA-14215: subpartition bound list contains too many elements
Cause: Subpartition bound list contained more elements than there are
subpartitioning columns
Action: Ensure that the number of elements in subpartition bound list is equal to the
number of subpartitioning columns of the table or index
ORA-14216: subpartition bound list contains too few elements
Cause: Subpartition bound list contained fewer elements than there are
ORA-12700 to ORA-19400 69-107
ORA-14217: VALUES (value list) clause expected

Cause: VALUES (value list) clause was not specified for the list subpartition being
added
Action: Specify a VALUES (value list) clause
ORA-14218: Invalid operation for object without a segment
Cause: The object (table or index or lob) did not have a segment.
Action: Create segments for the object with the ALTER TABLE ALLOCATE EXTENT
command.
ORA-14220: Invalid operation for object without a segment
Cause: Attempted to modify storage or allocate an extent for an object (table or LOB
or index) without a segment.
Action: Create segments for the object with the ALTER TABLE ALLOCATE EXTENT
command.
ORA-14221: Dictionary managed tablespace cannot be used for this operation
Cause: Attempted to create an index or add a LOB column in a dictionary managed
tablespace to a table without a segment.
Action: Specify a locally managed tablespace OR create segments for the table with
the ALTER TABLE ALLOCATE EXTENT command.
ORA-14223: Deferred segment creation is not supported for this table
Cause: The SEGMENT CREATION DEFERRED clause was specified in the CREATE
TABLE statement.
Action: Remove the SEGMENT CREATION DEFERRED clause.
ORA-14224: Deferred segment creation is not supported for this schema
Cause: The SEGMENT CREATION DEFERRED clause was specified in the CREATE
TABLE statement.
Action: Remove the SEGMENT CREATION DEFERRED clause.
ORA-14225: The INDEXING clause is not supported for this table.
Cause: The INDEXING clause was specified for an unsupported table type.
Action: Remove the INDEXING clause from the statement.
ORA-14226: unique index may not be PARTIAL
Cause: INDEXING PARTIAL was specified during creation or modification of a
unique index.
Action: Remove the INDEXING PARTIAL clause from the statement.
ORA-14227: INDEXING may be specified only when the underlying table is
partitioned
Cause: INDEXING FULL or INDEXING PARTIAL was specified during CREATE
INDEX or ALTER INDEX when the base table was not partitioned.
ORA-14228: INDEXING may not be specified for this index
Cause: INDEXING FULL or INDEXING PARTIAL was specified during CREATE
INDEX or ALTER INDEX for an unsupported index type.
ORA-14229: cannot modify the indexing attribute of a composite partition

Cause: An attempt was made to perform ALTER TABLE MODIFY PARTITION
INDEXING [ON|OFF] on a composite table partition.
Action: Run ALTER TABLE MODIFY SUBPARTITION INDEXING [ON|OFF] on
each subpartition individually.
ORA-14251: Specified subpartition does not exist
Cause: Subpartition not found for the object.
Action: Retry with correct subpartition name.
ORA-14252: invalid ALTER TABLE MODIFY PARTITION option for a Hash
partition
Cause: Only ALLOCATE EXTENT and DEALLOCATE UNUSED may be specified in
ALTER TABLE MODIFY PARTITION for a Hash partition.
ORA-14253: table is not partitioned by Composite Range method
Cause: The 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 by Composite Range method
Action: Ensure that the table is partitioned by Composite Range method
ORA-14254: cannot specify ALLOCATE STORAGE for a (Composite) Range or List
partitioned table
Cause: User specified ALLOCATE STORAGE clause in ALTER TABLE statement
issued against a Range or Composite Range partitioned table which is illegal.
partitions/subpartitions, ALLOCATE STORAGE clause may be specified with
ALTER TABLE MODIFY PARTITION/SUBPARTITION statement. If it is desired to
add storage to all subpartitions of a Composite partition, ALLOCATE STORAGE
clause may be specified with ALTER TABLE MODIFY PARTITION.
ORA-14255: table is not partitioned by Range, List, Composite Range or Composite
List method
Cause: The table was not partitioned by Range, List, Composite Range or Composite
List method.
Action: ALTER TABLE SPLIT/DROP PARTITION or ALTER TABLE MERGE
PARTITIONS command is only valid for table partitioned by Range, List, Composite
Range or Composite List methods. Ensure that the table is partitioned appropriately.
ORA-14256: invalid resulting partition description(s)
Cause: User specified STORE-IN clause, SUBPARTITIONS clause, and/or
subpartition-description clause in partition description(s) in ALTER TABLE SPLIT
PARTITION or ALTER TABLE MERGE PARTITIONS statement but the table in the
maintenance operation is not a Composite Range partitioned table which is illegal
Action: Remove invalid clause(s), or ensure that the table is partitioned by Composite
Range method
ORA-12700 to ORA-19400 69-109
ORA-14257: cannot move partition other than a Range, List, System, or Hash
partition
Cause: User attempt to move a partition that is not a Range,List,System, or Hash
partition which is illegal
Action: Specify MOVE PARTITION for a Range,List,System, or Hash partition only
ORA-14258: invalid partition description
Cause: User specified STORE-IN clause, SUBPARTITIONS clause, and/or
subpartition-description clause in ALTER TABLE ADD PARTITION statement but the
table in the maintenance operation is not a Composite Range/Hash partitioned table
which is illegal
Action: Remove invalid clause(s), or ensure that the table is partitioned by Composite
Range/Hash method
ORA-14259: table is not partitioned by Hash method
Cause: ALTER TABLE COALESCE PARTITION is only valid for table partitioned by
Hash method
Action: Specify valid ALTER TABLE option for the table, or ensure that the table is
partitioned by Hash method
ORA-14260: incorrect physical attribute specified for this partition
Cause: User specified INITRANS, MAXTRANS, STORAGE, PCTFREE, PCTUSED,
and/or [NO]LOGGING option to a Hash partition via ALTER TABLE ADD/MOVE
PARTITION command which is illegal. Only TABLESPACE may be specified.
Action: Remove invalid option(s)
ORA-14261: partition bound may not be specified when adding this Hash partition
Cause: User specified VALUES LESS THAN clause when adding a partition (via
ALTER TABLE ADD PARTITION) to a Hash partitioned table which is illegal
Action: Remove VALUES LESS THAN clause from the description of partition being
added
ORA-14262: new subpartition name must differ from the old subpartition name
Cause: User entered ALTER TABLE/INDEX RENAME SUBPARTITION specifying
new-subpartition-name which is identical to the name of the subpartition being
renamed
Action: Ensure that the new subpartition name is different from the name of any
(including the one being renamed) existing subpartition of a given table or index
ORA-14263: new subpartition name must differ from that of any other subpartition
of the object
Cause: User entered ALTER TABLE/INDEX RENAME SUBPARTITION specifying
new-subpartition-name which is identical to the name of some existing subpartition of
the object
Action: Ensure that the new subpartition name is different from the name of any
(including the one being renamed) existing subpartition of a given table or index
Cause: The table in the MODIFY DEFAULT ATTRIBUTES FOR PARTITION
operation is partitioned by method other than Composite method
Action: Ensure that the table is partitioned by Composite method
ORA-14265: data type or length of a table subpartitioning column may not be

changed
length of a column used to subpartition the table named in ALTER TABLE statement,
which is illegal
Action: Avoid modifying data type and/or length of table subpartitioning column(s)
ORA-14266: data type or length of an index subpartitioning column may not be
changed
length of a column used to subpartition some index defined on the table named in
ALTER TABLE statement, which is illegal
Action: Avoid modifying data type and/or length of index subpartitioning column(s)
ORA-14267: cannot specify PARALLEL clause when adding a (Composite) Range
partition
Cause: User issued ALTER TABLE ADD PARTITION statement with PARALLEL
clause for a Range or Composite Range partition which is illegal
Action: Remove the PARALLEL clause.
ORA-14268: subpartition 'string' of the partition resides in offlined tablespace
Cause: User attempted an operation requiring that we access data in a subpartition
which resides in a tablespace which was taken offline. Such operations include trying
to drop a tablespace of a table which has indices defined on it or is referenced by a
constraint.
ORA-14269: cannot exchange partition other than a Range,List,System, or Hash
partition
Cause: User attempt to exchange a partition with a non-partitioned table but the
specified partition is not a Range,List,System, or Hash partition which is illegal
Action: Specify EXCHANGE PARTITION for a Range,List,System, or Hash partition
only
ORA-14270: table is not partitioned by Range, System, Hash or List method
Cause: The table in ALTER TABLE MODIFY PARTITION { UNUSABLE LOCAL
INDEXES | REBUILD UNUSABLE LOCAL INDEXES } statement is not partitioned
by Range,List,System, or Hash method which is illegal.
Action: Ensure that the table is partitioned by Range,List,System, or Hash method
Cause: The table in ALTER TABLE MODIFY SUBPARTITION { UNUSABLE LOCAL
INDEXES | REBUILD UNUSABLE LOCAL INDEXES } statement is not partitioned
by Composite Range method which is illegal.
Action: Ensure that the table is partitioned by Composite Range method
ORA-14272: only a partition with higher bound can be reused
Cause: User attempt to reuse a lower-bound partition in ALTER TABLE MERGE
PARTITIONS statement as the resulting partition which is illegal.
Action: Use the higher-bound partition to be the resulting partition or specify a new
partition name
ORA-12700 to ORA-19400 69-111
ORA-14273: lower-bound partition must be specified first

Cause: User specified higher-bound partition before lower-bound partition in ALTER
TABLE MERGE PARTITIONS statement which is illegal
Action: Specify lower-bound partition then higher-bound partition
ORA-14274: partitions being merged are not adjacent
Cause: User attempt to merge two partitions that are not adjacent to each other which
is illegal
Action: Specify two partitions that are adjacent
ORA-14275: cannot reuse lower-bound partition as resulting partition
Cause: User attempt to reuse lower-bound partition of the partitions being merged
which is illegal
Action: Specify new resulting partition name or reuse the higher-bound partition only
ORA-14276: EXCHANGE SUBPARTITION requires a non-partitioned, nonclustered table
Cause: The table in the ALTER TABLE EXCHANGE SUBPARTITION operation is
either clustered or partitioned
Action: Ensure that the table with which the subpartition is being exchanged for is not
partitioned or clustered.
ORA-14277: tables in EXCHANGE SUBPARTITION must have the same number
of columns
Cause: The two tables specified in the ALTER TABLE EXCHANGE SUBPARTITION
have different number of columns
type and size.
ORA-14278: column type or size mismatch in EXCHANGE SUBPARTITION
EXCHANGE SUBPARTITION are of different type or size
type and size.
ORA-14279: index mismatch for tables in ALTER TABLE EXCHANGE
SUBPARTITION
Cause: The two tables specified in the ALTER TABLE EXCHANGE SUBPARTITION
have indexes which are not equivalent
Action: Ensure that the indexes for the two tables have indexes which follow this rule
For every non partitioned index for the non partitioned table, there has to be an
identical LOCAL index on the partitioned table and vice versa. By identical, the
column position, type and size have to be the same.
ORA-14280: all rows in table do not qualify for specified subpartition
Cause: There is at least one row in the non partitioned table which does not qualify
for the subpartition specified in the ALTER TABLE EXCHANGE SUBPARTITION
Action: Ensure that all the rows in the segment qualify for the subpartition. Perform
the alter table operation with the NO CHECKING option. Run ANALYZE table
VALIDATE on that subpartition to find out the invalid rows and delete them.
ORA-14281: CHECK constraint mismatch in ALTER TABLE EXCHANGE

SUBPARTITION
EXCHANGE SUBPARTITION statement have CHECK constraint defined on them.
Action: Ensure that the two tables do not have CHECK constraint defined on any
column
ORA-14282: FOREIGN KEY constraint mismatch in ALTER TABLE EXCHANGE
SUBPARTITION
EXCHANGE SUBPARTITION statement have different FOREIGN KEY constraints.
Action: Ensure that the two tables do not have FOREIGN KEY constraints defined on
any column or disable all FOREIGN KEY constraints on both tables. Then retry the
operation.
ORA-14283: UNIQUE constraints mismatch in ALTER TABLE EXCHANGE
SUBPARTITION
Cause: One of the tables named in the ALTER TABLE EXCHANGE SUBPARTITION
command has a UNIQUE constraint for which no matching (vis-a-vis key columns)
constraint is defined on the other table or a matching constraint is defined on the
other table, but it differs from that defined on the first table vis-a-vis being enabled
and/or validated.
Action: Ensure that for every UNIQUE constraint defined on one of the tables named
in the ALTER TABLE EXCHANGE SUBPARTITION statement there is a matching
(vis-a-vis key columns and being enabled and/or validated) UNIQUE constraint
defined on the other table. If UNIQUE constrains are enabled, UNIQUE constraints
on the partitioned table should be enforced using local indexes.
ORA-14284: one or more of table's subpartitions reside in a read-only tablespace
Cause: User issued ALTER TABLE statement attempting to modify an existing
VARCHAR2 (or VARCHAR) column to be of type CHAR (or CHARACTER), increase
length of an existing CHAR (or CHARACTER) column, or add a column with userspecified default for a table one or more subpartitions of which reside in read-only
tablespaces, which is illegal
Action: Avoid performing aformentioned operations on a partitioned table one or
more subpartitions of which reside in read-only tablespaces
ORA-14285: cannot COALESCE the only partition of this hash partitioned table or
index
Cause: A COALESCE PARTITION command was issued when there is only one
partition in the table or index, which is illegal
Action: Ensure that there is at least one partition. Drop the table or index 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 which is illegal
Action: Ensure that there is at least one subpartition. Drop partition to remove all
subpartitions.
ORA-12700 to ORA-19400 69-113
ORA-14287: cannot REBUILD a partition of a Composite Range partitioned index

Cause: User attempted to rebuild a partition of a Composite Range partitioned index
which is illegal
Action: REBUILD the index partition, a subpartition at a time
ORA-14288: index is not partitioned by Composite Range method
Cause: The index in a partition or subpartition maintenance operation (ALTER
INDEX MODIFY [SUBPARTITION|DEFAULT ATTRIBUTES FOR PARTITION] or
ALTER INDEX REBUILD SUBPARTITION command must be partitioned by
Composite Range method
Action: n/a
ORA-14289: cannot make local index partition of Composite Range partitioned
table unusable
which is illegal
Action: n/a
ORA-14290: PRIMARY KEY constraint mismatch in ALTER TABLE EXCHANGE
[SUB]PARTITION
EXCHANGE [SUB]PARTITION statement have different PRIMARY KEY constraints.
Action: Ensure that the two tables do not have PRIMARY KEY constraints defined on
any column or disable all PRIMARY KEY constraints on both tables. Then retry the
operation.
ORA-14291: cannot EXCHANGE a composite partition with a non-partitioned table
Cause: A composite partition can only be exchanged with a partitioned table.
Action: Ensure that the table being exchanged is partitioned or that that the partition
being exchanged is non-composite.
ORA-14292: Partitioning type of table must match subpartitioning type of
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 composite
partition.
Action: Ensure that the partitioning type of partitioned table is the same as the
subpartitioning type of the composite partition.
ORA-14293: Number of partitioning columns does not match number of
Cause: When exchanging a partitioned table with a composite partition the number of
partitioning columns of the table must match the number of subpartitioning columns
of the composite partition.
Action: Ensure that the number of partitioning columns in the partitioned table is the
same as the number of subpartitioning columns in the the composite partition.
ORA-14294: Number of partitions does not match number of subpartitions
Cause: When exchanging a partitioned table with a composite partition the number of
partitions of the table must match the number of subpartitions of the composite
partition.
Action: Ensure that the number of partitions in the partitioned table is the same as the
number of subpartitions in the the composite partition.
ORA-14295: column type or size mismatch between partitioning columns and
Cause: When exchanging a partitioned table with a composite partition the type and
size of the partitioning columns of the table must match the type and size of the
subpartitioning columns of the composite partition.
Action: Ensure that the type and size of the partitioning columns of the partitioned is
the same as the type and size of the subpartitioning columns of the composite
partition.
ORA-14296: Table block size mismatch in ALTER TABLE EXCHANGE
[SUB]PARTITION
Cause: The block sizes of the two tables specified in the ALTER TABLE EXCHANGE
[SUB]PARTITION statement are different. For index organized tables, either the block
sizes of the index or the overflow (or both) do not match.
Action: Ensure that the block sizes of the tables involved in the ALTER TABLE
EXCHANGE [SUB]PARTITION statement are the same. For index organized tables,
ensure that the block sizes of both the index and the overflow of the two tables match.
ORA-14297: Index block size mismatch in ALTER TABLE EXCHANGE
[SUB]PARTITION
Cause: The block sizes of a pair of indexes being exchanged in the ALTER TABLE
EXCHANGE [SUB]PARTITION statement are different.
Action: Ensure that the block sizes of the corresponding pairs of indexes that need to
be exchanged in the ALTER TABLE EXCHANGE [SUB]PARTITION statement are the
same.
ORA-14298: LOB column block size mismatch in ALTER TABLE EXCHANGE
[SUB]PARTITION
Cause: The block sizes of a pair of corresponding LOB columns of the two tables
specified in the ALTER TABLE EXCHANGE [SUB]PARTITION statement are
different.
Action: Ensure that the block sizes of corresponding pairs of LOB columns of the
tables involved in the ALTER TABLE EXCHANGE [SUB]PARTITION statement are
the same.
ORA-14299: total number of partitions/subpartitions exceeds the maximum limit
Cause: The total number of combined fragments specified in partitions /subpartitions
exceeds 1048575.
Action: Reissue the statement with fewer number of fragments
ORA-14300: partitioning key maps to a partition outside maximum permitted
number of partitions
Cause: The row inserted had a partitioning key that maps to a partition number
greater than 1048575
Action: Ensure that the partitioning key falls within 1048575 partitions or
subpartitions.
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 encountered after processing partition-level
ORA-12700 to ORA-19400 69-115
attributes of LOB columns or while processing CREATE TABLE statement, table-level

attributes of LOB columns were encountered after processing partition descriptions.
Action: Modify the SQL statement to specify table-level attributes prior to partitionlevel attributes or partition descriptions; then retry the statement.
ORA-14302: only one list of added-LOB-storage-clauses can be specified in a
statement
Cause: While parsing an ALTER TABLE ADD COLUMN statement, one list of addedLOB-storage-clauses was parsed when another list of added-LOB-storage-clauses was
encountered. There cannot be more than one list of added-LOB-storage-clauses in a
statement; all added-LOB-storage-clauses must be combined into one list.
Action: Combine all of the lists of added-LOB-storage-clauses into one list and retry
the statement.
ORA-14303: partitions or subpartitions are not in the right order
which is illegal
Action: Re-order the partitions or subpartitions in the added LOB storage clause by
partition or subpartition DDL order, and retry the statement.
ORA-14304: List partitioning method expects a single partitioning column
Cause: number of columns in a partitioning column list exceeded the legal limit of 1
for List partitioned objects
Action: modify partitioning column list so that it consists of at most 1 column
ORA-14305: List value 'string' specified twice in partition 'string'
Cause: A list value cannot be specified more that once
Action: Remove one of the specifications of the value
ORA-14306: List value 'string' specified twice in partitions 'string', 'string'
ORA-14307: partition contains too many list values
Cause: Partition list contains more than 524288 list values
Action: Reduce the number of values to not exceed 524288 values
ORA-14308: partition bound element must be one of: string, datetime or interval
literal, number, or NULL
Cause: Partition bound list contained an element of invalid type (i.e. not a number,
non-empty string, datetime or interval literal, or NULL)
Action: Ensure that all elements of partition bound list are of valid type
ORA-14309: Total count of list values exceeds maximum allowed
Cause: Partitioned object contains more than 524288 list values
Action: Reduce number of values to less than 524288.
ORA-14310: VALUES LESS THAN or AT clause cannot be used with List
partitioned tables
Cause: VALUES LESS THAN or AT clause can be used only with Range partitioned
tables
Action: Use VALUES (value list) clause with List partitioned tables
ORA-14311: Expecting VALUES LESS THAN or AT clause
Cause: VALUES (value list) clause can be used only with List partitioned tables
Action: Use VALUES LESS THAN clause with Range partitioned tables
ORA-14312: Value string already exists in partition string
Cause: One of the list values in the ADD PARTITION or ADD VALUES statement
already exists in another partition
Action: Remove the duplicate value from the statement and try again
ORA-14313: Value string does not exist in partition string
Cause: One of the list values in the SPLIT PARTITION or DROP VALUES statement
does not exist in the partition
Action: Remove the value from the statement and try again
ORA-14314: resulting List partition(s) must contain atleast 1 value
Cause: After a SPLIT/DROP VALUE of a list partition, each resulting partition(as
applicable) must contain at least 1 value
Action: Ensure that each of the resulting partitions contains atleast 1 value
ORA-14315: cannot merge a partition with itself
Cause: The same partition name was specified twice for the merge operation
Action: Re-submit operation with 2 distinct partition names
ORA-14316: table is not partitioned by List method
Cause: ALTER TABLE ADD|DROP VALUES can only be performed on List
partitioned objects
Action: Re-issue the command against a List partitioned object.
ORA-14317: cannot drop the last value of partition
Cause: ALTER TABLE DROP VALUES tried to drop the last value of the partition
Action: Cannot execute the command, unless two or more values exist for partition
ORA-14318: DEFAULT partition must be last partition specified
Cause: A partition description follows the one describing the default partition
Action: Ensure that the DEFAULT partition is the last partition description
ORA-14319: DEFAULT cannot be specified with other values
Cause: DEFAULT keyword has been specified along with other values when
specifying the values for a list partition
Action: Ensure that if DEFAULT is specified, it is the only value specified
ORA-14320: DEFAULT cannot be specified for ADD/DROP VALUES or SPLIT
Cause: DEFAULT keyword has been specified when doing a ADD VALUES or DROP
VALUES or SPLIT partition or subpartition.
Action: Ensure that DEFAULT is not specified for ADD/DROP VALUES or SPLIT
partition/subpartition operation.
ORA-14321: cannot add/drop values to DEFAULT partition
Cause: A ADD/DROP VALUES operation is being done on the default partition
ORA-12700 to ORA-19400 69-117
Action: Ensure that ADD/DROP VALUES is not done on the DEFAULT partition
ORA-14322: DEFAULT partition already exists
Cause: A partition already exists with DEFAULT value
Action: n/a
ORA-14323: cannot add partition when DEFAULT partition exists
Cause: An ADD PARTITION operation cannot be executed when a partition with
DEFAULT values exists
Action: Issue a SPLIT of the DEFAULT partition instead
ORA-14324: values being added already exist in DEFAULT partition
Cause: An ADD VALUE operation cannot be executed because the values being
added exist in the DEFAULT partition
Action: Issue a SPLIT of the DEFAULT partition and then MERGE the split partition
into the partition to which values need to be added
ORA-14325: only LOCAL indexes may be specified in this clause
Cause: A global index has been specified in the UPDATE INDEXES (..) clause
Action: Only specify local indexes when using this clause
ORA-14326: Primary index on an IOT, DOMAIN and LOB indexes may not be
specified in the UPDATE INDEXES clause
Cause: A Primary index on an IOT, DOMAIN or LOB index has been specified in the
UPDATE INDEXES (..) clause
Action: Do not specify any of these indexes when using this clause
ORA-14327: Some index [sub]partitions could not be rebuilt
Cause: The first phase (partition DDL and index [sub]partition placement) completed
successfully. During the second phase, some of the index [sub]partitions could not be
rebuilt.
Action: Search the alert log for the string DBMS_INDEX_UTL. Check the error
associated with each of the [sub]partitions that could not be rebuilt and take the
appropriate corrective action.
ORA-14329: domain index [sub]partitions cannot be renamed in this clause
Cause: The user tried to rename a domain index [sub]partition in the UPDATE
INDEXES clause of a ALTER TABLE MOVE [SUB]PARTITION operation. This is not
allowed.
Action: Leave the name blank or use the same name.
ORA-14330: Cannot drop a partition of a global hash-partitioned index
Cause: An attempt was made to drop a partition of a hash-partitioned global index.
Action: Try COALESCE PARTITION instead.
ORA-14331: cannot drop all [sub]partitions of a partitioned table
Cause: An attempt was made to drop all partitions of a partitioned table.
Action: Try DROP TABLE instead.
ORA-14332: duplicate partition or subpartition names specified
Cause: The list of partitions contained duplicate partition or subpartition names.
Action: Ensure that list of partition or subpartition names are distinct.
ORA-14333: subpartition names specified are across multiple partitions

Cause: The specified subpartitions did not belong to the same partition.
Action: Ensure that all subpartitions specified belong to the same partition.
ORA-14334: guard column expected
Cause: There was no guard column or the NOT NULL constraint was not specified
for this column.
Action: Add a guard column or NOT NULL constraint for column.
ORA-14335: number of new fragments for adding partitions exceeds the maximum
limit
Cause: The total number of new fragments for adding partitions exceeded 125000.
Action: Reissue the statement with a fewer number of new fragments.
ORA-14400: inserted partition key does not map to any partition
Cause: An attempt was made to insert a record into, a Range or Composite Range
object, with a concatenated partition key that is beyond the concatenated partition
bound list of the last partition -OR- An attempt was made to insert a record into a List
object with a partition key that did not match the literal values specified for any of the
partitions.
Action: Do not insert the key. Or, add a partition capable of accepting the key, Or add
values matching the key to a partition specification
ORA-14401: inserted partition key is outside specified partition
Cause: the concatenated partition key of an inserted record is outside the ranges of
the two concatenated partition bound lists that delimit the partition named in the
INSERT statement
Action: do not insert the key or insert it in another partition
ORA-14402: updating partition key column would cause a partition change
Cause: An UPDATE statement attempted to change the value of a partition key
column causing migration of the row to another partition
Action: Do not attempt to update a partition key column or make sure that the new
partition key is within the range containing the old partition key.
ORA-14403: cursor invalidation detected after getting DML partition lock
Cause: cursor invalidation was detected after acquiring a partition lock during an
INSERT, UPDATE, DELETE statement. This error is never returned to user, because is
caught in opiexe() and the DML statement is retried.
Action: nothing to be done, error should never be returned to user
ORA-14404: partitioned table contains partitions in a different tablespace
Cause: An attempt was made to drop a tablespace which contains tables whose
partitions are not completely contained in this tablespace
Action: find tables with partitions which span the tablespace being dropped and some
other tablespace(s). Drop these tables or move partitions to a different tablespace
ORA-14405: partitioned index contains partitions in a different tablespace
Cause: An attempt was made to drop a tablespace which contains indexes whose
partitions are not completely contained in this tablespace, and which are defined on
the tables which are completely contained in this tablespace.
ORA-12700 to ORA-19400 69-119
Action: find indexes with partitions which span the tablespace being dropped and
some other tablespace(s). 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-14406: updated partition key is beyond highest legal partition key
Cause: At attempt was made to update a record with a concatenated partition key
that is beyond the concatenated partition bound list of the last 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 tablespace
Cause: An attempt was made to drop a tablespace which contains tables whose
subpartitions are not completely contained in this tablespace
Action: find tables with subpartitions which span the tablespace being dropped and
some other tablespace(s). Drop these tables or move subpartitions to a different
tablespace
ORA-14408: partitioned index contains subpartitions in a different tablespace
Cause: An attempt was made to drop a tablespace which contains indexes whose
subpartitions are not completely contained in this tablespace, and which are defined
on the tables which are completely contained in this tablespace.
Action: find indexes with subpartitions which span the tablespace being dropped and
some other tablespace(s). 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 concatenated subpartition bound lists that delimit the subpartition named in
the INSERT statement
Action: do not insert the key or insert it in another subpartition
ORA-14411: The DDL cannot be run concurrently with other DDLs
Cause: Another conflicting DDL was already running.
Action: Retry after the conflicting DDL has finished.
ORA-14413: ALTER INDEX UNUSABLE ONLINE cannot be used with certain
types of indexes.
Cause: An attempt was made to use the ALTER INDEX UNUSABLE ONLINE
statement on an index type (for example, indexed-organized table (IOT), cluster, LOB,
domain indexes) that was not allowed.
Action: Using the ALTER INDEX UNUSABLE ONLINE statement on certain types of
indexes (for example, indexed-organized table (IOT), cluster, LOB, domain indexes) is
illegal. Remove the ONLINE keyword from the statement.
ORA-14414: DROP INDEX ONLINE cannot be used with certain types of indexes.
Cause: An attempt was made to use the DROP INDEX ONLINE statement on an
index type (for example, indexed-organized table (IOT), cluster, LOB, domain
indexes) that was not allowed.
Action: Using the DROP INDEX ONLINE statement on certain types of indexes (for
example, indexed-organized table (IOT), cluster, LOB, domain indexes) is illegal.
Remove the ONLINE keyword from the statement.
ORA-14415: index in partially dropped state, submit DROP INDEX

Cause: An attempt was made to access an index in a partially dropped state.
Action: Submit the DROP INDEX index statement to drop the index.
ORA-14416: Online DDL's cannot be used with certain types of tables.
Cause: An attempt was made to use the DROP INDEX ONLINE, ALTER TABLE
DROP CONSTRAINT ONLINE, or ALTER TABLE SET UNUSED COLUMN
ONLINE statement on an table type (for example, cluster, temporary, indexorganized table (IOT), external tables) that was not allowed.
Action: Using online DDL's like DROP INDEX ONLINE, ALTER TABLE DROP
CONSTRAINT ONLINE, or ALTER TABLE SET UNUSED COLUMN ONLINE
statement on certain types of tables (for example, cluster, temporary, indexedorganized table (IOT), external tables) is illegal. Remove the ONLINE keyword from
the statement.
ORA-14417: Online DDL's cannot be used with deferrable constraints.
Cause: An attempt was made to use the DROP CONSTRAINT ONLINE or SET
UNUSED COLUMN ONLINE statement on constraint states (for example, deferrable,
deferred) that was not allowed.
Action: Using DROP CONSTRAINT ONLINE or SET UNUSED COLUMN ONLINE
statement on constraints that are deferrable or deferred is illegal. Remove the
ONLINE keyword from the statement.
ORA-14418: Online DDL's cannot be used with this constraint type.
Cause: An attempt was made to use the DROP CONSTRAINT ONLINE or SET
UNUSED COLUMN ONLINE statement on a constraint type other than check,
primary key, unique, referential, or not null constraint.
Action: Using DROP CONSTRAINT ONLINE or SET UNUSED COLUMN ONLINE
statement on any other constraint types excluding check, primary key, unique,
referential, or not null constraints is illegal. Remove the ONLINE keyword from the
DDL.
ORA-14419: DROP CONSTRAINT ONLINE does not support the CASCADE
option.
Cause: An attempt was made to use the CASCADE option with DROP CONSTRAINT
ONLINE statement.
Action: Using the CASCADE option with the DROP CONSTRAINT ONLINE
statement is illegal. Remove the CASCADE keyword from the statement. Drop the
child key constraint in a separate DROP CONSTRAINT ONLINE statement on the
child table.
ORA-14450: attempt to access a transactional temp table already in use
Cause: An attempt was made to access a transactional temporary table that has been
already populated by a concurrent transaction of the same session.
Action: do not attempt to access the temporary table until the concurrent transaction
has committed or aborted.
ORA-14451: unsupported feature with temporary table
Cause: An attempt was made to create an IOT, specify physical attributes, specify
partition or parallel clause.
Action: do not do that.
ORA-12700 to ORA-19400 69-121
ORA-14452: attempt to create, alter or drop an index on temporary table already in

use
Cause: An attempt was made to create, alter or drop an index on temporary table
which is already in use.
Action: All the sessions using the session-specific temporary table have to truncate
table and all the transactions using transaction specific temporary table have to end
their transactions.
ORA-14453: attempt to use a LOB of a temporary table, whose data has alreadybeen
purged
Cause: An attempt was made to use LOB from a temporary table whose data has been
dropped either because table was transaction-specific and transaction has commited
or aborted, table was truncated or session which created this LOB has 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 temporary table in a referencial integrity
constraint. This is not supported.
Action: Use triggers.
ORA-14455: attempt to create referential integrity constraint on 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: cannot rebuild index on a temporary table
Cause: An attempt was made to rebuild an index on a temp table.
Action: The index data is anyway lost at end of session/transaction.
ORA-14457: disallowed Nested Table column in a Temporary table
Cause: An attempt made to create a Nested Table column in a temporary table. This is
not supported.
Action: Do not specify these datatypes for temporary tables.
ORA-14458: attempt was made to create a temporary table with INDEX
organization
Cause: An attempt was made to create an Index Organized Temporary table. This is
not supported.
Action: Create the table with HEAP organization and the primary key.
ORA-14459: missing GLOBAL keyword
Cause: keyword GLOBAL is missing while creating temporary table.
Action: supply keyword.
ORA-14460: only one COMPRESS or NOCOMPRESS clause may be specified
Cause: COMPRESS was specified more than once, NOCOMPRESS was specified
more than once, or both COMPRESS and NOCOMPRESS were specified.
Action: specify each desired COMPRESS or NOCOMPRESS clause option only once.
ORA-14461: cannot REUSE STORAGE on a temporary table TRUNCATE

Cause: REUSE STORAGE was specified with TRUNCATE on a temporary table. This
is unsupported as it is meaningless.
Action: Specify DROP STORAGE instead (which is the default).
ORA-14462: cannot TRUNCATE temporary table in an autonomous transaction
which is already in use by the parent transaction
Cause: An attempt was made to TRUNCATE a temporary table in an autonomous
transaction which is already in use by the parent transaction.
Action: Make sure the temporary table is not being used by the parent transaction
before trying to TRUNCATE in an autonomous transaction.
ORA-14463: OPERATIONS keyword not specified
Cause: OPERATIONS keyword was not specified in the Compression Clause.
Action: specify OPERATIONS in the Compression Clause.
ORA-14464: Compression Type not specified
Cause: Compression Type was not specified in the Compression Clause.
Action: specify Compression Type in the Compression Clause.
ORA-14465: Fast-Split is not possible on these partitions
Cause: The Fast-Split event was forced in this session.
Action: Disable the event that forces Fast-Split.
ORA-14500: LOCAL option not valid without partition name
ORA-14501: object is not partitioned
Cause: Table or index is not partitioned. Invalid syntax.
Action: Retry the command with correct syntax.
ORA-14503: only one partition name can be specified
Cause: More than one partition name has been specified for analyze
Action: Specify one partition name.
ORA-14504: syntax not supported for analyze
Cause: A partition/subpartition number or bind variable has been used
Action: Specify a valid partition/subpartition name.
ORA-14505: LOCAL option valid only for partitioned indexes
ORA-14506: LOCAL option required for partitioned indexes
ORA-14507: partition corrupt. all rows do not fall within partition bounds
Cause: The partition contains rows which should really be in some other partition.
Possibly due to an exchange partition without validation
ORA-12700 to ORA-19400 69-123
Action: Delete rows in partition which do not qualify

ORA-14508: specified VALIDATE INTO table not found
Cause: The specified table either does not exist or user does not have the proper
privleges.
ORA-14509: specified VALIDATE INTO table form incorrect
Action: Specify the correct table to use. See utlvalid.sql for more information.
ORA-14510: can specify VALIDATE INTO clause only for partitioned tables
Cause: The VALIDATE INTO has been specified for a non partitioned table or cluster
or index.
Action: Use syntax correctly
ORA-14511: cannot perform operation on a partitioned object
Cause: An attempt was made to perform an operation that is not allowed on
partitioned tables or indexes.
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.
ORA-14513: partitioning column may not be of object datatype
Cause: Partitioning column specified by the user was an object datatype (object, REF,
nested table, array) which is illegal.
Action: Ensure that no partitioning column is an object datatype.
ORA-14514: LOCAL option not valid without subpartition name
ORA-14515: only one aubpartition name can be specified
Cause: More than one subpartition name has been specified for analyze
Action: Specify one subpartition name.
ORA-14516: subpartition corrupt. all rows do not fall within subpartition bounds
Cause: The subpartition contains rows which should really be in some other
subpartition. Possibly due to an exchange subpartition without validation
Action: Delete rows in subpartition which do not qualify
ORA-14517: subpartition of index 'string.string' is in unusable state
Cause: An attempt has been made to access an index subpartition that has been
marked unusable by a direct load or by a DDL operation
Action: REBUILD the unusable index subpartition
ORA-14518: partition contains rows corresponding to values being dropped
Cause: table partition contains rows for the values being dropped.
Action: DELETE all rows for the values being dropped and reissue statement
ORA-14519: Conflicting tablespace blocksizes for string string: Tablespace string
block size string [string] conflicts with previously specified/implied tablespace
string block size string [string]
Cause: An attempt has been made to create a partitioned object in a manner that
would require the partitioned object to span tablespaces of more than one block size.
Action: Ensure that all tablespaces specified in the DDL command for the given object
as well as any tablespaces implicitly assigned to partitions or subpartitions of the
object being created are all of the same block size.
ORA-14520: Tablespace string block size [string] does not match existing object
block size [string]
Cause: A DDL statement was issued that would require a tablespace of a block size
different from the block size of the specified partitioned object to be assigned either:
(1) As the object's default tablespace (or one of the object's partition-level default
tablespaces, if composite partitioning is being used) OR (2) To one of the object's
partitions/subpartitions.
Action: Specify a tablespace of the same block size as the partitioned object.
ORA-14521: Default tablespace string block size [string] for string string does not
match existing string block size [string]
Cause: A DDL statement was issued that would require creation of a new partition/
subpartition in the object-level default tablespace of an existing partitioned object.
However, the object-level default tablespace block size does not match the block size
of the partitioned object.
Action: Either (1) Modify the default tablespace of the partitioned object to a
tablespace of the same block size as the object and then retry the DDL command, OR
(2) Ensure that tablespaces of the correct block size are specified for all new
partitions/subpartitions being created.
ORA-14522: Partition-level default tablespace string block size [string] for string
string does not match existing string block size [string]
Cause: A DDL statement was issued that would require creation of a new
subpartition in one of the partition-level default tablespaces of an existing composite
partitioned object. However, the partition-level default tablespace block size does not
match the block size of the partitioned object.
Action: Either (1) Modify the partition-level default tablespace of the appropriate
partition of the partitioned object to a tablespace of the same block size as the object
and then retry the DDL command, OR (2) Ensure that tablespaces of the correct block
size are specified for all new subpartitions being created.
ORA-14523: Cannot co-locate [sub]partition of string string with table
[sub]partition because string block size [string] does not match table block size
[string]
Cause: A DDL statement was issued that would require a partition/subpartition of a
local index/LOB column to be co-located with the corresponding partition/
subpartition of the base table. However, this is not possible because the block sizes of
the table and the LOB column/local index are different.
Action: Either (1) Specify an object-level default tablespace (or partition-level default
tablespace for the appropriate partition, if composite partitioning is used) for the
partitioned local index/LOB column and then retry the DDL command, OR (2)
Ensure that tablespaces of the correct block size are specified for all new partitions/
ORA-12700 to ORA-19400 69-125
subpartitions being created. Also ensure that neither of TABLESPACE DEFAULT and
STORE IN (DEFAULT) is specified for a local index whose block size does not match
that of the base table.
ORA-14530: row mismatches found in table string.string and index string.string
Cause: rows in table and index inconsistent
Action: run complete analyze to determine corrupt rows
ORA-14551: cannot perform a DML operation inside a query
Cause: DML operation like insert, update, delete or select-for-update cannot be
performed inside a query or under a PDML slave.
Action: Ensure that the offending DML operation is not performed or use an
autonomous transaction to perform the DML operation within the query or PDML
slave.
ORA-14552: cannot perform a DDL, commit or rollback inside a query or DML
Cause: DDL operations like creation tables, views etc. and transaction control
statements such as commit/rollback cannot be performed inside a query or a DML
statement.
Action: Ensure that the offending operation is not performed or use autonomous
transactions to perform the operation within the query/DML operation.
ORA-14553: cannot perform a lob write operation inside a query
Cause: A lob write operation cannot be performed inside a query or a PDML slave.
Action: Ensure that the offending lob write operation is not performed or use an
autonomous transaction to perform the operation within the query or PDML slave.
ORA-14554: cannot perform requested operation during database startup
Cause: Requested operation requires the Cost Based Optimizer(CBO) which is not
available during database startup. Features like partitioning, IOTs, grouping sets, and
flashback cursor require the CBO.
Action: Retry the query after the database is open.
ORA-14601: Illegal to specify SUBPARTITIONS or STORE-IN while specifying a
subpartition template
Cause: Cannot specify these clauses while specifying a template
Action: Correct the subpartition template clause.
ORA-14602: SUBPARTITION TEMPLATE is legal only for a composite partitioned
table
Cause: SUBPARTITION TEMPLATE can be specified only for composite partitioned
tables
Action: Do not use SUBPARTITION TEMPLATE on non-partitioned or noncomposite partitioned tables.
ORA-14603: [SUBPARTITIONS | SUBPARTITION TEMPLATE]
subpartition_count syntax is valid only for range-hash tables
Cause: This syntax is valid only if subpartitioning dimension is hash
Action: n/a
ORA-14604: During CREATE TABLE time it is illegal to specify SUBPARTITIONS

or STORE IN once a SUBPARTITION TEMPLATE has been specified
Cause: Once a subpartition template has been specified during a CREATE TABLE it is
illegal to specify SUBPARTITIONS or STORE IN anywhere else
Action: Remove either the SUBPARTITIONS | STORE IN or remove the
SUBPARTITION TEMPLATE clause
ORA-14605: Name missing for subpartition / lob segment in template
Cause: A subpartition / lob segment was not specified a name in the template
descriptions
Action: All subpartitions / lob segments must have names specified in the template
ORA-14607: Tablespace was not specified for previous subpartitions in template
but is specified for string
Cause: Tablespaces may either be specified for all subpartitions or must not be
specified for any subpartitions
Action: Either specify tablespaces for all or for none of the subpartitions
ORA-14610: Lob attributes not specified for lob column string for subpartition
string
Cause: Lob attributes of a column must be specified for all subpartitions or must not
be specified at all
Action: Ensure lob attributes of a column are specified for all subpartitions or not
specified at all
ORA-14611: Duplicate subpartition name string in template
Cause: A subpartition name cannot be duplicated within the template
Action: Rename one of the subpartitions.
ORA-14612: Duplicate lob segment name string for lob column string in template
Cause: Two lob segments of the same column were given the same name in the
template
Action: Rename one of the lob segments
ORA-14613: Attempt to generate name from parent name string and template name
string failed as the combine named would have been longer than allowed
Cause: Any name generated from a partition name and template name must be less
than the maximum permissible name for an identifier
Action: Shorten either partition or template name.
ORA-14614: List value 'string' specified twice in subpartition 'string'
ORA-14615: List value 'string' specified twice in subpartitions 'string', 'string'
ORA-12700 to ORA-19400 69-127
ORA-14616: table is not subpartitioned by List method

Cause: A subpartition maintenance operation, such as ALTER TABLE MODIFY
SUBPARTITION ADD|DROP VALUES, was performed on a non-List subpartitioned
object.
Action: Reissue the command against a List subpartitioned object.
ORA-14617: cannot add/drop values to DEFAULT subpartition
Cause: A ADD/DROP VALUES operation is being done on the default subpartition
Action: Ensure that ADD/DROP VALUES is not done on the DEFAULT subpartition
ORA-14618: cannot drop the last value of subpartition
Cause: ALTER TABLE DROP VALUES tried to drop the last value of the subpartition
Action: Cannot execute the command, unless two or more values exist for
subpartition
ORA-14619: resulting List subpartition(s) must contain at least 1 value
Cause: After a SPLIT/DROP VALUE of a list subpartition, each resulting
subpartition(as applicable) must contain at least 1 value
Action: Ensure that each of the resulting subpartitions contains atleast 1 value
ORA-14620: DEFAULT subpartition already exists
Cause: A subpartition already exists with DEFAULT value
Action: Remove the DEFAULT value from the list specified
ORA-14621: cannot add subpartition when DEFAULT subpartition exists
Cause: An ADD SUBPARTITION operation cannot be executed when a subpartition
with DEFAULT values exists
Action: Issue a SPLIT of the DEFAULT subpartition instead
ORA-14622: Value string already exists in subpartition string
Cause: One of the list values in the ADD SUBPARTITION or ADD VALUES
statement already exists in another subpartition
Action: Remove the duplicate value from the statement and try again
ORA-14623: Value string does not exist in subpartition string
Cause: One of the list values in the SPLIT PARTITION or DROP VALUES statement
does not exist in the subpartition
Action: Remove the value from the statement and try again
ORA-14624: DEFAULT subpartition must be last subpartition specified
Cause: A subpartition description follows the one describing the default subpartition
Action: Ensure that the DEFAULT subpartition is the last subpartition description
ORA-14625: subpartition contains rows corresponding to values being dropped
Cause: table subpartition contains rows for the values being dropped.
Action: DELETE all rows for the values being dropped and reissue statement
ORA-14626: values being added already exist in DEFAULT subpartition
Cause: An ADD VALUE operation cannot be executed because the values being
added exist in the DEFAULT subpartition
Action: Issue a SPLIT of the DEFAULT subpartition and then MERGE the split
subpartition into the subpartition to which values need to be added
ORA-14627: Invalid operation was specified on a GLOBAL partitioned index
Cause: An invalid operation such as ALTER INDEX DROP|SPLIT SUBPARTITION
was specified on the global index
Action: Ensure that subpartition level operations are not specified on a GLOBAL
index, since these are only RANGE partitioned
ORA-14628: specification of bounds is inconsistent with LIST method
Cause: An operation such as ALTER TABLE SPLIT|ADD SUBPARTITION specified
bounds that were inconsistent with List subpartitioning method
Action: Specify VALUES/subpartition descriptions correctly for SPLIT/ADD of List
subpartitions
ORA-14629: cannot drop the only subpartition of a partition
Cause: A drop subpartition command is being executed when there is only one
subpartition in the partition
Action: n/a
ORA-14630: subpartition resides in offlined tablespace
Cause: User attempted an operation requiring that we access data in a subpartition
which resides in a tablespace which was taken offline. Such operations include trying
to drop a tablespace of a table which has indices defined on it or is referenced by a
constraint.
ORA-14631: the partition bounds do not match the subpartition bounds of the
partition
Cause: When exchanging a partitioned table with a composite partition the bounds
that describe the partitions of the table must match the bounds that describe the
subpartitions of the composite partition.
Action: Ensure that the bounds describing partitions in the partitioned table is the
same as the bounds of the subpartitions in the the composite partition.
ORA-14632: cannot specify PARALLEL clause when adding a List subpartition
Cause: User issued ALTER TABLE ADD SUBPARTITION statement with PARALLEL
clause for a List subpartition of a Range/List partitioned object which is illegal
Action: Remove the PARALLEL clause.
ORA-14633: Index maintainence clause not allowed for ADD list subpartition to a
Composite partitioned table
Cause: The clause INVALIDATE or UPDATE GLOBAL INDEXES is allowed only for
ADD hash subpartition to a composite partitioned table.
Action: Remove clause and reissue operation
ORA-14634: Subpartition descriptions cannot be specified during the SPLIT/
MERGE of a partition of a Range-List partitioned table
Cause: During a split or a merge of a partition of a range list partitioned table you
cannot specify any subpartitioning information for the resulting partition (s)
Action: Remove all subpartitioning information from the DDL.
ORA-12700 to ORA-19400 69-129
ORA-14635: only one resulting subpartition can be specified for MERGE

SUBPARTITIONS
Cause: ALTER TABLE MERGE SUBPARTITIONS contained more than one resulting
subpartition for the MERGE
Action: Ensure that the statement describes exactly one subpartition as the target that
need to be MERGEd
ORA-14636: only 2 resulting subpartition can be specified for SPLIT
SUBPARTITION
Cause: ALTER TABLE SPLIT SUBPARTITION contained more than 2 resulting
subpartition for the SPLIT
Action: Ensure that the statement describes exactly 2 subpartitions as the target of the
SPLIT operation
ORA-14637: cannot merge a subpartition with itself
Cause: The same subpartition name was specified twice for the merge operation
Action: Re-submit operation with 2 distinct subpartition names within the same
composite partition
ORA-14638: cannot MERGE subpartitions in different Range Composite partitions
Cause: Attempted to MERGE subpartitions in different Range Composite partitions
Action: Reissue the command after ensuring that the 2 subpartitions being merged lie
in the same composite partition
ORA-14639: SUBPARTITIONS clause can be specfied only for Hash, Composite
Range Hash table/partition
Cause: Attempted to specify SUBPARTITIONS clause on table that is not partitioned
by the Composite Range-Hash method
Action: Reissue the command after ensuring that the SUBPARTITIONS clause is not
specified, to specify a template for a Composite Range List object use the
SUBPARTITION TEMPLATE clause
ORA-14640: add/coalesce index partition operation is valid only for hash
partitioned global indexes
Cause: User attempted to add or coalesce an index partition of a global index not
partitioned by hash method.
Action: Issue the statement on a global index partitioned by hash method. or if the
index is partitioned by range method consider using split/drop instead of add/
coalesce.
ORA-14641: STORE-IN clause can be specified only for a Hash, Composite Range
Hash table/partition
Cause: Specifying a STORE-IN clause during CREATE/ALTER of a Range,
Composite Range List partitioned table which is not allowed"
Action: Re-issue the stament after removing the STORE-IN clause
ORA-14642: Bitmap index mismatch for tables in ALTER TABLE EXCHANGE
PARTITION
Cause: The two tables in the EXCHANGE have usable bitmap indexes, and the
INCLUDING INDEXES option has been specified and the tables have different hakan
factors.
Action: Perform the exchange with the EXCLUDING INDEXES option or alter the
bitmap indexes to be unusable.
ORA-14643: Hakan factor mismatch for tables in ALTER TABLE EXCHANGE
PARTITION
Cause: Either records_per_block has been minimized for one of the tables to be
exchanged, but not the other, or the hakan factors for the tables to be exchanged are
not equal.
Action: If records_per_block has been minimized for one of the tables, but not the
other, either perform alter table with the NOMINIMIZE RECORDS_PER_BLOCK
option for both tables, or perform alter table with the MINIMIZE
RECORDS_PER_BLOCK for both tables. If the hakan factors do not match perform
alter table with the NOMINIMIZE RECORDS_PER_BLOCK option for both tables.
ORA-14644: table is not subpartitioned by Hash method
Cause: A subpartition maintenance operation such as ALTER TABLE MODIFY
PARTITION COALESCE SUBPARTITION can only be performed on Hash
subpartitioned objects
Action: Re-issue the command against a Hash subpartitioned object.
ORA-14645: STORE IN clause cannot be specified for Range List objects
Cause: A STORE IN clause was specified for Range List partitioned object
Action: Re-issue the command after removng the STORE IN clause
ORA-14646: Specified alter table operation involving compression cannot be
performed in the presence of usable bitmap indexes
Cause: The first time a table is altered to include compression, it cannot have a usable
bitmap index (partition). Subsequent alter table statements involving compression do
not have this same restriction.
Action: A) Drop any bitmap indexes defined on the table, and re-create them once the
operation is complete or, B) Mark all index fragments of all bitmap indexes defined
on the table UNUSABLE and rebuild them once the operation is complete.
ORA-14647: cannot MERGE subpartitions in different list composite partitions
Cause: An attempt was made to MERGE subpartitions in different list composite
partitions.
Action: Reissue the command after ensuring that the two subpartitions being merged
lie in the same composite partition.
ORA-14650: operation not supported for reference-partitioned tables
Cause: Attempted to perform an operation on a reference-partitioned table that was
not supported.
Action: Do not perform the unsupported operation.
ORA-14651: reference partitioning constraint is not supported
Cause: The specified partitioning constraint was not supported for referencepartitioned tables. The partitioning constraint must be enabled, validated, and not
deferrable. The partitioning constraint must not have ON DELETE SET NULL
semantics.
Action: Correct the statement to specify a supported partitioning constraint.
ORA-12700 to ORA-19400 69-131
ORA-14652: reference partitioning foreign key is not supported

Cause: The specified partitioning foreign key was not supported for referencepartitioned tables. All columns of the partitioning foreign key must be constrained
NOT NULL with enabled, validated, and not deferrable constraints. Furthermore, a
virtual column cannot be part of the partitioning foreign key.
Action: Correct the statement to specify a supported partitioning foreign key.
ORA-14653: parent table of a reference-partitioned table must be partitioned
Cause: Attempted to create a reference-partitioned table with a non-partitioned
parent table.
Action: Correct the statement and reenter.
ORA-14654: number of partitions of reference-partitioned table must equal that of
the parent table
Cause: Attempted to create a reference-partitioned table with a number of partitions
which was different from that of the parent table.
Action: Correct the CREATE TABLE statement to specify a correct number of
partitions.
ORA-14655: reference partitioning constraint not found
Cause: Partitioning constraint specified in CREATE TABLE ... PARTITION BY
REFERENCE was not one of the referential constraints on the table being created.
Action: Ensure that the specified partitioning constraint is one of the referential
constraints on the table being created.
ORA-14656: cannot drop the parent of a reference-partitioned table
Cause: Attempted to drop the parent of a reference-partitioned table.
Action: Drop all reference-partitioned child tables before dropping the parent table.
ORA-14657: cannot cascade row migration to reference-partitioned child table
Cause: Update of a parent key may require migration of rows in reference-partitioned
child tables, however this is not supported because the parent key was not suitably
indexed.
Action: Replace the existing index on the parent key with a unique index that does
not contain any columns in addition to the parent key.
ORA-14658: specified dependent table is not affected by this operation
Cause: A table has been specified in the DEPENDENT TABLES clause that is not a
reference-partitioned table affected by the operation.
ORA-14659: Partitioning method of the parent table is not supported
Cause: An attempt was made to create a reference-partitioned table with an interval
partitioned parent table.
Action: Do not create a reference-partitioned table with an interval partitioned parent
table.
ORA-14660: parent table of a reference-partitioned table cannot be index-organized
Cause: Attempted to create a reference-partitioned table with a index-organized
parent table.
ORA-14661: row movement must be enabled

Cause: Attempted to disable row movement for a reference-partitioned table,
although row movement was enabled for its parent table.
Action: Disable row movement for parent table before disabling row movement for
the reference-partitioned table.
ORA-14662: row movement cannot be enabled
Cause: Attempted to enable row movement for a partitioned table, although row
movement was disabled for a reference-partitioned child table.
Action: Enable row movement for reference-partitioned child tables before enabling
row movement for the parent table.
ORA-14663: reference partitioning parent key is not supported
Cause: Parent key of the reference-partitioned table's partitioning constraint
contained virtual columns.
Action: Correct the statement to specify a partitioning constraint with supported
parent key and reenter.
ORA-14664: Cannot use PL/SQL expressions in reference partitioning parent key
Cause: Parent key of the reference partitioned table's partitioning constraint contained
a virtual column that referenced a PL/SQL expression.
ORA-14665: Cannot use expressions involving ROWID data type in reference
partitioning parent key
a virtual column that involved the ROWID data type.
ORA-14666: Cannot use expressions involving BLOB or CLOB data types in
reference partitioning parent key
a virtual column that involved a BLOB or CLOB data type.
ORA-14667: Cannot use expressions involving object data types in reference
partitioning parent key
a virtual column that involved an object data type (object, REF, nested table, array).
ORA-14668: Cannot drop a unique or primary key referenced by the partitioning
constraint of a reference-partitioned table.
Cause: An attempt was made to drop a unique or primary key referenced by the
partitioning constraint of a reference-partitioned table.
Action: Drop all reference-partitioned child tables before dropping the unique or
primary key of the parent table.
ORA-12700 to ORA-19400 69-133
ORA-14669: interval partition of reference-partitioned table must correspond to

interval partition of the parent table
Cause: An attempt was made to create a reference-partitioned table with an interval
partiton that does not pair with an interval partition in the parent table.
Action: Correct the CREATE TABLE statement to specify a correct number of
partitions.
ORA-14670: there is no usable index on the reference partitioning parent key
Cause: An attempt was made to run an operation on a reference partitioned table that
requires a usable index on the reference partitioning parent key, but no such index
exists.
Action: Create a usable index on the reference partitioning parent key, or rebuild the
existing unusable index on the reference partitioning parent key.
ORA-14690: value too long for MIN or MAX aggregate
Cause: An attempt was made to use a MIN or MAX aggregate with a value that was
too long.
Action: Limit the size of MIN and MAX aggregate inputs to 32763 bytes.
ORA-14691: Extended character types are not allowed in this table.
Cause: An attempt was made to create VARCHAR2 or NVARCHAR2 columns larger
than 4000 bytes, or a RAW column larger than 2000 bytes, in a cluster, clustered table
or index-organized table.
ORA-14692: STORE AS clause is not allowed for extended character type column
Cause: An attempt was made to use the STORE AS clause to specify storage attributes
for an extended character type column.
ORA-14693: The MAX_STRING_SIZE parameter must be EXTENDED.
Cause: An attempt was made to set the MAX_STRING_SIZE parameter to
STANDARD in a database that has been created with, or migrated to, the EXTENDED
setting.
Action: Set MAX_STRING_SIZE to EXTENDED and retry.
ORA-14694: database must in UPGRADE mode to begin MAX_STRING_SIZE
migration
Cause: An attempt was made to update the MAX_STRING_SIZE parameter to
EXTENDED when the database was not in UPGRADE mode.
Action: Restart the database in UPGRADE mode, modify the parameter, run the
utl32k.sql script in $ORACLE_HOME/rdbms/admin, and restart the database in
normal mode.
ORA-14695: MAX_STRING_SIZE migration is incomplete
Cause: An attempt was made to open the database in normal mode before the
MAX_STRING_SIZE migration process completed.
Action: Restart the database in UPGRADE mode, run the utl32k.sql script in
$ORACLE_HOME/rdbms/admin, and restart the database in normal mode.
ORA-14696: MAX_STRING_SIZE migration is incomplete for pluggable database

string
Cause: An attempt was made to open the database in normal mode before the
MAX_STRING_SIZE migration process completed for the specified pluggable
database.
Action: Restart the database in UPGRADE mode, run the utl32k.sql script in
$ORACLE_HOME/rdbms/admin in the specified pluggable database, and restart the
database in normal mode.
ORA-14697: This connection does not support bind variables larger than 4000 bytes
for SQL statements.
Cause: An attempt was made to use a bind variable larger than 4000 bytes for a SQL
statement when the client initially connected to a container with STANDARD
MAX_STRING_SIZE, and then within the same session switched to a container with
EXTENDED MAX_STRING_SIZE.
Action: Initialize a new connection for the container with EXTENDED
MAX_STRING_SIZE and retry.
ORA-14700: Object(s) owned by SYS cannot be locked by non-SYS user
Cause: Attempt to issue a LOCK TABLE statement on SYS owned object(s) by a nonSYS user, user should minimally have DML privileges
Action: Re-issue LOCK TABLE statement for non-SYS user after granting DML
privileges on object, or non-SYS user should connect as SYS
ORA-14701: partition-extended name or bind variable must be used for DMLs on
tables partitioned by the System method
Cause: User attempted not to use partition-extended syntax for a table partitioned by
the System method
Action: Must use of partition-extended syntax in contexts mentioned above.
ORA-14702: The partition number is invalid or out-of-range
Cause: Attempted to use nonnumerical value or the number was out of range of the
partitions.
Action: Use a valid partition number.
ORA-14703: The AFTER clause can be used to ADD PARTITION only to a System
Partitioned table.
Cause: The table is not partitioned by the System method
Action: Skip the AFTER clause.
ORA-14704: Create table as select disallowed for SYSTEM patitioned tables
Cause: User attempted to create a SYSTEM partitioned table by doing a create table as
select.
Action: Do a create table followed by an insert as select into each partition.
ORA-14705: unique or primary keys referenced by enabled foreign keys in table
"string"."string"
Cause: An attempt was made to truncate a table with unique or primary keys
referenced by enabled foreign keys in another table.
Action: Before performing the TRUNCATE operation on the table, disable the foreign
key constraints in other tables. You can see what constraints exist in a table by issuing
ORA-12700 to ORA-19400 69-135
the following command: SELECT * FROM USER_CONSTRAINTS WHERE

TABLE_NAME = :1;
ORA-14706: multiple child tables reference constraint "string" in table "string"."
string"
Cause: An ALTER TABLE EXCHANGE [SUB]PARTITION CASCADE command
found that the specified parent key in the specified table was referenced by
partitioning constraints in multiple reference partitioned child tables.
Action: Perform EXCHANGE [SUB]PARTITION without the CASCADE option. The
CASCADE option is not supported if a parent key in the reference partitioned table
hierarchy is referened by multiple partitioning constraints.
ORA-14707: no match found for table "string"." string" for EXCHANGE CASCADE
Cause: There was no table matching the specified table in the ALTER TABLE
EXCHANGE [SUB]PARTITION CASCADE command.
Action: Perform EXCHANGE [SUB]PARTITION without the CASCADE option or
ensure that exactly one table matches the specified table.
ORA-14708: multiple matches found for table "string"." string" for EXCHANGE
CASCADE
Cause: There were multiple tables matching the specified table in the ALTER TABLE
EXCHANGE [SUB]PARTITION CASCADE command.
Action: Perform EXCHANGE [SUB]PARTITION without the CASCADE option or
ensure that exactly one table matches the specified table.
ORA-14709: index mismatch for table "string"."string" in ALTER TABLE
EXCHANGE [SUB]PARTITION
Cause: An ALTER TABLE EXCHANGE [SUB]PARTITION command was attempted
for the specified table, however, the exchange table did not have equivalent indexes.
Action: Ensure that the indexes for the two tables have indexes which follow this rule:
For every nonpartitioned index for the nonpartitioned table, there has to be an
identical LOCAL index on the partitioned table and vice versa. To be identical, the
column position type and size have to be the same.
ORA-14750: Range partitioned table with INTERVAL clause has more than one
column
Cause: You attempted to create an interval partitioned table with more than one
partitioning column.
Action: Use a single partitioning column.
ORA-14751: Invalid data type for partitioning column of an interval partitioned
table
Cause: You attempted to use interval partitioning on a table partitioned on a column
of data type other than number or date/time.
Action: Use only number or date/time columns as partitioning columns for interval
partitioned tables.
ORA-14752: Interval expression is not a constant of the correct type
Cause: You attempted to use either a nonconstant interval or an interval whose data
type does not correspond to the partitioning column
Action: Use only constant expressions for the interval. If the data type of partitioning
column is numeric, the interval must be a numeric constant. If the data type is of type
date/time, the interval must be a constant of interval type
ORA-14753: Interval cannot be zero

Cause: The interval mapped to zero.
Action: You must use a nonzero interval.
ORA-14754: Interval string is too long
Cause: The interval string was too long
Action: Specify interval using a shorter string
ORA-14755: Invalid partition specification for FOR VALUES clause.
Cause: The [SUB]PARTITION FOR VALUES (...) clause can only take constants. In
addition it takes as many arguments as there are partitioning columns and the values
must be coercible to the partitioning columns.
Action: Specify a valid FOR VALUES clause.
ORA-14756: Table is not partitioned by Interval method.
Cause: The table was not partitioned by Interval method.
Action: ALTER TABLE SET STORE IN is only valid for Interval partitioned tables.
Ensure that the table by Interval.
ORA-14757: Table is already a range partitioned table
Cause: SET INTERVAL () is used to convert an interval partitioned table to a range
partitioned table. It is not legal on a range partitioned table
Action: Use SET INTERVAL () only on an interval partitioned table.
ORA-14758: Last partition in the range section cannot be dropped
Cause: An attempt was made to drop the last range partition of an interval
partitioned table.
Action: Do not attempt to drop this partition.
ORA-14759: SET INTERVAL is not legal on this table.
Cause: SET INTERVAL clause was specified. ALTER TABLE SET INTERVAL is only
legal on a range partitioned table with a single partitioning column. Additionally, this
table cannot have a maxvalue partition and cannot be the parent table for any
reference partitioned tables.
Action: Use SET INTERVAL only on a valid table.
ORA-14760: ADD PARTITION is not permitted on Interval partitioned objects
Cause: ALTER TABLE ADD PARTITION was attempted on an Interval partitioned
object.
Action: Do not perform the operation on an Interval partitioned object. Insert a row to
create the new partition.
ORA-14761: MAXVALUE partition cannot be specified for Interval partitioned
objects
Cause: An attempt was made to create a partition with a MAXVALUE highbound on
an Interval partitioned object.
Action: Do not create a partition with a MAXVALUE highbound.
ORA-14762: Domain index creation on interval partitioned tables is not permitted
Cause: An attempt was made to create a domain index on an interval partitioned
table.
ORA-12700 to ORA-19400 69-137
Action: Do not create a domain index on an interval partitioned table.

ORA-14763: Unable to resolve FOR VALUES clause to a partition number
Cause: Could not determine the partition corresponding to the FOR VALUES clause.
Action: Remove bind variables and dependencies on session parameters from the
values specified in the FOR VALUES clause.
ORA-14764: FOR VALUES clause cannot be specified for only one partition
Cause: An attempt was made to specify the FOR VALUES clause for only one of the
two partitions being merged.
Action: Specify a FOR VALUES clause for each of the two partitions being merged or
do not specify the FOR VALUES clause for either.
ORA-14765: Cannot create a partition while doing a create index
Cause: An attempt was made to create a partition concurrently with index creation.
Action: Retry the statement after the index build is finished.
ORA-14766: Unable to obtain a stable metadata snapshot
Cause: This operation was not able to obtain a stable snapshot of the interval
partitioning metadata.
Action: Retry the statement.
ORA-14767: Cannot specify this interval with existing high bounds
Cause: The interval specified conflicts with the existing high bound for the last
partition. The combination might lead to invalid dates for high bounds in the future.
Action: If this is a CREATE TABLE, try specifying a different high bound value for
the last partition, or a different interval. If this is an ALTER TABLE SET INTERVAL,
please choose either a different interval, or, modify the table to change the high
bound for the last partition.
ORA-14769: cannot interval partition nested table or XMLType with objectrelational storage
Cause: Interval partition was not supported for nested table and XMLType with
object-relational storage.
Action: Use a list or range partition instead.
ORA-14801: Hash composite partitioning is not supported
Cause: An attempt was made to partition a table using a Hash composite method.
Action: Do not partition the table by a Hash composite method.
ORA-14802: Specified operation is not permitted on Hash composite partitioned
objects
Cause: An unsupported operation was attempted on a Hash composite partitioned
object.
Action: Do not perform the operation on a Hash composite partitioned object.
ORA-14803: partition bound may not be specified for hash subpartitioned tables
Cause: A VALUES LESS THAN or VALUES clause was specified with a subpartition
description.
Action: Remove the VALUES LESS THAN or VALUES clause from the subpartition
description.
ORA-14804: A partition must be split into two or more partitions

Cause: An ALTER TABLE SPLIT PARTITION contained a description for only one
resulting partition.
Action: Specify at least 2 resulting partitions.
ORA-14805: last resulting partition cannot contain bounds
Cause: An ALTER TABLE SPLIT PARTITION contained a description for the last
partition which included the bounds.
Action: Do not specify bounds for the last resulting partition.
ORA-14806: merging more than two partitions or subpartitions is only supported
for heap tables
Cause: An ALTER TABLE MERGE PARTITIONS or MERGE SUBPARTITIONS with
more than two source partitions or subpartitions was issued. Merging more than two
partitions or subpartitions is only supported for heap tables.
Action: Specify exactly two partitions or subpartitions to merge.
ORA-14807: merging partitions or subpartitions using name TO name syntax is
only supported for range partitioned tables
Cause: An ALTER TABLE MERGE PARTITIONS pname TO pname or an ALTER
TABLE MERGE SUBPARTITIONS subpname TO subpname was issued. This is only
supported for range partitions or subpartitions.
Action: Specify all the partitions or subpartitions to be merged.
ORA-14808: ONLINE MOVE PARTITION is not supported for this table
Cause: An ALTER TABLE MOVE PARTITION ONLINE statement was issued on a
table that was either not a heap table or had an object type, domain index or bitmap
join index defined on it. This operation is only supported for heap tables.
Action: Do not use the ONLINE keyword.
ORA-14809: ONLINE MOVE PARTITION not supported for this schema
table owned by SYS, SYSTEM, PUBLIC, OUTLN or XDB.
ORA-14810: ONLINE MOVE PARTITION not supported while database is not
open or in migrate mode
table while the database was not open or was in migrate mode.
ORA-14811: ONLINE MOVE PARTITION not supported under supplemental
logging
table while supplemental logging was enabled.
ORA-12700 to ORA-19400 69-139
ORA-14812: DBMS_LOB operations not allowed on partition while it is being

moved online
Cause: A DBMS_LOB operation was issued on a LOB while an ALTER TABLE MOVE
PARTITION ONLINE was concurrently executing on the partition containing the
LOB.
Action: Reissue DBMS_LOB operation after MOVE PARTITION ONLINE has
completed.
ORA-14900: The logical transaction ID is no longer valid.
Cause: The logical transaction ID has been purged and the commit failed.
Action: Reconnect and re-run the transaction.
ORA-14901: Commits during replay are not permitted.
Cause: The transaction tried to commit during replay.
ORA-14902: Instance has not been configured for application continuity.
Cause: The partition of the transaction history table had not been created.
ORA-14903: Corrupt logical transaction detected.
Cause: The logical transaction was corrupt. The size was incorrect.
Action: Verify your network configuration.
ORA-14904: Corrupt logical transaction ID detected.
Cause: The logical transaction was corrupt. The database ID was incorrect.
Action: Verify your network configuration.
ORA-14905: Serializable transactions cannot be replayed.
Cause: The transaction tried to replay a serializable transaction.
ORA-14906: Get LTXID outcome operation is not permitted on the current session.
Cause: The transaction tried to execute get LTXID outcome on the current session.
Action: Check the parameters used to invoke get LTXID outcome.
ORA-14907: Cannot execute get LTXID outcome for the transaction of another user.
Cause: The transaction tried to execute get LTXID outcome for a different user
session.
Action: Check the parameters used to invoke get LTXID outcome.
ORA-14908: Cannot invoke get LTXID outcome while a transaction is open.
Cause: Get LTXID outcome could not be executed because a transaction was open.
Action: Invoke get LTXID outcome after the transaction has been completed.
ORA-14909: Current session has been blocked by another user with the same user
name using GET_LTXID_OUTCOME.
Cause: Could not commit after GET_LTXID_OUTCOME was invoked.
ORA-14910: Sessions with SYSDBA privilege are not allowed to connect to a

service that has commit outcome enabled.
Cause: A session with SYSDBA privilege tried to connect to a service that has commit
outcome enabled.
Action: Connect without the SYSDBA privilege.
ORA-14911: XA transactions are not supported by Transaction Guard.
Cause: The transaction tried to commit an XA transaction.
ORA-14912: Transactions by DRCP clients are not supported by Transaction
Guard.
Cause: The Database Resident Connection Pooling (DRCP) client tried to commit a
transaction while Transaction Guard was enabled.
ORA-14950: Force outcome failed. Client transaction is too old.
Cause: The client transaction had been commited or forced earlier.
Action: None
ORA-14951: Force outcome failed. Client transaction is ahead of server logical
transaction ID.
Cause: The client transaction had not been seen by the server and could not be forced.
This can happen if the server is restored or a flashback operation has been executed.
Action: None
ORA-14952: Force outcome failed. General error occurred.
Cause: The force outcome operation failed. See previous error for the reason.
Action: None
ORA-14953: Invalid partition ID specified.
Cause: The partition IDs of the transaction history table were not consecutive.
Action: Specify the next higer partition ID.
ORA-14954: Invalid tablespace name specified.
Cause: The tablespace did not exist.
Action: Specify an existing tablespace.
ORA-15000: command disallowed by current instance type
Cause: The user has issued a command to a conventional RDBMS instance that is only
appropriate for an ASM instance. Alternatively, the user has issued a command to an
ASM instance that is only appropriate for an RDBMS instance.
Action: Connect to the correct instance type and re-issue the command.
ORA-15001: diskgroup "string" does not exist or is not mounted
Cause: An operation failed because the diskgroup specified does not exist or is not
mounted by the current ASM instance.
Action: Verify that the diskgroup name used is valid, that the diskgroup exists, and
that the diskgroup is mounted by the current ASM instance.
ORA-12700 to ORA-19400 69-141
ORA-15002: parameter LOCK_NAME_SPACE exceeds limit of string characters

Cause: The LOCK_NAME_SPACE initialization parameter contained a value that is
too long.
Action: Correct the LOCK_NAME_SPACE initialization parameter.
ORA-15003: diskgroup "string" already mounted in another lock name space
Cause: The diskgroup could not be mounted by the ASM instance because it was
operating in a lockspace different than another existing ASM instance which had
already mounted the diskgroup.
Action: Check the LOCK_NAME_SPACE initialization parameter value, or dismount
the diskgroup from the other ASM instances.
ORA-15004: alias "string" does not exist
Cause: The specified alias did not exist within the diskgroup.
Action: Check the alias name and diskgroup name.
ORA-15005: name "string" is already used by an existing alias
Cause: An existing alias in the diskgroup used the same name.
Action: Select another alias name, or drop the existing alias.
ORA-15006: template "string" does not exist
Cause: The specified template did not exist within the diskgroup.
Action: Check the template name and diskgroup name.
ORA-15007: name is already used by an existing template
Cause: A template with the same name already exists.
Action: Select another template name, or drop the existing template.
ORA-15008: cannot drop system template
Cause: The specified template was created by the system and must always exist for
proper operation.
Action: Select another template name.
ORA-15009: ASM disk "string" does not exist
Cause: The specified ASM disk was not found.
Action: Check the ASM disk name.
ORA-15010: name 'string' is already used by an existing ASM disk
Cause: The specified name was already used in this diskgroup.
Action: Specify a different ASM disk name.
ORA-15011: failure group "string" does not exist in diskgroup "string"
Cause: The specified name did not match the failure group of any disks in the
diskgroup. This usually indicates that the failure group name was specified
incorrectly.
Action: Check the failure group name.
ORA-15012: ASM file 'string' does not exist
Cause: The ASM file was not found.
Action: Check the ASM file name.
ORA-15013: diskgroup "string" is already mounted

Cause: An ALTER DISKGROUP MOUNT command specified the name of a
diskgroup which is already mounted by the current ASM instance.
Action: Check the name of the diskgroup.
ORA-15014: path 'string' is not in the discovery set
Cause: The operating system path specified was outside the set of disks that are
discovered by the instance.
Action: Specify a operating system path within the set of disks that are discovered
based upon the ASM_DISKSTRING parameter. Alternatively, check the setting of the
ASM_DISKSTRING parameter.
ORA-15015: Specified path 'string' conflicts with path 'string'
Cause: The ASM instance previously discovered specified disk with an ASM library
using a different path.
Action: Use the discovery string of the ASM library to add the disk.
ORA-15016: inconsistent respecification of path 'string'
Cause: The specified path was provided more than once with different properties.
Action: Do not provide a path more than once. Alternatively, provide consistent
properties.
ORA-15017: diskgroup "string" cannot be mounted
Cause: The disk group could not be mounted by the ASM instance either of an IO
error or due to other reasons explained in alert log or trace files.
Action: Check for additional errors reported. Correct the error and retry the
operation.
ORA-15018: diskgroup cannot be created
Cause: The specified diskgroup could not be created.
Action: Check for additional errors reported.
ORA-15019: discovered duplicate path 'string' for 'string'
Cause: The discovery encountered multiple paths to the same disk.
Action: Check that the ASM_DISKSTRING parameter specifies only a single path for
each disk.
ORA-15020: discovered duplicate ASM disk "string"
Cause: The discovery encountered two disks claiming to be the same named ASM
disk.
each disk.
ORA-15021: parameter "string" is not valid in string instance
Cause: The specified parameter was not supported when starting an instance of this
type.
Action: Delete the specified parameter from the INIT.ORA file.
ORA-15022: unable to load an Oracle ASM library
Cause: An Oracle instance attempted to load an Oracle ASM library which could not
be discovered.
ORA-12700 to ORA-19400 69-143
Action: Check other error messages to determine why Oracle is unable to retrieve the
library path from the Oracle ASM instance.
ORA-15023: reached maximum allowable number of disks string
Cause: An attempt was made to add another disk to a diskgroup which already
contains the maximum number of disks allowed.
Action: Consider dropping existing disks from the diskgroup before adding
additional ones, or create a new diskgroup.
ORA-15024: discovered duplicately numbered ASM disk string
Cause: ASM discovered two disks claiming to have the same ASM disk number in the
same disk group.
each disk.
ORA-15025: could not open disk "string"
Cause: The specified disk could not be opened. If the database instance is running as
an Operating System (OS) user different from that of the ASM instance, then the
permissions on the database oracle binary may be incorrect.
Action: Check the additional error messages, if any. If the database instance is
running as an OS user different from that of the ASM instance, use the "srvctl"
command to stop and restart the database to fix the permissions.
ORA-15026: disk 'string' is not an ASM disk
Cause: The disk did not contain a valid ASM disk header.
Action: Check to see if the data on the disk has been changed by some system
administrator action.
ORA-15027: active use of diskgroup "string" precludes its dismount
Cause: An ALTER DISKGROUP ... DISMOUNT command specified a diskgroup
which had clients with open files in the diskgroup. Diskgroups cannot be dismounted
until all open files in the diskgroup are closed.
Action: Stop all clients that are using this diskgroup and retry the ALTER
DISKGROUP ... DISMOUNT command. Query the V$ASM_CLIENT fixed view in an
ASM instance or use ASMCMD LSOF to list active clients.
ORA-15028: ASM file 'string' not dropped; currently being accessed
Cause: An attempt was made to drop an ASM file, but the file was being accessed by
one or more clients and therefore could not be dropped.
Action: Stop all clients that are using this file and retry the drop command. Query the
V$ASM_CLIENT fixed view in an ASM instance or use ASMCMD LSOF to list active
clients.
ORA-15029: disk 'string' is already mounted by this instance
Cause: An attempt was made to add to a diskgroup a disk that was already mounted
by the current instance as part of some (possibly other) diskgroup.
Action: Specify a different disk in the command. Note that not even the FORCE
option can be used to correct the situation until the diskgroup containing the disk
becomes dismounted by this instance.
ORA-15030: diskgroup name "string" is in use by another diskgroup

Cause: A CREATE DISKGROUP command specfied a diskgroup name that was
already assigned to another diskgroup.
Action: Select a different name for the diskgroup.
ORA-15031: disk specification 'string' matches no disks
Cause: The device specification string to a CREATE DISKGROUP command did not
match any devices which could be discovered.
Action: Check the device specification string matches a disk on the system.
ORA-15032: not all alterations performed
Cause: At least one ALTER DISKGROUP action failed.
Action: Check the other messages issued along with this summary error.
ORA-15033: disk 'string' belongs to diskgroup "string"
Cause: An attempt was made to ADD to a diskgroup (or REPLACE with) a disk that
was already part of another diskgroup, or an attempt was made to DROP /
OFFLINE / ONLINE / CHECK a disk that was not part of the specified diskgroup.
Action: For ADD and REPLACE, check the path specifier for the disk. If it is certain
that the disk is not in use by another diskgroup, the FORCE option may be used to
override this check. For the other commands, check the name of the specified disk.
ORA-15034: disk 'string' does not require the FORCE option
Cause: An attempt was made to add the disk to the diskgroup using the FORCE
option. The disk was not found to be in use at the present time, so the FORCE option
was not permitted.
Action: Avoid gratuitous use of the FORCE option.
ORA-15035: no disks belong to diskgroup "string"
Cause: An attempt was made to mount a diskgroup for which no member disks were
discovered.
Action: Specify a valid diskgroup name that contains disks.
ORA-15036: disk 'string' is truncated
Cause: The size of the disk, as reported by the operating system, was smaller than the
size of the disk as recorded in the disk header block on the disk.
Action: Check if the system configuration has changed.
ORA-15037: disk 'string' is smaller than mimimum of string MBs
Cause: The size of the disk, as reported by the operating system, was too small to
allow the disk to become part of the diskgroup.
Action: Check if the system configuration is correct.
ORA-15038: disk 'string' mismatch on 'string' with target disk group [string] [string]
Cause: An attempt was made to mount into a disk group a disk whose recorded
allocation unit size, metadata block size, physical sector size, or creation time stamp
was inconsistent with the other disk group members.
Action: Check if the system configuration has changed. Verify disk discovery string.
ORA-15039: diskgroup not dropped
Cause: An attempt to drop a diskgroup failed.
ORA-12700 to ORA-19400 69-145
Action: See the associated messages for details about why the drop was not
successful.
ORA-15040: diskgroup is incomplete
Cause: Some of the disks comprising a diskgroup were not present.
Action: Check the hardware to ensure that all disks are functional. Also check that the
setting of the ASM_DISKSTRING initialization parameter has not changed.
Alternatively, for normal or high redundancy diskgroups, use MOUNT FORCE to
offline missing disks as part of mounting the diskgroup.
ORA-15041: diskgroup "string" space exhausted
Cause: At least one disk in the diskgroup is out of space.
Action: If all disks are evenly balanced, add more disks to the diskgroup,
ORA-15042: ASM disk "string" is missing from group number "string"
Cause: The specified disk, which is a necessary part of a diskgroup, could not be
found on the system.
Action: Check the hardware configuration.
ORA-15043: ASM disk "string" is not a diskgroup member
Cause: The specified disk has been removed from the diskgroup, but a disk matching
its name was found.
Action: Check the hardware configuration.
ORA-15044: ASM disk 'string' is incorrectly named
Cause: Either the specified disk had its contents changed such that it no longer
contained an ASM disk name in its header that matches the diskgroup information or
its FAILGROUP information may have become inconsistent.
Action: Drop the disk from the diskgroup.
ORA-15045: ASM file name 'string' is not in reference form
Cause: The ASM file name was not in a form that can be used to reference an existing
file because a file/incarnation number or an alias name was not present or a template
name was included.
Action: Correct the specified ASM file name.
ORA-15046: ASM file name 'string' is not in single-file creation form
Cause: The ASM file name was not in a form that can be used to create an single file
because a file/incarnation number was present.
ORA-15047: ASM file name 'string' is not in multiple-file creation form
Cause: The ASM file name was not in a form that can be used to create multiple files
because either a fully-qualified file name or an alias name was present.
ORA-15048: ASM internal files cannot be deleted
Cause: An attempt was made to delete a metadata file used by ASM to manage the
diskgroup.
Action: Check the specified ASM file name.
ORA-15049: diskgroup "string" contains string error(s)

Cause: Errors were discovered by the ALTER DISKGROUP CHECK command.
Action: See the alert log for details of the errors.
ORA-15050: disk "string" contains string error(s)
Cause: Errors were discovered by the ALTER DISKGROUP CHECK DISK command.
ORA-15051: file 'string' contains string error(s)
Cause: Errors were discovered by the ALTER DISKGROUP CHECK FILE command.
ORA-15052: ASM file name 'string' is not in diskgroup "string"
Cause: The ASM file name did not contain a diskgroup name that specified the correct
diskgroup as implied by the other arguments to the command.
Action: Correct the specified ASM file name or diskgroup name.
ORA-15053: diskgroup "string" contains existing files
Cause: An attempt was made to drop a diskgroup that still contains existing files.
Action: Specify the INCLUDING CONTENTS option to drop the diskgroup and all of
its existing files.
ORA-15054: disk "string" does not exist in diskgroup "string"
Cause: An attempt was made to alter a disk that is not part of the specified diskgroup.
Action: Check the name of the specified disk and the specified diskgroup.
ORA-15055: unable to connect to ASM instance
Cause: The RDBMS instance was unable to connect to the required ASM instance
when accessing a disk group.
Action: Check the additional error messages. May need to configure correct ASM sid
or make sure the RDBMS instance has OS privileges for ASM SYSDBA.
ORA-15056: additional error message
Cause: An operating system error occured.
ORA-15057: specified size of string MB is larger than actual size of string MB
Cause: A disk size expression exceeded the amount of storage actually available, as
reported by the operating system.
Action: Specify a valid size.
ORA-15058: disk 'string' belongs to an incompatible diskgroup
Cause: An attempt was made to ADD to a diskgroup a disk which was already part of
another diskgroup. The other diskgroup was written by a more recent software
release.
Action: Check the path specifier for the disk. If it is certain that the disk is not in use
by another diskgroup, the FORCE option may be used to override this check.
ORA-15059: invalid device type for ASM disk
Cause: The device type of the discovered disk was not valid for use as an ASM disk.
ORA-12700 to ORA-19400 69-147
Action: Check the file path and retry or exclude it from the discovery set. See the
accompanying operating system error for additional information.
ORA-15060: template "string" does not exist
Cause: A command specified a template name, either directly or as part of an ASM
file name, which did not exist.
Action: Check the template specifier in the command.
ORA-15061: ASM operation not supported [string]
Cause: An ASM operation was attempted that is invalid or not supported by this
version of the ASM instance.
Action: This is an internal error code that is used for maintaining compatibility
between software versions and should never be visible to the user; contact Oracle
support Services.
ORA-15062: ASM disk is globally closed
Cause: The disk to which the I/O request was issued has gone offline or has been
globally closed by the background process. Check other messages in the trace files for
more information.
Action: Bring the disk online for I/Os to get through.
ORA-15063: ASM discovered an insufficient number of disks for diskgroup
"string"
Cause: ASM was unable to find a sufficient number of disks belonging to the
diskgroup to continue the operation.
Action: Check that the disks in the diskgroup are present and functioning, that the
owner of the ORACLE binary has read/write permission to the disks, and that the
ASM_DISKSTRING initialization parameter has been set correctly. Verify that ASM
discovers the appropriate disks by querying V$ASM_DISK from the ASM instance.
ORA-15064: communication failure with ASM instance
Cause: There was a failure to communicate with the ASM instance, most likely
because the connection went down.
Action: Check the accompanying error messages for more information on the reason
for the failure. Note that database instances will always return this error when the
ASM instance is terminated abnormally.
ORA-15065: hash collision for diskgroup names 'string' and 'string'
Cause: There was a collision in the group name used for the diskgroup. The
diskgroup(s) cannot be mounted using colliding names.
Action: Use a different diskgroup name and also report to Oracle Support Services the
two diskgroup names which collided.
ORA-15066: offlining disk "string" in group "string" may result in a data loss
Cause: Following I/O failures, the disks holding all copies of a data block were
attempted to be taken offline.
Action: Check the accompanying error messages for more information on the reason
for the disk I/O failures.
ORA-15067: command or option incompatible with diskgroup redundancy
Cause: An attempt was made to use a feature which is not permitted by the
diskgroup's redundancy policy. Common examples are forcibly dropping a disk from
an EXTERNAL REDUNDANCY diskgroup, using the FAILGROUP clauses with an

EXTERNAL REDUNDANCY diskgroup, or using invalid template attributes.
Action: Omit the option from the command.
ORA-15068: maximum number of diskgroups string already mounted
Cause: An attempt was made to mount more diskgroups than the instance is capable
of mounting at one time.
Action: Dismount a mounted diskgroup and retry the command.
ORA-15069: ASM file 'string' not accessible; timed out waiting for lock
Cause: An attempt was made to access an ASM file, but the file is currently being
created, resized, or deleted and therefore cannot be accessed.
Action: No action required, or try again later, after the create or resize has completed.
ORA-15070: maximum number of files string exceeded in diskgroup "string"
Cause: The diskgroup ran out of space.
Action: Delete some existing ASM files or create files in a new diskgroup.
ORA-15071: ASM disk "string" is already being dropped
Cause: An attempt was made to drop or replace a disk that was already in the process
of being dropped from the diskgroup. Alternatively, an attempt was made to forcibly
drop a disk from a diskgroup using the FORCE option that was already being forcibly
dropped from the diskgroup.
Action: Check the ASM disk name and FORCE option as specified in the command.
ORA-15072: command requires at least string regular failure groups, discovered
only string
Cause: An attempt was made to create either a normal redundancy diskgroup for
which fewer than two regular failure groups were both specified and discovered, or a
high redundancy diskgroup for which fewer than three regular failure groups were
both specified and discovered, or an external redundancy diskgroup for which only
quorum disks were both specified and discovered.
Action: Check the that the command does specify the required number of failure
groups, and that all of the specified disks are discovered by ASM. A query of the V
$ASM_DISK fixed view will show which disks are discovered by ASM. Note that a
quorum failure group will not be used as a regular failure group. An external
redundancy diskgroup requires at least one regular disk.
ORA-15073: diskgroup string is mounted by another ASM instance
Cause: An attempt was made to drop a diskgroup that is still mounted somewhere in
the cluster by another instance.
Action: dismount the diskgroup from all nodes except the one performing the drop
diskgroup command.
ORA-15074: diskgroup string requires rebalance completion
Cause: An attempt was made to repeatedly add or drop disks from a diskgroup. ASM
could not perform the operation given the current state of the diskgroup.
Action: Manually invoke the ALTER DISKGROUP REBALANCE command and
allow the rebalance to run to completion. Alternatively, invoke the ALTER
DISKGROUP UNDROP DISKS command and allow the rebalance to run to
completion. After the rebalance has completed, retry the operation.
ORA-12700 to ORA-19400 69-149
ORA-15075: disk string is not visible on instance number string

Cause: An ALTER DISKGROUP ADD DISK command specified a disk that could not
be discovered.
Action: Check operating system permissions for the device and the storage subsystem
configuration on the specified node.
ORA-15076: Emulating I/O errors on the OSM disk
Cause: The disk to which the I/O request was issued is in an error emulation mode.
Action: Bring the disk online for I/Os to get through.
ORA-15077: could not locate ASM instance serving a required diskgroup
Cause: The instance failed to perform the specified operation because it could not
locate a required ASM instance.
Action: If you want to start a database instance, start an ASM instance and mount the
required diskgroup. If you want to start an ASM instance, relink the ORACLE binary
with ASM_ON or explicitly set INSTANCE_TYPE initialization parameter to ASM.
ORA-15078: ASM diskgroup was forcibly dismounted
Cause: The diskgroup to which the I/O request was issued was forcibly dismounted
(with the ALTER DISKGROUP DISMOUNT FORCE command) so that it could not be
accessed.
Action: Mount the diskgroup to allow access again.
ORA-15079: ASM file is closed
Cause: The file to which the I/O request was issued was closed. This could have been
a consequence of the diskgroup being dismounted.
Action: Make sure the diskgroup is mounted and the file is open.
ORA-15080: synchronous I/O operation failed to string block string of disk string in
disk group string
Cause: A synchronous I/O operation invoked on a disk has failed.
Action: Make sure that all of the disks are operational.
ORA-15081: failed to submit an I/O operation to a disk
Cause: A submission of an I/O operation to a disk has failed.
Action: Make sure that all the disks are operational.
ORA-15082: ASM failed to communicate with client
Cause: There was a failure or time out when ASM tried to communicate with a
connected RDBMS or Oracle ASM Dynamic Volume Manager (Oracle ADVM) client.
Action: Check the accompanying error messages and alert logs for more information
on the reason for the failure. Check system specific logs (/var/log/messages on
Linux, Event Log on Windows) for Oracle ADVM messages.
ORA-15083: failed to communicate with ASMB background process
Cause: A database instance failed to communicate with its ASMB background process
when attempting to access an ASM file.
Action: Check the alert log for more information on the reason for the failure.
ORA-15084: ASM disk "string" is offline and cannot be dropped.
Cause: An attempt was made to drop a disk that is offline.
Action: Check the ASM disk name as specified in the command; or, if needed, use the
DROP DISK FORCE option.
ORA-15085: disk "string" has inconsistent sector size (expected string, actual string)
with disk group "string"
Cause: An attempt to mount a disk group failed because a disk reported inconsistent
sector size value.
Action: Use disks with sector size consistent with disk group sector size, or make sure
the operating system can accurately report the disk sector size.
ORA-15086: Diskgroup sector size must be specified.
Cause: The _disk_sector_size_override parameter was used but the sector disk value
was not specified in the command.
Action: Specify the sector size value, or do not set (or do not set to TRUE) the
_disk_sector_size_override parameter.
ORA-15087: disk 'string' is formatted as an ext2/ext3 or OCFS2 file system.
Cause: A signature was found on the specified disk indicating that it is in use by an
existing ext2/ext3 or OCFS2 file system.
Action: Adjust discovery string and device permissions to exclude previously
formatted disks from discovery.
ORA-15088: diskgroup creation incomplete
Cause: A previous failure during diskgroup creation left the diskgroup in an
inconsistent state.
Action: Issue DROP DISKGROUP ... FORCE INCLUDING CONTENTS to clean up
the failed creation, then re-create the diskgroup.
ORA-15090: handle string is not a valid descriptor
Cause: The file handle was not valid in this session.
Action: Submit a handle obtained from a successful call to
DBMS_DISKGROUP.OPEN().
ORA-15091: operation incompatible with open handle in this session
Cause: The current session contained an open handle from the DBMS_DISKGROUP
PL/SQL package which precluded performing the command.
Action: Execute the command in a different session.
ORA-15092: I/O request size string is not a multiple of logical block size string
Cause: The length of the request was not a multiple of logical block size.
Action: Correct the error and retry the operation.
ORA-15093: buffer only contains string bytes, I/O requested is string bytes
Cause: The buffer supplied for write was too small to satisfy the request.
Action: Correct the error and retry the operation.
ORA-15094: attempted to write to file opened in read only mode
Cause: The file handle passed to DBMS_DISKGROUP.WRITE() did not have write
privileges.
Action: Obtain a file handle in read-write mode and retry the write operation.
ORA-12700 to ORA-19400 69-151
ORA-15095: reached maximum ASM file size (string GB) for this disk group\n
Cause: An ASM file creation or file resize operation exceeded the maximum file size
permitted by ASM for this disk group.
Action: Use smaller files. Alternatively, set the disk group attribute compatible.rdbms
>= 11.1 if not set already.
ORA-15096: lost disk write detected
Cause: A failure either by disk hardware or disk software caused a disk write to to be
lost, even though ASM received acknowledgement that the write completed.
Alternatively, a clustering hardware failure or a clustering software failure resulted in
an ASM instance believing that another ASM instance had crashed, when in fact it
was still active.
Action: The disk group is corrupt and cannot be recovered. The disk group must be
recreated, and its contents restored from backups.
ORA-15097: cannot SHUTDOWN ASM instance with connected client (process
string)
Cause: A SHUTDOWN command was issued to an ASM instance that had one or
more connected clients.
Action: Stop all clients that are using this ASM instance and retry the SHUTDOWN
command. Alternatively, use the SHUTDOWN ABORT command. Note that issuing
the SHUTDOWN ABORT command to an ASM instance results in abormal
termination of all RDBMS instances connected to that ASM instance. One of the active
clients has been listed in the error message. Query the V$ASM_CLIENT fixed view in
an ASM instance or use ASMCMD LSOF to list all active clients.
ORA-15098: file type not recognized by ASM instance
Cause: An attempt was made by DB instance to create a file for a file type that is not
recognized by current version of ASM instance.
Action: Upgrade ASM to higher version that recognizes this file type.
ORA-15099: disk 'string' is larger than maximum size of string MBs
Cause: The specified size of the disk was too big to allow the disk to become part of
the diskgroup.
Action: Specify a smaller disk size than the maximum allowed size.
ORA-15100: invalid or missing diskgroup name
Cause: The command did not specify a valid diskgroup name.
Action: Specify a valid diskgroup name.
ORA-15101: no action specified
Cause: The ALTER DISKGROUP command did not specify any alterations.
Action: Specify at least one operation clause.
ORA-15102: invalid POWER expression
Cause: The syntax of the POWER expression was invalid.
Action: Specify a valid POWER expression.
ORA-15103: conflicting or duplicate REPAIR options
Cause: The command specified conflicting or duplicate REPAIR keywords.
Action: Specify only one REPAIR action.
ORA-15104: conflicting CONTENTS options

Cause: The command specified conflicting or duplicate INCLUDING CONTENTS or
EXCLUDING CONTENTS options.
Action: Specify only one option.
ORA-15105: missing or invalid FAILGROUP name
Cause: The command did not specify a valid failure group name.
Action: Specify a valid failure group name.
ORA-15106: missing or invalid operating system disk locator string
Cause: The command did not specify a valid operating system path for the device as a
string.
Action: Specify a valid operating system path for the device.
ORA-15107: missing or invalid ASM disk name
Cause: The command did not specify a valid ASM disk name identifier.
Action: Specify a valid ASM disk name identifier.
ORA-15108: missing or invalid template name
Cause: The command did not specify a valid template name identifier.
Action: Specify a valid template name identifier.
ORA-15109: conflicting protection attributes specified
Cause: The command contained an invalid combination of the UNPROTECTED,
MIRROR, or PARITY keywords.
Action: Specify only one keyword.
ORA-15110: no diskgroups mounted
Cause: No diskgroups were specified in the ASM_DISKGROUPS parameter, so
instance startup or the ALTER DISKGROUP ALL MOUNT command did not mount
any diskgroups.
Action: Specify valid diskgroups in the ASM_DISKGROUPS parameter or ignore the
error.
ORA-15111: conflicting or duplicate STRIPE options
Cause: The command contained both a FINE and COARSE keyword, or contained the
FINE keyword more than once, or contained the COARSE keyword more than once.
Action: Specify only one keyword.
ORA-15112: no diskgroups currently mounted
Cause: An ALTER DISKGROUP ALL command did not find any mounted
diskgroups upon which to operate. Either instance shutdown or an ALTER
DISKGROUP ALL DISMOUNT command did not dismount any diskgroups, or an
ALTER DISKGROUP ALL UNDROP DISKS command did not undrop any disks.
Action: Mount the diskgroups on which you wish to operate or ignore the error.
ORA-15113: alias name 'string' refers to a directory
Cause: The name specified referred to a directory in the alias directory and not a valid
alias entry.
Action: Check the alias name and retry.
ORA-12700 to ORA-19400 69-153
ORA-15114: missing or invalid ASM file name

Cause: The command did not specify a valid ASM file name identifier.
Action: Specify a valid ASM file name identifier.
ORA-15115: missing or invalid ASM disk size specifier
Cause: The command did not specify a valid ASM disk size.
Action: Specify a valid ASM disk size.
ORA-15116: invalid combination of ALTER DISKGROUP options
Cause: The ALTER DISKGROUP options may not be combined in this manner.
Action: Issue separate ALTER DISKGROUP commands to accomplish the desired
action.
ORA-15117: command only operates on one diskgroup
Cause: An ALTER DISKGROUP, CREATE DISKGROUP, or DROP DISKGROUP
command specified a list of diskgroups or the keyword ALL in a context where only a
single diskgroup was permitted.
Action: Issue separate ALTER DISKGROUP, CREATE DISKGROUP, or DROP
DISKGROUP commands to accomplish the desired action.
ORA-15118: ASM diskgroup 'string' was forcibly dismounted.
Cause: The diskgroup to which the I/O request was issued was forcibly dismounted
(with the ALTER DISKGROUP DISMOUNT FORCE command) so that it could not be
accessed.
Action: Mount the diskgroup to allow access again.
ORA-15119: too many disk groups (string); maximum allowed string
Cause: An attempt was made to mount more than the maximum allowed number of
disk groups.
Action: Do not attempt to mount more than the maximum allowed number of disk
groups. Check ASM instance parameters.
ORA-15120: ASM file name 'string' does not begin with the ASM prefix character
Cause: A file name was specified to ASM which did not begin with the ASM prefix
character (currently '+'). ASM uses the prefix to determine that a file specification is in
fact an ASM file.
Action: Correct the file name specification.
ORA-15121: ASM file name 'string' contains an invalid diskgroup name
Cause: A file name was specified that did not contain a valid diskgroup name. The
diskgroup name follows immediately after the ASM prefix character. It must start
with an alphabetic character, and consist of up to 30 characters which are alphabetic,
numeric, or the characters '$' and '_'.
ORA-15122: ASM file name 'string' contains an invalid file number
Cause: A numeric file name was specified which did not contain a valid ASM file
number. The ASM file number follows immediately after the diskgroup name. It must
be preceeded by a '.' character, and contain only numeric characters.
ORA-15123: ASM file name 'string' contains an invalid incarnation number

Cause: A numeric file name was specified which did not contain a valid ASM
incarnation number. The ASM incarnation number follows immediately after the
ASM file number. It must be preceeded by a '.' character, and contain only numeric
characters.
ORA-15124: ASM file name 'string' contains an invalid alias name
Cause: A file name was specified which did not contain a valid ASM alias name. The
ASM alias name, if present, follows immediately after the diskgroup name, in place of
the ASM file number. It must be preceeded by a slash, start with an alphabetic
character, and consist of up to 48 characters which are alphabetic, numeric, or the
characters '$', '_', '-', or '#". A space can separate two parts of an alias name.
ORA-15125: ASM file name 'string' contains an invalid template name
Cause: A file name was specified to ASM which did not contain a valid template
name. The template name, if present, follows immediately after the ASM incarnation
number or the ASM alias name, if such is used in place of the ASM file number. It
must be enclosed in parenthesis, start with an alphabetic character, and consist of up
to 30 characters which are alphabetic, numeric, or the characters '$' and '_'.
ORA-15126: component within ASM file name 'string' exceeds maximum length
Cause: The maximum identifier length of 48 characters was exceeded for the
diskgroup name, template name, or alias name field within the ASM file name.
ORA-15127: ASM file name 'string' cannot use templates
Cause: A fully qualified ASM file name was specified. Such a specification does not
permit the inclusion of a template name in the ASM file name.
ORA-15128: ASM file name 'string' exceeds maximum length string
Cause: The maximum ASM file name length of 256 characters was exceeded for the
combination of diskgroup name, file number, template name, alias name plus
punctuation within the ASM file name.
ORA-15129: entry 'string' does not refer to a valid directory
Cause: The entry indicated did not refer to a directory. Attempt was made to access
the contents of this directory.
Action: Correct the error and try again.
ORA-15130: diskgroup "string" is being dismounted
Cause: The diskgroup is being dismounted by request or because an I/O error was
encountered that could not be handled by taking the disks offline. A disk cannot be
offlined whenever doing so could result in all copies of a redundant extent being
unavailable.
Action: Repair the hardware problem and re-mount the diskgroup. Refer to the alert
log to determine which disks have failed.
ORA-12700 to ORA-19400 69-155
ORA-15131: block string of file string in diskgroup string could not be read
Cause: A block could not be read because the disk containing the block is either
offline or an I/O error occured while reading the block. If this is mirrored file, then all
disks that contain a copy of the block are either offline or received errors.
Action: Repair the affected disk and bring it back online. Refer to accompanying error
messages to determine which disk has failed.
ORA-15132: block string of file string in diskgroup string could not be written
Cause: A block could not be written because the disk containing the block is either
offline or an I/O error occured while writing the block. If this is mirrored file, then
insufficient disks which contain a copy of the block are either offline or received
errors.
Action: Repair the affected disk and bring it back online. Refer to accompanying error
messages to determine which disk has failed.
ORA-15133: instance recovery required for diskgroup string
Cause: An instance in the cluster crashed making instance recovery necessary.
Action: None. This error should not normally be seen by an ASM client. ASM will
trap this error and retry the operation after doing instance recovery automatically.
ORA-15134: mirror resilvering not supported for string
Cause: The specified device requires oracle to take mirror resilvering responsiblity.
ASM does not resilver logical volume manager (lvm) based mirrors.
Action: Disable lvm-based mirroring or set the parameter
_asm_allow_lvm_resilvering to TRUE. One might experience performance
degradation when lvm-based resilvering is enabled with ASM.
ORA-15135: The string cluster is not in rolling patch state. The patch level [string]
of instance string is not the same as the current cluster patch level [string].
Cause: During startup, this instance found one or more other instances running at a
different patch level, and the cluster was not in rolling patch state. Startup of this
instance failed.
Action: The patch level of this instance differs from the cluster patch level. If the
intention is to patch the cluster using the rolling option, then set the cluster in rolling
patch state using the 'crsctl start rollingpatch' command from an active node, and
restart Oracle Clusterware on this node. If the intention is to patch the cluster in a
non-rolling manner, and the patch has been applied on the local node, then stop all of
the active nodes in the cluster that have a patch level that does not match the patch
level of the current node. Use the 'crsctl query crs softwarepatch host' command to
retrieve the configured patch level of a node. If the intention is to patch the cluster in
a non-rolling manner, and the patch has not been applied on the local node, then
apply the requisite patch, and restart Oracle Clusterware on this node. Patches
applied on a node can be obtained by issuing the the 'crsctl query crs releasepatch'
command.
ORA-15136: cluster in rolling patch from patch level [string] to [string]
Cause: The current patch level of the instance was incompatible with the rolling patch
operation of the cluster.
Action: The patch level of the new member instance must be one of the two patch
levels involved in the rolling patch operation.
ORA-15137: The string cluster is in rolling patch state.

Cause: The cluster was already in the middle of rolling patch.
Action: Rolling patch needs to be stopped before attempting to start again.
ORA-15138: cluster rolling patch incomplete
Cause: The cluster was still performing rolling patch.
Action: Ensure that all of the instances in the cluster are patched before retrying the
command.
ORA-15139: patch level of string instances differ in cluster
Cause: Not all of the instances in the cluster had the same set of patches.
Action: Ensure that all of the instances in the cluster have the same patches before
retrying the command. Find the configured patch level on a node using the 'crsctl
query crs softwarepatch' command.
ORA-15140: rolling patch prevented by string
Cause: One or more instances were blocking the rolling patch.
Action: Terminate or wait until the reported operation is complete before attempting
the rolling patch to the cluster.
ORA-15141: The string cluster is not in either rolling upgrade or rolling patch state.
Cause: The ALTER SYSTEM STOP ROLLING MIGRATION or ALTER SYSTEM
STOP ROLLING PATCH command was executed when the cluster was not in either
the rolling upgrade or rolling patch state.
Action: The system has to be set to rolling upgrade or rolling patch state before
attempting to execute the command.
ORA-15142: either MIGRATION or PATCH keyword expected
Cause: The keyword was missing.
ORA-15143: either APPLY or ROLLBACK keyword expected
Cause: The keyword was missing.
ORA-15144: disk 'string' is about to fail
Cause: An attempt was made to ADD (or REPLACE) a failing disk to a disk group.
Action: Specify a different disk in the command. Note that not even the FORCE
option can be used to add the disk to the disk group.
ORA-15145: ASM disk 'string' is online and cannot be replaced.
Cause: The REPLACE DISK operation specified a disk which is online.
Action: Check to confirm that the ASM disk is offline. Online disks can be replaced
while maintaining redundancy by issuing ADD and DROP disk commands in a
single SQL statement.
ORA-15146: Rolling migration or patching operation failed
Cause: Operation failed due to temporary issue.
ORA-12700 to ORA-19400 69-157
ORA-15147: failed to start the instance

Cause: The instance could not be started during rolling upgrade from ASM instance
versions prior to 12.1.0.0.0
Action: Complete the rolling upgrade process and start the instance.
ORA-15148: Too many CRS users are created.
Cause: The number of CRS users has reached its limit of 999. The situation is
unexpected.
Action: Check to see why so many CRS users are created.
ORA-15149: another ASM instance found running on the host
Cause: Another ASM instance found on the host. Only one ASM instance is supported
on a host.
Action: Shut down the other instance before starting this ASM instance.
ORA-15150: instance lock mode 'string' conflicts with other ASM instance(s)
Cause: Some other ASM instance used the lock name space in a conflicting mode.
Action: Shut down the other instance or start up in compatible mode. Alternatively,
set the DB_UNIQUE_NAME initialization parameter to avoid the conflict.
ORA-15151: missing or invalid version number for rolling migration
Cause: The command did not specify a valid version number.
Action: Correct the version number in the command. It should be of the form
v#.#.#.#.# or other forms with fewer numbers delimited by a period. The version
number must be different from the current software version of the instance.
ORA-15152: The string cluster is in rolling upgrade state.
Cause: The cluster was already in the middle of rolling upgrade.
Action: Rolling upgrade needs to be stopped before attempting to start again.
ORA-15153: The string cluster is not in rolling upgrade state. The version [string] of
instance string is not the same as the current cluster version [string].
Cause: During startup, this instance found one or more other instances running at a
different version, and the cluster was not in rolling upgrade state. Startup of this
instance failed.
Action: The version of this instance differs from the cluster version. If the intention is
to upgrade the cluster using the rolling option, then set the cluster in rolling upgrade
state using the 'crsctl start rollingupgrade' command from an active node, and restart
Oracle Clusterware on this node. If the intention is to upgrade the cluster in a nonrolling manner, and the local node has already been upgraded, then stop all of the
active nodes in the cluster that have an older version than the current node. Use the
'crsctl query crs softwareversion host' command to retrieve the configured version of a
node. If the intention is to upgrade the cluster in a non-rolling manner, and the local
node has not been upgraded yet, then upgrade the node by running the
rootupgrade.sh script.
ORA-15154: cluster rolling upgrade incomplete
Cause: The cluster was still performing rolling upgrade.
Action: Ensure that all the instances in the cluster are upgraded before retrying the
command.
ORA-15155: version incompatible with the cluster

Cause: The current software version of the instance was incompatible with the other
members of the cluster.
Action: Make sure that all the members of the cluster are at the same version. If you
are attempting to perform rolling upgrade, execute ALTER SYSTEM START
ROLLING command. Ensure that the version being upgraded to is compatible with
the existing version of the cluster.
ORA-15156: cluster in rolling upgrade from version [string] to [string]
Cause: The current software version of the instance was incompatible with the rolling
upgrade operation of the cluster.
Action: The version number of new member instance must be one of the two versions
involved in the rolling upgrade.
ORA-15157: rolling migration is not allowed
Cause: The cluster was not capable of handling ASM rolling migration.
Action: The Oracle Cluster Services is using vendor clusterware. Oracle cannot
perform rolling upgrade or downgrade using vendor cluster ware. Restart ASM
instances using Oracle cluster ware and retry the operation.
ORA-15158: rolling upgrade prevented by string
Cause: One or more instances were blocking the rolling upgrade.
the rolling upgrade to the cluster.
ORA-15160: rolling migration internal fatal error in module string,string
Cause: Rolling migration experienced a fatal error.
Action: Please contact Oracle support services.
ORA-15161: invalid SYS_CLUSTER_PROPERTIES parameter
Cause: The parameter passed in for SYS_CLUSTER_PROPERTIES is invalid
Action: Pass in the correct parameter, refer to user documentation for a list of allowed
parameter values.
ORA-15162: cluster in rolling downgrade
Cause: The cluster was already in the middle of rolling downgrade.
Action: Rolling downgrade needs to be stopped before attempting to start again.
ORA-15163: cluster is not in the rolling downgrade to string
Cause: The cluster was not in the rolling downgrade.
Action: Start the rolling downgrade using the ALTER SYSTEM START ROLLING
MIGRATION command from another ASM instance and restart this instance.
ORA-15164: cluster rolling downgrade incomplete
Cause: The cluster was still performing rolling downgrade.
Action: Ensure that all the instances in the cluster are downgraded before retrying the
command.
ORA-15166: cluster in rolling downgrade from version [string] to [string]
Cause: The current software version of the instance was incompatible with the rolling
downgrade operation of the cluster.
ORA-12700 to ORA-19400 69-159
Action: The version number of new member instance must be one of the two versions
involved in the rolling downgrade.
ORA-15168: rolling downgrade prevented by string
Cause: One or more instances were blocking the rolling downgrade.
the rolling downgrade to the cluster.
ORA-15169: destination 'string' is a subdirectory of 'string'
Cause: Attempt to rename directory failed because the new directory name was a
subdirectory of the original directory.
Action: Correct the path of the destination and try again.
ORA-15170: cannot add entry 'string' in directory 'string'
Cause: Other errors prevented directory/alias creation.
Action: Correct the errors and try again.
ORA-15171: invalid syntax in the alias path after 'string'
Cause: An invalid alias/directory name syntax was specified.
Action: Correct the alias path and try again.
ORA-15173: entry 'string' does not exist in directory 'string'
Cause: The specified alias did not exist in the given directory.
ORA-15174: unable to create alias name
Cause: An attempt to create an alias name for an ASM file failed.
Action: Check the alert logs and trace files of the Oracle ASM instance for more
information on the failure, as well as checking the accompanying error messages.
ORA-15175: cannot create alias for diskgroup metadata file 'string'
Cause: An attempt was made to create an alias for a diskgroup metadata file.
ORA-15176: file 'string' already has an alias associated with it
Cause: An attempt was made to create an alias for a file that already had an existing
alias.
Action: Correct the file name and try again or drop existing alias.
ORA-15177: cannot operate on system aliases
Cause: An attempt was made to modify a system alias.
Action: Correct the alias name and try again.
ORA-15178: directory 'string' is not empty; cannot drop this directory
Cause: An attempt was made to drop a directory that contained valid entries.
Action: Correct the directory path or specify the FORCE option to drop a directory
that is not empty.
ORA-15179: missing or invalid alias name
Cause: The command did not specify a valid alias identifier.
Action: Specify a valid alias identifier.
ORA-15180: could not open dynamic library string, error [string]

Cause: The library was not accessible
Action: Correct the permissions of the library and try again.
ORA-15181: symbol [string] not found in library string, error [string]
Cause: An error was encountered while loading the specified ASMLIB symbol.
Action: Correct the error reported and try again.
ORA-15182: ASMLIB [string] version mismatch, ORACLE version [string]
Cause: The ASMLIB version reported is not supported by the ORACLE binary.
Action: Install the correct library and try again.
ORA-15183: ASMLIB initialization error [string]
Cause: Unable to initialize the ASMLIB in ORACLE.
Action: Check the configuration of ASMLIB or deinstall ASMLIB if not used.
ORA-15184: ASMLIB error could not be determined [string] [string]
Cause: An error was encountered which cannot be diagnosed further.
Action: Contact ASMLIB libary vendor for support.
ORA-15185: could not close dynamic library string, error [string]
Cause: Could not close the dynamic library.
Action: Contact ASMLIB libary vendor for support.
ORA-15186: ASMLIB error function = [string], error = [string], mesg = [string]
Cause: An error occured during a call to function listed in the error.
Action: The detailed message associated with the error is listed along with the error.
Correct the error and try again or contact ASMLIB library vendor for support.
ORA-15187: Incompatible RDBMS operation [string] pushed to storage
Cause: RDBMS to storage version mismatched with incompatibility operation.
Action: Upgrade RDBMS to match storage version.
ORA-15188: process terminated due to an ASMLIB error
Cause: A process was terminated as a result of an ASMLIB error.
Action: See the alert log for more information. Reconnect to the database or the ASM
instance. If the process termination resulted in instance termination, restart the
instance.
ORA-15192: invalid ASM disk header [string] [string] [string] [string] [string]
Cause: ASM encountered an invalid disk header.
ORA-15196: invalid ASM block header [string:string] [string] [string] [string]
[string != string]
Cause: ASM encountered an invalid metadata block.
ORA-12700 to ORA-19400 69-161
ORA-15197: suppressing string additional ASM messages

Cause: The ASM command generated so many erorrs that this summary message was
reported in place of many individual messages.
Action: If the command contained multiple actions, try separating each action into its
own command and executing each command by itself. Otherwise, try not to generate
so many errors.
ORA-15198: operation string is not yet available
Cause: An unimplemented operation was attempted.
Action: Consider upgrading to later releases as they become available.
ORA-15200: initialization parameter string (string) is not a power of two
Cause: The value specified for this initialization parameter was not a power of two.
Action: Correct the initialization parameter value and restart the instance.
ORA-15201: disk string contains a valid RDBMS file or foreign volume
Cause: A disk specified in a CREATE DISKGROUP or ALTER DISKGROUP ... ADD
DISK command appeared to contain a file from an existing database or a foreign
volume. By default, as a safeguard against damaging an existing database or foreign
volume, ASM does not allow a disk group to be created using this disk.
Action: Check that the ASM disk specification is correct. Otherwise, when storage
from a defunct database or unmounted foreign volume is reused as part of an ASM
disk group, specify the FORCE option to the ASM SQL command. See the alert log for
more information.
ORA-15202: cannot create additional ASM internal change segment
Cause: The mount of a diskgroup by an additional instance in a RAC cluster required
more space for internal use by ASM than was available in the diskgroup.
Action: Delete unused files from the diskgroup or add additional disks to the
diskgroup and retry the operation.
ORA-15203: diskgroup string contains disks from an incompatible version of ASM
Cause: Diskgroup was created by an ASM instance with a higher compatibility
setting.
Action: Use an ASM instance with the appropriate software version to mount the
diskgroup.
ORA-15204: database version string is incompatible with diskgroup string
Cause: The COMPATIBLE parameter for the RDBMS instance is less than the value of
the compatible.rdbms attribute for the disk group.
Action: Update the COMPATIBLE parameter for RDBMS instance to a version greater
than or equal to compatible.rdbms version. The compatible attributes for diskgroups
cannot be lowered.
ORA-15205: requested mirror side unavailable
Cause: The requested mirror side of a block is either unallocated or allocated on a
disk that has been dropped from the diskgroup.
Action: Resubmit the request or try another mirror side.
ORA-15206: duplicate diskgroup string specified
Cause: A command specified the same diskgroup twice.
Action: Specify each diskgroup only once.

ORA-15210: conflicting or duplicate PERMISSION options
Cause: The PERMISSION clause contained the USER, GROUP, or OTHER keyword
more than once.
Action: Specify each keyword, at most, once.
ORA-15211: conflicting or duplicate OWNERSHIP options
Cause: The OWNERSHIP clause contained either the OWNER or the GROUP
keyword more than once.
Action: Specify each keyword, at most, once.
ORA-15212: missing or invalid OWNER or GROUP name
Cause: The command did not specify a valid name for either the OWNER or the
GROUP keyword.
Action: Specify a valid name for either the OWNER or the GROUP keyword.
ORA-15213: command operates on only one attribute
Cause: More than one disk group attribute was specified in the ALTER DISKGROUP
statement.
Action: Specify only one disk group attribute per ALTER DISKGROUP statement.
ORA-15214: missing or invalid attribute specification
Cause: The command did not specify a valid attribute name or a valid attribute value.
Action: Specify a valid attribute name and value pair.
ORA-15215: missing or invalid user name
Cause: The command did not specify a valid user name.
Action: Specify a valid user name.
ORA-15216: missing or invalid user group name
Cause: The command did not specify a valid user group name.
Action: Specify a valid user group name.
ORA-15217: missing or invalid timeout value after DROP AFTER
Cause: The command did not specify a valid timeout value after the DROP AFTER
clause.
Action: Specify a valid timeout value after the DROP AFTER clause.
ORA-15218: timeout value exceeded range
Cause: The OFFLINE timeout value exceeded the range of 0-136 years, inclusive. 136
years are 49674 days, 1192176 hours, and 71530560 minutes.
Action: Specify a timeout value within the range of 0-136 years, inclusive.
ORA-15219: conflicting or duplicate disk region options
Cause: The command contained one or more of the following: - both the HOT and the
COLD keywords - both the MIRRORHOT and the MIRRORCOLD keywords - the
HOT keyword more than once - the COLD keyword more than once - the
MIRRORHOT keyword more than once - the MIRRORCOLD keyword more than
once
Action: Specify either the HOT or the COLD keyword and either the MIRRORHOT or
the MIRRORCOLD keyword, at most, once.
ORA-12700 to ORA-19400 69-163
ORA-15220: invalid file attribute specification

Cause: The keyword UNPROTECTED, MIRROR, HIGH, FINE, or COARSE was
specified in a MODIFY FILE clause. These file attributes are immutable once a file is
created.
Action: Specify a disk region keyword; for example, HOT, COLD, MIRRORHOT, or
MIRRORCOLD.
ORA-15221: ASM operation requires compatible.asm of string or higher
Cause: The ASM operation specified requires a higher disk group attribute value for
compatible.asm.
Action: Set the disk group attribute compatible.asm to or above the requested version.
ORA-15222: ASM disk "string" is offline and cannot be renamed.
Cause: An attempt was made to rename a disk that is offline.
Action: Check the ASM disk name as specified in the command.
ORA-15223: conflicting disk operations for string
Cause: An attempt was made to ADD and DROP the specified ASM disk in the same
statement.
Action: Revise the statement to specify distinct ASM disks in the ADD disk and
DROP disk clauses.
ORA-15224: disk "string" is already provisioned for ASM
Cause: An attempt was made to label a disk that is already provisioned for ASM.
Action: Check the ASM disk name as specified in the command.
ORA-15225: label name 'string' is already in use
Cause: A LABEL SET command specified a label name that was already used by
another ASM disk.
Action: Select a different name for the label.
ORA-15226: label name 'string' is not used by ASM
Cause: A LABEL CLEAR command specified a label name that was not used by ASM.
Action: Select a different name for the label.
ORA-15227: could not perform label set/clear operation
Cause: An error occurred while setting/clearing the ASM label.
Action: Look at the underlying error(s) on the error stack. Check other messages in
the trace files for more information.
ORA-15230: diskgroup 'string' does not require the FORCE option
Cause: An attempt was made to MOUNT or DROP a disk group with the FORCE
option.
Action: MOUNT and DROP diskgroup with the FORCE option are only permitted if
the diskgroup cannot be mounted normally.
ORA-15231: advancing diskgroup compatibility would exclude connected clients
Cause: Disk group compatibility could not be advanced because connected clients
were at a lower compatibility than the target value.
Action: Make sure all connected clients are at target compatibility level or higher.
ORA-15232: cannot advance diskgroup compatibility due to offline disks

Cause: Disk group compatibilty could not be advanced because some disks are
offline.
Action: Retry the command after offline disks are dropped.
ORA-15233: cannot advance diskgroup compatibility due to [string]
Cause: Disk group compatibilty could not be advanced because of errors.
Action: Check the alert log for more information on the reason for the failure.
ORA-15234: target RDBMS compatibility (string) exceeds ASM compatibility
(string)
Cause: An attempt was made to advance RDBMS compatibility beyond the disk
group's ASM compatibility.
Action: Advance ASM compatibility before advancing RDBMS compatibility.
ORA-15235: diskgroup string mount mode conflicts with existing mount
Cause: The mode specified in the diskgroup mount command conflicted with the
mode in which it was mounted on some other instance.
Action: Specify a compatible mode in the diskgroup mount command.
ORA-15236: diskgroup string mounted in restricted mode
Cause: The specified diskgroup was mounted in restricted mode prohibiting client
access.
Action: Dismount the diskgroup and remount it in appropriate mode.
ORA-15237: invalid attribute string to CREATE DISKGROUP command
Cause: An invalid attribute was specified with the CREATE DISKGROUP command.
Action: Check the valid attributes for CREATE DISKGROUP command and specify a
valid one.
ORA-15238: string is not a valid value for attribute string
Cause: The specified value was not valid for the attribute.
Action: Check the attribute name and value.
ORA-15239: allocation unit size higher than string requires RDBMS compatibility
string
Cause: The allocation unit size requested exceeded the limit imposed by the RDBMS
compatibility setting.
Action: Use a smaller allocation unit size or specify a higher RDBMS compatibility
setting.
ORA-15240: attribute name string is invalid
Cause: The attribute name was not valid or was not recognized.
Action: Check the attribute name.
ORA-15241: attribute string is read only
Cause: The attribute value is read-only and cannot be changed.
Action: None. The attribute value cannot be changed.
ORA-15242: could not set attribute string
Cause: An error occurred while setting the attribute.
ORA-12700 to ORA-19400 69-165
Action: Look at the underlying error(s) on the error stack.

ORA-15243: string is not a valid version number
Cause: The given version number was invalid, or not valid in this context.
Action: Verify that the version number is valid and is appropriate for this command.
Check for additional errors reported.
ORA-15244: new compatibility setting less than current [string]
Cause: The compatibility setting was invalid. The compatibility setting can only be
advanced.
Action: Check the version number.
ORA-15245: ASM disk string is already being brought online
Cause: An attempt was made to bring online a disk that is already being brought
online.
Action: Change the ONLINE statement to exclude the disk.
ORA-15246: cannot bring ASM disk string both online and then offline in the same
statement
Cause: An attempt was made to bring the specified disk both online and offline in the
same statement.
Action: Revise the statement to either bring the disk online or take the disk offline.
ORA-15247: cannot specify both WAIT and NOWAIT options in the same
statement
Cause: An attempt was made to specify both WAIT and NOWAIT options in the
same statement.
Action: Revise the statement and include at most one option.
ORA-15248: ASM attributes feature not enabled
Cause: The ASM attributes feature was not enabled.
Action: Advance disk group ASM compatibility to version 11.1.0 or newer.
ORA-15249: could not locate ASM attribute string
Cause: The specified attribute could not be accessed.
Action: Check the attribute name and examine underlying error(s) on the error stack.
ORA-15250: insufficient diskgroup space for rebalance completion
Cause: The command attempted to reduce the available diskgroup space below the
current space used.
Action: Consult V$ASM_DISK to determine the space requirements for the diskgroup
contents, and repeat the command after making the required storage available.
ORA-15251: only restricted mount is allowed in the ASM instance
Cause: The ASM instance was started in restricted mode, and an attempt was made to
mount a diskgroup in non-restricted mode.
Action: Start the ASM instance in non-restricted mode and mount the diskgroup
again, or mount the diskgroup in restricted mode.
ORA-15252: user name 'string' does not exist in OS user dictionary
Cause: The specified user name was not a valid operating system user.
Action: Specify a valid operating system user.
ORA-15253: user group name 'string' exceeds limit of string characters

Cause: The length of the specified user group name exceeded the maximum limit.
Action: Reduce the length of the user group name to a value within the limit.
ORA-15254: user group 'string' already exists in disk group
Cause: The specified user group name already existed in the disk group.
Action: Specify a different user group name.
ORA-15255: user group 'string' does not exist in disk group 'string'
Cause: The specified user group name did not exist in the disk group.
Action: Specify a valid user group name.
ORA-15256: user 'string' is already a member of user group 'string'
Cause: The specified user was already a member of the specified user group.
Action: Specify either an alternate user or an alternate user group.
ORA-15257: exceeded string number of members per user group
Cause: The maximum number of members per user group was exceeded.
Action: Delete existing members of the user group to create space.
ORA-15258: user group entry number must be between string and string, inclusive
Cause: The specified user group entry number was beyond the acceptable range.
Action: Specify a valid value for the user group entry number.
ORA-15259: user 'string' is not a member of user group 'string'
Cause: The specified user was not a member of the specified user group.
Action: Specify either an alternate user or an alternate user group.
ORA-15260: permission denied on ASM disk group
Cause: An attempt was made to perform an operation on an ASM disk group without
the appropriate privileges.
Action: Ask the ASM administrator to perform the operation or grant the required
privileges.
ORA-15261: user 'string' already exists in disk group 'string'
Cause: The specified UID already existed in the disk group.
Action: Specify a different UID.
ORA-15262: user 'string' does not exist in disk group 'string'
Cause: The specified UID did not exist in the disk group.
Action: Specify a user with a valid UID.
ORA-15263: user name 'string' exceeds limit of string characters
Cause: The length of the specified user name exceeded the maximum limit.
Action: Reduce the length of the user name to a value within the limit.
ORA-15264: Operating system function returned error string
Cause: An operating system error occurred.
ORA-12700 to ORA-19400 69-167
ORA-15265: user identification number not in range of [string,string]

Cause: The operating system user identification number exceeded the maximum
value.
Action: Change the user identification number to a value within the accepted range.
ORA-15266: user identification number 'string' is not allowed
Cause: This user identification number is used internally by ASM.
Action: Please choose a different user identification number.
ORA-15268: internal Oracle file string already exists.
Cause: File was already in existence.
ORA-15269: group identification number not in range of [string,string]
Cause: The operating system group identification number exceeded the maximum
value.
Action: Change the group identification number to a value within the accepted range.
ORA-15270: disk string is not a quorum disk
Cause: The specified disk was not a quorum disk.
Action: Retry the operation without the quorum attribute for the disk.
ORA-15271: failgroup string is a quorum failgroup
Cause: The specified failgroup was a quorum failgroup.
Action: Retry the operation with the quorum attribute for the failgroup.
ORA-15272: failgroup string is not a quorum failgroup
Cause: The specified failgroup was not a quorum failgroup.
Action: Retry the operation without the quorum attribute for the failgroup.
ORA-15273: Could not create the required number of voting files.
Cause: The required number of voting files could not be created. See accompanying
messages for possible causes.
Action: See accompanying messages for possible actions.
ORA-15274: Not enough failgroups (string) to create voting files
Cause: The number of failgroups required for this redundancy were not present in the
diskgroup to create voting files.
Action: Retry the operation after creating new failgroup(s).
ORA-15275: Not enough contiguous space (string AUs) in disk string to allocate a
voting file
Cause: The specified disk did not have enough space to allocate a voting file on it.
Action: Ensure that there is at least 1 disk with the required space in atleast the
required number of failgroups for the diskgroup.
ORA-15276: ASM diskgroup string has cluster voting files
Cause: An attempt was made to drop a diskgroup that contained cluster voting files.
Action: Move the cluster voting files out of the diskgroup and retry the operation.
ORA-15277: disk string is a quorum disk

Cause: The specified disk was a quorum disk.
Action: Retry the operation with the quorum attribute for the disk.
ORA-15278: external redundancy diskgroup requires at least one regular disk
Cause: An attempt was made to create an external redundancy diskgroup with only
quorum disks.
Action: Specify atleast one regular disk to create an external redundancy diskgroup.
ORA-15279: user 'string' is currently being deleted
Cause: The specified user was in the process of being deleted and could not be used.
Action: Either abandon this operation or specify a different user.
ORA-15280: user 'string' owns existing files
Cause: An attempt was made to drop a user that still owns existing files.
Action: Specify the CASCADE option to drop the user and all of the owned files.
ORA-15281: not all specified disks were brought ONLINE
Cause: Some of the disks specified either experienced I/O errors while being brought
ONLINE, or were simultaneously brought OFFLINE or dropped in another session,
or were full.
Action: Query V$ASM_DISK or use ASMCMD LSDSK to determine which disks were
not brought ONLINE. Inspect any additional error messages and the alert log to
determine the exact cause. If some of the disks failed, either fix the cause of the
failures or drop the disks. If some of the disks are full, either free space in the disk
group or add new disks to the diskgroup.
ORA-15283: ASM operation requires compatible.rdbms of string or higher
Cause: The ASM operation specified requires a higher disk group attribute value for
compatible.rdbms.
Action: Set the disk group attribute compatible.rdbms to or above the requested
version.
ORA-15284: ASM terminated ALTER DISKGROUP ONLINE
Cause: None of the disks specified by ALTER DISKGROUP ONLINE could be
brought ONLINE.
Action: Inspect additional error messages and the alert log to determine why the
specified disks cannot be brought ONLINE.
ORA-15285: disk 'string' violates disk group attribute string
Cause: Including the specifed disk would violate a restriction imposed by the
specified disk group attribute.
Action: Retry the operation while omitting the offending disk or change the attribute.
ORA-15286: could not set disk group attribute string due to offline disks
Cause: The specified disk group attribute could not be set because the disk group
includes offline disks.
Action: Retry the operation after the offline disks in this disk group are dropped or
brought online.
ORA-12700 to ORA-19400 69-169
ORA-15287: could not set disk group attribute string due to incompatible disks
Cause: The specified disk group attribute could not be set because the disk group
includes disks that conflict with the new value.
Action: Retry the operation after dropping the conflicting disks in this disk group.
ORA-15288: disk(s) require disk group attribute string clause
Cause: Some of the disks specified by the command also require the specified disk
group attribute to be stated.
Action: Retry the command including an ATTRIBUTE clause for the required disk
group attribute. Alternatively, omit the disks that require setting the disk group
attribue. See the alert log for additional information on the disks that require setting
the disk group attribute.
ORA-15289: disk string is limited to string MB on instance string
Cause: An ALTER DISKGROUP ADD DISK or RESIZE DISK command specified a
disk with a size greater than the specified instance could use.
Action: Check the storage subsystem configuration on the specified node.
ORA-15290: operation not permitted on offline disk string
Cause: An attempt was made to specify an operation that is only permitted on disks
that are online. The specified disk was not online.
Action: Online the disk or wait for online to complete before retrying the operation.
ORA-15291: ASM could not add disk "string" to disk group "string"
Cause: An attempt was made to add a disk to a disk group while the distribution of
disks in failure groups was too uneven.
Action: Add or drop disks to or from failure groups to balance their distribution in all
failure groups and retry the operation.
ORA-15292: Disk name string is being used by another disk
Cause: The specified disk name could not be reused because an 11.1.0.6.0 or earlier
database instance had it cached in memory.
Action: Do one of the following - Specify a different name for the disk. - Wait for the
rebalance to complete successfully. - Identify the database instance with the problem
and shut it down before retrying the command.
ORA-15293: operation disallowed by ASM_POWER_LIMIT
Cause: This operation required data movement in order to complete successfully.
However, ASM_POWER_LIMIT was set to zero, thereby preventing this operation.
Action: Repeat the operation after setting ASM_POWER_LIMIT to a non-zero value.
ORA-15294: SYSASM privilege not allowed on database instance
Cause: The SYSASM privilege was not allowed on this database instance; it is allowed
only on an ASM instance.
Action: Use either the SYSDBA or the SYSOPER privilege.
ORA-15295: ASM instance software version string less than client version string
Cause: The ASM instance software version was less than the client version.
Action: Upgrade the ASM instance software. Check the alert log for more information
on the reason for the failure.
ORA-15298: possible lost disk write detected during crash recovery

Cause: ASM crash recovery read a block who's version was older than expected.
Action: None. End users will not see this error. ASM automatically traps this error
and attempts a fallback recovery.
ORA-15299: FINE striping not allowed for the Staleness Registry
Cause: An SQL command attempted to set the striping attribute of the ASM_STALE
template to FINE striping.
Action: Do not modify the striping attribute of the ASM_STALE template.
ORA-15300: File string is incompatible with this operation
Cause: The file type was incompatible with the operation.
Action: Use another file of the correct type.
ORA-15301: cannot change string of the open file 'string'
Cause: A SET OWNERSHIP or SET PERMISSION command was attempted on an
open file.
Action: Close the file and retry the SQL command.
ORA-15302: active use of files owned by user 'string' precludes its drop
Cause: A DROP USER command specified a user owning files that were in use.
Action: Close all files owned by this user.
ORA-15303: Voting files could not be created in diskgroup string due to small
Allocation Unit size
Cause: An attempt was made to create voting files in a diskgroup with a small
Allocation Unit size.
Action: Create voting files in a different diskgroup whose Allocation Unit size is at
least 1 mega byte.
ORA-15304: operation requires ACCESS_CONTROL.ENABLED attribute to be
TRUE
Cause: An attempt was made to run an operation that required the
ACCESS_CONTROL.ENABLED attribute to be set to TRUE, but its existing state was
FALSE.
Action: Set the ACCESS_CONTROL.ENABLED attribute to TRUE and retry the
operation.
ORA-15305: cannot operate on ASM internal files
Cause: An attempt was made to operate on Automatic Storage Management (ASM)
metadata used to manage the diskgroup.
Action: Check the specified ASM file name.
ORA-15306: ASM password file update failed on at least one node
Cause: A CREATE USER, ALTER USER, DROP USER, GRANT, or REVOKE
command failed on at least one node of the Automatic Storage Management (ASM)
cluster.
Action: Check the ASM alert logs for more information.
ORA-12700 to ORA-19400 69-171
ORA-15307: disk string not discoverable by CSS; diskgroup string has CSS voting
files
Cause: An attempt was made to add a disk which cannot be discovered by Cluster
Synchronization Services (CSS). CSS has voting files in the disk group and will not be
able to use the new disk if CSS cannot discover the disks.
Action: Update the Automatic Storage Management (ASM) disk string in the Grid
Plug and Play (GPnP) profile to include the specified disk and retry the operation.
Alternatively, migrate the CSS voting files out of the diskgroup and retry the
operation
ORA-15308: could not access ASM SPFILE in RDBMS instance
Cause: A relational database management system (RDBMS) instance attempted to
access an Automatic Storage Management (ASM) SPFILE.
Action: Connect to an ASM instance and reissue the command. Alternatively, specify
an RDBMS SPFILE.
ORA-15309: could not access database SPFILE in ASM instance
Cause: An Automatic Storage Management (ASM) instance attempted to access a
relational database management system (RDBMS) SPFILE.
Action: Connect to an RDBMS instance and reissue the command. Alternatively,
specify an ASM SPFILE.
ORA-15310: process terminated due to signal
Cause: A process was terminated as a result of a signal in the I/O path.
Action: Reconnect to the database or the ASM instance. If the process termination
resulted in instance termination, restart the instance.
ORA-15311: process terminated due to fenced I/O
Cause: A process was terminated because it was fenced from doing any more I/Os.
Action: Reconnect to the database or the ASM instance. If the process termination
resulted in instance termination, restart the instance.
ORA-15312: invalid file type
Cause: Automatic Storage Management (ASM) could not determine the type of file.
Action: The file specified is not supported with Automatic Storage Management
(ASM). Specify a supported file type for the operation.
ORA-15313: Oracle ASM disk string cannot be resized under string M
Cause: An Oracle ASM disk resize command specified a size that was less than the
size required to support the voting file present on the disk.
Action: Increase the size specified for the disk.
ORA-15315: Write errors in disk group string could lead to inconsistent ASM
metadata.
Cause: One or more failures occurred while writing ASM metadata to disk.
Action: Repair the hardware problem and remount the disk group. Check the
accompanying errors and alert log for the disks which reported the error.
ORA-15316: Previous client instance string has not fully exited.
Cause: One or more processes from a prior instantiation of this client were not fenced.
Action: Make sure all processes belonging to the client instance exited. Check the
client alert log and the trace file of the process that terminated the instance.
ORA-15317: user identification number 'string' does not exist in operating system
user dictionary
Cause: The specified user identification number did not belong to a valid operating
system user.
Action: Specify a valid operating system user.
ORA-15318: disks in disk group string cannot be resized
Cause: Execution of ASM Storage Reclamation Utility script was incomplete on the
specified disk group.
Action: Execute ASM Storage Reclamation utility on the disk group to complete the
operation.
ORA-15319: ownership assignment of files to user 'string' precludes its drop
Cause: A DROP USER command specified a user currently being assigned as the
owner of one or more files with a SET OWNERSHIP command.
Action: Wait for the SET OWNERSHIP command to complete and then retry the
DROP USER command
ORA-15320: cannot drop user 'string' that has been assigned as the owner of one or
more open files
Cause: A SET OWNERSHIP command assigned this user as the owner of one or more
files which were open at the time of assignment, and hence this user cannot be
dropped due to possible inconsistencies in file ownerships.
Action: Restart all ASM client instances of the cluster in a rolling manner.
ORA-15321: cannot set attribute with connected clients
Cause: The disk group attribute could not be set because there were connected clients.
Action: Shut down connected clients and retry the command. Query the V
$ASM_CLIENT fixed view in an ASM instance or use ASMCMD LSOF to list active
clients.
ORA-15322: cannot drop the owner 'string' of user group 'string' in disk group
'string'
Cause: An attempt was made to drop the owner of a user group from the group's
member list.
Action: Specify a user group member who is not the owner of the user group.
ORA-15323: ASM password update has failed on local node
Cause: A CREATE USER, ALTER USER, DROP USER, GRANT, or REVOKE
command failed on the local node of the Automatic Storage Management (ASM)
cluster.
Action: Check the ASM alert logs for more information.
ORA-15324: requested operation is not allowed on the password file string
Cause: An attempt was made to run an operation that is not supported on password
files.
Action: Specify a new file name or a file with the correct file type and retry the
operation.
ORA-12700 to ORA-19400 69-173
ORA-15325: file string is not a valid password file

Cause: An attempt was made to open a file that had a type different from the
password file.
Action: Specify correct password file name and retry the operation.
ORA-15326: specified input string is a not an ASM file
Cause: The attributes could not be obtained as the specified input is either a disk
group or a directory.
Action: Specify a valid Automatic Storage Management (ASM) file name.
ORA-15327: remote ASM is not enabled
Cause: An operation was requested that requires remote ASM to be enabled.
Action: Enable remote ASM.
ORA-15328: user identification string 'string' exceeds limit of string characters
Cause: The user identification string provided for this operation exceeded the
maximum number of characters allowed.
Action: Provide a user identification string of shorter length.
ORA-15329: cluster identification string 'string' exceeds limit of string characters
Cause: The cluster identification string provided for this operation exceeded the
maximum number of characters allowed.
Action: Provide a cluster identification string of shorter length.
ORA-15330: ASM user name format requires COMPATIBLE.ASM of string or
higher
Cause: The ASM user name format specified requires a higher disk group attribute
value for COMPATIBLE.ASM.
Action: Set the disk group attribute COMPATIBLE.ASM to or above the requested
version.
ORA-15331: ASM proxy instance ORACLE_SID string does not start with string
Cause: The ASM proxy instance was started with an invalid ORACLE_SID prefix.
Action: Start the ASM proxy instance with an ORACLE_SID that begins with the
correct prefix.
ORA-15332: ASM proxy instance cannot connect to an ASM server
Cause: The ASM proxy instance could not find an ASM server to connect to during
startup.
Action: Verify that an ASM server instance is running and accessible in the cluster
and restart the proxy instance.
ORA-15333: disk is not visible on client instance
Cause: An ALTER DISKGROUP ADD DISK statement specified a disk that could not
be discovered by all ASM client instances.
Action: Check the ASM alert logs for more information. Check operating system
permissions for the device and the storage subsystem configuration.
ORA-15334: VUBG process terminated with error
Cause: The volume background process terminated with error.
ORA-15335: ASM metadata corruption detected in disk group 'string'

Cause: A corruption was detected reading a block. It may be recoverable.
Action: The corruption could be the result of a storage problem, a configuration issue,
or a software bug. Check the alert log for the result of the recovery attempt. If
unsuccessful, contact Oracle Support Services with the incident information.
ORA-15336: STRIPE_WIDTH cannot be set when STRIPE_COLUMNS equals 1
Cause: An ADD VOLUME command specified a STRIPE_COLUMNS equal to 1 and
specified the STRIPE_WIDTH argument.
Action: If striping is required, set STRIPE_COLUMNS to greater than 1. If striping is
not required, do not set STRIPE_WIDTH.
ORA-15337: invalid or missing database name
Cause: You did not specify a valid database name for this command.
Action: Specify a valid database name.
ORA-15338: ASM client instance string reconnection refused
Cause: The client was not found as an orphaned client and hence is not a legitimate
candidate to reconnect to Oracle ASM.
Action: Shut down and restart the remote client to be considered as a new client in the
cluster.
ORA-15339: ASM client instance string has been fenced by ASM
Cause: Oracle ASM has already fenced this client.
Action: Shut down and restart the remote client to be considered as a new client in the
cluster.
ORA-15340: unable to create Client Cluster 'string'
Cause: Creation of the Client Cluster failed.
information on the reason for the failure, as well as checking the accompanying error
messages.
ORA-15341: unable to delete Client Cluster 'string'
Cause: Deletion of the Client Cluster failed.
information on the reason for the failure, as well as checking the accompanying error
messages.
ORA-15343: Feature string ASM is not enabled
Cause: An operation was requested that requires Oracle Flex ASM to be enabled.
Action: Enable Oracle Flex ASM.
ORA-15344: client string not found
Cause: The specified Oracle ASM client was not registered with this instance.
Action: Check the alert logs and trace files of the client for more information on the
reason for the failure, as well as the accompanying error messages.
ORA-15345: disconnected client instance(s) detected
Cause: One or more ASM client instances were not connected to an ASM instance.
ORA-12700 to ORA-19400 69-175
Action: Check that all of the ASM client instances are connected to an ASM instance
ORA-15346: process attempting to identify or create ASM file string was aborted
Cause: The client process attempting to identify or create the ASM file terminated or
was interrupted.
Action: Correct the cause of the process interruption and retry the operation.
ORA-15347: logical block size string of ASM file 'string' is too small for disk group
sector size string
Cause: An attempt was made to create a file on ASM whose logical block size was less
than the sector size for the disk group.
Action: Check if the system configuration has changed. Correct the error and retry the
operation.
ORA-15348: ASMLIB misconfiguration error [string]
Cause: ASMLIB was found in more than one location.
Action: Check the configuration of ASMLIB and ensure that only one library is
configured.
ORA-15349: failed to set or get AFD_DISKSTRING parameter
Cause: The operation failed because Oracle Local Repository (OLR) was not available.
Action: Check that Oracle Clusterware is properly configured.
ORA-15350: invalid SYS_ASMFD_PROPERTIES parameter
Cause: The parameter passed in for SYS_ASMFD_PROPERTIES was invalid.
Action: Pass in the correct parameter. Refer to the product documentation for a list of
allowed parameter values.
ORA-15351: I/O request issued to a sparse grid disk failed because the disk was out
of space.
Cause: The sparse grid disk was out of space.
Action: Add more space to the disk group by adding more disks or add more space to
existing disks by resizing them.
ORA-15352: invalid client name string specified
Cause: The client name passed in was invalid.
Action: Pass in a valid client name. The valid client name is of format instance
name:dbunique name:cluster name or instance name:dbunique name
ORA-15353: disk 'string' cannot be added to disk group 'string'
Cause: The disk type did not match the disk group sparse type.
Action: Make sure the disk type matches the disk group sparse type.
ORA-15354: failed to format grid disk "string"
Cause: The grid disk format command failed.
Action: Check the grid disk logs and take corrective actions.
ORA-15357: Can not create file "string" on a sparse disk group
Cause: An attempt was made to create fine-grained striping files on sparse disk
groups. Fine-grained striping files cannot be created on sparse disk groups.
Action: Create the file on a regular disk group, or create a coarse-grained striping file
on a sparse disk group.
ORA-15358: query for materialized space to sparse grid disk "string" of disk group
"string" has failed
Cause: The query for materialized space to the cell server has failed.
Action: Check the ASM and cell alert logs and take corrective actions.
ORA-15359: could not perform label scan operation
Cause: An error occurred while scanning for ASM label.
Action: Look at the underlying errors on the error stack. Check other messages in the
trace files for more information.
ORA-15360: could not perform label filter operation
Cause: An error occurred while setting AFD filter status.
Action: Look at the underlying errors on the error stack. Check other messages in the
trace files for more information.
ORA-15361: unable to find Client Cluster 'string'
Cause: Looking up of the Client Cluster failed.
Action: Execute the 'asmcmd lscc' command to list all of the configured Client
Clusters. If the Client Cluster listed in the message is not present, it might have been
forcibly deleted. Refer to the product documentation for more information. If the
Client Cluster listed in the message was present, contact Oracle Support Services.
ORA-15362: invalid cluster name 'string' specified
Cause: An invalid cluster name was supplied.
ORA-15363: invalid version number 'string' specified
Cause: The command did not specify a valid version number.
Action: Correct the version number in the command. It should be of the form
v#.#.#.#.# or other forms with fewer numbers delimited by a period.
ORA-15364: Client Cluster version string is incompatible with Storage Server
version string
Cause: The specified Client Cluster version was not supported by the Storage Server.
Action: Upgrade or downgrade the Storage Server to a version that is compatible with
Client Cluster and retry the operation. Install a Client Cluster using a supported
version. Refer to product documentation for a complete list of supported releases.
ORA-15365: Client Cluster 'string' already configured
Cause: The specified Client Cluster was already configured.
Clusters. Reexecute the command with a Client Cluster name that has not already
been configured.
ORA-12700 to ORA-19400 69-177
ORA-15366: unable to delete configuration for Client Cluster 'string' because the
directory 'string' was not empty
Cause: Deleting the Client Cluster configuration failed because some files were
present.
Action: Deinstall the Client Cluster and rerun the command. If the command fails
again, execute the 'asmcmd rmcc <client_cluster_name> -f' command to force deletion
of the configuration for the Client Cluster.
ORA-15367: Client Cluster 'string' not configured
Cause: The specified Client Cluster was not configured.
Clusters. Reexecute the command with a Client Cluster name that is configured.
ORA-15368: Oracle Cluster Registry operation failed with error string.\nstring
ORA-15369: OCI invalid handle string
Cause: An Oracle Call Interface (OCI) call returned the OCI_INVALID_HANDLE
return code and did not store the error on the stack.
ORA-15371: The command is not supported on a Client Cluster.
Cause: An attempt was made to run a command that is not supported on a Client
Cluster.
Action: Rerun the command on the Storage Server.
ORA-15400: not running on supported ASM appliance
Cause: An attempt was made to initialize the server code as an appliance when it was
not running a supported appliance configuration.
Action: Check the appliance configuration and retry the operation.
ORA-15401: command not supported on ASM appliance 'string'
Cause: An attempt was made to run an operation that is not supported by the
specified appliance.
Action: Check the documentation to see which operations are allowed or disallowed
for the specified appliance.
ORA-15402: insufficient number of disks to support ASM appliance 'string'
Cause: An attempt was made to do an operation that resulted in insufficient number
of disks required for the specified appliance.
Action: Check the appliance configuration and retry the operation after inserting
disks in the appropriate slots.
ORA-15403: unable to read an ASM appliance configuration file
Cause: Oracle ASM was unable to read an appliance configuration file.
Action: Check the operating system error messages to determine the identity of the
configuration file. Then, fix the configuration file.
ORA-15404: Oracle ASM could not add disk "string" to disk group "string" on
appliance string
Cause: There were too many dropping or offline disks in the specified disk group.
Action: Wait for the drop and rebalance operations to complete, or online the offline
disks and wait for the online to complete. Then, retry the operation.
ORA-15405: Slot string in Oracle ASM appliance 'string' contains more than one
disk
Cause: An attempt was made to add a disk to a slot in the ASM appliance that already
had a disk (possibly OFFLINE) associated with it.
Action: Use FORCE to drop the disk that exists in the specified slot. Then, retry the
operation.
ORA-15406: ASM disk string is being replaced.
Cause: An attempt was made to either online or replace a disk that was already being
replaced, probably by another instance.
Action: Change the ONLINE statement to exclude the disk.
ORA-15407: Disk specification 'string' matches multiple disks.
Cause: More than one disk is discovered matching the specified disk string.
Action: Change the disk string to specify one and only one disk.
ORA-15408: Replacement disk 'string' for 'string' must be at least string MB.
Cause: The replacement disk must be at least of the same size of the old disk.
Action: Use a larger physical disk to replace.
ORA-15409: All disks in disk group string are not of the same type.
Cause: An attempt was made to add disks of a different type to the disk group under
appliance mode.
Action: Check if all the disks in the disk group are of the same type. Do not add flash
and hard disks to the same disk group.
ORA-15410: Disks in disk group string do not have equal size.
Cause: The disks in the disk group were not of equal size.
Action: Ensure that all disks in the disk group are of equal size. If adding new disks to
the disk group, their size must be equal to the size of the existing disks in the disk
group. If resizing, all disks in the disk group must be resized to the same size.
ORA-15411: Failure groups in disk group string have different number of disks.
Cause: An attempt was made to enable appliance mode with a different number of
disks in each failure group.
Action: Check if all failure groups have an equal number of disks and try again.
ORA-15412: Operation on disk group string is incompatible under appliance mode.
Cause: An attempt was made to do an operation that resulted in dropping all disks in
a failure group or creating a new failure group.
Action: Disable appliance mode, perform the operation and reenable appliance mode.
WARNING: To reenable appliance mode, ensure the following constraints are met: *
There are a sufficient number of disks in each failure group. * All failure groups have
an equal number of disks. * There are no offline disks in the disk group. * Every disk
ORA-12700 to ORA-19400 69-179
in the disk group is of the same type (flash or hard disk). * All disks in the disk group
have an equal size.
ORA-15413: Appliance mode is disabled.
Cause: Appliance mode could not be set because it was explicitly disabled.
Action: Enable appliance mode and appliance partnering parameters.
ORA-15414: Appliance mode requires at least string failure groups and either string
or string disks in all failure groups.
Cause: Appliance mode could not be enabled because it did not meet the minimum
requirements.
Action: Check if there are sufficient failure groups and a sufficient number of disks in
each failure group.
ORA-15415: could not retrieve appliance properties for disk group string
Cause: Some of the appliance properties were invalid. This could be due to a cell
software downgrade after setting the 'appliance.mode' attribute.
Action: Check the cell software on all of the cells or disable appliance mode.
ORA-15416: ASM disk string in disk group string is offline.
Cause: An offline disk prevented the current ADD or DROP operation.
Action: Drop the offline disk or online the offline disk or disable appliance mode.
ORA-15418: Appliance mode is not supported for compatible.asm string.
Cause: Appliance mode could not be enabled for the current value of the
compatible.asm attribute.
Action: Disable appliance mode if it is enabled or advance compatible.asm to a
version that supports appliance mode.
ORA-15419: disk group string is not mounted in restricted mode
Cause: The specified disk group was not mounted in restricted mode prohibiting the
requested operation.
Action: Dismount the disk group, remount it in restricted mode and retry the
operation.
ORA-15420: Operation on disk group string is disabled.
Cause: The current operation could not be completed because the disk group is in the
middle of an appliance migration.
Action: Wait for the migration to complete and then retry the command.
ORA-15440: VIO0 process terminated with error
Cause: A volume IO background process terminated with error.
Action: Wait for the process to restart.
ORA-15450: invalid volume name specifier
Cause: The volume name specified was invalid
Action: Specify a valid volume name.
ORA-15451: missing or invalid volume size specifier
Cause: The volume size specified was invalid.
Action: Specify a valid volume size.
ORA-15452: missing or invalid stripe width specifier

Cause: The volume stripe width specified was invalid.
Action: Specify a valid volume stripe width.
ORA-15453: invalid STRIPE_COLUMNS specifier
Cause: An ADD VOLUME command did not specify a valid number of stripe
columns.
Action: Specify a valid number of stripe columns.
ORA-15454: ALTER DISKGROUP ALL cannot use single volume names
Cause: An ALTER DISKGROUP ALL command specified a single volume or a list of
volumes
Action: Use the ALL keyword when specifying volumes on multiple diskgroups.
ORA-15455: FORCE option cannot be used when specifying ALL volumes
Cause: The FORCE option was used to disable ALL volumes.
Action: Use FORCE option to disable one volume at a time.
ORA-15456: missing or invalid volume usage specifier
Cause: The command did not specify a valid volume usage string.
Action: Specify a valid volume usage string with alphanumeric characters.
ORA-15457: first letter of the volume name is not alphabetic
Cause: A volume name was specified with a nonalphabetic first character.
Action: Set the first character of the volume name to be alphabetic.
ORA-15458: invalid character in volume name
Cause: A volume name was specified with an invalid character.
Action: Use a volume name with only alphanumeric characters.
ORA-15459: STRIPE_WIDTH of string is not a power of two
Cause: An ADD VOLUME command specified a STRIPE_WIDTH that was not a
power of two.
Action: Select a STRIPE_WIDTH that is a power of two; for example, 4K, 8K, etc.
ORA-15460: volume name 'string' is already in use
Cause: An ADD VOLUME command specified a volume name that was already used
by another volume.
Action: Select a different name for the volume.
ORA-15461: STRIPE_WIDTH of string bytes is less than the minimum of string
bytes
Cause: An ADD VOLUME command specified a STRIPE_WIDTH that was too small.
Action: Select a larger STRIPE_WIDTH.
ORA-15462: STRIPE_WIDTH of string bytes is greater than the maximum of string
bytes
Cause: An ADD VOLUME command specified a STRIPE_WIDTH that was too large.
Action: Select a smaller STRIPE_WIDTH.
ORA-12700 to ORA-19400 69-181
ORA-15463: volume size of stringK is less than the minimum of stringM

Cause: The volume size specified was too small.
Action: Select a larger volume size.
ORA-15464: STRIPE_COLUMNS of string is greater than the maximum of string
Cause: An ADD VOLUME command specified a STRIPE_COLUMNS that was that
was too large.
Action: Select a smaller STRIPE_COLUMNS value.
ORA-15465: STRIPE_COLUMNS of string is less than the minimum of string
Cause: An ADD VOLUME command specified a STRIPE_COLUMNS that was too
small.
Action: Select a larger STRIPE_COLUMNS value.
ORA-15466: volume 'string' in disk group 'string' does not exist
Cause: The command specified a volume name that does not exist.
Action: Ensure a valid volume name is used.
ORA-15467: volume operation is already in progress
Cause: Another command was currently operating on a volume.
Action: Wait a short time before retrying the command.
ORA-15468: volume 'string' in diskgroup 'string' is currently being accessed
Cause: An attempt was made to communicate with the volume driver. The volume
was being accessed by another application and, therefore, could not be changed.
Action: Shut down all applications that might be accessing this volume and then retry
the command.
ORA-15469: VBG process terminated with error
Cause: A volume background process terminated with error.
Action: Wait for process to restart.
ORA-15470: VDBG process terminated with error
Cause: The volume driver background process terminated with error.
ORA-15471: volume redundancy incompatible with disk group redundancy
Cause: An ADD VOLUME command specified a volume redundancy that was
incompatible with the redundancy of the disk group.
Action: Specify a valid volume redundancy. An unprotected redundancy volume
cannot be added to a normal or high redundancy disk group, and a mirror or high
redundancy volume cannot be added to an external redundancy disk group.
ORA-15472: volume library cannot be loaded. Platform may not support volume
creation.
Cause: The volume library could not be loaded. Either the platform does not support
volume operations, or there is a problem with the library.
Action: Ensure that the platform supports volumes. If the platform does support
volumes, check the alert log for library loading failure information.
ORA-15473: access to a volume's storage through an unsupported interface

Cause: An attempt was made to access or modify a volume's storage through an
unsupported interface.
Action: Use supported interfaces for access to volume devices.
ORA-15474: volume name is greater than string characters
Cause: An ADD VOLUME command specified a volume name that was too long.
Action: Select a smaller volume name.
ORA-15475: usage string is greater than string characters
Cause: The usage string specified was too long.
Action: Select a smaller usage string.
ORA-15476: ACFS volumes must be resized with the 'acfsutil size' operating
system command.
Cause: An attempt was made using SQL to resize an ADVM volume that contains an
ACFS file system.
Action: Use the 'acfsutil size' operating system command to resize the volume.
ORA-15477: cannot communicate with the volume driver
Cause: An attempt was made to communicate with the volume driver.
Action: Check that the ASM volume driver is loaded. If so, check the alert log to
identify the reason for failure and take necessary action to prevent such failures in the
future.
ORA-15478: ACFS process terminated with error
Cause: The ACFS background process terminated with error
Action: Wait for process restart
ORA-15479: ASM diskgroup does not support volumes
Cause: Volumes were not supported. A common example is having disks, such as
NFS, in the diskgroup that are not supported by volumes.
Action: Remove unsupported disks in the diskgroup.
ORA-15480: error reported in the ASM volume driver
Cause: An error was reported in the ASM volume driver.
Action: Check the operating system log files to identify the reason for the failure and
take necessary action to prevent such failures in the future.
ORA-15481: missing or invalid volume mountpath specifier
Cause: A invalid volume mountpath string was specified.
Action: Specify a valid volume mountpath string with alphanumeric characters.
ORA-15482: failed to create/remove device file for volume string on diskgroup
string
Cause: Improper driver installation.
Action: Check the alert log for device file creation failure information. Reload the
driver using the supported installation method.
ORA-15483: volume driver version is not compatible with the ASM instance
Cause: The version of the ASM volume driver was not supported by ASM.
ORA-12700 to ORA-19400 69-183
Action: Update the volume driver or the ASM instance.

ORA-15484: volume 'string' contains string error(s)
Cause: Errors were returned by the ALTER DISKGROUP CHECK VOLUME
command.
ORA-15485: number of volumes in diskgroup exceeds the maximum of string
Cause: A volume was added on a diskgroup that already contained the maximum
number allowed.
Action: Remove volumes on the diskgroup.
ORA-15486: internal error while altering volume
Cause: An internal ASM error occurred while altering a volume.
Action: See the alert log for details of the error.
ORA-15487: cannot shutdown the ASM instance with an open ASM volume
Cause: One or more ASM volumes were found to be open during shutdown.
Action: Close the ASM volume and retry the shutdown.
ORA-15488: volume string is open on instance string
Cause: ASM volume was not closed prior to instance termination on node specified.
Action: Close the ASM volume either via unmount or node restart and retry the
operation
ORA-15489: conflicting volume already open on this node
Cause: An ASM volume was not closed prior to instance shutdown on node specified.
It is conflicting with the volume that is to be enabled.
Action: Close the ASM volume either via unmount or node restart and retry the
operation.
ORA-15490: not all instances could add/drop the volume
Cause: The ASM volume cannot be added/dropped on all instances.
Action: See the alert log for the reason the volume could not be added/droped.
ORA-15491: volume redundancy conflicts with disk region options
Cause: Non-mirrored volumes erroneously contained the MIRRORHOT or
MIRRORCOLD keyword.
Action: Remove the MIRRORHOT or MIRRORCOLD keywords from non-mirrored
volumes.
ORA-15492: command or option incompatible with ASM volumes
Cause: An attempt was made to use a feature which is not compatible with existing
ASM volumes. A common example is adding a disk to the diskgroup that is
unsupported by ASM volumes.
Action: Omit the option from the command.
ORA-15493: target ADVM compatibility (string) exceeds ASM compatibility
(string)
Cause: An attempt was made to advance ADVM compatibility beyond the disk
group's ASM compatibility.
Action: Advance ASM compatibility before advancing ADVM compatibility.
ORA-15494: compatible.advm must be string or higher

Cause: An attempt was made to set the ADVM compatibility to a version that was
lower than the minimum supported.
Action: Set ADVM compatibility to at least the minimum supported version.
ORA-15495: ASM operation requires compatible.advm of string or higher
Cause: The ASM operation specified required a higher disk group attribute value for
compatible.advm.
Action: Set the disk group attribute compatible.advm to or above the requested
version.
ORA-15496: volume size is greater than the maximum of stringT
Cause: The volume size specified was too large.
Action: Select a smaller volume size.
ORA-15497: diskgroup uses a sector size that is incompatible with volumes
Cause: The diskgroup used a sector size that was not 512 bytes.
Action: Create the volume in a diskgroup with a sector size of 512 bytes.
ORA-15498: Volume name 'string' would collide with existing volume(s) 'string
string'.
Cause: A volume name was specified that would conflict with existing volume
device(s). A volume '<vol_name>-<dg_num>' is the name of the block device.
Additionally, a raw device named 'r<vol_name>-<dg_num>' is also created. Since
that name already existed, a name collision occurred.
Action: Choose another name for the volume (no leading 'r' is recommended).
ORA-15499: Volume Membership (VMB) process terminated with error
Cause: The volume driver background process terminated with error.
ORA-15501: cannot start workload capture on instance string
Cause: Given instance encountered unexpected errors while trying to start the
workload capture.
Action: Check the alert log and other diagnostics in the given instance to diagnose the
problem.
ORA-15502: cannot stop workload capture on instance string
Cause: Given instance encountered unexpected errors while trying to stop the
workload capture.
problem.
ORA-15503: cannot startup instance when procedures in
"DBMS_WORKLOAD_CAPTURE" or "DBMS_WORKLOAD_REPLAY" are in the
middle of their execution
Cause: The new instance could not be started because the database was executing a
procedure in either the DBMS_WORKLOAD_CAPTURE or
DBMS_WORKLOAD_REPLAY package.
Action: Start the new instance after such procedures in the given packages have
finished execution.
ORA-12700 to ORA-19400 69-185
ORA-15504: cannot start workload capture because instance string not present in
RESTRICTED SESSION mode
Cause: The NO_RESTART_MODE option in
DBMS_WORKLOAD_CAPTURE.START_CAPTURE was FALSE, therefore all the
active instances were expected to be in the RESTRICTED SESSION mode.
Action: Start all instances using STARTUP RESTRICT or execute ALTER SYSTEM
ENABLE RESTRICTED SESSION on all active instances before issuing
DBMS_WORKLOAD_CAPTURE.START_CAPTURE.
ORA-15505: cannot start workload capture because instance string encountered
errors while accessing directory "string"
Cause: Given instance could not access the specified CAPTURE directory or the
specified CAPTURE directory already had a workload capture in it.
Action: Provide a directory object that is valid, empty and accessible from all the
instances in the database cluster.
ORA-15506: cannot prepare instance string for replay
Cause: Given instance encountered unexpected errors while trying to prepare for a
workload replay.
problem.
ORA-15507: cannot start workload replay on instance string
Cause: Given instance encountered unexpected errors while trying to start a
workload replay.
problem.
ORA-15508: cannot cancel workload replay on instance string
Cause: Given instance encountered unexpected errors while trying to cancel a
workload replay.
problem.
ORA-15509: workload replay has been cancelled
Cause: Workload replay was cancelled.
Action: Restart the workload replay.
ORA-15510: cannot perform operation when "STATISTICS_LEVEL" is "BASIC"
Cause: The STATISTICS_LEVEL initialization parameter was set to BASIC.
Action: Change the STATISTICS_LEVEL initialization parameter setting to either
TYPICAL or ALL.
ORA-15511: cannot process workload capture because no user sessions were
recorded
Cause: No user sessions were recorded in the given workload capture. Processing this
capture failed because no user workload was captured.
Action: Capture a workload in which at least one user session connects and performs
some operations.
ORA-15512: directory "string" does not contain a valid processed workload capture
Cause: One or more files created by
DBMS_WORKLOAD_REPLAY.PROCESS_CAPTURE were missing.
Action: Process the workload capture using
DBMS_WORKLOAD_REPLAY.PROCESS_CAPTURE and then retry the command.
ORA-15513: cannot access the input directory
Cause: Given input directory is either invalid or inaccessible.
Action: Verify that the input directory is valid and accessible and then retry the
command.
ORA-15514: cannot find a match for the remote procedure call during replay
Cause: The corresponding PL/SQL program was either dropped or modified.
Action: Verify that the corresponding PL/SQL program is defined the same way
during replay as it was defined during workload capture.
ORA-15515: error while replaying remote procedure call: "string.string.string"
Cause: Error encountered during the replay of a remote procedure call.
Action: Correct the cause of the preceding error and restart workload replay.
ORA-15516: parallel preprocessing worker hit error ORA-string
Cause: One of the parallel preprocessing workers died unexpectedly while processing
the workload.
Action: Find the root cause or simply preprocess the workload using only one
process.
ORA-15517: cannot start parallel preprocessing worker
Cause: One of the parallel preprocessing workers could not be started.
process.
ORA-15518: parallel preprocessing encountered an unexpected error
Cause: An unexpected error occured during parallel preprocessing.
process.
ORA-15519: cannot access database link "string" because it is disabled
Cause: For security considerations, access to external databases via database links
were disabled during workload replay.
Action: Use advanced parameter for Database Replay to enable database links during
workload replay.
ORA-15520: Directory is corrupted. Two WMD files are found at "string" and
"string"
Cause: Two WMD files were found in the directory.
Action: Check that the WMD files in capture directory were not modified, moved,
duplicated or deleted.
ORA-15521: failed to create file "string" during workload processing
Cause: An attempt was made to create a file during workload processing without the
proper file permissions.
ORA-12700 to ORA-19400 69-187
Action: Correct the file permissions and try again.

ORA-15522: failed to generate a workload capture subset: "string"
Cause: An attempt to generate a workload capture subset failed. Possible reasons are
included in the error message.
Action: Correct the issue and try again.
ORA-15551: workload replay client cannot connect to database server
Cause: The server connection identifier was invalid.
Action: Restart the client with correct server connection identifier.
ORA-15552: workload replay client cannot login to database server
Cause: 1) the replay client used an invalid username or password; 2) the replay user
does not have the privilege to switch user; 3) the recorded username does not exist in
the replay database.
Action: 1) restart replay client with correct username and password 2) grant user
switching prvilege to the replay user 3) verify whether the replay database was
restored properly
ORA-15553: workload replay client cannot execute the
DBMS_WORKLOAD_REPLAY package
Cause: Workload Replay Client's replay user did not have EXECUTE permission on
the DBMS_WORKLOAD_REPLAY package.
Action: Grant execute permission on the DBMS_WORKLOAD_REPLAY package to
replay user and restart the Workload Replay Client.
ORA-15554: cannot start workload replay client because the database server is not
in PREPARE mode
Cause: The Workload Replay Client could not connect to the database server because
the database server was not in the PREPARE mode.
Action: Put the database in PREPARE mode by using
DBMS_WORKLOAD_REPLAY.PREPARE_REPLAY, and restart the Workload
Replay Client.
ORA-15555: workload replay client encountered unexpected error: "string"
Cause: Workload Replay Client encountered an unexpected error.
Action: Check the Workload Replay Client's log files and the database server alert log
to diagnose the problem.
ORA-15556: invalid input specified to the workload replay client; type 'wrc
HELP=Y' for help
Cause: Invalid input was specified.
Action: Use the Workload Replay Client's HELP=Y option to know more about valid
input options.
ORA-15557: workload replay client cannot access the replay directory or the
database version do not match the preprocessing one
Cause: The Workload Replay Client could not access the directory that contained the
workload to be replayed, or the workload was preprocessed by a different version of
the database.
Action: Restart the workload replay after specifying the correct replay directory, or
preprocess it with the correct database.
ORA-15558: replay thread encountered unexpected error

Cause: A single replay thread got disconnected from the server due to an unexpected
error.
Action: Check the Workload Replay Client's log files and the database server alert log
to diagnose the problem.
ORA-15559: workload replay client cannot open workload capture file
Cause: The Workload Replay Client could not access one or more workload capture
files from the replay directory.
Action: Restart the workload replay after copying all the workload capture files to the
replay directory.
ORA-15560: workload replay client cannot access the work directory
Cause: The Workload Replay Client could not access the work directory to write log
files for debug information.
Action: Restart the Workload Replay Client after specifying the correct work
directory.
ORA-15561: workload replay client cannot connect to the remapped connection
with conn_id : string
Cause: The specified connection is invalid or the specified host is inaccessible.
Action: Test the specified connection using other methods and redefine the
connection remapping, if necessary. Consult the view
DBA_WORKLOAD_CONNECTION_MAP to inspect connection remappings.
ORA-15562: workload replay client cannot read the
DBA_WORKLOAD_CONNECTION_MAP view
Cause: The DBA_WORKLOAD_CONNECTION_MAP view did not exist or was not
accessible.
Action: Re-create the workload capture and replay views. For additional information,
see the documentation.
ORA-15563: workload replay client cannot spawn new threads
Cause: The Workload Replay Client does not have enough resource (CPU or memory)
to spawn new threads.
Action: Restart the workload replay after allocating more resource (CPU and
memory) to the Workload Replay Client or use more hosts as replay clients to drive
the workload.
ORA-15564: contents of the replay directory provided to the workload replay client
do not match with the replay directory provided to the database server
Cause: The processed workload capture files given to the workload replay client
directory did not match the contents of the replay directory given as input to
DBMS_WORKLOAD_REPLAY.INITIALIZE_REPLAY.
Action: Provide the same processed workload capture files to both the database
server and all the workload replay clients and restart the replay. If the same workload
capture files were processed more than once, provide a copy of the latest processed
workload capture files to all the workload replay clients and the database server.
ORA-15566: workload replay client cannot replay user call in the current version
Cause: The workload replay client encountered a user call in the captured workload
that was not supported for replay in the current version.
ORA-12700 to ORA-19400 69-189
Action: Look in the DBA_WORKLOAD_REPLAY_DIVERGENCE view for details

about the call that encountered this error. Refer to the documentation for more details
on the types of workload that are not supported in the current version.
ORA-15567: replay user string encountered an error during a sanity check
Cause: The replay user encountered an error when accessing internal objects for
Database Replay or switching user.
Action: Set up the replay user appropriately at the replay database. Make sure the
replay user can access SYS-owned objects and has BECOME USER privilege.
ORA-15568: login of user string during workload replay failed with ORA-string
Cause: The recorded user did not exist in the replay database or encountered other
problems during log in.
Action: Check the returned error number and set up the recorded user appropriately
at the replay database.
ORA-15569: timeout encountered during the replay of a recorded user call
Cause: The replay of a recorded user call was terminated since it was significantly
slower than the workload capture.
Action: Find the root cause for the performance issue. Or, use
DBMS_WORKLOAD_REPLAY API to disable the timeout check if the replay is
expected to be slower.
ORA-15590: encountered incomplete workload capture files
Cause: The captured workload contained one or more incomplete recording files. This
can happen when the original workload capture's FINISH_CAPTURE command
timed out while waiting for all the active sessions to close their workload capture
files.
Action: Incomplete capture files will not interfere with the processing and replaying
of the captured workload. This is simply a warning message to point out that some
database calls might not have been recorded due to FINISH_CAPTURE command
timing out. For a list of the incomplete files, check the alert log for lines containing
DBMS_WORKLOAD_REPLAY.PROCESS_CAPTURE after capture processing.
ORA-15591: encountered corrupt workload capture files
Cause: The captured workload contained one or more corrupt recording files.
Action: For a list of the incomplete files, check the alert log for lines containing
DBMS_WORKLOAD_REPLAY.PROCESS_CAPTURE after capture processing. The
corrupt files will be replayed up to the point of the corruption. Alternatively, it is
possible to remove the corrupt files and run
DBMS_WORKLOAD_REPLAY.PROCESS_CAPTURE again. In this case, no workload
from the corrupt files will be replayed.
ORA-15601: Invalid value specified for parameter "string"
Cause: An invalid value was specified for the given parameter.
Action: Correct the value being specified for the parameter.
ORA-15602: Parameter "string" cannot be NULL.
Cause: An attempt was made to call a procedure without a required parameter.
ORA-15603: Action cannot be performed when database is in read-only mode.

Cause: A procedure in DBMS_AUTO_TASK_ADMIN package was invoked when
database was open in read-only mode.
Action: Retry when database is open in read/write mode.
ORA-15604: Initialization parameters prevent client from being enabled.
Cause: An attempt was made to enable a client that was disabled for automatic
execution by an initialization parameter.
Action: Check the related client parameters and try again.
ORA-15605: "string" is not a Maintenance Window
Cause: Window name passed to DBMS_AUTO_TASK_ADMIN.ENABLE procedure
must be a member of the MAINTENANCE_WINDOW_GROUP.
Action: Make the window a member of the MAINTENANCE_WINDOW_GROUP
and retry the call.
ORA-15700: SQL limit already reached by prior task execution
Cause: An attempt was made to resume the execution of a task when the prior
execution already reached the SQL limit.
Action: Task execution is complete. Examine the report to review Advisor's
recommendations.
ORA-15701: All "SQL Tuning Set(s)" with name like "string" and owner like
"string" are empty
Cause: An attempt was made to pack one or more SQL Tuning Sets, none * of which
contained any statements.
Action: Check the input and try again.
ORA-15702: duplicate values for plan line ID in input collection
Cause: An invalid input was provided containing duplicate values for plan line IDs
causing the load of the statement to fail.
ORA-15703: invalid version number "number" for SQL tuning set staging table
Cause: An invalid version number was provided for a staging table used to pack a
SQL tuning set.
ORA-15739: invalid name "string" for SQL Performance Analyzer task
Cause: An invalid SQL Performance Analyzer task name was used.
Action: Check the name of the SQL Performance Analyzer task to ensure that it is
correct.
ORA-15740: parameter "string" not set for SQL Performance Analyzer task "string"
Cause: Could not find the specified parameter name for the SQL Performance
Analyzer task.
Action: Check that the specified parameter exists for the SQL Performance Analyzer
task so that the parameter is set.
ORA-12700 to ORA-19400 69-191
ORA-15741: no COMPARE_PERFORMANCE execution exists for SQL

Performance Analyzer task "string"
Cause: Could not find an execution of type COMPARE_PERFORMANCE for
specified SQL Performance Analyzer task.
Action: Ensure that the given SQL Performance Analyzer task has at least one
execution of type COMPARE_PERFORMANCE.
ORA-15742: specified execution name "string" is not a valid
COMPARE_PERFORMANCE execution for SQL Performance Analyzer task
"string".
Cause: The specified execution name was not a valid execution of type
COMPARE_PERFORMANCE for the SQL Performance Analyzer task.
Action: Ensure that a valid COMPARE_PERFORMANCE execution name is used for
the SQL Performance Analyzer task.
ORA-15743: need to specify the object ID if the tuning task is on a SQL set.
Cause: There could be multiple objects in the SQL tuning task. Specify which one.
Action: Add object ID to the interface.
ORA-15744: The directory name is null.
Cause: The directory name for finding the SQL traces was null.
Action: Create the directory.
ORA-15745: The plan type is not valid.
Cause: The specified plan type was not valid
Action: Check the existing plan types and specify the right one.
ORA-15746: Missing EXECUTE privilege on DBMS_AUTO_SQLTUNE.
Cause: The current user was missing the necessary privileges to execute the API.
Action: Grant the privilege and try again.
ORA-15747: The previous Oracle Data Masking job is unfinished. "string" table is
not empty.
Cause: The previously executed Oracle Data masking job was not successfully
completed.
Action: Execute Oracle Data masking cleanup.
ORA-16000: database or pluggable database open for read-only access
Cause: The database or pluggable database was opened for read-only access.
Attempts to modify the database using DML or DDL statements generate this error.
Action: In order to modify the database or pluggable database, it must first be shut
down and reopened for read/write access.
ORA-16001: database already open for read-only access by another instance
Cause: The database has been 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 shut down and reopened for read-only access.
ORA-16002: database or pluggable database already open for read/write access by

another instance
Cause: The database or pluggable database has been 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 shut down and reopened for read/write access.
ORA-16003: standby database is restricted to read-only access
Cause: An attempt was made to open a physical standby database in read/write
mode.
Action: Reissue the ALTER DATABASE OPEN specifying READ ONLY.
ORA-16004: backup database required recovery
Cause: The database could not be opened for read-only access by this instance
because it requires recovery.
Action: Perform the necessary recovery and reopen for read-only access.
ORA-16005: database requires recovery
Cause: The database requires recovery, and therefore cannot be opened for read-only
access by this instance.
Action: Perform the necessary recovery and reopen for read-only access.
ORA-16006: A remote archival request was aborted due to database shutdown.
Cause: When opening or closing a database instance, the database may wait for
pending remote archival requests to complete before proceeding with the operation.
This error was reported because a shutdown was detected.
Action: This is an informational message so no action is required.
ORA-16007: invalid backup control file checkpoint
Cause: The database could not be opened for read-only access because its control file
did not contain a valid control file checkpoint.
Action: Open the database for read/write access to create a valid control file
checkpoint. The database can then be opened for read-only access.
ORA-16008: indeterminate control file checkpoint
Cause: The control file for the database being opened for read-only access was created
using the CREATE CONTROLFILE statement. Therefore, a control file checkpoint
could not be calculated and the database could not be opened for read-only access.
Action: First, open the database for read/write access. This creates a valid control file
checkpoint. Then, reopen the database for read-only access.
ORA-16009: invalid redo transport destination
Cause: The redo transport destination could not accept redo data because it was not a
valid redo transport destination type.
Action: Verify that all redo transport destinations are either standby databases or
downstream capture databases.
ORA-16011: Remote File Server process is in Error state.
Cause: The Remote File Server (RFS) process at the specified redo transport
destination experienced an unrecoverable error and was unable to receive further
redo data.
Action: Correct the problem at the redo transport destination.
ORA-12700 to ORA-19400 69-193
ORA-16012: database identifier mismatch

Cause: The database identifier of a physical standby database did not match that of
the primary database.
Action: Ensure that the database identifier of each physical standby database matches
that of the primary database.
ORA-16013: log string sequence# string does not need archiving
Cause: An attempt was made to archive the named file manually, but the file did not
require archiving. The file had previously been successfully archived.
ORA-16014: log string sequence# string not archived, no available destinations
Cause: An attempt was made to archive the named log, but the archive was
unsuccessful. The archival failed because there were no archive log destinations
specified, or all destinations are in an error state.
Action: Verify that archive log destinations are specified or take the necessary step to
correct any errors that may have occurred.
ORA-16015: Log string sequence# string was not archived.
Cause: An attempt was made to archive the named log to a destination, but the
operation did not succeed because the destination was not in ARCHIVELOG mode.
Action: Enable ARCHIVELOG mode at all destinations and retry.
ORA-16016: archived log for thread string sequence# string unavailable
Cause: Redo apply timed out waiting for the requested archived log file.
Action: Verify that the primary database is still archiving redo data to the standby
database and reissue the RECOVER STANDBY DATABASE command.
ORA-16017: cannot use LOG_ARCHIVE_DUPLEX_DEST without a primary
archive destination
Cause: The parameter LOG_ARCHIVE_DUPLEX_DEST was set to a non-NULL value
when the primary archive destination was set to NULL explicitly.
Action: Set the primary archive destination to a valid non-NULL value.
ORA-16018: cannot use string with LOG_ARCHIVE_DEST_n or
DB_RECOVERY_FILE_DEST
Cause: One of the following events caused an incompatibility: 1) Parameter
LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST was in use when a
LOG_ARCHIVE_DEST_n (n = 1...31) parameter was encountered while fetching
initialization parameters. 2) An ALTER SYSTEM ARCHIVE LOG START TO
command was in effect when a LOG_ARCHIVE_DEST_n parameter was encountered
while fetching initialization parameters. 3) A LOG_ARCHIVE_DEST_n parameter
was in use when an ALTER SYSTEM command was used to define a value for either
the LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST parameter. 4)
Parameter DB_RECOVERY_FILE_DEST was in use when an attempt was made to use
an ALTER SYSTEM or ALTER SESSION command to define a value for
LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST.
Action: Eliminate any incompatible parameter definitions.
ORA-16019: cannot use string with LOG_ARCHIVE_DEST or

LOG_ARCHIVE_DUPLEX_DEST
Cause: One of the following events caused an incompatibility: 1) Parameter
LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST was in use when the
specified LOG_ARCHIVE_DEST_n (n = 1...31) or DB_RECOVERY_FILE_DEST
parameter was encountered while fetching initialization parameters. 2) Parameter
LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST was in use when an
attempt was made to use an ALTER SYSTEM or ALTER SESSION command to define
a value for the specified LOG_ARCHIVE_DEST_n or DB_RECOVERY_FILE_DEST
parameter. 3) An ALTER SYSTEM ARCHIVE LOG START TO command was in effect
when the specified LOG_ARCHIVE_DEST_n parameter was encountered while
fetching initialization parameters. 4) 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 define a value for the specified
LOG_ARCHIVE_DEST_n parameter.
ORA-16020: fewer destinations available than specified by
LOG_ARCHIVE_MIN_SUCCEED_DEST
Cause: The number of archive log destinations that could be used was less than the
LOG_ARCHIVE_MIN_SUCCEED_DEST parameter value.
Action: Either adjust the log archive destination parameters, or lower the value of
LOG_ARCHIVE_MIN_SUCCEED_DEST.
ORA-16021: session string destination cannot be the same as session string
destination
Cause: An attempt was made to change the first specified archive log parameter using
ALTER SESSION to have a destination value that duplicates the session-level
destination value of the second specified archive log parameter.
Action: Specify a different session destination value for one of the
LOG_ARCHIVE_DEST_n parameters.
ORA-16022: LOG_ARCHIVE_DEST cannot be NULL because
LOG_ARCHIVE_DUPLEX_DEST is non-NULL
Cause: An attempt was made to change parameter LOG_ARCHIVE_DEST to NULL
when parameter LOG_ARCHIVE_DUPLEX_DEST is non-NULL.
Action: Either set parameter LOG_ARCHIVE_DEST to a non-NULL value, or set
parameter LOG_ARCHIVE_DUPLEX_DEST to a NULL value.
ORA-16023: system string destination cannot be the same as session string
destination
Cause: An attempt to change the first specified LOG_ARCHIVE_DEST_n (n = 1...31)
parameter produced a destination that duplicates the session destination value of the
second specified LOG_ARCHIVE_DEST_n 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 ALTER SESSION command, because then the
associated system destination value may appear as a duplicate.
Action: Specify a different destination value for the first specified
LOG_ARCHIVE_DEST_n parameter.
ORA-12700 to ORA-19400 69-195
ORA-16024: parameter string cannot be parsed

Cause: The value for the indicated LOG_ARCHIVE_DEST_n (n = 1...31) parameter
could not be parsed. Common causes for this error are a misplaced equal sign, an
unrecognized attribute, or an attribute that is missing a required value.
Action: Correct the value for the indicated LOG_ARCHIVE_DEST_n parameter.
ORA-16025: parameter string contains repeated or conflicting attributes
Cause: The value for the specified LOG_ARCHIVE_DEST_n (n = 1...31) parameter
contained either repeated attributes or attributes that conflicted with each other.
ORA-16026: parameter string contains an invalid attribute value
contained an attribute with an invalid value.
ORA-16027: parameter string is missing a destination option
Cause: The value for the indicated LOG_ARCHIVE_DEST_n (n = 1...31) parameter
failed to include a destination option. A destination option is specified using either
the LOCATION or SERVICE attrbute.
ORA-16028: new string causes less destinations than
LOG_ARCHIVE_MIN_SUCCEED_DEST requires
Cause: An attempt was made to change the indicated LOG_ARCHIVE_DEST_n or
LOG_ARCHIVE_DEST_STATE_n parameter (n = 1...31) to a value that reduces the
number of archive log destinations to less than the specified
LOG_ARCHIVE_MIN_SUCCEED_DEST value.
Action: Either select different options for the LOG_ARCHIVE_DEST_n or
LOG_ARCHIVE_DEST_STATE_n parameters, or reduce the value for 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 archive destinations using parameters
LOG_ARCHIVE_DEST, LOG_ARCHIVE_DUPLEX_DEST, or
LOG_ARCHIVE_DEST_n (n = 1...31). Then, change the value of parameter
ORA-16030: session specific change to the
LOG_ARCHIVE_MIN_SUCCEED_DEST parameter requires a
LOG_ARCHIVE_DEST_n destination
Cause: The following event caused an incompatibility: Parameter
LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST 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 LOG_ARCHIVE_DEST_n (n = 1...31) parameters.
ORA-16031: parameter string destination string exceeds string character limit

Cause: The value for the specified parameter contained a destination string that is too
long.
Action: Replace the destination value for the specified parameter with a character
string that has a length below the limit specified in the error message.
ORA-16032: parameter string destination string cannot be translated
Cause: The value for the specified parameter contained a destination string that could
not be translated.
Action: Use a valid destination string in the specified parameter.
ORA-16033: parameter string destination cannot be the same as parameter string
destination
Cause: An attempt was made to change the first specified archive log parameter to
have a destination value that duplicates the system-level destination value of the
second specified archive log parameter.
Action: Specify a different value for one of the archive log parameters.
ORA-16034: Recovery could not be started.
Cause: Database recovery could not be started because the FROM and MANAGED
STANDBY DATABASE clauses were both specifed when attempting to start recovery.
Action: Retry the command with either the FROM or MANAGED STANDBY
DATABASE clause, but not both.
ORA-16035: missing required keyword string
Cause: The indicated keyword is required but was not specified.
ORA-16036: invalid CANCEL option
Cause: A mode other than IMMEDIATE followed the CANCEL keyword in
RECOVER MANAGED STANDBY DATABASE statement.
Action: Specify either nothing or IMMEDIATE following CANCEL.
ORA-16037: user requested cancel of managed recovery operation
Cause: The managed standby database recovery operation has been canceled per user
request.
ORA-16038: log string sequence# string cannot be archived
Cause: An attempt was made to archive the named file, but the file could not be
archived. Examine the secondary error messages to determine the cause of the error.
ORA-16039: RFS request version mismatch
Cause: A request to archive a redo log to a redo transport destination failed because
of an Oracle software version mismatch at the destination.
Action: Verify that a compatible version of Oracle software is running at the redo
transport destination.
ORA-12700 to ORA-19400 69-197
ORA-16040: Destination archive log file is locked.

Cause: The target archive log file was locked. This indicates that the file is being
archived to another Remote File Server (RFS) process.
Action: Ensure that each remote redo transport destination uses a unique network
service name.
ORA-16041: Remote File Server fatal error
Cause: The Remote File Server (RFS) process at a redo transport destination
encountered a fatal error and was no longer available. Further redo transmission to
this destination may not be possible.
Action: Refer to the appropriate RFS trace file located at the redo transport destination
for details regarding the error encountered and take corrective action.
ORA-16042: user requested cancel immediate of redo apply
Cause: Redo apply was canceled immediately per user request. Processing of the
current archive log file has been interrupted and, therefore, the database is in an
inconsistent state.
ORA-16043: Redo apply has been canceled.
Cause: Redo apply was canceled per user request or operation timeout.
Action: More specific messages will accompany this message.
ORA-16044: Destination string attribute cannot be specified at session level.
Cause: An attempt was made to modify a redo transport destination attribute using
the ALTER SESSION command.
Action: Use the ALTER SYSTEM command to modify the destination attribute.
ORA-16045: circular redo transport destination dependency chain
Cause: An attempt was made to make a redo transport destination dependent on a
redo transport destination that was dependent on it.
Action: Ensure that no redo transport destination is dependent on any destination
that is dependent on it.
ORA-16046: Redo transport destination failed due to failed dependent destination.
Cause: The redo transport destination was dependent upon another destination,
which failed. Therefore, this destination failed.
ORA-16047: DGID mismatch between destination setting and target database
Cause: The DB_UNIQUE_NAME specified for the destination did not match the
DB_UNIQUE_NAME at the target database.
Action: Make sure the DB_UNIQUE_NAME specified in the
LOG_ARCHIVE_DEST_n parameter matches the DB_UNIQUE_NAME parameter
defined at the destination.
ORA-16050: destination exceeded specified quota size
Cause: An archive log was attempted to be created in a destination with a specified
maximum quota size. The creation of the archive log exceeded the specified quota
size. Therefore, the destination has been made inaccessible to future archival
operations.

ORA-16051: parameter string contains an invalid delay time
contained a DELAY attribute with an invalid numeric value. The valid range is 0-5760
(in minutes).
ORA-16052: DB_UNIQUE_NAME attribute is required.
Cause: DB_UNIQUE_NAME attribute was not specified. The value of the
LOG_ARCHIVE_DEST_n parameter for each remote redo transport destination must
contain the DB_UNIQUE_NAME attribute if the LOG_ARCHIVE_CONFIG
parameter value contains the DG_CONFIG attribute.
Action: Use the DB_UNIQUE_NAME attribute to specify the DB_UNIQUE_NAME
for the destination.
ORA-16053: DB_UNIQUE_NAME string is not in the Data Guard Configuration
Cause: The specified DB_UNIQUE_NAME is not in the Data Guard Configuration.
Action: If the DG_CONFIG attribute of the LOG_ARCHIVE_CONFIG parameter is
enabled, you must specify a valid DB_UNIQUE_NAME. The list of valid
DB_UNIQUE_NAMEs can be seen with the V$DATAGUARD_CONFIG view. This
problem can also occur when specifying a non-standby destination with an
DB_UNIQUE_NAME attribute that does not match the DB_UNIQUE_NAME
initialization parameter for the current instance.
ORA-16055: FAL request rejected
Cause: Fetch archive log (FAL) server rejected a redo gap fetch request from the
client. This may have various causes.
Action: Check the alert log on the primary database. Take the appropriate action to
solve the problem.
ORA-16056: Backup control file archival requires proper syntax.
Cause: An attempt was made to perform an online log file archival using a backup
control file. However, the USING BACKUP CONTROLFILE syntax was not specified.
Action: Use the USING BACKUP CONTROLFILE clause to perform an online log file
archival using a backup control file.
ORA-16057: server not in Data Guard configuration
Cause: The primary database or fetch archive log (FAL) server was not found in the
Data Guard configuration of the standby database.
Action: Add the database unique name of the primary database or FAL server to the
DG_CONFIG attribute of the LOG_ARCHIVE_CONFIG database initialization
parameter.
ORA-16058: standby database instance is not mounted
Cause: The Remote File Server (RFS) process on the standby database received an
internal error.
Action: Check the standby alert log and RFS trace files for more information.
ORA-16059: empty log file or invalid next available block
Cause: An attempt was made to archive an empty or invalid log file.
ORA-12700 to ORA-19400 69-199
ORA-16060: Log file is current.

Cause: An attempt was made to archive current log file.
ORA-16061: Log file status has changed.
Cause: The online log file was reclaimed as a new log file either before archival
started or during the archival operation.
ORA-16062: standby database not in Data Guard configuration
Cause: The standby database was not found in the Data Guard configuration of the
server.
Action: Add the database unique name of the standby database to the DG_CONFIG
attribute of the LOG_ARCHIVE_CONFIG database initialization parameter.
ORA-16065: remote archival disabled at standby destination
Cause: Receipt of remote archived REDO log files has been disabled at the associated
standby destination host database.
Action: If appropriate change the associated archive log parameter to specify a local
destination with the LOCATION keyword or defer the associated archive log
destination. Or, if possible, set the standby REMOTE_ARCHIVE_ENABLE parameter
to TRUE, or enable the RECEIVE attribute of the LOG_ARCHIVE_CONFIG
parameterand restart the standby database instance before further REDO log file
archivals occur.
ORA-16066: remote archival disabled
Cause: An archive log destination parameter has specified a remote destination with
the SERVICE keyword. Remote archival of REDO log files has been disabled for this
database. The associated archive log destination has been disabled.
Action: If appropriate change the archive log parameter to specify a local destination
with the LOCATION keyword or (if appropriate) set the
REMOTE_ARCHIVE_ENABLE parameter to TRUE, or enable the SEND attribute of
the LOG_ARCHIVE_CONFIG parameter and restart the database instance before
further REDO log file archivals occur.
ORA-16067: activation identifier mismatch in archive log string
Cause: The activation identifier contained in the archive log file header does not
match the activation identifier of the database being recovered. The indicated archive
log cannot be applied to the database.
Action: Locate the appropriate archive log for the database.
ORA-16068: redo log file activation identifier mismatch
Cause: The activation identifier of the indicated redo log file does not match the
activation identifier of the database.
Action: n/a
ORA-16069: activation identifier mismatch
Cause: Redo transport failed because the activation identifier of the primary and
physical standby databases did not match. This can happen if the physical standby
database was not created from a backup of the primary database.
Action: Create a valid configuration and re-try the failed operation.
ORA-16070: parameter string contains an invalid REGISTER attribute value

contained a REGISTER attribute that specified an invalid file name template string. If
specified, the REGISTER file name template string must indicate an O/S-specific file
path name including thread and log sequence number substitution directives (%t, %T,
%s, %S).
Action: Correct the value for the LOG_ARCHIVE_DEST_n parameter.
ORA-16071: Archived log file string was not found at dependency destination.
Cause: The specified archived log file was not found at a redo tranpsort destination
on which other destinations are dependent.
Action: Verify that all redo transport destinations that are dependent upon another
destination or upon which other destinations are dependent are configured correctly.
ORA-16072: a minimum of one standby database destination is required
Cause: No standby database archive log destinations were specified.
Action: Specify a standby archive log destination in the initialization parameter file.
ORA-16073: archiving must be enabled
Cause: Online log file archiving is disabled.
Action: Enable log file archiving.
ORA-16074: No ARCH processes are active.
Cause: All ARCH processes have stopped.
Action: Restart the instance.
ORA-16075: standby database destination mismatch
Cause: Another instance had access to a standby database destination that this
instance did not. If the initialization parameter LOG_ARCHIVE_CONFIG does not
define a DG_CONFIG, this may be due to a standby database becoming unavailable
recently.
Action: Ensure that at each instance the set of standby databases referred to by
LOG_ARCHIVE_DEST_n initialization parameters is the same and define a
DG_CONFIG at each instance to identify those databases explicitly.
ORA-16076: unknown standby database destination
Cause: A standby database destination was specified that was not accessed by
another instance. If the initialization parameter LOG_ARCHIVE_CONFIG does not
define a DG_CONFIG, this mismatch may be due to a standby database having been
restarted recently.
Action: Ensure that at each instance the set of standby databases referred to by
LOG_ARCHIVE_DEST_n initialization parameters is the same and define a
DG_CONFIG at each instance to identify those databases explicitly.
ORA-16078: media recovery disabled
Cause: The database is not in ARCHIVELOG mode.
Action: Place the database in ARCHIVELOG mode.
ORA-16079: standby archival not enabled
Cause: The standby database did not have archival enabled.
ORA-12700 to ORA-19400 69-201
Action: In order to allow the standby database to access the standby log files, the
standby database must be in ARCHIVELOG mode.
ORA-16080: invalid LogMiner session string for APPLY
Cause: Logical standby apply engine was started with an invalid LogMiner session
identifier.
Action: Fix the problem with the LogMiner session or create a new session.
ORA-16081: insufficient number of processes for APPLY
Cause: Logical standby apply engine was started with fewer processes available than
needed.
Action: Increase the values of the initialization parameters PROCESSES and or the
MAX_SERVERS parameter seen in the DBA_LOGSTDBY_PARAMETERS view.
ORA-16082: logical standby is not initialized correctly
Cause: Logical standby apply engine was started but it found inconsistencies in its
metadata.
Action: Look in the trace file for more information.
ORA-16083: LogMiner session has not been created
Cause: Logical standby apply engine was started without creating a LogMiner
session.
Action: Create a LogMiner session and restart the apply engine.
ORA-16084: an apply engine is already running
Cause: A logical standby apply engine was running when another was created.
Action: Shut down the previous apply engine before starting a new one.
ORA-16086: Redo data cannot be written to the standby redo log
Cause: The primary database was in MAXIMUM PROTECTION or MAXIMUM
AVAILABILITY mode, but redo data could not be written to the standby redo log at
the standby database(s).
Action: Check the Remote File Server (RFS) trace file for specific errors and
reconfigure the standby redo log as appropriate.
ORA-16087: Switchover requires standby or current control file.
Cause: An attempt was made to perform a switchover operation using a backup or
clone control file.
Action: Convert the backup control file into a current control file prior to attempting a
switchover operation. A clone control file cannot be used for a switchover operation.
ORA-16088: archive log has not been completely archived
Cause: An attempt was made to register an archive log that has not been completely
archived. The specified archive log may be a "current" log file.
Action: Specify a completed archive log.
ORA-16089: archive log has already been registered
Cause: An attempt was made to register an archive log that already has a
corresponding thread# and sequence# entry in the standby database control file.
Duplicate information is not permitted.
Action: Use the V$ARCHIVED_LOG fixed view to verify the archive log information.
ORA-16090: archive log to be replaced not created by managed standby process

Cause: An attempt was made to replace an archive log entry that was not originally
created by the managed standby operation.
Action: No user action required.
ORA-16091: dependent archive log destination already archived
Cause: An archive log destination contains a dependency to another archive log
destination that has previously been archived.
Action: The parent archive log destination cannot be dependent on another archive
log destination. Use the ALTER SYSTEM command to remove one of the dependency
attributes.
ORA-16092: dependent archive log destination is not active
destination that is not active"
Action: The child archive log destination cannot be dependent on another invalid
archive log destination. Use the ALTER SYSTEM command to remove one of the
dependency attributes.
ORA-16093: dependent archive log destination is not LGWR-enabled
destination that is not enabled for the LGWR process"
Action: The child archive log destination cannot be dependent on another archive log
destination not archived by the LGWR. Use the ALTER SYSTEM command to change
the parent archive log to specify the LGWR process.
ORA-16094: Database shut down during archival operation.
Cause: The database was shut down while an online log file archival was active.
ORA-16095: Dependent destination removal for inactivation
Cause: A dependent archive log destination was inactivated due to the parent archive
log destination becoming inelligible for archival. This may be due to the parent
destination being manually deferred by an application user.
ORA-16096: ALTER DATABASE COMMIT TO SWITCHOVER TO PHYSICAL
STANDBY
Cause: None
Action: Specify this command to switch the primary database to the physical standby
role.
ORA-16097: ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY
Cause: None
Action: Specify this command to switch the physical standby database to the primary
role.
ORA-16098: Primary database has been shut down to prevent data loss.
Cause: The primary database was shut down because it was operating in maximum
protection mode and no suitable standby databases were available to protect the
primary database from data loss.
ORA-12700 to ORA-19400 69-203
Action: Diagnose and correct whatever errors exist in the configuration or configure
the primary database for maximum availability or maximum performance mode.
ORA-16099: internal error ORA-00600 occurred at standby database
Cause: The RFS process on the standby database received an internal error.
Action: Check the standby alert log and RFS trace files for more information.
ORA-16100: not a valid Logical Standby database
Cause: This database has not been completely configured as a Logical Standby
database.
Action: Verify that the database is the intended Logical Standby database. Ensure that
you already started logical standby apply with the ALTER DATABASE START
LOGICAL APPLY INITIAL statement. See the Oracle8i SQL Reference manual for the
statement syntax.
ORA-16101: a valid start SCN could not be found
Cause: An SCN from which to start could not be found.
Action: Register the first log file following the backup from which this database was
generated. Using the ALTER DATABASE REGISTER LOGILE statement to register
the database is recommended. Alternatively, you can provide a starting SCN value
with this startement.
ORA-16102: remote information is not available on the specified primary
Cause: The new primary has not completed generating the necessary information for
the standby to begin consuming its log stream.
Action: Verify that the database link provided references a system that is about to
become a new primary. Wait a short time before retrying the command to allow the
primary some time to generate the necessary information.
ORA-16103: Logical Standby apply must be stopped to allow this operation
Cause: Logical Standby is currently applying changes. The apply must complete or be
stopped to allow the requested operation.
Action: Execute the ALTER DATABASE STOP LOGICAL STANDBY APPLY
statement, then re-enter or respecify the operation.
ORA-16104: Invalid Logical Standby parameter
Cause: The specified parameter is not valid.
Action: Check spelling or refer to the DBMS_LOGSTDBY PL/SQL package
documentation for the correct statement syntax.
ORA-16105: Logical Standby is already running in background
Cause: A Logical Standby apply operation is already running.
Action: None
ORA-16106: loading previously applied transaction information
Cause: Logical Standby coordinator was performing a scan to identify previously
applied transactions.
event for diagnostic purposes.
ORA-16107: all log data from primary has been processed

Cause: On the primary system, the log stream has been ended by the ALTER
DATABASE COMMIT TO SWITCHOVER TO LOGICAL STANDBY command.
Action: Issue one of the following commands to make this standby a primary or
resume applying changes from a new primary. ALTER DATABASE COMMIT TO
SWITCHOVER TO LOGICAL PRIMARY; ALTER DATABASE START LOGICAL
STANDBY APPLY NEW PRIMARY dblink;
ORA-16108: database is no longer a standby database
Cause: The current database has already been made a primary database.
Action: Issue the following commands to make this primary a standby. ALTER
DATABASE COMMIT TO SWITCHOVER TO LOGICAL STANDBY; ALTER
DATABASE START LOGICAL STANDBY APPLY NEW PRIMARY dblink;
ORA-16109: failed to apply log data from previous primary
Cause: Log data from previous primary could not be completely applied.
Action: Check DBA_LOGSTDBY_EVENTS for failures and take corrective action.
Then, reissue command.
ORA-16110: user procedure processing of logical standby apply DDL
Cause: A user provided stored procedure has been called to inspect a DDL statement
prior to it being processed.
Action: No action necessary, this informational statement is provided to record user
involvement in the processing of a statement. Additional information can be found in
the DBA_LOGSTDBY_EVENTS and the DBA_LOGSTDBY_SKIP views.
ORA-16111: log mining and apply setting up
Cause: This logical standby process is setting up to begin processing changes.
Action: No action necessary, this informational statement is provided to record the
ORA-16112: log mining and apply stopping
Cause: This logical standby process is cleaning up and stopping Logical Standby
apply.
ORA-16113: applying change to table or sequence string
Cause: The process is applying changes to a specific schema object.
ORA-16114: applying DDL transaction with commit SCN string
Cause: The process is applying a DDL change that's committed at the given SCN.
ORA-16115: string\% of LogMiner dictionary loading is done
Cause: The process is loading dictionary information from the redo stream. This
activity may take a few minutes.
ORA-12700 to ORA-19400 69-205

ORA-16116: no work available
Cause: The process is idle waiting for additional changes to be made available.
ORA-16117: processing
Cause: The process is performing its primary function and is not waiting on any
significant event.
ORA-16119: building transaction at SCN string
Cause: The transaction being committed at the given SCN is being prepared for
apply.
ORA-16120: dependencies being computed for transaction at SCN string
Cause: The transaction committed at the given SCN is being analyzed for
dependencies.
ORA-16121: applying transaction with commit SCN string
Cause: The transaction committed at the given SCN is being applied.
ORA-16122: applying large dml transaction at SCN string
Cause: A large transaction is being applied before the commit has been seen. The
current redo being applied ends as the given SCN.
ORA-16123: transaction string string string is waiting for commit approval
Cause: The apply process is waiting for approval to commit a transaction. This
transaction may depend on another or other synchronization activity may delay the
committing of a transaction.
ORA-16124: transaction string string string is waiting on another transaction
Cause: The apply process is waiting to apply additional changes. This transaction
likely depends on another.
ORA-16125: large transaction string string string is waiting for more data
Cause: The apply process is waiting until additional changes for a large transaction
are retrieved from the log stream.
ORA-16126: loading table or sequence string
Cause: Information on the given table or sequence is being loaded into an in memory
cache for future use.
ORA-16127: stalled waiting for additional transactions to be applied
Cause: This process is waiting for additional memory before continuing. Additional
log information cannot be read into memory until more transactions have been
applied to the database, thus freeing up additional memory.
event for diagnostic purposes. If this message occurs often and changes are not being
applied quickly, increase available SGA or the number of apply processes.
ORA-16128: User initiated stop apply successfully completed
Cause: Logical standby was shutdown in an orderly fashion.
ORA-16129: unsupported DML encountered
Cause: One or more DMLs to an unsupported table were encountered and skipped.
event for diagnostic purposes. Optionally, check the DBA_LOGSTDBY_EVENTS
view for more information including the impacted table owner and name.
ORA-16130: supplemental log information is missing from log stream
Cause: Supplemental logging is not enabled at the primary database.
Action: Issue the following command to enable supplemental logging. ALTER
DATABASE ADD SUPPLEMENTAL LOG DATA (PRIMARY KEY, UNIQUE INDEX)
COLUMNS;
ORA-16131: An error occurred during a Terminal Recovery of the standby.
Cause: An error occurred during a Terminal Recovery of the standby.
Action: Check the standby alert log additional information.
ORA-16132: An error occurred during activation of the standby.
Cause: An error occurred during activation of the standby database following a
Terminal Recovery.
Action: Check the standby alert log additional information.
ORA-16133: Datafile string has incorrect terminal recovery stamp.
Cause: After activation of a standby database following a terminal recovery (recovery
of standby using current logs), recovery of a datafile from before the activation must
have completed the same terminal recovery to avoid corruption.
ORA-12700 to ORA-19400 69-207
Action: A backup of the datafile taken after the terminal recovery and before
activating the standby must be used for recovery.
ORA-16134: invalid MANAGED recovery FINISH option
Cause: A mode other than NOWAIT follows the FINISH keyword in RECOVER
MANAGED STANDBY DATABASE statement.
Action: Specify either nothing or NOWAIT following FINISH.
ORA-16135: Invalid LOG_ARCHIVE_CONFIG modification while in protected
mode
Cause: The LOG_ARCHIVE_CONFIG parameter can not be modified while any RAC
instance is open in either maximum protection or maximum availability mode. Also,
the parameter can not be modified in such way that would cause all destinations to
fail while in maximum protection mode.
Action: Make the modification before the database is opened by any instance.
ORA-16136: Managed Standby Recovery not active
Cause: An attempt was made to cancel a managed recovery session but no managed
recovery session was active.
Action: No action is necessary.
ORA-16138: end of log stream not received from primary
Cause: The standby system has not received notification that the primary system log
stream has been terminated. A graceful switchover is not possible.
Action: Verify that the primary log stream has been terminated. Ensure that the
standby has applied all necessary redo from the primary system and, if appropriate,
reissue the graceful switchover command.
ORA-16139: media recovery required
Cause: An error has occurred while performing a switchover.
Action: If you were switching a primary database to the standby role, the conversion
was successful, but one or more errors occurred after the conversion completed. See
the alert log for more information. You can proceed with switching the target standby
database to the primary role, but you must address the errors reported at the old
primary database before it can protect the new primary database. If you encountered
this error while switching a physical standby database to the primary role, the
switchover did not succeed because additional redo must be applied. Verify that redo
apply is active and wait until the SWITCHOVER_STATUS column of the V
$DATABASE dynamic performance view reports TO_PRIMARY or
SESSIONS_ACTIVE before retrying the switchover.
ORA-16140: standby online logs have not been recovered
Cause: The standby database has online logs containing redo that has not been
recovered. Activating the standby would lose redo contained in the online logs.
Action: To recover the standby online logs issue the following command: ALTER
DATABASE RECOVER MANAGED STANDBY DATABASE FINISH. Then reissue
the ALTER DATABASE ACTIVATE STANDBY DATABASE command. To activate
the standby without recovering the online logs, issue the following command: ALTER
DATABASE ACTIVATE STANDBY DATABASE SKIP STANDBY LOGFILE.
ORA-16143: RFS connections not allowed during or after terminal recovery
Cause: An attempt was made, by an RFS process, to access a standby online log file
during or after a terminal recovery.
Action: The primary must not attempt to archive to the standby after a terminal
recovery.
ORA-16145: archival for thread# string sequence# string in progress
Cause: The indicated archived log file is not available for recovery due to the fact that
it is still being archived.
Action: Verify that archival of the indicated log file has completed and reissue the
RECOVER STANDBY DATABASE command.
ORA-16146: stringcontrol file enqueue unavailable
Cause: The control file enqueue is currently unavailable.
Action: No Action is required. We will try to re-fetch it at a later time.
ORA-16147: standby database referenced by multiple archive log destinations
Cause: Multiple archive log destinations reference the same standby database, using
different service names. This is not allowed.
Action: Remove one of the duplicate archive log destinations.
ORA-16148: user requested expiration of managed recovery operation
Cause: The managed standby database recovery operation has been canceled per user
specified EXPIRE option of the RECOVER MANAGED STANDBY DATABASE
statement.
ORA-16150: FINISH recovery performed on another, older standby database
Cause: An archive log containing a FINISH recovery indicator was received by a
standby database that has received archive logs in the future of the received archive
log. Because of the possibility that these future archive logs have been applied to this
standby database, the received archive log must be rejected.
ORA-16151: Managed Standby Recovery not available
Cause: The attempted operation failed because of a pending CANCEL of the
managed standby recovery operation.
Action: Wait for the managed standby recovery session to end. Then retry the
operation.
ORA-16152: standby database is in 'no-data-loss' protected mode
Cause: The attempted database operation is not allowed while the standby database is
in 'no-data-loss' protected mode.
Action: Verify that the attempted database operation is warranted, ALTER
DATABASE SET STANDBY DATABASE UNPROTECTED and reissue the statement.
ORA-16154: suspect attribute: string
Cause: Use of the indicated attribute is illegal in the given context.
Action: Make the appropriate changes and reissue the statement.
ORA-16156: LGWR archive log dependency not allowed if database is standby
protected
Cause: The use of a LGWR archive log dependency is not allowed when the primary
is protected by a standby database, as this requires use of the standby redo log files.
ORA-12700 to ORA-19400 69-209
Action: Remove the LGWR archive log dependency and use normal LGWR archival
instead.
ORA-16157: media recovery not allowed following successful FINISH recovery
Cause: A RECOVER MANAGED STANDBY DATABASE FINISH command has
previously completed successfully. Another media recovery is not allowed.
Action: Issue one of these operations following a FINISH recocvery: ALTER
DATABASE OPEN READ ONLY or ALTER DATABASE COMMIT TO
SWITCHOVER TO PRIMARY.
ORA-16159: Cannot change protected standby destination attributes
Cause: An attempt was made to change the LGWR/ARCH or SYNC/ASYNC
attributes for a destination that is participating in the standby protection mode of the
database.
ORA-16160: Cannot change protected standby database configuration
Cause: An attempt was made to change the standby database configuration when the
primary database is in standby protected mode.
Action: The standby database must be added to the configuration before the primary
database is opened.
ORA-16161: Cannot mix standby and online redo log file members for group string
Cause: An attempt was made to add a log file member that did not match the other
member types. This problem typically occurs when adding a standby log file member
to an online redo log file group, or adding an online redo log file member to a
standby redo log file group.
Action: Verify the log file group type using the TYPE column of the V$LOG fixed
view.
ORA-16162: Cannot add new standby databases to protected configuration
Cause: An attempt was made to enable a new standby database destination when the
primary database is in standby protected mode.
Action: The standby database must be added to the configuration before the primary
database is opened.
ORA-16163: LGWR network server host attach error
Cause: The LGWR network server could not attach to remote host
Action: The alert log contains more problem-specific information
ORA-16164: LGWR network server host detach error
Cause: The LGWR network server could not detach from remote host
ORA-16165: LGWR failed to hear from network server
Cause: The LGWR lost its connection to the network server
ORA-16166: LGWR network server failed to send remote message
Cause: The LGWR network server could not communicate with the remote host
ORA-16167: LGWR network server could not switch to non-blocking mode

Cause: The LGWR network server could not switch to non-blocking mode
ORA-16168: LGWR network server could not switch to blocking mode
Cause: The LGWR network server could not switch to blocking mode
ORA-16169: LGWR network server invalid parameters
Cause: The LGWR network server could not switch to blocking mode
ORA-16170: Terminal recovery may have left the database in an inconsistent state
Cause: When terminal recovery is invoked in a standby database without
synchronous log shipping, in the rare case of the recovery session being in an
unrecoverable state, terminal recovery cannot bring the standby database to a
consistent SCN boundary if the primary database continues to have redo thread(s)
open.
Action: Continue standby recovery with additional log shipping from primary.
ORA-16171: RECOVER...FINISH not allowed due to gap for thr string, seq stringstring
Cause: See alert log for more details
Action: Copy missing archived logs from primary or another standby. Register the
logs and reissue the RECOVER...FINISH command. If the logs are not available, issue
the ALTER DATABASE RECOVER MANAGED STANDBY SKIP command to ignore
the standby redo log files.
ORA-16172: archive logs detected beyond Terminal End-Of-Redo
Cause: An attempt to archive a Terminal End-Of-Redo archive log to a remote
destination failed due the existence, at the remote site, of archive logs containing
REDO in the future of the Terminal EOR.
Action: n/a
ORA-16173: incompatible archival network connections active
Cause: One of two situations can cause this error: 1) An attempt to start a Terminal
Incomplete Recovery operation failed due to an active Remote File Server process
detected. 2) An attempt to archive a Terminal End-Of-Redo archive log to a remote
destination failed due to an active Remote File Server process at the remote site. An
active Remote File Server (RFS) process implies connectivity with the primary
database which may indicate that a Terminal Incomplete Recovery operation is not
warrented.
Action: Verify the Managed Standby environment and re-evaluate the necessity of a
Terminal Incomplete Recovery operation.
ORA-16174: user requested thread/sequence termination of managed recovery
Cause: The managed standby database recovery operation has been terminated per
user specified THROUGH THREAD/SEQUENCE option of the RECOVER
MANAGED STANDBY DATABASE statement.
ORA-12700 to ORA-19400 69-211
ORA-16175: cannot shut down database when media recovery is active

Cause: An attempt was made to shut down a standby database while media recovery
was active.
Action: Cancel media recovery to proceed with the shutdown.
ORA-16176: background dictionary build cannot be running
Cause: The background process dedicated to dictionary build is active.
Action: wait and try it later.
ORA-16177: media recovery is not required
Cause: The THROUGH LAST SWITCHOVER clause of the ALTER DATABASE
RECOVER MANAGED STANDBY DATABASE was specified and the database has
been recovered to the most recent End-Of-Redo marker. All known archived logs
have been applied. Managed recovery is not required.
Action: No action is necessary. The standby database may be activated as a new
primary or may continue as a standby.
ORA-16178: Cannot specify remote destinations in manual archiving mode
Cause: The database is operating in manual archiving mode. Remote archivelog
destinations are not allowed in this mode.
Action: Use the ALTER DATABASE ARCHIVELOG command to place the database
in automatic ARCHIVELOG mode, or defer the archivelog destinations that specify
the SERVICE= attribute.
ORA-16179: incremental changes to "string" not allowed with SPFILE
Cause: Incremental changes to a log_archive_dest_n parameter cannot be made when
using an SPFILE.
Action: Specify either LOCATION or SERVICE plus all other attributes to be set in
one ALTER SYSTEM/SESSION SET command.
ORA-16180: number of processes specified is too large
Cause: The number of server processes available for Logical Standby is currently
limited to 1024 LogMiner processes and 1024 apply processes or a total of 2048.
Action: Retry with a lower value.
ORA-16181: SGA specified for Logical Standby is too large
Cause: MAX_SGA is larger than 75% of the larger of initialization parameters
SHARED_POOL_SIZE, MEMORY_TARGET, and SGA_TARGET.
Action: Specify the value of MAX_SGA to be less than 75% of the maximum of
SHARED_POOL_SIZE, MEMORY_TARGET, and SGA_TARGET.
ORA-16182: Internal error on internal channel during remote archival
Cause: An internal error was encountered on the internal channel between LGWR
and Network Server.
Action: No action is required, as an attempt will be made to re-archive the file that
had this failure during archival.
ORA-16184: DB_UNIQUE_NAME string hashes to the same value as
DB_UNIQUE_NAME string
Cause: The internal hash value generated for one DB_UNIQUE_NAME collided with
the hash value of another DB_UNIQUE_NAME.
Action: Slightly modify one of the DB_UNIQUE_NAMEs so it hashes to a different

value.
ORA-16185: REMOTE_ARCHIVE_ENABLE and LOG_ARCHIVE_CONFIG
mutually exclusive
Cause: Both the REMOTE_ARCHIVE_ENABLE and LOG_ARCHIVE_CONFIG
parameters are defined in the initialization file and they are mutually exclusive.
Action: The REMOTE_ARCHIVE_ENABLE parameter has been made obsolete. Use
only the LOG_ARCHIVE_CONFIG parameter.
ORA-16186: Modifying LOG_ARCHIVE_CONFIG requires SID='*' qualifier
Cause: The setting for the LOG_ARCHIVE_CONFIG parameter must be exactly the
same on all RAC instances so the SID='*' qualifier is required.
Action: Re-enter the command using the SID='*' qualifier.
ORA-16187: LOG_ARCHIVE_CONFIG contains duplicate, conflicting or invalid
attributes
Cause: The LOG_ARCHIVE_CONFIG parameter was specified with duplicate,
conflicting or invalid attributes.
Action: Check the documentation regarding the correct specification of the
LOG_ARCHIVE_CONFIG parameter.
ORA-16188: LOG_ARCHIVE_CONFIG settings inconsistent with previously
started instance
Cause: The settings for the LOG_ARCHIVE_CONFIG parameter are inconsistent with
the settings of a previously started instance. The settings for this parameter must be
exactly the same for all instances.
Action: Make sure all instances use the exact same LOG_ARCHIVE_CONFIG
settings.
ORA-16191: Primary log shipping client not logged on standby
Cause: An attempt to ship redo to standby without logging on to standby or with
invalid user credentials.
Action: Check that primary and standby are using password files and that both
primary and standby have the same SYS password. Restart primary and/or standby
after ensuring that password file is accessible and
REMOTE_LOGIN_PASSWORDFILE initialization parameter is set to SHARED or
EXCLUSIVE.
ORA-16192: Primary and standby network integrity mismatch
Cause: Standby wants sqlnet network integrity for redo shipment which is not
configured properly at the primary.
Action: Check sqlnet.ora documentation regarding how to setup network integrity
and set it up identically on both primary and standby. Restart primary and/or
standby.
ORA-16193: Primary and standby network encryption mismatch
Cause: Standby wants sqlnet network encryption for redo shipment which is not
configured properly at the primary.
Action: Check sqlnet.ora documentation regarding how to setup network encryption
and set it up identically on both primary and standby. Restart primary and/or
standby.
ORA-12700 to ORA-19400 69-213
ORA-16194: Modifying DB_UNIQUE_NAME requires SID='*' qualifier

Cause: The setting for the DB_UNIQUE_NAME parameter must be exactly the same
on all RAC instances so the SID='*' qualifier is required.
Action: Re-enter the command using the SID='*' qualifier.
ORA-16195: DG_CONFIG requires DB_UNIQUE_NAME be explicitly defined
Cause: The DG_CONFIG attribute of the LOG_ARCHIVE_CONFIG parameter can
only be used if the DB_UNIQUE_NAME parameter has been explicitly defined.
Action: Explicitly define a valid DB_UNIQUE_NAME.
ORA-16196: database has been previously opened and closed
Cause: The instance has already opened and closed the database, which is allowed
only once in its lifetime.
Action: Shut down the instance.
ORA-16197: Invalid DB_UNIQUE_NAME parameter specification
Cause: The DB_UNIQUE_NAME parameter has an invalid specification. The
DB_UNIQUE_NAME parameter has a maximum length of 30 characters and the only
characters allowed are alpha-numeric characters and "_", "$" and "#".
Action: Check the documentation and re-enter the parameter.
ORA-16198: Timeout incurred on internal channel during remote archival
Cause: A timeout was incurred during remote archival.
Action: No action is required, as an attempt will be made to re-archive the file that
had this failure during archival.
ORA-16199: Terminal recovery failed to recover to a consistent point
Cause: See alert log for more details
Action: Try to resolve the problem. Retry terminal recovery. If the problem occurs
repeatedly and cannot be resolved, call Oracle support.
ORA-16200: Skip procedure requested to skip statement
Cause: Logical standby called a skip procedure that requested for a particular
statement not to be applied.
ORA-16201: Skip procedure requested to apply statement
statement to be applied.
ORA-16202: Skip procedure requested to replace statement
statement to be replaced with a new statement.
ORA-16203: Unable to interpret skip procedure return values
Cause: The skip procedure returned conflicting or invalid values.
Action: Ensure that the new_statement output parameter is non-NULL when

returning DBMS_LOGSTDBY.SKIP_ACTION_REPLACE and NULL otherwise. Also
ensure SKIP_ACTION is specified correctly.
ORA-16204: DDL successfully applied
Cause: A DDL statement has successfully commited on the logical standby database.
ORA-16205: DDL skipped due to skip setting
Cause: A setting in the logical standby skip table indicates that this type of DDL
should always be skipped.
ORA-16206: database already configured as Logical Standby database
Cause: This database has been previously configured as a Logical Standby database.
A Logical Standby database is not capable of processing the requested operation.
Action: Ensure that you entered the command on the correct database as this database
is a Logical Standby and is not capable of servicing the request.
ORA-16207: Logical standby dictionary build not permitted.
Cause: A dictionary build is currently in progress. Only one build can be active at a
time.
Action: Wait for the active build to complete before invoking a new build.
ORA-16208: Logical standby dictionary build failed to start.
Cause: Failure to start the logical standby dictionary build process (LSP1)
Action: Check the accompanying messages, and the background process trace file.
Correct 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-16209: Logical standby dictionary build failed to complete.
Cause: The logical standby dictionary build process terminated abnormally.
ORA-16210: Logical standby coordinator process terminated with error
Cause: The logical standby coordinator process terminated abnormally.
ORA-16211: unsupported record found in the archived redo log
Cause: Log apply services encountered a record in the archived redo log that could
not be interpreted.
Action: 1. Use DBMS_LOGSTDBY.INSTANTIATE_TABLE to re-create the table on
the standby database or simply drop the table if it's unimportant. 2. ALTER
ORA-12700 to ORA-19400 69-215
DATABASE START LOGICAL STANDBY APPLY; 3. Examine the current_scn

column in the DBA_LOGSTDBY_EVENTS view to determine which log file contains
the unsupported record. 4. Provide the log file to Oracle Support Services.
ORA-16212: number of processes specified for SQL Apply is too great
Cause: Logical standby apply engine was started with more processes requested than
are available.
Action: Adjust the values of the initialization parameters PROCESSES or the
MAX_SERVERS parameter seen in the DBA_LOGSTDBY_PARAMETERS view. If
you did not specify MAX_SERVERS, but instead specified PREPARE_SERVERS and
APPLY_SERVERS through the dbms_logstdby.apply_set procedure, you will need to
decrease either one or both of them.
ORA-16213: ddl encountered, stopping apply engine
Cause: stop_on_ddl callout specified and DDL was encountered.
Action: Either disable stop_on_ddl callout or remove DDL.
ORA-16214: apply stalled for apply delay
Cause: A delay has been specified on the primary database for this destination.
Action: Either turn off the delay on the primary or use
DBMS_LOGSTDBY.APPLY_UNSET('APPLY_DELAY'); to override.
ORA-16215: history metadata inconsistency
Action: This is an internal error. Contact Oracle support.
ORA-16216: Log stream sequence error
Cause: The log stream being processed did not follow the last processed stream.
Action: If the database is in an active configuration, issue an ALTER DATABASE
START LOGICAL STANDBY APPLY NEW PRIMARY command to synchronize log
stream data with the current primary database. If the database is not in an active
configuration, manually add the next dictionary-begin log file that followed the
previous log stream.
ORA-16217: prepare to switchover has not completed
Cause: An ALTER DATABASE PREPARE TO SWITCHOVER command was issued,
but the prepare activity did not complete.
Action: Verify that the standby was prepared properly. You may cancel the prepare
and perform an unprepared switchover which requires a database link to complete.
Or reissue the prepare operation on the standby.
ORA-16218: This database is already preparing to switch over.
Cause: The database was already preparing to switch over and was not able to
accomodate another prepare attempt.
Action: Cancel the current prepare attempt with the ALTER DATABASE PREPARE
TO SWITCHOVER CANCEL command, then reissue the prepare request.
ORA-16219: This database is not preparing to switch over.
Cause: The database was not preparing to switch over. Therefore, it was not possible
to cancel the SWITCHOVER command.
Action: Preparing for the SWITCHOVER command can be accomplished with the
ALTER DATABASE PREPARE TO SWITCHOVER command.
ORA-16220: no failed transaction found

Cause: No failed transaction was found.
Action: Retry the ALTER DATABASE START LOGICAL STANDBY APPLY
command without the SKIP FAILED TRANSACTION option.
ORA-16221: history table synchronization error
ORA-16222: automatic Logical Standby retry of last action
Cause: A failure occurred while running Logical Standby apply. A new attempt is
automatically being made by Logical Standby apply.
Action: No action is necessary. This informational statement is provided to record the
ORA-16223: DDL skipped, unsupported in current version
Cause: The given DDL statement was not supported in the current version of Logical
Standby and was skipped.
ORA-16224: Database Guard is enabled
Cause: Operation could not be performed because database guard is enabled
Action: Verify operation is correct and disable database guard
ORA-16225: Missing LogMiner session name for Capture
Cause: An attempt was made to register the log file for Capture without a specified
LogMiner session name.
Action: Specify a valid LogMiner session name to which the log file will be registered.
ORA-16226: DDL skipped due to lack of support
Cause: Logical Standby does not support this type of DDL in this version, so the DDL
is skipped.
Action: The DBA may apply the DDL explicitly at a later time or a procedure to
handle this type of DDL can be created. see DBMS_LOGSTDBY.SKIP procedure for
details.
ORA-16227: DDL skipped due to missing object
Cause: A table or other database object upon which this DDL depended was not
defined on the Logical Standby database.
ORA-16228: Insufficient recovery for logical standby
Cause: Insufficient amount of recovery was run for logical standby instantiation.
Action: Continue to recover the database using ALTER DATABASE RECOVER
MANAGED STANDBY DATABASE.
ORA-12700 to ORA-19400 69-217
ORA-16229: PDML child string string string for parent string string string cannot be
skipped.
Cause: A request was made to skip a parallel DML child transaction id. This is not
supported.
Action: Using the DBMS_LOGSTDBY.UNSKIP_TRANSACTION procedure, remove
the child transaction id, then specify the parent transaction id using
DBMS_LOGSTDBY.SKIP_TRANSACTION if appropriate.
ORA-16230: committing transaction string string string
Cause: Logical Standby apply was committing changes for the given transaction.
ORA-16232: adding Logical Standby skip entry for table string.string
Cause: Table was previously unsupported due to datatype or storage attribute
definitions. Table is now capable of being supported.
Action: To have Logical Standby maintain the table, import that table directly from
the primary.
ORA-16233: The table string.string is unsupported now
Cause: Table was previously supported but now is unsupported due to altered
datatype or storage attribute definitions.
Action: None
ORA-16234: restarting to reset Logical Standby apply
Cause: Logical Standby encountered a work load that required a restart to properly
reschedule.
ORA-16235: DDL skipped because import has occurred
Cause: An object was exported from the primary database and imported into the
Logical Standby database. This DDL occurred before the export.
ORA-16236: Logical Standby metadata operation in progress
Cause: The requested operation failed because an incompatible Logical Standby
metadata operation such as DBMS_LOGSTDBY.SET_TABLESPACE,
DBMS_LOGSTDBY.APPLY_SET or DBMS_LOGSTDBY.INSTANTIATE_TABLE was
still running.
Action: Wait for the incompatible Logical Standby metadata operation to finish, then
reenter or respecify the operation.
ORA-16237: SGA specified for Logical Standby is too small
Cause: MAX_SGA must be at least 10 Megabytes for proper functioning of Logical
Standby.
Action: Specify the value of MAX_SGA to be greater than or equal to 10Mb.
Alternatively, increase the shared_pool_size/sga_target so that 1/4 of it will amount
to 10 Megabytes.
ORA-16238: attempt to use version 9 log

Cause: Version 9 log files are not supported.
Action: Use log files of a supported version.
ORA-16239: IMMEDIATE option not available without standby redo logs
Cause: The IMMEDIATE option cannot be used without standby redo logs.
Action: Do not specify the IMMEDIATE option unless standby redo logs are being
used.
ORA-16240: Waiting for log file (thread# string, sequence# string)
Cause: Process is idle waiting for additional log file to be available.
ORA-16241: Waiting for gap log file (thread# string, sequence# string)
Cause: Reader process was idle waiting for the log file to fill the log sequence gap.
ORA-16242: Processing log file (thread# string, sequence# string)
Cause: Reader process was processing the log file.
ORA-16243: paging out string bytes of memory to disk
Cause: Builder process is paging out momery to free up space in lcr cache.
ORA-16245: change db_name to string in the server-side parameter file (SPFILE)
Cause: An ALTER DATABASE RECOVER TO LOGICAL STANDBY new-dbname
command was successfully executed without a modifiable server parameter file
(SPFILE).
Action: The server-side parameter file must be modified so that db_name is set to the
given name before mounting the database again. You must do this by executing
CREATE PFILE FROM SPFILE, editing the resulting text parameter file, and then
executing CREATE SPFILE FROM PFILE.
ORA-16246: User initiated abort apply successfully completed
Cause: SQL Apply was stopped using the abort option.
ORA-16247: DDL skipped on internal schema
Cause: Logical Standby ignores DDLs on internal schemas such as SYS and SYSTEM.
For a complete list of internal schemas ignored by Logical Standby perform the
following query: SELECT owner FROM dba_logstdby_skip WHERE statement_opt =
'INTERNAL SCHEMA'.
ORA-12700 to ORA-19400 69-219
ORA-16248: RFS connections not permitted during Terminal Apply

Cause: Writes by RFS are not permitted while Logical Standby is performing
Terminal Apply.
Action: Permit any outstanding Logical Standby operations to complete.
ORA-16249: Terminal apply failed to complete during failover
Cause: The logical standby coordinator process terminated abnormally."
Action: Examine the DBA_LOGSTDBY_EVENTS view for the reason behind the
abnormal shutdown, and resolve accordingly. Once the problem has been rectified,
reissue the ALTER DATABASE ACTIVATE LOGICAL STANDBY DATABASE
command to complete the failover.
ORA-16250: Failed to acquire starting scn of new log stream
Cause: The starting SCN for the new log stream could not be determined.
Action: Please reissue the ACTIVATE LOGICAL STANDBY DATABASE command.
ORA-16251: LSP1 Background Build not permitted
Cause: The LSP1 background process is not permitted to start because it had
previously been attempted.
ORA-16252: Rebuild operation not permitted
Cause: The REBUILD operation is not permitted.
Action: Only on a primary database that has failed to complete the LogMiner
dictionary build may the REBUILD operation take place. Reissue the ACTIVATE
LOGICAL STANDBY DATABASE command if it previously failed to complete.
ORA-16253: Logical standby cannot start due to a prior, incomplete operation
Cause: A failure during a prior failover or configuration-related operation left the
logical standby in an inconsistent state.
Action: Identify and reissue the operation before attempting to restart the logical
standby apply engine.
ORA-16254: change db_name to string in the client-side parameter file (pfile)
Cause: An ALTER DATABASE RECOVER TO LOGICAL STANDBY new-dbname
command was successfully executed without a server parameter file (spfile).
Action: The client-side parameter file must be edited so that db_name is set to the
given name before mounting the database again.
ORA-16255: Log Auto Delete conflicts with another LogMiner session
Cause: Log Auto Delete cannot be on while another LogMiner session is running on
the same database.
Action: Start Logical Standby without Log Auto Delete or destroy other LogMiner
sessions first.
ORA-16256: Failure to complete standby redo log file archival after failover
Cause: The standby redo log files processed during the failover of a logical standby
were not archived.
Action: Execute DBMS_LOGSTDBY.REBUILD to reattempt the archival.
ORA-16257: Switchover initiated stop apply successfully completed

Cause: SQL Apply was stopped because of a switchover.
ORA-16258: marking index unusable due to a constraint violation
Cause: A constraint violation occurred during the apply of a direct path load. The
index will be marked unusable and the apply will be restarted.
Action: No action necessary. See alert log for index schema and name.
ORA-16259: Switchover to logical standby requires a log archive destination
Cause: A valid log archive destination was not found to which the local system could
archive the end of redo (EOR) log file. A minimum of one destination is required.
Action: Ensure all log archive destinations are properly configured and, if applicable,
have network connectivity before reissuing the ALTER DATABASE COMMIT TO
SWITCHOVER TO LOGICAL STANDBY DDL operation.
ORA-16260: Waiting to replace partial or corrupt log file (thread# string, sequence#
string)
Cause: LogMiner Reader process reached the end of a partial log file or encountered a
corrupted block. It is now waiting for the log file to be recovered and reregistered.
Action: No action necessary. Once the fetch archive log (FAL) archiver replaces the
log file, standby will automatically restart to process the replaced file.
ORA-16261: Identification key mismatch for table "string"."string".
Cause: Internal error in SQL Apply.
ORA-16262: Invalid value specified for Logical Standby parameter
Cause: The value specified in APPLY_SET is invalid for the parameter.
Action: Specify correct parameter value. Please refer to documentation on
DBMS_LOGSTDBY PL/SQL package for details.
ORA-16263: Dynamic parameters can only be set on SQL apply instance
Cause: Attempt to set a Logical standby dynamic parameter on an instacne other than
where SQL apply coordinator is running.
Action: Connect to the instance where SQL apply coordinator is running and reissue
the statement.
ORA-16264: invalid value for PREPARE_SERVERS parameter
Cause: attempt to set PREPARE_SERVERS parameter to zero or to a value which
would require MAX_SERVERS to be increased.
Action: set PREPARE_SERVERS parameter to a non zero value and or increase
MAX_SERVERS parameter accordingly.
ORA-16265: Unsupported PL/SQL procedure encountered
Cause: Apply encountered an unsupported procedure from an Oracle supplied
PL/SQL package that is otherwise supported
Action: Either add a skip rule for this procedure or manually apply the procedure and
restart apply skipping the failed transaction Please refer to documentation on the
PL/SQL package for details.
ORA-12700 to ORA-19400 69-221
ORA-16266: Cannot instantiate a Logical Standby from another Logical Standby

Cause: An instantiation of a Logical Standby has been attempted for another database
with the Logical Standby role, which is not supported.
Action: Instantiate a Logical Standby database only from a Primary Database.
ORA-16267: Cannot instantiate a Logical Standby during a switchover
Cause: An instantiation of a Logical Standby has been attempted for a primary
database that is in the middle of a switchover.
Action: Execute ALTER DATABASE PREPARE TO SWITCHOVER CANCEL to
cancel the switchover, and attempt the instantiation again.
ORA-16268: user procedure processing of logical standby apply PL/SQL
Cause: A user-provided stored procedure was called to inspect a PL/SQL statement
prior to the statement being processed.
Action: No action necessary, this informational statement is provided to record user
involvement in the processing of a statement. Additional information can be found in
the DBA_LOGSTDBY_EVENTS and the DBA_LOGSTDBY_SKIP views.
ORA-16269: PL/SQL procedure skipped due to failure on primary database
Cause: Because the PL/SQL procedure failed when executed on the primary
database, it could not be executed on the standby database.
Action: This informational statement is provided to record the event for diagnostic
purposes. The failed PL/SQL procedure needs to be investigated to ensure it did not
commit interesting data before it failed.
ORA-16270: PL/SQL procedure skipped due to unmaintained standby objects
Cause: Because the PL/SQL procedure manipulated objects not being maintained by
the standby database, it was skipped.
ORA-16271: PL/SQL successfully applied
Cause: A PL/SQL procedure was successfully applied on the logical standby
database.
ORA-16272: PL/SQL procedure skipped due to skip setting
Cause: A setting in the logical standby skip table indicated that this PL/SQL
procedure should always be skipped.
ORA-16273: invalid value for APPLY_SERVERS parameter
Cause: attempt to set APPLY_SERVERS parameter to zero or to a value which would
require MAX_SERVERS to be increased.
Action: set APPLY_SERVERS parameter to a non zero value or increase
MAX_SERVERS parameter accordingly.
ORA-16274: failure to perform operation on all Oracle RAC instances
Cause: One or more instances encountered an error while performing an operation.
Action: Ensure every instance in the Oracle RAC meets the requirements for the
operation, and retry the operation.
ORA-16275: prior failed CTAS detected and pre-existing table dropped
Cause: During the processing of a CTAS operation, an existing empty table with the
same name and attributes as the CTAS source table was found, and the table was
dropped.
ORA-16276: specified database link does not correspond to primary database
Cause: The database link specified to DBMS_LOGSTDBY.INSTANTIATE_TABLE did
not link to the primary database for this logical standby database.
Action: Specify a database link that corresponds to the primary database for this
logical standby database. The link should have privileges to read and lock the table
being instantiated, as well as the SELECT_CATALOG_ROLE.
ORA-16277: specified table is not supported by logical standby database
Cause: A call was made to DBMS_LOGSTDBY.INSTANTIATE_TABLE to instantiate
an unsupported table on the logical standby database. Tables with unsupported data
types cannot be replicated to a logical standby database.
Action: Specify a table which is not listed in the
DBA_LOGSTDBY_UNSUPPORTED_TABLE view.
ORA-16278: specified table has a multi-object skip rule defined
Cause: A table that is instantiated via DBMS_LOGSTDBY.INSTANTIATE_TABLE
must not have any skip rules defined with wildcard characters.
Action: Remove or rewrite any skip rules defined for the specified table so that they
no longer contain wildcard characters, or no longer affect the specified table.
ORA-16279: supplied dblink does not have sufficient privileges
Cause: A dblink was specified that lacked one or more of the CONNECT,
RESOURCE, or SELECT_CATALOG_ROLE roles or that connects to a user with
insufficient privileges to lock the table.
Action: Grant the necessary privileges to the dblink and the user to which the dblink
connects and retry the operation.
ORA-16280: cannot change master key on a logical standby database
Cause: An attempt was made to change the master key for transparent data
encryption on a logical standby database.
Action: Set GUARD to NONE and reissue the command. This prevents you from
replicating tables with encrypted columns from the primary database.
ORA-16281: missing identification key for table "string"."string".
Cause: No identification key was created for specified table.
Action: Create a primakey key or unique index for specified table.
ORA-16282: operation not permitted during rolling upgrade
Cause: An operation was attempted that is not supported during a rolling upgrade.
Action: Retry the operation upon completion of the upgrade.
ORA-12700 to ORA-19400 69-223
ORA-16283: operation not permitted on non-apply instance

Cause: An operation was attempted that is not supported since it requires a running
logical apply on the local instance.
Action: Retry the operation on the instance on which the apply engine is running.
ORA-16284: timed out waiting for an in-progress operation to complete
Cause: An operation timed out waiting for another operation to complete.
Action: Retry the operation when the in-progress operation has completed.
ORA-16285: operation not permitted due to inconsistent role state
Cause: A prior attempt to change the role of this database has failed before the new
role state could be fully committed.
Action: Retry the previously attempted role-related operation before attempting the
current operation.
ORA-16286: operation not permitted due to lack of synchronized destination
Cause: A synchronized log archive destination was not found to which the end-ofredo log file could be archived.
Action: Before re-attempting the operation, wait at least one minute for the Remote
File Server to automatically recover any missing log files or manually recover and
register any missing log files with logical standby.
ORA-16287: operation not permitted due to active apply state
Cause: An operation was attempted that was not supported while the logical standby
database had an active apply state.
Action: Confirm the procedures used to configure the logical standby database.
Procedures which attempt to reconfigure a logical standby database for a new
primary database may encounter this error if an error in a preliminary step was
encountered.
ORA-16288: DDL skipped due to missing edition "string"
Cause: The edition in which the DDL was performed on the primary did not exist on
the standby database.
ORA-16289: unable to access Pluggable Database "string"
Cause: Logical standby attempted to access a Pluggable Database that did not exist.
Action: Create or plug in the specified Pluggable Database or add an appropriate skip
rule and then restart logical standby.
ORA-16290: cannot alter the session logical replication state within a transaction
Cause: A transaction was already in progress.
Action: Commit or rollback the transaction and then reexecute.
ORA-16300: LSBY architected tracing event
ORA-16302: extended data type support is not supported for specified table
Cause: A call was made to DBMS_LOGSTDBY.EDS_ADD_TABLE for a table that was
not supported for such an operation. The table either does not have a primary key or
it has a data type not supported by this procedure.
Action: Specify a table for which support exists in EDS_ADD_TABLE.
ORA-16303: specified table already has extended data type support

Cause: A call was made to DBMS_LOGSTDBY.EDS_ADD_TABLE for a table that
already had EDS added on the local database.
Action: None
ORA-16304: procedure must first be called on primary database
Cause: A call was made to DBMS_LOGSTDBY.EDS_ADD_TABLE on a logical
standby database without having first called it on the primary database.
Action: Call DBMS_LOGSTDBY.EDS_ADD_TABLE on the primary database and
then retry on the standby.
ORA-16305: procedure not supported on a logical standby
Cause: A call was made to DBMS_LOGSTDBY.EDS_EVOLVE_TABLE on a logical
standby database which can only be called on a primary database
Action: Call DBMS_LOGSTDBY.EDS_EVOLVE_TABLE on the primary database
ORA-16306: specified table does not have a primary key
Cause: A call was made to DBMS_LOGSTDBY.EDS_ADD_TABLE for a table that did
not have a primary key.
Action: Add a primary key and retry the operation.
ORA-16307: TSE key string successfully applied
Cause: An ALTER SYSTEM SET ENCRYPTION KEY statement was successfully
committed on the logical standby database.
ORA-16308: specified table has extended data type support
Cause: A call was made to DBMS_LOGSTDBY.INSTANTIATE_TABLE for a table that
is being maintained by extended data type support.
Action: Call DBMS_LOGSTDBY.EDS_REMOVE_TABLE followed by either
DBMS_LOGSTDBY.EDS_ADD_TABLE or a retry of the operation.
ORA-16309: extended data type support evolve operation not yet started
Cause: A call was made to finish an extended data type support evolve operation
without having first started the operation.
Action: Call DBMS_LOGSTDBY.EDS_EVOLVE_MANUAL with START option and
then retry.
ORA-16310: extended data type support evolve operation in progress
Cause: An extended data type support evolve operation was started but not yet
completed.
Action: Wait a few seconds and retry the command if automatic evolve has been
enabled or call DBMS_LOGSTDBY.EDS_EVOLVE_MANUAL with the FINISH option
and then retry.
ORA-16311: materialized view log already exists
Cause: A call was made to DBMS_LOGSTDBY.EDS_ADD_TABLE for a table with a
LOB that requires the creation of a specifically-defined materialized view log but one
already exists.
Action: Drop the existing materialized view log and retry the operation.
ORA-12700 to ORA-19400 69-225
ORA-16330: error in container "string"

Cause: An operation was attempted on a container and an error occurred.
Action: Address the failure condition and then retry.
ORA-16331: container "string" is not open
Cause: An operation was attempted on a container. However, the container was not
open.
Action: Open the container and then retry.
ORA-16332: logical standby encountered non-fatal error ORA-string during DDL
execution
Cause: Logical standby apply encountered a non-fatal error during DDL execution
and continued to process subsequent transactions.
Action: This error is informational only. No user action is required.
ORA-16333: _MAX_LOG_LOOKBACK parameter not sufficiently larger than
MAX_SGA
Cause: _MAX_LOG_LOOKBACK or MAX_SGA parameter was set to a value that
will lead to decreased performance.
Action: Reset parameters such that _MAX_LOG LOOKBACK is at least 5 times the
value of MAX_SGA.
ORA-16334: skip procedure does not exist
Cause: The specified skip procedure did not exist.
Action: Ensure that the specified skip procedure exists and is accessible by the calling
user.
ORA-16400: quota attributes are not allowed with DB_RECOVERY_FILE_DEST
Cause: Quota attributes for the destination parameters are not allowed when the
parameter DB_RECOVERY_FILE_DEST is defined.
ORA-16401: archive log rejected by Remote File Server (RFS)
Cause: An attempt was made to re-archive an existing archive log.
Action: See alert log and trace file for more details. No action is necessary. This is an
informational statement provided to record the event for diagnostic purposes.
ORA-16402: TRANSPORT=ONDEMAND is unsupported.
Cause: The ARCHIVELOG destination TRANSPORT=ONDEMAND attribute was
specified on the primary database.
Action: Use of the TRANSPORT=ONDEMAND is no longer supported. Remove this
attribute from the LOG_ARCHIVE_DEST_n initialization parameter.
ORA-16403: shut down in progress - remote connection is not permitted
Cause: A redo transport session could not be started because the database was
shutting down.
Action: Wait for the remote instance to be restarted, or contact your DBA.
ORA-16406: primary and standby database software version mismatch
Cause: The primary and standby databases were not running compatible versions of
Oracle server software.
Action: Install the correct Oracle server software and try again.
ORA-16407: An archive log from an earlier redo branch has been rejected
Cause: An archive log from a redo branch that is earlier than the one that the standby
database is currently applying was rejected.
ORA-16408: An archive log from an incompatible redo branch has been rejected.
Cause: An archive log from a redo branch that is incompatible with the one that the
standby database is currently applying was rejected.
ORA-16409: archive log switchover reference number mismatch
Cause: The archive log switchover reference numbers of the primary and standby
database did not match. Remote archival of redo log files is not allowed to
incompatible standby database instances.
ORA-16411: TRANSPORT=ONDEMAND is unsupported
Cause: The archivelog destination TRANSPORT=ONDEMAND attribute was
ORA-16416: No viable stringswitchover targets available
Cause: Switchover failed because no standby databases of the appropriate type were
available.
Action: Check the alert log for errors, correct the problem and retry the switchover.
ORA-16417: Activation occurred after recovery from standby redo log files; a full
database backup is required
Cause: Activation occurred after recovery from standby redo log files.
Action: Take a full database backup.
ORA-16419: Snapshot standby must be converted to a physical standby database.
Cause: The database was not a physical standby database.
Action: Convert to physical standby database and retry the operation.
ORA-12700 to ORA-19400 69-227
ORA-16420: fast-start failover target cannot be converted to snapshot standby

Cause: The database chosen for conversion to a snapshot standby was the fast-start
failover target standby database.
Action: Choose another physical standby database and retry the operation.
ORA-16424: RECOVER FINISH cannot complete due to a redo gap.
Cause: RECOVER FINISH failed because there was a redo gap on the standby
database.
Action: Resolve redo gap or issue ALTER DATABASE ACTIVATE STANDBY
DATABASE to perform an immediate failover with some data loss.
ORA-16425: RECOVER FINISH cannot be issued when recovery branch string is
not the target branch string.
Cause: RECOVER FINISH failed because a new branch existed on the physical
standby database.
Action: Issue real-time apply recovery and see if recovery can proceed on the new
branch by checking if logs on the new branch are applied by recovery. If so, issue
another RECOVER FINISH. Otherwise, issue ALTER DATABASE ACTIVATE
STANDBY DATABASE.
ORA-16426: Recovery requested an incorrect log from which to apply redo data.
Cause: Media recovery selected an incorrect log.
Action: Verify that the appropriate log has been properly registered and restart media
recovery.
ORA-16427: Redo gap is too large to resolve.
Cause: The redo transport lag at this database was too large for automatic redo gap
detection to take place.
Action: Re-create this standby database from a current backup copy of the primary
database.
ORA-16431: cannot expand control file
Cause: Additional redo log threads were added on the primary database after the
standby control file was created.
Action: Shut down the standby database and replace the control file with a new
standby control file from the primary database or change the COMPATIBLE
parameter to 10.2.0 or above and restart the standby database.
ORA-16432: inconsistent set of logs applied at a standby database
Cause: Redo apply stopped because it detected an inconsistency in the progression of
the SCNs. If this database is a bystander standby database, this is most likely due to a
failover operation in which incompatible logs were applied from the old and new
primary databases.
Action: Determine the STANDBY_BECAME_PRIMARY_SCN by selecting it from V
$DATABASE on the new primary database. Then, flashback the target database to
this SCN and use RMAN to delete all archive logs at or beyond this SCN. Finally,
fetch all terminal end of redo (EOR) logs corresponding to the failover operation from
the new primary and register all these logs at the target database. Restart redo apply.
ORA-16433: The database or pluggable database must be opened in read/write

mode.
Cause: An attempt was made to open the database or pluggable database in read-only
mode after an operation that requires the database or pluggable database be opened
in read/write mode.
Action: Open the database in read/write mode. The database can then be opened in
read-only mode.
ORA-16434: archive log for branch string thread string sequence string cannot be
queued
Cause: An archive log needed by the standby database to resolve a redo gap was not
found on the source database. This is a fatal situation during a switchover or far sync
instance assisted failover because the source database waits for the target standby to
be clear of all archive log gaps before allowing the operation to proceed. If a redo gap
cannot be resolved during these operations, the operation cannot succeed so it must
be failed.
Action: If the specified log is listed in V$ARCHIVED_LOG for the DEST_ID of the
local destination on the source database but no longer exists at that location on disk,
the archived log can be copied back to that location to allow gap processing to
automatically resolve the gap. If the specified log has been purged from V
$ARCHIVED_LOG, the archived log can be copied to disk on either the source or
destination database and registered using the ALTER DATABASE REGISTER OR
REPLACE LOGFILE command.
ORA-16436: ALTER DATABASE ... RECOVER FINISH could not start
Cause: ALTER DATABASE ... RECOVER FINISH failed to start because the standby
database was missing redo changes below the checkpoint of data files.
Action: Issue ALTER DATABASE ACTIVATE STANDBY DATABASE command
instead.
ORA-16437: No active coordinator RFS for current operation
Cause: The coordinator Remote File Server (RFS) for this parallel archival either
abnormally terminated or ran down before this subordinate RFS could begin its leg of
the operation.
Action: No explicit user action is required.
ORA-16438: Switchover to primary cannot be executed at this time
Cause: ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY could not be
executed because an incompatible operation such as RMAN restore or flashback was
in progress. See the database alert log for details.
Action: Wait for the incompatible operation to complete. The files that have been
flashed back or restored need recovery before you can reissue ALTER DATABASE
COMMIT TO SWITCHOVER TO PRIMARY statement. Start redo apply and verify
that the SWITCHOVER_STATUS column of the V$DATABASE view reports
TO_PRIMARY or SESSIONS_ACTIVE before retrying ALTER DATABASE COMMIT
TO SWITCHOVER TO PRIMARY.
ORA-16439: Standby not ready to receive redo at this time
Cause: A logical standby or down stream capture database was not in a state where it
could accept a request to receive redo from another database. This was likely due to
the database not being open.
ORA-12700 to ORA-19400 69-229
Action: See the database alert log at the receiving side of the transfer for details of
why the database was not ready. If the database was mounted but not open, open it to
clear the problem. The initialization parameter LOG_ARCHIVE_DEST_STATE_n at
the sending site may need to be set to ENABLE.
ORA-16440: Control file is corrupt.
Cause: ALTER SYSTEM FLUSH REDO TO STANDBY failed because the control file
was corrupt.
Action: Restore the current control file at the primary database and then reissue
ALTER SYSTEM FLUSH REDO TO STANDBY from a mounted primary instance.
ORA-16441: Current log string for thread string sequence string is invalid.
Cause: ALTER SYSTEM FLUSH REDO TO STANDBY failed because the current redo
log file was corrupt.
Action: Restore the current log at the primary database, and then reissue ALTER
SYSTEM FLUSH REDO TO STANDBY from a mounted primary instance.
ORA-16442: ALTER SYSTEM FLUSH REDO TO STANDBY succeeded, but some
redo has not been applied.
Cause: The target standby database did not apply all received redo.
Action: Allow the target standby database to apply all redo and then reissue the
ALTER SYSTEM FLUSH REDO TO STANDBY statement.
ORA-16443: could not switch out of log string thread string
Cause: ALTER SYSTEM FLUSH REDO TO STANDBY could not switch out of the
current log.
Action: This can happen if there are one or more errors during archival of the current
log at the primary database. Reissue ALTER SYSTEM FLUSH REDO TO STANDBY
after resolving the archiving errors.
ORA-16444: ALTER SYSTEM FLUSH REDO TO STANDBY failed due to a
corrupted control file or online log file.
Cause: A flush redo operation discovered SCNs greater than a previously failed flush
redo operation.
Action: This can happen if there are one or more errors that have corrupted the
control file or online redo logs. In these cases, flush redo operation is not possible.
ORA-16445: Database has to be mounted and cannot be open
Cause: ALTER SYSTEM FLUSH REDO TO STANDBY required that the database be
mounted, but not opened.
Action: Mount the database and then reissue the operation.
ORA-16446: Target database was not a standby database
Cause: ALTER SYSTEM FLUSH REDO TO STANDBY failed because the target
database is not a standby database.
Action: Reissue the ALTER SYSTEM FLUSH REDO TO STANDBY statement and
specify a standby database as the target database.
ORA-16447: Redo apply was not active at the target standby database
Cause: ALTER SYSTEM FLUSH REDO TO STANDBY failed because redo apply is
not active at the target database.
Action: Start redo apply at the standby database and reissue the ALTER SYSTEM
FLUSH REDO TO STANDBY statement, or reissue the ALTER SYSTEM FLUSH
REDO TO STANDBY statement with the NO CONFIRM APPLY clause.
ORA-16448: Primary database corruption has been detected by standby database.
Cause: The primary database became corrupted.
Action: Identify the extent of the corruption on both the primary and standby
database and take remedial action.
ORA-16449: incomplete redo thread enable operation
Cause: The switchover operation could not continue because it failed to disable a
thread that was left in an incomplete thread enable state.
Action: Check alert log for more details.
ORA-16451: A remote archival request has timed out.
Cause: When opening or closing a database instance, the database may wait for up to
1 minute for pending remote archival requests to be performed before proceeding
with the operation. This error was reported because that time limit was exceeded.
Action: This is an informational message so no action is required.
ORA-16455: switchover to standby failed
Cause: An attempt to switchover to a physical standby database failed.
Action: Check alert log for more details. Issue the SHUTDOWN ABORT command on
the database before issuing another ALTER DATABASE COMMIT TO
SWITCHOVER TO STANDBY command.
ORA-16456: switchover to standby in progress or completed
Cause: The requested operation was not allowed because a switchover to standby
operation was either in progress or had completed.
Action: Issue the SHUTDOWN ABORT command on the database after switchover
operation completes.
ORA-16459: recovery already beyond standby failover
Cause: Redo Apply stopped because it detected that it had proceeded beyond a
standby failover operation.
Action: Determine the STANDBY_BECAME_PRIMARY_SCN by selecting it from V
$DATABASE on the new primary database. Then, flashback the target database to
this SCN and use RMAN to delete all archive logs at or beyond this SCN. Finally,
fetch all terminal end-of-redo (EOR) logs corresponding to the failover operation from
the new primary database and register all these logs at the target database. Restart
Redo Apply.
ORA-16461: database not flashed back or recovered to a consistent point
Cause: ALTER DATABASE CONVERT TO STANDBY command failed because either
the database was not properly flashed back to STANDBY_BECAME_PRIMARY_SCN,
or at least one of the online data files was not current.
Action: Flashback database to STANDBY_BECAME_PRIMARY_SCN and retry the
ALTER DATABASE CONVERT TO STANDBY command.
ORA-16463: invalid target database name
Cause: ALTER DATABASE FAILOVER TO <target_db_name> or ALTER
DATABASE SWITCHOVER TO <target_db_name> FORCE command failed because
ORA-12700 to ORA-19400 69-231
the target_db_name was invalid. The target_db_name must be the same as the name
of the database on which the SQL command is issued.
Action: Change the target database name and reissue the command.
ORA-16464: operation not allowed
Cause: An attempt was made to issue the ALTER DATABASE FAILOVER TO
<target_db_name> or the ALTER DATABASE SWITCHOVER TO <target_db_name>
FORCE command on a database other than a physical standby database.
Action: Issue the command on a physical standby database.
ORA-16465: operation not allowed
Cause: An attempt was made to issue the ALTER DATABASE SWITCHOVER TO
<target_db_name> [VERIFY] command on a database other than an open primary
database.
Action: Issue the command on an open primary database.
ORA-16466: invalid switchover target
Cause: The switchover target was not a valid, enabled, or active standby database.
Action: Fix the problem in the switchover target and reissue the command.
ORA-16467: switchover target is not synchronized
Cause: The switchover target was not synchronized with the primary database.
Action: Wait until the switchover target is synchronized with the primary database,
then reissue the command.
ORA-16468: error connecting to switchover target string
Cause: The primary database could not connect to the switchover target.
Action: Check the alert log for detailed errors.
ORA-16469: switchover target version number is lower than 12
Cause: The switchover target version number was lower than 12.
Action: Upgrade the switchover target to a higher release.
ORA-16470: Redo Apply is not running on switchover target
Cause: The switchover target was not running Redo Apply.
Action: Start Redo Apply on the switchover target and reissue the command.
ORA-16471: cannot convert switchover target string to a primary database
Cause: Switchover failed because the switchover target could not convert to a primary
database.
Action: Check the database role of the switchover target. If the switchover target
database role is standby, do one of the following: - Fix the problem shown in the alert
log. - Issue the remedial ALTER DATABASE SWITCHOVER TO <target_db_name>
FORCE command to convert the switchover target to a primary database. - If the
problem in the switchover target cannot be fixed, issue the remedial ALTER
DATABASE SWITCHOVER TO <target_db_name> FORCE command on the old
primary database to convert the old primary database back to a primary database. If
the switchover target database role is primary, the switchover has completed. Open
the switchover target and startup the old primary database to finish the switchover
process.
ORA-16472: failover failed due to data loss

Cause: The database was in MaxAvailability or MaxProtection mode but terminal
recovery finished with data loss.
Action: For a data loss failover, issue ALTER DATABASE ACTIVATE STANDBY
DATABASE command.
ORA-16473: database is not in limbo
Cause: The ALTER DATABASE SWITCHOVER TO <target_db_name> FORCE
command could not proceed because the database was not in limbo state.
Action: Make sure the SWITCHOVER_STATUS column in V$DATABASE has the
value TO PRIMARY or SESSIONS ACTIVE. If needed, start managed standby
recovery and reissue the command after the SWITCHOVER_STATUS column value
changes to one of the above values.
ORA-16474: target_db_name not found in the LOG_ARCHIVE_DEST_n parameter
Cause: ALTER DATABASE SWITCHOVER TO <target_db_name> or ALTER
SYSTEM FLUSH REDO TO <target_db_name> command failed because the
target_db_name was not defined in the LOG_ARCHIVE_DEST_n parameter.
Action: Make sure the target_db_name is defined in the LOG_ARCHIVE_DEST_n
parameter.
ORA-16475: succeeded with warnings, check alert log for more details
Cause: The ALTER DATABASE SWITCHOVER TO <target_db_name> VERIFY
command succeeded but with warnings.
Action: Check alert log for more details.
ORA-16476: far sync instance does not allow string operation
Cause: The specified operation was invalid on a far sync instance.
Action: Do not attempt the specified operation on a far sync instance.
ORA-16477: destination is being serviced by another viable source
Cause: An attempt was made by a far sync instance to perform gap analysis with a
remote destination that already had connectivity with a different viable source of live
redo.
Action: No action is required. This exception code is informational and is used by the
far sync instance to remain idle with respect to this destination until it establishes
connectivity with the primary database.
ORA-16478: cannot locate far sync instance connect string
Cause: The connect string for the far sync instance that is flagged as the source of live
redo for this database could not be located.
Action: Define a LOG_ARCHIVE_DEST_n parameter for the far sync instance using
the SERVICE attribute to define the connect string for the far sync instance
destination. This destination should be set to DEFER using the corresponding
LOG_ARCHIVE_DEST_STATE_n parameter. Once the connect string is defined, retry
the failover operation. Using the FORCE option on the failover command allows the
operation to proceed and bypass the far sync instance but bypassing the far sync
instance increases the potential for data loss.
ORA-16479: cannot connect to the far sync instance
Cause: An attempt was made to connect to the far sync instance to help facilitate the
failover operation but the connection attempt failed.
ORA-12700 to ORA-19400 69-233
Action: Make sure the far sync instance is mounted. Check the alert log and trace files
on both the current database and the far sync instance for further details. Retry the
operation if a problem is identified and corrected. Using the FORCE option on the
failover command allows the operation to proceed and bypass the far sync instance
but bypassing the far sync instance increases the potential for data loss.
ORA-16480: operational error during far sync instance assisted failover
Cause: After successfully connecting to the far sync instance, an error was
encountered when polling the far sync instance for progress.
Action: Check the alert log and traces of both the current database and the far sync
instance for further details. Retry the operation if a problem is identified and
corrected. Using the FORCE option on the failover command allows the operation to
proceed and bypass the far sync instance but bypassing the far sync instance increases
the potential for data loss.
ORA-16481: destination error during far sync instance assisted failover
Cause: After successfully connecting to the far sync instance, an error was
encountered when managing the failover target destination on the far sync instance.
Action: Check the alert log and traces of both the current database and the far sync
instance for further details. Retry the operation if a problem is identified and
corrected. Using the FORCE option on the failover command allows the operation to
proceed and bypass the far sync instance but bypassing the far sync instance increases
the potential for data loss.
ORA-16482: a role transition is in progress
Cause: The operation failed because a role transition was in progress.
Action: None
ORA-16483: unable to set a LOG_ARCHIVE_DEST_n parameter to the switchover
target
Cause: An attempt was made to set a LOG_ARCHIVE_DEST_n parameter to the
switchover target failed.
Action: Manually set a LOG_ARCHIVE_DEST_n parameter to the switchover target.
ORA-16484: compatibility setting is too low
Cause: The compatibility setting in the redo log transported to this standby database
exceeded the current compatibility setting.
Action: Check the compatibility setting on the primary and standby database, and
increase the compatibility setting in the initialization parameter file on the standby
database accordingly.
ORA-16485: redo log is already received at destination
Cause: A copy of this redo log was already received at the destination.
Action: None
ORA-16486: redo log is rejected by the destination
Cause: The destination was not allowed to receive this redo log.
Action: Ensure the source database is registered at the destination, the destination is
up and running, and storage is available.
ORA-16487: the destination database is not writable
Cause: The destination database was in read-only mode.
Action: Ensure the destination database is open for write.

ORA-16488: cannot create a bookkeeping entry in database
Cause: The destination database failed to create an entry in the table used to track the
redo log.
Action: Examine the trace file of the Remote File Server (RFS) process. Check and
make sure space is available in your database.
ORA-16489: cannot register the redo log at the destination database
Cause: Registering the redo log to the destination database failed.
Action: Examine the trace file of the Remote File Server (RFS) process. Check and
make sure space is available in your database.
ORA-16491: operation not allowed due to insufficient online redo log files string
Cause: A minimum of two online redo log files per active thread were not supplied.
Action: Add the required redo log files and reissue the command.
ORA-16492: switchover target local destination has error
Cause: The switchover target local destination either exceeded quota size or had an
error.
Action: Fix the problem in the switchover target and reissue the command.
ORA-16493: using SYSDBA, SYSOPER, SYSDG, or SYSBKUP user for redo
shipping to Recovery Appliance is not supported
Cause: An attempt was made to use a SYSDBA, SYSOPER, SYSDG, or SYSBKUP user
to ship redo logs to a Recovery Appliance.
Action: Use a user without the SYSDBA, SYSOPER, SYSDG, or SYSBKUP privilege to
ship redo logs to a Recovery Appliance.
ORA-16494: process started from pluggable database (PDB)
Cause: The Remote File Server (RFS) process or Remote Message Interface (RMI)
process or Fetch Archive Log (FAL) process was started from the PDB.
Action: Check the service name that the RFS or RMI or FAL client connected to.
Ensure the service is not from PDB.
ORA-16495: Using fast recovery area to receive redo log files on Recovery
Appliance is not supported.
Cause: An attempt was made to use fast recovery area to receive redo log file on a
Recovery Appliance.
Action: Do not configure fast recovery area for receiving redo log files on a Recovery
Appliance.
ORA-16501: The Oracle Data Guard broker operation failed.
Cause: The Oracle Data Guard broker operation failed.
ORA-16502: The Oracle Data Guard broker operation succeeded with warnings.
Cause: The Oracle Data Guard broker operation succeeded with warnings.
ORA-12700 to ORA-19400 69-235
ORA-16503: cannot exceed the maximum number of databases in this configuration

Cause: The Oracle Data Guard broker configuration already contained the maximum
number of databases that could be configured and managed by the broker.
Action: Select and remove an existing database from the broker configuration, then
reissue the command to add another database to the configuration. Note that when
COMPATIBLE is set lower than 11.2.0.0.0, the broker can configure and manage up to
10 databases. When COMPATIBLE is set to 11.2.0.0.0 or higher, this limit is increased
to 31.
ORA-16504: The Oracle Data Guard configuration already exists.
Cause: A request to create an Oracle Data Guard configuration was made while
connected to a database that is part of an existing configuration.
Action: To create a new configuration, the existing configuration must be deleted.
ORA-16506: out of memory
Cause: Process exceeded private or shared memory limits.
Action: Check for memory leaks, increase system parameters and restart.
ORA-16509: request timed out
Cause: The Oracle Data Guard broker timed out the request.
Action: Check the Oracle Data Guard broker log file for more information. Ensure
that the network connections between the databases are functioning properly and
retry the request.
ORA-16513: maximum requests exceeded
Cause: The maximum number of requests that the broker can service on the database
instance was exceeded.
Action: Wait for the broker to complete processing the requests before issuing more
requests.
ORA-16516: current state is invalid for the attempted operation
Cause: The broker may have returned this error for either switchover operations or
for database state change operations. If this error was returned for a switchover
operation, the broker determined that either: - The databases changing roles are shut
down. - The primary database is not shipping redo data. - The standby database that
will become the primary database is not applying redo data. If this error was returned
for database state change operations, the database state specified was invalid.
Action: If this error is returned when attempting a switchover operation, make sure
that: - The databases changing roles are started. - The primary database is shipping
redo data. - The standby database is applying redo data. If this error is returned when
attempting a database state change operation, make sure a valid database state is
specified.
ORA-16521: operation requires connection to the multitenant container database
Cause: The command required the client to connect to the multitenant container
database.
Action: Connect to the multitenant container database and reissue the command.
ORA-16522: configuration is part of Global Data Services pool
Cause: The attempted command was not allowed because the configuration was part
of a Global Data Services pool.
Action: Remove the configuration from the Global Data Services pool using GDSCTL.
Then, retry the broker command. If the command was attempting to repair a
database, disable or remove the individual database from the configuration and fix
the issue. After the issue is resolved, reenable the database, or add the database back
to the configuration if it had been removed.
ORA-16523: operation requires the client to connect to instance "string"
Cause: The switchover or failover operation required the client to connect to the apply
instance of the target database.
Action: Connect to the indicated instance and reissue the SWITCHOVER or
FAILOVER command.
ORA-16524: unsupported command, option, or argument
Cause: A command, option, or fast-start failover condition argument was specified
that is not supported in this release.
Action: If trying to enable or disable a fast-start failover condition, try a different
Oracle error number. Otherwise, contact Oracle Support Services.
ORA-16525: The Oracle Data Guard broker is not yet available.
Cause: The Oracle Data Guard broker process was either not yet started, was
initializing, or failed to start.
Action: If the broker has not been started, set the DG_BROKER_START initialization
parameter to true and allow the broker to finish initializing before making the
request. If the broker failed to start, check the Oracle Data Guard log for possible
errors. Otherwise, retry the operation.
ORA-16526: unable to allocate memory to process request
Cause: The Oracle Data Guard broker was unable to allocate memory for a request.
Action: Increase the size of the System Global Area (SGA).
ORA-16527: unable to allocate broker System Global Area (SGA) memory
Cause: The Oracle Data Guard broker was unable to allocate memory within the
System Global Area (SGA).
Action: Increase the size of the System Global Area (SGA) memory.
ORA-16528: unable to allocate Program Global Area (PGA) memory
Cause: There was insufficient space in Program Global Area (PGA) to allocate
memory.
Action: Increase process virtual memory.
ORA-16530: invalid buffer or length
Cause: A NULL buffer or a length of zero was specified.
Action: Correct the command parameters and retry the command.
ORA-16532: Oracle Data Guard broker configuration does not exist
Cause: A broker operation was requested that required a broker configuration to
already be created.
Action: Create a Data Guard broker configuration prior to performing other broker
operations. If only one instance of a RAC database is reporting this error, ensure that
the DG_BROKER_CONFIG_FILE[1|2] initialization parameters are set to file
locations that are shared by all instances of the RAC database.
ORA-12700 to ORA-19400 69-237
ORA-16534: switchover, failover or convert operation in progress

Cause: The Oracle Data Guard broker returned this status because a switchover,
failover or convert operation was in progress. The broker could not accept new
commands until the operation finished.
Action: Wait until the operation is complete and reissue the command.
ORA-16535: Oracle Restart or Oracle Clusterware prevented completion of broker
operation
Cause: The broker could not complete the operation because Oracle Restart (for single
instance databases) or Oracle Clusterware (for RAC databases) could not stop services
or instances on this database.
Action: Check the Oracle Data Guard broker log file for more information and stop
the appropriate services or instances using SRVCTL. Then retry the broker operation.
ORA-16538: no match on requested item
Cause: The Oracle Data Guard broker did not recognize the specified property or
state name, or a fast-start failover condition was specified that is not enabled.
Action: Verify the command parameters and reissue the command.
ORA-16540: invalid argument
Cause: One of the arguments for the specified command was invalid.
Action: Verify the arguments and then reissue the command.
ORA-16541: member is not enabled
Cause: The member specified in the command was not enabled.
Action: Select an enabled member and reissue the command.
ORA-16544: modifying DG_BROKER_START requires SID='*' qualifier
Cause: The setting for the DG_BROKER_START parameter must be exactly the same
on all RAC database instances. The SID='*' qualifier was required in the command.
Action: Reenter the command using the SID='*' qualifier.
ORA-16547: cannot disable or remove the primary database
Cause: An attempt was made to disable broker management of the primary database
or remove the primary database from the broker configuration while the
configuration was enabled.
Action: If you wish to disable broker management of the primary database when the
configuration is enabled, you must instead disable broker management of the entire
broker configuration. If you wish to remove the primary database from the broker
configuration while the configuration is enabled, you must instead remove the entire
broker configuration.
ORA-16548: database not enabled
Cause: An attempt was made to modify or query a disabled database. This error is
also returned on an attempt to enable, modify, or query a database that the broker has
disabled because of a switchover or failover operation. The broker disables its
management of a database when it detects that the database needs to be re-created
because of a failover or switchover operation.
Action: If broker management of the database is disabled, enable it and reissue the
command.
ORA-16549: invalid string

Cause: An invalid or NULL string value was specified.
Action: Correct command parameters and retry.
ORA-16550: truncated result
Cause: A string property value was truncated due to insufficient buffer size.
Action: Specify a larger receive buffer.
ORA-16551: short string copied
Cause: A string property value that did not fill the receive buffer was placed in the
receive buffer.
ORA-16552: error occurred while generating directives for client
Cause: The operation could not be completed because the broker required assistance
from the client that it was unable to provide because of the accompanying error.
Action: See the accompanying error message for more information and follow the
directions provided in the Action section of that message. Then retry the operation.
ORA-16555: database is not active
Cause: An operation was attempted on a database that was not active. not active.
Action: Verify that the database is active and retry the operation.
ORA-16556: observer version mismatch
Cause: This version of the observer was incompatible with the version of the specified
Oracle database server to which the observer had been connected. This observer client
cannot be used to observe the specified Oracle server.
Action: Use a version of the observer that is compatible with the Oracle database
server to be observed.
ORA-16557: database is already in use
Cause: An attempt was made to create a duplicate database in the broker
configuration, or to add a duplicate instance (sid) for an existing database in the
broker configuration.
Action: Check the database to be added to ensure there are no duplicates.
ORA-16558: database specified for switchover is not a standby database
Cause: An attempt was made to switchover to a database that was not a standby
database.
Action: Locate an enabled standby database and select that database as the target of
the switchover.
ORA-16561: cannot remove an active instance
Cause: The instance to be removed was running.
Action: Shut down the instance and reissue the REMOVE command.
ORA-16568: cannot set property string
Cause: The specified property could not be modified because it was either a
monitorable property or a property that did not exist.
Action: Retry the command with a valid configurable property.
ORA-12700 to ORA-19400 69-239
ORA-16569: Oracle Data Guard configuration is not enabled

Cause: The requested operation required that broker management of the Data Guard
configuration must be enabled.
Action: Enable the Oracle Data Guard configuration and reissue the command.
ORA-16570: database needs restart
Cause: The Oracle Data Guard broker operation required this database instance to be
shut down and restarted.
Action: If DGMGRL or Enterprise Manager has not already done so, shut down the
Oracle instance and then restart it.
ORA-16571: Oracle Data Guard configuration file creation failure
Cause: The Oracle Data Guard broker was unable to create the configuration file on
permanent storage.
Action: Verify space, permissions and file name as indicated by the
DG_BROKER_CONFIG_FILE[1|2] initialization parameters and retry the operation.
ORA-16572: Oracle Data Guard configuration file not found
Cause: The Oracle Data Guard broker configuration file was either unavailable or did
not exist.
Action: Verify that the configuration file was successfully created. If the
DG_BROKER_CONFIG_FILE[1|2] initialization parameters were changed, ensure
the file name on disk and the parameter value match, there is space on the device, and
the proper permissions are granted. For a RAC database, ensure that these
initialization parameters are set to file locations that are shared by all instances of the
RAC database.
ORA-16573: attempt to change or access configuration file for an enabled broker
configuration
Cause: The operation was rejected because the Oracle Data Guard broker
configuration file was in use. The attempted operation was unsafe while broker
management of the configuration was enabled. For example: - An attempt was made
to alter the DG_BROKER_CONFIG_FILE[1|2] initialization parameters while the
broker was running. - Non-broker access (such as DBMS_FILE_TRANSFER) to the
configuration files was attempted. See the alert log for additional information.
Action: Disable the broker configuration and shut down the Oracle Data Guard
broker, then retry the operation. If the operation includes altering the
DG_BROKER_CONFIG_FILE[1|2] initialization parameters, be sure that the new
parameter values correctly specify the files at their expected location before
reenabling broker management of the configuration.
ORA-16574: switchover disallowed when required databases are shut down
Cause: Switchover failed because either the primary database or the designated
standby database were shut down.
Action: Ensure that the primary and standby databases are running and that primary
database is shipping redo data to the designated standby database. Also ensure that
that the designated standby database is applying the redo data received from the
primary database.
ORA-16575: request terminated because failover is in progress
Cause: This error was returned when the broker terminated a request because it was
processing a failover command.
Action: Wait for failover to complete and then retry the request.
ORA-16576: failed to update Data Guard configuration file
Cause: A failure was encountered while the broker was updating the Oracle Data
Guard broker configuration file on permanent storage.
DG_BROKER_CONFIG_FILE[1|2] initialization parameters.
ORA-16577: corruption detected in Data Guard configuration file
Cause: The Oracle Data Guard broker detected errors while loading the configuration
file.
DG_BROKER_CONFIG_FILE[1|2] initialization parameters. Contact Oracle Support
Services.
ORA-16578: failed to read Data Guard configuration file
Cause: A failure was encountered while the broker was reading the configuration file
on permanent storage.
DG_BROKER_CONFIG_FILE[1|2] initialization parameters.
ORA-16582: cannot change instance-specific property
Cause: An attempt was made to change an instance-specific property for a database
that had more than one instance.
Action: Retry the command and identify a specific instance whose property value is
to be changed.
ORA-16584: operation cannot be performed on a standby database
Cause: The database specified for the operation was a standby database, or the
operation was attempted on a standby database.
Action: Check the database type and retry the operation. If the command must be
executed on a primary database, connect to the primary database and retry the
operation.
ORA-16585: operation cannot be performed on a primary database
Cause: The database specified for the operation was a primary database, or the
operation was attempted on a primary database.
Action: Check the database type and retry the operation. If the command must be
executed on a standby database, connect to a standby database and retry the
operation.
ORA-16586: cannot change database property with EDIT INSTANCE command
Cause: An attempt was made to change a database property using an EDIT
INSTANCE command instead of an EDIT DATABASE command.
Action: Use the EDIT DATABASE command to change database properties.
ORA-16587: ambiguous object specified to Data Guard broker
Cause: An object was specified that the broker could not uniquely distinguish from
other objects in the configuration.
Action: Try to further distinguish the object specified for the operation and reissue the
command.
ORA-12700 to ORA-19400 69-241
ORA-16589: Oracle Data Guard broker detected network transfer error

Cause: The Oracle Data Guard broker detected an error while transferring data from
one database to another. This may happen when: - The broker detects an
inconsistency in the block count of configuration file when the file is transmitted
between databases. - The broker encountered an error when writing the configuration
file.
ORA-16594: DMON background process is not running
Cause: The Oracle Data Guard broker background process, DMON, was not running.
Action: Check the Oracle Data Guard broker log file and DMON process trace file to
determine why the DMON process is not running.
ORA-16595: process string failed to terminate
Cause: The specified process did not terminate at the request of the Data Guard
broker.
ORA-16596: database not part of the Oracle Data Guard broker configuration
Cause: The specified database was not in the Oracle Data Guard broker configuration.
Action: Retry the command with a database that is in the broker configuration.
ORA-16597: Oracle Data Guard broker detects two or more primary databases
Cause: The Oracle Data Guard broker detected two or more primary databases in the
broker configuration and could not continue.
ORA-16598: Oracle Data Guard broker detected a mismatch in configuration
Cause: The Oracle Data Guard broker detected a significant mismatch while
performing configuration membership validation between two or more databases in
the broker configuration. This can occur when the primary database has stale broker
configuration files.
ORA-16599: Oracle Data Guard broker detected a stale configuration
Cause: The Oracle Data Guard broker detected a stale configuration during
initialization for this database.
Action: The broker will automatically resolve this situation once the primary database
completes its initialization.
ORA-16600: not connected to target standby database for failover
Cause: The failover command failed because the client was not connected to the target
standby database.
Action: Explicitly connect to the standby database to be failed over to and retry the
failover command.
ORA-16602: database must be disabled to perform this operation
Cause: An attempt was made to edit a database property while the database was
enabled.
Action: Disable the database and retry the command.
ORA-16603: database is part of another Data Guard broker configuration

Cause: The database was part of another Data Guard broker configuration. This could
occur if the original configuration was re-created while this database was
disconnected from the network or the same database was added to two different Data
Guard broker configurations.
Action: Make sure the database belongs to only one broker configuration. Shut down
the broker by setting the DG_BROKER_START initialization parameter to false. Then,
remove the Oracle Data Guard broker configuration files. Finally, restart the broker
by setting the DG_BROKER_START initialization parameter to true.
ORA-16604: operation not allowed on a database that ships redo data
Cause: An attempt was made to delete, disable, or convert a database that ships redo
data to another database.
Action: Ensure that the name of the database to be deleted, disabled, or converted is
not specified in another database's RedoSource property.
ORA-16606: unable to find property "string"
Cause: The specified property did not exist.
Action: Specify a valid property name and reissue the command.
ORA-16607: one or more databases have failed
Cause: A failure was detected for one or more databases in the Data Guard broker
configuration.
Action: Locate the database(s) with a failure status and correct it.
ORA-16608: one or more databases have warnings
Cause: A warning was detected for one or more databases in the Data Guard broker
configuration.
Action: Locate the database(s) with a warning status and correct it.
ORA-16609: database is being disabled
Cause: A command was attempted on a database that was being disabled. For
example, attempting to reinstate the old primary database, the database that was the
primary database prior to the most recent failover, before it was ready to be
reinstated.
Action: Wait for the Oracle Data Guard broker to disable the database and then retry
the command.
ORA-16610: command "string" in progress
Cause: The specified broker command was already running and the command issued
could not be completed.
Action: Wait for the specified command to finish and then retry the command.
ORA-16611: command aborted at user request
Cause: The command was aborted at the user's request.
ORA-16612: string value too long for attribute "string"
Cause: The string value for the named attribute was too long.
Action: Specify a shorter string value.
ORA-12700 to ORA-19400 69-243
ORA-16613: initialization in progress for database

Cause: A request was made that required access to the Oracle Data Guard broker
configuration before the Oracle Data Guard broker had completed initialization.
Action: Wait until the Oracle Data Guard broker has completed initialization, then
reissue the command.
ORA-16614: Oracle Data Guard broker configuration is disabled
Cause: An attempt to enable a database failed because the Oracle Data Guard broker
configuration was disabled.
Action: Enable the Oracle Data Guard broker configuration and issue the DGMGRL
CLI SHOW CONFIGURATION command to see if there are any databases that are
still disabled. If the database you tried to enable is still disabled, issue the DGMGRL
CLI SHOW DATABASE command to check the status of the database. If the database
status indicates that the database needs to be reinstated, then issue the DGMGRL CLI
REINSTATE DATABASE command to reinstate and enable the database. If the
database does not require reinstatement, then issue the DGMGRL CLI ENABLE
DATABASE command to enable the database.
ORA-16617: unknown object identifier specified in request
Cause: Object identifier specified in the request was invalid or unknown.
Action: Verify that a valid object identifier is specified and reissue the command.
ORA-16619: condition for fast-start failover is already enabled
Cause: The condition specified for fast-start failover was already enabled.
Action: No action is required. Use the DGMGRL CLI SHOW FAST_START
FAILOVER command to see the conditions that are enabled.
ORA-16620: one or more databases could not be reached for a delete operation
Cause: One or more standby databases could not be reached for either a DGMGRL
CLI REMOVE DATABASE or a REMOVE CONFIGURATION command.
Action: This typically indicates a network problem where the standby database is
unable to respond to the primary database. In the event of this situation, examine the
primary database Data Guard broker log file to determine which standby databases
could not be reached. For each standby database not reached, connect to that database
and shut down the broker by setting the initialization parameter,
DG_BROKER_START, to false. After the broker has been shut down for the standby
database, locate the Data Guard broker configuration files from the standby database
DG_BROKER_CONFIG_FILE[1|2] initialization parameter values and delete them.
Then restart the broker by setting DG_BROKER_START to true.
ORA-16621: database name for ADD DATABASE must be unique
Cause: An attempt was made to add a database to the broker configuration that
already included a database with the specified name. The database names must be
unique.
Action: Verify that a unique name is specified for the new database to be added. Also,
the database name must match the DB_UNIQUE_NAME initialization parameter of
the database.
ORA-16622: two or more broker database objects resolve to the same database
Cause: Multiple database objects referred to the same database.
Action: Examine the details of all databases in the broker configuration and verify
that there are not two or more databases referring to the same database. If two or
more database profiles in the broker configuration have the same value for the
DGConnectIdentifier database property, either: - Remove and re-add the erroneously
defined database(s) to resolve the ambiguity. - Ensure that the DGConnectIdentifier
database property for each database allows the broker to properly connect to that
database.
ORA-16623: database detected role change
Cause: A successful switchover or failover operation had been completed and was
detected during database startup or broker health check. If this database was
unavailable during a switchover or failover operation, it may not be a viable standby
database for the new primary database and was disabled by the Oracle Data Guard
broker.
Action: Connect to the new primary database and examine the broker configuration
for databases that were disabled and that may require reinstatement or re-creation.
ORA-16624: broker protocol version mismatch detected
Cause: A network protocol version number mismatch was detected. This could
happen if the databases in the broker configuration were not running the same
version of Oracle. The broker would disable standby databases that were not running
the same version of Oracle as the primary database if this situation was detected.
Action: Examine the version of Oracle installed on all databases in the broker
configuration to ensure they are identical. Once all of the databases in the broker
configuration are running the same version of Oracle, reenable the standby databases
that were disabled.
ORA-16625: cannot reach database "string"
Cause: The command could not be executed because the database noted in the error
text was not reachable from the database where the command was issued.
Action: See accompanying messages for more information. Check the network
connections to the specified database. Alternatively, connect to a different database in
the Oracle Data Guard broker configuration and retry the command.
ORA-16626: failed to enable specified database
Cause: This status was returned when attempting to enable a standby database that: Could not locate itself in the broker configuration file. - Failed to distinguish itself
from two or more databases in the configuration file. - Determined it missed a role
change within the configuration.
Action: To correct the problem, try one of these actions: - Confirm that the host and
SID names for the database exactly match the values in the HOST_NAME and
INSTANCE_NAME columns of V$INSTANCE. - Confirm that there are not two or
more databases with the same connect identifier. That is, multiple databases in the
broker configuration should not reach the same database. - If a failover had been
performed and the old primary database has been re-created (or a standby database
has been re-created), make sure the Oracle Data Guard broker configuration files have
been removed for that database. Do NOT remove the configuration files that are in
use by the new primary database.
ORA-16627: operation disallowed since no standby databases would remain to
support protection mode
Cause: This status was returned because of one of the following: - The broker rejected
an attempt to change the overall configuration protection mode since it could not find
any enabled standby databases that supported the proposed protection mode. - The
broker rejected an attempt to enable the configuration if it determined that there were
ORA-12700 to ORA-19400 69-245
no enabled standby databases that supported the overall protection mode. - The
broker rejected an attempt to disable or remove a database that, if disabled or deleted,
would result in no remaining standby databases that could support the overall
configuration protection mode. - The broker rejected an attempt to switchover if
doing so would violate the overall configuration protection mode. - Performing
automatic health check if the broker determined that no standby datbases supported
the overall protection mode.
Action: - If changing the overall protection mode, confirm that at least one standby
database satisfies the new protection mode. - For enable failures, confirm that at least
one standby database has a LogXptMode configurable property setting that supports
the current overall protection mode. - For delete and disable failures, confirm that at
least one other standby database has a LogXptMode configurable property setting
that supports the overall protection mode. - For switchover failures that occur when
the configuration is operating in maximum protection or maximum availability mode,
confirm that at least one other standby database has its LogXptMode configurable
property set to the value "SYNC". If the configuration contains a primary database
and a single standby database and is operating in either maximum protection or
maximum availability mode, ensure that the LogXptMode configurable property of
the primary database is set to the value "SYNC". Since the old primary database will
become the standby database after switchover completes, its LogXptMode
configurable property setting must support the configuration protection mode. - For
health check error, confirm that at least one standby database has a LogXptMode
configurable property setting that supports the current overall protection mode.
ORA-16628: broker protection mode inconsistent with the database setting
Cause: The Oracle Data Guard broker protection mode saved in the broker
configuration file was inconsistent with the actual database setting.
Action: Reset the protection mode through the Oracle Data Guard broker.
ORA-16629: database reports a different protection level from the protection mode
Cause: The current database protection level was different from the configured
protection mode. This typically was caused by redo transport problems, or the
primary database was not open.
Action: Check the database alert log files and Data Guard broker log files for more
details. Also, check the redo transport status. Ensure that one standby database
supports the configured protection mode and that the network to that standby
database is working properly. Ensure the primary database is open.
ORA-16630: database property has been deprecated
Cause: The property that was specified in the command was deprecated.
Action: Check the broker documentation to identify a replacement property or SQL
command for the deprecated property.
ORA-16631: operation requires shutdown of database or instance "string"
Cause: The Oracle Data Guard broker operation required a shutdown of the database
or instance.
Action: If database or instance has not been shutdown by the DGMGRL CLI or
Enterprise Manager, shutdown the database or instance manually.
ORA-16632: instance being added to database profile
Cause: The Oracle Data Guard broker determined that an instance successfully found
its database profile within the broker configuration file, but lacked an instance-
specific profile. The broker automatically created an instance-specific profile and

associated the instance with its database profile.
Action: No user action is required. The broker will automatically associate the
instance with its database profile and incorporate the instance into broker activity.
ORA-16633: the only instance of a member cannot be removed
Cause: The instance to be removed was the only instance of the corresponding
member that was known to the broker.
Action: Remove the corresponding member from the broker configuration instead of
the individual instance of the member.
ORA-16635: network connection failed during transmission
Cause: The Oracle Data Guard broker detected a connection failure to a remote
database in the broker configuration. This failure happened in the middle of a
transmission session. A transmission session usually requires more than one send
operation for sending a large amount of data (for example, the broker configuration
file) to the remote database.
Action: In most cases, no user action is required. The Oracle Data Guard broker
always tries to resend the data. This error will be reported if the problem persists.
This error indicates there are some problems with the network connection between
broker managed databases. Further network troubleshooting should be done to
identify and correct the actual problem.
ORA-16636: fast-start failover target standby in error state, cannot stop observer
Cause: A STOP OBSERVER operation could not be completed when fast-start failover
was enabled because the target standby database could not participate in the STOP
OBSERVER operation.
Action: Additional information about this failure is recorded in the Data Guard
broker log file for the primary database. This information helps to identify the reason
why the target standby database was unable to participate in the STOP OBSERVER
operation. If the problem can be corrected by the information in the broker log file,
retry the operation. Alternatively, fast-start failover may be forcibly disabled by
connecting to the primary database and issuing the DISABLE FAST_START
FAILOVER FORCE command from the DGMGRL CLI. Once fast-start failover has
been forcibly disabled, the observer can be stopped regardless of the current state of
the target standby database.
ORA-16637: maximum number of Oracle error numbers for fast-start failover
already reached
Cause: The broker could not enable any more Oracle error numbers for initiating a
fast-start failover.
Action: Use the DGMGRL CLI SHOW FAST_START FAILOVER command to help
identify an Oracle error number that can be disabled before attempting to enable an
additional error number for initiating a fast-start failover.
ORA-16638: could not obtain instance status
Cause: The broker could not determine whether the specified instance was running.
Action: See the next error message in the error stack for more detailed information. If
the situation described in the next error in the stack can be corrected, do so;
otherwise, contact Oracle Support Services.
ORA-12700 to ORA-19400 69-247
ORA-16639: specified instance inactive or currently unavailable

Cause: An attempt was made to perform an operation on an instance that was not
running or was unavailable.
Action: Ensure that the instance specified in the operation is running and then retry
the operation.
ORA-16642: DB_UNIQUE_NAME mismatch
Cause: The expected DB_UNIQUE_NAME value did not match the actual
DB_UNIQUE_NAME value for the database that the broker contacted using the
connect identifier that was associated with that database.
Action: Verify that the connect identifier correctly connects to the intended database.
Verify that the name of the database the broker expects to find by that connect
identifier matches the actual DB_UNIQUE_NAME for that database.
ORA-16643: unable to determine location of broker configuration files
Cause: The Oracle Data Guard broker was unable to determine the location of its
configuration files from the DG_BROKER_CONFIG_FILE[1|2] initialization
parameters.
Action: Retry the operation and, if the error persists, contact Oracle Support Services.
ORA-16644: apply instance not available
Cause: The broker operation could not finish, because it requires a running apply
instance for the standby database, and either there was no such instance designated
for the standby database or the designated apply instance was not currently available.
Action: Start the designated apply instance or wait until the broker specifies an
instance to be the apply instance and reissue the command.
ORA-16645: startup of an instance interrupted current operation
Cause: The startup of an instance that is not part of the broker configuration
prevented the operation from completing.
Action: Reissue the operation after the new instance has joined the Data Guard
configuration.
ORA-16646: fast-start failover is disabled
Cause: The operation was not allowed because fast-start failover was disabled.
Action: Enable fast-start failover and retry the operation.
ORA-16647: could not start more than one observer
Cause: The observer could not start because there was another observer already
observing the Oracle Data Guard configuration for which fast-start failover may have
been enabled.
Action: Stop the running observer. Retry the operation.
ORA-16648: a new observer registered with identifier string
Cause: The observer was registered with the Oracle Data Guard broker and will begin
observing the Oracle Data Guard configuration for conditions that warrant doing a
fast-start failover.
Action: None
ORA-16649: possible failover to another database prevents this database from

being opened
Cause: An attempt to open the primary database was made either after a failover
occurred, or when it was likely to have occurred as the result of the primary being
isolated from the fast-start failover target standby database and from the fast-start
failover observer.
Action: Check if a failover did occur. If fast-start failover is enabled, and a failover did
not occur, ensure that connectivity exists between the primary database and either the
observer or the target standby database. Then, try opening the database again.
ORA-16650: unrecognized object specified
Cause: An unrecognized database or far sync instance was specified in the command.
Action: Try the command again using a valid object name. Use the SHOW
CONFIGURATION command to identify the members in the configuration.
ORA-16651: requirements not met for enabling fast-start failover
Cause: The attempt to enable fast-start failover could not be completed because one or
more requirements were not met: - The Oracle Data Guard configuration must be in
either MaxAvailability or MaxPerformance protection mode. - The LogXptMode
property for both the primary database and the fast-start failover target standby
database must be set to either SYNC or FASTSYNC if the configuration protection
mode is set to MaxAvailability mode. - The LogXptMode property for both the
primary database and the fast-start failover target standby database must be set to
ASYNC if the configuration protection mode is set to MaxPerformance mode. - The
primary database and the fast-start failover target standby database must both have
flashback enabled. - No valid target standby database was specified in the primary
database FastStartFailoverTarget property prior to the attempt to enable fast-start
failover, and more than one standby database exists in the Oracle Data Guard
configuration. - fast-start failover target standby database did not receive redo data
directly from the primary database or from a far sync instance.
Action: Retry the command after correcting the issue: - Set the Oracle Data Guard
configuration to either MaxAvailability or MaxPerformance protection mode. Ensure that the LogXptMode property for both the primary database and the faststart failover target standby database are set to either SYNC or FASTSYNC if the
configuration protection mode is set to MaxAvailability. - Ensure that the
LogXptMode property for both the primary database and the fast-start failover target
standby database are set to ASYNC if the configuration protection mode is set to
MaxPerformance. - Ensure that both the primary database and the fast-start failover
target standby database have flashback enabled. - Set the primary database
FastStartFailoverTarget property to the DB_UNIQUE_NAME value of the desired
target standby database and set the desired target standby database
FastStartFailoverTarget property to the DB_UNIQUE_NAME value of the primary
database. - Ensure the RedoSource properties of both the primary and the target
standby database are set to either the empty value or the name of a far sync instance.
ORA-16652: fast-start failover target standby database is disabled
Cause: The command to enable or disable fast-start failover could not be completed
because Data Guard broker management of the fast-start failover target standby
database is currently disabled.
Action: Enable broker management of the target standby database and reissue the
command. If an attempt was made to disable fast-start failover when this error was
reported, disable fast-start failover forcibly using the DGMGRL DISABLE
ORA-12700 to ORA-19400 69-249
FAST_START FAILOVER FORCE command. Consult the documentation for more

information.
ORA-16653: failed to reinstate database
Cause: The Oracle Data Guard broker failed to reinstate the specified database
because the reinstatement could not be completed or the database was already
enabled.
Action: Additional information about this failure is recorded in the primary database
or the specified database Data Guard broker log files. This information is helpful in
determining how to proceed.
ORA-16654: fast-start failover is enabled
Cause: The attempted command was not allowed while fast-start failover was
enabled: - The FastStartFailoverTarget property may not be modified. - The
LogXptMode property for either the primary database or the fast-start failover target
standby database may not be modified. - The configuration's protection mode may
not be modified. - Neither the broker configuration nor the fast-start failover target
standby database may be disabled using the DGMGRL CLI DISABLE command. Neither the broker configuration nor the fast-start failover target standby database
may be removed using the DGMGRL CLI REMOVE command. - The FAILOVER
IMMEDIATE command is not allowed. - The DG_BROKER_START initialization
parameter may not be set to FALSE.
Action: Disable fast-start failover, using the FORCE option if required. Then retry the
attempted command.
ORA-16655: specified target standby database invalid
Cause: The attempted command was not allowed because fast-start failover was
enabled for this Data Guard configuration and the target standby database specified
in the command differs from the standby database that was indicated by the
FastStartFailoverTarget property associated with the current primary database.
Action: Retry the attempted command by specifying the standby database that is
indicated by the FastStartFailoverTarget property that is associated with the current
primary database. Alternatively, fast-start failover may be disabled. Then retry the
command using the originally specified target standby database.
ORA-16656: Oracle Data Guard broker detected role change
Cause: The Oracle Data Guard broker detected a role change during database startup
or health check.
Action: Additional information about this failure is recorded in the Oracle Data
Guard broker log files, one for the primary database and one for each standby
database in the Oracle Data Guard configuration. This information is helpful in
determining how best to proceed from this failure.
ORA-16657: reinstatement of database in progress
Cause: Reinstatement of this database was in progress.
Action: None
ORA-16658: unobserved fast-start failover configuration
Cause: The fast-start failover configuration was currently unobserved so failover was
disallowed.
Action: Make sure the observer is running and has connectivity to both the primary
and the target standby databases. Otherwise, disable fast-start failover to perform a
failover in the absence of the observer process.
ORA-16659: failover operation in progress

Cause: A primary database that restarted contacted a standby database that is being
failed over to.
Action: Shut down the primary database and wait for failover to complete on the
standby database. Once failover is complete, restart the old primary database. If the
failover occurred due to fast-start failover, restarting the primary database after
failover is complete allows it to be automatically reinstated as a standby database to
the new primary database.
ORA-16660: fast-start failover operation attempted in absence of a broker
configuration
Cause: An attempt was made to enable or disable fast-start failover when connected
to a standby database for which broker configuration details are currently
unavailable. For instance, the standby database may currently require re-creation (or
flashback reinstantiation) before it may respond to broker client commands.
Action: 1) An attempt to enable or disable (non-FORCE) fast-start failover at this
standby database will be rejected until such time that the broker configuration details
have been made available to that standby database from the primary database. This
normally occurs when the standby database is successfully re-created or flashed back,
and then reenabled at the primary database. 2) Use the FORCE option to override
fast-start failover that has been enabled at the standby database even when the broker
configuration details are currently unavailable to the standby database. In this case,
this status message is only a warning. Note that fast-start failover is not formally
disabled in the broker configuration. The effect of this command issued under these
circumstances may or may not be permanent, depending upon when the primary and
standby databases regain full communication between each other and if the state of
fast-start failover has been altered at the primary database in the meantime.
ORA-16661: the standby database needs to be reinstated
Cause: A role change has caused this database to require reinstatement.
Action: Use the DGMGRL REINSTATE DATABASE command or Enterprise Manager
to reinstate the database. Reinstate the database as soon as possible, because the
database will have to be re-created if another role change occurs while it is in this
state.
ORA-16662: network timeout when contacting a database
Cause: In response to the issued command, the Oracle Data Guard broker attempted
to contact a database in the Oracle Data Guard configuration. That attempt failed
because there was no response from that database after the period of time specified
by the CommunicationTimeout configuration property.
Action: Check the Oracle Data Guard broker log file for the details of the failure. Fix
the problem and try the command again.
ORA-16664: unable to receive the result from a database
Cause: During execution of a command, a database in the Oracle Data Guard broker
configuration failed to return a result.
Action: Check Oracle Data Guard broker log files for the details of the failure. Ensure
network communication is working properly amongst the members of the
configuration. Fix any possible network problems and reissue the command.
ORA-16665: timeout waiting for the result from a database
Cause: The Oracle Data Guard broker was forced to time out a network connection to
a remote database because: - The network call to the remote database did not
ORA-12700 to ORA-19400 69-251
complete in a timely manner. - The remote database was unable to execute the
command due to an instance failure.
Action: Check Data Guard broker log files for the details of the failure. If the network
call did not complete in a timely manner, increase the CommunicationTimeout
configuration property value and reissue the command.
ORA-16666: unable to initiate fast-start failover on a bystander standby database
Cause: The request to initiate a fast-start failover using
DBMS_DG.INITIATE_FS_FAILOVER was made on a bystander standby database.
DBMS_DG.INITIATE_FS_FAILOVER can only be called on either the primary or faststart failover target standby database.
Action: Call DBMS_DG.INITIATE_FS_FAILOVER on either the primary or fast-start
ORA-16667: request Oracle Data Guard broker client to reissue command
Cause: The Oracle Data Guard broker operation required the same command be
issued again from the client.
Action: If DGMGRL or Enterprise Manager has not already done so, reissue the same
command to the Oracle Data Guard broker manually.
ORA-16668: operation cannot be performed on the fast-start failover target standby
database
Cause: The database specified for the operation was the fast-start failover target
standby database.
Action: Retry the operation on a different database. Alternatively, disable fast-start
failover and retry the operation.
ORA-16671: instance-specific property must be set uniquely for instances of an
Oracle RAC database
Cause: An attempt was made to set an instance-specific property to the same value
for all instances of an Oracle RAC database for a property whose value must be
unique for each instance.
Action: Use the EDIT INSTANCE command and specify the SID of each instance
whose instance-specific property value is to be changed.
ORA-16672: some switchover databases need to be restarted manually
Cause: An error occurred during the restart of either the old and the new primary
databases or both in a switchover operation.
Action: Manually restart both the old and new primary databases, including all their
Oracle RAC instances if it is an Oracle RAC database.
ORA-16673: standby database running different Oracle version
Cause: The standby database was running a different version of Oracle than the
primary database.
Action: Ensure the primary and standby databases are running the same versions of
Oracle.
ORA-16674: standby database type has changed
Cause: An attempt to enable a database whose standby type changed from physical or
snapshot to logical (or vice versa) was disallowed.
Action: If the intention is to retain the database conversion to the new type, the
database must be removed and re-added to the configuration in order to obtain
correct values for database properties specific to the new standby type.
ORA-16675: database instance restart required for property value modification to
take effect
Cause: One or more properties that correspond to static initialization parameters were
modified, but the database instances were not restarted. Or, a static initialization
parameter that corresponds to a broker property was modified using an ALTER
SYSTEM SQL*Plus statement.
Action: Restart the database instances for the modified property values to take effect.
If the error persists after having restarted the instance, use the DGMGRL CLI or
Enterprise Manager to modify the property the static initialization parameter
corresponds to.
ORA-16676: RedoRoutes property for two or more databases contains a circular
route
Cause: The value of a RedoRoutes property for two or more databases was set such
that a database that sends redo also receives redo data data in the same route. For
example, A sends to B, B sends to C, and C sends to A.
Action: Correct the setting of the RedoRoutes propety on one or more databases to
eliminate the circular route.
ORA-16677: physical standby database cannot be an alternate destination
Cause: A physical standby database was set as an alternate destination for another
physical standby, or for a far sync instance and the FALLBACK keyword was not
specified.
Action: Check the Oracle Data Guard broker log file for the reason for the failure and
reissue the command. Ensure that a physical standby database is not set to be an
alternate destination for another physical standby. If the physical standby is to be an
alternate destination for a far sync instance, be sure to specify the FALLBACK
keyword.
ORA-16678: unrecognized or duplicate attribute specified
Cause: The specified value contained an unrecognized or duplicated attribute.
Action: Ensure the property string does not contain any undefined or duplicate
attributes. See the Oracle Data Guard broker documentation for supported attributes.
ORA-16679: one or more illegal keywords found
Cause: The specified value contained one or more illegal keywords.
Action: See the Oracle Data Guard broker documentation for the supported
keywords.
ORA-16680: value contains unbalanced set of parentheses
Cause: The specified value contained an unbalanced set of parentheses or a missing
set of parentheses.
Action: Ensure the parentheses are correctly matched and specify parentheses when
required. See the Oracle Data Guard broker documentation for more information.
ORA-16681: value does not contain a colon
Cause: The specified value did not contain a colon (:).
Action: Include the colon (:) in the value.
ORA-12700 to ORA-19400 69-253
ORA-16682: value contains duplicate databases or far sync instances

Cause: The specified value contained the same database or far sync instance multiple
times.
Action: Ensure that a database or far sync instance is specified only once.
ORA-16683: illegal, empty substring specified in property value
Cause: The value specified contained an illegal, empty string or substring, e.g. "()".
Action: Remove the illegal empty strings and retry the command.
ORA-16684: maximum number of destinations exceeded
Cause: The value specified for the RedoRoutes property contained more than the 30
destinations.
Action: Ensure that no more than 30 destinations are specified.
ORA-16685: database does not receive redo data
Cause: The RedoRoutes property for all members of the configuration were set such
that this database did not receive redo data. Or, the transport state of the database
that sends redo data to this database is not valid.
Action: Check the setting of the RedoRoutes property for all members of the
configuration. Ensure that at least one member's RedoRoutes property value is set to
ship redo data to this database. Also check the transport state of the database that
sends redo data to this database.
ORA-16686: database may not receive redo data if redo source is an alternate
destination
Cause: This database may not receive redo data if the redo source is an alternate
destination that does not ship redo to this database.
Action: Ensure that any alternates for the redo source for this database includes this
database in its send to list.
ORA-16687: database has multiple redo sources
Cause: Using the RedoRoutes properties, multiple redo sources were shipping redo to
the standby.
Action: Using the RedoRoutes properties, ensure that only one redo source ships redo
to the standby.
ORA-16688: illegal alternate destination specified for RedoRoutes property
Cause: The specified value contained an alternate destination that was duplicated
with a regular destination or another alternate destination.
Action: Ensure that any database that's specified as an alternate is not also specified as
a regular destination or as an alternate destination for another regular destination in
the same rule.
ORA-16689: illegal sender specified for RedoRoutes property
Cause: A far sync instance or a recovery appliance was specified as the redo source in
a RedoRoutes property rule.
Action: Check the setting of the RedoRoutes property and confirm that a far sync
instance or a recovery appliance is not specified as the redo source in the RedoRoutes
property rule.
ORA-16690: illegal destination specified for RedoRoutes

Cause: A specified destination in a RedoRoutes rule either appears in the primary
setting of the same rule or is the local database itself.
Action: Ensure that any specfifed destination in a RedoRoutes rule neither appears in
the primary setting of the same rule nor be the local database itself.
ORA-16691: cannot remove a configuration member that is specified in a
RedoRoutes property
Cause: An attempt was made to remove a database or far sync instance that is
specified in another configuration member's RedoRoutes property.
Action: First remove the database or far sync instance from all other member's
RedoRoutes property values. Then retry the remove command.
ORA-16692: operation disallowed for a database or far sync instance that sends
redo data
Cause: An attempt was made to delete, disable, or convert a database that sends redo
data to another database or far sync instance.
Action: Reset the value of the RedoRoutes property to the empty string of the
database or far sync instance to be deleted, disabled, or converted (physical standby
database).
ORA-16693: requirements not met for enabling fast-start failover
Cause: The attempt to enable fast-start failover could not be completed because one or
more requirements were not met: - The Oracle Data Guard configuration must be in
either MaxAvailability or MaxPerformance protection mode. - The LogXptMode
property for both the primary database and the fast-start failover target standby
database must be set to either SYNC or FASTSYNC if the configuration protection
mode is set to MaxAvailability mode. - The LogXptMode property for both the
primary database and the fast-start failover target standby database must be set to
ASYNC if the configuration protection mode is set to MaxPerformance mode. - The
primary database and the fast-start failover target standby database must both have
flashback enabled. - No valid target standby database was specified in the primary
database FastStartFailoverTarget property prior to the attempt to enable fast-start
failover, and more than one standby database exists in the Oracle Data Guard
configuration. - fast-start failover target standby database did not receive redo data
directly from the primary database when the protection mode was set to maximum
performance mode. - The primary database has multiple routes to the fast-start
Action: Retry the command after correcting the issue: - Set the Oracle Data Guard
configuration to either MaxAvailability or MaxPerformance protection mode. Ensure that the LogXptMode property for both the primary database and the faststart failover target standby database are set to either SYNC or FASTSYNC if the
configuration protection mode is set to MaxAvailability. - Ensure that the
LogXptMode property for both the primary database and the fast-start failover target
standby database are set to ASYNC if the configuration protection mode is set to
MaxPerformance. - Ensure that both the primary database and the fast-start failover
target standby database have flashback enabled. - Set the primary database
FastStartFailoverTarget property to the DB_UNIQUE_NAME value of the desired
target standby database and set the desired target standby database
FastStartFailoverTarget property to the DB_UNIQUE_NAME value of the primary
database. - Ensure the RedoRoutes property of the primary includes the name of the
fast-start failover target standby database when the protection mode is set to
ORA-12700 to ORA-19400 69-255
maximum performance mode. - Ensure the RedoRoutes property of the primary

database has only one route to the fast-start failover target standby database.
ORA-16694: one or more databases involved for switchover need to be restarted
Cause: An error occurred during the restart of either the old and the new primary
databases or both in a switchover operation.
Action: Manually restart both the old and new primary databases, including all their
Oracle RAC instances if it is an Oracle RAC database.
ORA-16695: redo transport mode incompatible with RedoRoutes property value
Cause: The standby database could not be set to receive redo data from another
standby database or a far sync instance because either a RedoRoutes rule for that
standby did not specify ASYNC or the database's LogXptMode property was not set
to ASYNC.
Action: A standby database or far sync instance can only send redo data in
asynchronous mode. Set the standby database's LogXptMode property to ASYNC
before changing the RedoRoutes of the standby that is to send redo data. Or, specify
ASYNC in the sending database's RedoRoutes property to override the value
specified in the receiving database's LogXptMode property.
ORA-16696: redo source is disabled
Cause: An attempt was made to enable a database whose redo source was disabled.
Action: Enable the redo source first and then retry the command.
ORA-16697: wrong standby type specified for RedoRoutes property modification
Cause: A logical standby database or snapshot standby database was specified to
send redo data.
Action: Check the setting of the RedoRoutes property and confirm that a primary
database, physical standby database, or far sync instance is specified to send the redo
data.
ORA-16698: member has a LOG_ARCHIVE_DEST_n parameter with SERVICE
attribute set
Cause: One or more LOG_ARCHIVE_DEST_n initialization parameters that contain a
SERVICE attribute for another member in the configuration were set on the new
member when attempting to add a standby database or far sync instance to the
configuration.
Action: Clear all LOG_ARCHIVE_DEST_n initialization parameters that contain a
SERVICE attribute for another member in the configuration on the new member to be
added.
ORA-16699: connect identifier not specified
Cause: The connect identifier was not specified for the DGMGRL CLI ADD
command.
Action: Retry the ADD command with a connect identifier for the object to be added.
ORA-16700: the standby database has diverged from the primary database
Cause: The primary database may have been flashed back or restored from a backup
set and then reopened with the RESETLOGS option.
Action: Re-create the standby database from the primary database or flash back the
standby database to the same point the primary database had been flashed back to.
ORA-16701: Oracle Data Guard broker command failed

Cause: The command to modify or query the database failed.
ORA-16702: Oracle Data Guard broker command warning
Cause: The command to modify or query the database resulted in a warning.
Action: Check the Oracle Data Guard broker log file for the warning and, if necessary,
ORA-16703: cannot set property while the database is enabled
Cause: An attempt was made to change a database property while the database was
enabled.
Action: Disable the database first, update the property and then, reenable the
database.
ORA-16704: standby database not valid for primary database
Cause: The standby database was not added to the Oracle Data Guard broker
configuration because it was not a valid standby database for the primary database.
Action: Add a database to the Oracle Data Guard broker configuration that is a valid
standby database to the primary database.
ORA-16706: Oracle Data Guard broker worker process not available
Cause: The Oracle Data Guard broker worker process was not available to service the
request.
ORA-16707: the value of the property string is invalid, valid values are string
Cause: An invalid property value was specified while broker management of the
database was disabled.
Action: Reset the property to a valid value.
ORA-16708: the state supplied to broker is invalid
Cause: The state name specified was invalid for the database.
Action: Check the state name and reissue the command.
ORA-16709: standby archived log location settings conflict with database recovery
area
Cause: The StandbyArchiveLocation or AlternateLocation property was set to
USE_DB_RECOVERY_FILE_DEST, but the initialization parameter
DB_RECOVERY_FILE_DEST did not specify a valid destination.
Action: Use a value other than USE_DB_RECOVERY_FILE_DEST for
StandbyArchiveLocation or AlternateLocation, or set up a valid database recovery
area by setting DB_RECOVERY_FILE_DEST to a valid destination.
ORA-16710: snapshot standby database should be converted back to a physical
standby database as soon as possible
Cause: A failover causes this snapshot standby database to enter a state that requires
it to be re-created if another failover occurs before it is converted back to a physical
standby database.
ORA-12700 to ORA-19400 69-257
Action: Reenable the snapshot standby database if it is disabled and convert it back to
a physical standby database as soon as possible because the snapshot standby
database will have to be re-created if another failover occurs while it is in this state.
ORA-16713: The Oracle Data Guard broker command timed out.
Cause: The Oracle Data Guard broker timed out the command.
Action: Verify that the command is valid for the database and then retry the
command.
ORA-16714: the value of property string is inconsistent with the database setting
Cause: The value of the specified configuration property was inconsistent with
database in-memory settings or server parameter file settings. This may be caused by
changing an initialization parameter that corresponds to a configuration property.
Action: Query the InconsistentProperties property on the database to determine the
which properties are set inconsistently. Reset the properties to make them with the
database settings.
ORA-16715: redo transport-related property string of standby database "string" is
inconsistent
Cause: The value of the specified redo transport-related configuration property of the
given standby database was inconsistent with the primary database redo transport
service setting. This may be caused by changing an initialization parameter that
corresponds to a configuration property.
Action: Query the InconsistentLogXptProps property on the primary database to
determine which redo transport properties are set inconsistently Reset the properties
on the standby database to make them consistent with the primary database redo
transport settings.
ORA-16716: clearing parameter LOG_ARCHIVE_DEST failed
Cause: An attempt to clear the LOG_ARCHIVE_DEST parameter failed.
ORA-16717: clearing parameter LOG_ARCHIVE_DUPLEX_DEST failed
Cause: An attempt to clear the LOG_ARCHIVE_DUPLEX_DEST parameter failed.
ORA-16718: failed to locate database
Cause: The Oracle Data Guard broker was unable to locate the database in the broker
configuration.
Action: Add the database to the broker configuration and then reissue the command.
ORA-16719: unable to query V$ARCHIVE_DEST fixed view
Cause: The broker failed to query the V$ARCHIVE_DEST fixed view."
Action: Test and clear the problem using SQL*Plus.
ORA-16720: no LOG_ARCHIVE_DEST_n initialization parameters available
Cause: All LOG_ARCHIVE_DEST_n initialization parameters were in use, or all
initialization parameters from LOG_ARCHIVE_DEST_1 through
LOG_ARCHIVE_DEST_10 that can support SYNC or ALTERNATE were in use.
Action: Clear one or more LOG_ARCHIVE_DEST_n initialization parameters so that
Data Guard broker can use them to set up the primary database redo transport.
ORA-16721: unable to set LOG_ARCHIVE_DEST_n initialization parameters

Cause: The broker was unable to set one or more LOG_ARCHIVE_DEST_n
initialization parameters.
Action: Check the Oracle Data Guard broker log file and the Oracle alert log files for
more details.
ORA-16722: unable to set LOG_ARCHIVE_DEST_STATE_n initialization
parameters
Cause: The broker was unable to set one or more LOG_ARCHIVE_DEST_STATE_n
initialization parameters.
Action: Check the Oracle Data Guard broker log file and the Oracle alert log files for
more details.
ORA-16723: setting AlternateLocation property conflicts with the redo transport
setting
Cause: The standby database was not using standby redo logs, and the redo transport
service to the standby database is set to a nonzero value for the ReopenSecs property
and a value of zero for the MaxFailure property. In this case, the redo transport
service will attempt to send redo data to the standby database indefinitely and never
switch to the alternate destination.
Action: Any one of the following actions will solve the problem: - add standby redo
logs to the standby database. - set ReopenSecs property to zero. - set MaxFailure
property to a nonzero value. After performing one of the above actions, reset the
standby database AlternateLocation property.
ORA-16724: cannot resolve gap for one or more standby databases
Cause: The primary database could not resolve a gap request from one or more
standby databases.
Action: To see which standby database has an unresolvable gap, check the status of
the primary database using either Enterprise Manager or the DGMGRL CLI SHOW
DATABASE command. Copy the missing archived log files from either backups or
from another database in the configuration that has the files to the standby database
that is missing the files.
ORA-16727: cannot close database
Cause: The Oracle Data Guard broker could not close the database.
Action: Terminate any active sessions connected to the database and then reissue the
command.
ORA-16728: consistency check for property string found string error
Cause: The consistency check for the specified property failed due to the error shown.
Action: Check the error message and clear the error.
ORA-16729: validation of value for property string found string error
Cause: The property value validation failed due to the error shown.
Action: Check the error message and clear the error.
ORA-16730: SQL Apply was not started
Cause: SQL Apply was not started because there were no pluggable databases opened
in read/write mode.
Action: Open at least one pluggable database in read/write mode. Data Guard will
then automatically start SQL Apply.
ORA-12700 to ORA-19400 69-259
ORA-16731: No pluggable databases are opened in read/write mode

Cause: The operation failed because there were no pluggable databases opened in
read/write mode.
Action: Open at least one pluggable database in read/write mode and retry the
command.
ORA-16732: Oracle Clusterware is restarting the database instance
Cause: The Oracle Data Guard broker operation required this database instance to be
shut down and restarted.
Action: If Oracle Clusterware has not already done so, shut down the Oracle instance
and then restart it.
ORA-16736: unable to find the destination entry of standby database "string" in V
$ARCHIVE_DEST
Cause: Either the standby destination was manually changed or deleted outside of
Oracle Data Guard broker, or no entry was available for the Oracle Data Guard
broker to use.
Action: Clean up the destination setting, remove the unused settings, and reset the
redo transport service.
ORA-16737: the redo transport service for standby database "string" has an error
Cause: A communication problem with the standby database caused the redo
transport to fail.
Action: Query the LogXptStatus property to see the error message. Check the Oracle
Data Guard broker log file and the Oracle alert log file for more details.
ORA-16738: redo transport service for database "string" is not running
Cause: The redo transport service for the specified standby database was not running.
Action: Check the Oracle Data Guard broker log file or the Oracle alert log file for
more details. If necessary, start the redo transport service for the standby database.
ORA-16739: redo transport service for standby database "string" is running
Cause: The redo transport service for the standby database was running.
Action: Check the Oracle Data Guard broker log file for more details. If necessary,
stop the redo transport service for the standby database.
ORA-16740: redo transport service for standby database "string" incorrectly set to
ALTERNATE
Cause: The redo transport service to the standby database was set to ALTERNATE
when no other destination was set to alternate to this destination.
Action: Reenable the standby database or the entire configuration to allow the
configuration property settings to be propagated to the initialization parameters.
ORA-16741: the destination parameter of standby database "string" has incorrect
syntax
Cause: The destination defined in the server parameter file of the primary database
had incorrect syntax and Data Guard broker failed to update the destination when
redo transport services were enabled.
Action: Fix the syntax error in the primary database server parameter file or remove
the entry from the server parameter file. Also, check the values of the redo transportrelated properties for the specified standby database.
ORA-16742: the standby database "string" has exhausted its quota

Cause: The standby database exhausted its quota for storing archived redo logs.
Action: Remove some archived redo logs from the standby database or increase its
quota.
ORA-16743: cannot determine status of redo transport service for standby database
"string"
Cause: The status of redo transport to the specified standby database could not be
determined.
Action: Check the Oracle Data Guard broker log file and the Oracle alert log file for
more details.
ORA-16744: The DG_CONFIG list of LOG_ARCHIVE_CONFIG parameter is full.
Cause: The DG_CONFIG list of the LOG_ARCHIVE_CONFIG attribute was full and
the Oracle Data Guard broker was not able to add a new DB_UNIQUE_NAME to the
list.
Action: Remove some unused entries in the DG_CONFIG list, then reenable the
database.
ORA-16745: unable to add DB_UNIQUE_NAME "string" into the DG_CONFIG list
because it is full
Cause: The DG_CONFIG list of the LOG_ARCHIVE_CONFIG attribute was full and
the Oracle Data Guard broker was not able to add the specified DB_UNIQUE_NAME
to the list.
Action: Remove some unused entries in the DG_CONFIG list then reenable the
database.
ORA-16746: Oracle Data Guard broker cannot mount the database
Cause: The Oracle Data Guard broker failed to mount the database.
more details.
ORA-16747: logical standby database guard could not be turned on
Cause: The Oracle Data Guard broker could not turn on the logical standby database
guard.
more details.
ORA-16748: Oracle Data Guard broker cannot open the primary database
Cause: The Oracle Data Guard broker failed to open the primary database.
more details.
ORA-16749: switchover to logical standby database failed
Cause: The Oracle Data Guard broker failed to switch a logical standby database over
to a primary database.
more details.
ORA-16750: failed to activate logical standby database
Cause: The Oracle Data Guard broker failed to activate a logical standby database.
ORA-12700 to ORA-19400 69-261
more details.
ORA-16751: failed to switchover to physical standby database
Cause: The Oracle Data Guard broker failed to switch a physical standby database
over to a primary database.
more details.
ORA-16753: Oracle Data Guard broker cannot open standby database
Cause: The Oracle Data Guard broker failed to open the standby database.
more details.
ORA-16754: failed to activate physical standby database
Cause: The Oracle Data Guard broker failed to activate the physical standby database.
more details.
ORA-16755: failed to set initialization parameter
Cause: The Oracle Data Guard broker failed to set an initialization parameter using
either the ALTER SYSTEM SET or ALTER SYSTEM RESET command.
more details.
ORA-16757: unable to get the value of this property
Cause: The Oracle Data Guard broker failed to get the value for the specified property
because the value for the specified property is not available for the current database
role.
Action: If the value of the specified property is not available for the current role of the
database, specify this property for a database for which the value is available.
Otherwise, check the Oracle Data Guard broker log file for more details.
ORA-16758: the specified apply instance is not running
Cause: The Oracle Data Guard broker could not start apply services on the specified
instance because that instance was not running.
Action: Start the instance and then retry the command.
ORA-16759: cannot start SQL Apply with initial SCN
Cause: The Oracle Data Guard broker failed to start SQL Apply with an initial system
change number (SCN).
more details.
ORA-16760: cannot start SQL Apply
Cause: The Oracle Data Guard broker failed to start SQL Apply.
more details.
ORA-16761: cannot stop SQL Apply
Cause: The Oracle Data Guard broker failed to stop SQL Apply.
more details.
ORA-16762: invalid database state
Cause: Database was not in the intended state.
Action: Determine the reason why the database is not running in the intended state
and reissue the command.
ORA-16763: redo transport service for a member is running
Cause: The redo transport service for a member was running.
Action: For more details, check the status of the primary database using either Oracle
Enterprise Manager or the DGMGRL CLI SHOW DATABASE command. If necessary,
stop the redo transport service to the member.
ORA-16764: redo transport service to a member is not running
Cause: The redo transport service to a member was not running.
Action: For more details, check the status of the primary database using either Oracle
Enterprise Manager or the DGMGRL CLI SHOW DATABASE command. If necessary,
start the redo transport service to the member.
ORA-16765: Redo Apply is running
Cause: Redo Apply was running when it should have been stopped.
Action: If necessary, stop Redo Apply.
ORA-16766: Redo Apply is stopped
Cause: Redo Apply was stopped when it should have been running.
Action: Check the alert log to see why Redo Apply terminated, correct any problems
that may exist, and restart Redo Apply by setting the physical standby database state
to APPLY-ON.
ORA-16767: SQL Apply is running
Cause: SQL Apply was running when it should have been stopped."
Action: If necessary, stop SQL Apply.
ORA-16768: SQL Apply is stopped
Cause: SQL Apply was stopped when it should have been running."
Action: Check the alert log to see why SQL Apply terminated, correct any problems
that may exist, and restart SQL Apply by setting the logical standby database state to
APPLY-ON.
ORA-16769: the physical standby database is open read-only
Cause: All instances in the physical standby database were put into a read-only state
instead of APPLY-OFF.
Action: Issue the EDIT DATABASE SET STATE command to set the database to the
APPLY-OFF state.
ORA-16770: Redo Apply not started since physical standby database is opening
Cause: Redo Apply services could not be started on the physical standby database
because it was being opened. The Oracle Data Guard broker will start Redo Apply
services once the physical standby database has been opened.
ORA-12700 to ORA-19400 69-263
ORA-16771: failover to a physical standby database failed

Cause: The Oracle Data Guard broker encountered errors when converting a physical
standby database to a primary database.
more details.
ORA-16772: switchover to a standby database failed
Cause: The Oracle Data Guard broker encountered errors when switching over to the
specified standby database.
more details.
ORA-16773: cannot start Redo Apply
Cause: The Oracle Data Guard broker failed to start Redo Apply.
more details. If the database is already open, the broker will not start Redo Apply if
the Oracle Active Data Guard option is not enabled.
ORA-16774: cannot stop Redo Apply
Cause: The Oracle Data Guard broker failed to stop Redo Apply.
more details.
ORA-16775: target standby database in broker operation has potential data loss
Cause: The target standby database specified for the broker operation did not have all
the redo data from the primary database.
Action: Confirm that the redo transport service on the primary database is
functioning correctly by checking its status using either Enterprise Manager or the
DGMGRL CLI SHOW DATABASE command. Reissue the broker command once all
redo data is available on the target standby database.
ORA-16776: health check of the redo transport service failed
Cause: The Oracle Data Guard broker could not complete the health check for the
redo transport service.
more details.
ORA-16777: unable to find the destination entry of a standby database in V
$ARCHIVE_DEST
Cause: Either a destination was manually deleted or no entry was available for Oracle
Data Guard.
more details. The redo transport service may need to be reset.
ORA-16778: redo transport error for one or more databases
Cause: The redo transport service was unable to send redo data to one or more
standby databases.
more details. Query the LogXptStatus property to see the errors.
ORA-16779: the destination parameter of a database is set incorrectly

Cause: The destination was defined in the LOG_ARCHIVE_DEST_n server parameter
file with incorrect syntax. The Oracle Data Guard broker failed to update the
destination when the redo transport was turned on.
Action: Check the Oracle Data Guard broker log file to see which database has the
problem. Fix the syntax error in the server parameter file or remove the entry from
the server parameter file. Check if the syntax of the redo transport-related properties
are correct.
ORA-16780: a database has exhausted its archived redo log storage quota
Cause: A database has exhausted its quota for storing archived redo logs.
Action: Check the Oracle Data Guard broker log file to see which database has the
problem. Remove some archived logs at the standby database or increase its quota.
ORA-16781: cannot determine status of redo transport service for standby database
Cause: The status of redo transport to the specified standby database could not be
determined.
more details.
ORA-16782: instance not open for read and write access
Cause: The database was mounted on an instance but not opened for read and write
access.
Action: For more details, check the status of the database using either Enterprise
Manager or the DGMGRL CLI SHOW DATABASE command. If possible, open the
instance manually.
ORA-16783: cannot resolve gap for database string
Cause: The primary database could not resolve a gap request from the specified
standby database(s).
Action: Copy the missing archived redo log files from either backups or from another
database in the configuration that has the files to the standby database(s) missing the
files.
ORA-16784: database name specified by Dependency property is incorrect
Cause: The database name, that should be the value of the DB_UNIQUE_NAME
initialization parameter, specified in the Dependency property was incorrect.
Action: Reset the Dependency property to the correct name of the database.
ORA-16785: the database is in NOARCHIVELOG mode
Cause: The database was in NOARCHIVELOG mode when it was either a primary
database or when it was a standby database that was being switched over to be a
primary database.
Action: Set the database to ARCHIVELOG mode by issuing the ALTER DATABASE
ARCHIVELOG command.
ORA-16786: unable to access Oracle Data Guard broker configuration files
Cause: The Oracle Data Guard broker configuration files did not exist or or could not
be accessed.
Action: Check the Oracle Data Guard broker log file for more details.
ORA-12700 to ORA-19400 69-265
ORA-16788: unable to set one or more database configuration property values

Cause: This situation occurred when the broker attempted to set database
configurable property values into the database by issuing ALTER SYSTEM or ALTER
DATABASE commands. Typical causes of this error are: - The values of redo
transport-related properties contain syntax syntax errors. - The value of the
LogArchiveTrace property was out of range.
Action: Check the Oracle Data Guard broker log file to see which property has the
problem and set the property to the correct value.
ORA-16789: standby redo logs configured incorrectly
Cause: Standby redo logs were not configured or were configured incorrectly for the
database.
Action: Standby redo logs are required when the redo transport mode is set to SYNC
or ASYNC. Check the Oracle Data Guard documentation to find more information
about the correct configuration of standby redo logs.
ORA-16790: the value of the configurable property is invalid
Cause: An invalid property value was entered, or a RESET was attempted on a
property for which no Broker default value exists.
Action: Set the property to a correct value.
ORA-16791: unable to check the existence of the standby redo logs
Cause: The database may not be mounted, or the query of the V$STANDBY_LOG
fixed view failed.
Action: Ensure the database is mounted and query the V$STANDBY_LOG fixed view
to see if the problem has been corrected, and retry the operation.
ORA-16792: configurable property value is inconsistent with database setting
Cause: The values of one or more configurable properties were inconsistent with
database in-memory settings or server parameter file settings. This may happen by
directly altering initialization parameters instead of editing configurable property
values using Oracle Data Guard broker.
Action: Query the InconsistentProperties property on the database or check the Oracle
Data Guard broker log file to find which properties are set inconsistently. Reset these
properties to make them consistent with the database settings. Alternatively, enable
the database or the entire configuration to allow the configurable property settings to
be propagated to the initialization parameters.
ORA-16793: logical standby database guard is off
Cause: The logical standby database guard was turned off.
Action: Issue the ALTER DATABASE GUARD ALL command to turn the guard on
and verify that Data Guard health check error or warning is cleared.
ORA-16794: database guard is on for primary database
Cause: The database guard was turned on for the primary database.
Action: Issue the ALTER DATABASE GUARD NONE command to turn off the guard
and verify that Data Guard health check error or warning is cleared.
ORA-16795: the standby database needs to be re-created
Cause: A switchover or failover operation caused this database to require re-creation.
The database was marked for re-creation because it was not a viable standby database
for the new primary database. Until this error status is resolved for this database,
information about this database and the broker configuration to which it belongs is
unavailable to a broker client that is connected to this database. Therefore, all
commands directed by that client to this database cannot be completed.
Action: Re-create (or flash back) the standby database. Connect to the primary
database in the broker configuration and reenable broker management of that
database. Once enabled, it is possible to connect to that standby database and manage
it with the broker. Alternatively, many client commands that cannot be completed at
the standby database when in this error state can be completed successfully when
issued to the primary database. In this case, simply reconnect to the primary database
and retry the command.
ORA-16796: one or more properties could not be imported from the member
Cause: The broker was unable to import property values for the member being added
to the broker configuration. This error indicates: - The Oracle Net service name
specified in DGMGRL CREATE CONFIGURATION, ADD DATABASE, ADD
FAR_SYNC, or ADD RECOVERY_APPLIANCE command was not one that provides
access to the member being added. - There were no instances running for the member
being added.
Action: Remove the member from the configuration using the REMOVE
CONFIGURATION, REMOVE DATABASE, REMOVE FAR_SYNC, or REMOVE
RECOVERY_APPLIANCE command. Make sure that the member to be added has at
least one instance running and that the Oracle Net service name provides access to the
running instance. Also, check the broker log file for additional information. Then,
reissue the CREATE CONFIGURATION, ADD DATABASE, ADD FAR_SYNC, or
ADD RECOVERY_APPLIANCE command.
ORA-16797: member is not using a server parameter file
Cause: The member was not using a server parameter file or the broker was unable to
access the server parameter file.
Action: Issue the CREATE SPFILE='..' FROM PFILE='...' command to create a server
parameter file and then restart the member to use it.
ORA-16798: unable to complete recovery during failover
Cause: The physical standby database could not complete recovery during failover.
Action: Check the Oracle Data Guard broker log file and the Oracle alert log files to
see more details on the reason for the failure.
ORA-16799: Redo Apply is not running
Cause: Either the Oracle Data Guard broker configuration indicated that Redo Apply
was turned off, or the MRP0 recovery process was not running. As a result, Redo
Apply-related properties could not be set.
Action: Turn on Redo Apply through Oracle Data Guard broker and reissue the
command to set a Redo Apply-related property.
ORA-16800: redo transport service for a standby database incorrectly set to
ALTERNATE
Cause: The redo transport service for a standby database was set to ALTERNATE
when no other destination is set to alternate to this destination.
Action: Reenable the standby database or the entire configuration to allow the
configuration property settings to be propagated to the initialization parameters.
ORA-12700 to ORA-19400 69-267
ORA-16801: redo transport-related property is inconsistent with database setting

Cause: The values of one or more redo transport-related configuration properties
were inconsistent with database in-memory settings or server parameter file settings.
This may happen by directly altering initialization parameters instead of editing
configurable property values using Oracle Data Guard broker.
Action: Query the InconsistentLogXptProps property on the primary database or
check the Oracle Data Guard broker log file to find which properties are set
inconsistently. Reset these properties to make them consistent with the database
settings. Alternatively, enable the database or the entire configuration to allow the
configurable property settings to be propagated to the initialization parameters.
ORA-16802: downgrading redo transport mode from SYNC disallowed
Cause: An attempt was made to downgrade the redo transport mode of a standby
database from SYNC to ASYNC when the configuration was in Maximum Protection
or Maximum Availability mode and the primary database was an Oracle RAC
database. This was disallowed even though there may have been other standby
databases with redo transport modes set to SYNC to support the protection mode.
Action: Do one of the following if the redo transport mode of the standby must be
downgraded: - Shut down all instances of the primary database and restart one
instance with the initialization parameter CLUSTER_DATABASE set to FALSE.
Downgrade the redo transport mode of the standby database of interest. Then,
shutdown the instance, set the the CLUSTER_DATABASE initialization parameter to
TRUE, and restart all primary database instances. - Downgrade the protection mode
to Maximum Performance mode and then, downgrade the redo transport mode of the
standby database of interest. Finally, upgrade the protection mode. This will require a
restart of all primary database instances if upgrading to Maximum Protection mode.
Note that the above only works when there is at least one standby database in the
configuration that has its redo transport mode set to SYNC.
ORA-16803: unable to query a database table or fixed view
Cause: Querying a database table or fixed view failed. The database may not be
opened or mounted.
Action: Check the Oracle Data Guard broker log file for more details.
ORA-16804: one or more configuration properties have invalid values
Cause: Oracle Data Guard broker health check detected that one or more
configuration properties in the broker configuration had invalid values. The property
values were changed while broker management of the database was disabled.
Action: Check Data Guard broker log file for more details on which properties have
invalid values and reset them through the Oracle Data Guard broker.
ORA-16805: change of LogXptMode property violates overall protection mode
Cause: The broker disallowed the attempt to change the LogXptMode configurable
property for the standby database because, if allowed, the overall protection mode for
the configuration would have been violated.
Action: If the LogXptMode configuration property must be changed for the specified
standby database, first downgrade the overall protection mode for the broker
configuration. After that operation has completed, the LogXptMode configuration
property for the standby database can be changed.
ORA-16806: supplemental logging is not turned on
Cause: Supplemental logging was not turned on while there was a logical standby
database in the configuration. This could happen either on the primary database or on
the logical standby database that was being switched over to become the primary
database.
Action: Check the Oracle Data Guard broker log file for more details. Issue the
ALTER DATABASE ADD SUPPLEMENTAL LOG DATA (PRIMARY KEY, UNIQUE
INDEX) COLUMNS to add supplemental logging.
ORA-16807: unable to change database protection mode
Cause: An attempt to issue the ALTER DATABASE SET STANDBY TO MAXIMIZE
{PROTECTION | AVAILABILITY | PERFORMANCE} failed.
more information.
ORA-16808: primary database is not open
Cause: A prior attempt to open the primary database was disallowed because the
primary had shut itself down earlier after being isolated from both the fast-start
failover observer and the target standby database for more than
FastStartFailoverThreshold seconds. It was assumed that a fast-start failover was
underway. Since that time, re-contact with either the observer or the target standby
database indicates that no such failover had actually occurred. The primary database
can now be opened.
Action: Open the database by issuing the SQL*Plus ALTER DATABASE OPEN
command.
ORA-16809: multiple warnings detected for the database
Cause: The broker detected multiple warnings for the database.
Action: To get a detailed status report, check the status of the database specified using
either Enterprise Manager or the DGMGRL CLI SHOW DATABASE command.
ORA-16810: multiple errors or warnings detected for the database
Cause: The broker detected multiple errors or warnings for the database.
ORA-16811: apply instance not recorded by the Oracle Data Guard broker
Cause: The broker did not register an apply instance for a standby database.
Action: Reenable the standby database to clear the error.
ORA-16812: log apply service not running on apply instance recorded by the broker
Cause: Log apply services were not running on the instance the Data Guard broker
expected them to be running upon.
ORA-16813: log apply service not running on apply instance string recorded by the
broker
Cause: Log apply services were not running on the instance the Data Guard broker
expected them to be running upon.
ORA-16814: incorrect redo transport setting for AlternateLocation for standby
database
Cause: The Oracle Data Guard broker detected an incorrect redo transport setting for
a standby database AlternateLocation property. The incorrect setting could be one of
ORA-12700 to ORA-19400 69-269
the following: - The AlternateLocation property was empty, but the redo transport to
the standby database had an ALTERNATE setting. - The AlternateLocation property
was not empty and the redo transport to the standby database had no ALTERNATE
setting. - The AlternateLocation property did not match the ALTERNATE setting in
the redo transport. The mismatch may include service string, directory specification
of the alternate location, or the DB_UNIQUE_NAME attribute. - The
LOG_ARCHIVE_DEST_STATE_n parameter corresponding to the alternate location
was not set to ALTERNATE. - The flash recovery area was being used by the standby
database for archived logs, but the redo transport to the standby database still had an
ALTERNATE setting for the AlternateLocation property. Data Guard broker log files
provide more details on which of the above cases caused the error.
Action: Reenable the primary database to clear the error.
ORA-16815: incorrect redo transport setting for AlternateLocation for standby
database "string"
Cause: The Oracle Data Guard broker detected an incorrect redo transport setting for
a standby database AlternateLocation property. The incorrect setting could be one of
the following: - The AlternateLocation property was empty, but the redo transport to
the standby database had an ALTERNATE setting. - The AlternateLocation property
was not empty and the redo transport to the standby database had no ALTERNATE
setting. - The AlternateLocation property did not match the ALTERNATE setting in
the redo transport. The mismatch may include service string, directory specification
of the alternate location, or the DB_UNIQUE_NAME attribute. - The
LOG_ARCHIVE_DEST_STATE_n parameter corresponding to the alternate location
was not set to ALTERNATE. - The flash recovery area was being used by the standby
database for archived logs, but the redo transport to the standby database still had an
ALTERNATE setting for the AlternateLocation property. Data Guard broker log files
provide more details on which of the above cases caused the error.
Action: Reenable the primary database to clear the error.
ORA-16816: incorrect database role
Cause: The Oracle Data Guard broker detected that the specified database had a
different database role than that recorded in the Oracle Data Guard broker
configuration. This could be the result of a failed switchover or failover operation, or
a switchover or failover operation performed with SQL*Plus.
Action: Check the Oracle Data Guard broker documentation to see how to recover
from failed role change operations, or from role changes that were performed using
SQL*Plus for databases managed by Oracle Data Guard broker.
ORA-16817: unsynchronized fast-start failover configuration
Cause: The fast-start failover target standby database was not synchronized with the
primary database. As a result, a fast-start failover could not happen automatically in
case of a primary database failure.
Action: Ensure that the fast-start failover target standby database is running and that
the primary database can ship redo data to it. When the standby database has
received all of the redo data from the primary database, the primary and standby
databases will then be synchronized. The Oracle Data Guard configuration may then
fail over automatically to the standby database in the event of loss of the primary
database.
ORA-16818: fast-start failover suspended
Cause: The primary database was intentionally shutdown. As a result, a fast-start
failover could not happen automatically.
Action: Start the primary database. This effectively restores the ability to
automatically perform a fast-start failover in the event of a failure of the primary
database.
ORA-16819: fast-start failover observer not started
Cause: The observer for fast-start failover was not started. As a result, fast-start
failover could not happen in the case of a primary database failure.
Action: Start the fast-start failover observer by using, for example, the DGMGRL
START OBSERVER command.
ORA-16820: fast-start failover observer is no longer observing this database
Cause: A previously started observer was no longer actively observing this database.
A significant amount of time elapsed since this database last heard from the observer.
Possible reasons were: - The host where the observer was running was not available. The network connection between the observer and this database was not available. The observer process was terminated unexpectedly.
Action: Check the reason why the observer cannot contact this database. If the
problem cannot be corrected, stop the current observer by connecting to the Oracle
Data Guard configuration and issue the DGMGRL STOP OBSERVER command.
Then, restart the observer on another host. Finally, use the DGMGRL START
OBSERVER command to start the observer on the other host.
ORA-16821: logical standby database dictionary not yet loaded
Cause: The logical standby database had not loaded the dictionary. This status was
detected by the broker health check mechanism. Alternatively, this status may be
returned when attempting to switch or fail over to a logical standby database that had
not yet loaded its dictionary.
Action: Start SQL Apply on the logical standby database, if it is not already running,
and wait for it to reach the APPLYING state.
ORA-16822: new primary database not yet ready for standby database
reinstatement
Cause: The new primary database, as a result of a logical standby database failover
operation, had not fully completed the failover operation. An attempt to reinstate a
disabled standby database could not be completed until failover completed on the
new primary database.
Action: Wait until the failover operation has completed on the new primary database.
Then retry the reinstate operation.
ORA-16823: redo transport mode is incompatible for current operation
Cause: The redo transport mode of this database was incompatible for this broker
operation.
Action: Reset the LogXptMode database property for this database and retry the
broker operation.
ORA-16824: multiple warnings, including fast-start failover-related warnings,
detected for the database
Cause: The broker detected multiple warnings for the database. At least one of these
warnings may have prevented fast-start failover from occurring.
ORA-12700 to ORA-19400 69-271
ORA-16825: multiple errors or warnings, including fast-start failover-related errors

or warnings, detected for the database
Cause: The broker detected multiple errors or warnings for the database. At least one
of these errors or warnings may have prevented a fast-start failover from occurring.
ORA-16826: apply service state is inconsistent with the DelayMins property
Cause: This warning was caused by one of the following reasons: - The apply service
was started without specifying the real-time apply option or without the NODELAY
option when the DelayMins property was set to zero. - The apply service was started
with the real-time apply option or with the NODELAY option when the DelayMins
property was set to a value greater than zero.
Action: Reenable the standby database to allow the broker to restart the apply service
with the apply options that are consistent with the specified value of the DelayMins
property.
ORA-16827: Flashback Database is disabled
Cause: The broker detected that the Flashback Database feature was disabled. With
Flashback Database disabled, the broker would not be able to: - reinstate a database
that required reinstatement. - convert a physical standby database to a snapshot
standby database. - convert a snapshot standby database to a physical standby
database. Flashback Database may been disabled manually with the ALTER
DATABASE FLASHBACK DATABASE OFF command or automatically by the
database in the event of an error.
Action: Check the database alert log to determine whether Flashback Database was
disabled due to errors and then correct the problem. If Flashback Database had been
manually disabled, reenable Flashback Database with the ALTER DATABASE
FLASHBACK DATABASE ON command. If, after enabling Flashback Database, the
database still cannot be reinstated or converted, you must re-create the database from
a copy of the primary database.
ORA-16828: invalid value specified for REDO_TRANSPORT_USER initialization
parameter
Cause: An invalid value was specified for the REDO_TRANSPORT_USER
initialization parameter. The length of the user name exceeded 30 characters.
Action: Check the documentation and specify a new value for the
REDO_TRANSPORT_USER initialization parameter.
ORA-16829: fast-start failover configuration is lagging
Cause: The fast-start failover target standby database was not within the lag limit
specified by the FastStartFailoverLagLimit configuration property. As a result, a faststart failover could not happen in the event of a primary database failure.
Action: Ensure that the fast-start failover target standby database is running and
applying redo data and that the primary database is successfully transmitting redo
data. If this condition persists consider raising the value of the
FastStartFailoverLagLimit configuration property.
ORA-16830: primary isolated from fast-start failover partners longer than
FastStartFailoverThreshold seconds: shutting down
Cause: The primary database was isolated from both the observer and target standby
database for longer than the seconds specified by the FastStartFailoverThreshold
property. A fast-start failover probably occurred. If the
FastStartFailoverPmyShutdown configuration property was set to TRUE, the broker

will shut down the primary database in this situation.
Action: Ensure one instance of this database is running and the database is mounted
on that instance so that the broker may reinstate the old primary database.
ORA-16831: operation not allowed on this member
Cause: The Oracle Data Guard broker operation was not allowed for the specified
member of the Oracle Data Guard broker configuration.
Action: Check the documentation for the Oracle Data Guard broker command and
then reissue the command with the correct member.
ORA-16832: user-configurable fast-start failover initiated: shutting down
Cause: The broker initiated a fast-start failover to the target standby database because
a user-configurable condition was detected on the primary database. In addition, the
broker shut down the primary database.
Action: Correct the problem on the old primary database that caused the broker to
initiate a fast-start failover, then reinstate the old primary database.
ORA-16833: no logging operations detected on database
Cause: The broker detected that no logging operations were performed on this
database. The data modified by these operations may be lost if failover or switchover
was performed.
Action: Use Data Repair Advisor to determine which operations were not logged
before attempting a switchover or failover.
ORA-16834: control file corruptions detected on database
Cause: The broker detected control files corruptions. Many database operations,
including switchover and failover, may not be possible.
Action: Use Data Repair Advisor to determine the extent of the corruptions and how
to repair them.
ORA-16835: standby database has one or more unavailable standby redo log groups
Cause: The broker detected that the standby database had one or more unavailable
standby redo log groups.
Action: Use Data Repair Advisor to determine which standby redo log groups are
unavailable and how the log groups can be made available.
ORA-16836: one or more system data files are missing
Cause: The broker detected that one or more system data files were missing.
Action: Use Data Repair Advisor to determine which system data files are missing
and how the files can be restored.
ORA-16837: one or more system data files are corrupt
Cause: The broker detected that one or more system data files were corrupt.
Action: Use Data Repair Advisor to determine which system data files are corrupt
and how the files can be restored.
ORA-16838: one or more system data files are offline
Cause: The broker detected that one or more system data files were offline.
Action: Use Data Repair Advisor to determine which system data files are offline and
how the files can be made online.
ORA-12700 to ORA-19400 69-273
ORA-16839: one or more user data files are missing

Cause: The broker detected that one or more user data files were missing.
Action: Use Data Repair Advisor to determine which user data files are missing and
how the files can be restored.
ORA-16840: one or more user data files are corrupt
Cause: The broker detected that one or more user data files were corrupt.
Action: Use Data Repair Advisor to determine which user data files are corrupt and
how the files can be restored.
ORA-16841: one or more user data files are offline
Cause: The broker detected that one or more user data files were offline.
Action: Use Data Repair Advisor to determine which user data files are offline and
how the files can be made online.
ORA-16842: block corruptions detected
Cause: The broker detected block corruptions on this database.
Action: Use Data Repair Advisor to determine which files are affected by block
corruptions and how the files can be repaired.
ORA-16843: errors discovered in diagnostic repository
Cause: The broker detected one or more errors in the Automatic Diagnostic
Repository.
Action: Use Data Repair Advisor to see the errors that were discovered and how they
can be repaired.
ORA-16844: redo transport mode incompatible with RedoSource property value
Cause: The standby database could not be set to receive redo data from another
standby database or a far sync instance because the standby database LogXptMode
property was not set to ASYNC.
Action: Set the standby database LogXptMode property to ASYNC before setting its
RedoSource property to a non-empty value. Or, set the standby database RedoSource
property to the empty value before setting its LogXptMode property to a value other
than ASYNC.
ORA-16845: database specified by RedoSource property is disabled
Cause: An attempt was made to either set a database RedoSource property to the
name of a database that was disabled or to enable a database whose RedoSource
property was set to the name of a database that was disabled.
Action: Enable the database specified by the RedoSource property and retry the
command.
ORA-16846: too many cascading levels
Cause: The value of the RedoSource property was not set to the name of either a far
sync instance or a database that receives redo data directly from the primary
database.
Action: Set the RedoSource property to either a far sync instance or a database that
receives redo data directly from the primary database.
ORA-16847: a previous switchover from this database failed with error string
Cause: A previous switchover operation from this database failed.
Action: Fix the underlying problem and reissue the switchover command again.
ORA-16848: a previous switchover to this database failed with error string
Cause: A previous switchover operation to this database failed.
ORA-16849: a previous switchover from this database was interrupted and aborted
Cause: A previous switchover operation from this database was interrupted by the
user. It may be caused by a hang.
ORA-16850: a previous switchover to this database was interrupted and aborted
Cause: A previous switchover operation to this database was interrupted by the user.
It may be caused by a hang.
ORA-16851: a previous failover to this database failed with error string
Cause: A previous failover operation to this database failed.
Action: Fix the underlying problem and reissue the failover command again.
ORA-16852: a previous failover to this database was interrupted and aborted
Cause: A previous failover operation to this database was interrupted by the user. It
may be caused by a hang.
Action: Fix the underlying problem and reissue the failover command again.
ORA-16853: apply lag has exceeded specified threshold
Cause: The current apply lag exceeded the value specified by the
'ApplyLagThreshold' database property. It may be caused either by a large transport
lag or poor performance of apply services on the standby database.
Action: Check for gaps on the standby database. If no gap is present, tune the apply
services.
ORA-16854: apply lag could not be determined
Cause: Apply lag could not be determined because either apply services were not
running or there was no connectivity between the redo source and standby database.
Action: Start apply services if they are not running. Also, ensure that there is network
connectivity between the redo source and standby databases, and the redo source is
sending redo data to the standby.
ORA-16855: transport lag has exceeded specified threshold
Cause: The current transport lag exceeded the value specified by the
'TransportLagThreshold' database property. It is caused by either poor network
performance between the redo source and the standby databases or a network
disconnection.
Action: Check the network connection between the redo source and standby
databases. If they are connected, check the network performance between the redo
source and the standby databases and tune it if necessary.
ORA-16856: transport lag could not be determined
Cause: Transport lag could not be determined because there was no connectivity
between the redo source and standby databases.
ORA-12700 to ORA-19400 69-275
Action: Ensure that there is network connectivity between the redo source and
standby databases, and the redo source is working properly.
ORA-16857: standby disconnected from redo source for longer than specified
threshold
Cause: The amount of time the standby was disconnected from the redo source
database exceeded the value specified by the 'TransportDisconnectedThreshold'
database property. It is caused by no network connectivity between the redo source
and the standby databases.
ORA-16858: last communication time from redo source could not be determined
Cause: The standby database had never been contacted by the redo source.
ORA-16859: request terminated because delete, disable, or failover operation is in
progress
Cause: The broker terminated a request because it was processing a delete, disable, or
failover operation.
Action: Wait for the operation to complete and then retry the request.
ORA-16860: invalid member specified as the fast-start failover target
Cause: The member specified as the fast-start failover target was either a far sync
instance or snapshot standby database, or does not exist in the configuration.
Action: Only a physical or logical standby database can be specified as a fast-start
failover target. Check the database name and retry the command.
ORA-16861: ExternalDestination property requires DB_UNIQUE_NAME attribute
Cause: The value specified for the ExternalDestination property did not contain the
DB_UNIQUE_NAME attribute.
Action: Ensure that DB_UNIQUE_NAME is specified as the value for the
ExternalDestination property.
ORA-16862: unsupported attribute specified for the ExternalDestination property
Cause: The value specified for the ExternalDestination property contained
unsupported attributes.
Action: Ensure that the value specified for the ExternalDestination property does not
contain any of these attributes: LOCATION, ALTERNATE, MAX_FAILURE, SYNC,
TEMPLATE, MANDATORY, DELAY, NET_TIMEOUT, and VALID_FOR.
ORA-16863: A member whose MaxFailure property is set to zero cannot have an
alternate destination.
Cause: A member was specified to have an alternate destination when its MaxFailure
configurable property was set to zero.
Action: Set the member's MaxFailure property to a nonzero value and retry the
command.
ORA-16864: The MaxFailure property cannot be set to zero for a member that has
an alternate destination.
Cause: An attempt was made to set the MaxFailure configurable property to zero
when it had an alternate destination specified.
Action: Set the member's MaxFailure configurable property to a nonzero value.
ORA-16865: database is closing or is not mounted on the instance
Cause: Broker health check was unable to complete because the database was closing
or was not mounted on the instance.
Action: No action is required if the database is closing. Mount the database if it is not
yet mounted on the instance.
ORA-16900: change of LogXptMode or RedoRoutes property violates overall
protection mode
Cause: The broker did not allow the attempt to change the LogXptMode or
RedoRoutes configurable property for the standby database or far sync instance
because, if allowed, the overall protection mode for the configuration would have
been violated.
Action: If the LogXptMode or RedoRoutes configuration property must be changed
for the specified standby database or far sync instance, first downgrade the overall
protection mode for the broker configuration. After that operation has completed, the
LogXptMode or RedoRoutes configuration property for the standby database can be
changed.
ORA-16901: inconsistent alternate destinations specified with RedoRoutes
Cause: The specification of alternates for the RedoRoutes property for a member was
set inconsistently with respect to another member's RedoRoutes property.
reissue the command. Ensure that the member's RedoRoutes alternate setting is set
consistently with other member's RedoRoutes property.
ORA-16950: Remote mapped cursors are not supported by this feature.
Cause: This cursor is a remote mapped cursor which could not be processed locally.
Action: Try to process this statement directly on the remote site.
ORA-16951: Too many bind variables supplied for this SQL statement.
Cause: Binding this SQL statement failed because too many bind variables were
supplied.
Action: Pass the correct number of bind variables.
ORA-16952: Failed to bind this SQL statement.
Cause: Binding this SQL statement failed.
Action: Check if bind variables for that statement are properly specified.
ORA-16953: Type of SQL statement not supported.
Cause: This type of SQL statement could not be processed.
Action: n/a
ORA-16954: SQL parse error.
Cause: The specified SQL statement failed to be parsed.
Action: Check if syntax is correct and ensure that this statement can be parsed by the
specified user name.
ORA-12700 to ORA-19400 69-277
ORA-16955: Unknown error during SQL analyze.

Cause: The specified SQL statement failed to be analyzed.
Action: This is an internal error, please contact Oracle support.
ORA-16956: Only SELECT or DML statements are supported for test execute.
Cause: The specified SQL statement cannot be tested for execute.
Action: n/a
ORA-16957: SQL Analyze time limit interrupt
Cause: This is an internal error code used indicate that SQL analyze has reached its
time limit.
Action: n/a
ORA-16958: DML statements running parallel are not supported for test execute.
Cause: The specified DML statement cannot be tested for execute because part of it is
running parallel.
Action: n/a
ORA-16959: Statement type has been disabled for SQL Analyze
Cause: The system attempted to analyze a type of statement that was disabled by the
current feature.
Action: Try a different feature capable of analyzing this statement type.
ORA-16960: SQL Analyze could not reproduce the desired plan.
Cause: SQL Analyze failed to reproduce a particular plan using an outline.
Action: Check the outline data.
ORA-16961: SQL statement with SQL patch is ignored
Cause: SQL statements with SQL patches are not supported by SQL tuning advisor.
Action: Check the SQL patch information. Rerun SQL repair advisor on that SQL
statement for a potential better SQL patch.
ORA-16962: SQL statement attempted to begin an autonomous transaction
Cause: The SQL statement being analyzed attempted to begin an autonomous
transaction, which is not supported.
Action: Analyze another statement or remove the autonomous transaction from the
current statement.
ORA-16963: The given user or schema is not supported by this feature.
Cause: The SQL statement being analyzed had a parsing user or schema which is not
currently supported for SQL Analyze.
Action: Analyze another statement.
ORA-17500: ODM err:string
Cause: An error returned by ODM library
Action: Look at error message and take appropriate action or contact Oracle Support
Services for further assistance
ORA-17501: logical block size string is invalid
Cause: logical block size for oracle files must be a multiple of the physical block size,
and less than the maximum
Action: check INIT.ORA file parameters

ORA-17502: ksfdcre:string Failed to create file string
Cause: file creation failed due to either insufficient OS permission or the file already
exists
Action: check additional error messages
ORA-17503: ksfdopn:string Failed to open file string
Cause: file open failed due to either insufficient OS permission or the name of file
exceeds maximum file name length.
ORA-17504: ksfddel:Failed to delete file string
Cause: The file that was being deleted is still in use or the process has insufficient
permission to delete file.
ORA-17505: ksfdrsz:string Failed to resize file to size string blocks
Cause: There is insufficient space left on the device or the process has insufficient
permission to resize file.
ORA-17506: I/O Error Simulation
Cause: The i/o request is marked with error because the i/o error simulation event is
turned on.
Action: n/a
ORA-17507: I/O request size string is not a multiple of logical block size
Cause: i/o's are done in multiple of logical block size
Action: Check additional error messages
ORA-17508: I/O request buffer ptr is not alligned
Cause: i/o request buffer should be alligned, check additional information for buffer
ptr value
Action: Call Oracle Support Services
ORA-17509: Attempt to do i/o beyond block1 offset
Cause: When a file is identified with logical block size of 0, only i/o's to block1 is
allowed.
Action: check additional error messages and call Oracle Support Services
ORA-17510: Attempt to do i/o beyond file size
Cause: The i/o request points to a block beyond End Of File
Action: check additional error messages and call Oracle Support Services
ORA-17512: Block Verification Failed
Cause: Block Verification after a read operation on a database file failed since the
block is media corrupt.
Action: check additional error messages in the trace file and call Oracle Support
Services
ORA-12700 to ORA-19400 69-279
ORA-17513: dNFS package call failed

Cause: An attempt was made to call a dNFS package in a non-dNFS environment
Action: Make sure dNFS is enabled and the file can be accessed using dNFS.
ORA-17514: Access to clonedb bitmap file failed
Cause: Accessing the bitmap block file in clonedb environment has encountered an
error
Action: check additional error messages in the trace file and call Oracle Support
Services
ORA-17515: Creation of clonedb failed using snapshot file string
Cause: Creating a datafile in a clonedb environment failed.
Action: Make sure the snapshot file passed to clonedb is not from another clonedb
instance and call Oracle Support Services for further assistance
ORA-17516: dNFS asynchronous I/O failure
Cause: The asynchronous I/O request failed due to storage server reboot.
Action: Make sure the storage server does not reboot repeatedly during database
operations.
ORA-17517: Database cloning using storage snapshot failed on file string:string
Cause: An invocation of the storage clone command was returned with an error.
Action: Make sure all necessary steps are performed for storage cloning and check the
Oracle trace file for additional information.
ORA-17518: backup file string cannot be found
Cause: Access to the specified backup file was required for Instant Restore.
Action: Make sure the path and file name are correct for the backup file and the path
to the backup file can be accessed from the node of the instance.
ORA-17519: Reason(string): data file string cannot be prepared
Cause: The snapshot layer could not prepare the specified data file.
Action: Make sure the file does not already exist, is already part of a clone setup, or is
being repopulated by an Instant Restore background process. Make sure the path
specified is accessable and writable by the instance.
ORA-17520: data file string cannot be added to repopulation
Cause: Instant Restore could not add the file to the repopulation work queue.
Action: The repopulation process may be working on too many files for the system.
Try waiting for some files to complete and try again.
ORA-17521: Instant Restore is not enabled
Cause: The initialization parameters for Instant Restore were not set.
Action: Make sure Instant Restore initialization parameter is set as required for this
feature.
ORA-17522: file string is already being repopulated
Cause: The file is currently being repopulated from a previous restore.
Action: Make sure the file compeletes restore before you start another restore.
ORA-17523: Instance number cannot spawn repopulation (RPOP) process

Cause: Instance may have too many running processes.
Action: Make sure maxmimum number of processes initialization parameter is set
properly for this feature.
ORA-17524: Repopulation cannot take place - no RPOP processes
Cause: Maxmimum processes initialization parameter may not be set properly.
Action: Make sure maxmimum number of processes initialization parameter is set
properly for this feature. check alert log for other related errors.
ORA-17525: Database clone using storage snapshot not supported on file string
Cause: Cloning a database using storage level snapshot is not supported on the
underlying storage.
Action: Use storage product that has snapshot based cloning support for Oracle.
ORA-17526: Block size of file string is too small string. Must be >= string.
Cause: Files with block sizes smaller than a minimum size cannot be used for clones
backed by snapshot file.
Action: Use files with larger block size.
ORA-17527: Creation of a snapshot failed because the destination string was not a
sparse disk group.
Cause: Creating a snapshot failed because the destination disk group was not sparse.
Action: Make sure the 'create_file_dest' clause passed to the snapshot copy is in a
sparse disk group.
ORA-17528: cannot write to file string opened for read
Cause: The file is read-only or was opened read-only and an attempt was made to
write to the file, or there was an internal error.
Action: If the file is a parent of a napshot, then you cannot open read/write, drop or
unplug the database. Otherwise, look at trace file and contact Oracle Support
Services.
ORA-17610: file 'string' does not exist and no size specified
Cause: An attempt to create a file found neither an existing file nor a size for creating
the file.
Action: Specify a size for the file.
ORA-17611: ksfd: file 'string' cannot be accessed, global open closed
Cause: An attempt to write to a file which has gone offline/unidentified
Action: Check for other errno in the stack
ORA-17612: Failed to discover Oracle Disk Manager library, return value string
Cause: Discovery of the odm library by calling odm_discover() failed
Action: Contact your storage vendor who has provided the ODM library or call
Oracle Support
ORA-17613: Failed to initialize Oracle Disk Manager library: string
Cause: ODM initialization for the thread failed due to insufficient previlige or
memory.
ORA-12700 to ORA-19400 69-281
Action: Make sure there is enough system resources available for the oracle process
and it has access to the ODM library
ORA-17618: Unable to update block 0 to version 10 format
Cause: An attempt was made to update block 0 to version 10 format.
Action: Check additional error messages and call Oracle Support Services
ORA-17619: max number of processes using I/O slaves in a instance reached
Cause: An attempt was made to start large number of processes requiring I/O slaves.
Action: There can be a maximum of 35 processes that can have I/O slaves at any
given time in a instance.
ORA-17620: failed to register the network adapter with Oracle Disk Manager
library: string
Cause: The ODM library returned an error while trying to register the network
adapter.
Action: Make sure the network adapter name given in the fileio_network_adapters is
a valid name, and that the Oracle user has the correct access privileges.
ORA-17621: failed to register the memory with Oracle Disk Manager library
Cause: The ODM library returned an error while trying to register the memory.
Action: Contact the Oracle Disk Manager Library provider.
ORA-17622: failed to deregister the memory with Oracle Disk Manager library
Cause: The ODM library returned an error while trying to deregister the memory.
Action: Contact the Oracle Disk Manager Library provider
ORA-17624: Failed to delete directory string
Cause: The directory that was being deleted is still in use or the process had
insufficient permission to delete the directory.
Action: check additional error messages.
ORA-17626: ksfdcre: string file exists
Cause: trying to create a database file, but file by that name already exists
Action: verify that name is correct, specify REUSE if necessary
ORA-17627: string
Cause: An error returned by OCI while sending/receiving message from remote
instance
Action: Look at error message and take appropriate action or contact Oracle Support
Services for further assistance
ORA-17628: Oracle error string returned by remote Oracle server
Cause: Oracle server on the remote instance has returned an error.
Action: Look at remote instance alert log/trace file for more information and take
appropriate action or contact Oracle Support Services for further assistance
ORA-17629: Cannot connect to the remote database server
Cause: Connecting to the remote server specified by database connect string for
netowrk file transfer failed.
ORA-17630: Mismatch in the remote file protocol version client string server string
Cause: Cannot communicate with the remote database server as there is a mismatch
in the Oracle file protocol version.
ORA-17631: dbname 'string' specified by remote server does not match the instance
name 'string'
Cause: The dbname specified by the remote server is not intended for this instance.
Action: Check the dbname specified in the command of the remote instance and look
for further error messages.
ORA-17632: file 'string' is a formatted ASM disk
Cause: An attempt to create a datafile on a device that was formatted for ASM disk
failed.
Action: Check that the device specified is not an ASM disk. If you would like to use
the disk for datafiles, please clear the disk before you retry the operation.
ORA-17633: Operation not supported as one of the servers involved is not capable
of performing the requested operation
Cause: An attempt was made to perform an operation involving two Oracle servers
where both servers did not have the capability required for carrying out the
operation. It is likely that one of the servers needs a patch or an upgrade to
successfully participate in the operation.
Action: Apply the required fix or update on the lower version server. Contact Oracle
Support Services for further assistance.
ORA-17634: network file transfer operation aborted
Cause: An error occurred during network file transfer operation.
Action: Check addtional error messages.
ORA-17635: failure in obtaining physical sector size for 'string'
Cause: An error occurred while determining the physical sector size from the
underlying storage (ASM/ODM/OSD).
ORA-17636: Invalid sparse block format (string). Start block=string. Error=string.
File=string
Cause: An error occurred while reading the block on sparse media.
ORA-17676: Failed to mount 'string' with error:'string'
Cause: Mounting database file system failed with an error.
Action: Check additional error messages in the trace file.
ORA-17677: failed to unmount 'string' with error:'string'
Cause: Unmounting database file system failed with an error.
Action: Check additional error messages in the trace file.
ORA-18000: invalid outline name
Cause: The parser detected a missing or invalid outline name
Action: n/a
ORA-12700 to ORA-19400 69-283
ORA-18001: no options specified for ALTER OUTLINE

Cause: The parser detected that no clause was specified on the command Our
performance tests, which are not typical as they exercise all branches of the code, have
shown approximately a 30% performance increase line for ALTER OUTLINE.
Action: Re-issue the command, specifying a valid ALTER OUTLINE clause.
ORA-18002: the specified outline does not exist
Cause: Either the outline did not exist to begin with, or a timing window allowed for
another thread to drop or alter the outline midstream.
Action: n/a
ORA-18003: an outline already exists with this signature
Cause: The signature generation algorithm generates signatures that are are 16 bytes
in length so it is highly unlikely that any 2 signatures will be identical. This message
is raised in such a rare case.
Action: Either re-issue the statement that led to the outline being created with some
whitespace added or force the outline to be created in a different category.
ORA-18004: outline already exists
Cause: An outline already exists, either with the specified name, or for the specified
SQL text.
Action: n/a
ORA-18005: CREATE ANY OUTLINE privilege is required for this operation
ORA-18006: DROP ANY OUTLINE privilege is required for this operation
ORA-18007: ALTER ANY OUTLINE privilege is required for this operation
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 outline system tables do not exist
Cause: Either the database creation script that creates these tables was not executed or
a user accidently deleted the table
Action: Review the log files to see what happened when the database was created.
ORA-18010: command missing mandatory CATEGORY keyword
Cause: User failed to specify the CATEGORY keyword
Action: Re-issue the command with the CATEGORY keyword included
ORA-18011: the outline specified in the FROM clause does not exist
ORA-18012: select_catalog_role role is required for this operation
ORA-18013: timed out while waiting for resource string
ORA-18014: deadlock detected while waiting for resource string
ORA-18015: invalid source outline signature

Cause: User imported an 8i outline into a 9i database without updating signatures
Action: execute dbms_outln.update_signatures
ORA-18100: XUST0001 - Updating expression in a wrong position
Cause: An updating expression was used in a position other than one of the
following: - The topmost expression in the body of a query. - The MODIFY clause of a
TRANSFORM expression. - The RETURN clause of a FLWOR expression. - The
RETURN clauses of a TYPESWITCH expression in which every RETURN clause
contains an updating expression, an empty expression ( ), or a call to the fn:error
function. - The THEN and ELSE clauses of a conditional statement in which both the
then and else clauses contain either an updating expression, an empty expression ( ),
or a call to the fn:error function. - An operand of a comma expression in which each
operand is either an updating expression, an empty expression ( ), or a call to the
fn:error function. - The content of a parenthesized expression. - The body of a function
declaration in which the keyword UPDATING is specified.
Action: None
ORA-18101: XUST0002 - Non-updating expression in a wrong position
Cause: A non-updating expression other than an empty expression ( ) or a call to the
fn:error function was used in one of the following positions: - The MODIFY clause of
a TRANSFORM expression. - The top-level expression in the body of a function
declaration in which the keyword UPDATING is specified.
Action: None
ORA-18102: XUST0003 - Repeated revalidation declaration
Cause: Prolog contained more than one revalidation declaration.
Action: None
ORA-18103: XUTY0004 - Invalid attribute node in the insertion sequence
Cause: The insertion sequence of an INSERT expression contained an attribute
following a node that was not an attribute node.
Action: None
ORA-18104: XUTY0005 - Invalid target expression for INSERT
Cause: In an INSERT expression where INTO, AS FIRST INTO, or AS LAST INTO
was specified, the target expression returned a nonempty result that did not consist of
a single element or document node.
Action: None
ORA-18105: XUTY0006 - Invalid target expression for INSERT
Cause: In an INSERT expression where BEFORE or AFTER was specified, the target
expression returned a nonempty result that did not consist element, text, comment, or
processing instruction node.
Action: None
ORA-18106: XUTY0007 - Invalid target expression for DELETE
Cause: The target expression of a DELETE expression did not return a sequence of
zero or more nodes.
Action: None
ORA-12700 to ORA-19400 69-285
ORA-18107: XUTY0008 - Invalid target expression for REPLACE

Cause: In a REPLACE expression, the target expression returned a nonempty result
that did not consist of a single element, attribute, text,
Action: None
ORA-18108: XUDY0009 - Invalid target expression for REPLACE
Cause: In a REPLACE expression where VALUE OF was not specified, the node
returned by the target expression did not have a parent.
Action: None
ORA-18109: XUTY0010 - Invalid replacement sequence for REPLACE
Cause: In a REPLACE expression where VALUE OF was not specified and the target
was an element, text, comment, or processing instruction node, the replacement
sequence did not consist of zero or more element, text, comment, or processing
instruction nodes.
Action: None
ORA-18110: XUTY0011 - Invalid replacement sequence for REPLACE
Cause: In a REPLACE expression where VALUE OF was not specified and the target
is an attribute node, the replacement sequence did not consist of zero or more
attribute nodes.
Action: None
ORA-18111: XUTY0012 - Invalid target expression for RENAME
Cause: In a RENAME expression, the target expression returned a nonempty result
that did not consist of a single element, attribute, or processing instruction node.
Action: None
ORA-18112: XUTY0013 - Invalid COPY expression for TRANSFORM
Cause: In a TRANSFORM expression, a source expression in the copy clause did not
return a single node.
Action: None
ORA-18113: XUDY0014 - Modified node was not created by the COPY clause
Cause: In a TRANSFORM expression, the MODIFY clause modified a node that was
not created by the COPY clause.
Action: None
ORA-18114: XUDY0015 - Duplicate RENAME for the same target node
Cause: A node was the target of more than one RENAME expression within the same
query.
Action: None
ORA-18115: XUDY0016 - Duplicate REPLACE for the same target node
Cause: A node was the target of more than one REPLACE expression (without
VALUE OF being specified) within the same query.
Action: None
ORA-18116: XUDY0017 - Duplicate REPLACE for the same target node
Cause: A node was the target of more than one REPLACE VALUE OF expression
within the same query.
Action: None
ORA-18117: XUDY0018 - External not updating function returns an updated value
Cause: A function that was declared to be external but not updating returned a
nonempty pending update list.
Action: None
ORA-18118: XUDY0019 - External updating function returns an invalid value
Cause: A function that was declared to be both external and updating returned a
nonempty data model instance.
Action: None
ORA-18119: XUDY0020 - Deleted node has no parent
Cause: Node was deleted that had no parent before execution of the query began.
Action: None
ORA-18120: XUDY0021 - The result XDM instance violates XDM constraints
Cause: XDM instance resulting from applying all the updates in a query violated
constraint specified in [XQuery/XPath Data Model (XDM)]. In this case, none of the
updates in the query were made effective.
Action: None
ORA-18121: XUTY0022 - Invalid attribute insertion into a document node
Cause: INSERT expression specified the insertion of an attribute node into a
document node.
Action: None
ORA-18122: XUDY0023 - Updating expression introduces a namespace conflict
Cause: An INSERT, REPLACE, or RENAME expression affected an element node by
introducing a new namespace binding that conflicted with one of its existing
namespace bindings.
Action: None
ORA-18123: XUDY0024 - Updating expression introduces a namespace conflict
Cause: Effect of a set of updating expressions introduced conflicting namespace
bindings into an element node.
Action: None
ORA-18124: XUDY0025 - Invalid QName for processing instruction RENAME
Cause: Target of a RENAME expression was a processing instruction node, and the
new name expression returned a QName with a nonempty namespace prefix.
Action: None
ORA-18125: XUST0026 Revalidation mode string is not supported
Cause: Revalidation declaration in a Prolog specified a revalidation mode that is not
supported by the current implementation.
Action: None
ORA-18126: XUDY0027 - Invalid target expression
Cause: Target expression of an INSERT, REPLACE, or RENAME expression
evaluated to an empty sequence.
Action: None
ORA-12700 to ORA-19400 69-287
ORA-18127: XUST0028 - Updating function should not have a return type

Cause: Function declaration specified both UPDATING and a return type.
Action: None
ORA-18128: XUDY0029 - INSERT expression target node doesn't have a parent
Cause: In an INSERT expression where BEFORE or AFTER was specified, a node
returned by the target expression did not have a parent.
Action: None
ORA-18129: XUDY0030 - Invalid insertion of an attribute node
Cause: INSERT expression specified the insertion of an attribute node before or after a
child of a document node.
Action: None
ORA-18130: FOUP0001 - Invalid 'fn:put' first operand
Cause: The first operand of fn:put was not a node of a supported kind.
Action: None
ORA-18131: FOUP0002 - Invalid 'fn:put' second operand
Cause: The second operand of fn:put was not a valid lexical representation of the
xs:anyURI type.
Action: None
ORA-18150: SQL input value cannot be modified in updating expression
Cause: Updating expression was specified as top-level XMLQuery expression.
Action: Use XQuery TRANSFORM expression to copy input value and modify it.
ORA-18160: FTST0001 - FTMildNot operator not supported
Cause: An attempt was made to use the mild not option when the FTMildNot
operator was not supported. An implementation that does not support the
FTMildNot operator must raise a static error if a full-text query contains a mild not.
Action: Do not use the FTMildNot full-text query operator.
ORA-18161: FTST0002 - FTUnaryNot operator not supported
Cause: An implementation that enforces one of the restrictions on FTUnaryNot must
raise a static error if a full-text query does not obey the restriction.
Action: Do not use the FTUnaryNot full-text query operator.
ORA-18162: FTST0003 - FTUnit and FTBigUnit not supported
Cause: An implementation that does not support one or more of the choices on
FTUnit and FTBigUnit must raise a static error if a full-text query contains one of
those choices.
Action: Do not use the FTUnit or FTBigUnit option.
ORA-18163: FTST0004 - FTScope not supported
Cause: An implementation that does not support the FTScope operator must raise a
static error if a full-text query contains a scope.
Action: Do not use the FTScope full-text query operator.
ORA-18164: FTST0005 FTTimes not supported

Cause: An implementation that does not support the FTTimes operator must raise a
static error if a full-text query contains a times.
Action: Do not use the FTTimes full-text query operator.
ORA-18165: FTST0006 FTStopwordOption not supported
Cause: An implementation that restricts the use of FTStopwordOption must raise a
static error if a full-text query contains a stop word option that does not meet the
restriction.
Action: Do not use the FTStopwordOption full-text query operator.
ORA-18166: FTST0007 FTIgnoreOption not supported
Cause: An implementation that restricts the use of FTIgnoreOption must raise a static
error if a full-text query contains an ignore option that does not meet the restriction.
Action: Do not use the FTIgnoreOption full-text query operator.
ORA-18167: FTST0008 stop word list not found
Cause: It is a static error if, during the static analysis phase, the query is found to
contain a stop word option that refers to a stop word list that is not found in the
statically known stop word lists.
Action: Please make sure the stop word list exist.
ORA-18168: FTST0009 language option not supported
Cause: It may be a static error if, during the static analysis phase, the query is found
to contain a language identifier in a language option that the implementation does not
support. The implementation may choose not to raise this error and instead provide
some other implementation-defined behavior.
Action: Do not use the language full-text query option.
ORA-18169: FTST0010 FTOrder not succeeding FTWindow or FTDistance operator
Cause: It is a static error if, during the static analysis phase, an expression is found to
use an FTOrder operator that does not appear directly succeeding an FTWindow or
an FTDistance operator and the implementation enforces this restriction.
Action: Do not use the FTOrder succeeding FTWindow or FTDistance full-text query
operator.
ORA-18170: FTST0011 FTWindow and FTDistance restriction
Cause: An implementation may restrict the use of FTWindow and FTDistance to an
FTOr that is either a single FTWords or a combination of FTWords involving only the
operators && and ||. If it a static error if, during the static analysis phase, an
expression is found that violates this restriction and the implementation enforces this
restriction.
Action: Follow FTWindow and FTDistance restriction.
ORA-18171: FTST0012 FTContent not supported
Cause: An implementation that does not support the FTContent operator must raise a
static error if a full-text query contains one.
Action: Do not use FTContent full-text query operator.
ORA-12700 to ORA-19400 69-289
ORA-18172: FTST0013 more than one language encountered

Cause: It is a static error if, during the static analysis phase, an implementation that
restricts the use of FTLanguageOption to a single language, encounters more than one
distinct language option.
Action: Do not use more than one language in FTLanguag full-text option.
ORA-18173: FTST0014 score computation restriction
Cause: An implementation may constrain the form of the expression used to compute
scores. It is a static error if, during the static analysis phase, such an implementation
encounters a scoring expression that does not meet the restriction.
Action: n/a
ORA-18174: FTST0015 FTCaseOption restriction
Cause: It is a static error if, during the static analysis phase, an implementation that
restricts the choices of FTCaseOption encounters the "lowercase" or "uppercase"
option.
Action: n/a
ORA-18175: FTDY0016 weights invalid
Cause: It is a dynamic error if an implementation that does not support negative
weights encounters a weight expression that does not meet the restriction.
Action: Do not use invalid weights value.
ORA-18176: FTDY0017 mild not selection containings StringExclude
Cause: It is a dynamic error if an implementation encounters a mild not selection, one
of whose operands evaluates to an AllMatches that contains a StringExclude
Action: n/a
ORA-18177: XQuery full text expression 'string' cannot be evaluated using XML
full-text index
Cause: There was no XML full-text index to evaluate the XQuery full text expression
filtering XML documents that were stored in an XMLType table or column.
Action: Create an XML full-text index on the XML documents stored in an XMLType
table or column and ensure that the XQuery full text expression can be evaluated by
an XML full-text index.
ORA-18178: XMLType input to XMLTABLE row expression needs to use PASSING
BY REF clause
Cause: The XMLTABLE column expression used the XMLTYPE(SEQUENCE) BY REF
clause which requires XMLType input to the XMLTABLE row expression to use the
PASSING BY REF clause.
Action: Specify the PASSING BY REF clause for XMLType input to the XMLTABLE
row expression.
ORA-18179: XMLTABLE column expression needs to be specified using
XMLTYPE(SEQUENCE) BY REF clause
Cause: Output of the XMLTABLE column expression was passed to an XMLTABLE
row expression with PASSING BY REF clause.
Action: Specify the XMLTABLE column expression using XMLTYPE(SEQUENCE) BY
REF clause.
ORA-18180: wrong argument is passed to XMLTABLE row expression using

PASSING BY REF clause
Cause: An XML document that was not stored in an XMLTYPE table or column was
passed to an XMLTABLE row expression using the PASSING BY REF clause.
Action: Make sure only XML documents that are stored in an xmltype table or
column can be passed in as input to XMLTABLE row expression using the PASSING
BY REF clause
ORA-18181: XQuery full text expression option 'string' is not supported
Cause: An attempt was made to use an XQuery full text expression option that is not
supported.
Action: Avoid using an XQuery full text expression option which is not supported.
ORA-18182: FTST0018 unknown thesaurus is used
Cause: During the static analysis phase, the query was found to contain a thesaurus
option that referred to a thesaurus that was not found in the statically known
thesauri. This is a static error.
Action: Avoid using unknown thesaurus.
ORA-18183: FTST0019 more than one match option of any given match option
group is used within a single FTMatchOptions.
Cause: Within the single FTMatchOptions, there was more than one match option of
any given match option group. This is a static error.
Action: Avoid using more than one match option of any given match option group is
used within a single FTMatchOptions.
ORA-18184: FTDY0020 a query string violates wildcard syntax when wildcards is in
effect
Cause: Because wildcards were in effect, the query string violated wildcard syntax.
This is a dynamic error.
Action: Fix wildcard syntax when wildcards is in effect.
ORA-18185: query is not parsed correctly
Cause: The query string was not parsed correctly.
Action: Check the syntax of the query string.
ORA-19000: missing RELATIONAL keyword
Cause: The keyword RELATIONAL in the work OBJECT RELATIONAL is missing in
the XMLTYPE storage clause specification.
Action: Supply the RELATIONAL keyword in the storage clause
ORA-19001: Invalid storage option specified
Cause: An invalid storage option was specified for the XMLType.
Action: Supply a valid storage option.
ORA-19002: Missing XMLSchema URL
Cause: A XML schema URL must be specified in the storage option.
Action: Specify a URL for the XMLSchema.
ORA-12700 to ORA-19400 69-291
ORA-19003: Missing XML root element name

Cause: A root element in the XMLSchema must be specified if the XML schema is
given.
Action: Specify a root element in the XML schema.
ORA-19004: Duplicate XMLType OBJECT RELATIONAL storage option
Cause: A duplicate storage option for the XMLType column was specified
Action: Specify a single storage option for an XMLType column
ORA-19005: Duplicate XMLType LOB storage option
Cause: A duplicate storage option for the XMLType column was specified
Action: Specify a single storage option for an XMLType column
ORA-19006: XMLType TYPE storage option not appropriate for storage type
Cause: The TYPE option can only be used in case of OBJECT RELATIONAL storage
option
Action: Remove the TYPE option or specify an OBJECT RELATIONAL storage for the
XMLType column
ORA-19007: Schema string does not match expected string.
Cause: The given XML document conformed to a different schema than expected.
Action: Insert/Update only the XML documents that conform to that particular
schema.
ORA-19008: Invalid version of the XMLType
Cause: An invalid version of the XMLType was found.
Action: This is possible due to data corruption or an internal error or running an older
client against a newer version of the database. Make sure that the version of the client
can understand the XMLType in the database.
ORA-19009: Missing XMLSchema keyword
Cause: The XMLSchema keyword is missing
Action: Specify the XMLSchema URL and element name.
ORA-19010: Cannot insert XML fragments
Cause: XML fragments got from extractNode cannot be inserted into the database.
Action: Convert the fragment into a proper XML document before insertion.
ORA-19011: Character string buffer too small
Cause: The string result asked for is too big to return back
Action: Get the result as a lob instead
ORA-19012: Cannot convert XML fragment to the required datatype
Cause: A conversion to a datatype was requested which cannot be performed
Action: The XMLType may contain fragments and other elements which cannot be
converted to the appropriate datatype.
ORA-19013: Cannot create VARRAY columns containing XMLType
Cause: An attempt was made to create a VARRAY column which contains a
XMLType
Action: You cannot store VARRAYs containing XMLTypes in tables. Use nested tables
instead
ORA-19015: Invalid XML tag identifier (string)
Cause: An invalid XML identifer was detected during XML generation
Action: Fix the offending tag to not contain characters or symbols that are not allowed
by the XML specification
ORA-19016: attributes cannot occur after element specifications
Cause: Attributes specified using the "@" identifier can only occur before any other
element definition when creating XML
Action: Change the order of the types so that the attributes occur in the begining
ORA-19017: Attributes can only be simple scalars
Cause: Attribute values can only be simple scalar values
Action: Use only simple datatypes for attribute values
ORA-19018: Invalid character in XML tag 'string'
Cause: A tag name was found to have an invalid XML character during XML
generation.
Action: Rewrite the query so that the generated XML tag, corresponding to a column
name or alias, contains only valid characters.
ORA-19019: Invalid context passed to DBMS_XMLGEN.GETXML
Cause: The value of context passed to GETXML was invalid.
Action: Rewrite the query so that the value of context passed to GETXML is valid.
ORA-19020: invalid dereference of XMLType columns
Cause: An attempt was made to dereference the attributes of an XMLType column
which is not part of a base table
Action: You can only dereference the attributes of a base table XMLType column
ORA-19022: Unoptimized XML construct detected.
Cause: XMLOptimizationCheck is enabled and unrewritten XML construct was
detected. This prevents execution of XML construct.
Action: Make sure that XML construct is being optimized. See trace file for further
information. Disable XMLOptimizationCheck if you want the unoptimized XML
operation to be executed.
ORA-19023: The first argument to UPDATEXML operator has to be an XMLTYPE
Cause: The first argument passed to the update value operator was not an XMLTYPE.
Action: Rewrite the query so that the first argument to the UPDATEXML operator is
XMLTYPE.
ORA-19024: Cursor expression must be named
Cause: The value of context passed to GETXML was invalid.
Action: Rewrite the query so that the value of context passed to GETXML is valid.
ORA-19025: EXTRACTVALUE returns value of only one node
Cause: Given XPath points to more than one node.
Action: Rewrite the query so that exactly one node is returned.
ORA-12700 to ORA-19400 69-293
ORA-19026: EXTRACTVALUE can only retrieve value of leaf node

Cause: Given XPath does not point to a leaf node.
Action: Rewrite the query so that a leaf node is returned.
ORA-19028: Invalid ADT parameter passed to toObject() function
Cause: The object passed as ADT parameter to sys.XMLType.toObject() is not the
same type, or a super-type, of the mapped type.
Action: Pass an object of the correct type to toObject().
ORA-19029: Cannot convert the given XMLType to the required type
Cause: The passed in XMLType could not be convert to the required type
Action: Binary XMLtype instances or other objects cannot be converted to the
required object or collection types.
ORA-19030: Method invalid for non-schema based XML Documents.
Cause: The method can be invoked on only schema based xmltype objects.
Action: Don't invoke the method for non schema based xmltype objects.
ORA-19031: XML element or attribute string does not match any in type
string.string
Cause: The passed in XML tag does not match any in the object type
Action: Pass a valid canonical XML that can map to the given object type
ORA-19032: Expected XML tag string got string
Cause: When converting XML to object, a wrong tag name was present
Action: Pass a valid canonical XML that can map to the given object type
ORA-19033: schema specified in the XML document does not match the schema
parameter
Cause: When creating schema-based XML, the schema specified in the XML
document is different from the schema passed in as the 'schema' parameter.
Action: Change the schema parameter to match the schema specified in the XML
document.
ORA-19034: Type not supported during schema generation
Cause: The object type contained a type that is not supported for schema generation.
Action: Use a different type or do not generate a schema.
ORA-19035: Invalid select item of the query in newContextFromHierarchy()
Cause: The query does not have a number select item followed by an XMLType select
item only.
Action: Make sure the result set of the query used in the newContextFromHierarchy()
must have only two selected items: the first item must be number type and the second
item must be XMLType.
ORA-19036: Invalid query result set in newContextFromHierarchy()
Cause: The result set of the query used in the newContextFromHierarchy() does not
have the same property as the result set generated by a CONNECT BY query.
Action: Make sure the query used in newContextFromHierarchy() is a CONNECT BY
query or the query returns the result set have the same property as the result set
generated by a CONNECT BY query.
ORA-19037: XMLType result can not be a fragment

Cause: The select item of the query in newContextFromHierarchy() is an XML
fragment.
Action: Make sure the select item of the query in newContextFromHierarchy() is NOT
an XML fragment
ORA-19038: Invalid opertions on query context
Cause: SetMaxRows, SetSkipRows, SetRowTagName opertions are applied to a query
context created from newContextFromHierarchy().
Action: SetMaxRows, SetSkipRows, SetRowTagName opertions can not be applied to
a query context created from newContextFromHierarchy().
ORA-19039: Keyword string reserved for future use
Cause: The keyword is reserved for future use as a builtin function.
Action: Change the name mentioned above to a different one.
ORA-19040: Element string does not match expected string.
Cause: The given XML document had a different root element than expected.
Action: Insert/Update only the XML documents that conform to that particular
schema and element.
ORA-19041: Comment data cannot contain two consecutive '-'s
Cause: The given comment string expression has two consecutive '-'s.
Action: Modify comment string to eliminate one or both of the consevutive '-'s.
ORA-19042: Enclosing tag string cannot be xml in any case combination
Cause: The given enclosing tag matched 'xml' in some case combination
Action: Modify the enclosing tag so that it is not xml in any case combination.
ORA-19043: Multiply nested XMLROOT function disallowed
Cause: An XMLROOT function has an operand that is also an XMLROOT function.
Action: Modify the query so that there are no multiply nested XMLROOT functions.
ORA-19044: character length specified for XMLSerialize is too small.
Cause: An XMLSerialize function was called with a type of character type (e.g.
VARCHAR2(27)), and the length specified (27 in the example) was too small.
Action: Modify the query so that the character length specified is larger.
ORA-19045: character set id specified for XMLSerialize not valid
Cause: An XMLSerialize function was called with an invalid value for the caracter set
id.
Action: Modify the query so that the character set id is valid.
ORA-19046: Out-of-line table cannot be shared by two top-level tables (table
'string.string' and the current table being created).
Cause: An attempt was made to share an out-of-line table between two top-level
tables.
Action: Use the existing top-level XML table.
ORA-12700 to ORA-19400 69-295
ORA-19047: Cannot specify storage for individual VARRAYS

Cause: An attempt was made to combine storage specification for a particular
VARRAY with STORE ALL VARRAYS clause.
Action: Either specify storage for individual VARRAYs or use the STORE ALL
VARRAYS clause.
ORA-19048: Cannot specify VARRAY storage in tableProps
Cause: An attempt was made to store all varrays as tables or LOBs in tableProps.
Action: Do not specify varray store as tables or LOBs in tableProps.
ORA-19051: Cannot use fast path insert for this XMLType table
Cause: Error while trying to insert into an XMLType table using fast path insert.
Action: Set event 19049 to disable fast path insert and try again.
ORA-19100: PASSING or RETURNING keyword expected
Cause: The keyword PASSING or RETURNING was missing.
Action: Specify the PASSING or RETURNING keyword.
ORA-19101: CONTENT keyword expected
Cause: The keyword CONTENT was missing.
Action: Specify the CONTENT keyword.
ORA-19102: XQuery string literal expected
Cause: The string literal containing the XQuery expression was missing.
Action: Specify the XQuery expression as a string literal.
ORA-19103: VALUE keyword keyword
Cause: The keyword VALUE was missing.
Action: Specify the VALUE keyword.
ORA-19104: invalid XQueryX: missing attribute string
Cause: The XQueryX expression was not assigned the expected attribute.
Action: Specify a valid XQueryX.
ORA-19105: invalid XQueryX: expected text node - got string
Cause: The XQueryX expression did not contain a text node as expected.
ORA-19106: invalid XQueryX: expected string - got string
Cause: The XQueryX expression did not contain the node as expected.
ORA-19107: invalid XQueryX - unsupported construct - string
Cause: The given XQuery expression contains an unsupported construct.
ORA-19108: WHITESPACE keyword expected
Cause: The keyword WHITESPACE was missing.
Action: Specify the WHITESPACE keyword.
ORA-19109: RETURNING keyword expected

Cause: The keyword RETURNING was missing.
Action: Specify the RETURNING keyword.
ORA-19110: unsupported XQuery expression
Cause: The program specified an XQuery expression that is not supported.
Action: Rewrite the XQuery with a expression that is supported.
ORA-19111: error during evaluation of the XQuery expression
ORA-19112: error raised during evaluation: string
Cause: The error function was called during evaluation of the XQuery expression.
ORA-19113: trace function called during evaluation: string
Cause: The trace function was called during evaluation of the XQuery expression.
Action: Check the log file for the trace message.
ORA-19114: XPST0003 - error during parsing the XQuery expression: string
Cause: An error occurred during the parsing of the XQuery expression.
ORA-19115: too many context items specified
Cause: More than one context item was specified as input to the XMLQuery function.
Action: Specify a single context item for the XMLQuery function.
ORA-19116: too many xmlspace declarations
Cause: The query prolog contained multiple xmlspace declarations.
Action: Remove the duplicate xmlspace declarations.
ORA-19117: XQST0070 - invalid redefinition of predefined namespace prefix
'string'
Cause: The given predefined namespace was being redefined in a namespace
declaration.
Action: Remove the namespace declaration that redefines the predefined namespace
prefix.
ORA-19118: XQST0066 - duplicate default namespace definition - string
Cause: More than one default namespace declaration used the given namespace URI.
Action: Remove the duplicate default namespace definition.
ORA-19121: duplicate attribute definition - string
Cause: More than one attribute with the same name.
Action: Remove the duplicate attribute definition.
ORA-19122: unsupported XQuery declaration
Cause: The program specified an XQuery declaration that is not supported.
Action: Rewrite the XQuery with a declaration that is supported.
ORA-12700 to ORA-19400 69-297
ORA-19123: FORG0003: fn:zero-or-one() called with a sequence containing more

than one item
Cause: sequence with more than one item was passed into fn:zero-or-one() function
Action: correct input argument to fn:zero-or-one() function
ORA-19124: FORG0004: fn:one-or-more() called with a sequence containing no
items
Cause: sequence containing no items was passed into fn:one-or-more() function
Action: correct input argument to fn:one-or-more() function
ORA-19125: FORG0005: fn:exactly-one() called with a sequence containing zero or
more than one item
Cause: sequence containing zero or more than one item was passed into fn:exactlyone() function
Action: correct input argument to fn:exactly-one() function
ORA-19126: XQuery extension expression contains neither a pragma that is
recognized by the implementation nor an expression enclosed in curly braces
Cause: No expression was enclosed in curly braces for the extension expression or the
pragma content was not recognized.
Action: Correct inputs to extension expression.
ORA-19127: XQST0067: XQST0067: A static error is raised if a Prolog contains more
than one construction declaration
ORA-19128: XQST0068: A static error is raised if a Prolog contains more than one
boundary-space declaration
empty order declaration
ORA-19130: XQST0070: A static error is raised if the predefined namespace prefix
xml or xmlns is redeclared by a namespace declaration or namespace declaration
attribute
ORA-19131: XQST0071: A static error is raised if the namespace declaration
attributes of a direct element constructor do not have distinct names
ORA-19132: XQDY0072: It is a dynamic error if the result of the content expression

of a computed comment constructor contains two adjacent hyphens or ends with a
hyphen
ORA-19133: XQST0073: It is a static error if the graph of module imports contains a
cycle (that is, if there exists a sequence of modules M1 ... Mn such that each Mi
imports Mi+1 and Mn imports M1), unless all the modules in the cycle share a
common namespace
ORA-19134: XQDY0074: It is a dynamic error if the value of the name expression in
a computed element constructor cannot be converted to an expanded QName (for
example, because it contains a namespace prefix not found in statically known
namespaces.)
ORA-19135: XQST0075: An implementation that does not support the Validation
Feature must raise a static error if it encounters a validate expression
ORA-19136: XQST0076: It is a static error if a collation subclause in an order by
clause of a FLWOR expression does not identify a collation that is present in
statically known collations
ORA-19137: XQST0079: It is a static error if an extension expression contains
neither a pragma that is recognized by the implementation nor an expression
enclosed in curly braces
ORA-19138: The target type of a cast or castable expression must be an atomic type
that is in the in-scope schema types and is not xs:NOTATION or
xs:anyAtomicType, optionally followed by the occurrence indicator "?"; otherwise a
static error is raised
ORA-19139: XPST0081: It is a static error if a QName used in a query contains a
namespace prefix that cannot be expanded into a namespace URI by using the
statically known namespaces
ORA-19140: XPST0083: It is a static error if the target type of a cast expression or
constructor function is xs:QName or a type derived from xs:QName or
ORA-12700 to ORA-19400 69-299
xs:NOTATION, and the argument of the cast expression or constructor function is

not a string literal
ORA-19141: XQDY0084: It is a dynamic error if the element validated by a validate
statement does not have a top-level element declaration in the in-scope element
declarations, if validation mode is strict
ORA-19142: FONC0001 = FONC0001: undefined context item
ORA-19143: XQTY0086: It is a type error if the typed value of a copied element or
attribute node is namespace-sensitive when construction mode is preserve and
copy-namespaces mode is no-preserve
ORA-19145: XQST0087: It is a static error if the encoding specified in a Version
Declaration does not conform to the definition of EncName specified in [XML 1.0]
ORA-19146: XQST0088: It is a static error if the literal that specifies the target
namespace in a module import or a module declaration is of zero length
ORA-19147: XQST0089: It is a static error if a variable bound in a for clause of a
FLWOR expression, and its associated positional variable, do not have distinct
names (expanded QNames)
ORA-19148: XQST0090: It is a static error if a character reference does not identify a
valid character in the version of XML that is in use
ORA-19149: XQDY0091: An implementation may raise a dynamic error if an xml:id
error, as defined in [XML ID], is encountered during construction of an attribute
named xml:id
ORA-19150: XQDY0092: An implementation may raise a dynamic error if a
constructed attribute named xml:space has a value other than preserve or default
ORA-19151: XQST0093: It is a static error to import a module M1 if there exists a
sequence of modules M1 ... Mi ... M1 such that each module directly depends on
the next module in the sequence (informally, if M1 depends on itself through some
chain of module dependencies.)
ORA-19152: FOCH0001 = FOCH0001: codepoint not valid
ORA-19153: FOCH0002: unsupported collation
ORA-19154: FOCH0003: unsupported normalization form
ORA-19155: FOCH0004: collation does not support collation units
ORA-19156: FODC0001: no context document
ORA-19157: FODC0002: error retrieving resource
ORA-19158: FODC0004: invalid argument to fn:collection()
ORA-19159: FODC0005: invalid argument to fn:doc
ORA-19160: XPST0003 - syntax error: invalid variable name string
Cause: The given XQuery variable does not begin with the '$' sign
Action: Fix the variable name to start with the "$" sign.
ORA-19161: XPTY0004 - XQuery type mismatch: invalid argument type 'string' for
function 'string'
Cause: The type of the argument that was passed to the given function was not valid.
Action: Fix the argument to be of a type supported by the given function.
ORA-12700 to ORA-19400 69-301
ORA-19162: XPTY0004 - XQuery type mismatch: invalid argument types 'string',

'string' for function 'string'
Cause: The type of the arguments that were passed to the given function was not
valid.
Action: Fix the arguments to be of a type appropriate for the given function.
ORA-19163: XPTY0004 - XQuery type mismatch: argument type mismatch: expected
- 'string' got - 'string' for function 'string'
Cause: The type of the arguments that were passed to the given function was not
valid.
Action: Fix the arguments to be of a type appropriate for the given function.
ORA-19164: XQST0085 - It is a static error if the namespace URI in a namespace
declaration attribute is a zero-length string, and the implementation does not
support [XML Names 1.1].
Cause: There was a zero-length URI in namespace declaration.
Action: Fix the namespace declaration.
ORA-19165: FONS0003: no prefix defined for namespace
ORA-19166: FONS0003: FONS0004: no namespace found for prefix
ORA-19167: FONS0005: base uri not defined in the static context
ORA-19168: FORG0002: invalid argument to fn:resolve-uri()
ORA-19169: FORG0006: invalid argument type in 'string'
ORA-19171: FORG0007: invalid argument to aggregate function
ORA-19172: FORG0008: both arguments to fn:dateTime have a specified timezone
ORA-19173: FORG0009: error in resolving a relative URI against a base URI in
fn:resolve-uri
ORA-19174: FORX0001: invalid regular expression flags

ORA-19175: FORX0002: invalid regular expression
ORA-19176: FORX0003: regular expression matches zero-length string
ORA-19177: FORX0004: invalid replacement string
ORA-19178: FOTY0001: type error
ORA-19179: FOTY0011: Type error. Context item is not a node
ORA-19180: FOTY0012: argument node does not have a typed value
ORA-19181: FOTY0014: type exception
ORA-19182: FORT0001: invalid number of parameters
ORA-19183: FOTY0002: type definition not found
ORA-19184: FOTY0021: invalid node type
ORA-19185: FOAR0002: numeric operation overflow/unflow
ORA-19186: FOCA0001: input value too large for decimal
ORA-12700 to ORA-19400 69-303
ORA-19187: FOCA0002: invalid lexical value
ORA-19188: FOCA0003: input value too large for integer
ORA-19189: FOCA0005: NaN supplied as float/double value
ORA-19190: FOER0000: Unidentified error
ORA-19191: FOAR0001: division by zero
ORA-19192: XQST0047: It is a static error if multiple module imports in the same
Prolog specify the same target namespace
ORA-19193: XQST0045: It is a static error if the function name in a function
declaration is in one of the following namespaces: http://www.w3.org/XML/1998/
namespace, http://www.w3.org/2001/XMLSchema, http://www.w3.org/2001/
XMLSchema-instance, http://www.w3.org/2005/04/xpath-functions, http://
www.w3.org/2005/04/xpath-datatypes
ORA-19194: XQDY0026: It is a dynamic error if the result of the content expression
of a computed processing instruction constructor contains the string "?>"
ORA-19195: Invalid policy in ora:contains
Cause: An invalid policy was specified in ora:contains.
Action: Rename the policy name, policy schema name, or do not specify any policy to
pick up default policy.
ORA-19196: XMLType table or view is not allowed with this form of fn:collection
Cause: The table or view specified in fn:collection was of XMLType.
Action: XMLType table or view is not allowed in the form of fn:collection('oradb:/
schema/table/ROW/column'). It has to be a relational table or view.
ORA-19197: Column not found or invalid column type with this form of
fn:collection
Cause: The column to be retrieved was not found or was not of XMLType.
Action: The column to be retrieved in the form of fn:collection('oradb:/schema/
table/ROW/column') or fn:collection('oradb:/schema/table/ROW[predicate]/
column') has to be of XMLType.
ORA-19198: Column not found or invalid column specified in the predicate with
this form of fn:collection
Cause: The column specified in the predicate was not found or was not allowed.
Action: The column specified in the predicate in the form of fn:collection('oradb:/
schema/table/ROW[predicate]/column') cannot be of XMLType.
ORA-19200: Invalid column specification
Cause: All input arguments must be valid columns
Action: Specify a valid list of columns
ORA-19201: Datatype not supported
Cause: The particular datatype is not supported in the XMLGEN operator
Action: Specify only supported datatypes as arguments to the XMLGEN operator
ORA-19202: Error occurred in XML processingstring
Cause: An error occurred when processing the XML function
ORA-19203: Error occurred in DBMS_XMLGEN processingstring
Cause: An error occurred when processing the DBMS_XMLGEN functions
ORA-19204: Non-scalar value 'string' is marked as XML attribute
Cause: Only scalar values (i.e. values which are not of object or collection type) can be
marked as XML attribute,i.e. is prefixed by '@'. In this case, a non-scalar value was
prefixed with '@'
Action: Remove the '@' sign, or make the value a scalar.
ORA-19205: Attribute 'string' qualifies a non-scalar value in the select list
Cause: The attribute immediately follows a value of object or collection type in the
select list or type definition.
Action: Remove the '@' sign, or make the previous value a scalar.
ORA-19206: Invalid value for query or REF CURSOR parameter
Cause: The queryString argument passed to DBMS_XMLGEN.newContext was not a
valid query, or REF CURSOR.
Action: Rewrite the query so that the queryString argument is a valid query or REF
CURSOR.
ORA-19207: scalar parameter string of XMLELEMENT cannot have an alias.
Cause: The scalar parameter to XMLELEMENT has been qualified with an alias.
Action: Remove the AS clause of the scalar element.
ORA-12700 to ORA-19400 69-305
ORA-19208: parameter string of function string must be aliased

Cause: The indicated parameter of the XML generation function has not been aliased,
although it is an expression.
Action: Specify an alias for the expression using the AS clause.
ORA-19209: invalid or unsupported formatting argument
Cause: An invalid or unsupported formatting argument was supplied
Action: Change the formatting argument to legal supported values
ORA-19210: column 'string', specified to be a key or update column for
DBMS_XMLSTORE, does not not exist in table 'string'
Cause: The column specified using setKeyColumn()/setUpdateColumn() did not exist
in the table.
Action: Change the column specified to be a column in the table
ORA-19211: column 'string', specified as key using
DBMS_XMLSTORE.setKeyColumn() , must be of scalar type
Cause: The column specified using setKeyColumn() was a non-scalar type column.
Action: Change the column specified to be a scalar column in the table
ORA-19212: no key columns specified before call to
DBMS_XMLSTORE.updateXML()
Cause: No columns were specified as key columns before the call to
DBMS_XMLSTORE.updateXML.
Action: Use DBMS_XMLSTORE.setKeyColumn() to specify key columns
ORA-19213: error occurred in XML processing at linesstring
Cause: An error occurred when processing the given lines in an XML function.
Action: Check the given error message and fix the appropriate problem.
ORA-19221: XPST0001 - XQuery static context component string not initialized
Cause: An unitialized static context component was encountered during the static
analysis of the expression.
Action: initialize the given static context.
ORA-19222: XPDY0002 - XQuery dynamic context component string not initialized
Cause: An unitialized dynamic context component was encountered during the
evaluation of the expression.
Action: Initialize the particular dynamic context component.
ORA-19223: XPST0003 - syntax error in XQuery expression
Cause: The given XQuery expression contains syntax errors.
Action: Fix the syntax error in the XQuery expression.
ORA-19224: XPTY0004 - XQuery static type mismatch: expected - string got - string
Cause: The expression could not be used because it's static type is not appropriate for
the context in which it was used.
Action: Fix the expression to be of the required type or add appropriate cast functions
around the expression.
ORA-19225: XPST0005 - XQuery static type error: expected non empty type got
empty sequence
Cause: The static type assigned to an expression other than the () expression must not
be the empty type.
Action: Fix the expression so it does not return empty sequences.
ORA-19226: XPTY0006 - XQuery dynamic type mismatch: expected string got string
Cause: The expression could not be used because it's dynamic type did not match the
required type as specified by XQuery sequencetype matching rules.
Action: Fix the expression to return the expected type or use appropriate cast
functions.
ORA-19227: XPTY0007 - fn:data function is applied to a node (type (string)) whose
type annotation denotes a complex type with non-mixed complex content.
Cause: The input node for atomization contained a type annotation that denoted a
complex type with non-mixed complex content.
Action: Fix the input expression to fn:data to be a node that does not contain nonmixed complex content.
ORA-19228: XPST0008 - undeclared identifier: prefix 'string' local-name 'string'
Cause: The given identifier refers to either a type name, function name, namespace
prefix, or variable name that is not defined in the static context.
Action: Fix the expression to remove the identifier, or declare the appropriate
variable, type, function or namespace.
ORA-19229: XQST0009 - schema import not supported
Cause: A schema import was encountered in the query.
Action: remove the schema import.
ORA-19230: XPST0010 - unsupported axis string
Cause: An unsupported axis was encountered in the given expression.
Action: Remove the unsupported axis from the expression.
ORA-19231: XPST0011 ORA-19232: XQST0012 - imported schemas violate validity rules
Cause: The imported schemas did not satisfy the conditions for schema validity
specified in the XMLSchema specification.
Action: Fix the imported schemas to satisfy the validity rules.In particular, the
definitions must be valid, complete, and unique -- that is, the pool of definitions must
not contain two or more schema components with the same name and target
namespace.
ORA-19233: XQST0013 - invalid pragma
Cause: A pragma was specified whose contents are invalid.
Action: Specify the pragma with the correct contents.
ORA-19234: XQST0014 - invalid or unsupported must-understand extension
Cause: The must-understand extension specified was either invalid or unsupported.
Action: remove the unsupported must-understand extension or fix the error.
ORA-12700 to ORA-19400 69-307
ORA-19235: XQST0015 - unsupported must-understand extension

Cause: The XQuery flagger was enabled and the query contained a must-understand
extension.
Action: remove the unsupported must-understand extension.
ORA-19236: XQST0016 - module declaration or import not supported
Cause: The given query had a module declaration or module import.
Action: Remove the import module or module declaration.
ORA-19237: XPST0017 - unable to resolve call to function - string:string
Cause: The name and arity of the function call given could not be matched with any
in-scope function in the static context.
Action: Fix the name of the function or the number of parameters to match the list of
in-scope functions.
ORA-19238: XPTY0018 - It is a type error if the result of the last step in a path
expression contains both nodes and atomic values
ORA-19239: XPTY0019 - It is a type error if the result of an step (other than the last
step) in a path expression contains an atomic value
Cause: The step expression returned a sequence containing an atomic value.
Action: Fix the path expression to return only nodes.
ORA-19240: XPTY0020 - context item must be node in an axis expression
Cause: The context item that was used in the axis epression is not a node.
Action: Change the context item to be a node.
ORA-19241: XPDY0021 - cast to type string failed
Cause: The value inside a cast expression could not be cast to the required type.
Action: Fix the input to the cast expression to be of a castable type.
ORA-19242: XQST0022 - namespace declaration attribute must be a literal
Cause: The namespace declaration attribute was not a literal string.
Action: Fix the namespace declaration to be a literal string.
ORA-19243: XQTY0023 - invalid document node content in element constructor
Cause: The content sequence in an element constructor contained a document node.
Action: Change the content of the element constructor so that it does not contain a
document node.
ORA-19244: XQTY0024 - invalid attribute node in element constructor
Cause: The content sequence in an element constructor contained an attribute node
following a node that was not an attribute node.
Action: Change the content sequence of the element constructor so that it does not
contain the attribute node.
ORA-19245: XQDY0025 - duplicate attribute name string
Cause: The content sequence of the element constructor contained more than one
attribute that had the same name.
Action: Remove the duplicate attributes.

ORA-19246: validation failed - element string not found in in-scope element
declarations
Cause: The validation mode was strict and the element-constructor contained an
element name that was not present in the in-scope element declarations.
Action: Fix the validation mode to be lax or import the schema definition that
contains the required element declaration.
ORA-19247: XQDY0027 - validation error
Cause: An error was encountered during the validation of the expression.
Action: Fix the validation error.
ORA-19248: XQTY0028 - invalid node in document constructor
Cause: The content sequence in a document constructor contained either a document
or an attribute node.
Action: Fix the content so it does not contain any of the above node types.
ORA-19249: XQDY0029 - value does not match facet of the target type
Cause: The input value to a cast expression did not satisfy the facets of the target type.
Action: Fix the value to conform to the facets of the target type.
ORA-19250: XQTY0030 - too many values to validate expression
Cause: The argument of a validate expression returned more than one element or
document node.
Action: Fix the argument of the validate expression to return a single element or
document node.
ORA-19251: XQST0031 - unsupported query version
Cause: The query version specified in the prolog was not supported.
Action: Supply the version of the query that is supported.
ORA-19252: XQST0032 - too many declarations for base URI
Cause: The query prolog contained multiple declarations for the base URI.
Action: Remove the duplicate definitions for the base URI.
ORA-19253: XQST0033 - too many declarations for namespace prefix string
Cause: The query prolog contained multiple declarations for the same namespace
prefix.
Action: Remove the duplicate definitions for the namespace prefix.
ORA-19254: XQST0034 - too many declarations for function string
Cause: The query module contained more than one function, either declared or
imported, which have the same expanded QName.
Action: Remove the duplicate function definitions.
ORA-19255: XQST0035 - too many declarations of string in imported schemas
Cause: Two schemas were imported that defined the same name in the same symbol
space and in the same scope.
Action: Fix the schema imports to remove the name conflict.
ORA-12700 to ORA-19400 69-309
ORA-19256: XQST0036 - missing type definitions in imported module

Cause: A module was imported, which contains references to type names that are not
defined in the in-scope type definitions inside the module.
Action: Fix the module definintion to include the in-scope type definition.
ORA-19257: XQST0037 - function or variable string in module already defined
Cause: A module being imported contained the function or variable that is already
declared in the static context of the importing module.
Action: Remove the conflicting declarations.
ORA-19258: XQST0038 - unsupported or duplicate default collation specified
Cause: The query prolog prolog either specified more than one default collation or the
collation specified was not supported.
Action: Remove the duplicate definition or specify a supported collation.
ORA-19259: XQST0039 - duplicate parameter name string in function declaration
Cause: The function declaration contained more than one parameter with the same
name.
Action: Fix the function declaration to remove the duplicate parameters.
ORA-19260: XQST0040 - invalid namespace node in element constructor
Cause: The content sequence in an element constructor contained a namespace node
node following a node that was not a namespace node.
Action: Remove the namespace node in the element constructor.
ORA-19261: XQDY0041 - non empty URI in QName
Cause: The name expression in a computed processing instruction or computed
namespace constructor returned a QName whose URI part was not empty.
Action: Fix the processing instruction or computed namespace constructor to return
the QName with an empty URI part.
ORA-19262: XQST0042 - namespace constructor not inside an element constructor
Cause: The enclosing expression of a computed namespace constructor was not a
computed element constructor.
Action: Fix the namespace constructor to be inside an element constructor.
ORA-19263: XQST0043 - duplicate namespace prefix string
Cause: Two or more computed namespace constructors within the same computed
element constructor attempted to bind the same namespace prefix.
Action: Remove the duplicate namespace definitions.
ORA-19264: XQDY0044 - invalid namespace in attribute constructors
Cause: A computed attribute constructor returned a QName that is in the pre-defined
XML namespace (corresponding to namespace prefix xmlns).
Action: Change the namespace for the computed attribute constructor.
ORA-19265: XQST0045 - invalid or unknown prefix string in function declaration
Cause: The declared function name in a function declaration had no namespace prefix
or had one of the predefined namespace prefixes other than local.
Action: Fix the function declaration to have the correct prefix.
ORA-19266: XQST0046 - invalid URI

Cause: The given URI contained a lexical form that was not valid according to the
definition of xs:anyURI in XML Schema.
Action: Fix the URI.
ORA-19267: module string not found
Cause: The module with the given target URI could not be found.
Action: Fix the prolog to import only available modules.
ORA-19268: XQST0048 - namespace string does not match target namespace string
Cause: The module contained a function or variable whose namespace did not match
the target namespace of the module.
Action: Fix the namespace of the function or variable to match the target namespace
of the module.
ORA-19269: XQST0049 - variable string defined multiple times
Cause: The module defined or imported the same variable multiple times.
Action: Fix the import or the module definition to remove duplicate definitions.
ORA-19270: XPDY0050 - treat failed - expected string got string
Cause: The type of the operand to the treat expression did not match the required
type.
Action: Fix the input operand to be of the correct type.
ORA-19271: XPST0051 - invalid atomic type definition
Cause: The QName used as an AtomicType in a SequenceType was not defined in the
in-scope type definitions as an atomic type.
Action: Use the correct atomic type name.
ORA-19272: XQDY0052 - invalid atomic value in attribute or element constructor
Cause: The content of the element or attribute constructor included an atomic value
that could not be cast into a string.
Action: Fix the content to contain atomic values that can be cast to a string.
ORA-19273: XQST0053 - empty string in namespace declaration
Cause: An empty string was used in a namespace declaration.
Action: Fix the namespace declaration to have a non-empty string.
ORA-19274: XQST0054 - variable initialization failed due to circularity
Cause: A circular definition was encountered when the variable was initialized.
Action: Remove the circularity in the initialization.
ORA-19275: XQST0055 - schema path string not found in list of in-scope schema
definitions
Cause: The ElementTest specified a schema path that could not be found in the list of
in-scope schema definitions.
Action: Include the appropriate schema that can be used to resolve the ElementTest.
ORA-12700 to ORA-19400 69-311
ORA-19276: XPST0005 - XPath step specifies an invalid element/attribute name:

(string)
Cause: The XPath step specified invalid element or attribute name that did not match
any nodes according to the input XML schema or structure.
Action: Correct the element or attribute name as the name may be mis-spelled.
ORA-19277: XPST0005 - XPath step specifies an item type matching no node:
(string)
Cause: The XPath step specified an item type that did not match any nodes according
to the input XML schema or structure.
Action: Correct the item type defintion as node of such type does not exit in the input
XML schema or structure.
ORA-19278: Invalid value: (string) for type: (string)
Cause: The value was invalid for the type.
Action: Correct the value or change the type.
ORA-19279: XPTY0004 - XQuery dynamic type mismatch: expected singleton
sequence - got multi-item sequence
Cause: The XQuery sequence passed in had more than one item.
Action: Correct the XQuery expression to return a single item sequence.
ORA-19280: XQuery dynamic type mismatch: expected atomic value - got node
Cause: A node was passed in to the expression where an atomic value was expected.
Action: Correct the XQuery expression to return an atomic value.
ORA-19281: XQST0055 - It is a static error if a Prolog contains more than one copynamespaces declaration
Cause: The query prolog contained multiple copy-namespaces declarations.
Action: Remove the duplicate copy-namespaces declarations.
ORA-19282: XQST0068 - It is a static error if a Prolog contains more than one
xmlspace declaration
Cause: The query prolog contained multiple xmlspace declarations.
Action: Remove the duplicate xmlspace declarations.
ORA-19283: XQST0031 - It is a static error if the version number specified in a
version declaration is not supported by the implementation.
Cause: The query contained a version declaration not supported by this
implementation.
Action: Change the version declaration to 1.0 which is the version supported by this
implementation.
ORA-19284: Encoding specification in version declaration not supported
Cause: The query contained an encoding specification.
Action: Remove the encoding specification.
ORA-19285: FODC0002 - error retrieving resource
Cause: The URI provided could not be resolved to a valid resource.
Action: Provide a valid URI for a resource.
ORA-19286: XPST0017 - unable to resolve call to function - string

in-scope functions.
ORA-19287: XPST0017 - invalid number of arguments to function - string:string
in-scope functions.
ORA-19288: XPST0017 - invalid number of arguments to function - string
in-scope functions.
ORA-19289: XQST0034 - function string:string declared or defined multiple times
Cause: Multiple functions declared or imported by a module had the same expanded
QName and the same number of arguments.
Action: Fix the function declaraction or definition to remove duplicates.
ORA-19290: XQST0069 - more than one empty order declaration declared in the
prolog
Cause: A prolog had more than one empty order declaration.
Action: Fix the prolog to have just one empty order declaration.
ORA-19291: XPST0081 - specified QName cannot be expanded into a namespace
URI
Cause: The namespace prefix of the QName could not be expanded into a namespace
URI by using the statically known namespaces.
Action: Use a namespace prefix that can be resolved into a namespace URI from the
statically known namespaces.
ORA-19292: XQST0057: It is a static error if a schema import binds a namespace
prefix but does not specify a target namespace other than a zero-length string
ORA-19293: XQST0058: It is a static error if multiple schema imports specify the
same target namespace
ORA-19294: XQST0059: It is a static error if an implementation is unable to process
a schema or module import by finding a schema or module with the specified
target namespace
ORA-12700 to ORA-19400 69-313
ORA-19295: XQST0060: It is a static error if the name of a function in a function

declaration is not in a namespace (expanded QName has a null namespace URI)
ORA-19296: XQDY0061: It is a dynamic error if the operand of a validate expression
is a document node whose children do not consist of exactly one element node and
zero or more comment and processing instruction nodes, in any order
ORA-19297: XQDY0064: It is a dynamic error if the value of the name expression in
a computed processing instruction constructor is equal to "XML" (in any
combination of upper and lower case
ordering mode declaration
default element/type namespace declaration, or more than one default function
namespace declaration
ORA-19300: Error occurred in uri processingstring
Cause: An error occurred when processing the URL
ORA-19320: Host name not specified in HTTP URL
Cause: A host name was not specified in the HTTP url
Action: Specify a host name in the HTTP url when creating the URL string
ORA-19321: Could not open HTTP connection to host (string): port (string)
Cause: A HTTP connection could not be opened to the host
Action: Specify a valid host name and port to connect to
ORA-19322: An error occurred while reading from host (string): port (string)
Cause: An error occurred while reading from the HTTP host
Action: Specify a valid host name and port to read from
ORA-19323: Invalid url string
Cause: The URL must be a valid URL string
Action: Specify a valid url string
ORA-19330: Type 'string'.'string' not installed. Please install the type before using
the CREATE_DBURI operator
Cause: The type required for the CREATE_DBURI operator has not been installed
correctly.
Action: Read the installation notes to install the type correctly.
ORA-19331: Last argument to CREATE_DBURI operator must be a column
Cause: The final argument to the CREATE_DBURI operator must be a column to
which the reference is being created.
Action: Specify a valid column name in the query.
ORA-19332: Invalid column in the CREATE_DBURI operator
Cause: The argument to the CREATE_DBURI operator can only be a column.
Action: Specify a valid column name for the operator
ORA-19333: Invalid flags for the CREATE_DBURI operator
Cause: The flags argument given to the DBURI operator is invalid
Action: Specify a valid flag value (TEXT) for the DBURI operator
ORA-19334: Invalid column specification for CREATE_DBURI operator
Cause: All columns must be valid and pointing to the same table or view
Action: Specify valid list of columns that are from the same table or view.
ORA-19335: Invalid format type object
Cause: An invalid format type object was specified for the XML function
Action: Specify a valid format type object
ORA-19336: Missing XML root element
Cause: The XML being generated does not have an enclosing root element.
Action: The XML generated must have a root element
ORA-19361: ONLINE option not allowed with this type of index
Cause: The ONLINE option was specified to validate the structure of a systemgenerated metadata index
Action: The ONLINE option can not be used with system-generated metadata indexes
such as an LOB index, an IOT Top index, an Index on Clusters etc., Run query
without using the ONLINE option.
ORA-19371: invalid update option
Cause: The user attempted to call load_sqlset with an update option that is different
than REPLACE and ACCUMULATE.
Action: Adjust the update option and retry the operation.
ORA-19372: invalid update condition
Cause: The user attempted to call load_sqlset with an invalid update condition.
Action: Check the update condition (e.g., NEW.COL1_NAME >= OLD.COL2_NAME)
ORA-19373: invalid staging table or tablespace
Cause: The user attempted to create a staging table and specified an invalid staging
table (or one that already exists) or tablespace
ORA-12700 to ORA-19400 69-315
Action: Check the arguments and try again.

ORA-19374: invalid staging table
Cause: The user specified an invalid staging table to one of the pack, unpack, or
remap stgtab routines, or the user does not have the correct privileges on the staging
table
Action: Provide a correct staging table or grant the appropriate privileges
ORA-19375: no CREATE TABLE privilege on schema "string"
Cause: The user tried to create a staging table when he is missing the CREATE TABLE
privilege on the specified schema.
Action: Grant the privilege to the user and retry
ORA-19376: no privileges on tablespace provided or tablespace is offline
Cause: The user tried to create a staging table on a tablespace on which he does not
have any space allocated, or it is offline
Action: Allocate space on the tablespace, bring it online, and retry
ORA-19377: no "SQL Tuning Set" with name like "string" exists for owner like
"string"
Cause: The user specified a filter to a pack/unpack function for the SQL Tuning Set
that targets no STS in the SYS schema or the staging table, respectively
Action: Provide a different filter after checking the state of the system
ORA-19378: invalid mode
Cause: The user specified an invalid mode argument to the capture function.
Action: Provide a mode argument that was defined in the dbmssqlt file
ORA-19379: invalid time_limit or repeat_interval
Cause: The user specified a NULL value for either the time_limit or the
repeat_interval, or a repeat_interval that is greater than the time_limit
Action: Provide a non-null value and make sure time_limit >= repeat_interval
ORA-19380: invalid plan filter
Cause: The user specified an invalid filter for the plan when calling the select_sqlset
table function.
Action: Adjust the the filter to be one of the following values and retry the operation:
MAX_ELAPSED_TIME, MAX_CPU_TIME, MAX_DISK_READS,
MAX_OPTIMIZER_COST, MAX_BUFFER_GETS, FIRST_LOADED LAST_LOADED,
FIRST_GENERATED, or LAST_GENERATED.
ORA-19381: cannot create staging table in SYS schema
Cause: The user attempted to create a staging table in the sys schema
Action: Create the table in another schema.
ORA-19384: cannot pack into staging table from previous version
Cause: An attempt was made to perform a pack operation on a staging table from a
previous version.
Action: Create a staging table in the current version and retry the operation.
ORA-19385: staging table is empty
Cause: An attempt was made to perform an operation on an empty staging table.
Action: Check the staging table to make sure that it has rows.
ORA-19386: target object already exists for tuning task "string"
Cause: An attempt was made to set a target object for a tuning task when one had
already been set.
Action: Create a new task if another target object is needed.
ORA-19387: "SQL Tuning Set" "string" belongs to another tuning task
Cause: The user attempted to tune a task-managed SQL Tuning Set belonging to one
task within the scope of another task.
Action: Check the SQL Tuning Set and retry the operation.
ORA-19388: operation not supported for "SQL Tuning Set" type
Cause: The attempted operation was unsupported for the type of the given SQL
Tuning Set.
Action: Check the SQL Tuning Set and retry the operation.
ORA-19389: LOB types are not supported for SQL binds
Cause: A LOB type was provided in a SQL bind list.
Action: Replace the LOB binds with legal bind types or try another SQL.
ORA-19390: The profile type is not valid
Cause: The profile type is not valid.
Action: Check the available profile types.
ORA-19400: System type conflict with object SYS.string
Cause: The user had an object with the same name as one of the system types. The
system types were not initialized properly.
Action: Remove the conflicting object and rerun migration.
ORA-12700 to ORA-19400 69-317
70
ORA-19500 to ORA-19997
ORA-19500: device block size string is invalid
Cause: the device block size returned by sequential I/O OSD is invalid
Action: If the block size was set by using the PARMS option of the Recovery Manager
ALLOCATE CHANNEL command, then the specified block size must be changed. If
no PARMS option was specified on the ALLOCATE CHANNEL command, then this
is an internal error that should be reported to Oracle.
ORA-19501: read error on file "string", block number string (block size=string)
Cause: read error on input file
Action: check the file
ORA-19502: write error on file "string", block number string (block size=string)
Cause: write error on output file
Action: check the file
ORA-19503: cannot obtain information on device, name="string", type="string",
parms="string"
Cause: call to get device information returned an error
Action: check device name, type and parameters
ORA-19504: failed to create file "string"
Cause: call to create file returned an error
Action: check additional messages, check access permissions.
ORA-19505: failed to identify file "string"
Cause: call to identify the file returned an error
Action: check additional messages, and check if the file exists.
ORA-19506: failed to create sequential file, name="string", parms="string"
Cause: call to create the sequential file returned an error
Action: check additional messages, check access permissions.
ORA-19507: failed to retrieve sequential file, handle="string", parms="string"
Cause: call to retrieve the sequential file returned an error
Action: check additional messages, and check if the file exists.
ORA-19508: failed to delete file "string"
Cause: call to delete the file returned an error
Action: check additional messages.
ORA-19500 to ORA-19997 70-1
ORA-19509: failed to delete sequential file, handle="string", parms="string"

Cause: call to delete the sequential file returned an error
ORA-19510: failed to set size of string blocks for file "string" (block size=string)
Cause: call to resize the file returned an error
ORA-19511: non RMAN, but media manager or vendor specific failure, error text:
\n string
Cause: An error occurred in the media management software which is linked with 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, then you should contact the vendor of the media management software.
ORA-19512: file search failed
Cause: Recovery manager or Oracle Server attempted to discover files that matched
the specified pattern but failed.
Action: Check errors on the error stack for an explanation why the search for files
could not be successfully executed.
ORA-19513: failed to identify sequential file
Cause: Unable to identify the sequential file.
Action: Check additional messages, and check if the file exists on media.
ORA-19525: tempfile for the clone database must be renamed
Cause: Opening a clone database failed because Oracle server forces the tempfile to be
renamed, in order to avoid overwriting the primary tempfile.
Action: Rename the tempfiles manually or automatically by using the
DB_FILE_NAME_CONVERT initialization parameter.
ORA-19526: only one location allowed for parameter string
Cause: A list of default locations was provided in an Oracle-managed files parameter.
Action: Edit the parameter to include a single location.
ORA-19527: physical standby redo log must be renamed
Cause: An attempt was made to clear redo log at a physical standby database.
Clearing an OMF redo log will not work unless DB_CREATE_FILE_DEST,
DB_CREATE_ONLINE_LOG_DEST_n or DB_RECOVERY_FILE_DEST parameter is
specified. Clearing a non-OMF (or user-defined) redo log file will not work unless the
LOG_FILE_NAME_CONVERT initialization parameter is set.
Action: Set DB_CREATE_FILE_DEST, DB_CREATE_ONLINE_LOG_DEST_n or
DB_RECOVERY_FILE_DEST parameter for OMF redo log files and re-issue the
operation that attempted to clear redo log. Set LOG_FILE_NAME_CONVERT
parameter for non-OMF redo log files and re-issue the operation that attempted to
clear redo log.
ORA-19528: redo logs being cleared may need access to files
Cause: The redo logs are being cleared. This procedure may need the files this
operation is being applied to.
Action: Wait for the redo logs to be cleared.
70-2 Error Messages
ORA-19529: Pattern string in initialization parameter string has an Oracle Managed

Files file name.
Cause: An attempt was made to convert a database file name to an Oracle Managed
Files file name using DB_FILE_NAME_CONVERT, PDB_FILE_NAME_CONVERT or
LOG_FILE_NAME_CONVERT initialization parameter. This was not a valid
operation.
Action: Retry the operation with a pattern template instead of a full Oracle Managed
Files file name.
ORA-19550: cannot use backup/restore functions while using dispatcher
Cause: Attempted to use backup/restore functions while connected to the dispatcher
in a shared server. This is not allowed because the device that is used for backup and
restore must remain allocated to a single process.
Action: Connect directly to the instance then re-execute the backup or restore
function.
ORA-19551: device is busy, device type: string, device name: string
Cause: The indicated device could not be allocated because it is allocated to another
session, or no device was named, or all devices of the requested type are busy.
Action: Either attempt to allocate another device or wait until the required device is
no longer busy.
ORA-19552: device type string is invalid
Cause: The device type indicated is invalid.
Action: Supply a correct device type and retry the allocation.
ORA-19553: device name string is invalid
Cause: The device name indicated is invalid.
Action: Supply a correct device name and retry the allocation.
ORA-19554: error allocating device, device type: string, device name: string
Cause: The specified device could not be allocated.
Action: One or more other messages should be displayed to help pinpoint the cause
of the error. Correct the error and retry the allocation.
ORA-19555: invalid LOG_ARCHIVE_MIN_SUCCEED_DEST parameter value
Cause: The value of parameter LOG_ARCHIVE_MIN_SUCCEED_DEST was not set
within the valid range.
Action: Specify a correct value for parameter
LOG_ARCHIVE_MIN_SUCCEED_DEST. If the archive log parameters
LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST are in use, set parameter
LOG_ARCHIVE_MIN_SUCCEED_DEST to either 1 or 2.
ORA-19556: required destination LOG_ARCHIVE_DUPLEX_DEST currently is
deferred
Cause: The destination for parameter LOG_ARCHIVE_DUPLEX_DEST was deferred
when it was required to be enabled. The destination was deferred automatically when
an ALTER SYSTEM command for parameter LOG_ARCHIVE_DEST defined a
destination which duplicated an existing LOG_ARCHIVE_DUPLEX_DEST parameter
destination.
Action: Change the destination value for the LOG_ARCHIVE_DUPLEX_DEST
parameter.
ORA-19500 to ORA-19997 70-3
ORA-19557: device error, device type: string, device name: string

Cause: An error occurred in the platform-specific device code
ORA-19558: error de-allocating device
Cause: The specified device could not be de-allocated.
ORA-19559: error sending device command: string
Cause: An error occurred while sending the indicated command to the session device.
ORA-19560: string is not a valid device limit name
Cause: An invalid name of device limit was specified in a call to
DBMS_BACKUP_RESTORE.SETLIMIT.
Action: Use one of the device limit names described in dbmsbkrs.sql
ORA-19561: string requires a DISK channel
Cause: The attempted command requires that a DISK device channel be allocated to
the session, but a non-DISK device was found.
Action: Deallocate the current device and allocate a DISK channel, then then retry the
command.
ORA-19562: file string is empty
Cause: The indicated file, which is an archived log, control file, or datafile was found
to be empty during a copy, backup, or scan] operation.
Action: Ensure that the correct files are being specified for the copy or backup
operation.
ORA-19563: string header validation failed for file string
Cause: When opening the file to be placed in a copy or backup set, to be inspected, or
used as the target for an incremental restore, its header was not recognized as a valid
file header for a file of the indicated type (datafile, archived log, or control file)
belonging to the current database.
Action: Ensure that the correct files are being specified for the copy or backup
operation.
ORA-19564: error occurred writing string bytes at block number string
Cause: An error occurred while writing to a file.
of the error. Correct the error if possible, then retry the copy, backup, or restore
operation.
ORA-19565: BACKUP_TAPE_IO_SLAVES not enabled when duplexing to
sequential devices
Cause: An attempt was made to specify duplexing to sequential devices, but the
BACKUP_TAPE_IO_SLAVES initialization parameter was not enabled.
70-4 Error Messages
Action: Specify BACKUP_TAPE_IO_SLAVES=TRUE in the INIT.ORA file, or do not

specify duplexing to sequential devices.
ORA-19566: exceeded limit of string corrupt blocks for file string
Cause: The user specified limit of allowable corrupt blocks was exceeded while
reading the specified datafile for a datafile copy or backup.
Action: None. The copy or backup operation fails. The session trace file contains
detailed information about which blocks were corrupt.
ORA-19567: cannot shrink file string because it is being backed up or copied
Cause: An ALTER statement attempted to reduce the size of the indicated file while
the same file is being backed up or copied.
Action: Retry the resize after the backup or copy is complete.
ORA-19568: a device is already allocated to this session
Cause: A device cannot be allocated to a session if another device is already allocated.
Action: Deallocate the current device
ORA-19569: no device is allocated to this session
Cause: An operation was attempted which requires a device to be allocated to the
current session, and there is no device allocated.
Action: Allocate a device then retry the operation.
ORA-19570: file number string is outside valid range of 1 through string
Cause: A file number used in a copy, backup, or restore operation is not valid 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 is not found in the control file.
Action: Specify a correct RECID/STAMP and retry the copy or backup.
ORA-19572: cannot process file string, file is being being resized
Cause: The input file specified for a copy or backup operation could not be opened
because the file is being resized.
Action: Wait for the resize to complete then retry the copy or backup.
ORA-19573: cannot obtain string enqueue for datafile string
Cause: The file access enqueue could not be obtained for a file specified in a backup,
copy or restore operation. If the enqueue type shown is 'shared', then the file is the
input file for a backup or copy. If the type is 'exclusive', then the file is the output file
for a datafile copy or restore which is attempting 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', then you are attempting to back up or copy this file
while the database is in NOARCHIVELOG mode.
Action: Wait until the conflicting operation is complete, then retry the copy or
backup. If the database is in NOARCHIVELOG mode, then all files being backed up
must be closed cleanly.
ORA-19574: output file name must be specified
Cause: This type of copy or restore requires an output file name.
ORA-19500 to ORA-19997 70-5
Action: Specify an output file name and retry the copy.

ORA-19575: expected string blocks in file string, found string
Cause: During a backup, restore, copy, or scan operation, the indicated file did not
contain as many blocks as were indicated in the file header.
Action: The input copy or backup piece is probably corrupt. If another backup or
copy exists of the file that is being restored, then the corrupt file can be deleted from
the recovery catalog and the operation can be restarted.
ORA-19576: datafile 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 no 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 not named during the last CREATE
CONTROLFILE statement, so the name in the control file cannot be used for
restoration.
Action: Either specify an output file name or issue a SQL RENAME command to enter
a valid name for this file in the control file.
ORA-19578: end of volume while duplexing to sequential files, backup piece
incomplete
Cause: An end of volume (EOV) condition was detected while duplexing to
sequential files, and this condition cannot be handled currently.
Action: Before retrying the backup, make sure the backup pieces will fit in the
volume, or disable duplexing.
ORA-19579: archived log record for string not found
Cause: No archived log record corresponding to input file could be found in the
control file.
Action: Specify a valid archived log file name and retry the operation.
ORA-19580: string conversation not active
Cause: A backup or restore operation was attempted before a conversation was
started.
Action: Start a conversation then retry the operation.
ORA-19581: no files have been named
Cause: An attempt was made to proceed from the file naming phase to the piece
processing phase of a backup or restore conversation before any files have been
specified for backup or restore.
Action: Specify some files then retry the operation.
ORA-19582: archived log file header validation for string failed
Cause: Archived log file header is corrupt and could not be validated.
Action: Provide a valid archived log file and retry the operation.
70-6 Error Messages
ORA-19583: conversation terminated due to error

Cause: An error occurred which forced the termination of the current backup or
restore conversation.
Action: There should be other error messages to help identify the cause of the
problem. Correct the error and begin another conversation.
ORA-19584: file string already in use
Cause: The indicated file, which was specified as the target for a copy, restore, or
delete operation is already in use by the database.
Action: Specify a different name and retry the operation.
ORA-19585: premature end of volume on piece string
Cause: While creating the indicated backup piece, an end-of-volume condition was
encountered before all of the backup set control data was written to the backup piece.
This is most likely a media error, because the amount of backup set control data is
very small in relation to the total amount of data in a backup set.
Action: Retry the piece with a larger piece of output media.
ORA-19586: string k-byte limit is too small to hold piece directory
Cause: The user-specified limit for MAXPIECESIZE for this channel is not enough to
hold the backup set control data.
Action: Allocate a channel specifying a larget valule for MAXPIECESIZE and retry the
operation.
ORA-19587: error occurred reading string bytes at block number string
Cause: An error occurred while reading from a file.
of the error. Correct the error then retry the copy, backup, or restore operation.
ORA-19588: string RECID string STAMP string is no longer valid
Cause: The indicated record has been marked as deleted. This indicates that the
corresponding file has either been overwritten by another copy or restore, or that the
copy was 'consumed' by a SWITCHTOCOPY operation.
Action: If you know the name of the file you wish to copy, then inspect it and then
retry the copy specifying the new RECID.
ORA-19589: string is not a snapshot or backup control file
Cause: The control file that is the source for a backup or copy operation is not a
snapshot or backup control file.
Action: Specify the name of a snapshot or backup control file.
ORA-19590: conversation already active
Cause: You tried to begin a backup or restore conversation, but another conversation
is already active in this session.
Action: Either continue the current conversation, or call BACKUPCANCEL or
RESTORECANCEL to end the current conversation before starting a new one.
ORA-19591: backup aborted because job time exceeded duration time
Cause: You tried to backup with duration option and the time provided was not
sufficient to complete the backup.
ORA-19500 to ORA-19997 70-7
Action: Adjust the duration time and re-run the command. Or run the backup
command without duration option.
ORA-19592: wrong string conversation type
Cause: You attempted to specify a type of file to be backed-up or restored, but the
current conversation cannot process this type of file. For example, you specified an
archived log to be included in a datafile backup set. The specified file will not be
included in the backup or restore operation.
Action: No action required - the conversation is still active, and more files can be
specified.
ORA-19593: datafile number string already included as string
Cause: This datafile is already specified for inclusion in this backup or restore
conversation. A backup or restore conversation may process only a single instance of
a datafile.
specified.
ORA-19594: control file already included as string
Cause: The control file is already specified for inclusion in this backup or restore
the control file.
specified.
ORA-19595: archived log string already included in backup conversation
Cause: The indicated archived log has already been specified for inclusion in this
backup conversation.
specified.
ORA-19596: SPFILE already included
Cause: The SPFILE is already specified for inclusion in this backup or restore
the SPFILE.
specified.
ORA-19597: file string block size string does not match set block size of string
Cause: A file was specified for inclusion in a backup set but it has a logical block size
different from 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: can not backup SPFILE because the instance was not started with
SPFILE
Cause: A backup command requested a backup of the SPFILE, but no SPFILE was
used to startup the instance.
Action: Create an SPFILE and re-start the instance using the SPFILE.
70-8 Error Messages
ORA-19599: block number string is corrupt in string string

Cause: A corrupt block was found in a control file, archived log, or backup piece that
is being read for a backup or copy. Corruption shall not be tolerated in control files,
archived logs, or backup pieces.
Action: None. The copy or backup operation fails. Note that in the case of a backup
set, the conversation is still active and the piece may be retried.
ORA-19600: input file is string string (string)
Cause: This message identifies the input file for a failed copy operation. Both the file
number and name (if the name has been determined) are shown. For a datafile, the
file number refers to the datafile's absolute file number as shown in the
DBA_DATA_FILES view. For a datafile copy, the file number refers to the copy's
control file record number as shown in the RECID column of the V
$DATAFILE_COPY view. For an archived log, the file number refers to the log's
control file record number as shown in the RECID column of the V$ARCHIVED_LOG
view.
Action: See other error message.
ORA-19601: output file is string string (string)
Cause: This message identifies the output file for a failed copy operation. The fields
are as described in message 19600. When creating a new datafile copy, its control file
record number may not have been determined when the message is printed. In that
case, the record number shown is zero.
ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode
Cause: You tried to copy or backup a file that was not closed cleanly, and the
database was in NOARCHIVELOG mode. This is not allowed because when restored,
the file will require redo application before it is usable, and redo is not currently being
saved beyond the contents of the online redo logs.
Action: Take the tablespace offline clean or close the database and retry the copy or
backup.
ORA-19603: cannot backup or copy active file with KEEP .. UNRECOVERABLE
option
Cause: The user tried to copy or backup a file that was not closed cleanly, with
KEEP .. UNRECOVERABLE option. This is not allowed because when restored, the
file will require redo application before it is usable, and redo will not be saved
because of KEEP .. UNRECOVERABLE option.
Action: Take the tablespace offline cleanly, or close the database and retry the copy or
backup.
ORA-19604: conversation file naming phase is over
Cause: A call was made to specify a file to be backed up or restored after the first
backup piece has been processed.
Action: You cannot specify more files to be processed during a backup or restore
conversation after the first backup piece has been processed. If more files must be
specified, you must begin a new conversation.
ORA-19605: input file name must be specified
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-19500 to ORA-19997 70-9
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. It is not permitted to overwrite the snapshot control file
in this manner. Other methods are available to create the snapshot control file.
Action: Specify a different file name and retry the operation. If this is a restore, then
the restore conversation remains active and more files may be specified.
ORA-19607: string is an active control file
Cause: A control file copy, restore, or backup specified the name of a control file
named in the INIT.ORA file as the input or output file.
Action: Specify a different file name and retry the operation. If this is a backup or
restore conversation, then the conversation remains active and more files may be
specified.
ORA-19608: string is not a backup piece
Cause: The specified file is not a backup piece produced by the
DBMS_BACKUP_RESTORE package. Either the first block of the backup piece is
corrupt or this file is not a backup piece.
Action: Specify a different file name and retry the operation.
ORA-19609: string is from different backup set: stamp string count string
Cause: The specified file is not from the backup set which is currently being
processed. It is part of a different backup set. The identification of the set containing
this piece is shown.
Action: Specify the correct backup piece and retry the operation.
ORA-19610: directory block string is corrupt
Cause: The indicated directory block failed checksum validation. This backup piece is
unusable.
Action: Supply another copy of the same backup piece, or terminate the restore
conversation.
ORA-19611: backup piece out of order. Expected string but found string
Cause: This backup piece is out of sequence.
Action: Supply the correct backup piece.
ORA-19612: datafile string 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 piece.
Action: The restore conversation remains active, and the current piece must be reprocessed. If the failure cannot be resolved by re-processing the current piece, then
the restore conversation must be cancelled.
ORA-19613: datafile 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, then this refers to the control file.
Action: This message is issued when the directory from the first backup piece is read
and one or more files named for restoration were not found. The restore conversation
is still active, but no data has been read and you must supply the first backup piece of
a backup set that contains all of the requested files.
ORA-19614: archived log thread string sequence string not found in backup set
Cause: The indicated archived log file was named explicitly for restoration but is not
contained in this backup set.
and one or more files named for restoration were not found. The restore conversation
is still active, but no data has been read and you must supply the first backup piece of
a backup set that contains all of the requested files.
ORA-19615: some files not found in backup set
Cause: Some files that were specified for restoration were not found in the backup set
directory. Message 19613 or 19614 is issued for each file that was not found.
Action: See the instructions for message 19613.
ORA-19616: output file name must be specified if database not mounted
Cause: A datafile restore specified no target file name, but the database is not
mounted. The database must be mounted when no target file name is specified, so
that the target file name can be obtained from the control file.
Action: The restore conversation remains active. If you wish to restore datafiles
without their target file names, then mount the database before continuing.
Otherwise, a target file name must be specified on all datafile restoration calls.
ORA-19617: file string contains different RESETLOGS data
Cause: The indicated file contains RESETLOGS data which is different from the
archived log files which are already included in the backup set. All archived log files
in a backup set must have the same RESETLOGS data.
Action: The restore conversation remains active, and you may continue to specify
archived log files for inclusion in the backup set.
ORA-19618: cannot name files after RESTOREVALIDATE has been called
Cause: A call was made to specify a file to restore from a backup set, but a previous
call to RESTOREVALIDATE has already been made.
Action: You must cancel and restart the conversation if you wish to specify files to
restore.
ORA-19619: cannot call RESTOREVALIDATE after files have been named
Cause: RESTOREVALIDATE was called after some files had already been specified
for restoration.
Action: You must cancel and restart the conversation if you wish to call
RESTOREVALIDATE.
ORA-19620: string is not of string type
Cause: When opening the file to be placed in a copy or backup set, to be inspected, or
used as the target for an incremental restore, its header was not recognized as a valid
file header for a file of the indicated type (datafile, archived log, or control file)
belonging to the current database.
Action: The indicated file cannot be processed. Ensure that the correct files are being
specified for the copy or backup operation.
ORA-19621: archived log range has already been specified
Cause: A range of logs has already been specified. Only one SCN range may be
specified per conversation.
ORA-19500 to ORA-19997 70-11
Action: The restore conversation remains active and more logs may be specified by
thread and sequence number, if desired.
ORA-19622: archived log thread string sequence string 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 piece.
Action: The restore conversation remains active, and the current piece must be reprocessed. If the failure cannot be resolved by re-processing the current piece, then
the restore conversation must be cancelled.
ORA-19623: file string is open
Cause: A SWITCHTOCOPY operation specified a datafile copy whose parent datafile
is open.
Action: Take the owning tablespace offline or close the database, then retry the
operation.
ORA-19624: operation failed, retry possible
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, then the operation may be retried.
Action: This message is used by recovery manager to decide whether or not to retry
the operation.
ORA-19625: error identifying file string
Cause: A file specified as input to a copy or backup operation, or as the target for an
incremental restore, could not be identified as an Oracle file. The file may have been
deleted or moved so that it is no longer accessible to RMAN. An operating systemspecific error accompanies this error to help pinpoint the problem.
Action: Specify a different file and retry the operation. If the problem file has simply
been deleted or moved, you can run crosscheck to allow RMAN to update its
metadata with the correct file status.
ORA-19626: backup set type is string - can not be processed by this conversation
Cause: The data in the backup set is not compatible with the current conversation.
Action: Either supply the first piece from a backup set that matches the current
conversation or start a new restore conversation which can process this backup set.
ORA-19627: cannot read backup pieces during control file application
Cause: This is a control file restore conversation, which is using the offline range
information from one or more control files to update datafile checkpoint data. Backup
sets are not used during this type of conversation.
Action: The conversation is still active and more control files may be applied.
ORA-19628: invalid SCN range
Cause: The starting SCN for RESTOREREDOLOGRANGE is greater than the ending
SCN.
Action: Specify a starting SCN which is less than or equal to the ending SCN.
ORA-19629: no files in specified archived log SCN range
Cause: This backup set contains no files in the specified range.
Action: Either supply a backup set that contains files in the correct range or start a
new conversation and specify a range which will select some files from this backup
set.
ORA-19630: end of volume encountered while copying backup piece

Cause: While copying a backup piece from the OS native file system to an output
device, the output device encountered end-of-volume.
Action: The copy fails. This could happen if a tape was used which is not large
enough to hold the entire backup piece.
ORA-19631: archived log record contains no file name
Cause: This archived log record represents a switch into an active log that took place
without archiving its prior contents. The prior contents of the log file are lost.
Action: Specify the RECID of an archived log record that contains a file name. Fixed
view v$archived_log can be used to examine the archived logs.
ORA-19632: file name not found in control file
Cause: The name passed to GETFNO was not found in the control file.
Action: Supply a valid file name.
ORA-19633: control file record string is out of sync with recovery catalog
Cause: The control file record describing the file to be deleted in a call to
DELETEBACKUPPIECE, DELETEDATAFILECOPY, PROXYDELETE or
DELETEARCHIVEDLOG does not match the validation data supplied by recovery
manager.
Action: contact Oracle support
ORA-19634: file name required for this function
Cause: The FNAME or HANDLE parameter was not specified for DELETEPIECE,
DELETEDATAFILECOPY, DELETEREDOLOG or PROXYDELETE.
Action: Specify the FNAME or HANDLE parameter when calling these functions.
ORA-19635: input and output file names are identical: string
Cause: Identical input and output file names were specified for a datafile copy
operation.
Action: Specify an output file name which is different from the input file name.
ORA-19636: archived log thread string sequence string already included
Cause: The indicated archived log has already been specified for inclusion in this
restore conversation. A restore conversation may process only one copy of any
archived log.
specified.
ORA-19637: BACKUPPIECECREATE requires file name when using DISK device
Cause: The session device is currently allocated to disk, and so a file name is required.
Action: Supply a file name and retry the operation.
ORA-19638: file string is not current enough to apply this incremental backup
Cause: The checkpoint of the target for this incremental backup is less than the start of
the incremental backup. If this backup were applied, then any changes made between
the datafile checkpoint and the start of the incremental backup could be lost.
Action: Supply a backup set that can be applied and retry the operation.
ORA-19500 to ORA-19997 70-13
ORA-19639: file string is more current than this incremental backup

Cause: The checkpoint of the target for this incremental backup is greater than or
equal to the checkpoint of the file in the incremental backup set. This backup cannot
advance the checkpoint of the target file, so there is no point in applying it.
Action: Supply a backup set that can be applied and retry the operation.
ORA-19640: datafile checkpoint is SCN string time string
Cause: This message identifies the datafile checkpoint for a datafile that was too old
to take an incremental backup from, or the target of an incremental restore that could
not be applied.
ORA-19641: backup datafile checkpoint is SCN string time string
Cause: This message identifies the checkpoint of a datafile in an incremental backup
set that could not be applied.
ORA-19642: start SCN of incremental backup is string
Cause: This message identifies the starting SCN of an incremental backup that could
not be applied.
ORA-19643: datafile string: incremental-start SCN is too recent
Cause: The incremental-start SCN which was specified when starting an incremental
datafile backup is greater than the datafile checkpoint SCN, which could cause some
blocks to be missed.
Action: Specify a smaller incremental-start SCN.
ORA-19644: datafile string: incremental-start SCN is prior to RESETLOGS SCN
string
datafile backup is less than the RESETLOGS SCN.
Action: Specify a larger incremental-start SCN.
ORA-19645: datafile string: incremental-start SCN is prior to creation SCN string
datafile backup is less than the datafile's creation SCN.
Action: Specify a larger incremental-start SCN.
ORA-19646: cannot change size of datafile string from string to string
Cause: Restore needs to adjust the size of the file as indicated, but the file size
adjustment failed.
Action: Examine the other messages which should be present to indicate the cause of
the failure.
ORA-19647: non-zero LEVEL cannot be specified when INCREMENTAL is FALSE
Cause: BACKUPSETDATAFILE was called with a non-zero backup_level and a
FALSE incremental indication.
Action: Either set incremental to TRUE or change backup_level to zero.
ORA-19648: datafile string: incremental-start SCN equals checkpoint SCN

datafile backup is equal to the datafile's checkpoint SCN. Since an incremental backup
can only be applied to a datafile whose checkpoint SCN is between the backup set
incremental-start SCN (inclusive) and the backup set checkpoint SCN (exclusive),
there is no datafile that this backup set could ever be applied to.
Action: Specify a smaller incremental-start SCN. NOTE that this message will usually
only be encountered by the user while taking an incremental backup with Recovery
Manager. Recovery Manager should intercept all usual cases of this error and simply
ignore the incremental backup for this file. So, if you do encounter this error, please
report it to Oracle Support.
ORA-19649: offline-range record RECID string STAMP string not found in file
string
Cause: APPLYOFFLINERANGE was called with a RECID/STAMP which 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 a record that exists in the control file copy.
ORA-19650: Offline-range record RECID string STAMP string in file string has
SCN string
Cause: This messages identifies the offline-clean SCN from the indicated offline-range
record in the indicated file.
ORA-19651: cannot apply offline-range record to datafile string: SCN mismatch
Cause: APPLYOFFLINERANGE cannot apply an offline-range record to a target
datafile unless the datafile's checkpoint SCN exactly matches the offline-clean SCN in
the specified offline-range record.
Action: Specify an offline-range record whose offline-clean SCN matches the target
datafile's checkpoint.
ORA-19652: cannot apply offline-range record to datafile string: file is fuzzy
Cause: The target datafile for an APPLYOFFLINERANGE call is fuzzy.
Action: Specify a target datafile that is closed cleanly.
ORA-19653: cannot switch to older file incarnation
Cause: SWITCHTOCOPY was called with a datafile copy for a datafile that was
dropped prior to the time this control file was backed up.
Action: Restore and mount an earlier control file. It is acceptable to use a control file
that was backed up prior to the creation of the specified datafile.
ORA-19654: must use backup control file to switch file incarnations
Cause: This SWITCHTOCOPY operation is attempting to switch incarnations of a
datafile, but the currently mounted control file is not a backup control file.
Action: Restore and mount a backup control file.
ORA-19655: cannot switch to incarnation with different RESETLOGS data
Cause: This SWITCHTOCOPY operation is attempting to switch to a datafile which
comes from a different RESETLOGS version of the database.
Action: Either restore a backup control file that was taken from the same database
version as the target datafile copy, or switch to a different datafile copy.
ORA-19500 to ORA-19997 70-15
ORA-19656: cannot backup, copy, or delete online log string

Cause: The indicated log file is an active log. You can only backup, copy, or delete
archived logs.
Action: The indicated log file cannot be processed - select another file.
ORA-19657: cannot inspect current datafile string
Cause: The file being inspected is already part of the currently mounted database.
Action: None - the file is already part of the database.
ORA-19658: cannot inspect string - file is from different RESETLOGS
Cause: The RESETLOGS data in the log file being inspected does not match that in the
currently mounted control file.
Action: The indicated file cannot be processed - inspect another file.
ORA-19659: incremental restore would advance file string past RESETLOGS
Cause: This incremental backup cannot be applied to the specified datafile, because
the datafile is from an earlier incarnation of the database, and its checkpoint would be
advanced too far to be recoverable in the current incarnation of the database.
Action: This incremental cannot be applied to this datafile. If you wish to recover the
file to the RESETLOGS SCN 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 made to verify all the files in a backup set, and the
files which were printed in messages 19661 or 19662 could not be verified because
corrupt blocks for those files were found in the backup set.
Action: Unless the damage to the backup set can be repaired, the indicated files
cannot be restored from this backup set.
ORA-19661: datafile string could not be verified
Cause: Some data blocks for the indicated datafile were corrupt in the backup set.
Action: Unless the damage to the backup set can be repaired, the indicated datafile
cannot be restored from this backup set.
ORA-19662: archived log thread string sequence string could not be verified
Cause: Some data blocks for the indicated archived log were corrupt in the backup
set.
Action: Unless the damage to the backup set can be repaired, the indicated archived
log cannot be restored from this backup set.
ORA-19663: cannot apply current offline range to datafile string
Cause: An attempt was made to apply the current offline range to the specified
datafile, but the datafile is either not current enough or is not at the correct SCN to
apply the offline range.
Action: The datafile remains unchanged.
ORA-19664: file type: string, file name: string
Cause: This message is issued to identify the file which is the subject of an error.
Action: None - this is an informational message. There should be other Oracle
messages explaining the cause of the error.
ORA-19665: size string in file header does not match actual file size of string
Cause: The size of the file as indicated in the file header does not match the true size
of the file. The two differing sizes are shown in units of logical blocks.
Action: This file is not usable - it has most likely been truncated.
ORA-19666: cannot do incremental restore of the control file
Cause: The control file was included in an incremental restore conversation
Action: If you wish to restore the control file, you must do a full restore of the control
file
ORA-19667: cannot do incremental restore of datafile string
Cause: The backup of the datafile is a full backup
Action: If you wish to restore the datafile, you must do a full restore of the datafile
ORA-19668: cannot do full restore of datafile string
Cause: The backup of the datafile is an incremental backup
Action: If you wish to restore the datafile, you must do an incremental restore of the
datafile
ORA-19669: proxy copy functions cannot be run on DISK channel
Cause: A proxy copy procedure was called, but the device which is allocated to the
current session has type DISK.
Action: Allocate a non-DISK channel and retry the operation. Note that proxy copy
requires a 3rd-party media management software product that supports the this
backup/restore feature.
ORA-19670: file string already being restored
Cause: A proxy restore function has already named this file as a restore destination.
Action: Use a different file name. If this message occurs during a recovery manager
job, then this is an internal error in recovery manager, and you should contact Oracle
support.
ORA-19671: media management software returned invalid proxy handle
Cause: During a proxy backup or restore, the media management software returned
an invalid file handle.
Action: This is an internal error in the media management software which is linked
with Oracle to provide backup/restore services. Contact the media management
software vendor.
ORA-19672: media management software returned invalid file status
Cause: During a proxy backup or restore, the media management software returned
an invalid file status.
Action: This is an internal error in the media management software which is linked
with Oracle to provide backup/restore services. Contact the media management
software vendor.
ORA-19673: error during proxy copy of file string
Cause: During a proxy backup or restore, an error occurred while copying this file,
but other files may have been copied successfully.
Action: There should be other errors on the error stack which explain why the file
could not be successfully copied.
ORA-19500 to ORA-19997 70-17
ORA-19674: file string is already being backed up with proxy copy

Cause: Recovery manager attempted to back up the specified file with proxy copy,
but the file is already being backed up by another recovery manager job.
Action: Wait until the other recovery manager backup of this file is complete, then
retry the backup.
ORA-19675: file string was modified during proxy copy
Cause: A proxy backup of the specified file failed because the file was brought on-line
or otherwise modified while the proxy backup was in progress. This file was off-line
or read-only when the backup began, so the file was not put into hot-backup mode,
therefore no modifications are permitted while the backup is in progress.
Action: Take 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. The files for which no error messages are shown were processed
successfully.
Action: Examine the messages regarding the specific files to determine the cause of
the problems.
ORA-19677: RMAN configuration name exceeds maximum length of string
Cause: The configuration name string exceeds maximum length.
Action: Supply a correct configuration name and retry the function.
ORA-19678: RMAN configuration value exceeds maximum length of string
Cause: The configuration value string exceeds maximum length.
Action: Supply a correct configuration value and retry the operation.
ORA-19679: RMAN configuration number string is outside valid range of 1
through string
Cause: An invalid RMAN Configuration number was specified.
Action: Specify a correct datafile number and retry the operation.
ORA-19680: some blocks not recovered. See trace file for details
Cause: Some blocks are not recovered during block media recovery.
Action: See trace files for details of the problem.
ORA-19681: block media recovery on control file not possible
Cause: file number 0 specified in block media recovery
Action: check file number
ORA-19682: file string not in block media recovery context
Action: n/a
ORA-19683: real and backup block size of file string are unequal
Cause: block size changed between backup & real file
Action: use right backup
ORA-19684: block media recovery failed because database is suspended
Cause: Database is suspended, probably by an ALTER SYSTEM SUSPEND statement
Action: Execute ALTER SYSTEM RESUME then retry block media recovery
ORA-19685: SPFILE could not be verified
Cause: Some data blocks for the SPFILE were corrupt in the backup set.
Action: Unless the damage to the backup set can be repaired, the SPFILE cannot be
restored from this backup set.
ORA-19686: SPFILE not restored due to string
Cause: The indicated file could not be restored, because some of its data blocks were
not found in the backup piece.
Action: Unless the damage to the backup set can be repaired, the SPFILE cannot be
restored from this backup set.
ORA-19687: SPFILE not found in backup set
Cause: The SPFILE could not be restored, because it is not in this backup set.
and one or more files named for restoration were not found in the piece. You must
supply the first backup piece of a backup set that contains the requested file.
ORA-19688: control file AUTOBACKUP format(string) for string does not have %F
Cause: control file AUTOBACKUP format must contain %F for the device.
Action: Change control file format using RMAN command CONFIGURE
CONTROLFILE BACKUP FORMAT FOR DEVICE TYPE type TO format.
ORA-19689: cannot have more than one %F in control file AUTOBACKUP
format(string) for string
Cause: control file AUTOBACKUP format contains more than one %F for the device.
Action: Change control file format using RMAN command CONFIGURE
CONTROLFILE BACKUP FORMAT FOR DEVICE TYPE type TO format.
ORA-19690: backup piece release string incompatible with Oracle release string
Cause: The backup piece was created by incompatible software.
Action: Either restart with a compatible software release or create another backup
using the current release.
ORA-19691: string is from different database: id=string, name=string
Cause: The database name or database id in backup piece header does not match the
one in control file.
Action: Supply the correct backup piece belonging to this database.
ORA-19692: missing creation stamp on piece string
Cause: The backup piece doesn't have information about creation stamp.
Action: Supply another backup piece which is created by oracle 9i or later version.
ORA-19693: backup piece string already included
Cause: This backup piece was already specified for inclusion in the restore
conversation. A restore conversation may process only a single instance of a backup
piece.
Action: Remove the specified duplicate backup piece in restore steps and restart the
conversation.
ORA-19500 to ORA-19997 70-19
ORA-19694: some changed blocks were not found in the change tracking file
Cause: A backup or copy found that some changed blocks had not been recorded in
the change tracking file. The details of which files and blocks are affected will be in an
Oracle trace file.
Action: This indicates that there is a problem with the change tracking feature.
Disable change tracking and re-start the backup.
ORA-19695: fixed table X$KRBMSFT has not been populated
Cause: This is an internal error. The fixed table X$KRBMAFT was not populated
using the function DBMS_BACKUP_RESTORE.SEARCHFILES.
ORA-19696: control file not found in backup set
Cause: The control file could not be restored because it is not in this backup set.
ORA-19697: standby control file not found in backup set
Cause: The standby control file could not be restored because it is not in this backup
set.
ORA-19698: string is from different database: id=string, db_name=string
Cause: Catalog failed because the database id in file header does not match the one in
control file.
Action: Supply the correct file belonging to this database.
ORA-19699: cannot make copies with compression enabled
Cause: Datafile copies with compression are not supported.
Action: If the function DBMS_BACKUP_RESTORE.BACKUPPIECECREATE is called
outside RMAN, then the incompatible values are being passed for the parameters
DOCOMPRESS and IMAGCP. If this message occurs during an RMAN job, then this
is an internal error in RMAN, and you should contact Oracle support.
ORA-19700: device type exceeds maximum length of string
Cause: The device type indicated is invalid.
Action: Supply a correct device type and retry the allocation.
ORA-19701: device name exceeds maximum length of string
Cause: The device name indicated is invalid.
Action: Supply a correct device name and retry the allocation.
ORA-19702: device parameter exceeds maximum length of string
ORA-19703: device command string exceeds maximum length of string
Cause: The device command string exceeds maximum length.
Action: Correct the command and retry the operation.
ORA-19704: file name exceeds maximum length of string

Cause: The specified file name, which was a parameter to a copy, backup, or restore
operation, exceeds the maximum file name length for this operating system.
Action: Retry the operation with a shorter file name.
ORA-19705: tag value exceeds maximum length of string characters
Cause: During a backup or copy operation, the user supplied a tag value too long to
fit in the file header.
Action: Supply a shorter tag and retry the operation.
ORA-19706: invalid SCN
Cause: The input SCN is either not a positive integer or too large.
Action: Check the input SCN and make sure it is a valid SCN.
ORA-19707: invalid record block number - string
Cause: The input number is either negative or too large.
Action: Check the input record block number and make sure it is a valid number
clauses in the create database statement.
ORA-19708: log destination exceeds maximum length of string characters
Cause: When starting a restore conversation, the user specified a log restore
destination longer than the port-specific maximum.
Action: Supply a shorter destination and retry the operation.
ORA-19709: numeric parameter must be non-negative integer
Cause: A numeric parameter to an DBMS_BACKUP_RESTORE procedure is negative
or contains a fractional portion.
Action: Supply a valid numeric parameter.
ORA-19710: unsupported character set string
Cause: When the target database is not mounted, RMAN sets the target database
character set to the value specified in the users environment.
Action: Specify a valid character set in the environment. This is usually done via the
NLS_LANG environment variable.
ORA-19711: cannot use RENORMALIZEALLFILENAMES while database is open
Cause: An attempt was made to re-normalize all the file names in the control file
while the database is open.
Action: Close the database before using the RENORMALIZEALLFILENAMES
procedure.
ORA-19712: table name exceeds maximum length of string
Cause: The table name string exceeds maximum length.
Action: Retry the operation with a shorter table name.
ORA-19713: invalid copy number: string
Cause: The copy number is not in a valid range or you have reached maximum limit.
Action: Report the error and other information to support.
ORA-19714: length for generated name longer than string
Cause: The specified format exceeds the maximum length for the piece name.
ORA-19500 to ORA-19997 70-21
Action: Change the format to create shorter piece names.

ORA-19715: invalid format string for generated name
Cause: A restricted format or undefined format was used incorrectly.
Action: Change the format specified in the additional information by removing the
restricted format.
ORA-19716: error processing format string to generate name for backup
Cause: There were errors while processing the format to generate name for backup.
Action: Change the format.
ORA-19717: for non-OMF search the pattern must be specified
Cause: The procedure DBMS_BACKUP_RESTORE.SEARCHFILES was called with an
empty pattern while the parameter OMF was set to FALSE.
Action: Either specify the pattern or set the parameter OMF to TRUE.
ORA-19718: length for command id longer than string
Cause: The specified command id exceeds the maximum length for command id.
Action: Supply a shorter command id and retry the operation.
ORA-19719: length for operation name longer than string
Cause: The specified operation name exceeds the maximum length for operation
name.
Action: Supply a shorter operation name and retry the operation.
ORA-19720: Error occurred when converting an OCI number into an SCN
Cause: This is most likely caused by an invalid SCN number that came from an
external file, such as an export file.
Action: See other errors on the error stack to look for the source of the problem.
ORA-19721: Cannot find datafile with absolute file number string in tablespace
string
Cause: Can not find one of the datafile that should be in the Pluggable Set.
Action: Make sure all datafiles are specified via import command line option or
parameter files.
ORA-19722: datafile string is an incorrect version
Cause: The datafile is an incorrect version. It contains either less or more changes then
the desired version.
Action: Make sure the right datafiles are transported. Make sure the datafile is copied
while its tablespace is read only.
ORA-19723: Cannot recreate plugged in read-only datafile string
Cause: The datafile is plugged in read only. It can not recreated.
Action: Use ALTER DATABASE RENAME FILE command instead.
ORA-19724: snapshot too old: snapshot time is before file string plug-in time
Cause: The snapshot SCN is before the SCN at which the referred datafile is plugged
into the database.
Action: retry the query.
ORA-19725: can not acquire plug-in enqueue

Cause: There maybe another "ALTER DATABASE RESET COMPATIBILITY"
command issued concurrently, preventing this process from acquiring the plug-in
enqueue.
Action: retry the operation.
ORA-19726: cannot plug data [string] at level string into database running at
compatibility level string
Cause: Some of the data in the pluggable set requires a compatibility level higher than
what is currently allowed by the database. The string in square bracket is the name of
the compatibility type associated with the data.
Action: Raise the "compatible" init.ora parameter and retry the operation.
ORA-19727: cannot plug data [string] at level string into database running Oracle
string
Cause: Some of the data in the pluggable set requires a compatibility level higher than
the release level of the Oracle executable. The string in square bracket is the name of
the compatibility type associated with the data.
Action: Upgrade 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 in the partitioned table. One can not exchange the table with the partition in
this case.
Action: Use "alter table move partition" command to move the offending partition, so
that the partition will get a new data object number. Retry the operation then.
ORA-19729: File string is not the initial version of the plugged in datafile
Cause: The file is not the initial version of the plugged in datafile.
Action: Use the correct initial version of the plugged in datafile.
ORA-19730: can not convert offline plugged-in datafile string
Cause: As part of making a tablespace read-write, we need to convert datafiles that
are plugged in read-only. The file must be online.
Action: Online the datafile and retry the operation.
ORA-19731: cannot apply change to unverified plugged-in datafile string
Cause: Recovery was not able to verify the referred datafile according to information
in the control file. Before encountering this change vector for this file, somehow
recovery did not encounter the file conversion redo that is supposed to verify the file.
This may happen due to corrupted or incorrect control file used for media recovery.
Action: Use the correct control file and continue recovery.
ORA-19732: incorrect number of datafiles for tablespace string
Cause: The number of datafiles in the export file for the referred tablespace 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-19500 to ORA-19997 70-23
ORA-19733: COMPATIBLE parameter needs to be string or greater

Cause: The COMPATIBLE initialization parameter is not high enough to allow the
operation. Allowing the command would make the database incompatible with the
release specified by the current COMPATIBLE parameter.
ORA-19734: wrong creation SCN - control file expects converted plugged-in
datafile
Cause: When a tablespace is plugged into a database, the tablespace is initially readonly. Oracle converts the header of the plugged-in datafiles (assign them a new
creation SCN) when the tablespace is first made read-write. This error occurs when
the creation SCN in the file header is different from the creation SCN in the control
file, possibly because this is the initial version of plugged-in datafile.
Action: Either restore the converted datafile or continue recovering the datafile.
ORA-19735: wrong creation SCN - control file expects initial plugged-in datafile
Cause: When a tablespace is plugged into a database, the tablespace is initially readonly. Oracle converts the header of the plugged-in datafiles (assign them a new
creation SCN) when the tablespace is first made read-write. This error occurs when
the creation SCN in the file header is different from the creation SCN in the control
file, possibly because this is the converted datafile.
Action: Either restore the initial version of the plugged-in datafile, or continue
database recovery, which will recover the control file.
ORA-19736: can not plug a tablespace into a database using a different national
character set
Cause: Oracle does not support plugging a tablespace into a database using a
different national character set.
Action: Use import/export or unload/load to move data instead.
ORA-19738: cannot find language information for character set: 'string'
Cause: The compatibility check failed because a character set name that was provided
is not valid.
Action: Correct the character set name and retry.
ORA-19740: text is longer than string
Cause: The specified text exceeds the maximum length for text.
Action: Supply a shorter text and retry the operation.
ORA-19741: string exceeds maximum allowable length of string for parameter
'string'
Cause: The specified string exceeds the maximum allowable length for the parameter
Action: Supply a shorter string for the parameter and retry the operation.
ORA-19742: control file is not a backup control file
Cause: This parameter could not be set because the control file was not a backup
control file.
Action: Do not use this call for this control file.
ORA-19750: change tracking file: 'string'
Cause: This message reports the name of a file involved in other messages.
Action: See associated error messages for a description of the problem.

ORA-19751: could not create the change tracking file
Cause: It was not possible to create the change tracking file.
Action: Check that there is sufficient disk space and no conflicts in file names and try
to enable block change tracking again.
ORA-19752: block change tracking is already enabled
Cause: The ALTER DATABASE ENABLE BLOCK CHANGE TRACKING command
was issued, but block change tracking is already turned on for this database.
Action: None, this is an informative message only.
ORA-19753: error writing to change tracking file
Cause: An I/O error occurred while writing to the change tracking file.
Action: There will be other messages on the error stack that show details of the
problem.
ORA-19754: error reading from change tracking file
Cause: An I/O error occurred while reading from the change tracking file.
problem.
ORA-19755: could not open change tracking file
Cause: The change tracking file could not be opened.
problem.
ORA-19756: corrupt block number string found in change tracking file
Cause: The specified block number is corrupt in the change tracking file.
problem. There will also be a trace file that contains a complete dump of the corrupt
block.
ORA-19757: could not resize change tracking file to string blocks
Cause: An error occurred while trying to change the size of the change tracking file.
problem.
ORA-19758: failed to enable/disable block change tracking: out of SGA memory
Cause: out of SGA memory
Action: Increase SGA and restart the instance.
ORA-19759: block change tracking is not enabled
Cause: A command was entered that requires block change tracking to be enabled,
but block change tracking is not enabled.
Action: None, this is an informative message only.
ORA-19760: error starting change tracking
Cause: Change tracking is enabled, but a problem was encountered while enabling
the change tracking subsystem in this instance. The alert log and the trace file from
the CTWR process will contain more information about the error.
ORA-19500 to ORA-19997 70-25
Action: Examine the trace and alert files. Correct the error if possible, otherwise
disable change tracking.
ORA-19761: block size string is not valid for change tracking file
Cause: While opening the specified change tracking file, it was found that the file
header did not contain a valid logical block size. This probably means that the file is
corrupt.
Action: If the file can be repaired, do so, otherwise disable and re-enable change
tracking to re-initialize the file.
ORA-19762: invalid file type string
Cause: An invalid file type was found in the change tracking file. Some other file was
put in place of the change tracking file, or the file is corrupt.
Action: Disable then re-enable change tracking.
ORA-19763: compatibility version string is higher than maximum allowed: string
Cause: The compatibility version in the change tracking file is greater than what can
be used by the current release of Oracle. This can happen when you upgrade, use
change tracking with a new release, then downgrade.
ORA-19764: database id string does not match database id string in control file
Cause: The change tracking file is not the correct one for this database. This can
happen when the database ID for this database has been changed.
ORA-19765: mount id string does not match mount id string in control file
Cause: The change tracking file does not match the one that was present when this
instance was opened. In RAC, this error is most likely caused by having a change
tracking file that cannot be consistently updated by all instances.
Action: In RAC, ensure that the name specified for the change tracking file truly
represents the same disk location for all nodes in the cluster. Disable then re-enable
change tracking.
ORA-19766: missing CHANGE keyword
Action: Use the correct syntax: ENABLE/DISABLE BLOCK CHANGE TRACKING
ORA-19767: missing TRACKING keyword
ORA-19768: USING clause only valid with ENABLE CHANGE TRACKING
Cause: The USING clause was specified with DISABLE CHANGE TRACKING
Action: Correct the statement.
ORA-19769: missing FILE keyword
ORA-19770: invalid change tracking file name

Cause: The USING clause was specified with ALTER DATABASE ENABLE BLOCK
CHANGE TRACKING, but no file name was given.
Action: Specify the change tracking file name, or omit the USING clause to allow
Oracle to create a default name for the change tracking file.
ORA-19771: cannot rename change tracking file while database is open
Cause: The ALTER DATABASE RENAME FILE command was used to rename the
change tracking file, and the database is open by one or more instances. The database
must be mounted, and not open, to rename the change tracking file.
Action: Close the database and reissue the command.
ORA-19772: change tracking file name exceeds limit of string characters
Cause: The name specified for the change tracking file is too long.
Action: Specify a shorter change tracking file name.
ORA-19773: must specify change tracking file name
Cause: No file name was specified with the ALTER DATABASE ENABLE CHANGE
TRACKING command, and the DB_CREATE_FILE_DEST parameter was not set.
Action: Either specify a file name, or set the DB_CREATE_FILE_DEST parameter.
ORA-19776: PROXY restore to ASM disk group "string" is not supported.
Cause: An attempt was made to proxy restore a file to ASM disk group using RMAN
command. This is not supported.
Action: Use a different file name and reissue RMAN command.
ORA-19777: ASM file string cannot be proxy backed up.
Cause: An attempt was made to proxy backup a ASM file. This is not supported.
Action: Use a different file name and reissue RMAN command.
ORA-19779: could not obtain resilvering status for change tracking file
Cause: An error occurred while obtaining the mirror resilvering status of the change
tracking file.
Action: Refer to other error messages shown for additional details of the problem.
ORA-19780: Active Data Guard option not enabled
Cause: Change tracking at a standby database required the Active Data Guard option.
Action: Enable the Active Data Guard option.
ORA-19800: Unable to initialize Oracle Managed Destination
Cause: The name given for an Oracle managed files destination cannot be initialized.
Action: Check previous error messages for the reason Oracle was unable to initialize
destination. Take corrective action, if possible, and retry the command or use a
different name for destination.
ORA-19801: initialization parameter DB_RECOVERY_FILE_DEST is not set
Cause: An attempt was made to create a file in DB_RECOVERY_FILE_DEST when
DB_RECOVERY_FILE_DEST was not set. There are number of possible causes of this
error, including: 1) A LOG_ARCHIVE_DEST_n parameter was specified using a
LOCATION attribute whose value was DB_RECOVERY_FILE_DEST and an archived
log file creation was attempted. 2) STANDBY_ARCHIVE_DEST parameter was
ORA-19500 to ORA-19997 70-27
specified using a LOCATION attribute whose value was

DB_RECOVERY_FILE_DEST and an archived log file creation was attempted.
Action: Specify a valid destination for DB_RECOVERY_FILE_DEST in initialization
parameter file or with the ALTER SYSTEM SET command.
ORA-19802: cannot use DB_RECOVERY_FILE_DEST without
DB_RECOVERY_FILE_DEST_SIZE
Cause: There are two possible cause for this error: 1) The
DB_RECOVERY_FILE_DEST parameter was in use when no
DB_RECOVERY_FILE_DEST_SIZE parameter was encountered while fetching
initialization parameter. 2) An attempt was made to set DB_RECOVERY_FILE_DEST
with the ALTER SYSTEM command when no DB_RECOVERY_FILE_DEST_SIZE was
in use.
Action: Correct the dependency parameter definitions and retry the command.
ORA-19803: Parameter DB_RECOVERY_FILE_DEST_SIZE is out of range (1 string)
Cause: Parameter DB_RECOVERY_FILE_DEST_SIZE specified was not valid.
Action: Specify a valid number within the range.
ORA-19804: cannot reclaim string bytes disk space from string limit
Cause: Oracle cannot reclaim disk space of specified bytes from the
DB_RECOVERY_FILE_DEST_SIZE limit.
Action: There are five possible solutions: 1) Take frequent backup of recovery area
using RMAN. 2) Consider changing RMAN retention policy. 3) Consider changing
RMAN archived log deletion policy. 4) Add disk space and increase
DB_RECOVERY_FILE_DEST_SIZE. 5) Delete files from recovery area using RMAN.
ORA-19805: RECID string of string was deleted to reclaim disk space
Cause: The file described by the record in control file was deleted in order to reclaim
disk space from recovery area for other operations.
Action: Wait and try again.
ORA-19806: cannot make duplex backups in recovery area
Cause: Duplex backup to recovery area is not supported.
Action: Remove duplex option and try again.
ORA-19808: recovery destination parameter mismatch
Cause: The value of parameters DB_RECOVERY_FILE_DEST and
DB_RECOVERY_FILE_DEST_SIZE must be same in all instances. instance. All
databases must have same recovery destination parameters.
Action: Check DB_RECOVERY_FILE_DEST and DB_RECOVERY_FILE_DEST_SIZE
values in all instances.
ORA-19809: limit exceeded for recovery files
Cause: The limit for recovery files specified by the DB_RECOVERY_FILE_DEST_SIZE
was exceeded.
Action: There are five possible solutions: 1) Take frequent backup of recovery area
using RMAN. 2) Consider changing RMAN retention policy. 3) Consider changing
RMAN archived log deletion policy. 4) Add disk space and increase
DB_RECOVERY_FILE_DEST_SIZE. 5) Delete files from recovery area using RMAN.
ORA-19810: Cannot create temporary control file string in

DB_RECOVERY_FILE_DEST
Cause: An attempt was made to create a control file for a temporary purpose in
DB_RECOVERY_FILE_DEST.
Action: Retry the operation with a new file name.
ORA-19811: cannot have files in DB_RECOVERY_FILE_DEST with keep attributes
Cause: An attempt was made to 1) Create a backup piece or image copy in the
recovery area with KEEP option. 2) Update the KEEP attributes of an existing backup
piece or image copy in the recovery area.
Action: Reissue RMAN command without KEEP options.
ORA-19812: cannot use string without DB_RECOVERY_FILE_DEST
Cause: There are three possible cause for this error: 1) The indicated parameter was in
use when no DB_RECOVERY_FILE_DEST parameter was encountered while fetching
the initialization parameter. 2) An attempt was made to set indicated the parameter
with the ALTER SYSTEM command when no DB_RECOVERY_FILE_DEST was in
use. 3) An attempt was made to clear DB_RECOVERY_FILE_DEST with the ALTER
SYSTEM command when the indicated parameter was in use.
ORA-19813: cannot have unavailable file string in DB_RECOVERY_FILE_DEST
Cause: An attempt was made to change a backup piece or image copy in recovery
area to UNAVAILABLE.
Action: Correct and resubmit the RMAN command. Do not use messages 19814; it is
used for simulating crash.
ORA-19815: WARNING: string of string bytes is string%% used, and has string
remaining bytes available.
Cause: DB_RECOVERY_FILE_DEST is running out of disk space.
Action: One of the following: 1. Add disk space and increase
DB_RECOVERY_FILE_DEST_SIZE. 2. Backup files to tertiary device using RMAN. 3.
Consider changing RMAN retention policy. 4. Consider changing RMAN archived
log deletion policy. 5. Delete files from recovery area using RMAN.
ORA-19816: WARNING: Files may exist in string that are not known to database.
Cause: One of the following events caused this: 1. A database crash happened during
file creation. 2. A backup control file was restored. 3. The control file was re-created. 4.
DB_RECOVERY_FILE_DEST has previously been enabled and then disabled.
Action: Use RMAN command CATALOG RECOVERY AREA to re-catalog any such
files. If the file header is corrupted, then delete those files using an OS utility. Do not
use messages 19817; it is used for simulating lock failure Do not use messages 19818;
it is used for space reclamation before backup Do not use messages 19819; it is used to
disable clearing file name
ORA-19820: database must be in NOARCHIVELOG mode to disable logging
Cause: Logging was disabled when ARCHIVELOG mode was used.
Action: Execute ALTER DATABASE NOARCHIVELOG in mount state.
ORA-19821: an intentionally corrupt log file was found
Cause: A log file that was intentionally corrupt for testing or benchmarking purposes
was found and failed the operation.
ORA-19500 to ORA-19997 70-29
Action: Remove such log files and retry or use the NOARCHIVELOG option if
possible.
ORA-19830: error from target database: \nstring
Cause: This error should be followed by other errors indicating the cause of the
problem.
ORA-19831: incompatible string.string.string.string DBMS_BACKUP_RESTORE
package: string.string.string.string required
Cause: This version of database was incompatible with the the indicated
DBMS_BACKUP_RESTORE package installed in the database.
Action: If the database has been upgraded from an earlier version, ensure that the
catxxxx.sql script has been run successfully. Re-install dbmsbkrs.sql and prvtbkrs.plb
if necessary.
ORA-19836: cannot use passphrase encryption for this backup
Cause: Passphrase encryption was attempted for a backup that contains encrypted
tablespaces and uses compression.
Action: Do not use passphrase encryption for this backup. Use transparent walletbased encryption instead.
ORA-19837: invalid blocksize string in backup piece header
Cause: The blocksize of the backup piece obtained from the header was invalid.
Action: The backup piece is corrupted, a different backup piece should be used for
restore.
ORA-19838: Cannot use this control file to open database
Cause: This control file was restored by a DUPLICATE operation used only to restore
and recover the datafiles of the new database. It is not meant to be used for opening
the database, as allowing so might corrupt datafiles or online redo logs of the target
database or both.
Action: Re-create control file manually specifying all names of datafiles and online
redo logs. Do not forget to use NID to change the name or DBID or both of the new
database.
ORA-19839: snapshot datafile checkpoint time is greater than snapshot time
Cause: The snapshot time which was specified when starting the recovery less than
data file's checkpoint time. The snapshot recovery is only possible with data file's
whose checkpoint time is less than snapshot time.
Action: Restore the data file's associated for the specified snapshot time or specify the
correct snapshot time associated with the data file.
ORA-19840: SNAPSHOT TIME recovery is not enabled
Cause: An attempt was made to use SNAPSHOT TIME recovery. But, the feature was
not enabled.
Action: Contact Oracle Support Services to enable snapshot time recovery and then
retry the command.
ORA-19841: Cross-platform backups require COMPATIBLE string or greater
Cause: An attempt to create a cross-platform backup was made but the
COMPATIBLE parameter was not set to a high enough value to allow this.
Action: Do not attempt to use this functionality or raise the compatibility level.
ORA-19842: The current database incarnation changed during backup
Cause: The backup failed because the current database incarnation was changed
during the backup. One of the following events caused this incarnation change: - The
database was opened using ALTER DATABASE OPEN RESETLOGS statement. RMAN command RESET DATABASE TO INCARNATION was issued. - If this
happened on physical standby database, then redo apply has applied redo data from
a new database incarnation.
Action: Retry the backup.
ORA-19843: Cannot obtain datafile name for datafile string
Cause: While trying to obtain the file enqueue for the datafile the datafile name could
not be obtained.
Action: Examine the trace and alert files for possible causes. Fix underlying problem
before attempting command again.
ORA-19844: database ID is from different database: ID=string
Cause: The database ID on the remote site did not match the ID of the target database.
This is most likely caused by a wrong service name for the remote connection.
Action: Supply the correct service name and retry the command.
ORA-19845: error in string while communicating with remote database server
Cause: An error occurred while initiating backup on remote database server for
network restore. Additional error messages will be issued to describe the failure.
ORA-19846: cannot read header of datafile string from remote site
Cause: Unable to read the file header from remote site.
Action: Make sure the data file is accessible on remote site and retry the command.
ORA-19847: cannot read header of control file from remote site
Cause: Could not read the control file header from the remote site.
Action: Make sure the database is mounted on the remote site and retry the
command.
ORA-19848: cross-platform backup piece requires COMPATIBLE string or greater
Cause: An attempt was made to perform a cross-platform operation from a backup
piece created with a higher compatibility than the current COMPATIBLE parameter.
Action: Raise the compatibility level or do not attempt a cross-platform restore from
this backup piece.
ORA-19849: error while reading backup piece from service string
problem.
Action: See other errors actions.
ORA-19850: backup piece constructed from service string is corrupt
Cause: This error indicates that the backup piece that was constructed from the
service is corrupt.
Action: See alert log for details of the corruption. Fix the corruption and retry the
command.
ORA-19500 to ORA-19997 70-31
ORA-19851: OS error while managing auxiliary database string

Cause: An OS error was received while managing the automatic auxiliary instance.
ORA-19852: error creating services for auxiliary instance string (error string)
Cause: An error was received while managing the services of the auxiliary instance.
ORA-19853: error preparing auxiliary instance string (error string)
Cause: An error was received while managing the automatic auxiliary instance.
ORA-19854: error obtaining connect string from target
Cause: Could not obtain the connect string from the target database
ORA-19860: piece validation cannot be performed more than once
Cause: The user attempted to validate a list of backup pieces more than once.
Validation may only be performed once for a given validation conversation.
Action: Do not attempt to validate the pieces more than once.
ORA-19861: additional backup pieces cannot be validated in this conversation
Cause: The user tried to add new pieces to the list of files being validated after the
validation had already been performed. In a validation conversation, the list can only
be validated once.
Action: Add all the backup pieces to the list before validating, or start a new
validation conversation for the remaining pieces.
ORA-19862: backup pieces must be validated before accessing results
Cause: The user tried to get validation results for backup pieces before the pieces
were actually validated.
Action: Validate the pieces before trying to access the results.
ORA-19863: device block size string is larger than max allowed: string
Cause: The user specified a device BLKSIZE that is larger than the device BLKSIZE
specified during compressed backup.
Action: Change the device BLKSIZE to be smaller than the maximum allowed.
ORA-19864: string
ORA-19865: Backup piece string has no data
Cause: No data was returned for the specified backup piece.
Action: This normally indicates a problem with the media management software
which is linked with Oracle to provide backup and restore services. Contact the
media management software vendor.
ORA-19866: error writing file header for datafile string
Cause: During a block recovery, the header of the datafile could not be updated.
ORA-19867: backup piece string is from a different container identifier string; data
file string
Cause: This backup piece container identifier did not match the supplied data file
container identifier.
Action: Retry the command with the correct backup piece or the correct data file.
ORA-19870: error while restoring backup piece string
problem.
Action: See other errors actions.
ORA-19872: Unexpected end of file at block string while decompressing backup
piece string
Cause: While reading a compressed backup piece, RMAN received an end-of-file
without finding the end-of-compression stream.
Action: This is most likely caused by a corrupted backup piece. Consider using a
different backup piece for restore.
ORA-19873: cannot apply this backup section to file string
Cause: RMAN cannot restore a multi-section backup to the indicated file, because this
section is not a backup of this file, or the file was not prepared correctly for this
restore.
Action: If this error occurs while running RMAN, then it is an internal error and you
should contact Oracle support.
ORA-19874: cannot finish multisection restore or copy to file string
Cause: During a multisection restore or copy, the file being restored was not a file in
which a multisection restore or copy was in progress.
Action: If this error occurs while running RMAN, then it was an internal error and
you should contact Oracle Support Services.
ORA-19875: multisection restore or copy not complete for file string
Cause: While completing a multisection restore or copy, it was found that all required
sections for this file were not correctly applied.
Action: If this error occurs while running RMAN, then it is an internal error and you
should contact Oracle Support Services.
ORA-19880: Corrupted space header for datafile string, block string
Cause: When reading the space header block to use Unused Block Optimization for
the backup of the datafile, the space header block had corrupted information.
Action: The corrupt space header must be fixed before Unused Block Optimization
can be used for this file. Note that you should fix the corruption in any case because it
will affect the availability of the data in the file, beyond just taking backups.
ORA-19881: Corrupted space bitmap for datafile string, block string
Cause: When reading a space bitmap block to use Unused Block Optimization for the
backup of the datafile, the space bitmap block had corrupted information.
Action: The corrupt space bitmap must be fixed before Unused Block Optimization
can be used for this file. Note that you should fix the corruption in any case because it
will affect the availability of the data in the file, beyond just taking backups.
ORA-19500 to ORA-19997 70-33
ORA-19882: datafile string checkpoint string is ahead of space bitmap datafile

string checkpoint string
Cause: When checkpointing the datafile containing the space bitmaps for the datafile
being backed up in order to use Unused Block Optimization, the checkpoint of the
datafile containing the space bitmaps did not advance.
Action: Examine the trace and alert files for possible causes. Fix underlying problem
to use Unused Block Optimization for datafile's backup.
ORA-19884: datafile string is unable to use Unused Block Optimization because
tablespace has been dropped
Cause: When attempting to find information about datafile that holds bitmaps of
migrated tablespace, the tablespace was found to have been dropped.
Action: None. This is an informational message.
ORA-19899: missing incarnation information
Cause: Media recovery stopped because information of one or more ancestor
incarnations of recovery target incarnation was not available.
Action: Register logs from the missing incarnations and retry recovery.
ORA-19900: RESETLOGS must be specified after recovery to new incarnation
Cause: Recovery was done to an incarnation after changing the destination
incarnation using RMAN's RESET DATABASE command.
Action: Open the database with the RESETLOGS option.
ORA-19901: database needs more recovery to create new incarnation
Cause: Recovery was done to an incarnation after changing the destination
incarnation using RMAN's RESET DATABASE command, but one or more of the
recovered datafiles still belongs to the parent incarnation. This usually happens when
recovery is ended before any logs from the desired incarnation have been applied.
Action: Continue recovery.
ORA-19902: incarnation key string not found
Cause: The specified incarnation was not found in the control file.
Action: Resubmit request with known incarnation key. To see which incarnations are
available for this target database, query V$DATABASE_INCARNATION or use
RMAN's LIST INCARNATION command.
ORA-19903: test recovery not allowed when recovering to new incarnation
Cause: Either a new incarnation was set using RMAN's RESET DATABASE command
for a control file that was CURRENT, or the control file is from a prior incarnation. As
recovery to a new incarnation requires changing the control file, test recovery is not
allowed.
Action: Perform actual recovery or RESET DATABASE to incarnation that was last
opened using the control file to do test recovery.
ORA-19904: test recovery not allowed for datafile string
Cause: The specified datafile has been restored from a backup that was taken before
the last RESETLOGS. Recovering this datafile will require a file header update that is
incompatible with test recovery.
Action: Perform actual recovery.
ORA-19905: log_archive_format must contain %string, %string and %%r

Cause: log_archive_format is missing a mandatory format element. Starting with
Oracle 10i, archived log file names must contain each of the elements %s(sequence),
%t(thread), and %r(RESETLOGS ID) to ensure that all archived log file names are
unique.
Action: Add the missing format elements to log_archive_format.
ORA-19906: recovery target incarnation changed during recovery
Cause: While a media recovery was active, a new incarnation was detected by the
server due to inspection or cataloging of archived logs or backup files.
Action: If you want recovery to use the new incarnation, restart recovery. This is the
most common action on a standby database when RESETLOGS is done in primary. If
you do not want recovery to use the new incarnation, change the recovery destination
using RMAN's RESET DATABASE TO INCARNATION <incarnation#> command.
To see which incarnations are available for this target database, query V
$DATABASE_INCARNATION or use RMAN's LIST INCARNATION command.
ORA-19907: recovery time or SCN does not belong to recovered incarnation
Cause: A point-in-time recovery to an SCN or time stamp prior to the last
RESETLOGS was requested.
Action: Either change the specified recovery time/SCN, or change the recovery
destination using RMAN's RESET DATABASE command.
ORA-19908: datafile string has invalid checkpoint
Cause: The specified datafile has an invalid checkpoint.
Action: Restore the datafile from a backup.
ORA-19909: datafile string belongs to an orphan incarnation
Cause: Either the specified datafile was restored from a backup that was taken during
a period of time that has already been discarded by a RESETLOGS operation, or
Oracle cannot identify which database incarnation the file belongs to. The alert log
contains more information.
Action: Restore a backup of this file that belongs to either the current or a prior
incarnation of the database. If you are using RMAN to restore, RMAN will
automatically select a correct backup.
ORA-19910: can not change recovery target incarnation in control file
Cause: The RESET DATABASE TO INCARNATION command was used while the
database is open. This is not allowed.
Action: Close the database then re-issue the command.
ORA-19911: datafile string contains future changes at the incarnation boundary
Cause: The file did not hit end backup marker redo during recovery at the incarnation
boundary, hence may contain changes discarded by new incarnation.
Action: Use older backup of the file and then re-issue the command.
ORA-19912: cannot recover to target incarnation string
Cause: The control file is not in the recovery path of the target incarnation, and does
not contain enough information as to how to recover to the target incarnation.
Action: Restore the latest control file from the target incarnation and retry.
ORA-19500 to ORA-19997 70-35
ORA-19913: unable to decrypt backup

Cause: A backup piece could not be decrypted. This message is accompanied with
another message that indicates the name of the encrypted backup that could not be
restored. The reason could be either that an invalid password was entered, or that,
when using transparent decryption, the database external security device is not open.
Action: If password-based restore was enabled for this backup, then supply the
correct password using the RMAN SET DECRYPTION command. If transparent
restore was enabled for this backup, then ensure that the database external security
device is open.
ORA-19914: unable to encrypt backup
Cause: RMAN could not create an encrypted backup. This message will be
accompanied by other messages that give more details about why the encrypted
backup could not be created. The most common reason for this message is that you
are trying to create a backup that can be transparently decrypted, and the database
external security device is not open.
Action: If the external security device is not open, then open it. If the external security
device is not configured, then the only type of encrypted backup that you can create is
a password-based backup.
ORA-19915: unable to encrypt pre-10.2 files
Cause: An RMAN encrypted backup was requested, but this backup includes one or
more archived logs that were generated by an older release of Oracle. These archived
logs cannot be encrypted.
Action: Back up the older logs without encryption. Logs created with Oracle release
10.2 and greater can be encrypted.
ORA-19919: encrypted backups to tertiary storage require Oracle Secure Backup
Cause: RMAN was configured to create encrypted backups, but the channel is neither
a DISK channel nor an Oracle Secure Backup channel.
Action: Allocate a DISK channel or an Oracle Secure Backup channel to use backup
encryption.
ORA-19920: RMAN does not support PKI-based master key for encryption.
Cause: An attempt was made to use Oracle public key infrastructure (PKI) based
master key algorithm. RMAN only supports Advanced Encryption Standard (AES)
based encryption.
Action: Use AES based encryption.
ORA-19921: maximum number of string rows exceeded
Cause: The maximum number of rows in the V$RMAN_STATUS or V
$RMAN_OUTPUT table has been exceeded.
Action: Close some of existing and unused RMAN connections and sessions.
ORA-19922: there is no parent row with id string and level string
Cause: RMAN tried to add a new V$RMAN_STATUS row, but the parent row did not
exist.
Action: This is an internal error. Contact Oracle Support.
ORA-19923: the session for row with id string is not active
Cause: RMAN tried to update an V$RMAN_STATUS row but the process which
owns this row died.

ORA-19924: there are no row with id string
Cause: RMAN tried to update an V$RMAN_STATUS row, but the row don't exist.
ORA-19925: Internal error while cleaning memory used by V$RMAN_STATUS
view
ORA-19926: Database cannot be converted at this time
Cause: Another CONVERT DATABASE operation is already in progress.
Action: Retry CONVERT DATABASE command later.
ORA-19927: CONVERT DATABASE operation cannot proceed
Cause: An error occurred earlier during CONVERT DATABASE operation.
Action: Retry CONVERT DATABASE command.
ORA-19928: CONVERT of data files with undo segments between different endian
is not supported.
Cause: Conversion of data files with undo segments was not supported between
endianess. The only time that data files with undo segments can be converted is
between the same endianess as part of convert database. Convert database between
different endian is not supported.
Action: Do not attempt to convert data files with undo segments between different
endian.
ORA-19929: no archive log registered
Cause: An error occurred during ALTER DATABASE RECOVER with the FORCE
START AT option because there were no archive logs registered in the control file
covering the specified start SCN or time.
Action: Register archive logs covering the specified SCN or time.
ORA-19930: file string has invalid checkpoint SCN string
Cause: When opening the file to be placed in a copy or backup set, to be inspected, the
file header was not recognized as a valid header because it contained a invalid
checkpoint SCN. The indicated file cannot be processed.
Action: Ensure that the correct files are being specified for the catalog or backup
operation.
ORA-19931: file string has invalid creation SCN string
Cause: When opening the file to be placed in a copy or backup set, to be inspected, the
file header was not recognized as a valid header because it contained a invalid
creation SCN. The indicated file cannot be processed.
Action: Ensure that the correct files are being specified for the catalog or backup
operation.
ORA-19932: control file is not clone, standby or backup
Cause: The operation failed because the control file was not mounted as clone,
standby or backup.
Action: Mount the database as clone, standby or backup and retry.
ORA-19500 to ORA-19997 70-37
ORA-19933: catalog backup piece string of data pump dump file is not supported
Cause: This backup piece contained data pump dump file. Cataloging such a backup
piece is not supported.
Action: Do not request to catalog data pump dump file backup piece.
ORA-19934: cannot validate block 0
Cause: An attempt was made to validate block 0 of a datafile.
Action: Do not specify block 0 for validation.
ORA-19936: some tablespaces were not found in backup set
Cause: Some tablespaces that were specified for restoration were not found in the
backup set directory. Message 19937 is issued for each file that was not found.
Action: See the instructions for message 19937.
ORA-19937: tablespace string was not found in backup set
Cause: The indicated tablespace could not be restored because it was not in this
backup set.
and one or more tablespaces named for restoration are not found. The restore
conversation is still active, but no data has been read and you must supply the first
backup piece of a backup set that contains all of the requested files or tablespaces or
both.
ORA-19938: Data Pump dump file backup requires COMPATIBLE string or greater
Cause: Data Pump dump file backup requested but COMPATIBLE did not allow it.
Action: Do not request dump file backup or set COMPATIBLE to minimum value and
retry backup.
ORA-19939: Data Pump dump file can only be included in a cross-platform backup
Cause: Data Pump dump file backup requested but the backup conversation is not a
cross-platform conversation.
Action: Start a new cross-platform backup conversation or do not include a Data
Pump dump file.
ORA-19940: cannot use cross-platform backups to convert whole database to
different endianess
Cause: Cross-platform backups or restores of whole database between different
endianess was requested but it is not supported.
Action: Revise the specified platforms for conversion before retrying the command.
ORA-19941: invalid blocksize in cross-platform datafile string
Cause: Blocksize in header of datafile copy being converted at target was invalid.
Either datafile has not been made read/write with compatibility 10.0 or greater at
source database or datafile copy is corrupted.
Action: Make a new datafile copy taken after tablespace has been made read/write
with compatibility 10.0 at source database and retry conversion.
ORA-19942: datafile copy string not created with compatibility 10.0 or greater
Cause: The specified datafile copy to be converted at the target was not produced
after making the tablespace in read/write mode with compatibility 10.0 or greater at
the source database.
Action: Make a new datafile copy taken after tablespace has been made read/write
with compatibility 10.0 at source database and retry conversion.
ORA-19943: Data Pump dump file not found in backup set
Cause: The Data Pump dump file could not be restored because it was not in this
backup set.
and the Data Pump dump file is not found in the piece. You must supply the first
backup piece of a backup set that contains the requested file.
ORA-19944: Specified platform: 'string' does not match piece header platform:
'string'
Cause: The backup piece did not belong to the platform specified in FROM
PLATFORM.
Action: Retry the restore using the correct FROM PLATFORM or without specifying
FROM PLATFORM at all.
ORA-19945: file string already included to be restored to string
Cause: This file was already specified for inclusion in this restore conversation. The
restore conversation may process only a single instance of a datafile.
Action: No action required. The conversation is still active and more files can be
specified.
ORA-19946: Cannot determine block size of backup piece 'string' (string)
Cause: It was not possible to determine the cross-platform transportable backup piece
block size.
ORA-19947: Invalid block size string in backup piece 'string' from specified
platform 'string'
Cause: The block size obtained from the backup piece using the specified platform
was not valid. Either the piece is corrupted or the specified platform is incorrect.
Action: Retry the restore using the correct FROM PLATFORM clause.
ORA-19948: Backup piece does not contain a cross-platform datafile backup,
reason=string
Cause: A cross-platform transportable restore was specified but the backup piece was
not produced with the correct command.
Action: Produce a cross-platform transportable backup piece by using BACKUP ... TO
PLATFORM and retry the restore.
ORA-19949: Specified platform: 'string' has different endianess than piece 'string',
cannot read
Cause: The backup piece had a different endianess than the platform specified in
FROM PLATFORM.
Action: Retry the restore using the correct FROM PLATFORM or without specifying
FROM PLATFORM at all.
ORA-19950: tablespace string already included to be restored
Cause: This tablespace was already specified for inclusion in this restore conversation.
ORA-19500 to ORA-19997 70-39
Action: No action required. The conversation is still active and more tablespaces or
files or both can be specified. The restore conversation may process only a single
instance of a tablespace.
ORA-19951: cannot modify control file until DBNEWID is completed
Cause: An operation requiring to modify the control file was attempted, but a NID
change is in progress.
Action: Wait until NID completes before attempting the operation.
ORA-19952: database should be mounted exclusively
Cause: The database was started in parallel mode. To change the DBID, the database
must be mounted exclusively.
Action: Shut down the database and start it in exclusive mode.
ORA-19953: database should not be open
Cause: The database was open. To change the DBID, the database must be mounted
exclusively.
Action: Shut down the database and mount it in exclusive mode.
ORA-19954: control file is not current
Cause: The operation failed because a non-current, non-standby control file was
mounted.
Action: Make the control file current and retry.
ORA-19955: only one open thread is allowed to change the DBID
Cause: The operation failed because there were active threads in the database. The
most likely cause is that the database crashed the last time it was shut down.
Action: Ensure that all threads are closed before retrying the operation. Start and
open the database to perform crash recovery, then shut down with the NORMAL or
IMMEDIATE options to close it cleanly. Finally, try running the utility again.
ORA-19956: database should have no offline immediate datafiles
Cause: The operation failed because the database had one or more datafiles that were
in OFFLINE IMMEDIATE mode.
ORA-19957: database should have no datafiles in unknown state
Cause: The operation failed because the database had one or more datafiles that were
in an unknown state.
ORA-19958: potential deadlock involving DIAG process
Cause: DIAG requested a control file operation that may lead to a deadlock
Action: Try last operation later when the control file is released
ORA-19959: DBNEWID utility only allowed in CDB$ROOT
Cause: An attempt was made to use the DBNEWID utility in a pluggable database.
Action: Connect to CDB$ROOT and retry the command.
ORA-19960: Internal use only
Cause: NID usage
Action: None
ORA-19961: compression algorithm string requires advanced compression option to

be enabled
Cause: Requested compression algorithm in initialization parameter or by RMAN
configuration requires that the advanced compression option be enabled and it was
not.
Action: Change initialization parameter advanced_compression_option_usable to
true or change RMAN configurations and retry the operation.
ORA-19962: compression algorithm string is not valid with release string
Cause: Algorithm in initialization parameter requires a lower compatibility that is
currently set.
Action: Change algorithm in initialization parameter file or lower compatibility.
ORA-19963: error getting logical block size of file string
Cause: Error occurred when querying the logical block size of a file.
Action: None
ORA-19965: ALTER DATABASE RECOVER STANDBY TABLESPACE has been
deprecated
Cause: The STANDBY TABLESPACE clause of the ALTER DATABASE RECOVER
statement (partial_database_recovery clause) has been deprecated.
Action: If you want to recover the standby database to a consistent point, but no
further, use the statement ALTER DATABASE RECOVER MANAGED STANDBY
DATABASE UNTIL CONSISTENT.
ORA-19966: ALTER DATABASE RECOVER STANDBY DATAFILE has been
deprecated
Cause: The STANDBY DATAFILE clause of the ALTER DATABASE RECOVER
statement (partial_database_recovery clause) has been deprecated.
Action: If you want to recover the standby database to a consistent point, but no
further, use the statement ALTER DATABASE RECOVER MANAGED STANDBY
DATABASE UNTIL CONSISTENT.
ORA-19970: multi-instance standby role transition in progress
Cause: ALTER DATABASE MOUNT failed because a multi-instance standby role
transition was in progress.
Action: Retry after the multi-instance standby role transition finishes.
ORA-19971: event 10875 or 10879 is set
Cause: Event 10875 or event 10879 was set which prevented the operation from
completing with multiple instances running in Oracle RAC.
Action: Shutdown all but one instance, then retry the command.
ORA-19972: ALTER DATABASE RECOVER TO LOGICAL requires one instance
left
Cause: ALTER DATABASE RECOVER TO LOGICAL required only one instance to
be left running.
ORA-19500 to ORA-19997 70-41
ORA-19973: flashback database is not enabled

Cause: Physical standby transition to snapshot standby required only one instance left
running if flashback database logging was not enabled.
ORA-19974: database name has changed
Cause: Physical standby role transition required only one instance left running if
database name was changed and flashback database logging was enabled.
ORA-19975: database must not be started in any other instance
Cause: The physical standby role transition command failed because a certain
condition required the database to be mounted in this instance and not started in any
other instance.
Action: See associated error message for detailed explanation.
ORA-19976: a concurrent standby role transition in progress
Cause: The standby role transition operation failed because a concurrent standby role
transition was already in progress.
Action: None
ORA-19980: cannot open Data Pump dump file string
Cause: When attempting to open the specified dump file, an error was received.
Action: Verify that the specified dump file exists and is accessible.
ORA-19981: cannot read header of Data Pump dump file string
Cause: When attempting to read the header of the specified dump file, an error was
received.
Action: Verify that the specified dump file is complete.
ORA-19982: file string is not a Data Pump dump file
Cause: The specified dump file did not contain data created by Data Pump.
Action: Verify that the specifed dump file is really a file created by Data Pump.
ORA-19983: Data Pump dump file could not be verified
Cause: Some data blocks for the Data Pump dump file were corrupt in the backup set.
Action: Unless the damage to the backup set can be repaired, the Data Pump dump
file cannot be restored from this backup set.
ORA-19984: Data Pump dump file restore requires COMPATIBLE string or greater
Cause: Data Pump dump file restore requested but COMPATIBLE did not allow it.
Action: Do not request dump file backup or set COMPATIBLE to minimum value and
retry backup.
ORA-19985: Data Pump dump file can only be requested in a cross-platform restore
Cause: Data Pump dump file restore requested but the restore conversation is not a
cross-platform conversation.
Action: Start a new cross-platform restore conversation or do not include a Data
Pump dump file.
ORA-19986: archived log backup piece found for cross-platform backup

Cause: A cross-platform backup was requested for a backup piece that contained
archived logs.
Action: Specify a datafile backup piece for cross-platform processing.
ORA-19987: unknown platform ID string
Cause: The platform ID obtained from a cross-platform backup was incorrect.
Action: Verify that the platform specified in the FROM PLATFORM clause is correct.
ORA-19988: must specify FROM PLATFORM for cross-platform restore of backup
sets with pre-12.1 compatibility
Cause: A cross-platform restore was requested from a backup piece created with
pre-12.1 compatibility without providing the platform name that created it.
Action: Reissue the command including the FROM PLATFORM clause.
ORA-19990: restore from cross-platform encrypted backup with different endianess
is not supported
Cause: A cross-platform restore was requested from an encrypted backup set with
different endianess from the current platform.
Action: Specify a non-encrypted backup set from which to perform the restore.
ORA-19991: cross-platform backup of encrypted backups to different endianess is
not supported
Cause: A cross-platform backup was requested for an encrypted backup to a different
endianess from the current platform.
Action: Do not specify an encrypted backup or specify the same endian platform.
ORA-19992: cross-platform backup of encrypted backup piece with different
endianess is not supported
Cause: A cross-platform backup was requested for an encrypted backup piece with
different endianess from the current platform.
Action: Specify a backup piece without encryption to the backup.
ORA-19993: must specify FROM PLATFORM for cross-platform backup of backup
pieces with compatibility set prior to 12.1
Cause: A cross-platform backup was requested for a backup piece created with
compatibility prior to 12.1 without providing the platform name that created it.
Action: Reissue the command including the FROM PLATFORM clause.
ORA-19994: cross-platform backup of compressed backups to different endianess
is not supported
Cause: A cross-platform backup was requested for a compressed backup to a different
endianess from the current platform.
Action: Do not specify a compressed backup or specify the same endian platform.
ORA-19995: controlfile cannot be restored from a cross-platform backup with
different endianess
Cause: A restore of the controlfile was requested from a cross-platform backup, but
the backup did not have the same endianess and restore was not possible.
Action: Do not attempt to restore a controlfile from a cross-platform backup set.
ORA-19500 to ORA-19997 70-43
ORA-19996: cross-platform backup of backup pieces with pre-10.2 compatibility is

not supported
Cause: A cross-platform backup was requested for a backup created with pre-10.2
compatibility.
Action: Do not attempt to perform cross-platform backup of backups created with
with pre-10.2 compatibility.
ORA-19997: backup pieces prior to 10.2 cannot be operated for cross-platform
Cause: A cross-platform operation was requested for a backup created with pre-10.2
compatibility.
Action: Do not attempt to perform the cross-platform operation of backups created
with pre-10.2 compatibility. 19998 is used for event
71
ORA-19999 to ORA-24279
ORA-19999: skip_row procedure was called
Cause: The skip_row procedure was called which raises this error
Action: Skip_row should only be called within a trigger or a procedure called by a
trigger.
ORA-20000: string
Cause: The stored procedure 'raise_application_error' was called which causes this
error to be generated.
Action: Correct the problem as described in the error message or contact the
application administrator or DBA for more information.
ORA-21000: error number argument to raise_application_error of stringstring is out
of range
ORA-21001: error number argument to raise_system_error of stringstring is out of
range
ORA-21300: objects option not installed
Cause: The objects option is not installed at this site. object types and other object
features are, therefore, unavailable.
Action: Install the objects option. The objects option is not part of the Oracle Server
product and must be purchased separately. Contact an Oracle sales representative if
the objects 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 OCI_OBJECT mode when calling OCIInitialize().
ORA-21500: internal error code, arguments: [string], [string], [string], [string],
Cause: This is the generic error number for the OCI environment (client-side) internal
errors. This indicates that the OCI environment has encountered an exceptional
condition.
ORA-21501: program could not allocate memory
ORA-21503: program terminated by fatal error
Cause: A program is in an unrecoverable error state.
ORA-19999 to ORA-24279 71-1

ORA-21520: database server driver not installed
Cause: User attempted to access a database server through an object-mode OCI
environment but the necessary driver for supporting such access to the database
server is not installed or linked in.
Action: Check if the driver corresponding to the database server has been installed/
linked in and entered in the server driver table.
ORA-21521: exceeded maximum number of connections in OCI (object mode only)
Cause: User exceeded the maximum number of connections (255) that can be
supported by an OCI environment in object mode.
Action: Close some of existing and unused connections before opening more
connections.
ORA-21522: attempted to use an invalid connection in OCI (object mode only)
Cause: User attempted to use an invalid connection or a connection that has been
terminated in an OCI environment (object mode), or user attempted to dereference a
REF obtained from a connection which has been terminated.
Action: Ensure that the connection exists and is still valid.
ORA-21523: functionality not supported by the server (object mode only)
Cause: User attempted to use a functionality that the server does not support.
Action: Upgrade the server
ORA-21524: object type mismatch
Cause: The object type of the object is different from what is specified.
Action: Check the type of the object and correct it.
ORA-21525: attribute number or (collection element at index) string violated its
constraints
Cause: Attribute value or collection element value violated its constraint.
Action: Change the value of the attribute or collection element such that it meets its
constraints. The constraints are specified as part of the attribute or collection element's
schema information.
ORA-21526: initialization failed
Cause: The initialization sequence failed. This can happen, for example, if an
environment variable such as NLS_DATE_FORMAT is set to an invalid value.
Action: Check that all NLS environment variables are well-formed.
ORA-21527: internal OMS driver error
Cause: A process has encountered an exceptional condition. This is the generic
internal error number for Oracle object management services exceptions.
Action: Report this as a bug to Oracle Support Services.
ORA-21528: internal error, image could not be understood
Cause: The format of the image passed to the pickler is incorrect and cannot be
understood.
71-2 Error Messages
ORA-21560: argument string is null, invalid, or out of range

Cause: The argument is expecting a non-null, valid value but the argument value
passed in is null, invalid, or out of range. Examples include when the LOB/FILE
positional or size argument has a value outside the range 1 through (4GB - 1), or
when an invalid open mode is used to open a file, etc.
Action: Check your program and correct the caller of the routine to not pass a null,
invalid or out-of-range argument value.
ORA-21561: OID generation failed
Cause: The handles passed in may not be valid
Action: Check the validity of the env, svc handles
ORA-21600: path expression too long
Cause: The path expression that is supplied by the user is too long. The path
expression is used to specify the position of an attribute in an object. This error occurs
when one of the intermediate elements in the path expression refers to an attribute of
a built-in type. Thus, the OCI function cannot proceed on to process the rest of the
elements in the path expression.
Action: User should pass in the correct path expression to locate the attribute.
ORA-21601: attribute is not an object
Cause: The user attempts to perform an operation (that is valid only for an object) to
an attribute of a built-in type. An example of such an illegal operation is to
dynamically set a null structure to an attribute of a built-in type.
Action: User should avoid performing such operation to an attribute of built-in type.
ORA-21602: operation does not support the specified typecode
Cause: The user attempts to perform an operation that does not support the specified
typecode.
Action: User should use the range of valid typecodes that are supported by this
operation.
ORA-21603: property id [string] is invalid
Cause: The specified property id is invalid.
Action: User should specify a valid property id. Valid property ids are enumerated by
OCIObjectPropId.
ORA-21604: property [string] is not a property of transient or value instances
Cause: Trying to get a property which applies only to persistent objects.
Action: User should check the lifetime and only get this property for persistent
objects.
ORA-21605: property [string] is not a property of value instances
Cause: Trying to get a property which applies only to persistent and transient objects.
Action: User should check the lifetime and only get this property for persistent and
transient objects.
ORA-21606: can not free this object
Cause: Trying to free an object that is persistent and dirty and the
OCI_OBJECTFREE_FORCE flag is not specified.
Action: Either flush the persistent object or set the flag to OCI_OBJECTFREE_FORCE
ORA-19999 to ORA-24279 71-3
ORA-21607: memory cartridge service handle not initialized

Cause: Attempt to use the handle without initializing it.
Action: Initialize the memory cartridge service handle.
ORA-21608: duration is invalid for this function
Cause: Attempt to use a duration not valid for this function.
Action: Use a valid duration - a previously created user duration or
OCI_DURATION_STATEMENT or OCI_DURATION_SESSION. For callout duration
or external procedure duration, use OCIExtProcAllocCallMemory.
ORA-21609: memory being resized without being allocated first
Cause: Attempt to resize memory without allocating it first.
Action: Allocate the memory first before resizing it.
ORA-21610: size [string] is invalid
Cause: Attempt to resize memory with invalid size.
Action: Pass in a valid size (must be a positive integer).
ORA-21611: key length [string] is invalid
Cause: Attempt to use an invalid key length.
Action: Key length is invalid and valid range is 0 to 64
ORA-21612: key is already being used
Cause: Attempt to use a key that is already used.
Action: Use a new key that is not yet being used.
ORA-21613: key does not exist
Cause: Attempt to use a non-existent key
Action: Use a key that already exists.
ORA-21614: constraint violation for attribute number [string]
Cause: Constraints on the attribute were violated
Action: Correct the value (of the attribute) so that it satisfies constraints
ORA-21615: copy of an OTS (named or simple) instance failed
Cause: see following message
Action: Check that no attribute value violates constraints.
ORA-21700: object does not exist or is marked for delete
Cause: User attempted to perform an inappropriate operation to an object that is nonexistent or marked for delete. Operations such as pinning, deleting and updating
cannot be applied to an object that is non-existent or marked for delete.
Action: User needs to re-initialize the reference to reference an existent object or the
user needs to unmark the object.
ORA-21701: attempt to flush objects to different servers
Cause: User attempted to flush objects to different servers in one function call. These
objects are obtained by calling a callback functions provided by the program.
71-4 Error Messages
ORA-21702: object is not instantiated or has been de-instantiated in cache

Cause: User attempted to perform an inappropriate operation to a transient object
that is not instantiated in the object cache. Operations that cannot be applied to a notinstantiated transient object include deleting or pinning such an object.
Action: User should check their code to see if they are performing such an operation
without instantiating the object first, or performing such an operation after the
allocation duration of the object has expired.
ORA-21703: cannot flush an object that is not modified
Action: The object should not be flushed.
ORA-21704: cannot terminate cache or connection without flushing first
Action: The transaction should be aborted or committed before terminating the cache
or connection.
ORA-21705: service context is invalid
Cause: The service context that is supplied by the user is not valid.
Action: User needs to establish the service context.
ORA-21706: duration does not exist or is invalid
Cause: The duration number that is supplied by the user is not valid.
Action: User needs to establish the duration or use a correct predefined duration.
ORA-21707: pin duration is longer than allocation duration
Cause: The pin duration supplied by the user is longer than the allocation duration.
This affects operations such as pinning and setting default parameters.
Action: User should use a shorter pin duration or use the null duration.
ORA-21708: inappropriate operation on a transient object
Cause: User attempted to perform an inappropriate operation on a transient object.
Operations that cannot be applied to a transient object include flushing and locking.
Action: User should avoid performing such operation on a transient object.
ORA-21709: cannot refresh an object that has been modified
Cause: User attempted to refresh an object that has been marked for delete, update or
insert (new).
Action: User should unmark the object before refreshing it.
ORA-21710: argument is expecting a valid memory address of an object
Cause: The object memory address that is supplied by the user is invalid. The user
may have passed in a bad memory address to a function that is expecting a valid
memory address of an object.
Action: User should pass in a valid memory address of an object to the function.
ORA-21779: duration not active
Cause: User is trying to use a duration that has been terminated.
ORA-19999 to ORA-24279 71-5
ORA-21780: Maximum number of object durations exceeded.

Cause: This typically happens if there is infinite recursion in the PL/SQL function
that is being executed.
Action: User should alter the recursion condition in order to prevent infinite
recursion.
ORA-22053: overflow error
Cause: This operation's result is above the range of Oracle number.
Action: Decrease the input value(s) so that the result is in the range of Oracle number.
ORA-22054: underflow error
Cause: This operation's result is below the range of Oracle number.
Action: Increase the input value(s) so that the result is in the range of Oracle number.
ORA-22055: unknown sign flag value [string]
Cause: Signed flag used is not OCI_NUMBER_SIGNED or
OCI_NUMBER_UNSIGNED.
Action: Use either OCI_NUMBER_SIGNED or OCI_NUMBER_UNSIGNED as sign
flag.
ORA-22056: value [string] is divided by zero
Cause: Given value is divied by zero.
Action: Modify divisor value to be non-zero.
ORA-22057: bad integer length [string]
Cause: The length of the integer (ie number of bytes) to be converted to or from an
Oracle number is invalid.
Action: Use integer length 1, 2, 4 or 8 bytes only.
ORA-22059: buffer size [string] is too small - [string] is needed
Cause: The buffer to hold the resulting text string is too small.
ORA-22060: argument [string] is an invalid or uninitialized number
Cause: An invalid or uninitialized number is passed in.
Action: Use a valid number. To initialize number call OCINumberSetZero().
ORA-22061: invalid format text [string]
Cause: The numeric format string for converting characters to or from an Oracle
number is invalid.
ORA-22062: invalid input string [string]
Cause: The text string for converting to numbers is invalid.
Action: Use a valid input string as documented in OCI Programmer's Guide.
ORA-22063: reading negative value [string] as unsigned
Cause: Attempt to convert a negative number to an unsigned integer.
Action: Use the sign flag ORLTSB to convert a signed number.
71-6 Error Messages
ORA-22064: invalid NLS parameter string [string]

Cause: The NLS parameter string for converting characters to or from an Oracle
number is invalid.
ORA-22065: number to text translation for the given format causes overflow
Cause: Rounding done due to the given string format causes overflow.
Action: Change the string format such that overflow does not occur.
ORA-22130: buffer size [string] is less than the required size [string]
Cause: The size of the buffer into which the hexadecimal REF string is to be written is
too small.
ORA-22131: hexadecimal string length is zero
Cause: The given hexadecimal string length must be greater than zero.
Action: Specify a length greater than zero.
ORA-22132: hexadecimal string does not correspond to a valid REF
Cause: The given hexadecimal string is invalid.
Action: Provide a valid hexadecimal string which was previously returned by a call to
OCIRefToHex().
ORA-22140: given size [string] must be in the range of 0 to [string]
Cause: The given resize size is invalid.
Action: Ensure that the given size is in the required range.
ORA-22141: given size [string] must be even in UTF-16 environment
Cause: The given resize size is odd. In a UTF-16 environment, all characters are 2
bytes in length.
Action: Ensure that the given size is even.
ORA-22150: variable-length array has not been initialized
Cause: An un-initialized variable-length array is being operated upon.
Action: Initialize the variable-length array prior to calling this function.
ORA-22151: cannot resize non-zero variable-length array to zero elements
Cause: Trying 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-hand-side of an assignment or the
destination array of an append is not initialized.
ORA-22153: source variable-length array is not initialized
Cause: The variable-length array on the left-hand-side of an assignment or the source
array of an append is not initialized.
ORA-19999 to ORA-24279 71-7
ORA-22160: element at index [string] does not exist

Cause: Collection element at the given index does not exist.
Action: Specify the index of an element which exists.
ORA-22161: type code [string] is not valid
Cause: Given type code is not valid.
Action: Use one of the typecodes enumerated in OCITypeCode.
ORA-22162: element at index [string] has been previously deleted
Cause: Trying to delete a non-existent collection element.
Action: Check for the existence of the element prior to calling this function.
ORA-22163: left hand and right hand side collections are not of same type
Cause: Left hand and right side collections are not of same type.
Action: Ensure that the same collection type is passed for both left hand and right
hand side of this function.
ORA-22164: delete element operation is not allowed for variable-length array
Cause: Trying to delete an element of a variable-length array.
Action: Ensure that the collection is not a variable-length array prior to calling this
function.
ORA-22165: given index [string] must be in the range of [string] to [string]
Cause: Given index is not in the required range.
Action: Ensure that the given index is in the required range.
ORA-22166: collection is empty
Cause: Given collection is empty.
Action: Test if collection is empty prior to invoking this function.
ORA-22167: given trim size [string] must be less than or equal to [string]
Cause: Given trim size is greater than the current collection size.
Action: Ensure that the given size is less than or equal to the collection size prior to
calling this function.
ORA-22275: invalid LOB locator specified
trying to update the LOB in a trigger body -- LOBs in trigger bodies are read only; (5)
the locator is for a BFILE/BLOB and the routine expects a CLOB/NCLOB locator; (6)
the locator is for a CLOB/NCLOB and the routine expects a BFILE/BLOB locator;
setting the LOB locator to empty. For (2),(3), (5) and (6)pass the correct type of locator
into the routine. For (4), remove the trigger body code that updates the LOB value.
ORA-22276: invalid locator for LOB buffering
Cause: There are several causes: (1) the locator was never enabled for buffering (2) it
is not an updated locator but is being used for a write/flush operation
Action: For (1) enable the locator for buffering; (2) ensure that only an updated locator
is used for a LOB update operation
71-8 Error Messages
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 LOB buffering, modify the LOB through one LOB locator only.
ORA-22278: must update the LOB only through the LOB buffers
Cause: LOB buffering is enabled for this LOB and there are buffers for this LOB in the
buffer pool. Thus, updating the LOB through means other than the 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, buffers associated with this LOB
should either be flushed as necessary or buffering should be disabled. Once this is
done, reissue the command.
ORA-22279: cannot perform operation with LOB buffering enabled
Cause: The operation attempted is not allowed when LOB buffering is enabled.
Action: If the operation is required, LOB buffering should not be used. In this case,
flush buffers associated with the input LOB locator as necessary, disable buffering on
the input LOB locator and reissue the command.
ORA-22280: no more buffers available for operation
Cause: There are two causes: (1) All buffers in the buffer pool have been used up by
previous operations (2) Attempt to flush a LOB without any previous buffered update
operations.
Action: For (1), flush the LOB(s) through the locator that is being used to update the
LOB. For (2), write to the LOB through a locator enabled for buffering before
attempting to flush buffers.
ORA-22281: cannot perform operation with an updated locator
Cause: The input locator has buffering enabled and was used to update the LOB
value through the LOB buffering subsystem. The modified buffer has not been
flushed since the write that was performed by the the input locator; thus, the input
locator is considered an updated locator. Updated locators cannot be the source of a
copy operation. Only one locator per LOB may be used to modify the LOB value
through the LOB buffering subsystem.
Action: Depending on whether the modifications made through the input locator to
the LOB buffering subsystem should be written to the server, either flush the buffer to
write the modifications, or, disable buffering on the locator to discard the
modifications. Then, reissue the command.
ORA-22282: non-contiguous append to a buffering enabled LOB not allowed
Cause: The buffered write operation has an input offset value more than one byte or
character past the end of the LOB.
Action: Specify an input offset value which is exactly one character or byte greater
than the length of the LOB that you are attempting to update through a buffered write
operation.
ORA-22283: filename contains characters that refer to parent directory
Cause: Filename contains a path "../" which references a parent directory
Action: Ensure that the filename does not contain characters which reference a parent
directory.
ORA-19999 to ORA-24279 71-9
ORA-22284: duplicate LONG binds are not supported

Cause: LOB access layer could not handle duplicate LONG binds.
Action: Provide distinct LONG or VARCHAR binds.
ORA-22285: non-existent directory or file for string operation
Cause: Attempted to access a directory that does not exist, or attempted to access a
file in a directory that does not exist.
Action: Ensure 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 file or directory to perform string operation
Cause: The user does not have the necessary access privileges on the directory alias
and/or the file for the operation.
Action: Ask the database/system administrator to grant the required privileges on the
directory alias and/or the file.
ORA-22287: invalid or modified directory occurred during string operation
Cause: The directory alias used for the current operation is not valid if being accessed
for the first time, or has been modified by the DBA since the last access.
Action: If you are accessing this directory for the first time, provide a valid directory
name. If you have been already successful in opening a file under this directory
before this error occured, then close the file and retry the operation with a valid
directory alias as modified by your DBA. Oracle recommends that directories should
be modified only during quiescent periods.
ORA-22288: file or LOB operation string failed\nstring
Cause: The operation attempted 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 set for the
specified operation. If the error still persists, report the error to the DBA.
ORA-22289: cannot perform string operation on an unopened file or LOB
Cause: The file or LOB is not open for the required operation to be performed.
Action: Precede the current operation with a successful open operation on the file or
LOB.
ORA-22290: operation would exceed the maximum number of opened files or LOBs
Cause: The number of open files or LOBs has reached the maximum limit.
Action: Close some of the opened files or LOBs and retry the operation.
ORA-22291: Open LOBs exist at transaction commit time
Cause: An attempt was made to commit a transaction with open LOBs at transaction
commit time.
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.
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 hte LOB in read-only mode does not require a transaction.
ORA-22293: LOB already opened in the same transaction

Cause: An attempt was made to open a LOB that already is open in this transaction.
Action: Close the LOB before attempting to re-open it.
ORA-22294: cannot update a LOB opened in read-only mode
Cause: An attempt was made to write to or update a LOB opened in read-only mode.
Action: Close the LOB and re-open it in read-write mode before attempting to write to
or update the LOB.
ORA-22295: cannot bind more than 4000 bytes data to LOB and LONG columns in 1
statement
Cause: An attempt was made to bind data more than 4000 bytes of data to both LOB
and LONG columns in the same insert or update statement. You can bind more than
4000 bytes of data to either a LONG column or one or more LOB columns but not
both.
Action: Bind more than 4000 bytes of data to either the LONG column or one or more
LOB columns but not both.
ORA-22296: invalid ALTER TABLE option for conversion of LONG datatype to
LOB
Cause: An attempt was made to specify ALTER TABLE options which are disallowed
during conversion of LONG datatype to LOB. The only ALTER TABLE options
allowed during conversion of LONG datatype to LOB are the default clause and LOB
storage clause for the column being converted to LOB.
Action: Remove the disallowed options.
ORA-22297: warning: Open LOBs exist at transaction commit time
Cause: An attempt was made to commit a transaction with open LOBs at transaction
commit time.
Action: This is just a warning. The transaction was commited successfully, but any
domain or functional indexes on the open LOBs were not updated. You may want to
rebuild those indexes.
ORA-22298: length of directory alias name or file name too long
Cause: The length of directory alias name or file name given for a BFILE is too long.
Action: Use a shorter alias or file name.
ORA-22303: type "string"."string" not found
Cause: The user is trying to obtain information for a type that cannot be found.
Action: Check that the schema is correct and that the type has been created correctly.
ORA-22304: input type is not an object type
Cause: The user is trying to obtain the supertype information for a non-object type.
Action: Pass in only an object type.
ORA-22305: attribute/method/parameter "string" not found
Cause: Type element with the given name is not found in the type.
Action: Check to make sure that the type element exists.
ORA-22306: type "string"."string" already exists
Cause: The user is trying to create a type that already exists.
ORA-19999 to ORA-24279 71-11
Action: Check to make sure that the type has not been created prior to this.
ORA-22307: operation must be on a user-defined type
Cause: attempt to perform an operation that is allowed only on a user-defined type,
and the type is not a user-defined type.
Action: Check to make sure that only user-defined types are being operated on.
ORA-22308: operation not allowed on evolved type
Cause: An attempt was made to replace a type whose attribute definition been been
altered.
Action: Submit ALTER TYPE ADD/DROP statement instead of ALTER TYPE
REPLACE.
ORA-22309: attribute with name "string" already exists
Cause: The user is attempting to create an object type where more than one attributes
have the same name.
Action: Check to make sure that all attribute names are unique.
ORA-22310: ALTER TYPE error. Refer to table "string"."string" for errors
Cause: An invalid alter type statement was submitted.
Action: Correct the errors listed in specified table and resubmit statement.
ORA-22311: type for attribute "string" does not exist
Cause: The type of the attribute does not exist.
Action: No types were created/modified for this DDL transaction. Redo the DDL
transaction and add the creation of the attribute's type in the DDL transaction.
ORA-22312: must specify either CASCADE or INVALIDATE option
Cause: An attempt was made to alter a type which has a dependent type or table
without specifying the CASCADE or INVALIDATE option.
Action: Resubmit the statement with either the CASCADE or INVALIDATE option.
Specify CASCADE if you want to cascade the type change to dependent types and
tables; otherwise, specify INVALIDATE to invalidate all dependents.
ORA-22313: cannot use two versions of the same type "string"
Cause: The version of this type conflicts with the version of this type used by another
library that was linked in with the application. An application may only use one
version of a type.
Action: Check that the libraries being linked with this application and use the same
versions of the type.
ORA-22314: method information mismatch in ALTER TYPE
Cause: The number of methods or the method signature do not match that of the
original type declaration. This is not supported.
Action: Make sure the method signature stay identical for the previously declared
method. Do not drop existing methods.
ORA-22315: type "string" does not contain a map or order function
Cause: The input type does not contain a map or order function so one cannot be
returned.
Action: Add a map or order function to the type or catch this error.
ORA-22316: input type is not a collection type

Cause: The user is trying to obtain information for collection types on a non-named
collection type.
Action: Use a named collection type for the function.
ORA-22317: typecode string is not legal as a number type
Cause: The user is trying to use a number typecode that is not valid.
Action: Use only OCI_TYPECODE_SMALLINT, OCI_TYPECODE_INTEGER,
OCI_TYPECODE_REAL, OCI_TYPECODE_DOUBLE, OCI_TYPECODE_FLOAT,
OCI_TYPECODE_NUMBER, or OCI_TYPECODE_DECIMAL.
ORA-22318: input type is not an array type
Cause: The user is trying to obtain the number of elements for a non-array type.
Action: Pass in only a named collection type which is an array.
ORA-22319: type attribute information altered in ALTER TYPE
Cause: The type attribute information does not match that of the original type
declaration when altering type. Attributes cannot be altered during ALTER TYPE.
Only new methods can be added.
Action: Check that all type alterations are legal.
ORA-22320: missing user version string
Cause: The VERSION option is specified without a user version string.
Action: Resubmit the statement with the version string following the VERSION
keyword.
ORA-22321: method does not return any result
Cause: OCITypeResult() was called on a method that does not return any results.
Action: Check that you are passing in the correct method descriptor, or that your
method creation was done correctly.
ORA-22322: error table "string"."string" has incorrect structure
Cause: The specified error table does not have the expected table structure.
Action: Execute the DBMS_UTILITY.CREATE_ALTER_TYPE_ERROR_TABLE
procedure to create an error table, then resubmit the statement using the new error
table.
ORA-22323: error table "string"."string" does not exist
Cause: The error table does not exist.
Action: Resubmit the statement with a correct error table name.
ORA-22324: altered type has compilation errors
Cause: The use of the ALTER TYPE statement caused a compilation error.
Action: Correct the error reported and resubmit the statement.
ORA-22325: event for create type with user version string
ORA-22326: cannot change a type to FINAL if it has subtypes
Cause: An attempt was made to change a type with subtypes to FINAL.
Action: Drop all subtypes of the target type before changing it to FINAL.
ORA-19999 to ORA-24279 71-13
ORA-22327: cannot change a type to NOT INSTANTIABLE if it has dependent

tables
Cause: An attempt was made to change a type with dependent tables to NOT
INSTANTIABLE.
Action: Drop all dependent tables of the target type and resubmit the statement.
ORA-22328: object "string"."string" has errors.\nstring
Cause: Altering the target type causes errors in its dependent object.
Action: Correct the problem in the dependent object and resubmit the statement.
ORA-22329: cannot alter a non-object type
Cause: An attempt was made to execute ALTER TYPE on a non-object type.
Action: Drop the non-object type first, then re-create it as an object type.
ORA-22330: cannot alter a type that is not valid
Cause: An attempt was made to perform ALTER TYPE on an invalid type.
Action: Use the CREATE OR REPLACE TYPE command to modify the type.
ORA-22331: cannot alter an incomplete type
Cause: An attempt was made to perform ALTER TYPE on an incomplete type.
Action: Use CREATE TYPE to completely define the original type before executing
the ALTER TYPE.
ORA-22332: a dependent object in schema "string" has errors.\nstring
Cause: Altering the target type causes errors in its dependent object.
Action: Correct the problem in the dependent object and resubmit the statement.
ORA-22333: cannot reset type "string"."string" due to invalid dependent types and
tables
Cause: An attempt was made to reset the type version with invalid dependent types
and tables.
Action: Use the ALTER TYPE COMPILE statement to compile all invalid dependent
types and use the ALTER TABLE UPGRADE INCLUDING DATA to upgrade all the
dependent tables then resubmit the statement.
ORA-22334: cannot reset type "string"."string". Dependent tables must be upgraded
to latest version
Cause: An attempt was made to reset the type version when the data in the
dependent table has not been upgraded to the latest type version.
Action: Use the ALTER TABLE UPGRADE INCLUDING DATA statement to
upgrade the data in the dependent tables then resubmit the statement.
ORA-22335: The client cannot work with an altered type
Cause: A pre 8.2 client has requested a type that has been altered on the server.
Action: Only 8.2 or higher clients could access altered types
ORA-22336: table contained 8.0 image format, must specify INCLUDING DATA
Cause: One of the following: 1) An attempt was made to alter a type with a dependent
table in 8.0 image format and the NOT INCLUDING TABLE DATA option was
specified. 2) An attempt was made to upgrade a table in 8.0 image format with the
NOT INCLUDING DATA option specified.
Action: Resubmit the statement with INCLUDING DATA option.

ORA-22337: the type of accessed object has been evolved
Cause: The type of the accessed object has been altered and the client's object is based
on an earlier type definition.
Action: The user needs to exit application and modify application to accommodate
the type change. From SQL/PLUS, reconnect and resubmit statement.
ORA-22338: must specify CASCADE INCLUDING DATA when altering the final
property
Cause: An attempt was made to alter the final property of a type with dependent
table(s) without specifying the CASCADE INCLUDING DATA . option.
Action: Resubmit the statement with the CASCADE INCLUDING DATA option.
ORA-22339: cannot alter to not final since its attribute column is substitutable
Cause: An attempt was made to alter a type to not final when its embedded attribute
is defined as substitutable in some tables. Note, this is a restriction in 9.0 version
because when a type is altered to not final, column of that type is set to not
substitutable at all levels; thus, it is an error if one of its embedded attribute column is
already marked substitutable.
Action: Recreate the table and specify NOT SUBSTITUTABLE AT ALL LEVELS for all
columns of non final type. Then resubmit the ALTER TYPE statement.
ORA-22340: cannot string type "string"."string". Dependent tables must be
upgraded to latest version
Cause: An attempt was made to reset the version, drop or alter a type when the data
in dependent table has not been upgraded to the latest version.
Action: Use the ALTER TABLE UPGRADE INCLUDING DATA statement to
upgrade the data in the dependent tables then resubmit the statement.
ORA-22341: cannot assign supertype instance to subtype
Cause: An attempt was made to assign or copy a supertype instance to a container
(destination) that can only hold a subtype instance.
Action: Make sure the runtime type of the source of the assignment or copy is the
same type as the destination or is a subtype of the destination type
ORA-22342: dependent VARRAY column exceeds the maximum inline column size
Cause: An attempt was made to alter a type (add or modify attribute) which causes
the size of its dependent VARRAY column to exceed the maximum inline column
size. However, the VARRAY column was not specified to be stored as LOB at the
table level when the table was created.
Action: Specify the VARRAY column to be stored as LOB at the table level when the
table is created.
ORA-22343: Compilation error for type invalidated by ALTER TYPE
Cause: Compilation failed for a type which was invalidated by ALTER TYPE. We
throw this error and rollback the compilation effort so that the user may be able to fix
whatever is causing the compilation error and try again. It is important that we do not
chnage status here and modify the dependency information as this will affect the
creation of versions.
Action: Check what is causing teh compilation error and correct it and try again.
ORA-19999 to ORA-24279 71-15
ORA-22344: can not specify CONVERT TO SUBSTITUTABLE option for ALTER

TYPE other than NOT FINAL change
Cause: An attempt was made to specify CONVERT TO SUBSTITUTABLE option for
ALTER TYPE other than NOT FINAL change.
Action: Specify CONVERT TO SUBSTITUTABLE option only for ALTER TYPE NOT
FINAL change.
ORA-22345: recompile type string.string before attempting this operation
Cause: An attempt was made to perform an operation which requires the specified
datatype to be valid, but the datatype is invalid
Action: Recompile the specified type and retry the operation
ORA-22346: Type has cyclical dependency. Should use CASCADE option
Cause: An attempt was made to alter a type which has a cyclical dependency, with
invalidate option.
Action: Give CASCADE option instead of INVALIDATE
ORA-22347: No changes to type specified for ALTER TYPE
Cause: The ALTER TYPE does not contain any changes to the type.
Action: If any change is required for the type, modify the ALTER TYPE to specify the
change. Else no need for the ALTER.
ORA-22348: The object type DDL is not supported in Editioned schema
Cause: The object type DDL was not supported in an Editioned schema.
Action: Do not perform this DDL on an Editioned schema object.
ORA-22349: This version of the Oracle server does not support PL/SQL package
type descriptions.
Cause: An attempt was made to get PL/SQL package type description information
from a version of the Oracle server that does not support the description of PL/SQL
package types.
Action: Do not attempt to describe package types on this Oracle server.
ORA-22350: Incomplete opaque type cannot be used here
Cause: An incomplete SYS.AnyType or SYS.AnyData or SYS.AnyDataSet is being
used inappropriately.
ORA-22351: OCI API is not supported by this version of the Oracle server.
Cause: An attempt was made to call an Oracle Call Interface (OCI) API which is not
supported by this version of the Oracle server.
Action: Do not call the unsupported OCI API when connected to this Oracle server.
ORA-22352: Type is unsupported or contains an unsupported attribute or element.
Cause: A PL/SQL package type was not supported on the client or contained an
attribute or element that was not supported on the client. Unsupported types include
index by VARCHAR2 collections, remote types and MLSLABELs.
Action: Do not attempt to use unsupported PL/SQL package types or types that
contain unsupported attributes or elements on the client.
ORA-22369: invalid parameter encountered in method string

Cause: An invalid parameter is being passed to this method of
SYS.AnyType ,SYS.AnyData or SYS.AnyDataSet
Action: Check the parameters being passed to this method and make sure that the
parameters are allowed.
ORA-22370: incorrect usage of method string
Cause: This method of SYS.AnyType or SYS.AnyData or SYS.AnyDataSet is being
used inappropriately.
ORA-22371: Table contains data of type string.string, version string, which does not
exist
Cause: Some of the older versions of the type may have got deleted because one or
more of the types it were referencing was dropped.
Action: These data could not be read as the whole ADT. Read the data at individual
scalar attribute level.
ORA-22372: Event for type dictionary upgrade
Cause: This is an internally used event for type dictionary upgrades from 8.0 to 8.1.
Action: None
ORA-22373: Older version hashcode encountered
Cause: An older version HC is encountered when creating a new version hahscode.
Currently this is handled internally.
Action: None
ORA-22374: cannot reset the version of a type with table dependents
Cause: The type for which reset version was requested has table dependents.
Action: None
ORA-22375: Event to check for subtypes in complete type tree
Cause: This event is used to check for subtypes in complete type tree without any
restriction on depth in the fix for bug# 12430142.
Action: None
ORA-22376: Event to keep old behavior for type public synonyms
Cause: A public type synonym was qualified with a schema which may lead to
incorrect name resolution. This issue has been resolved. However, this event allows
you to use the old behavior if desired.
Action: None
ORA-22377: Unpacking of ANYDATA columns is not supported for attribute
columns.
Cause: An attribute column has been referenced in the 'modify_opaque_type' clause.
Action: Do not use an attribute column in the 'modify_opaque_type' clause.
ORA-19999 to ORA-24279 71-17
ORA-22378: cannot add, drop or modify attributes of a type with synonym

dependents defined on FINAL types
Cause: An attempt to ALTER TYPE [ADD | DROP | MODIFY] ATTRIBUTE on a
type with synonym dependents defined on a FINAL type, which has table
dependents, failed.
Action: None
ORA-22379: event to bypass hashcode in kottyphcequ
Cause: This event is used to bypass the error "ORA-39779" during the import of table
data which occurs because of the mismatch in the hashcodes of a user-defined type
between the source and the target databases. The event has to be used when the
source database has an improper hashcode for the user-defined type.
Action: None
ORA-22380: event to skip updating the dependencies
Cause: This event is used to bypass regenerating dependencies during upgrade while
running ALTER TABLE MOVE on type dictionary tables to enable storage in row.
This happens on the upgrade path from 10.1.
Action: None
ORA-22600: encountered 8.0.2 (Beta) VARRAY data that cannot be processed
Cause: Production Oracle8 (8.0.3 and beyond) encounters some VARRAY data which
was created and stored by Oracle8 8.0.2 (Beta 2). Production Oracle8 cannot
understand or process such VARRAY data.
Action: Delete the VARRAY data from the table by dropping the table, deleting the
rows, or nulling out the VARRAY columns, and then re-insert the VARRAY data.
There is no provided script or tool to help automate this conversion.
ORA-22601: pickler TDS context [string] is not initialized
Cause: Attempt to use the pickler TDS context without initializing it.
Action: Use OCIPicklerTdsCtxInit to initialize the context.
ORA-22602: pickler TDS handle [string] is not well-formed
Cause: Attempt to use the pickler TDS handle without initializing/ constructing it.
Action: Use OCIPicklerTdsInit to initialize the handle before it is constructed. Use
OCIPicklerTdsGenerate to generate the TDS before its attributes can be accessed.
ORA-22603: cannot add an attribute to the already generated TDS handle
Cause: Attempt to add an attribute to the already constructed TDS.
Action: Use a TDS handle that is initialized but not yet constructed.
ORA-22604: TDS handle already generated
Cause: Attempt to geneate TDS that is already genearated.
Action: Use a TDS handle that is initialized but not yet generated.
ORA-22605: FDO handle [string] is not initialized
Cause: Attempt to use an uninitialized FDO handle.
Action: Use OCIPicklerFdoInit to initialize FDO handle".
ORA-22606: pickler image handle [string] is not well-formed
Cause: Attempt to use the image handle without initializing/ constructing it.
Action: Use OCIPicklerImageInit to initialize the handle before it is constructed. Use

OCIPicklerImageGenerate to generate the image before its attributes can be accessed.
ORA-22607: image handle already generated
Cause: Attempt to geneate image that is already genearated.
Action: Use a image handle that is initialized but not yet generated.
ORA-22608: cannot add an attribute to the already generated image handle
Cause: Attempt to add an attribute to the already constructed image.
Action: Use a image handle that is initialized but not yet constructed.
ORA-22609: error string during initialization of FDO
Cause: Error during FDO initialization.
Action: Take an action based on the specified error.
ORA-22610: error while adding a scalar to the image handle
Cause: Error while adding a scalar attribute to the image handle
Action: Make sure image handle is initialized before adding scalar
ORA-22611: TDS version is not recognized
Cause: Incorrect TDS handle is passed
Action: Make sure image handle is initialized with the correct TDS
ORA-22612: TDS does not describe a collection TDS
Cause: collection construct/access routines are being on an image but the TDS does
not describe that a collection TDS
Action: Make sure a collection TDS is used before invoking collection routines on the
image handle
ORA-22613: buflen does not match the size of the scalar
Cause: buflen is incorrect
Action: Make sure buflen is correct and matches the size of the scalar
ORA-22614: error while construction the collection in the image
Cause: Error during the construction of collection
Action: Make sure image handle is initialized and OCIPicklerImageCollBegin is called
to begin collection
ORA-22615: attribute is not a collection
Cause: collection routine is invoked upon a non-collection attribute
Action: Make sure attribute is a collection
ORA-22616: image is not of Oracle 8.1 format
Cause: The function being invoked is applicable only for 8.1 images
Action: Make sure image is of 8.1 format
ORA-22617: error while accessing the image handle collection
Cause: Error while accessing collection in the image handle
Action: Make sure image is initialized correctly and the collection is constructed
properly.
ORA-19999 to ORA-24279 71-19
ORA-22618: attribute is a BAD NULL in the image handle

Cause: attribute in question is probably the attribute of a null embedded image
Action: Make sure attribute number is valid or it is NULL or NOT NULL.
ORA-22619: all collection elements have already been accessed
Cause: Accessing a collection element after all the collection elements are already
accessed
Action: This function should not be invoked any more.
ORA-22620: buffer size too small to hold the value
Cause: Buffer size is not enough to hold the value. Most likely while doing the
character set conversion, a bigger buffer is needed.
Action: Pass in a bigger buffer. If the client character set format differs from that of
server, doing the conversion may result in 4X expansion.
ORA-22621: error transfering an object from the agent
Cause: Any error returned from pickler routines on the agent side.
ORA-22625: OCIAnyData is not well-formed
Cause: Attempt to use the OCIAnyData without initializing constructing it.
Action: Use OCIAnyDataBeginConstruct to initialize the handle before it is adding
attributes. Use OCIAnyDataEndConstruct to complete the construction. Or use
OCIAnyDataConvert to do the construction. MAke sure it is properly constructed
before accessing attributes.
ORA-22626: Type Mismatch while constructing or accessing OCIAnyData
Cause: Type supplied is not matching the type of the AnyData. If piece wise
construction or access is being attempted, the type supplied is not matching the type
of the current attribute.
Action: Make sure the type supplied matches the type of object to to be constucted or
accessed.
ORA-22627: tc [string] must be that of object/varray/nested table
Cause: Type code is not that of object/varray/nested table
Action: Make sure the type code is OCI_TYPECODE_OBJECT or
OCI_TYPECODE_VARRAY or OCI_TYPECODE_TABLE
ORA-22628: OCIAnyData already constructed
Cause: Attempt to add attributes to OCIAnyData that is already constructed.
Action: Use the OCIAnyData that is initialized but not yet constructed.
ORA-22629: OCIAnyData is null
Cause: Attempting an operation that is not valid on null OCIAnyData
Action: Make sure OCIAnyData is not null.
ORA-22630: attribute [string] is null or it is not well-formed
Cause: Passing an attribute that is null or not well-formed
Action: Make sure the attribute is not null or is well-formed.
ORA-22631: attribute [string] is is not well-formed or does not match the type
Cause: Passing an attribute that is not well-formed or does not match the input type.
Action: Make sure the attribute is well-formed and matches the type specified.
ORA-22632: AnyDataSet parameter is not valid for the current operation
Cause: The AnyDataSet parameter is null or it is somehow invalid for the current
operation.
Action: Check the documentation for the current operation.
ORA-22633: Error freeing AnyDataSet
Cause: AnyDataSet that is passed in may not be valid.
Action: Check all the AnyDataSet parameters.
ORA-22634: Error adding new instance to AnyDataSet
Cause: Current instance in the AnyDataSet has not been fully constructed.
Action: Make sure that the current instance is fully constructed before adding new
instance.
ORA-22635: time stamp with time zone type not supported
Cause: OCIAnyData did not support conversion of time stamp with time zone when
the version of time zone files differ.
Action: Use same version of time zone files.
ORA-22800: invalid user-defined type
Cause: An attempt was made to use an incomplete type as a constructor.
Action: Complete the type definition before using it in a query.
ORA-22801: invalid object row variable
Cause: The specified object row variable is not available in the scope of name
resolution.
Action: Verify the specified object row variable is correct, or use an object row
variable visible in scope.
ORA-22802: remote implementation type not supported
Cause: Remote type reference was not supported with user-defined aggregate
function.
Action: Use local implementation type with user-defined aggregate function.
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 not permitted on object tables or user-defined type
columns
Cause: An attempt was made to perform queries or DML operations on remote object
tables or on remote table columns whose type is one of object, REF, nested table or
VARRAY.
Action: n/a
ORA-19999 to ORA-24279 71-21
ORA-22805: cannot insert NULL object into object tables or nested tables
Cause: An attempt was made to insert a NULL object into an object table or a Nested
Table.
Action: Ensure that a non-NULL object is inserted into the table or insert an object
with attributes whose values are NULL.
ORA-22806: not an object or REF
Cause: An attempt was made to extract an attribute from an item that is neither an
object nor a REF.
Action: Use an object type or REF type item and retry the operation.
ORA-22807: cannot resolve to a scalar type or a collection type
Cause: Invalid use of a non-scalar (for example, object type) item.
Action: Change the item's data type and retry the operation.
ORA-22808: REF dereferencing not allowed
Cause: An attempt was made to access an object type's attributes by dereferencing a
REF item.
Action: Make the item an object type instead of a REF to an object type.
ORA-22809: nonexistent attribute
Cause: An attempt was made to access a non-existent attribute of an object type.
Action: Check the attribute reference to see if it is valid. Then retry the operation.
ORA-22810: cannot modify object attributes with REF dereferencing
Cause: An attempt was made to modify the attributes an object by dereferencing a
REF column in an UPDATE statement.
Action: Update the table containing the object that the REF points to, or change the
REF column to an object type column.
ORA-22812: cannot reference nested table column's storage table
Cause: An attempt to access the nested table column's storage table is not allowed in
the given context.
Action: Issue the statement against the parent table containing the nested table
column.
ORA-22813: operand value exceeds system limits
Cause: Object or Collection value was too large. The size of the value might have
exceeded 30k in a SORT context, or the size might be too big for available memory.
Action: Choose another value and retry the operation.
ORA-22814: attribute or element value is larger than specified in type
Cause: Value provided for the object type attribute or collection element exceeded the
size specified in the type declaration.
Action: Choose another value and retry the operation.
ORA-22816: unsupported feature with RETURNING clause
Cause: RETURNING clause is currently not supported for object type columns,
LONG columns, remote tables, INSERT with subquery, and INSTEAD OF Triggers.
Action: Use separate select statement to get the values.
ORA-22817: subquery not allowed in the default clause

Cause: An attempt was made to use a subquery in the column default clause
expression.
Action: Remove the subquery from the default clause.
ORA-22818: subquery expressions not allowed here
Cause: An attempt was made to use a subquery expression where these are not
supported.
Action: Rewrite the statement without the subquery expression.
ORA-22819: scope of input value does not correspond to the scope of the target
Cause: An attempt to operate on a REF value scoped to a different table than the
expected one
Action: Use a ref which is scoped to the expected table and retry the operation
ORA-22826: cannot construct an instance of a non instantiable type
Cause: An attempt was made to use a non instantiable type as a constructor.
Action: None
ORA-22828: input pattern or replacement parameters exceed 32K size limit
Cause: Value provided for the pattern or replacement string in the form of
VARCHAR2 or CLOB for LOB SQL functions exceeded the 32K size limit.
Action: Use a shorter pattern or process a long pattern string in multiple passes.
ORA-22833: Must cast a transient type to a persistent type
Cause: An attempt was made to use the transient type in the query result.
Action: Cast the transient type to a structurally equivalent persistent type.
ORA-22835: Buffer too small for CLOB to CHAR or BLOB to RAW conversion
(actual: string, maximum: string)
Cause: An attempt was made to convert CLOB to CHAR or BLOB to RAW, where the
LOB size was bigger than the buffer limit for CHAR and RAW types. Note that
widths are reported in characters if character length semantics are in effect for the
column, otherwise widths are reported in bytes.
Action: Do one of the following: 1. Make the LOB smaller before performing the
conversion, for example, by using SUBSTR on CLOB 2. Use DBMS_LOB.SUBSTR to
convert CLOB to CHAR or BLOB to RAW.
ORA-22837: Relational hint or keyword is disallowed for user-level DML
Cause: An attempt was made to use relational hint or keyword in user- level DML.
Action: Avoid using DML with relational hint or keyword.
ORA-22839: Direct updates on SYS_NC columns are disallowed
Cause: An attempt was made to update SYS_NC columns directly.
Action: Avoid direct updates on SYS_NC columns.
ORA-22850: duplicate LOB storage option specificed
Cause: A LOB storage option (CHUNK, PCTVERSION, CACHE, NOCACHE,
TABLESPACE, STORAGE, INDEX, SECUREFULE/BASICFILE, [A]SYNC) was
Action: Specify all LOB storage options only once.
ORA-19999 to ORA-24279 71-23
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 retry the operation.
ORA-22852: invalid PCTVERSION LOB storage option value
Cause: The specified PCTVERSION LOB storage option value must be an integer.
Action: Choose an appropriate integer value and retry the operation.
ORA-22853: invalid LOB storage option specification
Cause: A LOB storage option was not specified
Action: Specify one of CHUNK, PCTVERSION, CACHE, NOCACHE, TABLESPACE,
STORAGE, INDEX, [A]SYNC or DATA SYNC as part of the LOB storage clause.
ORA-22854: invalid option for LOB storage index
Cause: A valid LOB store index option was not specified.
Action: Specify one of (INITRANS, 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 LOB storage segment was specified with multiple
columns in the column list.
Action: Specify each column LOB storage only with optional name(s).
ORA-22856: cannot add columns to object tables
Cause: An attempt was made to add columns to an object table. Object tables cannot
be altered to add columns since its definition is based on an object type.
Action: Create a new type with additional attributes, and use the new type to create
an object table. The new object table will have the desired columns.
ORA-22857: cannot modify columns of object tables
Cause: An attempt was made to alter the object table by modifing existing columns.
An object table cannot be altered to modify existing columns since it is based on an
object type. The table definition must be in sync 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 alteration of datatype
Cause: An attempt was made to modify the column type to object, REF, nested table,
VARRAY or LOB type.
Action: Create a new column of the desired type and copy the current column data to
the new type using the appropriate type constructor.
ORA-22859: invalid modification of columns
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 current column data to
the new type using the appropriate type constructor.
ORA-22860: object type expected
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.
Action: Use a valid object type in the table or column definition.

ORA-22861: invalid user-defined type
Cause: An attempt was made to create a column or object table of a non- existent type.
Action: Specify a valid type in the table or column definition.
ORA-22862: specified object identifier doesn't 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 of the same name.
Action: Specify the correct object identifier or leave it out of the statement.
ORA-22863: synonym for datatype string.string not allowed
Cause: A synonym specification for a datatype is not supported
Action: do not use the synonym for the datatype
ORA-22864: cannot ALTER or DROP LOB indexes
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: cannot replace a type with table dependents
Cause: An attempt was made to replace a type that has table dependents.
Action: Drop all table(s) depending on the type, then retry the operation.
ORA-22868: table with LOBs contains segments in different tablespaces
Cause: An attempt was made to drop a tablespace which contains the segment(s) for
the LOB columns of a table but does not contain the table segment.
Action: Find table(s) with LOB columns which have non-table segments in this
tablespace. Drop these tables and reissue drop tablespace.
ORA-22869: depth of type dependency hierarchy exceeds maximum limit
Cause: The type dependency hierarchy was structured to have depth greater than
1024.
Action: Re-structure the type dependency hierarchy to a shorter depth.
ORA-22870: ALTER TYPE with REPLACE option a non-object type
Cause: attempt to perform ALTER TYPE with REPLACE option a non-object type
Action: drop the non-object type first, then re-create it as an object type
ORA-22871: ALTER TYPE with REPLACE is not allowed for pure incomplete types
Cause: An attempt to perform ALTER TYPE with REPLACE option for a pure
incomplete type
Action: Completely define the original type, before using the ALTER TYPE with
REPLACE option.
ORA-19999 to ORA-24279 71-25
ORA-22872: OID INDEX clause not allowed on tables with primary key based
object identifiers
Cause: An attempt to create an OID INDEX on a table with primary key based object
identifiers.
Action: Remove the OID INDEX clause
ORA-22873: primary key not specified for primary key based object table
Cause: An attempt 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 the type "string"
Cause: Attribute specified in the user_defined clause is not an attribute of the REF
type
Action: Ensure that the name specified in the user_defined clause is the name of a
valid attribute of the REF type
ORA-22875: cannot drop primary key of an object table whose object identifier is
primary key based
Cause: An attempt to drop the primary key of an object table which has a primary key
based object identifier
Action: Remove the drop primary key clause
ORA-22876: this user-defined type is not allowed or it cannot be used in this
context
Cause: An attempt to create a kind of user-defined type which is not allowed, or an
attempt to create table columns or use default constructor with a type on which these
are not supported.
Action: Ensure that the type is permitted 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 encountered while parsing the physical
attributes of a LOB partition or subpartition. Either the LOB partition is in a table
partitioned using the HASH method, or the LOB subpartition is in a table
subpartitioned using the HASH method. TABLESPACE is the only valid option for a
HASH partition or subpartition.
Action: Remove the invalid option(s).
ORA-22878: duplicate LOB partition or subpartition specified
Cause: An attempt was made to specify a partition or subpartition that has already
been specified for the LOB column.
ORA-22879: cannot use the 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: invalid REF
Cause: An invalid REF was accessed.
Action: Modify the REF and retry the operation.

ORA-22881: dangling REF
Cause: The object corresponding to the REF that was accessed does not exist.
Action: Ensure that the REF value is pointing to an existing object.
ORA-22882: object creation failed
Cause: The object cannot be created in the database.
Action: Check to see if the object table exists and the object size is not too big. Then
ORA-22883: object deletion failed
Cause: The object could not be deleted from the database.
Action: Check to see if the object table exists.Then retry the operation.
ORA-22884: object modification failed
Cause: The object could not be modified in the database.
Action: Check to see if the object table exists and the object size is not too big. Then
ORA-22885: cannot get REF to a non-persistent object
Cause: An attempt was made to get a REF for something other than an object in an
object table. REFs can only be taken for objects in object tables.
Action: Rewrite the query to obtain REF values from 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.
Action: Ensure that the scoped table is an object table.Then retry the operation.
ORA-22887: type of REF column is not the same as that of its scoped table
Cause: The type specified for the REF column and the type specified for the scope
table are different.
Action: Ensure that the types of a REF column and its scoped table are the same.
ORA-22888: duplicate SCOPE clauses for a REF column
Cause: Multiple SCOPE clauses were specified for a single REF column.
Action: Remove the duplicate SCOPE clauses and retry the operation.
ORA-22889: REF value does not point to scoped table
Cause: An attempt was made to insert a REF value that does not point to the scoped
table.
Action: Ensure that the REF values point to the scoped table.
ORA-22890: cannot specify name for REF column constraint
Cause: An attempt was made to specify a constraint name for a constraint on a REF
column.
Action: Remove the constraint name and retry the operation.
ORA-22891: cannot have multiple columns in REF constraint
Cause: An attempt was made to specify multiple columns in a single REF constraint.
Action: Specify separate constraints for each column and retry the operation.
ORA-19999 to ORA-24279 71-27
ORA-22892: scoped table "string" does not exist in schema "string"

Cause: The scoped table specified for a REF column does not exist.
Action: Ensure that the scoped table exists and retry the operation.
ORA-22893: constraint can be specified only for REF columns
Cause: The constraint specified does not apply to non-REF columns.
Action: Remove the constraint and retry the operation.
ORA-22894: cannot add constraint on existing unscoped REF columns of nonempty tables
Cause: An attempt was made to add a constraint to existing unscoped REF columns
of a table which contains one or more rows.
Action: Remove 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.
Action: Ensure that the referenced table is an object table.Then retry the operation.
ORA-22896: cannot have both scope and referential constraint on REF column
"string"
Cause: REF column has both a referential and a scope constraint. A referential
constraint implies a scope constraint.
Action: Remove either the referential or scope constraint and then retry the operation.
ORA-22897: no scope clause specified for user-defined REF column "string"
Cause: User-defined REF column does not have a scope constraint.
Action: Specify a scope constraint for the user-defined REF column and retry the
operation.
ORA-22898: existing scope clause on "string" points to a table other than the one
mentioned in the referential constraint
Cause: Table mentioned in the referential integrity constraint is different from the
scope table of the REF column.
Action: Specify the scope table of the REF column in the referential integrity
constraint and then retry the operation.
ORA-22899: cannot specify both scope and rowid constraint on ref column
Cause: An attempt was made to specify both a scope and a rowid constraint on a REF
column.
Action: Remove either the rowid or scope constraint and then retry the operation.
ORA-22900: the SELECT list item of THE subquery is not a collection type
Cause: The THE subquery must SELECT a nested table or VARRAY item.
Action: change the subquery to SELECT a nested table or VARRAY item.
ORA-22901: cannot compare VARRAY or LOB attributes of an object type
Cause: Comparison of VARRAY or LOB attributes of an object type was attempted 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: CURSOR on a subquery is allowed only in the top-level SELECT list of a
query.
Action: n/a
ORA-22903: MULTISET expression not allowed
Cause: MULTISET expressions are allowed only inside a CAST to a nested table or
VARRAY type.
Action: put the MULTISET(subquery) expression inside a CAST to a nested table or
VARRAY type.
ORA-22904: invalid reference to a nested table column
Cause: invalid use of a nested table column
Action: remove invalid reference to the nested table column
ORA-22905: cannot access rows from a non-nested table item
Cause: attempt to access rows of an item whose type is not known at parse time or
that is not of a nested table type
Action: use CAST to cast the item to a nested table type
ORA-22906: cannot perform DML on expression or on nested table view column
Cause: Attempted to perform a DML on an expression or on a nested table view
column where a nested table column of a base table is expected.
Action: Only nested table column of a base table is allowed in the DML.
ORA-22907: invalid CAST to a type that is not a nested table or VARRAY
Cause: Attempted to CAST to a type that is not a nested table or VARRAY
Action: Re-specify CAST to a nested table or VARRAY type.
ORA-22908: reference to NULL table value
Cause: The evaluation of the THE subquery or nested table column resulted in a
NULL value implying a NULL table instance. The THE subquery or nested table
column must identify a single non-NULL table instance.
Action: Ensure that the evaluation of the THE subquery or nested table column
results in a single non-null table instance. If happening in the context of an insert
statement where the THE subquery is the target of an insert, then ensure that an
empty nested table instance is created by updating the nested table column of the
parent table's row specifying an empty nested table constructor.
ORA-22909: exceeded maximum VARRAY limit
Cause: The total number of elements used in VARRAY construction exceeds the
specified VARRAY limit.
Action: Don't use the more than the specified limit of elements for VARRAY
construction.
ORA-22910: cannot specify schema name for nested tables
Cause: Table name was qualified with schema name in the nested table column's (or
attribute's) storage clause.
Action: Re-specify the nested table item's storage clause without the schema name
qualification. By default, the storage table for the nested table item is created in the
same schema as the containing table.
ORA-19999 to ORA-24279 71-29
ORA-22911: duplicate storage specification for the nested table item

Cause: The storage clause is specified more than once for the NESTED TABLE
column.
Action: Remove the duplicate storage specification.
ORA-22912: specified column or attribute is not a nested table type
Cause: The storage clause is specified for a column or attribute that is not a nested
table column or attribute.
Action: Specify a valid nested table column or attribute.
ORA-22913: must specify table name for nested table column or attribute
Cause: The storage clause is not specified for a nested table column or attribute.
Action: Specify the nested table storage clause for the nested table column or
attribute.
ORA-22914: DROP of nested tables not supported
Cause: Attempted to DROP a nested table.
Action: nested tables cannot be explicitly dropped. nested tables can only be dropped
by dropping their containing parent table.
ORA-22915: cannot ALTER a nested table's storage table to ADD/MODIFY
columns
Cause: An attempt was made to ADD or MODIFY columns of a nested table's storage
table.
Action: Columns cannot be added or modified for a nested table's storage table. You
must alter the parent table's nested table column to cause any such change.
ORA-22916: cannot do an exact FETCH on a query with Nested cursors
Cause: Exact FETCH on a query was specified which is not allowed if the query
returns any cursors.
Action: Do not use an exact FETCH.
ORA-22917: use VARRAY to define the storage clause for this column or attribute
Cause: Not using VARRAY to define storage clause for VARRAY column or attribute.
Action: Specify VARRAY before the column storage clause and resubmit statement.
ORA-22918: specified column or attribute is not a VARRAY type
Cause: Attemp to define a VARRAY storage clause for a column or attribute which is
not VARRAY type.
Action: Specify VARRAY storage clause for a VARRAY column or attribute.
ORA-22919: dangling REF error or lock object failed for no wait request
Cause: The error could 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 nowait
request failed.
Action: Ensure that the REF value is pointing to an existing object or issue a lock
request without the nowait option.
ORA-22920: row containing the LOB value is not locked
Cause: The row containing the LOB value must be locked before updating the LOB
value.
Action: Lock the row containing the LOB value before updating the LOB value.
ORA-22921: length of input buffer is smaller than amount requested
Cause: The buffer length is not big enough to hold the amount of data requested.
Action: Verify that the number of bytes/characters specified in the input amount
parameter is not bigger than the number of bytes specified in the input buffer length
parameter. Allocate more space for the input buffer if necessary.
ORA-22922: nonexistent LOB value
Cause: The LOB value associated with the input locator does not exist. The
information in the locator does not refer to an existing LOB.
Action: Repopulate the locator by issuing a select statement and retry the operation.
ORA-22923: amount of data specified in streaming LOB write is 0
Cause: Trying to write LOB value via the streaming mechanism (i.e. unlimited write)
but the input amount of data to stream was specified as 0. Thus, the user is trying 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 needed for the consistent read was already
overwritten by another writer.
Action: Use a larger version pool.
ORA-22925: operation would exceed maximum size allowed for a LOB value
Cause: Trying to write too much data to the LOB value. LOB size is limited to 4
gigabytes.
Action: Either start writing at a smaller LOB offset or write less data to the LOB value.
ORA-22926: specified trim length is greater than current LOB value's length
Cause: The input length for which to trim the LOB value to is greater than the current
length of the LOB value.
Action: May not need to trim the LOB value because it's already smaller than the trim
length specified. Or, if trimming the LOB value really is required, use a smaller trim
length.
ORA-22927: invalid LOB locator specified
trying to update the LOB in a trigger body -- LOBs in trigger bodies are read only.
setting the LOB locator to empty. For (2) and (3), pass the correct type of locator into
the routine. For (4), remove the trigger body code 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, WRITE and EXECUTE 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-19999 to ORA-24279 71-31

ORA-22930: directory does not exist
Cause: Attempt to access a directory that does not exist.
Action: Make sure the name is correct.
ORA-22933: cannot change object with type or table dependents
Cause: Attempt to replace, drop or rename an object with type or table dependents.
Action: Drop depending objects or use FORCE option if available.
ORA-22936: cannot replace a system predefined type
Cause: An attempt was made to replace a system predefined type.
Action: Use other names for newly created system types.
ORA-22950: cannot ORDER 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: ORDER method used to compare two object values returned NULL which is
not allowed.
Action: Redefine the ORDER method to not return a NULL.
ORA-22952: Nested Table equality requires a map method on the element ADT
Cause: Nested Table equality was tried where the element ADT did not have a map
method defined on it.
Action: Define a map method on the element ADT..
ORA-22953: Cardinality of the input to powermultiset exceeds maximum allowed
Cause: The cardinality of the input nested table to the powermultiset should not
exceed 32 elements
Action: Reduce the number of elements to the input.
ORA-22954: This multiset operation is not supported for this element type.
Cause: The multiset operation attempted was not supported for the nested table
element type.
Action: Use a supported element type.
ORA-22955: The cardinality parameter is not within the allowed limits
Cause: The cardinality parameter has to be greater than 1 and less than or equal to the
cardinality of the input.
Action: Give a valid cardinality value.
ORA-22956: The set contains no elements
Cause: An empty set was given as input to the powermultiset function.
Action: Give a non-empty set as input
ORA-22957: NULL is an invalid input to powermultiset and COLLECT functions
Cause: NULL was given as input to the powermultiset or COLLECT function.
Action: Give a non-null value as input
ORA-22958: This operation is not allowed in check constraints or triggers

Cause: An invalid operation is used in a check constraint or trigger
Action: Do not use the operation
ORA-22970: name does not correspond to an object view
Cause: Either the expression is not a view name or the name specified does not
correspond to an object view.
Action: Replace the expression with the name of an object view.
ORA-22971: invalid datatype for PRIMARY KEY-based object identifier
Cause: When creating an object view, the datatype of an expression in the WITH
OBJECT OID clause is not allowed for PRIMARY KEY-based OID.
Action: Replace the expression with one of appropriate scalar datatype.
ORA-22972: NULL value not allowed in PRIMARY KEY-based object identifier
Cause: A value constituting the PRIMARY KEY-based object identifier is NULL.
Action: Ensure the expressions in MAKE_REF system function or attributes in the
WITH OBJECT OID clause of an object view do not evaluate to NULL.
ORA-22973: size of object identifier exceeds maximum size allowed
Cause: Size of the PRIMARY KEY-based object identifier of an object view exceeds the
maximum size of 4000 bytes.
Action: Specify fewer or smaller PRIMARY KEY attributes in the WITH object OID
clause when creating the object view.
ORA-22974: missing WITH OBJECT OID clause
Cause: WITH OBJECT OID clause is not specified when creating an object view.
Action: Specify the WITH OBJECT OID clause.
ORA-22975: cannot create a PRIMARY KEY-based REF to this object view
Cause: The object view specified in the MAKE_REF function does not have a
PRIMARY KEY-based object identifier. A PRIMARY KEY-based REF cannot be
created for such a view.
Action: 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: Number of arguments for 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: Either the attribute name is missing in the WITH OBJECT OID clause or it is
invalid.
Action: Specify a valid attribute of the object type of the object view.
ORA-22978: only simple attribute name is allowed in the WITH OBJECT OID
clause
Cause: Attempted 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-19999 to ORA-24279 71-33
ORA-22979: cannot INSERT object view REF or user-defined REF

Cause: Attempt to insert an object view REF or user-defined REF in a REF column
created to store system generated REF values"
Action: Make sure the REF to be inserted is not from an object view or from a userdefined REF column
ORA-22980: must specify a set of attributes for the WITH OBJECT OID clause
Cause: The WITH OBJECT OID DEFAULT clause was used, but the underlying view
or table does not have a OID.
Action: Specify attributes for the WITH OBJECT OID clause to create a primary key
based object identifier for the object view.
ORA-22981: must specify a table/view having system generated OID
Cause: The super-view is based on a table/view having the system generated OID
and the sub-view must also be based on a similar table/view.
Action: Specify table/view having system generated OID and retry the the operation.
ORA-22982: cannot create sub-view under this view
Cause: The view derives its OID from a table/view having primary key based OID
and sub-views cannot be created under such views.
Action: Specify view having system generated OID or a view created with the
specification of attributes in the WITH OBJECT ID clause and retry the operation.
ORA-22983: not a user-defined REF
Cause: Attempt to use a system generated REF value where a user-defined REF value
should be used.
Action: Make sure the REF value is user-defined.
ORA-22984: view query cannot contain references to a super view
Cause: The query defining the view contains references to a super-view of the view
being created.
Action: Make sure that the view query does not reference a super-view.
ORA-22990: LOB locators cannot span transactions
Cause: A LOB locator selected in one transaction cannot be used in a different
transaction.
Action: Re-select the LOB locator and retry 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 LOB locators selected from remote tables
Cause: A remote LOB column cannot be referenced.
Action: Remove references to LOBs in remote tables.
ORA-22993: specified input amount is greater than actual source amount
Cause: (1) For LOB write, the amount of data received is different from the amount
that was indicated would be sent. (2) For LOB copy and loadfromfile, the end of the
source LOB/FILE value was reached before the specified input amount was copied/
loaded.
Action: (1) will happen when using OCI's piecewise mechanism with polling or with
a callback function. Modify the code either to send the amount specified or to pass 0
as the input amount so that any amount of data can be sent. (2) will happen if the
specified input amount is too large for the source LOB/FILE given the starting source
offset. Either decrease the starting source 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 LOB COPY or LOB LOADFROMFILE is beyond the end
of the source LOB.
Action: Check the length of the LOB and then adjust the source offset.
ORA-22995: TABLESPACE DEFAULT option is invalid in this context
Cause: TABLESPACE DEFAULT option can be specified for LOB columns only in the
following contexts: - 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.
Action: Remove the TABLESPACE DEFAULT option.
ORA-22996: NEXT extent size is smaller than LOB chunksize
Cause: An attempt was made to create or alter a LOB segment so that its NEXT extent
size was less than the LOB chunksize
Action: Specify a NEXT extent size that is greater than or equal to the LOB chunksize
ORA-22997: VARRAY | OPAQUE stored as LOB is not specified at the table level
Cause: An attempt was made to specify a VARRAY|OPAQUE column to be stored as
LOB at the partition/subpartition/template level. However the VARRAY|OPAQUE
column was not specified to be stored as LOB at the table level when the table was
created.
Action: Specify the VARRAY | OPAQUE column to be stored as LOB at the table
level when the table is created. Alternatively, do not specify the VARRAY | OPAQUE
column to be stored as LOB at the partition/subpartition/template level if it is not
specified at the table level when the table is created.
ORA-22998: CLOB or NCLOB in multibyte character set not supported
Cause: A CLOB or NCLOB in a fixed-width or varying-width multibyte character set
was passed to a SQL character function which does not support multibyte LOB data.
Action: Use DBMS_LOB functions such as DBMS_LOB.INSTR() and
DBMS_LOB.SUBSTR() or use PLSQL DBMS_LOB.READ/WRITE to access LOB data.
ORA-22999: CLOB or NCLOB data may have been corrupted
Cause: CLOB or NCLOB contains invalid character data. One possible cause is that
the wrong csid was specified for the external file when calling
DBMS_LOB.LOADCLOBFROMFILE or DBMS_XSLPROCESSOR.READ2CLOB to
load CLOB or NCLOB data from external files.
Action: Reload the CLOB/NCLOB data with the correct csid specified for the external
file.
ORA-23290: This operation may not be combined with any other operation
Cause: ALTER TABLE RENAME COLUMN/CONSTRAINT operation was given in
conjunction with another ALTER TBALE Operation. This is not allowed.
ORA-19999 to ORA-24279 71-35
Action: Ensure that RENAME COLUMN/CONSTRAINT is the only operation

specified in the ALTER TABLE.
ORA-23291: Only base table columns may be renamed
Cause: Tried to rename a column of a non-base table, like object table/ nested table/
materialized view table.
Action: None. This is not allowed.
ORA-23292: The constraint does not exist
Cause: The given constraint name does not exist.
Action: Give an existing constraint's name.
ORA-23293: Cannot rename a column which is part of a join index
Cause: The column participates in a join index.
Action: If you need to rename the column, you need to drop the join index.
ORA-23300: string
Cause: The stored procedure 'raise_system_error' was called which causes this error
to be generated.
Action: Correct the problem as described in the error message or contact the
application administrator or DBA for more information.
ORA-23301: mixed use of deferred rpc destination modes
Cause: Replication catalog determined deferred RPC destinations were mixed with
destination determined by other mechanisms in the same transaction.
Action: Do not mix destination types in the same transaction.
ORA-23302: application raised communication failure during deferred RPC
Cause: An application declared a communication failure during a defered RPC.
Action: Retry the application when communication is restored.
ORA-23303: application raised generic exception during deferred RPC
Cause: An application declared a generic failure during a defered RPC.
Action: Determined by the application
ORA-23304: malformed deferred rpc at arg string of string in call string, in tid string
Cause: A deferred RPC call was issued without the correct number of arguments as
determined by the count parameter to dbms_defer.call
Action: Be sure the number of actuals matches the count.
ORA-23305: internal deferred RPC error: string
Cause: An internal error occurred in deferred rpc.
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 string already exists
Cause: The given database already replicates the given schema.
Action: Choose a different schema or a different database.
ORA-23308: object string.string does not exist or is invalid

Cause: The given name was null or misspelled, the given type was wrong, the object
does not exist as a valid database object, or the object does not exist as a replicated
object with the appropriate status.
Action: Ensure the object is valid in the database, is visible to the user, and, if
appropriate, is a valid object in all_repobject.
ORA-23309: object string.string of type string exists
Cause: An object in the same namespace exists, perhaps with a different type or
shape, or the same object has already been registered as an repobject in another object
group.
Action: Remove the offending object with the SQL DROP command, unregister the
offending object with dbms_repcat.drop_master_repobject(), or reinvoke the request
using TRUE for a boolean parameter such as retry or use_existing_object.
ORA-23310: object group "string"."string" is not quiesced
Cause: The requested operation requires the object group to be suspended.
Action: Invoke suspend_master_activity at the repgroup's masterdef, wait until the
status has changed to quiesced, and then retry the original request.
ORA-23312: not the masterdef according to string
Cause: The group name is null, the group name is misspelled, the invocation or given
database is not the masterdef, or one of the masters does not believe the invocation
database is the masterdef.
Action: If the given group name and masterdef were both correct, connect to the
masterdef and retry the request, or relocate the masterdef at the (errant) databases
using relocate_masterdef.
ORA-23313: object group "string"."string" is not mastered at string
Cause: The group name is null, the group name is misspelled, the invocation database
is not a master, or the invocation database does not believe the given database is a
master.
Action: If the given group name was correct, connect to a current master and retry the
request, make the invocation database a master with add_master_database, or use
switch_mview_master if the invocation database is a materialized view site.
ORA-23314: database is not a materialized view site for "string"."string"
Cause: The invocation database is not a materialized view database for the given
object group.
Action: Connect to the desired materialized view database and retry the request, or
make the invocation database a materialized view site with create_mview_repschema
or create_mview_repgroup.
ORA-23315: repcatlog version or request string is not supported by version string
Cause: Either incompatible repcat versions are used, or a repcatlog record has been
corrupted.
Action: Convert the master to a compatible version of repcat or retry the request.
ORA-23316: the masterdef is string
Cause: The requested operation is not permitted on a masterdef site.
Action: Relocate the masterdef to another master and retry the operation.
ORA-19999 to ORA-24279 71-37
ORA-23317: a communication failure has occurred

Cause: The remote database is inaccessible.
Action: Ensure the remote database is running, the communications network is
functioning, and the appropriate database links are present.
ORA-23318: a ddl failure has occurred
Cause: User-supplied or system-generated ddl did not execute successfully.
Action: Examine ddl, database state, repcatlog, and all_errors to determine why the
failure occurred.
ORA-23319: parameter value string is not appropriate
Cause: The given value of a parameter is either null, misspelled, or not supported.
Action: Refer to the documentation and use parameter values that are appropriate for
the given situation.
ORA-23320: the request failed because of values string and string
Cause: A missing ddl record for a repcatlog record, or inconsistency in repcat views.
Action: Retry the request, or make the views consistent.
ORA-23321: Pipename may not be null
Cause: You called dbms_pipe with a null pipe name.
Action: Find out the name of the pipe and call function with non-null pipename.
ORA-23322: Privilege error accessing pipe
Cause: You either tried to create a pipe that already existed and belonged to someone
else, or remove a pipe that you were not authorized to use, or put a message into a
pipe that you were not authorized for, or get a message from a pipe that you were not
authorized for.
Action: You may have to use a different pipename.
ORA-23323: parameter length exceeds deferred RPC limits
Cause: A deferred rpc parameter was longer than the deferred rpc limits of 4000 bytes
for char/varchar2 parameters and 2000 bytes for raw parameters.
Action: Use smaller parameters.
ORA-23324: error string, while creating deferror entry at "string" with error string
Cause: The given error was encountered while attempting to create a deferor entry for
the give error code and the give database.
Action: Correct the cause of the given error.
ORA-23325: parameter type is not string
Cause: A conflict resolution priority function was given a type different than the type
assigned to the priority group; or the priority group has no type assigned or a
function; 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: object group "string"."string" is quiesced

Cause: Either suspend_master_activity has been called before the object group has
resumed normal operation or a (deferred) rpc operation was attempted while the
object group was quiesced.
Action: If suspend_master_activity has been called and a resume_master_activity
request is pending, wait until it completes, and then reinvoke
suspend_master_activity. Otherwise, resume database activity with the
resume_master_activity call.
ORA-23327: imported deferred rpc data does not match string of importing db
Cause: Deferred rpc queues were imported from a database with a different global
name or operating system than importing database.
Action: Deferred rpc data should only be imported into a database with the same
global name and hardware and operating system.
ORA-23328: mview base table "string"."string" differs from master table
"string"."string"
Cause: When creating a materialized view through repcat, the materialized view base
table name did not match a replicated table name at the master.
Action: Change the materialized view ddl to use the same base table as the replicated
table name at the master.
ORA-23329: successful user-provided ddl but no materialized view "string"."string"
Cause: The DDL provided by the user to create a materialized view was executed
without error, but materialized view does not exist.
Action: Manually back-out the DDL, and reregister with matching ddl and
materialized view.
ORA-23330: column group string already exists
Cause: The column group was already registered in the object group.
Action: Use a column group name not yet registered in the replicated object group.
ORA-23331: column group string does not exist
Cause: The given column group is either null, misspelled or not registered.
Action: Use a registered column group.
ORA-23332: group string is in use; cannot drop
Cause: The given column group or priority group is being used to resolve conflicts.
Action: Call dbms_repcat procedures drop_update_resolution,
drop_delete_resolution, drop_unique_resolution so that the column group or priority
group is no longer in use before dropping.
ORA-23333: column string is already part of a column group
Cause: Attempted to add a column to a column group when the column was already
a member of a column group.
Action: Drop the column from its existing column group before trying to add it to
another.
ORA-23334: column string does not exist in table or column group
Cause: The given column is either null, misspelled or is not part of the given table or
column group.
ORA-19999 to ORA-24279 71-39
Action: Use a column that is a member of the table or column group.

ORA-23335: priority group string already exists
Cause: The priority group was already registered in the object group.
Action: Use a column group name not yet registered in the object group.
ORA-23336: priority group string does not exist
Cause: The priority group was already registered in the object group.
Action: Use a priority group name not yet registered in the object group.
ORA-23337: priority or value not in priority group string
Cause: The specified value or priority has not been registered as part of the priority
group.
Action: Either 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 has already been registered as part of the
priority group.
Action: Either specify a different value or priority that not already part of the priority
group, or drop the value to 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: Verify that additional conflict resolution information needs to be added and
provide a new sequence number. If modifying existing information, the existing
information must be dropped first.
ORA-23340: incorrect resolution method string
Cause: User function is specified when conflict resolution method was not "USER
FUNCTION" or specified resolution method is not one of the predefined methods.
Action: If user function is specified when conflict resolution method was not "USER
FUNCTION", either reregister function with method as "USER FUNCTION" or
specify a NULL user function. Otherwise Specify one of the documented supported
conflict resolution methods.
ORA-23341: user function required
Cause: A NULL user function was specified for the "USER FUNCTION" method.
Action: Provide user function name (e.g., "schema"."package"."function") that
conforms to the documented user function specifications or specify one of the
documented supported conflict resolution methods.
ORA-23342: invalid parameter column string
Cause: The parameter column name is null or misspelled, the invocation database is
not a master, or is of the wrong type for the specified conflict resolution method.
Action: 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, sequence, conflict type has not
been registered (e.g., for adding a comment).
Action: Specify a combination of column group, sequence, conflict type has been
registered.
ORA-23344: constraint (string.string) does not exist
Cause: A null, misspelled or nonexistent constraint was specified when registering a
uniqueness conflict.
Action: Register a named constraint for the specified table.
ORA-23345: table "string"."string" not registered to collect statistics
Cause: A procedure that deals with conflict resolution statistics-gathering was called
for a table that was not registered to collect statistics.
Action: Call dbms_repcat.register_statistics to register the table.
ORA-23346: primary key or object ID is undefined for table or materialized view
string
Cause: Trying to generate replication support for a table or materialized view without
a primary key (as defined by a constraint or dbms_repcat.set_columns) or an object
ID.
Action: For a table, add a primary key constraint or define a primary key using
dbms_repcat.set_columns or use object tables. For a ROWID materialized view, set
min_communication to false or use primary key or object ID materialized views.
ORA-23347: datatype string for column string table string not supported
Cause: The table has a column whose datatype is not supported by repcat.
Action: Remove the column from the table, or alter the column to have one of the
supported datatypes.
ORA-23348: cannot replicate procedure string; only IN parameters supported
Cause: Trying to generate replication support for a package that has a procedure with
OUT or IN OUT parameters.
Action: Remove the procedure from the package, or remove the OUT or IN OUT
parameters from the procedure.
ORA-23349: cannot generate replication support for functions
Cause: Trying to generate replication support for a package that has a public function,
or for a stand-alone function.
Action: Remove the public function from the package, or alter the function to be a
procedure.
ORA-23350: maximum number of recursive calls exceeded
Cause: This usually occurs when trying to resolve conflicts in a table while concurrent
updates to the same row create more conflicts.
Action: Re-execute the deferred transaction from DefError using
dbms_defer_sys.execute_error
ORA-23351: parameter datatype string for procedure string not supported
Cause: The procedure has a parameter whose datatype is not supported by repcat.
ORA-19999 to ORA-24279 71-41
Action: Remove the parameter from the procedure, or alter the parameter to have one
of the supported datatypes.
ORA-23352: duplicate destination for deferred transaction
Cause: A duplicate destination was specified for a deferred transaction either in a
dbms_defer.call call or an earlier dbms_defer.transaction call or a
dbms_defer_sys.add_default_dest call.
Action: Remove the duplicate entry
ORA-23353: deferred RPC queue has entries for object group "string"."string"
Cause: The requested action cannot be performed until the queue is empty for the
given object group
Action: Use dbms_defer_sys.execute or dbms_defer_sys.delete_tran to empty the
queue.
ORA-23354: deferred RPC execution disabled for "string" with "string"
Cause: Deferred RPC can not be executed at the destination with the specified
catchup value because their propogation has been disabled.
Action: Enable deferred RPC execution with the dbms_defer_sys.set_disabled call.
ORA-23355: object string.string does not exist or is invalid at master site
does not exist as a valid database object at the master site, or the object does not exist
as a replicated object with the appropriate status.
Action: Ensure the object is valid in the master database, and is visible to the user,
and, if appropriate, is a valid object in all_repobject.
ORA-23356: masterdef recognizes a master which does not recognize the masterdef
Cause: Possibly drop_master_repgroup was run at a master site but
remove_master_databases was not run at master definition site for that master.
Action: Run remove_master_databases from master definition site to remove the
appropriate master (see associated error messages).
ORA-23357: the propagator does not exist
Cause: The propagator does not exist.
Action: Register a new propagator.
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 identified database link with the connect-to user
identical to the owner of the database link.
ORA-23359: error on creating a ddl record for a repcatlog record
Cause: The userid in the repcatlog record does not match the userid of the connected
user.
Action: Retry the operation with a different user.
ORA-23360: only one materialized view for master table "string" can be created
Cause: Trying to create more than one materialized view on a given master table in
the same rep group.
Action: Create these other materialized views in a different rep group at another site.
ORA-23361: materialized view "string" does not exist at master site

Cause: The materialized view does not exist at the master site for offline instantiation
of the materialized view.
Action: The correct procedure is to create the materialized view in a different schema
at the master site, and then follow the instructions for offline instantiation of
materialized views.
ORA-23362: invalid user
Cause: The given user does not exist.
Action: n/a
ORA-23363: mismatch of mview base table "string" at master and mview site
Cause: The name of the base table of the materialized view at the master site is
different from the base table at the materialized view site. This error may arise during
offline instantiation of materialized views.
Action: Retry offline instantiation with a materialized view name less than 24 bytes
ORA-23364: Feature not enabled: Advanced replication
Cause: The Advanced Replication feature is not enabled at this site. Updatable
materialized views, deferred RPCs, and other replication features are, therefore,
unavailable.
Action: Do not attempt to use this feature. Contact an Oracle Customer Support
representative if the Advanced Replication feature has been purchased but not
enabled.
ORA-23365: site string does not exist
Cause: site specified in argument "reference_site" or argument "comparison_site" in
call to "differences()" routine or "rectify()" routine does not name an existing site.
Action: Make sure that database sites specified really do exist, and re-run the routine.
ORA-23366: integer value string is less than 1
Cause: Value of argument "max_missing" to routine "differences()" cannot be less than
1. Value of argument "commit_rows" to routines "differences()" and "rectify()" cannot
be less than 1.
Action: Choose an integer value for those arguments to be 1 or greater.
ORA-23367: table string is missing the primary key
Cause: Table specified in argument "oname1" or "oname2" in call to "differences()"
routine does not contain either a primary key or a virtual primary key (defined
through dbms_repcat package under symmetric replication).
Action: Make sure the tables specified have a primary key defined.
ORA-23368: name string cannot be null or the empty string
Cause: 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 argument to non-null or non-empty string.
ORA-23369: value of "string" argument cannot be null
Cause: Argument "max_missing" to "differences()" routine cannot be NULL.
Action: Legal values for "max_missing" are integers 1 or greater.
ORA-19999 to ORA-24279 71-43
ORA-23370: table string and table string are not shape equivalent (string)
Cause: The tables specified are not shape equivalent, which means intuitively that the
number of columns, the names, their datatypes and lengths are not the same.
Specifically, problem is in the parentheses and is one of the following: the number of
columns are not equal, datatypes of columns with same name in different tables are
different, lengths of varchar2 and char columns are not equal, precision and scale of
number datatypes are not equal.
Action: Make sure the two tables being compared have the same number of columns,
same column names, and same datatypes.
ORA-23371: column string unknown in table string
Cause: Some column in "array_columns" argument (or "column_list" argument) to
"differences()" routine does not correspond to a column in the specified table.
Action: Make sure that all the columns in either "array_columns" or "column_list" are
present in the specified table.
ORA-23372: type string in table string is unsupported
Cause: Certain types in the table comparison utility are not supported.
Action: Make sure that the types of columns in the tables to be compared are the ones
supported by 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.
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 given object group. A materialized
view repgroup cannot be created at a given site where a master repgroup with the
same name already exists.
Action: Choose a different group or a different database.
ORA-23375: feature is incompatible with database version at string
Cause: A feature not compatible with the specified database was used
Action: Set or raise the value of the "compatible" INIT.ORA parameter to match the
necessary compatibility level.
ORA-23376: node string is not compatible with replication version "string"
Cause: A feature not compatible with the remote database was used
Action: Upgrade the remote database and retry the operation
ORA-23377: bad name string for missing_rows_oname1 argument
Cause: An attempt was made to use the name of the reference site table as the name of
the missing_rows_oname1 argument.
Action: Provide a separately created table with a different name for
missing_rows_oname1 argument. The separately created table will contain the
differences between the tables being compared.
ORA-23378: connection qualifier "string" is not valid 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.
Action: Use or create a database link which 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 name of the database link
ORA-23380: propagation mode "string" is not valid
Cause: The specified propagation may be misspelled, or is not supported. For
materialized view sites, all materialized view object groups at the same materialized
view site with the same master object group must all have the same propagation
method.
Action: Refer to the manual on replicated data for valid propagation modes. For
materialized view sites, also ensure that the propagation modes of all materialized
view object groups with the same master object group are the same.
ORA-23381: generated object for base object string.string@string does not exist
Cause: The system generated object(s) for the specified base object do not exist at the
specified site. The current operation requires the base object to have generated
replication support.
Action: Ensure that the generated replication object(s) for the base object exist and are
valid at the specified site. If the generated object(s) do not exist, then the procedure
dbms_repcat.generate_replication_support() needs to be called from the master
definition site for the base object. missing_rows_oname1 argument. The separately
created table will contain the differences between the tables being compared.
ORA-23382: materialized view repgroup "string"."string" is not registered at site
string
Cause: The materialized view repgroup is not currently registered at the master and
so cannot be unregistered.
Action: None
ORA-23383: registration for materialized view repgroup "string"."string" failed at
site string
Cause: Insertion into local repschema table failed.
Action: None
ORA-23384: replication parallel push string argument out of range
Cause: Specified numeric argument to dbms_defer_sys.push is invalid.
Action: Fix the argument value and try again.
ORA-23385: replication parallel push string argument not valid
Cause: Specified string argument to dbms_defer_sys.push is invalid.
ORA-23386: replication parallel push cannot create slave processes
Cause: An error was occurred while creating slave processes for parallel push.
ORA-19999 to ORA-24279 71-45
Action: n/a
ORA-23387: replication parallel push dequeue error
Cause: An attempt to dequeue a deferred transaction failed while trying to assign a
new queue batch number.
Action: n/a
ORA-23388: replication parallel push watermark error
Cause: An error occurred during parallel push while trying to update the high-watermark information in system.def$_destination.
Action: n/a
ORA-23389: obsolete procedure; drop objects and recreate using new master
Cause: dbms_repcat.switch_mview_master is no longer supported.
Action: Drop the objects in the object group and recreate them using the new master.
ORA-23392: could not find materialized view to be associated with "string"."string"
Cause: Could not find materialized view associated with a trigger or index that is
being pulled from the master site.
Action: Ensure that materialized view, master, and master index or trigger is
registered as replicated objects.
ORA-23393: the user is already the propagator
Cause: The given user is already the current propagator.
Action: n/a
ORA-23394: duplicate propagator
Cause: More than one valid propagator exist.
Action: Unregister any duplicate propagator.
ORA-23395: object "string"."string" of type "string" does not exist or is invalid
does not exist as a valid database object, or the object does not exist as a replicated
object with the appropriate status.
Action: Ensure the object is valid in the database, is visible to the user, and, if
appropriate, is a valid object in all_repobject.
ORA-23396: database link "string" does not exist or has not been scheduled
Cause: the database link does not exist in the schema of the replication propagator or
has not been scheduled.
Action: Ensure that the database link exists in the database, is accessible and is
scheduled for execution.
ORA-23397: global name "string" does not match database link name "string"
Cause: the database link name at the local node does not match the global name of the
database that the link accesses.
Action: Ensure that global names is set to true and the link name matches the global
name.
ORA-23398: user name "string" at database link "string" does not match local user
name "string"
Cause: the user name of the replication administration user at the local node and the
user name at the node corresponding to the database link are not the same.
Symmetric replication expects the two users to be the same.
Action: Ensure that the user ID of the replication administration user at the local node
and the user ID at the node corresponding to the database link are the same.
ORA-23399: generation of replication support for "string"."string" is not complete
Cause: Replication support for the specified object has not been generated or the
generation process is not yet complete.
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 materialized view name "string"
Cause: A null, misspelled, or badly formed materialized view name was given to
dbms_mview.refresh.
Action: Provide a valid materialized view name to dbms_mview.refresh.
ORA-23401: materialized view "string"."string" does not exist
Cause: A materialized view name was given to dbms_mview.refresh that is not in
sys.snap$ or its associated views.
Action: Provide a materialized view name that is in sys.snap$, all_mviews or
user_mviews.
ORA-23402: refresh was aborted because of conflicts caused by deferred txns
Cause: There are outstanding conflicts logged in the DefError table at the materialized
view's master.
Action: Resolve the conflicts in the master DefError table and refresh again after the
table is empty. Alternatively, refresh with refresh_after_errors set to TRUE, which
will proceed with the refresh even if there are conflicts in the master's DefError table.
Proceeding despite conflicts can result with an updatable materialized view's changes
appearing to be temporarily lost (until a refresh succeeds after the conflicts are
resolved).
ORA-23403: refresh group "string"."string" already exists
Cause: Making a new refresh group when there is already a group of the same name
in sys.rgroup$.
Action: Choose a diifferent refresh group name.
ORA-23404: refresh group "string"."string" does not exist
Cause: A refresh group name was given that is not in sys.rgroup$.
Action: Provide a refresh group name that is in sys.rgroup$ or dbs_rgroup.
ORA-23405: refresh group number string does not exist
Cause: A refresh group number was given that is not in sys.rgroup$.
Action: Provide a refresh group number that is in sys.rgroup$ or dbs_rgroup.
ORA-19999 to ORA-24279 71-47
ORA-23406: insufficient privileges on user "string"

Cause: The caller is not the owner of the materialized view and does not have ALTER
ANY MATERIALIZED VIEW privileges.
Action: Perform the operation as the owner of the materialized view or as a user with
ALTER ANY MATERIALIZED VIEW privileges.
ORA-23407: object name string must be shaped like "schema"."object" or "object"
Cause: The object name (e.g., the rollback segment, the materialized view name, the
refresh group) was incorrectly specified.
Action: Retry the operation with the object name properly specified (like
"schema"."object" or "object")
ORA-23408: this replication operation is not supported in a mixed configuration
Cause: operation is not supported if the object group is replicated at a pre-V8 node.
Action: Ensure that all nodes of the replicated object group are V8.
ORA-23409: could not find an unused refresh group number
Cause: 1000 consecutive refresh group numbers, as defined by the rgroupseq number,
were already used by rows in sys.rgroup$.
Action: Alter the sequence number to be within a legal unused range and destroy
unneeded refresh groups.
ORA-23410: materialized view "string"."string" is already in a refresh group
Cause: A materialized view of the same name is already in a refresh group.
Action: Subtract the materialized view from the current refresh group and add it to its
new refresh group, or combine the two refresh groups into a single refresh group.
ORA-23411: materialized view "string"."string" is not in refresh group
"string"."string"
Cause: The specified materialized view is not in the specified refresh group.
Action: Try again with the proper materialized view and refresh group names.
ORA-23412: master table's primary key columns have changed
Cause: The master table's primary key constraint was modified after the primary key
materialized view was created.
Action: Drop and recreate the primary key materialized view
ORA-23413: table "string"."string" does not have a materialized view log
Cause: The fast refresh can not be performed because the master table does not
contain a materialized view log.
Action: Use the CREATE MATERIALIZED VIEW LOG command to create a
materialized view log on the master table.
ORA-23414: materialized view log for "string"."string" does not record rowid values
Cause: A rowid materialized view is being fast refreshed, but the materialized view
log does not record rowid information.
Action: Use the CREATE MATERIALIZED VIEW LOG...ADD ROWID command to
begin recording rowid information in the materialized view log.
ORA-23415: materialized view log for "string"."string" does not record the primary
key
Cause: A primary key materialized view is being fast refreshed, but the materialized
view log does not record primary key information.
Action: Use the CREATE MATERIALIZED VIEW LOG...ADD PRIMARY KEY
command to begin recording primary key information in the materialized view log.
ORA-23416: table "string"."string" does not contain a primary key constraint
Cause: The master table does not constaint a primary key constraint or the primary
key constraint has been disabled.
Action: Create a primary key constraint on the master table or enable the existing
constraint.
ORA-23417: unknown materialized view type: string
Cause: A fast refresh is being performed on a materialized view of an unknown or
unsupported type.
Action: Check all_mviews and ensure that the materialized view being refreshed a
valid materialized view.
ORA-23418: cannot unregister the propagator who is currently in use
Cause: The propagator is currently used in propagating replication RPCs.
Action: Try again later when there is no transaction active in propagating replication
RPCs.
ORA-23419: regenerate replication support before resuming master activity
Cause: There are tables in the object group that require regeneration of replication
support.
Action: Check the generation_status column in the all_repobjects view. Regenerate
replication support for any table in the object group with a 'NEEDSGEN' status.
Resume master activity.
ORA-23420: interval must evaluate to a time in the future
Cause: The parameter "interval" evaluates to a time earlier than SYSDATE.
Action: Choose an expression that evaluates to a time later than SYSDATE.
ORA-23421: job number string is not a job in the job queue
Cause: There is no job visible to the caller with the given job number.
Action: Choose the number of a job visible to the caller.
ORA-23422: Oracle Server could not generate an unused job number
Cause: Oracle Server could not generate a job number that was not used to identify
another job.
ORA-23423: job number string is not positive
Cause: The given job number is less than 1.
Action: Choose a positive integer.
ORA-23424: materialized view "string"."string" at string not registered
Cause: The specified materialized view has not be successfully registered at this site.
ORA-19999 to ORA-24279 71-49
Action: Register the materialized view manually at either the master site or the
materialized view site.
ORA-23425: invalid materialized view identifier string
Cause: The argument provided to dbms_mview.purge_mview_from_log is an invalid
materialized view identifer or it does not identify an Oracle 8 fast refreshable
materialized view or the materialized view has been already purged.
Action: If the materialized view is an Oracle 8 fast refreshable materialized view then
provide purge_mview_from_log with its valid materialized view identifier.
ORA-23426: deferred RPC queue has entries for string
Cause: The requested action cannot be performed until the queue is empty for the
given site/dblink
Action: Use dbms_defer_sys.push, dbms_defer_sys.purge_queue or
dbms_defer_sys.delete_tran to empty the queue.
ORA-23427: deferred purge queue argument string out of range
Cause: Specified numeric argument to dbms_defer_sys.purge_queue is invalid.
ORA-23428: job associated instance number string is not valid
Cause: A job is associated with an instance that is not running.
Action: Choose a running instance for job affinity, or set force parameter to TRUE.
ORA-23430: argument "string" cannot be NULL or empty string
Cause: The caller has provided an argument whose value cannot be NULL or the
empty string.
Action: Check that the varchar2 value provided is not NULL or the empty string, and
retry the call.
ORA-23431: wrong state: string
Cause: The routine was executed against a replicated object group that was in the
wrong state.
Action: Make sure that the replicated object group is in the state given in the error
message.
ORA-23432: master site string already exists
Cause: An attempt was made to instantiate a replicated object group at a master site
that was already a part of the object group.
Action: If you were trying to add this site, do nothing because it already exists;
otherwise, pick the name of another site, and re-run the routine.
ORA-23433: executing against wrong master site string
Cause: An attempt was made to execute the routine at a site that is different from the
site specified in the argument of the routine.
Action: Provide an argument to the routine that correctly indicates the site against
which the routine should be executing.
ORA-23434: master site string not known for object group
Cause: The site name given as an argument to a routine was not already known to the
replicated object group.
Action: Execute the dbms_offline_og.begin_instantiation() routine to add a new site to

the replicated object group.
ORA-23435: cannot create an updatable ROWID materialized view with LOB
columns
Cause: The propagation of LOB data from materialized view sites to the master site
requires a primary key on the replicated table. Thus updatable ROWID materialized
views that contain LOB columns are not supported.
Action: Create a primary key materialized view instead of a ROWID materialized
view. If the materialized view already exists, it can be converted to a primary key
materialized view using the ALTER MATERIALIZED VIEW DDL command.
ORA-23436: missing template authorization for user
Cause: The specified template authorization does not exist.
Action: Check the values for user name and refresh template name to ensure a valid
row exists in the DBA_REPCAT_USER_AUTHORIZATIONS view.
ORA-23437: template authorization already exists for user
Cause: The specified user already has been authorized to use the specified refresh
group template.
Action: Check the values for user name and refresh template name or query the
DBA_REPCAT_USER_AUTHORIZATIONS view to ensure that the correct values
were passed as parameters.
ORA-23438: missing refresh group template
Cause: The specified refresh group template does not exist.
Action: Verify that the refresh group template does not exist by querying the
DBA_REPCAT_REFRESH_TEMPLATES view.
ORA-23439: refresh group template already exists
Cause: The specified refresh group template already exists.
Action: Verify that the refresh 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.
Action: Correct the value of the public template parameter. It must be 'Y','N' or
NULL.
ORA-23441: object does not exist for refresh group template
Cause: The specified object does not exist in the refresh group template.
Action: Correct the object name and object type parameters. Check the
DBA_REPCAT_TEMPLATE_OBJECTS view to verify the correct name and type of
the object.
ORA-23442: object already exists for the refresh group template
Cause: The specified object already exists in the refresh group template.
Action: Change the object name and object type parameters. Query the
DBA_REPCAT_REMPLATE_OBJECTS view to verify the correct name and type of
the object.
ORA-19999 to ORA-24279 71-51
ORA-23443: missing template parameter

Cause: The specified template parameter does not exist.
Action: Correct the template parameter value and execute the procedure again. Use
the DBA_REPCAT_TEMPLATE_PARMS view to verify the name of the refresh group
template and parameter name.
ORA-23444: duplicate template parameter
Cause: The template parameter already exists for the specified refresh group
template.
Action: Correct the template parameter value and execute the procedure again. Use
the DBA_REPCAT_TEMPLATE_PARMS view to verify the name of the refresh group
template and parameter name.
ORA-23445: missing template site
Cause: The template site specified by the site name, user name and refresh group
template name does not exist.
Action: Correct the invalid parameter and execute the procedure again. Use the
DBA_REPCAT_TEMPLATE_SITES view to query the existing template sites.
ORA-23446: duplicate template site
Cause: The template site specified by the site name, user name and refresh group
template name already exists.
DBA_REPCAT_TEMPLATE_SITES view to query the existing template sites.
ORA-23447: missing user parameter value
Cause: The user parameter value specified by the user name, parameter name and
refresh group template name does not exist.
DBA_REPCAT_USER_PARMS view to query the existing user parameters.
ORA-23448: duplicate user parameter value
Cause: The user parameter value specified by the user name, parameter name and
refresh group template name already exists.
DBA_REPCAT_USER_PARMS view to query the existing user parameters.
ORA-23449: missing user name
Cause: The user specified by the user name parameter does not exist in the database.
Action: Correct an invalid user name or create the user in the master database. Use
the DBA_USERS view to select the valid database users.
ORA-23450: flavor already contains object "string"."string"
Cause: The flavor already contains the specified object.
Action: Check that the specified object is correct. To add all columns of a table object,
delete the object from the flavor and then add it again.
ORA-23451: flavor string already defined for object group "string"."string"
Cause: The given object group already contains a (possibly unpublished) definition of
the specified flavor.
Action: Check the spelling of the flavor name. Check for an unpublished flavor of the
desired name.
ORA-23452: flavor string of object group "string"."string" is already published
Cause: The given object group already contains a (published) definition of the
specified flavor.
Action: Check the spelling of the flavor name.
ORA-23453: requested operation is not supported on top flavor
Cause: The TOP flavor has a NULL name and may not be directly defined or deleted.
Action: Supply the name of a flavor other than the TOP flavor or use dbms_repcat
routines to implicitly change the TOP flavor.
ORA-23454: flavor string not defined for object group "string"."string"
Cause: The given object group does not contain a (published) definition of the
specified flavor.
Action: Check the spelling of the flavor name. Ensure the flavor has been defined
(and published) for the object group.
ORA-23455: flavor string contains object "string"
Cause: The given flavor contains the object to be dropped.
Action: Purge the flavor or choose another object to drop.
ORA-23456: flavor string does not contain "string"
Cause: The flavor does not contain the given object, column, or attribute.
Action: Either drop the flavor or choose a different object, column, or attribute.
ORA-23457: invalid flavor ID string
Cause: The given flavor ID is invalid.
Action: Make sure this flavor has been instantiated. If the flavor ID is outside the
range (-2147483647, 2147483647), contact customer support.
ORA-23458: inappropriate flavor string at string
Cause: The given flavor at the given database prevents the operation from
succeeding.
Action: Either change the database flavor or choose a different operation.
ORA-23459: flavor string must contain "string"
Cause: The flavor must contain the given object, column, or attribute.
Action: Either choose a different database flavor or ensure the object, column, or
attribute is available.
ORA-23460: missing value for column string in resolution method "string" for
"string"."string"."string"
Cause: before resolving conflicts, some values necessary resolving conflicts are not
available, or after resolving conflicts, some values necessary for re-trying of the SQL
are not available
Action: define appropriate flavors, provide necessary values through availability
vector in USER FLAVOR FUNCTION for conflict resolution
ORA-23461: fail to resolve conflict for "string"."string"."string"
ORA-19999 to ORA-24279 71-53
ORA-23462: flavor string in use at site string

Cause: The given flavor cannot be deleted because it is being used at the given site.
Action: Change the flavor of the site, or unregister it if it is a materialized view site.
ORA-23463: flavor incompatible with object "string"."string"
Cause: An existing flavor includes the specified object with an incompatible type.
Action: Change the type of the object, or delete the flavor if it is not in use.
ORA-23464: flavor lacks column string of "string"."string"
Cause: The flavor includes some columns of an object group but not all the required
columns.
Action: Change the flavor definition to include all required columns.
ORA-23465: flavor already includes column string of "string"."string"
Cause: The flavor includes the specified column which is being added.
Action: Check that the specified column is correct.
ORA-23466: flavor requires missing object "string"."string"
Cause: The flavor includes the specified object which does not exist
Action: Check that the specified object name is correct, and create the object if
appropriate.
ORA-23467: flavor lacks object "string"."string"
Cause: The flavor does not include the specified object which is being dropped.
Action: Check that the specified object is correct.
ORA-23468: missing string string
Cause: The template is missing the object with the specified key.
Action: Add the object to the template.
ORA-23469: string is different between templates
Cause: The values for the specified columns are different in each template for the
same key values.
Action: Correct the column values to make the templates the same.
ORA-23470: invalid status
Cause: The status should be DELETED, INSTALLING or INSTALLED. Any other
status is invalid.
Action: Check that the specified status value is correct.
ORA-23471: template not authorized for user
Cause: The refresh template is private and the user has not been authorized to
instantiate the template.
Action: Authorize the user to use the template.
ORA-23472: materialized view "string"."string" must be atomically refreshed
Cause: Non-atomic refresh is not supported for the specified materialized view.
Action: Set the value of the ATOMIC parameter to FALSE in the refresh procedure
being used or remove the specified materialized view from the set of materialized
views being refreshed.
ORA-23473: replication RPC processing for "string"."string" is disabled

Cause: The processing of replication RPCs for the object group that contains this
object is disabled. This includes RPCs in the error queue.
Action: Processing of replication RPCs is disabled when the object group is being
offline instantiated. Wait until offline instantiation is finished.
ORA-23474: definition of "string"."string" has changed since generation of
replication support
Cause: The current columns in the specified table and their column types do not
match the columns and column types when replication support was last generated.
Action: Regenerate replication support for the affected table. All flavors that include
the specified table should be checked for validity. Types for any UDT columns 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
replication propagation.
Action: Make sure every key column is sent and compared.
ORA-23476: cannot import from string to string
Cause: This object was imported from a database with a different global name than
the importing database.
Action: Only import this object into a database with the same global name.
ORA-23477: unable to alter propagation mode for object group "string"."string"
Cause: The propagation method of a materialized view object group can only be
altered when no other object groups with the same master object group are sharing
the materialized view site.
Action: Ensure that there are no other materialized view object groups at the local site
with the same master object group.
ORA-23478: object group "string" is already mastered at string
Cause: There is at least one other materialized view repgroup at the local site with the
same group name but a different master site.
Action: Ensure that all materialized view repgroups at the local site with the same
group name have the same master.
ORA-23480: Column string is not a top-level column of "string"."string".
Cause: The column is either not a top-level column or is not present in the table or
materialized view.
Action: Ensure only valid top-level columns are used.
ORA-23481: unexpected name string "string"
ORA-23482: column string of "string"."string": object types not allowed.
Cause: The column is of Object Type.
Action: Ensure that all the columns are not of Object Type.
ORA-23483: object "string"."string" not allowed in this operation.
Cause: The specified operation does not support the given object.
Action: Do not invoke the operation for this object.
ORA-19999 to ORA-24279 71-55
ORA-23484: internal internet Application Server error: string

Cause: An internal error occurred in internet Application Server.
ORA-23485: Column group "string" must consist of a single numeric column only
Cause: The column group doesn't contain only one numeric column.
Action: Use a column group containing a single numeric column.
ORA-23487: object groups "string"."string" and "string"."string" do not have the
same connection qualifier
Cause: The specified two object groups do not have the same connection qualifier.
Action: Do not invoke the operation on the above object groups, or ensure they have
the same connection qualifier.
ORA-23488: propagation mode "string" for "string" is not allowed for this operation
Cause: This operation does not support the specified dblink in the above propagation
mode.
Action: Do not invoke the operation for this dblink, or change the propagation mode
for this dblink.
ORA-23489: duplicate entry "string"
Cause: The specified value is duplicated in the parameter list.
Action: Remove duplicated entries in the parameter list.
ORA-23490: extension request "string" with status "string" not allowed in this
operation
Cause: The specified operation is not allowed for the extension request with the
specified status.
Action: Ensure the extension request has the appropriate status before retrying this
operation.
ORA-23491: no valid extension request at "string"
Cause: The specified database does not have a valid extension request.
Action: Ensure there is a valid extension request in DBA_REPEXTENSIONS view
before retrying this operation.
ORA-23492: no new sites for extension request "string"
Cause: There is no new site with the specified extension request.
Action: Ensure there is at least one new site in DBA_REPSITES_NEW view for this
request before retrying this operation.
ORA-23493: "string" is not a new site for extension request "string"
Cause: The specified extension request does not include the specified site as a new
site.
Action: Ensure the specified site is a new site for this extension request before retrying
this operation.
ORA-23494: too many rows for destination "string"
Cause: The specified destination has too many rows in system.def$_destination table.
Action: Ensure the specified destination has at most two valid rows before retrying
this operation.
ORA-23495: serial propagation can not be used for "string"

Cause: The sites involved may be in the process of adding a new site without
quiescing.
Action: Check the def$_destination table for this destination and try parallel
propagation.
ORA-23496: can not change disabled status for "string" and "string"
Cause: The disabled status for this site is set internally for synchronization during
adding a new master without quiescing.
Action: Ensure adding a new master without quiescing finished before invoking this
procedure.
ORA-23497: repgroup name cannot be null
Cause: The array of Repgroup names contains a null value.
Action: Ensure that the array of Repgroup names is dense and is not null terminated.
ORA-23498: repgroups specified must have the same masters
Cause: The Repgroup names specified do not have the same masters.
Action: Ensure that the Repgroup names specified have the same masters.
ORA-23500: cannot switch master for a multi-tier materialized view repgroup
"string"."string"
Cause: An attempt was made to switch master for a materialized view repgroup
when its parent repgroup is also a materialized view repgroup. This is not allowed.
Action: Drop and recreate the materialized view repgroup based on a proper parent
repgroup.
ORA-23501: refresh template cannot be instantiated for database with compatibilty
equal to or less than 8.0
Cause: Instantiation of a refresh template is not supported for database compatibility
8.0 or less.
Action: Be sure the database compatibility is 8.1 or above.
ORA-23502: valid directory for offline instatiation is not specified
Cause: An attempt was made to offline instantiate to a directory which is not
specified or null.
Action: There are two ways to specify the directory: o As a parm offline_dirpath to
the API o As an init.ora parm named utl_file_dir Make sure you have specified an
appropriate directory in which the offline file can be created.
ORA-23503: error occurred during IAS instantiation
Cause: An attempt was made to instantiate a IAS site. Error occurred during IAS
instantiation.
Action: See other errors on the error stack to look for the source of the problem. If the
error still persists, contact Oracle Support.
ORA-23504: columns added to table do not match list of columns to be added
Cause: The list of columns passed as a parameter does not match the columns to be
added to the table.
Action: Correct the DDL string or list of columns and rexecute.
ORA-19999 to ORA-24279 71-57
ORA-23505: Object "string"."string" is missing.

Cause: The specified object does not exist.
Action: Check that the specified object is correct.
ORA-23514: invalid or incorrect number of arguments
Cause: The arguments passed to the online redefinition API were invalid or missing.
Action: Call the online redefinition API with the right number of valid arguments.
ORA-23515: materialized views and/or their indices exist in the tablespace
Cause: An attempt was made to drop a tablespace which contains materialized views
and/or their indices.
Action: Drop the materialized views in this tablespace. Also, find indices belonging to
materialized views in this tablespace and drop then. Then try dropping the
tablespace.
ORA-23531: site owner already exists in the template.
Cause: Site owner for the template already exists.
Action: Do not create multiple siteowners for this template.
ORA-23532: tables with different synchronization mechanisms are in the same
group
Cause: Tables belonging to the same replication group were specified to be cached
with different synchronization mechanisms.
Action: Do not specify different synchronization mechanisms while caching tables
belonging to the same replication group.
ORA-23533: object "string"."string" can not be cached
Cause: An attempt was made to cache an object which is not supported.
Action: Do not cache an object which is not supported.
ORA-23534: missing column in materialized view container table "string"."string"
Cause: After import, the materialized view container table has missing columns.
Action: Check if materialized view container table was imported correctly.
ORA-23535: instantiating templates from multiple back ends is not allowed.
Cause: An attempt was made to set a new non-null back end database for an iAS site.
Action: Call dbms_ias_configure.set_back_end_db procedure with null dblink. Then,
call the same procedure with the new non-null dblink.
ORA-23536: the object "string"."string" is not cached at the middle tier as expected.
Cause: The object may have been dropped or renamed at the back end after
dbms_ias_inst.start_ias_inst was executed.
Action: Check the validity of the object at the back end and retry the instantiation.
ORA-23537: function or procedure string is not allowed to be invoked from this
site.
Cause: This function or procedure is restricted to the backend or middle tier site
Action: Connect to the proper site before calling this function or procedure.
ORA-23538: cannot explicitly refresh a NEVER REFRESH materialized view

("string")
Cause: An attempt was made to explicitly refresh a NEVER REFRESH MV.
Action: Do not perform this refresh operation or remove the MV(s) from the list.
ORA-23539: table "string"."string" currently being redefined
Cause: An attempt was made to redefine a table which is currently involved in an
ongoing redefinition.
Action: Do not perform this redefinition operation on this table or wait till the
ongoing redefinition of the table is completed.
ORA-23540: Redefinition not defined or initiated
Cause: An attempt was made to continue or complete a redefinition which was not
defined or initiated.
Action: Define or initiate the redefinition before performing this operation.
ORA-23541: tables do not match tables used while defining the redefinition
Cause: An attempt was made to continue or complete a redefinition by providing
different tables than those used while defining or initiating the redefinition.
Action: Repeat this operation and specify the same tables as those that were specified
while defining or initiating the redefinition.
ORA-23542: dependent object "string"."string" already registered
Cause: An attempt was made to register an already registered dependent object to an
Action: Do not attempt to register an already registered dependent object to an
ORA-23543: materialized view log on "string"."string" is in an inconsistent state
Cause: There was an error while creating the materialized view log and the log is
currently in an inconsistent state. A possible cause could be that schema redefinition
has occurred on the master table while the log was being created. Another possible
cause could be that there were DMLs being applied on the master table concurrently
in another session at the time the materialized view log creation started and those
DML transactions haven't committed even after a very long period of time.
Action: Drop the materialized view log and recreate it.
ORA-23546: cannot create rowid mapping table string.string
Cause: The online partition mover could not create a rowid mappping table.
Action: Rename the conflicting table or rerun the SQL statement. * There may be a
concurrent online operation on the same object.
ORA-23547: dml_lock_timeout value is out of the permitted range
Cause: The value for dml_lock_timeout was out of the permitted range of 0 to
1,000,000.
Action: Use a value within the range of 0 to 1,000,000 and reexecute the procedure
ORA-23600: cannot create PROPAGATION, string already exists
Cause: The propagate_name already exists.
Action: Drop the propagate_name usign DROP_PROPAGATEcommand or specify
propagate_name.
ORA-19999 to ORA-24279 71-59
ORA-23601: PROPAGATION_NAME string does not exist

Cause: Propagation does not exist.
Action: Query DBA_PROPAGATION view to find existing propagation_name
ORA-23602: Invalid string process type string
Cause: Specified GoldenGate, XStream or Streams process type is not valid.
Action: Specify either capture or apply.
ORA-23603: string enqueue aborted due to low SGA
Cause: An attempt to enqueue a GoldenGate, XStream or Streams message was
aborted because ORACLE is running low on memory allotted.
Action: Either start consuming messages by enabling any GoldenGate, XStream or
Streams propagation or apply which might be disabled. An alternative is to allot more
memory to STREAMS, which can be done by increasing the streams_pool_size
initialization parameter if one was defined or by increasing the shared_pool_size.
ORA-23605: invalid value "string" for string parameter string
Cause: An attempt was made to specify an invalid parameter value.
Action: Specify a valid value for the parameter. Check the documentation for valid
parameter values.
ORA-23606: invalid object string
Cause: An attempt was made to specify an invalid object.
Action: Specify a valid object.
ORA-23607: invalid column "string"
Cause: An invalid column was specified in the column list.
Action: Check the columns in the object and specify the right column name.
ORA-23608: invalid resolution column "string"
Cause: An invalid column was specified as the resolution column. The resolution
column must belong to the list of columns specified in the 'column_list' parameter.
Action: Check the columns in the column_list and specify the right resolution column
name.
ORA-23609: unable to find directory object for directory string
Cause: There was no entry in ALL_DIRECTORIES corresponding to the specified
directory.
Action: Grant to the current user appropriate privileges on either a new directory
object or an existing directory object.
ORA-23610: internal dbms_streams_tablespaces error: [string] [string] [string]
[string]
Cause: Streams detected an erroneous result.
Action: Look for information in the session trace file and contact customer support.
ORA-23611: tablespace "string" has more than one data file
Cause: The specified tablespace had more than one data file and hence did not qualify
as a simple tablespace.
Action: Choose a self-contained tablespace with a single data file, or use a procedure
that supports any tablespace.
ORA-23612: unable to find tablespace "string"

Cause: Either the tablespace did not exist, or the current user did not have sufficient
privileges on the tablespace.
Action: Grant appropriate privileges on the tablespace to the current user or choose a
different tablespace.
ORA-23613: Script string already exists
Cause: A script for the specified invoking package already existed.
Action: Complete the previous invocation or drop the previous invocation before
proceeding with the current invocation.
ORA-23614: Script string does not exist
Cause: The named script did not exist.
Action: Create the script.
ORA-23615: Block number string does not exist for script string
Cause: The specified block number did not exist for the script.
Action: Add the block or check the block number and reexecute.
ORA-23616: Failure in executing block string for script string with \nstring
Cause: The execution of specified block failed.
Action: Check the error. Query DBA_RECOVERABLE_SCRIPT_BLOCKS to view the
failed block. Rectify and rerun the block or script.
ORA-23617: Block string for script string has already been executed
Cause: The specified block was already executed.
Action: Check the block number and reissue the command.
ORA-23618: Generation of script string is not complete.
Cause: Script generation for the specified script was not completed in a prior
invocation.
Action: Purge the specified script by calling the RECOVER_OPERATION API in the
package DBMS_STREAMS_ADM and reattempt the entire operation.
ORA-23619: non-Oracle system error: string
Cause: A non-Oracle database has returned an error message to STREAMS when
attempting to apply a DML statement. The non-Oracle system error message is a
parameter to this Oracle error.
Action: Corrective action may or may not be possible (depending on the non-Oracle
system error). If corrective action is possible, correct the problem and try applying the
transaction again.
ORA-23620: bind value size too large for PL/SQL CALL operation
Cause: In a PL/SQL CALL to a stored procedure, the bind string size exceeded 4K.
Action: Either make the bind string size shorter (less than 4K) or use BEGIN-END to
call the procedure instead of CALL.
ORA-23621: Operation corresponding to script string is in progress.
Cause: The script was already being run in a different session or was terminated
before status for the script was updated to ERROR or EXECUTED.
ORA-19999 to ORA-24279 71-61
Action: Make sure the script is not being run in a parallel session. Then call the
RECOVER_OPERATION API in the DBMS_STREAMS_ADM package with the
appropriate OPERATION_MODE argument.
ORA-23622: Operation string.string.string is in progress.
Cause: An attempt was made to execute a procedure which was being executed in a
parallel session or failed execution.
Action: Query the DBA_RECOVERABLE_SCRIPT view to identify the operation that
is currently in progress for the specified invoking procedure. Complete the operation
before proceeding.
ORA-23623: internal DBMS_COMPARISON error: [string] [string] [string] [string]
Cause: DBMS_COMPARISON detected an erroneous result.
Action: Look for information in the session trace file and contact Oracle Support
Services.
ORA-23624: A comparison operation is currently in progress for string.
Cause: Another session was already performing an operation on this object.
Action: Retry the operation once other sessions are done with the specific comparison
object.
ORA-23625: Table shapes of string.string and string.string@string did not match.
Cause: Table shapes of local and remote tables to compare did not match.
Action: Retry by explicitly specifying columns that match in column_list or create
views on the tables as appropriate.
ORA-23626: No eligible index on table string.string
Cause: Table did not have an eligible index to use for comparison.
Action: For a table to be compared using DBMS_COMPARISON, the table must have
an appropriate index on a column of certain data types. Check the documentation for
supported data types.
ORA-23627: Comparison object string already existed.
Cause: A comparison object by the specified name already exists.
Action: Retry with a different name.
ORA-23628: Comparison query too long (actual string, allowed string).
Cause: A generated query for comparison was too long.
Action: Comparison is unsupported for very large tables with long column names.
Retry with a subset of columns or with shorter column names.
ORA-23629: string.string is not an eligible index on table string.string for
comparison
Cause: The specified index was not an eligible index to use for comparison.
an appropriate index. Please specify an eligible index for the table to be compared.
ORA-23630: Cannot switch to apply-state checkpoint mode (value "string", string
parameter string), due to the following reason:
Cause: Could not switch to apply-state checkpoint mode, or already in apply-state
checkpoint mode.
Action: Can switch to apply-state checkpoint mode only if the capture is new (it never
ran), the capture wasn't cloned from a capture with checkpoints, the capture doesn't
include any extra attributes, and combined capture and apply is enabled.
ORA-23631: apply-state checkpoint mode cannot change (value "string", string
parameter string)
Cause: Could not switch to checkpoints because apply-state checkpoint mode was set.
Action: Drop the apply-state checkpoint capture and create a new one that will / take
checkpoints.
ORA-23632: Cannot force checkpoints in apply-state checkpoint mode (value
"string", string parameter string)
Cause: The capture process was in apply-state checkpoint mode.
Action: Cannot take checkpoints in apply-state checkpoint mode.
ORA-23633: Cannot turn off combined capture and apply mode in apply-state
checkpoint mode (value "string", string parameter string)
Cause: The capture was running in apply-state checkpoint mode and had to run in
combined capture and apply mode also.
Action: Ensure that this capture runs in combined capture and apply by dropping
additional propagation or apply processes for the same queue.
ORA-23634: Cannot include extra attributes in apply-state checkpoint mode
Cause: The capture process was in apply-state checkpoint mode.
Action: Extra attributes are not supported in apply-state checkpoint mode.
ORA-23635: MAINTAIN_TTS: tablespace(s) already exist(s) in target database.
Cause: The tablespaces were already in existence in the target database when the
streams MAINTAIN_TTS APIs were called."
Action: Check whether you can drop the tablespaces to be maintained in the target
database. If not, don't use streams MAINTAIN_TTS APIs to setup streams. Check the
Oracle documentation on how to setup streams.
ORA-23636: MAINTAIN_TTS: Invalid tablespace name, reason: string.
Cause: The tablespace name was either NULL or too long when the streams
MAINTAIN_TTS APIs were called.
Action: Check that the specified tablespace names are not NULL and are spelled
correctly. If there are too many tablespaces, group them together and call the streams
MAINTAIN_TTS APIs for the group.
ORA-23637: Capture started in checkpoint mode
ORA-23638: Capture cloned from a capture with checkpoints
ORA-23639: Extra Attribute included
ORA-23640: Combined capture and apply disabled
ORA-23641: Capture started in apply-state checkpoint mode already
ORA-23642: Cannot switch to checkpoint mode (value "string", string parameter
string)
Cause: Capture was cloned from a capture in apply-state checkpoint mode.
ORA-19999 to ORA-24279 71-63
Action: Clone from a capture with checkpoints.

ORA-23643: Capture cloned from a capture in apply-state checkpoint mode
ORA-23644: Cannot switch to apply-state checkpoint mode (Capture string)
Cause: Switch to apply-state checkpoint mode was prevented by a previous error.
Action: See the previous error for the appropriate action.
ORA-23645: Cannot switch to checkpoints (Capture string)
Cause: Switch to checkpoints was prevented by a previous error.
Action: See the previous error for the appropriate action.
ORA-23646: string string process string does not exist
Cause: Capture or Apply did not exist.
Action: Create a Capture or Apply process, then try again.
ORA-23647: string string process string is not running
Cause: Capture or Apply were not running.
Action: Start Capture or Apply process, then try again
ORA-23648: Capture string is for Change Data Capture
Cause: Capture was for Change Data Capture, and checkpoints were required.
Action: None
ORA-23649: Capture string is for Audit Vault
Cause: Capture was for Audit Vault, and checkpoints were required.
Action: None
ORA-23650: No progress Capture string
Cause: Capture was not capturing changes.
Action: Make sure Capture is running and capturing changes.
ORA-23651: Capture string is already in string mode
Cause: Capture was already in the desired mode.
Action: None
ORA-23652: The oldest SCN could not be updated at Apply string
Cause: The oldest SCN was not updated before the switch was performed.
Action: Make sure Apply is running and the switch package version is the same at
both databases.
ORA-23653: LogMiner session does not exist
Cause: LogMiner session did not exist.
Action: Make sure the Capture process exists.
ORA-23654: Attempting to set the oldest SCN to a greater value (string) than the
current one (string) at Apply string
Cause: The new value for the oldest SCN was not computed correctly.
Action: Make sure Capture and Apply are running, and Capture is making progress.
ORA-23655: The SCN range cannot be smaller than 0, (SCN range = string)
Cause: The function was invoked with a negative SCN range.
Action: Use a positive SCN range.
ORA-23656: Timeout occurred while string string process string
Cause: The GoldenGate, XStream or Streams process could not be stopped or started.
Action: Call the switch procedure again.
ORA-23657: the converted file string already exists
Cause: The converted file was already in existence. CONVERT FILE call does not
overwrite the existing file.
Action: Check whether the existing file can be deleted. If the existing file can be
deleted, delete it. Otherwise, specify a different directory or file extension.
ORA-23658: Invalid character set specified when converting column 'string' in
'string.string'
Cause: The conversion between two character sets for the column in the given table is
not supported.
Action: Check if the implicit conversion between source and destination column is
supported.
ORA-23659: Destination buffer is not large enough when converting column
'string' in 'string.string' (actual length: string; maximum length: string)
Cause: The conversion between two character sets failed because a source column
value is too large for the destination column.
Action: Check if size of the source and destination column matches.
ORA-23660: Unable to load NLS data object when converting column 'string' in
'string.string'
Cause: It may be caused by invalid NLS environment setting.
Action: Check your NLS environment setting.
ORA-23661: Canon capture name "string" not found
Cause: There's no such capture process
Action: Pass the right parameter to the function
ORA-23662: subset rule length exceeds maximum allowed value
Cause: The length of an insert, update, or delete subset rule computed from the DML
condition input exceeded the maximum allowed length.
Action: Make the DML condition shorter.
ORA-23663: local object string.string is not a single table view
Cause: The view was based either on another view or multiple tables or views.
Action: For comparison, specify a view based on a single table.
ORA-23664: remote object string.string is not a single table view
Cause: The view was based either on another view or multiple tables or views.
Action: For comparison, specify a view based on a single table.
ORA-23665: DML conflict handler "string" not found
Cause: The DML conflict handler was not found for modification or removal.
ORA-19999 to ORA-24279 71-65
Action: Make sure the name of the conflict handler is correct and that it exists.
ORA-23666: Default column group in use by DML conflict handler "string"
Cause: A default column group was found for the specified Apply name, operation
name, and conflict type.
Action: Remove the existing default column group and retry.
ORA-23667: Column "string" already used by conflict handler "string"
Cause: The column was already in the column group of another conflict handler for
the specified Apply name, operation name, and conflict type.
Action: Remove the column from the other conflict handler or specify a different
column.
ORA-23668: Column "string" does not have a numeric data type.
Cause: The specified column did not have a numeric data type. Delta conflict
resolution requires numeric columns.
Action: Check the data type of the column and specify only numeric columns.
ORA-23669: Duplicate conflict handler name
Cause: A DML conflict handler with the specified name was found.
Action: Remove the current DML conflict handler or specify a different name.
ORA-23670: Duplicate column name "string"
Cause: The specified value was duplicated in the column group list.
Action: Remove duplicated entries from the column group list.
ORA-23671: Default column group required
Cause: A default column group was not specified. The specified Apply name,
operation name, and conflict type is only supported on default column groups.
Action: Specify a default column group.
ORA-23672: Column not specified in column group for DML conflict handling for
table "string"."string"
Cause: The specified table contained a column that was not specified as part of a
column group.
Action: Add the column to a column group.
ORA-23673: Invalid resolution column "string" for table "string"."string"
Cause: The specified resolution column was not valid.
Action: Set the resolution column to a valid column.
ORA-23674: Unable to handle delta conflict resolution for table "string"."string"
Cause: The specified table or the LCR contained a null value in one of the columns
belonging to a delta conflict group.
Action: Correct each delta column in the table or the error LCR if it currently has a
null value.
ORA-23675: Unsupported OPERATION_NAME, CONFLICT_TYPE, and
METHOD_NAME
Cause: The specified OPERATION_NAME, CONFLICT_TYPE, and
METHOD_NAME was not a valid set of parameters.
Action: Retry with a valid set of parameters.
ORA-23676: no eligible index on local table "string"."string"

Cause: The local table did not have an eligible index to use for comparison.
ORA-23677: no eligible index on remote table "string"."string"
Cause: The remote table did not have an eligible index to use for comparison.
ORA-23678: index "string"."string" on local table "string"."string" is not eligible for
comparison
Cause: The specified index was not eligible for comparison.
an appropriate index. Specify an eligible index for the table to be compared.
ORA-23679: index "string"."string" on remote table "string"."string" is not eligible
for comparison
Cause: The specified index was not eligible for comparison.
an appropriate index. Specify an eligible index for the table to be compared.
ORA-24000: invalid value string, string should be of the form [SCHEMA.]NAME
Cause: An invalid value was specified for the paramerter.
Action: Specify a string of the form [SCHEMA.]NAME .
ORA-24001: cannot create QUEUE_TABLE, string already exists
Cause: The queue table already exists in the queueing system.
Action: Drop the table first using the DROP_QUEUE_TABLE() command or specify
another table.
ORA-24002: QUEUE_TABLE string does not exist
Cause: Queue_table not exist.
Action: Query on the user view USER_QUEUE_TABLES to find out existing queue
tables.
ORA-24003: Queue table index string inconsistent with queue table string
Cause: The queue table index has not yet been successfully imported.
Action: Import the queue table index before attempting to use the queue table. If the
import failed, correct the problem and try to import the queue table index again.
ORA-24004: invalid column name string in SORT_LIST, should be ENQ_TIME or
PRIORITY
Cause: Invalid column name was specified in the SORT_LIST.
Action: The valid column names are ENQ_TIME and PRIORITY.
ORA-24005: Inappropriate utilities used to perform DDL on AQ table string.string
Cause: An attempt was made to use the SQL command DROP TABLE or TRUNCATE
TABLE or ALTER TABLE on queue metadata or tables.
ORA-19999 to ORA-24279 71-67
Action: Use the DBMS_AQADM.DROP_QUEUE_TABLE to DROP TABLE,

DBMS_AQADM.PURGE_QUEUE_TABLE to TRUNCATE TABLE. ALTER TABLE
redefinition based on only ALTER_TABLE_PROPERTIES and
ALTER_TABLE_PARTITIONING clauses are allowed.
ORA-24006: cannot create QUEUE, string already exists
Cause: The queue requested to be created already exists.
Action: Specify another queue name. Query USER_QUEUES for all the exisiting
queues in the users's schema.
ORA-24007: invalid value string, MAX_RETRIES should be non-negative integer
Cause: An invalid value was specified for MAX_RETRIES.
Action: Specify a non-negative integer.
ORA-24008: queue table string.string must be dropped first
Cause: An error was detected when dropping a queue table in a cluster, tablespace, or
schema.
Action: Use the DBMS_AQADM.DROP_QUEUE_TABLE procedure to drop the
specified queue table first; then, retry the operation.
ORA-24009: invalid value string, QUEUE_TYPE should 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 the valid queues.
ORA-24011: cannot drop QUEUE, string should be stopped first
Cause: The queue has not been stopped i.e. either enqueue or dequeue is still enabled.
Action: Stop the queue first using the STOP_QUEUE command and disable it from
both enqueueing and dequeueing.
ORA-24012: cannot drop QUEUE_TABLE, some queues in string have not been
dropped
Cause: A queue exists in the queue table which has not been dropped. All queues
need to be dropped first.
Action: Drop all queues belonging to this queue table using the drop_queue()
command. Be sure to stop the queues appropriately before dropping them.
Alternately, use the force option in drop_queuetable.
ORA-24013: invalid value string, RETRY_DELAY should be non-negative
Cause: A negative value was specified for RETRY_DELAY.
Action: Specify a non-negative value for RETRY_DELAY.
ORA-24014: invalid value string, RETENTION_TIME should be FOREVER or nonnegative
Cause: Queue retention was specified, but the retention time was specified to be less
than zero.
Action: Specify the retention time to be non-negative or FOREVER. Alternately don't

specify retention.
ORA-24015: cannot create QUEUE_TABLE, QUEUE_PAYLOAD_TYPE string.string
does not exist
Cause: An invalid QUEUE_PAYLOAD_TYPE specified during create_queue_table.
Action: The QUEUE_PAYLOAD_TYPE should 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 specified for QUEUE_PAYLOAD_TYPE during
create_queue_table.
Action: The user should have execute priviliges on the object type specified for the
queue.
ORA-24017: cannot enable enqueue on QUEUE, string is an exception queue
Cause: User tried to enable enqueueing to an exception queue.
Action: None
ORA-24018: STOP_QUEUE on string failed, outstanding transactions found
Cause: There were outstanding transactions on the queue, and WAIT was set to false,
so STOP_QUEUE was unsucessful in stopping the queue.
Action: Set WAIT to TRUE and try STOP_QUEUE again. It will hang till all
outstanding transactions are completed.
ORA-24019: identifier for string too long, should not be greater than string
characters
Cause: The identifier specified is too long.
Action: Try again with a shorter identifier.
ORA-24020: Internal error in DBMS_AQ_IMPORT_INTERNAL, string
Cause: Internal Error occured in the package DBMS_AQ_IMPORT_INTERNAL.
Action: Internal error, call Oracle Support.
ORA-24021: queue table definition not imported for string.string
Cause: The queue definition is not updated because the queue table was not imported
properly
Action: Import the queue table again.
ORA-24022: the specified parameters has no effect on the queue
Cause: The parameter combination will not cause the queue to be started or stoped.
Action: None. This is just a warning.
ORA-24023: Internal error in DBMS_AQ_EXP_INTERNAL.string [string] [string]
Cause: Internal Error occured in the package DBMS_AQ_EXP_INTERNAL.
ORA-24024: Internal error in DBMS_AQ_IMP_INTERNAL.string [string] [string]
Cause: Internal Error occured in the package DBMS_AQ_IMP_INTERNAL.
ORA-19999 to ORA-24279 71-69
ORA-24025: invalid value string, QUEUE_PAYLOAD_TYPE should be RAW or an

object type
Cause: Parameter queue_payload_type has invalid value.
Action: Specify a valid object type or RAW.
ORA-24026: operation failed, queue string.string has errors
Cause: An attempt was made to enqueue, dequeue or administer a queue which has
errors.
Action: Drop the queue table setting the force option to true.
ORA-24027: AQ HTTP propagation encountered error, status-code string, string
Cause: AQ propagation's HTTP request to the propagation servlet at the specified
address encountered an error
Action: Specify a valid address in the connect string of the propagation destination
dblink, the dblink user has the correct permissions, check if the AQ propagation
servlet was properly installed.
ORA-24028: cannot create a reciever non-repudiable single consumer queue
Cause: Tried to create a reciever non-repudiable single consumer queue
Action: This feature is not supported
ORA-24029: operation not allowed on a single-consumer queue
Cause: Tried an operation not allowed on a single-consumer queue.
Action: Specify the operation on a multi-consumer queue.
ORA-24030: Only one of rule or rule-set must be specified
Cause: Specified both a rule and rule-set for the operation.
Action: Specify only one of rule or rule-set.
ORA-24031: invalid value, string should be non-NULL
Cause: Parameter is NULL.
Action: Specify a non NULL value for the parameter.
ORA-24032: object string exists, index could not be created for queue table string
Cause: Oracle AQ tried to create an index with the name specified in the error
message. The index could not be created for the specified queue table because a object
exists with the same name.
Action: Drop the object specified in the error message and retry the command. You
can also choose a different name for the queue table.
ORA-24033: no recipients for message
Cause: An enqueue was performed on a queue that has been set up for multiple
dequeuers but there were neither explicit recipients specified in the call nor were any
queue subscribers determined to be recipients for this message.
Action: Either pass a list of recipients in the enqueue call or add subscribers to the
queue for receiving this message.
ORA-24034: application string is already a subscriber for queue string
Cause: An application name that was already a subscriber for the queue was specified
in the dbms_aq.subscribe call.
Action: n/a
ORA-24035: AQ agent string is not a subscriber for queue string

Cause: An AQ agent that was not a subscriber for the queue was specified.
Action: Check the name and/or address of the agent and retry the call.
ORA-24036: invalid SORT_ORDER column string specified for 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
grouping.
Action: Change the sort order list in the create queue table command and retry the
call.
ORA-24037: schema string in QUEUE_NAME is not same as 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.
Action: Use the same schema name for both the QUEUE_NAME and QUEUE_TABLE
parameters and retry the command.
ORA-24038: RETRY_DELAY and MAX_RETRIES cannot be used for a 8.0
compatible multiple consumer queue
Cause: The CREATE_QUEUE or ALTER_QUEUE command was issued with a nonzero RETRY_DELAY and a QUEUE_TABLE that was created for multiple consumers
and with COMPATIBLE parameter set to '8.0'.
Action: Either set the RETRY_DELAY to zero or upgrade the queue table to 8.1
compatible using the DBMS_AQADM.MIGRATE_QUEUE_TABLE procedure.
ORA-24039: Queue string not created in queue table for multiple consumers
Cause: Either an ADD_SUBSCRIBER, ALTER_SUBSCRIBER, or
REMOVE_SUBSCRIBER procedure, or an ENQUEUE with a non-empty recipient list,
was issued on a queue that was not created for multiple consumers.
Action: Create the queue in a queue table that was created for multiple consumers
and retry the call.
ORA-24041: propagation schedule exists for QUEUE string and DESTINATION
string
Cause: A SCHEDULE_PROPAGATION was issued for a queue and destination pair
which has an existing propagation schedule.
Action: Issue UNSCHEDULE_PROPAGATION to remove the existing schedule and
then reissue the SCHEDULE_PROPAGATION call.
ORA-24042: no propagation schedule exists for QUEUE string and DESTINATION
string
Cause: AN UNSCHEDULE_PROPAGATION was issued for a queue and destination
pair which has no existing propagation schedule.
Action: Verify the spelling of the specified QUEUE and DESTINATION and then
reissue the call with the correct spelling.
ORA-24043: destination string uses a reserved name, names with AQ$_ prefix are
not valid
Cause: An attempt was made to specify a reserved name for a destination.
ORA-19999 to ORA-24279 71-71
Action: Enter a different value or NULL for the local destination. Then retry the
operation.
ORA-24044: source string and destination string object types do not match
Cause: A message recipient's queue has a different object structure than the sender's
queue. The message cannot be propagated.
Action: Either remove the recipient from the subscriber's list for the sender's queue or
create the destination queue with an object type that matches the source queue's
object type.
ORA-24045: invalid agent address string, agent address should be of the form
[SCHEMA.]NAME[@DATABASE LINK]
Cause: An invalid value was specified for the agent address parameter.
Action: Specify a string of the form [SCHEMA.]NAME[@DATABASE LINK].
ORA-24046: protocol attribute reserved for future use
Cause: The protocol attribute of the AQ agent object type 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 should be of the form NAME
Cause: An invalid value was specified for the agent name parameter.
Action: Specify a string of the form NAME. Then retry 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 internal AQ object types.
Action: Use the DBMS_AQADM.GRANT_TYPE_ACCESS procedure to grant the user
access to the AQ object types.
ORA-24049: invalid agent name string, names with AQ$_ prefix are not valid
Cause: An attempt was made to use a reserved prefix in the agent name.
Action: Enter a different value for the agent name. Then, retry the operation.
ORA-24050: subscribers are not supported for exception queue string
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.
ORA-24051: cannot propagate object type payloads that have a REF attribute
Cause: An ADD_SUBSCRIBER or ENQUEUE procedure with a non-NULL address
field in the agent type was issued on a queue whose payload has a REF attribute.
Propagation of object type payloads that have a REF attribute currently is not
supported.
Action: Specify an agent with a NULL address field so that the agent can dequeue
from the same queue. Or, change the object type definition to one that does not use
REF attributes.
ORA-24052: cannot propagate object type payloads with LOB attributes to an 8.0
release
Cause: The recipient of a message with LOB attributes was using an Oracle 8.0
release. Propagation of LOB attributes is supported only in Oracle 8.1 and higher
releases.
Action: Upgrade the target release to Oracle 8.1 and retry. Or, change the object type
definition to one that does not use LOBs.
ORA-24053: PRIMARY_INSTANCE and SECONDARY_INSTANCE must be nonnegative
Cause: One of PRIMARY_INSTANCE or SECONDARY_INSTANCE was negative.
Action: Specify non-negative integers for PRIMARY_INSTANCE and
SECONDARY_INSTANCE.
ORA-24054: cannot propagate to an Oracle 8.0.3 release or lower release
Cause: The recipient of a message was using an Oracle 8.0.3 release or lower release.
Propagation is supported only in Oracle 8.0.4 and higher releases.
Action: Upgrade the target release to Oracle 8.0.4 or higher and retry.
ORA-24055: cannot delete propagation status rows that are in prepared state
Cause: An attempt was made to use the internal administration procedure to delete
status rows from the SYS.AQ$_PROPAGATION_STATUS table that were in the
prepared state.
Action: Wait for the propagation to complete successfully before retrying the
operation.
ORA-24056: internal inconsistency for QUEUE string and destination string
Cause: The sequence numbers used in the SYS.AQ$_PROPAGATION_STATUS table
were inconsistent for the given queue and destination.
ORA-24057: cannot define subscriber with rule for queue string
Cause: An ADD_SUBSCRIBER or ALTER_SUBSCRIBER procedure with a rule was
issued on a queue for which rule based subscribers are not supported. Rule based
subscribers currently are supported only for NORMAL (persistent) multi-consumer
queues created using an Oracle release 8.1.0 or higher compatible queue table.
Action: Create a NORMAL multi-consumer queue in an Oracle release 8.1.0 or higher
compatible queue table, and retry the call. Or, if the queue is a normal (persistent)
multi-consumer queue, convert the queue table to Oracle 8.1.0 or higher compatibility
and retry.
ORA-24058: cannot downgrade QUEUE_TABLE that has propagation in a prepared
state
Cause: An attempt was made to downgrade the queue table when there were
messages being propagated that were in the prepared state.
Action: Wait for the propagation to complete before retrying the operation.
ORA-24059: invalid COMPATIBLE parameter setting string specified in
DBMS_AQADM.string
Cause: An invalid compatible parameter was specified in the DBMS_AQADM
procedure. The parameter setting must be of the form '8.x.y' where x is the release
number and y is the update number.
ORA-19999 to ORA-24279 71-73
Action: Specify a valid COMPATIBLE parameter setting, and retry the operation.
ORA-24060: cannot convert QUEUE_TABLE, string already is 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.
ORA-24061: cannot specify non-zero SECONDARY_INSTANCE if
PRIMARY_INSTANCE was zero
Cause: A non-zero value was specified for SECONDARY_INSTANCE when
PRIMARY_INSTANCE was zero.
Action: Specify a non-zero primary instance before you specify a non-zero secondary
instance.
ORA-24062: Subscriber table string inconsistent with queue table string
Cause: The subscriber table has not yet been successfully imported.
Action: Import the subscriber table before attempting 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 that has queues with rule-based
subscribers
Cause: An attempt was made to downgrade the queue table when there were queues
on which rule based subscribers are defined.
Action: Remove the rule based subscribers for all queues in this queue table and retry.
ORA-24064: propagation for QUEUE string and DESTINATION string already
enabled
Cause: An ENABLE_SCHEDULE_PROPAGATION command was issued for a queue
and destination pair whose propagation schedule already was enabled.
Action: Make sure the QUEUE and DESTINATION are correct when you issue the
ENABLE_SCHEDULE_PROPAGATION command.
ORA-24065: propagation for QUEUE string and DESTINATION string already
disabled
Cause: A DISABLE_SCHEDULE_PROPAGATION command was issued for a queue
and destination pair whose propagation schedule already was disabled.
Action: Make sure the QUEUE and DESTINATION are correct when you issue the
DISABLE_SCHEDULE_PROPAGATION command.
ORA-24066: invalid privilege specified
Cause: An invalid privilege is specified for granting or revoking privilege
Action: Specify a valid privilege.
ORA-24067: exceeded maximum number of subscribers for queue string
Cause: An attempt was made to add new subscribers to the specified, but the number
of subscribers for this queue has 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 string, queue table string is being migrated
Cause: An attempt was made to start a queue in a queue table that is being migrated.
Action: Complete the queue table migration, and retry the operation.
ORA-24069: cannot downgrade queue table string while it is being upgraded
Cause: An attempt was made to downgrade a queue table, but a previous command
to upgrade the queue table has not yet completed successfully.
Action: Complete the upragde of the queue table by re-executing the
DBMS_AQADM.MIGRATE_QUEUE_TABLE procedure. Then, downgrade the queue
table.
ORA-24070: cannot upgrade queue table string while it is being downgraded
Cause: An attempt was made to upgrade a queue table, but a previous command to
downgrade the queue table has not yet completed succesfully.
Action: Complete the downgrade of the queue table by re-executing the
DBMS_AQADM.MIGRATE_QUEUE_TABLE procedure. Then, upgrade the queue
table.
ORA-24071: cannot perform operation string, queue table string is being migrated
Cause: An attempt was made to perform an operation on a queue in a queue table
that is being migrated.
Action: Complete the queue table migration, and retry the operation.
ORA-24072: cannot execute MIGRATE_QUEUE_TABLE procedure; must own
queue table
Cause: An attempt was made to upgrade or downgrade a queue table using the
DBMS_AQADM.MIGRATE_QUEUE_TABLE procedure, but the user who executed
the procedure does not own the queue.
Action: Reconnect as the owner of the queue table, and then execute the
DBMS_AQADM.MIGRATE_QUEUE_TABLE procedure.
ORA-24073: cannot specify RETENTION_TIME on exception queue string.string
Cause: An attempt was made to create or alter an exception queue by specifying a
non-zero RETENTION_TIME.
Action: Use the default RETENTION_TIME parameter value for exception queues.
ORA-24074: RETRY_DELAY and MAX_RETRIES cannot be used for exception
queue %.string
Cause: The CREATE_QUEUE or ALTER_QUEUE command was issued with a nonzero RETRY_DELAY and an exception queue.
Action: Do not specify RETRY_DELAY or MAX_RETRIES for exception queues.
ORA-24075: cannot specify agent with NULL address and non-NULL protocol
Cause: An ADD_SUBSCRIBER or enqueue was attemoted with an agent that had a
NULL address and a non-NULL protocol.
Action: Either specify a non-NULL address or set the protocol to NULL.
ORA-24076: cannot perform operation string for NON_PERSISTENT queue
string.string
Cause: One of the operations, SCHEDULE_PROPAGATION, ALTER_QUEUE,
LISTEN, DEQUEUE was issued for a NON_PERSISTENT queue.
ORA-19999 to ORA-24279 71-75
Action: Do not specify a NON_PERSISTENT queue for these operations.

ORA-24077: cannot create propagation schedule for EXCEPTION queue
string.string
Cause: A SCHEDULE_PROPAGATION was issued for an EXCEPTION queue.
Propagation schedules can be created only for NORMAL queues.
Action: To propagate messages from a queue specify the queue type as NORMAL.
ORA-24078: cannot specify a non-NULL SECONDARY_INSTANCE if
PRIMARY_INSTANCE was NULL
Cause: A non-NULL value was specified for SECONDARY_INSTANCE when
PRIMARY_INSTANCE was NULL.
Action: Specify a non-NULL primary instance before you specify a non-NULL
secondary instance.
ORA-24079: invalid name string, names with AQ$_ prefix are not valid 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, retry the operation.
ORA-24080: unschedule_propagation pending for QUEUE string and
DESTINATION string
Cause: A propagation administration command was issued for a queue and
destination pair whose propagation is being unscheduled.
Action: Do not issue propagation administration commands for a propagation
schedule on which there is a pending unschedule request.
ORA-24081: compatible parameter needs to be string or greater
Cause: The compatible parameter was not high enough to allow the operation.
Action: Shutdown and restart with a higher compatibility setting.
ORA-24082: propagation may still be happening for the schedule for QUEUE string
and DESTINATION string
Cause: The snapshot process executing the propagation schedule did not respond to
the disable propagation command.
Action: Make sure that the job for the propagation schedule has been ended.
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
which does not support remote subscribers. Remote subscribers are not supported for
NON_PERSISTENT QUEUES.
Action: Specify a null address field and retry the call.
ORA-24084: DBLINK name in address field of agent string is not unique within the
first 24 bytes
Cause: Advanced Queuing requires that the agent's dblink name should be unique
within the first 24 bytes (for 8.0 compatible queuetables)
Action: Specify a dblink name that is unique within the first 24 bytes or migrate to 8.1
compatible queuetables where this restriction is not there.
ORA-24085: operation failed, queue string is invalid

Cause: An attempt was made to enqueue, dequeue or administer a queue which is
invalid. This could have occured because the payload type of the queue's queue table
was dropped or rules associated with queue subscribers got altered or dropped.
ORA-24086: cannot create a 8.0 compatible string queue
Cause: An attempt was made to create a 8.0 compatible queue table and enable a
feature that is supported only on 8.1 style queue tables
Action: This feature is not supported
ORA-24087: Invalid database user string
Cause: An invalid database username was specified
Action: Specify a valid database user
ORA-24088: AQ Agent string does not exist
Cause: This AQ Agent does not exist
Action: Specify a valid AQ agent. Check the DBA_AQ_AGENTS view for a list of
valid aq agents
ORA-24089: AQ Agent string already exists
Cause: This AQ agent has already been created
Action: Specify another agent name or use the ALTER api to modify the agent
information.
ORA-24090: at least one protocol must be enabled
Cause: No protocol was enabled for aq agent
Action: Enable one of the protocols by setting one of the enable parameters to true.
ORA-24091: Destination queue string is the same as the source queue
Cause: Propagation cannot be scheduled when the destination queue is the same as
the source queue.
Action: Specify a different destination queue.
ORA-24092: invalid value string specified
Cause: A queue, queue table, rule, or ruleset name that requires double quotes was
specifed when the database compatibility was less than 10.0.
Action: Specify a value that does not require double quotes and retry the operation.
ORA-24093: AQ agent string not granted privileges of database user string
Cause: The specified AQ agent does not have privileges of the specified database user
Action: Specify a valid combination of AQ agent and database user. Check the
DBA_AQ_AGENT_PRIVS or USER_AQ_AGENT_PRIVS view for user/agent
mappings
ORA-24094: invalid transformation, target type does not match that of the queue
Cause: The target type of the transformation specified was different from the type of
the queue.
Action: Provide a valid transformation whose target type is the same as the queue
type.
ORA-19999 to ORA-24279 71-77
ORA-24095: invalid transformation, source type does not match that of the queue
Cause: The source type of the transformation specified was different from the type of
the queue.
Action: Provide valid transformation whose source type is the same as the queue
type.
ORA-24096: invalid message state specified
Cause: Invalid value is specified for message state
Action: Provide a valid message state as specified in the documentation
ORA-24097: Invalid value string, string should be non-negative
Cause: A negative value or NULL was specified for the parameter.
Action: Specify a non negative integer.
ORA-24098: invalid value string for string
Cause: An Invalid value or NULL was specified for the parameter.
Action: Check the documentation for valid values.
ORA-24099: operation not allowed for 8.0 compatible queues
Cause: The specified operation is only supported for queues with compatibility 8.1 or
greater
Action: Upgrade the 8.0 compatible queue to release 8.1 using
DBMS_AQADM.MIGRATE_QUEUE_TABLE or specify a queue with compatibility
8.1
ORA-24100: error in ktz testing layer
Cause: There is an error in the Transaction layer test ICDs
Action: n/a
ORA-24101: stopped processing the argument list at: string
Cause: One of the arguments of the requested operation contained a list of scheduler
objects. While processing this list an error was encountered with the specified item.
Action: Resolve the error for this element of the list and then re-issue the command
with the remainder of the argument list. See the rest of the error stack to find out what
the exact error is.
ORA-24102: invalid prefix for generate_job_name
Cause: generate_job_name was called with a prefix longer than 18 characters or a
prefix ending in a digit.
Action: Re-issue the command using a prefix no longer than 18 characters and not
ending in a digit.
ORA-24103: job "string"."string" failed to be enabled after creation
Cause: The job failed to be enabled after creation.
Action: Review the reason for the failure, correct it if possible and re-create the job.
ORA-24120: invalid string parameter passed to DBMS_REPAIR.string procedure
Cause: An invalid parameter was passed to the specified DBMS_REPAIR procedure.
Action: Specify a valid parameter value or use the parameter's default.
ORA-24121: both cascade and a block range passed to

DBMS_REPAIR.CHECK_OBJECT procedure
Cause: Both cascade and a block range were specified in a call to
DBMS_REPAIR.CHECK_OBJECT.
Action: Use either cascade or a block range, or do not use either one.
ORA-24122: invalid block range specification
Cause: An incorrect block range was specified.
Action: Specify correct values for the BLOCK_START and BLOCK_END parameters.
ORA-24123: feature string is not yet implemented
Cause: An attempt was made to use the specified feature, but the feature is not yet
implemented.
Action: Do not attempt to use the feature.
ORA-24124: invalid ACTION parameter passed to DBMS_REPAIR.string
procedure
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 fix corrupt blocks on an object that has been dropped
or truncated since DBMS_REPAIR.CHECK_OBJECT was run.
Action: Use DBMS_REPAIR.ADMIN_TABLES to purge the repair table and run
DBMS_REPAIR.CHECK_OBJECT to determine whether there are any corrupt blocks
to be fixed.
ORA-24126: invalid CASCADE_FLAG passed to DBMS_REPAIR.string procedure
Cause: CASCADE_FLAG was specified for an object that is not a table.
Action: Use CASCADE_FLAG only for tables.
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 a non-partitioned object
Cause: A partition name was specified for an object that is not partitioned.
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.
Action: Pass a valid table name parameter.
ORA-24130: table string does not exist
Cause: An attempt was made to specify a map, repair, or sync table that does not
exist.
Action: Specify a valid table name parameter.
ORA-19999 to ORA-24279 71-79
ORA-24131: table string has incorrect columns

Cause: An attempt was made to specify a map, repair, or sync table that does not
have a correct definition.
Action: Specify a table name that refers to a properly created table.
ORA-24132: table name string is too long
Cause: An attempt was made to specify a table name is greater than 30 characters
long"
Action: Specify a valid table name parameter.
ORA-24141: rule set string.string does not exist
Cause: An attempt to access or modify a ruleset was made, which failed because the
ruleset does not exist.
Action: Only access or modify existing rulesets.
ORA-24142: invalid ruleset name
Cause: An attempt to create a ruleset with an invalid name was made. The ruleset
name can not be NULL, and can not be more than 26 characters, unless a
rules_table_name is also specified, in which case the ruleset name may be up to 30
characters.
Action: Retry the create with a valid ruleset name.
ORA-24143: invalid evaluation context name
Cause: An attempt to create a rule/ruleset on an invalid evaluation name was made.
The evaluation_context can not be more than 30 characters. The evaluation context
with the name specified must exist.
Action: Retry the create with a valid evaluation context name.
ORA-24144: rules engine internal error, arguments: [string], [string]
Cause: An internal error occurred in the rules engine. This indicates that the rules
engine has encountered an exception condition.
Action: Please report this error as a bug. The first argument is the error and the
second argument is the package.
ORA-24145: evaluation context string.string already exists
Cause: An evaluation context of the given name already exists
Action: Specify another name for the evaluation context being created
ORA-24146: rule string.string already exists
Cause: A rule of the given name already exists
Action: Specify another name for the rule being created.
ORA-24147: rule string.string does not exist
Cause: The rule of the given name does not exist
Action: create the rule or specify one that exists
ORA-24148: cannot drop rule string.string with dependents
Cause: The rule still belongs to some rulesets, cannot be dropped
Action: do not drop a rule that belongs to rulesets without force option
ORA-24149: invalid rule name

Cause: An attempt to create a rule with an invalid name was made. The rule name
can not be NULL, and can not be more than 30 characters
Action: n/a
ORA-24150: evaluation context string.string does not exist
Cause: The evaluation context of the given name does not exist
Action: create the evaluation context or specify one that exists
ORA-24151: no evaluation context is associated with rule string.string or rule set
string.string
Cause: Whening adding a rule to a rule set, either the rule or the rule set must have an
evaluation context associated with it
Action: do not add a rule without an evaluation context to a ruleset that does not have
a default evaluation context
ORA-24152: cannot drop evaluation context string.string with dependents
Cause: The evaluation context still belongs to some rules or rule sets, cannot be
dropped
Action: do not drop an evaluation context with dependents without force option
ORA-24153: rule set string.string already exists
Cause: A rule set of the given name already exists
Action: Specify another name for the rule set being created.
ORA-24154: rule string.string already in rule set string.string
Cause: a rule can be added to a rule set only once
Action: do not add a rule to a rule set that already contains this rule
ORA-24155: rule string.string not in rule set string.string
Cause: the rule to be removed from the rule set is not in the rule set
Action: do not remove a rule from a rule set that does not contain the rule
ORA-24156: duplicate table alias string
Cause: there is a table alias of the same name in the evaluation context
Action: do not add two table aliases of the same name to an evaluation context
ORA-24157: duplicate variable name string
Cause: there is a variable of the same name in the evaluation context
Action: do not add two variables of the same name to an evaluation context
ORA-24158: invalid table alias
Cause: table alias name or base table name is not specified in the table alias definiton
Action: specify both alias name and alias base table in the table alias structure
ORA-24159: invalid variable definiton
Cause: variable name or variable type is not specified in the variable definiton
Action: specify both variable name and variable type in the variable definition
structure
ORA-19999 to ORA-24279 71-81
ORA-24160: name string already exists in the name value pair list
Cause: there is already a name-value pair with the same name in the NVlist
Action: try another name.
ORA-24161: name string does not exist in the name value pair list
Cause: there is not such a name-value pair in the NVlist
Action: check the name-value pair exists in the NVList.
ORA-24162: name value pair list is full, cannot add another entry
Cause: The NVList is full (1024 elements) and cannot hold more elements
Action: do not add elements to a full list.
ORA-24163: dblink is not supported in rules engine DDLs
Cause: the object name has a database link in it, which is not supported
Action: Do not specify remote objects in rules engine DDLs.
ORA-24164: invalid rule engine system privilege: string
Cause: no such system privilege number for rule engine objects
Action: check specfication of dbms_rule_adm for valid system privilege numbers
ORA-24165: invalid rule engine object privilege: string
Cause: no such object privilege number for rule engine objects
Action: check specfication of dbms_rule_adm for valid object privilege numbers
ORA-24166: evaluation context string.string has errors
Cause: The table aliases and the variable types specified in the evaluation context
could not be resolved.
Action: Make sure that all base tables exist and that all variable types are correct.
Also, make sure that tables are not composite partitioned or clustered partitioned.
ORA-24167: incompatible rule engine objects, cannot downgrade
Cause: there are rule engine objects in the database that cannot be downgraded.
Action: check utlincmp.sql and remove all incompatible rules engine objects before
downgrade.
ORA-24168: rule string.string cannot have default evaluation context
Cause: If a rule is added to a rule set with more than one evaluation contexts, it must
not have an evaluation context itself.
Action: Do not set the evaluation context of such rules to a not-null value
ORA-24169: rule condition has unrecognized variables
Cause: The rule references variables not in the evaluation context.
Action: Modify the rule condition to remove illegal reference.
ORA-24170: string.string is created by AQ, cannot be dropped directly
Cause: This object is created by AQ, thus cannot be dropped directly
Action: use dbms_aqadm.drop_subscriber to drop the object
ORA-24171: creation properties are only for internal use

Cause: user specified not null creation properties when creating rules engine objects,
which are not for external use
Action: do not set creation properties when creating rules engine objects
ORA-24172: rule set string.string has errors
Cause: The rule references variables not in the evaluation context.
Action: Modify the rule condition to remove illegal reference.
ORA-24173: nested query not supported for rule condition
Cause: user specified nested query in rule condition.
Action: do not use nested query in rule condition.
ORA-24174: The number of string per evaluation context is more than string
Cause: Number of tables or variables were more than the defined upper limit.
Action: Reduce the number of tables or variables per evaluation context.
ORA-24175: The number of string exceeds limit string as there exists at least one
nonsimple rule condition
Cause: Upper limit of tables or variable per evaluation context exceeded as there
exists at least one nonsimple rule condition.
Action: Reduce the number of tables or variables per evaluation context.
ORA-24180: invalid transformation expression, the transformation expression does
not evaluate to the target type/attribute
Cause: The transformation expression does not evaluate to the target type or the
target type's specified attribute.
Action: Provide valid transformation expression which evaluates to the target type or
the target type's specified attribute.
ORA-24181: The type string does not exist
Cause: The source or destination type for the transformation does not exist
Action: Create the type or specify one that exists
ORA-24182: attribute number specified does not exist
Cause: The target type of the transformation does not have the attribute number
specified in the ADD_ATTRIBUTE_TRANSFORMATION command
Action: check the target type definition and specify a valid attribute number
ORA-24183: invalid transformation
Cause: The transformation specified is invalid because the source or the target type
have been dropped/modified.
Action: Drop and recreate the transformation
ORA-24184: transformation string.string already exists
Cause: The named transformation already exists.
Action: Specify another name for the transformation being created.
ORA-24185: transformation string.string does not exist
Cause: The specified transformation does not exist.
ORA-19999 to ORA-24279 71-83
Action: Create the transformation before using it or specify an existing

transformation.
ORA-24186: wrong object type, could not transform message
Cause: The object type of the message to be transformed does not match the source
type of the specified transfomation.
Action: Specify another transformation, or specify a message of the correct type.
ORA-24190: length of payload exceeds string
Cause: the length of payload being taken exceeds the limit of varchar2 or raw.
Action: use clob type or blob type to call get_text or get_bytes.
ORA-24191: the property name string has existed
Cause: the property name being set has existed.
Action: use another property name.
ORA-24192: the property name cannot be null
Cause: the property name cannot be null.
Action: make sure the property name not null.
ORA-24193: the property value exceeds the valid range string
Cause: the property valus being set exceeds the valid range.
Action: make sure the property value is within the valid range.
ORA-24194: attempt to read data in a message as the wrong type
Cause: According to JMS specification, some type conversions were not allowed.
Action: Make sure to use the correct READ function to retrieve message data.
ORA-24195: attemp to retrieve the name list of a map message with size exceeding
1024
Cause: The GET_NAMES function returns the names in a varray with a size limit of
1024.
Action: Retrieve in several smaller steps using the GET_NAMES function with
OFFSET and LENGTH parameters.
ORA-24196: access the message in a wrong access mode
Cause: StreamMessage and BytesMessage could not be read when they were in write
only mode and vice versa.
Action: Change the access mode using PREPARE, CLEAR_BODY and RESET
procedures.
ORA-24197: JAVA stored procedure throws JAVA exceptions
Cause: The JAVA stored procedure threw some exceptions that could not be
catergorized.
Action: Use GET_EXCEPTION procedure to see what the exception is about.
ORA-24198: attempt to use an invalid operation ID
Cause: An attempt was made to use an invalid operation ID to access messages.
Action: Use the correct operation ID returned by PREPARE or CLEAR_BODY
procedure.
ORA-24199: message store is overflow

Cause: An attemp was made to access too many messages at the same time.
Action: Use the CLEAN procedure to clean up some of the messages.
ORA-24201: duplicate publisher, publisher already added to the queue
Cause: Attempted to add a publisher to the queue again.
Action: Specify another publisher or user DBMS_AQADM.ALTER_PUBLISHER to
alter the publisher's properties.
ORA-24202: publisher does not exist for the queue
Cause: Attempted to alter or drop a non existent publisher from a queue.
Action: Specify another publisher.
ORA-24203: operation failed, queue table string.string has errors
Cause: An operation attempt was made to a queue table which has errors.
ORA-24204: existing string propagation schedules
Cause: A propagation administrative interface was called when the existing
propagation schedules were running in different mode (10.2/11g).
Action: Set appropriate internal parameter and unschedule existing schedules if
required.
ORA-24205: feature string not supported for sharded queues
Cause: An attempt was made to use a feature that is not supported for sharded
queues.
Action: Specify only supported features and try again.
ORA-24206: maximum limit of string nondurable subscribers reached for queue
string.string
Cause: An attempt to add a new nondurable subscriber to the queue failed because
the number of nondurable subscribers has exceeded the maximum limit.
Action: Remove existing subscribers and then attempt to add a new subscriber.
ORA-24207: addition of a nondurable subscriber for queue string.string aborted
due to low SGA
Cause: An attempt to add a new nondurable subscriber on the specified queue was
aborted because of memory constraints.
Action: Increase the shared pool size by increasing the value of the
SHARED_POOL_SIZE parameter.
ORA-24208: API not supported for non-sharded queues
Cause: An attempt was made to use a sharded queue API on a non-sharded queue.
Action: Use non-sharded queue APIs.
ORA-24209: nondurable subscriber rule has errors for queue string
Cause: An attempt was made to create a nondurable subscriber with a rule condition,
but the condition had compilation errors.
Action: Correct the condition statement based on the error stack.
ORA-19999 to ORA-24279 71-85
ORA-24210: attempt to string string on queue string.string, string already string

Cause: An attempt was made to start or stop a queue operation on a queue which is
already enabled or disabled for that operation.
Action: Make only one attempt to start or stop the queue operation.
ORA-24230: input to DBMS_DDL.WRAP is not a legal PL/SQL unit
Cause: The input supplied to DBMS_DDL.WRAP or
DBMS_DDL.CREATE_WRAPPED did not specify a legal PL/SQL package
specification, package body, type specification, type body, function or procedure. This
error can occur if you used incorrect syntax in the CREATE OR REPLACE statement
or specified a unit that cannot be wrapped (e.g., a trigger or anonymous block).
Action: Provide a legal PL/SQL unit as input.
ORA-24231: database access descriptor (DAD) string not found
Cause: The specified Database Access Descriptor (DAD) did not exist.
Action: Make sure the name of the Database Access Descriptor (DAD) is correct and
the DAD exists.
ORA-24232: unknown Embedded PL/SQL Gateway attribute string
Cause: The specified Embedded PL/SQL Gateway attribute was not known.
Action: Make sure the name of the Embedded PL/SQL Gateway attribute is correct.
ORA-24233: argument passed to DBMS_UTILITY.VALIDATE is not legal
Cause: One or more input arguments to the DBMS_UTILITY.VALIDATE routine was
not legal. This error occurred because the object name or owner or namespace
arguments (if specified) were NULL or illegal.
Action: Identify and correct the illegal argument.
ORA-24234: unable to get source of string "string"."string", insufficient privileges or
does not exist
Cause: The specified PL/SQL object in a DBMS_PREPROCESSOR subprogram did
not exist or you did not have the privileges necessary to view its source.
Action: Make sure the specified object exists and you have the privileges necessary to
view its source.
ORA-24235: bad value for object type: string
Cause: The specified object type was not appropriate.
Action: Make sure the specified object type is one of the following: package, package
body, procedure, function, trigger, type, and type body.
ORA-24236: source text is empty
Cause: The input source text supplied to a DBMS_PREPROCESSOR subprogram was
empty.
Action: Pass a non-empty input source text as the input.
ORA-24237: object id argument passed to DBMS_UTILITY.INVALIDATE is not
legal
Cause: This error occurred because the p_object_id argument passed to the
DBMS_UTILITY.INVALIDATE routine was NULL, there was no object with the
specified object id, or the user calling the routine did not have sufficient privileges to
invalidate the object.
Action: Correct the illegal argument.

ORA-24238: object settings argument passed to DBMS_UTILITY.INVALIDATE is
not legal
Cause: This error occurred because the p_plsql_object_settings argument passed to
the DBMS_UTILITY.INVALIDATE routine was NULL or malformed.
Action: Correct the illegal argument.
ORA-24239: object could not be invalidated
Cause: A call to the DBMS_UTILITY.INVALIDATE routine failed. This error occurred
because the object type of the object specified by the p_object_id argument is not one
of the types that can be handled by this routine. Alternately, the object was an object
type specification with table dependents, or the object was the specification of the
STANDARD, DBMS_STANDARD, DBMS_UTILITY package, or the body of the
DBMS_UTILITY package.
Action: Call DBMS_UTILITY.INVALIDATE only on supported object types.
ORA-24240: invalid database access descriptor (DAD) name
Cause: The specified Database Access Descriptor (DAD) name was invalid.
Action: Make sure the name of the Database Access Descriptor (DAD) is valid and its
length does not exceed its limit.
ORA-24241: source text is in wrapped format
Cause: The input source text supplied to a DBMS_PREPROCESSOR subprogram was
in wrapped format.
Action: Pass a nonwrapped source text as the input.
ORA-24242: anonymous access through a dynamically authenticated Database
Access Descriptor (DAD) prohibited
Cause: An attempt to allow anonymous access through a dynamically authenticated
Database Access Descriptor (DAD) was prohibited.
Action: Make sure the Database Access Descriptor (DAD) is not dynamically
authenticated before allowing anonymous access through it.
ORA-24243: access control entry (ACE) already exists
Cause: An access control entry (ACE) for the principal with the same grant or deny
attribute in the IS_GRANT argument already existed.
Action: Add the privilege to the existing access control entry (ACE) instead.
ORA-24244: invalid host or port for access control list (ACL) assignment
Cause: The host or port to which the access control list (ACL) was assigned was
invalid.
Action: Ensure the host and port to which you are assigning the access control list
(ACL) are valid.
ORA-24245: invalid network privilege
Cause: The network privilege being added to the access control list (ACL) was
invalid.
Action: Ensure the network privilege that you are adding to the access control list
(ACL) is valid.
ORA-19999 to ORA-24279 71-87
ORA-24246: empty access control list (ACL) not allowed

Cause: An attempt was made to store an empty access control list (ACL).
Action: Ensure that the access control list (ACL) has at least one
ORA-24247: network access denied by access control list (ACL)
Cause: No access control list (ACL) has been assigned to the target host or the
privilege necessary to access the target host has not been granted to the user in the
access control list.
Action: Ensure that an access control list (ACL) has been assigned to the target host
and the privilege necessary to access the target host has been granted to the user.
ORA-24248: XML DB extensible security not installed
Cause: XML DB extensible security necessary for this operation has not been installed.
Action: Ensure that XML DB has been installed.
ORA-24249: Authentication scheme "string" not supported
Cause: An unsupported authentication scheme was used.
Action: Retry with a supported authentication scheme.
ORA-24250: No supported authentication scheme found
Cause: A supported authentication scheme was not found.
Action: Retry with a supported authentication scheme.
ORA-24251: This statement is not supported by EXPAND_SQL_TEXT.
Cause: EXPAND_SQL_TEXT supports only SELECT statements.
Action: Submit only a SELECT statement.
ORA-24252: SQL translation profile does not exist
Cause: An attempt was made to access a SQL translation profile that either did not
exist or for which the current user did not have privileges on.
Action: Check the SQL translation profile name and verify that the current user has
appropriate privileges on the SQL translation profile.
ORA-24253: translation of SQL statement or error code not found
Cause: An attempt to translate a SQL statement or error code or to change a SQL or
error code translation failed because the translation was not found.
Action: Verify that the SQL statement or error code is valid and either a custom
translation is registered or the translator package in the SQL translation profile can
translate it.
ORA-24254: appropriate SQL translation profile not set
Cause: An attempt to translate a SQL statement or error code failed because either a
SQL translation profile was not set or the profile could not translate the given SQL
syntax.
Action: Set an appropriate SQL translation profile before attempting to translate a
SQL statement or error code.
ORA-24255: Implementation restriction: bind variables cannot change in the
translated SQL statement
Cause: An attempt to register or use a translated SQL statement failed because the
number or the order of bind variables were changed in the statement.
Action: Do not change the number or the order of bind variables in the translated SQL
statement.
ORA-24256: EXPAND_SQL_TEXT failed with string
Cause: See the string parameter at the end of the message.
Action: See the string parameter at the end of the message and take corrective action.
ORA-24265: Insufficient privileges for SQL profile operation
Cause: A DDL operation was attempted on a SQL profile by a session without the
proper privileges.
Action: Grant the user the appropriate privilege.
ORA-24270: a row already exists in the 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 either T, S or M
Cause: The translation type parameter is not a T, S or an M. A value other than T, S or
M was specified.
Action: Correct the translation type and reexecute the API call.
ORA-24272: initialization value must be either F or T
Cause: The initialization value must be either F or T. A value other than F or T was
specified.
Action: Correct the initialization value and reexecute the API call.
ORA-24273: translation text is required if translation type is T or S
Cause: If a translation type of T or S is specified, translation text must be supplied.
Action: Provide translation text and reexecute the API call.
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 specified values exist.
ORA-24275: function 'string' parameter 'string' missing or invalid
Cause: The function <pkgname.funcname> was called with a parameter parmname
that was null, 0 length, or had an invalid value.
Action: Correct the parameter to supply values that comply with its datatype and
limits as specified in the documentation.
ORA-24276: function 'string' output 'string' maximum value exceeded
Cause: The function <pkgname.funcname> computed a value for the output
parmname that exceeded the maximum allowed. This can occur when multiple input
parameters, each valid separately, combine to specify an invalid result. For example,
when a length parameter multiplied by a copies parameter yields a total length
exceeding the maximum for the output datatype.
Action: Correct the input values to produce a result that will comply with the limits as
specified in the documentation.
ORA-19999 to ORA-24279 71-89
ORA-24277: invalid database link string

Cause: The database link did not exist.
Action: Make sure the database link name is correct.
ORA-24278: remote table string not found
Cause: The table did not exist in the remote database.
Action: Make sure the remote table name is correct.
ORA-24279: view string is not a parallel access view
Cause: The view was not created by CREATE_OR_REPLACE_VIEW API.
Action: Provide the correct view name that was created by
CREATE_OR_REPLACE_VIEW API.
72
ORA-24280 to ORA-28709
ORA-24280: invalid input value for parameter string
Cause: The parameter has been provided a negative, out of range, or NULL input
value.
Action: Correct the input value such that it is valid, and is within the range as
specified in the documentation.
ORA-24281: invalid access past the maximum size of LOB parameter string
Cause: The value of positional or size parameters exceeds the maximum allowed LOB
size of 4 Gigabytes.
Action: Correct the input values for amount and offset such that their sum is less than
or equal to 4 Gigabytes. If error occurs in a read or write loop, check the looping
conditions and/or offset increments.
ORA-24291: Sort Hash Cluster error string
ORA-24292: no more tables permitted in this sorted hash cluster
Cause: A sorted hash cluster only supports a maximum of 2 tables
Action: n/a
ORA-24295: max key length (string) for sorted hash cluster exceeded
Cause: Sorted hash clusters have a maximum key size
Action: n/a
ORA-24296: error in processing the XML configuration file string
Cause: Parameters or their values were specified incorrectly in the configuration file.
Action: Check and correct the configuration parameters or their values.
ORA-24300: bad value for mode
Cause: An undefined mode value was specified.
Action: Check that the correct mode is selected and that an allowed value for that
mode is specified.
ORA-24301: null host specified in thread-safe logon
Cause: An HDA was not specified in the logon call while running in a thread safe
environment.
Action: Make sure that HDA is not NULL when calling the logon 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 finish before using this connection.
ORA-24280 to ORA-28709 72-1
ORA-24303: call not supported in non-deferred linkage

Cause: One of the calls that is supported in deferred mode linkage exclusively was
invoked when the client was linked non-deferred.
Action: Use this call in deferred mode of linkage.
ORA-24304: datatype not allowed for this call
Cause: Data of this datatype cannot be sent or fetched in pieces.
Action: Use other bind or define calls for this datatype.
ORA-24305: bad bind or define context
Cause: The call was executed on a cursor for which this is invalid.
Action: Verify that this call is valid for this cursor. For example, Get piece information
and set piece information are valid on a cursor if appropriate binds and defines have
been done on this cursor.
ORA-24306: bad buffer for piece
Cause: A zero length buffer or a null buffer pointer was provided.
Action: Verify that the buffer pointing to this piece or its length is non-zero. The
buffer pointer for the next piece or its length can be zero if it is the last piece to be
inserted and there are no more data for the column.
ORA-24307: invalid length for piece
Cause: The length of the piece exceeded the maximum possible size.
Action: Verify that the length of this piece and the cumulative length of all the
previous pieces is not more than the desired value supplied by the application.
ORA-24308: illegal define position
Cause: Call to modify attributes was done for a non-existent position
Action: Verify that a define has been done for this position
ORA-24309: already connected to a server
Cause: This server handle is already attached to a server.
Action: Disconnect from the server and then retry the call to establish a connection.
ORA-24310: length specified for null connect string
Cause: The connect string is null, but a length was specified for it.
Action: Set length to zero if connect string is null.
ORA-24311: memory initialization failed
Cause: Cannot initialize user memory.
ORA-24312: illegal parameters specified for allocating user memory
Cause: An illegal size or null pointer was specified for user memory.
Action: Specify a legal size and a valid pointer for user memory.
ORA-24313: user already authenticated
Cause: A user has already been authenticated on this service handle.
Action: Terminate the service context before using it for another user.
72-2 Error Messages
ORA-24314: service handle not initialized

Cause: The server context does not done exist.
Action: Establish the server context in the service context.
ORA-24315: illegal attribute type
Cause: An illegal attribute type was specified for the handle.
Action: Consult user manual to specify an attribute valid for this handle.
ORA-24316: illegal handle type
Cause: An illegal handle type was specified.
Action: Consult user manual to specify a valid handle type.
ORA-24317: define handle used in a different position
Cause: A define was done with an existing handle on a different position.
Action: Specify the same position as before on a re-define.
ORA-24318: call not allowed for scalar data types
Cause: This call is valid only for object types.
Action: Verify that the data-type for this variable is an object type
ORA-24319: unable to allocate memory
Cause: Process was unable to allocate memory to store diagnostics.
Action: Terminate other processes in order to reclaim needed memory.
ORA-24320: unable to initialize a mutex
Cause: An attempt to initialize a mutex failed.
ORA-24321: inconsistent parameters passed
Cause: One of the three memory function pointers is null or non-null.
Action: Verify that either all the memory functions are null or non-null.
ORA-24322: unable to delete an initialized mutex
Cause: An attempt to delete an initialized mutex failed.
ORA-24323: value not allowed
Cause: A null value or a bogus value was passed in for a mandatory parameter.
Action: Verify that all mandatory parameters are properly initialized.
ORA-24324: service handle not initialized
Cause: An attempt was made to use an improper service context handle.
Action: Verify that the service context handle has all the parameters initialized prior
to this call.
ORA-24325: this OCI operation is not currently allowed
Cause: An attempt was made to use a context handle outside its scope.
Action: Verify that the context handle is set to a service context handle that has been
converted to a logon data area for other OCI calls. The logon data area must be
converted back to a service context before it can be used.
ORA-24280 to ORA-28709 72-3
ORA-24326: handle passed in is already initialized

Cause: An attempt was made to pass an initialized handle.
Action: Verify that the parameter passed in to retrieve a handle does not already
point to a handle.
ORA-24327: need explicit attach before authenticating a user
Cause: A server context must be initialized before creating a session.
Action: Create and initialize a server handle.
ORA-24328: illegal attribute value
Cause: The attribute value passed in is illegal.
Action: Consult the users manual and specify a legal attribute value for the handle.
ORA-24329: invalid character set identifier
Cause: The character set identifier specifed is invalid
Action: Specify a valid character set identifier in the OCI call.
ORA-24330: internal OCI error
Cause: An internal OCI error has occurred.
Action: Please contact Oracle customer support.
ORA-24331: user buffer too small
Cause: The user buffer to contain the output data is too small.
Action: Specify a bigger buffer.
ORA-24332: invalid object type
Cause: An invalid object type is requested for the describe call.
Action: Specify a valid object type to the describe call.
ORA-24333: zero iteration count
Cause: An iteration count of zero was specified for the statement
Action: Specify the number of times this statement must be executed
ORA-24334: no descriptor for this position
Cause: The application is trying to get a descriptor from a handle for an illegal
position.
Action: Check the position number.
ORA-24335: cannot support more than 1000 columns
Cause: The number of columns exceeds the maximum number supported.
Action: n/a
ORA-24336: invalid result set descriptor
Cause: The result set descriptor should have valid data fetched into it before it can be
converted to a statement handle
Action: Fetch valid data into the descriptor before attempting to convert it into a
statement handle
ORA-24337: statement handle not prepared
Cause: A statement cannot be executed before making preparing a request.
Action: Prepare a statement before attempting to execute it.
72-4 Error Messages
ORA-24338: statement handle not executed

Cause: A fetch or describe was attempted before executing a statement handle.
Action: Execute a statement and then fetch or describe the data.
ORA-24339: cannot set server group name after connecting to server
Cause: An attempt was made to set the server group in a server handle after
connecting to the server. However, once the connection is established to a server, the
server group name cannot be set anymore.
Action: Attach to the server after setting the server group name in the server handle.
ORA-24340: cannot support more than 255 columns
Cause: The number of columns exceeds maximum supported by the server.
Action: Limit your operation to 255 columns.
ORA-24341: bad mode specified
Cause: OCI_ENV_NO_MUTEX mode was specified for a non-threaded client.
Action: OCI_ENV_NO_MUTEX may be specified when OCI_THREADED had been
specified at process initialization.
ORA-24342: unable to destroy a mutex
Cause: An attempt to destroy a mutex failed.
Action: n/a
ORA-24343: user defined callback error
Cause: The only valid return value for a user defined callback function is
OCI_CONTINUE or OCI_ROWCBK_DONE. Any other value will cause this error.
Action: Please insure that OCI_CONTINUE or OCI_ROWCBK_DONE is returned
from the user defined callback function.
ORA-24344: success with compilation error
Cause: A sql/plsql compilation error occurred.
Action: Return OCI_SUCCESS_WITH_INFO along with the error code
ORA-24345: A Truncation or null fetch error occurred
Cause: A truncation or a null fetch error"
Action: Please ensure that the buffer size is long enough to store the returned data.
ORA-24346: cannot execute without binding variables
Cause: None of the bind variables in the SQL statement are bound.
Action: Please bind all the variables before the execute is done.
ORA-24347: Warning of a NULL column in an aggregate function
Cause: A null column was processed by an aggregate function
Action: An OCI_SUCCESS_WITH_INFO is returned.
ORA-24348: Update or Delete without Where
Cause: An update or delete was executed without where clause
Action: An OCI_SUCCESS_WITH_INFO is returned.
ORA-24280 to ORA-28709 72-5
ORA-24349: Array DML row counts not available

Cause: One of the following occurred: -The attribute in OCIAttrGet was used
incorrectly. -The version of the database used does not support this feature -There
was an error in the array DML for all of the iterations.
Action: Ensure that the statement is an array DML and also ensure that the database
version is Oracle 12 or higher and the correct mode is used.
ORA-24350: OCI call not allowed
Cause: OCI used is not permitted from external procedures.
Action: Refer to user manual for usage restrictions.
ORA-24351: invalid date passed into OCI call
Cause: A bad date was passed into one of the OCI calls.
Action: Check your date bind values and correct them.
ORA-24352: invalid COBOL display type passed into OCI call
Cause: A bad COBOL display type was passed into one of the OCI calls.
Action: Check your COBOL display type bind values and correct them.
ORA-24353: user buffer too small to accommodate COBOL display type
Cause: User supplied buffer for a COBOL display type was too small to accommodate
fetched number.
Action: Increase the allocation for COBOL display type buffer.
ORA-24354: number fetched too large to fit in COBOL display type buffer.
Cause: The number fetched was beyond the range that can be displayed.
Action: Please check the number in the database.
ORA-24355: attempt to store a negative number in an Unsigned Display type.
Cause: An attempt was made to convert a negative number into an unsigned display
type.
Action: Please check the number in the database or change the defined datatype.
ORA-24356: internal error while converting from to COBOL display type.
Cause: An internal error was encountered during conversion to COBOL display type.
ORA-24357: internal error while converting from to OCIDate.
Cause: An internal error was encountered during conversion to OCIDate type.
ORA-24358: OCIBindObject not invoked for a Object type or Reference
Cause: OCIBindObject was not invoked resulting in an incomplete bind specification
for a Object Type or Reference.
Action: Please invoke the OCIBindObject call for all Object Types and References.
ORA-24359: OCIDefineObject not invoked for a Object type or Reference
Cause: OCIDefineObject was not invoked resulting in an incomplete bind
specification for a Object Type or Reference.
Action: Please invoke the OCIDefineObject call for all Object Types and References.
72-6 Error Messages
ORA-24360: Type Descriptor Object not specified for Object Bind/Define

Cause: Type Descriptor Object is a mandatory parameter for Object Types Binds and
Defines.
Action: Please invoke the OCIBindObject() or OCIDefineObject() call with a valid
Type Descriptor Object.
ORA-24361: basic bind call not invoked before invoking advanced bind call
Cause: One of the basic bind calls was not invoked on this bind handle before
performing an advanced bind call.
Action: Please invoke the advanced bind call on this bind handle only after
performing a basic bind call.
ORA-24362: improper use of the character count flag
Cause: When the character count flag is set, then the maximum size of the buffer in
the server should be specified as a non-zero value.
Action: Please use a non-zero value for the mamimum size of the buffer in the server.
ORA-24363: measurements in characters illegal here
Cause: Measurements in characters instead of bytes are illegal if either the server's or
client's character set is varying width.
Action: If either the client's or server's character set is varying width then do not use
the OCI_ATTR_CHAR_COUNT attribute for the bind handle. Use
OCI_ATTR_MAXDATA_SIZE instead.
ORA-24364: internal error while padding blanks
Cause: An internal error has occurred while attempting to blank pad string data. This
error should not occur normally.
ORA-24365: error in character conversion
Cause: This usually occurs during conversion of a multibyte character data when the
source data is abnormally terminated in the middle of a multibyte character.
Action: Make sure that all multibyte character data is properly terminated.
ORA-24366: migratable user handle is set in service handle
Cause: This occurs during user authentication, a migratable user handle has been set
in the service handle.
Action: Service handle must not be set with migratable user handle when it is used to
authenticate another user.
ORA-24367: user handle has not been set in service handle
Cause: This occurs during authentication of a migratable user. the service handle has
not been set with non-migratable user handle.
Action: Service handle must be set with non-migratable user handle when it is used to
authenticate a migratable user.
ORA-24368: OCI mutex counter non-zero when freeing a handle
Cause: This is an internal OCI error.
ORA-24280 to ORA-28709 72-7
ORA-24369: required callbacks not registered for one or more bind handles
Cause: No callbacks have been registered for one or more of the bind handles which
are part of the RETURNING clause.
Action: The bind handles which are to receive data in a DML statememt with a
RETURNING clause must have their mode set as DATA_AT_EXEC and callback
functions must be registered for these bind handles using OCIBindDynamic.
ORA-24370: illegal piecewise operation attempted
Cause: Data of a certain datatype that does not support piecewise operation is being
sent or fetched in pieces.
Action: Always set the piece value to OCI_ONE_PIECE for datatypes that does not
support piecewise operation.
ORA-24371: data would not fit in current prefetch buffer
ORA-24372: invalid object for describe
Cause: The object to be described is not valid. It either has compilation or
authorization errors.
Action: The object to be described must be valid.
ORA-24373: invalid length specified for statement
Cause: The length specified for the statement is either 0 or too large.
Action: Specify a valid length for the statement.
ORA-24374: define not done before fetch or execute and fetch
Cause: The application did not define output variables for data being fetched before
issuing a fetch call or invoking a fetch by specifying a non-zero row count in an
execute call.
Action: Issue OCI define calls for the columns to be fetched.
ORA-24375: Cannot use V6 syntax when talking to a V8 server
Cause: V6 syntax is no longer supported in V8 server.
Action: Change syntax to V7 syntax or higher.
ORA-24376: cannot register/get user callback for non-environment handle
Cause: A user callback registration or get was attempted on a handle which is not an
environment handle.
Action: Pass the environment handle to register/get user callback.
ORA-24377: invalid OCI function code
Cause: An invalid function code was used to register or get user callback"
Action: Use a valid OCI function code.
ORA-24378: user callbacks not allowed for this call
Cause: An attempt was made to register a user callback for an OCI call for which it
not allowed to register user callbacks.
Action: Do not register user callback for this OCI call.
72-8 Error Messages
ORA-24379: invalid user callback type

Cause: An invalid type of user callback was specified.
Action: Specify a valid user callback type.
ORA-24380: invalid mode specification
Cause: The mode parameter in an OCI call is invalid
Action: Use only valid mode parameter
ORA-24381: error(s) in array DML
Cause: One or more rows failed in the DML.
Action: Refer to the error stack in the error handle.
ORA-24382: statement handled already executed or described
Cause: The Statement handle was executed or described successfuly before.
Action: Perform a OCIStmtPrepare again before OCI_PARSE_ONLY.
ORA-24383: Overflow segment of an IOT cannot be described
Cause: The name specified in the OCIDescribeAny call referred to an IOT overflow
segment.
Action: Use OCIDescribeAny to describe only documented objects.
ORA-24384: Application context size is not initialized
Cause: The size of the application context must be initialized before populating each
context element.
Action: Issue OCIAttrSet with OCI_ATTR_CTX_SIZE to initialize context size
ORA-24385: Application context size or index is not valid
Cause: The size or index of the application context must be non-zero and nonnegative.
Action: Use an appropriate value for the size.
ORA-24386: statement/server handle is in use when being freed
Cause: This is an internal OCI error.
Action: The user should reset in-use flag in statement handle before freeing the
handle.
ORA-24387: Invalid attach driver
Cause: Trying to attach using the wrong driver
Action: Relink the application in the right mode
ORA-24388: Unsupported functionality in fast path mode
Cause: Feature not supported in fast path mode
Action: Avoid using the functionality in this mode
ORA-24389: Invalid scrollable fetch parameters
Cause: All the requested rows in this fetch could not be received.
Action: Check the fetch orientation, scroll offset, OCI_ATTR_CURRENT_POSITION
and number of rows in OCIStmtFetch2 call. If required, change some of above
parameters and fetch again.
ORA-24280 to ORA-28709 72-9
ORA-24390: Unsupported scrollable cursor operation

Cause: The scrollable cursor execute or fetch has failed.
Action: Check the documentation for supported types, and other restrictions while
using scrollable cursors.
ORA-24391: invalid fetch operation
Cause: Scrollable cursor operation requested with non-scrollable cursor.
Action: Check if the statement was executed in the scrollable mode. Else the only
acceptable orientation is OCI_FETCH_NEXT that ignores the scroll offset parameter.
ORA-24392: no connection pool to associate server handle
Cause: OCIServerAttach called in OCI_POOL mode but no connection pool found to
associate the server handle.
Action: 1) Verify that OCIConnectionPoolCreate is called before calling
OCIServerAttach. 2) Verify that the database link specified in OCIServerAttach
matches with that of the connection pool database link.
ORA-24393: invalid mode for creating connection pool
Cause: Mode specified in OCIConnectionPoolCreate is invalid.
Action: Use a valid mode.
ORA-24394: invalid mode for destroying connection pool
Cause: Mode specified in OCIConnectionPoolDestroy is invalid.
Action: Use a valid mode.
ORA-24395: cannot reinitialize non-existent pool
Cause: OCIConnectionPoolCreate was not called in OCI_DEFAULT mode for this
pool handle.
Action: Create a connection pool prior to reinitializing it.
ORA-24396: invalid attribute set in server handle
Cause: Attribute OCI_ATTR_NONBLOCKING_MODE has been set on the server
handle and attached in OCI_POOL mode. Connection pooling does not support non
blocking mode.
Action: Do not set the OCI_ATTR_NONBLOCKING_MODE attribute on the server
handle while attaching in OCI_POOL mode.
ORA-24397: error occured while trying to free connections
Cause: An internal error occured while trying to free connections.
ORA-24398: connection pool already exists
Cause: A connection pool has already been created for the specified pool handle.
Action: 1) Specify a different pool handle to create a new connection pool. 2) If you
wish to modify the pool parameters, call OCIConnectionPoolCreate in
OCI_CPOOL_REINITIALIZE mode.
ORA-24399: invalid number of connections specified
Cause: An invalid combination of minimum, maximum and increment number of
connections was specified in the OCIConnectionPoolCreate call.
Action: Specify a valid combination of parameters.
ORA-24400: error occured while creating connections in the pool

Cause: The database link specified in OCIConnectionPoolCreate might be an invalid
one.
Action: Specify a valid database link.
ORA-24401: cannot open further connections
Cause: Sufficient number of connections are not present in the pool to execute the call.
No new connections can be opened as the connMax parameter supplied in
OCIConnectionPoolCreate has been reached.
Action: Call OCIConnectionPoolCreate in OCI_CPOOL_REINITIALIZE mode and
increase the value of the connMax parameter.
ORA-24402: error occured while creating connections in the pool
Cause: The username and password specified in OCIConnectionPoolCreate might be
invalid.
Action: Specify a valid username and password.
ORA-24403: error occured while trying to destroy the connection pool
Cause: Some connections in the pool were busy when an attempt to destroy the
connection pool was made.
Action: Ensure no connections from the pool are being used.
ORA-24404: connection pool does not exist
Cause: An attempt was made to use the connection pool before creating it.
Action: Create the connection pool.
ORA-24405: error occured while trying to create connections in the pool
Cause: An internal error occured while creating connections in the pool.
ORA-24406: API mode switch is disallowed when a call is in progress.
Cause: A mode switch from OCI8 to OCI7 was attempted in a callback.
Action: The user should perform the API mode switch either prior to initiating the top
call or after the main call is done.
ORA-24407: connection pool already exists
Cause: A connection pool has already been created for the specified pool name.
Action: Specify a different pool name to create a new connection pool.
ORA-24408: could not generate unique server group name
Cause: An internal error occured while generating unique server group name.
ORA-24409: client cannot understand the object
Cause: The client cannot process all the new features in the object.
Action: Upgrade the client so that features like inheritance and SQLJ objects can be
used.
ORA-24410: scrollable cursor max size exceeded
Cause: Result set size exceeded the max limits.
ORA-24280 to ORA-28709 72-11
Action: Check the documentation for allowable maximum result set size for scrollable
cursors. Re-execute with a smaller expected result set size or make the cursor nonscrollable.
ORA-24411: Session pool already exists.
Cause: A session pool has already been created for the specified pool handle.
Action: 1) Specify a different pool handle to create a new session pool. 2) If you wish
to modify the pool parameters, call OCISessionPoolCreate in
OCI_SPOOL_REINITIALIZE mode.
ORA-24412: Cannot reinitialize non-existent pool
Cause: OCISessionPoolCreate was not called in OCI_DEFAULT mode for this pool
handle.
Action: Create a session pool prior to reinitializing it.
ORA-24413: Invalid number of sessions specified
Cause: An invalid combination of minimum, maximum and increment number of
sessions was specified in the OCISessionPoolCreate call.
Action: Specify a valid combination of parameters.
ORA-24414: Only number sessions could be started.
Cause: The number of sessions specified by the minSess parameter of
OCISessionPoolCreate could not be started, possibly because the value supplied was
larger than that supported by the server."
Action: This is a warning. Check the maximum number of sessions allowed on the
server.
ORA-24415: Missing or null username.
Cause: Username and password must be specified when pool is created in this mode.
Action: Specify a valid username and password.
ORA-24416: Invalid session Poolname was specified.
Cause: An attempt was made to use a Session Pool that does not exist.
Action: Create a Session Pool before using it.
ORA-24417: Session pool size has exceeded the maximum limit
Cause: The number of sessions has exceeded the maximum size of the Session Pool.
Action: This is a warning. You can tune the session pool with appropriate minimum
and maximum parameters.
ORA-24418: Cannot open further sessions.
Cause: Sufficient number of sessions are not present in the pool to execute the call. No
new sessions can be opened as the sessMax parameter supplied in
OCISessionPoolCreate has been reached.
Action: Call OCISessionPoolCreate in OCI_SPOOL_REINITIALIZE mode and
increase the value of the sessMax parameter.
ORA-24419: Proxy sessions are not supported in this mode.
Cause: A proxy session was requested for from a Session Pool which does not support
proxy sessions.
Action: Do not specify mode OCI_CRED_PROXY.
ORA-24420: OCISessionRelease must be used to release this session.

Cause: The session was retrieved using OCISessionGet, and an attempt has been
made to release it using a call other than OCISessionRelease.
Action: Call OCISessionRelease.
ORA-24421: OCISessionRelease cannot be used to release this session.
Cause: The session was not retrieved using OCISessionGet, and an attempt has been
made to release it using OCISessionRelease.
Action: Release the session using an appropriate call.
ORA-24422: error occurred while trying to destroy the Session Pool
Cause: An attempt was made to destroy the session pool while some sessions in the
pool were busy.
Action: Ensure that no sessions from the pool are being used OR call
OCISessionPoolDestroy with mode set to OCI_SPD_FORCE.
ORA-24423: Cannot set the ROWID attribute - OCI_ATTR_FETCH_ROWID
Cause: An attempt was made to set the implicit ROWID attribute.
Action: Use a SELECT ... FOR UPDATE statement that has not previously been
described or executed before setting this ROWID attribute.
ORA-24424: Invalid attempt to define at position 0
Cause: An invalid attempt was made to call OCIDefineByPos for position 0.
Action: Ensure that the implicit ROWID attribute, OCI_ATTR_FETCH_ROWID, is set
on the statement handle before doing the execute.
ORA-24425: Invalid mode passed when defining at position 0
Cause: An invalid mode was passed to OCIDefineByPos.
Action: Ensure a valid mode is passed to OCIDefineByPos when defining at position
0.
ORA-24427: Invalid attributes on user handle
Cause: Some of the attributes set on the user handle were not allowed in pooled
mode.
Action: Unset the attributes on the user handle and call OCISessionGet or use sessions
that are not pooled.
ORA-24428: Sessions with SYSDBA privileges are not supported in this mode.
Cause: A session with SYSDBA privileges was requested from a Session Pool which
does not support sessions with SYSDBA privileges.
Action: Do not specify mode OCI_SESSGET_SYSDBA.
ORA-24429: External authentication is not supported in this mode.
Cause: An externally authenticated session was requested from a Session Pool which
does not support external authentication.
Action: Do not specify mode OCI_SESSGET_CREDEXT.
ORA-24430: Null values for sqltext and key were specified.
Cause: An attempt was made to call OCIStmtPrepare2 and neither sqltext nor key
were specified.
Action: Specify valid values for sqltext or key or both.
ORA-24280 to ORA-28709 72-13
ORA-24431: Statement does not exist in the cache

Cause: The statement that was requested for does not exist in the statement cache.
Action: Please request for a valid statement.
ORA-24432: The statement that was returned is not tagged.
Cause: A tagged statement was requested for, but an untagged statement has been
returned.
Action: This is a warning. Please modify and tag the statement as desired.
ORA-24433: This statement has already been prepared using OCIStmtPrepare2.
Cause: A statement that was earlier prepared using OCIStmtPrepare2 is now being
reprepared using OCIStmtPrepare."
Action: Please use a different statement handle.
ORA-24434: OCIStmtRelease called before OCIStmtPrepare2.
Cause: An attempt was made to release a statement without first preparing it using
OCIStmtPrepare2.
Action: Call OCIStmtPrepare2 before OCIStmtRelease.
ORA-24435: Invalid Service Context specified.
Cause: The statement was prepared using a service context that is different from the
one specified in OCIStmtExecute.
Action: Please specify the same service context that the statement was prepared with.
ORA-24436: Invalid statement Handle.
Cause: OCIHandleFree called on a statement that was prepared using
OCIstmtPrepare2.
Action: Release the statement using OCIStmtRelease.
ORA-24437: OCIStmtExecute called before OCIStmtPrepare2.
Cause: An attempt was made to execute a statement without first preparing it using
OCIStmtPrepare2.
Action: Call OCIStmtPrepare2 before OCIStmtExecute.
ORA-24438: Invalid Authentication Handle specified.
Cause: The statement was prepared using an authentication handle that is different
from the one specified in OCIStmtExecute.
Action: n/a
ORA-24439: success with PLSQL compilation warning
Cause: A plsql compilation warning occurred.
Action: Return OCI_SUCCESS_WITH_INFO along with the error code.
ORA-24440: OCI Easy Install mode cannot be initialized
ORA-24441: Invalid cookie, resend sql text
ORA-24450: Cannot pre-process OCI statement

Cause: An error occured during statement pre-processing. E.g., SQL statement has
invalid usage of N' or Q' literals.
Action: Correct the SQL statement.
ORA-24451: string, Maximum call depth exceeded
Cause: Your program has too many levels of recursion.
Action: Restructure your program to eliminate some levels of recursion.
ORA-24452: value_sz exceeding SB4MAXVAL is not supported
Cause: value_sz specified in OCIBindByPos2, OCIBindByName2 or OCIDefineByPos2
exceeds SB4MAXVAL and is not supported in this release.
Action: Specify a value less than or equal to SB4MAXVAL for value_sz in
OCIBindByPos2, OCIBindByName2 or OCIDefineByPos2.
ORA-24453: number of application context settings supplied during authentication
has exceeded the supported limit of number settings
Cause: The number of application context settings supplied during authentication
exceeded the specified limit.
Action: Reduce the number of application context settings that are passed during
authentication.
ORA-24460: Native Net Internal Error
Cause: Internal error .
Action: This error should not normally occur. If it persists, please contact your
customer service representative.
ORA-24480: invalid OCI mode
Cause: An attempt was made to invoke OCI API with an invalid mode.
Action: Provide the OCI API with legitimate mode.
ORA-24481: Failed to initialize multithreaded environment
Cause: Operating system did not support multithreaded mode.
Action: Use single thread mode instead.
ORA-24482: Pool size was less than 1 in shared mode
Cause: Pool size must be positive in shared mode.
Action: Set a positive pool size.
ORA-24483: Invalid parameters were passed into environment creation call
Cause: Invalid parameters were passed into the environment creation call. Check the
passed in parameters for the following conditions: -envp should not be NULL xtramem_sz should not be negative -Either both xtramem_sz and usrmempp have to
be provided. Or, neither should be provided.
Action: Pass in legitimate parameters.
ORA-24484: Setting authentication handle not allowed after pool create
Cause: An attempt was made to set the authentication handle on session pool handle
after OCISessionPoolCreate.
Action: Set the authentication handle on session pool handle before calling
OCISessionPoolCreate.
ORA-24280 to ORA-28709 72-15
ORA-24485: Invalid attributes in session pool authentication handle

Cause: Some of the attributes set on the authentication handle being set on the session
pool handle are invalid.
Action: Unset the illegal attributes on the authentication handle being set on session
pool handle and then call OCIAttrSet. Refer to OCI documentation for details.
ORA-24486: Conflicting attributes in session pool authentication handle
Cause: Some attributes could not be set both on the authentication handle passed to
OCISessionGet and the authentication handle set on session pool handle.
Action: Unset the conflicting attributes on the authentication handle and call
OCISessionGet.
ORA-24500: invalid UTF16 mode
Cause: UTF16 mode is allowed only at environment handle creation time.
Action: Remove UTF16 mode for functions other than OCIEnvCreate()
ORA-24501: invalid UTF16 string passed in
Cause: Non-UTF16 string is passed in while UTF16 string is expected
Action: Check the parameter which is actually a string
ORA-24502: codepoint length overflows
Cause: Returned buffer has more codepoints than allowed
Action: Set OCI_MAXCHAR_SIZE large enough to accommodate
ORA-24503: codepoint length overflows for piecewise operation
Cause: Accumulated codepoint length exceeds allowed codepoint length
Action: Set OCI_MAXCHAR_SIZE large enough to accommodate
ORA-24504: data length larger than expected
Cause: Incoming data larger than receiving buffer
Action: Set OCI_MAXDATA/MAXCHAR_SIZE appropriately or remove the setting
ORA-24505: cannot change character set id on the handle
Cause: Attempts to change character set id on non-environment handles
Action: Only try to change character set id on environment handles
ORA-24506: invalid attempt to change character set id on env handle
Cause: Attempts to change character set id after other handles have been allocated
from the env handle
Action: Change character set id after creating environment handle but before
allocating any handles from it.
ORA-24507: invalid combination of character set ids
Cause: Attempts to set one character set id as zero
Action: Set both charset and ncharset as zero or non-zero in OCIEnvNlsCreate()
ORA-24508: Buffer is not aligned correctly.
Cause: Alignment error ocurred in buffer when converting between character sets.
Action: Align buffer appropriately. For UTF16 buffer, pass a ub2 pointer.
ORA-24509: OCI function currently not supported in UTF16 mode.

Cause: Attempt to call an OCI function that was not supported in OCI_UTF16ID
mode.
Action: Remove the offending function or do not create an OCI environment with
OCI_UTF16ID mode or OCI_UTF16ID character set ID.
ORA-24530: User not authorized to access column value.
Cause: Column security is enabled and column value is not authorized.
Action: The program needs to handle this error and take appropriate action.
ORA-24531: Column value authorization is unknown.
Cause: Column security is unknown for the column.
Action: Verify the fetched data. It may or may not contain a meaningful value because
it is probably the result of an expression that operated on unauthorized values.
ORA-24536: Warning - column authorization unknown.
Cause: Column security is unknown for one or more columns.
Action: Verify the fetched data. It may or may not contain a meaningful value because
it is probably the result of an expression that operated on unauthorized values.
ORA-24542: PRELIM mode logon not allowed to a pluggable database
Cause: PRELIM mode logon was attempted to a pluggable database.
Action: Create PRELIM mode connections to CDB$ROOT only.
ORA-24543: instance startup or shutdown not allowed in pluggable database
Cause: An instance startup or shutdown operation was attempted when connected to
a pluggable database.
Action: Perform instance startup or shutdown operations by connecting to CDB
$ROOT.
ORA-24544: Oracle RAC One Node instance is already running.
Cause: An instance startup failed because an instance of the Oracle RAC One Node
database was already running on one of the cluster nodes.
Action: In Oracle RAC One Node, avoid any attempt to start a second instance by any
means while the instance is already running.
ORA-24550: unhandled signal #number received. string
Cause: Serious error: signal received
Action: Refer to the platform-specific signal code, and see if the application code
caused the error. Otherwise, record all error state and notify Oracle Support Services.
ORA-24557: error string encountered while handling error string; exiting server
process
Cause: A second-level error occurred in an Oracle server process that required that
process to exit.
Action: None. If an excessive number of incidents are dumped, contact Oracle
Support Services.
ORA-24600: could not create OCI environment
Cause: The Oracle Client library used to communicate with the database failed to
initialize correctly.
ORA-24280 to ORA-28709 72-17
Action: Check that the Oracle environment or registry entries are consistent and
correct. If using the Oracle Instant Client, make sure the Oracle driver for MySQL and
Oracle libraries are from the same release. Make sure you have read access to the
libraries.
ORA-24601: bind buffer not allocated by caller
Cause: A valid buffer was not provided for the bind call.
Action: Provide a non-NULL pointer for the bind call and a valid length for the
buffer.
ORA-24602: attempting to read with no fetch
Cause: A column was being fetched while not in fetch state.
Action: Fetch the column after fetching of the result set has started.
ORA-24750: incorrect size of attribute
Cause: Transaction ID attribute size is incorrect.
Action: Verify that the size parameter is correct.
ORA-24752: OCI_TRANS_NEW flag must be specified for local transactions
Cause: Application attempted to start a local transaction without using
OCI_TRANS_NEW.
Action: Use OCI_TRANS_NEW when starting local transactions.
ORA-24753: local transactions cannot be detached
Cause: An attempt to detach a local transaction was made.
Action: Local transactions may only be committed or rolled back.
ORA-24754: cannot start new transaction with an active transaction
Cause: An attempt to start a new transaction was made when there was an active
transaction.
Action: Commit, rollback or detach the existing transaction before starting a new
transaction.
ORA-24755: OCI_TRANS_NOMIGRATE, OCI_TRANS_JOIN options are not
supported
Cause: These flags are currently not supported.
Action: n/a
ORA-24756: transaction does not exist
Cause: An invalid transaction identifier or context was used or the transaction has
completed.
Action: Supply a valid identifier if the transaction has not completed and retry the
call.
ORA-24757: duplicate transaction identifier
Cause: An attempt was made to start a new transaction with an identifier already in
use by an existing transaction.
Action: Verify that the identifier is not in use.
ORA-24758: not attached to the requested transaction
Cause: An attempt was made to detach or complete a transaction that is not the
current transaction.
Action: 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: Verify that only one of the following values is specified: OCI_TRANS_NEW,
OCI_TRANS_JOIN, OCI_TRANS_RESUME, or OCI_TRANS_PROMOTE.
ORA-24760: invalid isolation level flags
Cause: An invalid isolation level flag was passed.
Action: Verify that only one of following values - OCI_TRANS_READONLY,
OCI_TRANS_READWRITE, OCI_TRANS_SERIALIZABLE is used.
ORA-24761: transaction rolled back
ORA-24762: server failed due to unspecified error
Cause: An internal error has occured in the server commit protocol.
ORA-24763: transaction operation cannot be completed now
Cause: The commit or rollback cannot be performed now because the session cannot
switch to the specified transaction.
ORA-24764: transaction branch has been heuristically committed
ORA-24765: transaction branch has been heuristically rolled back
ORA-24766: transaction branch has been partly committed and aborted
ORA-24767: transaction branch prepare returns read-only
Cause: The transaction is read-only, or this is the outcome of an optimization for twophase commit protocol.
Action: None. Informational only.
ORA-24768: commit protocol error occured in the server
ORA-24769: cannot forget an active transaction
Cause: Transaction identifier refers to an active transaction.
Action: Verify that the identifier of an active transaction was not passed as an
argument.
ORA-24770: cannot forget a prepared transaction
Cause: Transaction identifier refers to a prepared transaction.
Action: Verify that the identifier of a prepared transaction was not passed as an
argument.
ORA-24771: cannot detach, prepare or forget a local transaction
Cause: Service handle contains a local transaction context.
Action: Verify that the transaction context does not refer to a local transaction.
ORA-24280 to ORA-28709 72-19
ORA-24772: Cannot mix tightly-coupled and loosely-coupled branches

Cause: Application attempted to start a transaction with a global transaction identifier
and a wrong option.
Action: Verify that all branches of a global transaction are started with either
OCI_TRANS_TIGHT or OCI_TRANS_LOOSE option. If the application is correct and
uses distributed updates, contact customer support.
ORA-24773: invalid transaction type flags
Cause: OCI_TRANS_TIGHT or OCI_TRANS_LOOSE mode was not specified.
Action: Verify that the right parameters are being used.
ORA-24774: cannot switch 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 that they can be switched.
ORA-24775: cannot prepare or commit transaction with non-zero lock value
Cause: An attempt was made to detach the transaction with a non-zero lock value.
Action: Detach the transaction with lock value set to zero and then try to prepare or
commit the transaction.
ORA-24776: cannot start a new transaction
Cause: An attempt was made to start a new transaction when session was already
attached to an existing transaction.
Action: End the current transaction before creating a new transaction.
ORA-24777: use of non-migratable database link not allowed
Cause: The transaction, which needs to be migratable between sessions, tried to access
a remote database from a non-multi threaded server process.
Action: Perform the work in the local database or open a connection to the remote
database from the client. If multi threaded server option is installed, connect to the
Oracle instance through the dispatcher.
ORA-24778: cannot open connections
Cause: The migratable transaction tried to access a remote database when the session
itself had opened connections to remote database(s).
Action: Close the connection(s) in the session and then try to access the remote
database from the migratable transaction. If the error still occurs, contact Oracle
customer support.
ORA-24779: detach not allowed with open remote cursor
Cause: The migratable transaction tried to detach from the current session while
having an open remote cursor.
Action: Close any open remote cursor prior to detach.
ORA-24780: cannot recover 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 idle too long).
Action: Detach from the current transaction and retry the operation.
ORA-24781: branches don't belong to the same global transaction

Cause: The list of xids passed into kpotxmp() don't have the same gtrid
Action: n/a
ORA-24782: Cannot detach from a non-migratable transaction
Cause: An attempt was made to detach from a non-migrateable transaction.
Action: Either commit or rollback the transaction.
ORA-24783: Cannot switch non-migratable transactions
Cause: An attempt was made to prepare/commit a txn different from current.
Action: n/a
ORA-24784: Transaction exists
Cause: An attempt was made to start a transaction, while attached to a nonmigrateable transaction
Action: n/a
ORA-24785: Cannot resume a non-migratable transaction
Cause: An attempt was made to resume a non-migrateable transaction.
Action: n/a
ORA-24786: separated transaction has been completed
Cause: The current transaction has been completed by another process.
Action: Start a new transaction
ORA-24787: remote cursors must be closed before a call completes
Cause: The previous operation did not close all the remote cursors it opened. Since
separated transactions are enabled, this is not allowed.
Action: Close all remote cursors in each call, or start a regular (non-separated)
transaction.
ORA-24788: cannot switch to specified transaction (server type)
Cause: The transaction specified was created by a shared server and the requestor is a
dedicated server, or the transaction was created by a dedicated server and the
requestor is a shared server.
Action: All parts of this application should connect as dedicated or as shared.
ORA-24789: start not allowed in recursive call
Cause: Oracle RM will not start/resume a branch in a recursive call
Action: Reconsider your application stack design
ORA-24790: cannot mix OCI_TRANS_RESUME and transaction isolation flags
Cause: An attempt was made to change the isolation level of an existing transaction.
ORA-24791: invalid transaction start flags
Cause: An invalid transaction start flag was passed.
Action: Verify that OCI_TRANS_LOOSE was not passed along with
OCI_TRANS_JOIN, OCI_TRANS_RESUME. Also, verify that other flags (such as
OCI_TRANS_SEPARABLE) passed by the client are supported by the version of the
Oracle server.
ORA-24280 to ORA-28709 72-21
ORA-24792: cannot mix services in a single global transaction

Cause: Oracle RM will not serve global (distributed) transaction requests if branches
are created using different services
Action: Configure clients such that those participating in the same distributed
transaction use the same service name.
ORA-24794: no active DTP service found
Cause: Oracle RM will not serve global (distributed) transaction requests until DTP
services are configured in RAC. It is possible that a service was stopped while
transactions were in-flight.
Action: Provision/Start DTP services first.
ORA-24795: Illegal string attempt made
Cause: An illegal attempt was made to commit/rollback current transaction
Action: Use appropriate commit/rollback mechanism
ORA-24796: operation completed; resume of original transaction rolled back
Cause: The commit, rollback, or prepare completed successfully, but the current
transaction for this thread was rolled back.
Action: If desired, retry the current transaction. If the operation was prepare, then end
transaction appropriately with a commit or rollback operation.
ORA-24797: cannot promote the current transaction to a distributed transaction
Cause: An illegal attempt was made to promote the current transaction.
Action: Verify that OCI_ATTR_XID, OCI_ATTR_INTERNAL_NAME, and
OCI_ATTR_EXTERNAL_NAME attributes have been set properly, and verify that the
current transaction has neither performed IDL or PDML operations, nor already been
a distributed transaction. Also, verify that the local transaction is in the same isolation
level if the isolation flag value is set.
ORA-24798: cannot resume the distributed transaction branch on another instance
Cause: An attempt was made to resume a distributed transaction branch that is
physically located on another RAC instance.
Action: Get a connection to the instance where the transaction branch is located.
ORA-24801: illegal parameter value in OCI lob function
Cause: One of the parameter values in the OCI lob function is illegal.
Action: Check every parameter in the OCI Lob function call to make sure they are
correct. Offsets should be greater than or equal to one.
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 lob read
callback function.
ORA-24803: illegal parameter value in lob read function
Cause: Internal error .
Action: This error should not normally occur. If it persists, please contact your
customer service representative.
ORA-24804: Lob read/write functions called while another OCI LOB read/write
streaming is in progress
Action: Wait for the ongoing LOB streaming call to finish before issuing the next
server call, or use OCIBreak() abort the current LOB streaming call.
ORA-24805: LOB type mismatch
Cause: When copying or appending LOB locators, both source and desctination LOB
locators should be of the same type.
Action: Pass the same type of LOB locators for copying or appending.
ORA-24806: LOB form mismatch
Cause: When reading from or writing into LOBs, the character set form of the user
buffer should be same as that of the LOB.
Action: Make sure that the buffer you are using to read or write has the same form as
that of the LOB.
ORA-24807: LOB form mismatch
Cause: When copying or appending LOBs, both source and desctination LOB locators
should have the same character set form.
Action: Pass locators of the same character set form for copying or appending LOBs.
ORA-24808: streaming of lob data is not allowed when using lob buffering
Cause: Attempted to stream lob data via the polling mode or a callback when lob
buffering was enabled for the input lob locator.
Action: Lob buffering is useful when reading/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 streaming of data is required, lob buffering should
not be used. In this case, flush buffers associated with the input lob locator as
necessary, disable buffering on the input lob locator and reissue the OCILobRead/
OCILobWrite call.
ORA-24809: amount specified will not fit in the lob buffers
Cause: LOB buffering is enabled for the input lob locator so buffering will be used.
However, the amount of lob data to read or write is larger than what the lob buffers
can hold.
Action: Either disable buffering on the input lob locator and reissue the command or
pass a smaller amount.
ORA-24810: attempting to write more data than indicated
Cause: While writing into a LOB, more data was supplied than indicated.
Action: If data is written in pieces, then make sure that you do not provide more data
in the pieces (cumulatively), than you indicated.
ORA-24811: less data provided for writing than indicated
Cause: While writing into a LOB, less data was provided than indicated.
Action: If writing data in single pieces, then make sure that the buffer length specified
is big enough to accommodate tha data being provided. If data is written in pieces,
then make sure that all the data has been provided before specifying
OCI_LAST_PIECE.
ORA-24280 to ORA-28709 72-23
ORA-24812: character set conversion to or from UCS2 failed

Cause: If the database character set is varying-width, the CLOB/NCLOB value is
implicitly converted to or from UCS2. This implicit conversion failed.
ORA-24813: cannot send or receive an unsupported LOB
Cause: An attempt was made to send a LOB across the network, but either 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 server are running
different versions of Oracle.
Action: Use a version of the Oracle that supports the LOB on both the client and the
server.
ORA-24814: operation not allowed for temporary LOBs
Cause: Temporary LOB locators are not allowed in the operation. For example:
OCILobAssign only takes persistent LOB locators as parameters, not temporary
LOBs.
Action: Use OCILobLocatorAssign for temporary LOBs instead. Note that
OCILobLocatorAssign can also be used for persistent LOBs, in which case it will
behave the same as OCILobAssign.
ORA-24815: Invalid character set form
Cause: An invalid character set form was passed into an OCI LOB function. For
example, the only valid cs form for OCILobCreateTemporary() is OCI_DEFAULT(0),
SQLCS_IMPLICIT(1) or SQLCS_NCHAR(2).
Action: Specify a valid character set form.
ORA-24816: Expanded non LONG bind data supplied after actual LONG or LOB
column
Cause: A Bind value of length potentially > 4000 bytes follows binding for LOB or
LONG.
Action: Re-order the binds so that the LONG bind or LOB binds are all at the end of
the bind list.
ORA-24817: Unable to allocate the given chunk for current lob operation
Cause: The given size is increased to accomodate the number of bytes from server due
to varying width db char/nchar set.
Action: Use smaller chunk sizes when you have character set conversion between
client/server or perform piece-wise read or write.
ORA-24818: Operation not permitted on Abstract LOBs
Cause: Abstract LOB locators were not allowed in the operation. For example,
OCILobAssign only takes persistent LOB locators as parameters, not Abstract (i.e.,
client-side created) LOBs.
Action: Avoid the operation on Abstract LOBs.
ORA-24819: Illegal reference count encountered for a temporary LOB
Services.
ORA-24820: Differnt LOB function called while another OCI LOB call is in
progress
Cause: An attempt was made to execute a new OCI LOB call while another OCI LOB
call was in progress.
Action: Wait for the ongoing LOB streaming call to finish before issuing the next
server call, or use OCIBreak() to abort the current LOB streaming call.
ORA-24850: failed to startup shared subsystem
Cause: While attempting to initialize OCI in shared mode, a problem was
encountered in starting up the shared subsystem.
Action: Contact Oracle Customer support.
ORA-24851: failed to connect to shared subsystem
encountered in connecting the process to the shared subsystem.
ORA-24852: protocol error during statement execution
Cause: An internal protocol error occurred while receiving describe data from the
server during execution of a statement.
ORA-24853: failed to connect thread to shared subsystem
encountered in connecting the thread to the shared subsystem.
ORA-24854: invalid pieceinfo provided
Cause: While making the first call to write LOB data, an invalid pieceinfo value
provided.
Action: Correct the call to use OCI_ONE_PIECE or OCI_FIRST_PIECE. If using OCCI,
make sure to call writeBuffer before calling writeLastBuffer.
ORA-24900: invalid or unsupported mode parameter passed in call
Cause: The mode parameter passed into the OCI Client Notification call is incorrect.
Action: Please correct the mode parameter passed into OCI.
ORA-24901: handles belonging to different environments passed into an OCI call
Cause: All handles passed into an OCI call should belong to the same environment. In
the call that returned this error, handles belonging to different environments were
passed in.
Action: Please ensure that the handle parameters in the call to come from the same
OCI Environment.
ORA-24902: invalid subscription name or name-length in subscription handle
Cause: The subscription handle passed into the OCI call does not have a proper name
or name-length attribute.
Action: Please set the name and name-length attributes using the OCIAttrSet() call.
ORA-24280 to ORA-28709 72-25
ORA-24903: invalid namespace attribute passed into OCI call

Cause: The subscription handle passed into the OCI call does not have a proper
namespace attribute.
Action: Please set the namespace attribute using the OCIAttrSet() call.
ORA-24904: invalid callback attribute passed into OCI call
Cause: The subscription handle passed into the OCI call does not have a proper
callback attribute.
Action: Please set the callback attribute using the OCIAttrSet() call.
ORA-24905: invalid recipient protocol attribute passed into OCI call
Cause: The subscription handle passed into the OCI call did not have a proper
recipient protocol attribute.
Action: Please set the recipient protocol attribute using the OCIAttrSet() call.
ORA-24906: invalid recipient attribute passed into OCI call
Cause: The subscription handle passed into the OCI call did not have a proper
recipient attribute.
Action: Please set the recipient attribute using the OCIAttrSet() call.
ORA-24907: invalid pair of callback and recipient protocol attributes
Cause: The subscription handle passed into the OCI call can't have both the callback
defined and a recipient protocol other than OCI_SUBSCR_PROTO_OCI at the same
time.
Action: Please set the appropriate callback and recipient protocol attributes using the
OCIAttrSet() call.
ORA-24908: invalid recipient presentation attribute
Cause: The subscription handle passed into the OCI call does not have a valid
recipient presentation attribute.
Action: Set the recipient presentation attribute using the OCIAttrSet() call
ORA-24909: call in progress. Current operation cancelled
Cause: The OCI call was invoked when another call on the connection was in
progress.
Action: Check if the OCI call is supported when the call is in progress under special
conditions; for example, if it is being used by a signal handler.
ORA-24911: Cannot start listener thread at specified port
Cause: Thread already running at a different port.
Action: Set the correct port in the environment handle or let the system choose the
port.
ORA-24912: Listener thread failed. string
Cause: Thread listening for event notification exited because of an error. The error
encountered is appended to the error message.
Action: The client needs to be restarted.
ORA-24913: Event to enable NLS validation
Cause: N/A
Action: Set this event in your environment to enable NLS character validation even
when character sets are the same for client/server.
ORA-24915: Cannot start Listener at specified IP address
Cause: Thread was already listening at a different IP address.
Action: Set the correct IP address in the environment handle or let the system choose
the correct IP address.
ORA-24916: cannot use IP address attribute before release 11.2 compatible
notifications
Cause: An attempt was made to use OCI_ATTR_SUBSCR_IPADDR attribute before
release 11.2 compatible notifications.
Action: Change the compatibility to 11.2.
ORA-24918: secure notification mode not supported
Cause: An attempt was made to use OCI_SECURE_NOTIFICATION before release
12.0 compatible notifications.
ORA-24919: subscription to Fast Application Notification failed
Cause: An error occurred while subscribing to Fast Application Notification. This
could be due to problems in the Oracle clusterware configuration.
Action: Look at the client trace files for additional information. Ensure that the Oracle
clusterware is properly configured.
ORA-24920: column size too large for client
Cause: Client attempted to fetch a column whose size is larger than the maximum size
that can be handled by the client.
Action: Upgrade the client stack to Oracle 12c or higher.
ORA-24940: invalid combination of string namespace, string presentation and
string receive protocol
Cause: An invalid combination of namespace, presentation and receive protocol was
specified during notification registration. Currently, only AQ namespace is supported
with XML presentation. Non-AQ namespace is not supported for e-mail and HTTP
receive protocols.
Action: Please change the register call appropriately.
ORA-24941: invalid combination of notification grouping attributes
Cause: An invalid combination of notification grouping attributes was specified.
Currently, only TIME notification grouping class is supported. If notification
grouping class is zero, all other notification grouping attributes must be zero.
Action: Refer to documentation and change the attributes appropriately.
ORA-24942: cannot use ntfn grouping attributes on before release 11.0 compatible
ntfns
Cause: An attempt was made to use notification grouping on before release 11.0
compatible notifications.
ORA-24280 to ORA-28709 72-27
ORA-24943: cannot use ntfn grouping with this receive protocol, presentation
and/or QoS
Cause: An attempt was made to use notification grouping with e-mail or HTTP
receive protocol or XML presentation or payload delivery or reliable QoS. Currently,
only OCI and PLSQL receive protocols and default presentation are supported with
notification grouping.
Action: Refer to documentation and change the call appropriately.
ORA-24944: cannot use timeout or grouping with ANONYMOUS namespace
Cause: An attempt was made to use timeout or grouping with ANONYMOUS
namespace. Currently, timeout and grouping are supported only with AQ and
DBCHANGE namespaces.
Action: Refer to documentation and change the call appropriately.
ORA-24945: cannot use context, QOS and timeout attributes of notification on
lower than 10.2 compatible notifications
Cause: An attempt was made to use context, QOS and timeout attributes of
notification on lower than 10.2 compatible notifications.
Action: Change the database compatibility to 10.2.
ORA-24946: invalid registration callback
Cause: An attempt was made to use a reserved callback for notification registration.
Action: Choose a different name for the notification callback and change the register
call appropriately.
ORA-24947: Invalid namespace attribute specified for the subscription string
Cause: An attempt was made to register with invalid namespace attribute.
Action: Refer to documentation and change the namespace appropriately.
ORA-24950: unregister failed, registration not found
Cause: The registration that was asked to be unregistered could not be found.
Action: Please check the callback function name and the subscription name in the
unregister call.
ORA-24952: register, unregister or post has incorrect collection count
Cause: The register, unregister or post function was invoked with a collection that
was smaller than the size specified by the parameter to the function.
Action: Please check the function's use and ensure that the size parameter is correct.
ORA-24960: the attribute string is greater than the maximum allowable length of
number
Cause: The user attempted to pass an attribute that is too long
Action: Shorten the specified attribute and retry the operation.
ORA-24962: connect string could not be parsed, error = string
Cause: The address portion of the connect string could not be parsed. The client may
be using a format of the connect string that the server does not understand.
Action: Correct the connect string.
ORA-24981: deferred SGA thread spawn failed
Action: None
ORA-24982: deferred SGA segment allocation failed, index = string location =
string
Cause: System-defined shared memory limits are inadequate for Oracle.
Action: Consult the alert file for details.
ORA-24983: defer SGA thread memory allocation failed
Action: None
ORA-24984: SGA allocation slaves termination failed
Action: None
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: Remove the bind variable. To access the table columns use (new/
old).column_name.
ORA-25001: cannot create this trigger type on this type of view
Cause: INSTEAD OF triggers can be created on any view which is not an Editioning
View, while BEFORE and AFTER triggers may only be created on Editioning Views.
Action: Change the trigger type to INSTEAD OF or change the view on which you are
attempting to create a DML trigger.
ORA-25002: cannot create INSTEAD OF triggers on tables
Cause: Only BEFORE or AFTER triggers can be created on a table.
Action: Change the trigger type to BEFORE or AFTER.
ORA-25003: cannot change NEW values for this column type in trigger
Cause: Attempt to change NEW trigger variables of datatype object, REF, nested
table, VARRAY or LOB datatype which is not supported.
Action: Do not change the NEW trigger variables in the trigger body.
ORA-25004: WHEN clause is not allowed in INSTEAD OF triggers
Cause: WHEN clause is specified in an INSTEAD OF trigger.
Action: Remove the WHEN clause when creating an INSTEAD OF trigger.
ORA-25005: cannot CREATE INSTEAD OF trigger on a read-only view
Cause: attempt to create an INSTEAD OF trigger on a view created with read-only
option. The view cannot be updated using INSTEAD OF triggers.
Action: Do not create the trigger.
ORA-25006: cannot specify this column in UPDATE OF clause
Cause: Attempt to create a trigger on update of a column whose datatype is
disallowed in the clause, such as LOB and nested table.
Action: Remove the UPDATE OF clause.
ORA-24280 to ORA-28709 72-29
ORA-25007: functions or methods not allowed in WHEN clause

Cause: PLSQL function call or method invocation is not allowed in the WHEN clause
when creating a trigger.
Action: Remove the function call or method invocation from the WHEN clause.
ORA-25008: no implicit conversion to LOB datatype in instead-of trigger
Cause: When inserting or updating a view using instead-of trigger, the new value for
a LOB view column is of a different datatype.
Action: Specified a LOB value as the new value for the LOB view column.
ORA-25009: Nested table clause allowed only for INSTEAD OF triggers
Cause: Triggers on nested tables can only be created on view columns using
INSTEAD OF triggers.
Action: Use view nested table columns for defining 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 correspond to a nested table column.
Action: Specify a nested table column on which the trigger is to be defined.
ORA-25011: cannot create trigger on internal AQ table
Cause: An attempt was made to try to create a trigger on a table that is used internally
to support the Advanced Queueing (AQ) feature.
Action: Do not create the trigger.
ORA-25012: PARENT and NEW values cannot be identical
Cause: The referencing clause specifies identical values for PARENT and OLD.
Action: Re-specify either the PARENT or NEW referencing value.
ORA-25013: OLD and PARENT values cannot be identical
Cause: The referencing clause specifies identical values for OLD and PARENT.
Action: Re-specify either the OLD or PARENT referencing value.
ORA-25014: cannot change the value of a PARENT reference variable
Cause: Parent values can only be read and not changed.
Action: Do not attempt to change a Parent variable.
ORA-25015: cannot perform DML on this nested table view column
Cause: DML cannot be performed on a nested table view column except through an
INSTEAD OF trigger
Action: Create an INSTEAD OF trigger over the nested table view column and then
perform the DML.
ORA-25016: cannot specify column list for insert into nested table view column
Cause: A column list cannot be specified for inserts into the nested table view column.
Action: Specify all the columns for insert into the nested table.
ORA-25017: cannot reference NEW ROWID for movable rows in before triggers
Cause: NEW ROWID was referenced in a before row trigger which is defined on an
index-organized table, or a partitioned table with enabled movement of rows. The
ROWID cannot be computed in a before row update trigger because it depends on the
actual values of the row
Action: Remove references to NEW ROWID from the trigger definition.
ORA-25018: conflicting trigger string already exists
Cause: Conflicting instead of DDL trigger on schema/database already exists.
Action: Remove the old trigger
ORA-25019: too much concurreny
Cause: cannot pin the database/schema because of too much concurrency
Action: try the operation later
ORA-25020: renaming system triggers is not allowed
Cause: renaming system triggers is not allowed
Action: Drop the trigger, and create a new one for the same
ORA-25021: cannot reference a trigger defined on another table
Cause: Referenced trigger in the FOLLOWS clause was defined on another table.
Action: Create the referenced trigger on the same table
ORA-25022: cannot reference a trigger of a different type
Cause: Referenced trigger in the FOLLOWS or PRECEDES clause was either a
different type or not a compound trigger.
Action: Create the referenced trigger as the same type or a compound trigger.
ORA-25023: Cyclic trigger dependency is not allowed
Cause: A cycle of trigger dependency can be formed.
Action: Do not create a trigger that can formed a cyclic dependency.
ORA-25024: cannot specify FOLLOWS for a REVERSE CROSSEDITION trigger
Cause: The FOLLOWS clause was specified when creating the REVERSE
CROSSEDITION trigger.
Action: Do not create a REVERSE CROSSEDITION trigger with a FOLLOWS clause.
ORA-25025: cannot specify PRECEDES clause
Cause: The PRECEDES clause was specified when creating a FORWARD
CROSSEDITION trigger or a regular trigger.
Action: Do not create a FORWARD CROSSEDITION or a regular trigger with a
PRECEDES clause.
ORA-25026: FOR EACH ROW was specified with compound triggers
Cause: FOR EACH ROW is not allowed with compound triggers.
Action: Remove the FOR EACH ROW clause.
ORA-25027: compound triggers cannot be used as system triggers
Cause: Compound trigger was defined as system trigger.
Action: Do not use compound trigger as system trigger.
ORA-25028: regular trigger body can not start with keyword COMPOUND
Cause: Regular triggers body should start with BEGIN/DECLARE etc .
Action: Fix the syntax and recompile.
ORA-24280 to ORA-28709 72-31
ORA-25029: compound triggers should always start with keyword COMPOUND

Cause: Compound trigger body was started with incorrect keyword.
Action: Fix the syntax and recreate.
ORA-25030: crossedition trigger cannot be owned by a non-editioned user
Cause: An attempt was made to create a crossedition trigger in a schema where
triggers were not editionable.
Action: Enable editions for the user for triggers and then create the crossedition
trigger.
ORA-25031: only a crossedition trigger may be specified
Cause: The trigger specified was not a crossedition trigger.
Action: Specify a crossedition trigger.
ORA-25032: crossedition trigger cannot be created in ORA$BASE
Cause: An attempt was made to create crossedition trigger in the ORA$BASE edition.
Action: Do not create a crossedition trigger in the ORA$BASE edition.
ORA-25033: triggers cannot be executed at this time
Cause: An attempt was made to execute a trigger when the session was almost
finished.
Action: Do not attempt to DML with triggers that are expected to execute when
session has almost ended.
ORA-25034: cannot bypass trigger owned by another user
Cause: An attempt was made to do DML from a crossedition trigger on an object that
has a non-crossedition trigger owned by another user. DML from a crossedition
trigger bypasses the running of non-crossedition triggers; this cannot be allowed for
triggers owned by other users.
Action: Permit the non-crossedition trigger to be bypassed by attaching it to the
editioning view rather than the table, moving one of the triggers to be in the same
schema as the other, or explicitly disabling the non-crossedition trigger.
ORA-25035: cannot perform DML on remote object from a crossedition trigger
Cause: An attempt was made to do DML from a crossedition trigger that would
modify data in a remote database. DML from a crossedition trigger has special rules
applied regarding what triggers will fire as part of that DML; these special rules
cannot be applied across database links and therefore the DML cannot be allowed.
Action: Perform the DML in a helper function separate from the crossedition trigger
itself; the special rules are not applied when the DML is not issued from within the
crossedition trigger itself.
ORA-25100: TABLESPACE option can only be used with ALTER INDEX REBUILD
Cause: The TABLESPACE option to ALTER INDEX was used without the REBUILD
option.
Action: Use ALTER INDEX REBUILD TABLESPACE tablespace name.
ORA-25101: duplicate REBUILD option specification
Cause: The REBUILD option to ALTER INDEX is specified more than once.
ORA-25102: PARALLEL option can only be used with ALTER INDEX REBUILD
Cause: The PARALLEL option to ALTER INDEX was used without the REBUILD
option.
Action: Use ALTER INDEX REBUILD.
ORA-25103: NOPARALLEL option can only be used with ALTER INDEX
REBUILD
Cause: The NOPARALLEL option to ALTER INDEX was used without the REBUILD
option.
ORA-25104: UNRECOVERABLE option can only be used with ALTER INDEX
REBUILD
Cause: The UNRECOVERABLE option to ALTER INDEX was used without the
REBUILD option.
ORA-25105: RECOVERABLE option can only be used with ALTER INDEX
REBUILD
Cause: The RECOVERABLE option to ALTER INDEX was used without the
REBUILD option.
ORA-25106: only one of PARALLEL or NOPARALLEL clause may be specified
Cause: PARALLEL was specified more than once, NOPARALLEL was specified more
than once, or both 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: the TABLESPACE was specified more than once in an ALTER INDEX
REBUILD statement.
Action: Remove all but one of the TABLESPACE clauses.
ORA-25108: standby lock name space exceeds size limit of string characters
Cause: The lock name space for the standby database exceeded the maximum string
length.
Action: Change initialization parameter _STANDBY_LOCK_NAME_SPACE to a
character string of less than the specified characters.
ORA-25109: standby lock name space has illegal character 'string'
Cause: An invalid lock name space was specified for the standby database. The lock
name space for the standby database can only contain A-Z, 0-9, '_', '#', '$', '.' and '@'
characters.
Action: Change initialization parameter _STANDBY_LOCK_NAME_SPACE to a
valid character string.
ORA-25110: NOSORT may not 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-24280 to ORA-28709 72-33
ORA-25111: creation of BITMAP cluster indices 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.
ORA-25112: maximum number of BITMAP index columns is 30
Cause: Too many columns were specified for the index.
Action: Create an index on fewer columns.
ORA-25113: GLOBAL may not 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 the DUMP DATAFILE/TEMPFILE
command
Cause: An invalid file number was used in dumping a datafile or tempfile.
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 the DUMP DATAFILE/TEMPFILE
command
Cause: An invalid block number was used in dumping a datafile or tempfile.
Action: Specify a valid block number.
ORA-25117: MIN/MAX/Block Number expected
Cause: A value other than MIN/MAX, or a block number was entered in the DUMP
DATAFILE/TEMPFILE command.
ORA-25118: invalid DUMP DATAFILE/TEMPFILE option
Cause: An invalid option was specified for the DUMP DATAFILE/TEMPFILE
command.
ORA-25119: LOGGING/NOLOGGING option already specified
Cause: In CREATE TABLESPACE, the LOGGING and/or NOLOGGING options
were specified more than once.
Action: Remove all but one of the logging 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 MINIMUM EXTENT specifications.
ORA-25121: MINIMUM EXTENT value greater than maximum extent size
Cause: In CREATE/ALTER TABLESPACE, the value specified for the MINIMUM
EXTENT option was greater than the maximum extent size.
Action: Choose a lower value for the MINIMUM EXTENT option.

ORA-25122: Only LOCAL bitmap indexes are permitted on partitioned tables
Cause: An attempt was made to create a global bitmap index on a partioned table.
Action: create a local bitmap index instead.
ORA-25123: Too many components specified in the name.
Cause: Specifying more components to a name than allowed.
Action: Check the name specified for the operation.
ORA-25124: Database link name not allowed.
Cause: Specifying a database link name when it is not permitted.
Action: Check the name specified for the operation.
ORA-25125: BUFFER_POOL/FLASH_CACHE/CELL_FLASH_CACHE storage
option not allowed
Cause: An attempt was made to specify the BUFFER_POOL, FLASH_CACHE, or
CELL_FLASH_CACHE storage option. This option may only be specified during CREATE or ALTER TABLE - CREATE or ALTER CLUSTER - CREATE or ALTER
INDEX
Action: Remove this option and retry the statement.
ORA-25126: Invalid name specified for BUFFER_POOL/FLASH_CACHE/
CELL_FLASH_CACHE
Cause: The name of the cache hints specified by was invalid. The only valid names for
BUFFER_POOL are KEEP, RECYCLE and DEFAULT. The only valid names for
FLASH_CACHE and CELL_FLASH_CACHE are KEEP, NONE and DEFAULT.
Action: Use a valid name or remove the BUFFER_POOL, FLASH_CACHE, or
CELL_FLASH_CACHE clause.
ORA-25127: RELY not allowed in NOT NULL constraint
Cause: An attempt to set RELY on for NOT NULL constraint.
Action: only NORELY may be specified for a NOT NULL constraint.
ORA-25128: No insert/update/delete on table with constraint (string.string)
disabled and validated
Cause: Try to insert/update/delete on table with DISABLE VALIDATE constraint.
Action: Change the constraint's states.
ORA-25129: cannot modify constraint (string) - no such constraint
Action: Obvious
ORA-25130: cannot modify primary key - primary key not defined for table
Cause: Attempted to modify a primary key that is not defined for the table.
Action: None
ORA-25131: cannot modify unique(string) - unique key not defined for table
Cause: attempted to modify a unique key that is not deined for the table.
Action: None
ORA-24280 to ORA-28709 72-35
ORA-25132: UNIQUE constraint (string.string) disabled and validated in ALTER

TABLE EXCHANGE PARTITION
Cause: cannot ALTER TABLE EXCHANGE PARTITION when the partition and the
table have a disabled and validated unique constraints AND the unique keys in the
partion is not mutually exclusive from the rest of the table.
Action: Change the constraint's status.
ORA-25133: duplicate SINGLE TABLE option specified
Cause: The SINGLE TABLE option was specified more than once.
Action: Specify the SINGLE TABLE option only once.
ORA-25134: keyword TABLE expected
Cause: The keyword TABLE is missing from the SINGLE TABLE option.
Action: Place the keyword TABLE after the keyword SINGLE in the command.
ORA-25135: cannot use the SINGLE TABLE option
Cause: The SINGLE TABLE option is only valid for hash clusters.
Action: Do not specify the SINGLE TABLE option.
ORA-25136: this cluster can contain only one table
Cause: An attempt was made to store more than one table in a cluster that was
created with the SINGLE TABLE option.
Action: Do not attempt to store more than one table in the cluster.
ORA-25137: Data value out of range
Cause: Value from cast operand is larger than cast target size.
Action: Increase size of cast target.
ORA-25138: string initialization parameter has been made obsolete
Cause: An obsolete initialization parameter has been specified
Action: The system will come up, but parameters must be examined
ORA-25139: invalid option for CREATE TEMPORARY TABLESPACE
Cause: An invalid option appears.
Action: Specify one of the valid options: TEMPFILE, EXTENT MANAGEMENT
LOCAL, UNIFORM
ORA-25140: string space policy cannot be specified for the string extent
management
Action: Make sure that for LOCAL extent management UNIFORM or
AUTOALLOCATE is specified, and for DICTIONARY extent management
UNIFORM or AUTOALLOCATE are not specified
ORA-25141: invalid EXTENT MANAGEMENT clause
Cause: An invalid option appears for EXTENT MANAGEMENT clause
Action: Specify one of the valid options: UNIFORM SIZE, AUTOALLOCATE
ORA-25142: default storage clause specified twice
Cause: default storage clause was specified twice for create tablespace
Action: Specify it once.
ORA-25143: default storage clause is not compatible with allocation policy

Cause: default storage clause was specified for a tablespace with AUTOALLOCATE
or UNIFORM policy
Action: Omit the storage clause
ORA-25144: invalid option for CREATE TABLESPACE with TEMPORARY
contents
Action: Specify one of the valid options: EXTENT 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: EXTENT MANAGEMENT option already specified
Cause: In CREATE TABLESPACE, the EXTENT MANAGEMENT option was
Action: Remove all but one of the EXTENT MANAGEMENT specifications.
ORA-25147: UNIFORM SIZE value greater than 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 lower value for the UNIFORM SIZE option.
ORA-25148: ONLINE option not permitted
Cause: An attempt was made to specify ONLINE for ALTER TABLE MOVE on a
table that is not index-organized. The ONLINE option is currently supported only for
index-organized tables.
Action: Remove the ONLINE option from the command.
ORA-25149: Columns of UROWID type may not be indexed
Cause: An attempt was made to create an index on a column of UROWID type
Action: Remove the column from the list of indexed columns
ORA-25150: ALTERING of extent parameters not permitted
Cause: An attempt was made to alter the extent parameters for a segment in a
tablespace with autoallocate or uniform extent allocation policy.
Action: Remove the appropriate extent parameters from the command.
ORA-25151: Rollback Segment cannot be created in this tablespace
Cause: An attempt was made to create a rollback segment in a tablespace with
autoallocate extent allocation policy.
Action: 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 being used by online users
Action: The TEMPFILE has been taken offline. Try again, later.
ORA-24280 to ORA-28709 72-37
ORA-25153: Temporary Tablespace is Empty

Cause: An attempt was made to use space in a temporary tablespace with no files.
Action: Add files to the tablespace using ADD TEMPFILE command.
ORA-25154: column part of USING clause cannot have qualifier
Cause: Columns that are used for a named-join (either a NATURAL join or a join with
a USING clause) cannot have an explicit qualifier.
Action: Remove the qualifier.
ORA-25155: column used in NATURAL join cannot have qualifier
Cause: Columns that are used for a named-join (either a NATURAL join or a join with
a USING clause) cannot have an explicit qualifier.
Action: Remove the qualifier.
ORA-25156: old style outer join (+) cannot be used with ANSI joins
Cause: When a query block uses ANSI style joins, the old notation for specifying
outer joins (+) cannot be used.
Action: Use ANSI style for specifying outer joins also.
ORA-25157: Specified block size string is not valid
Cause: An attempt was made to create a tablespace with a block size which is not
supported.
Action: Specify one of the valid blocksizes i.e the standard blocksize or one of (2k, 4k,
8k, 16k, 32k) subject to the maximum and minimum blocksizes supported by the
platform.
ORA-25158: Cannot specify RELY for foreign key if the associated primary key is
NORELY
Cause: RELY is specified for the foreign key contraint, when the associated primary
key constraint is NORELY.
Action: Change the option of the primary key also to RELY.
ORA-25159: Must specify a valid tablespace number
Cause: A valid tablespace number was missing.
Action: Specify a valid tablespace number.
ORA-25160: Must specify a valid relative data block address
Cause: A valid relative data block address was missing.
Action: Specify a valid relative data block address.
ORA-25161: Cannot have both DBA and RDBA options
Cause: Both the DBA and RDBA options were passed to ALTER SYSTEM DUMP
REDO.
Action: Use either the DBA option or the RDBA option but not both.
ORA-25162: Must specify both RDBA MIN and RDBA MAX options
Cause: Only one RDBA option was passed to ALTER SYSTEM DUMP REDO.
Action: Specify both RDBA MIN and RDBA MAX.
ORA-25163: Invalid tablespace number or relative data block address

Cause: The relative data block adress is invalid for the given tablespace number or the
table space number is invalid.
Action: Specify a valid tablespace number or relative data block address.
ORA-25164: The tag expression is too complex.
Cause: The statement tag value was not specified using a simple expression.
Action: Reduce the complexity of the statement tag expression. For example, assign
the tag expression to a variable and reference the variable in the error logging clause.
ORA-25165: number of passwords in statement exceeds maximum limit of string
Cause: The SQL statement had more passwords than the maximum limit allowed.
Action: Reconstruct the SQL statement to have a number of passwords less than or
equal to the maximum allowed.
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 permitted for primary key
Cause: Storage parameters cannot be defined for a PRIMARY KEY constraint for a
table with this organization
Action: Remove storage specification for primary key
ORA-25177: UNRECOVERABLE option not permitted
Cause: The UNRECOVERABLE option may not be specified for a primary key for a
table with this organization
Action: Remove UNRECOVERABLE option for primary key
ORA-25178: duplicate PCTTHRESHOLD storage option specification
Cause: The storage option PCTTHRESHOLD is specified more than once.
Action: Specify storage options at most once.
ORA-25179: invalid PCTTHRESHOLD storage option value
Cause: The specified value must be a positive integer.
ORA-25180: PCTTHRESHOLD 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: ON keyword required to specify nested index column nest
Action: Add ON keyword
ORA-25182: feature not currently available for index-organized tables
Cause: An attempt was made to use one or more of the following feature(s) not
currently supported for index-organized tables: CREATE TABLE with LOB/BFILE/
VARRAY columns, partitioning/PARALLEL/CREATE TABLE AS SELECT options,
ALTER TABLE with ADD/MODIFY column options, CREATE INDEX
Action: Do not use the disallowed feature(s) in this release.
ORA-24280 to ORA-28709 72-39
ORA-25183: index-organized table top index segment is in a different tablespace

Cause: An attempt was made to drop a tablespace which contains an index only
table's overflow segment but not the top index segment"
Action: find index-organized tables which span the tablespace being dropped and
some other tablespace(s). Drop these tables.
ORA-25184: column name expected
Cause: A column name is not present where required by the CREATE TABLE for
specifying last column to be included in the index segment of the index-organized
table
Action: Specify a column name where required by the syntax.
ORA-25185: index column other than last can not be specified for INCLUDE clause
Cause: An index column name other than the last is specified as including column
Action: Specify either a column name which is not part of index-organized table
primary key index , or the last key column of the primary key for the INCLUDING
clause.
ORA-25186: INCLUDING clause specified for index-organized table without
OVERFLOW
Cause: INCLUDING clause of a CREATE TABLE is an valid option only for indexorganized tables with OVERFLOW clause (at creation time) or if an OVERFLOW
segment already exists (at ALTER time).
Action: Specify OVERFLOW clause for the index-organized table : For ALTER,
perform ADD OVERFLOW first.
ORA-25187: specified exceptions table form incorrect
ORA-25188: cannot drop/disable/defer the primary key constraint for indexorganized tables or sorted hash cluster
ORA-25189: illegal ALTER TABLE option for an index-organized table
Cause: During ALTER of a 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 may not be combined
with other operations
Cause: ALTER TABLE statement attempted to combine an index-organized table
maintenance operation (e.g. changing physical attributes) with some other operation
(e.g. ADD constraint) which is illegal
Action: Ensure that a index-organized table maintenance operation is the sole
operation specified in ALTER TABLE statement;
ORA-25191: cannot reference overflow table of an index-organized table
Cause: An attempt to directly access the overflow table of an index-organized table
Action: Issue the statement against the parent index-organized table containing the
specified overflow table.
ORA-25192: invalid option for an index-organized table

Cause: An attempt to specify one or more of the following options for an indexorganized table: [NO]CACHE, NO LOGGING, CLUSTER
Action: Remove the illegal option(s)
ORA-25193: cannot use COMPRESS option for a single column key
Cause: An attempt to use COMPRESS option on 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
ORA-25195: invalid option for index on an index-organized table
Cause: An attempt to specify one or more of the following options for index on an
IOT: BITMAP, REVERSE, PCTUSED
Action: n/a
ORA-25196: keyword MOVE in ALTER TABLE MOVE must immediately follow
table name
Cause: MOVE specified after one/more other ALTER options
Action: Change order of options, MOVE should be first Remove the illegal option(s)
ORA-25197: an overflow segment already exists for the indexed-organized table
Cause: An attempt was made to ADD OVERFLOW segment on an index-organized
table that already has an overflow segment
Action: n/a
ORA-25198: only range, list, and hash partitioning are supported for indexorganized table
Cause: System, or Composite partitioning schemes are not supported yet
Action: Select a different partitioning scheme
ORA-25199: partitioning key of a index-organized table must be a subset of the
primary key
Cause: An attempt to specify a partitioning key which is not a prefix of the primary
key of the index-organized table
Action: Select a different partitioning key
ORA-25200: invalid value string, QUEUE_NAME should be [SCHEMA.]NAME
Cause: A NULL parameter was specified for QUEUE_NAME.
Action: Specify a non-NULL queue name.
ORA-25201: invalid value, VISIBILITY should be ON_COMMIT or IMMEDIATE
Cause: An invalid value specified for parameter VISIBILITY.
Action: Specify either ON_COMMIT or IMMEDIATE.
ORA-25202: invalid value NULL, string should be non-NULL
Cause: A NULL value was specified for the parameter.
Action: Specify a non-NULL value.
ORA-24280 to ORA-28709 72-41
ORA-25203: invalid value string, DELAY should be non-negative

Cause: A negative value or NULL was specified for DELAY.
Action: Specify a non negative integer for DELAY.
ORA-25204: invalid value, SEQUENCE_DEVIATION should be BEFORE or TOP
Cause: An invalid SEQUENCE_DEVIATION was specified.
Action: Specify either the option 'BEFORE' or 'TOP'.
ORA-25205: the QUEUE string.string does not exist
Cause: The specified queue does not exist.
Action: Create the queue first before specifying it for enqueue or dequeue.
ORA-25206: enqueue failed, enqueue to exception queue string.string not permitted
Cause: An attempt was made to enqueue to an exception queue.
Action: Try enqueueing to another queue.
ORA-25207: enqueue failed, queue string.string is disabled from enqueueing
Cause: The queue has been stopped to prevent any further enqueueing.
Action: Enable the queue first by using an administrative operation.
ORA-25208: RELATIVE_MSGID must be specified if SEQUENCE_DEVIATION is
BEFORE
Cause: A relative message identifier should be specified if sequence deviation is
specified as BEFORE.
Action: Either specify an existing relative message identifier or don't specify sequence
deviation as BEFORE.
ORA-25209: invalid value string, EXPIRATION should be non-negative or NEVER
Cause: The expiration is less than zero or NULL.
Action: Specify a valid value for expire_after which should be greater than or equal to
zero or NEVER.
ORA-25210: invalid value for RELATIVE_MSGID, no message in queue with that
msgid
Cause: No message inm the queue with the msgid equal to the specified
RELATIVE_MSGID.
Action: Try again with a valid RELATIVE_MSGID.
ORA-25211: invalid DELAY specified when using sequence deviation
Cause: The DELAY specified in the enqueue is greater than the delay of the message
with the given relative message id.
Action: Set the DELAY 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 the messages in the queue.
ORA-25212: invalid PRIORITY specified when using sequence deviation
Cause: The PRIORITY specified in the enqueue is less than the priority of the message
with the given relative message id.
Action: Set the PRIORITY to be less than the delay of the message with the given
relative message id. If the TOP option is used the prioirty must be greater than or
equal to the priority of all the messages in the queue.
ORA-25213: message with specified RELATIVE_MSGID has been dequeued

Cause: The message specified by the RELATIVE_MSGID field in the sequence
deviation BEFORE option has been dequeued.
Action: n/a
ORA-25214: cannot specify delay or expiration for enqueue to exception queue
Cause: A message was enqueued to the exception queue with either delay or
expiration specified.
Action: Enqueue a message without delay or expiration.
ORA-25215: user_data type and queue type do not match
Cause: A user tries to enqueue an object to a queue that was created for objects of
different type.
Action: Try enqueue again with an object of the right type.
ORA-25216: invalid recipient, either NAME or ADDRESS must be specified
Cause: Both attributes, NAME and ADDRESS, were specified null for one of the
recipients in the recipient list.
Action: Specify a non-null NAME or ADDRESS for the recipient.
ORA-25217: enqueue failed, visibility must be IMMEDIATE for queue string.string
Cause: An attempt was made to enqueue to a non-persistent queue without setting
visibility to IMMEDIATE.
Action: Set visibility to IMMEDIATE.
ORA-25218: enqueue failed, delay must be zero for queue string.string
Cause: An attempt was made to enqueue to a non-persistent queue with delay greater
than zero seconds.
Action: Set delay to zero.
ORA-25219: enqueue failed, sequence deviation not allowed for queue string.string
Cause: An attempt was made to enqueue to a non-persistent queue with sequence
deviation specified.
Action: Do not specify sequence deviation.
ORA-25220: enqueue failed, signature not specified for a non-repudiable queue
Cause: An attempt was made to enqueue to a non-repudiable queue without
specifying the signature
Action: Give the signature
ORA-25221: enqueue failed, signature specified queue not supporting nonrepudiation
Cause: An attempt was made to enqueue to a queue specifying the signature for a
queue not supporting non-repudiation
Action: Remove the signature
ORA-25222: enqueue failed, complete sender info. not provided for a queue
supporting non-repudiation
Cause: An attempt was made to enqueue to a queue without giving the complete
sender information (name) for a queue supporting non-repudiation
Action: Provide the sender information
ORA-24280 to ORA-28709 72-43
ORA-25223: user_data type used is not supported

Cause: An attempt was made to enqueue data into a non persistent queue that is of a
type other than the supported raw or object type.
Action: Enqueue the message again with data of raw or object type.
ORA-25224: sender name must be specified for enqueue into secure queues
Cause: An attempt was made to enqueue into a secure queue without specifying a
sender name.
Action: Enqueue the message with sender name specified.
ORA-25225: invalid value string, DEQUEUE_MODE should be REMOVE or
BROWSE or LOCKED
Cause: An invalid parameter has been specified for DEQUEUE_MODE.
Action: Specify either REMOVE, BROWSE or LOCKED.
ORA-25226: dequeue failed, queue string.string is not enabled for dequeue
Cause: The queue has not been enabled for dequeue.
Action: Enable the queue using START_QUEUE.
ORA-25227: Propagation job string doesn't exist
Cause: The job doesn't exist in AQ$_SCHEDULES or cache.
Action: n/a
ORA-25228: timeout or end-of-fetch during message dequeue from string.string
Cause: User-specified dequeue wait time has passed or the end of the queue has been
reached but no message has been retrieved.
Action: Try dequeue again with the appropriate WAIT_TIME or the
FIRST_MESSAGE option.
ORA-25229: error on transformation of message string string
Cause: There was an error when transforming a message at enqueue, dequeue or
propagation time.
Action: Correct the transformation function.
ORA-25230: invalid value string, WAIT should be non-negative
Cause: A negative value has been specified for WAIT.
Action: specify a non negative value or FOREVER.
ORA-25231: cannot dequeue because CONSUMER_NAME not specified
Cause: A user tried to dequeue from a queue that has been created for multiple
consumers but a CONSUMER_NAME was not been specified in the dequeue options.
Action: Specify the CONSUMER_NAME in the dequeue options.
ORA-25232: duplicate recipients specified for message
Cause: An enqueue was performed with duplicate queue agents in the recipients
parameter.
Action: Remove the duplicate queue agent and retry the call.
ORA-25233: invalid parameter specified for NAVIGATION
Cause: An invalid parameter has been specified for NAVIGATION.
Action: Choose one of FIRST_MESSAGE, NEXT_MESSAGE or

NEXT_TRANSACTION. Use FIRST_MESSAGE for dequeuing the first message that
satisifies the criterion, NEXT_MESSAGE for dequeuing the next message that
satisifies the criterion and NEXT_TRANSACTION for moving to a set of messages
enqueued by another transaction.
ORA-25234: NEXT_TRANSACTION navigation option invalid for queue table
string.string
Cause: The NEXT_TRANSACTION navigation option was used in a dequeue from a
queue in a queue table that was not created for transactional grouping.
Action: Specify either FIRST_MESSAGE or NEXT_MESSAGE as the navigation
option. If you want to dequeue messages using transactional grouping create the
queue in a queue table that has transactional grouping enabled.
ORA-25235: fetched all messages in current transaction from string.string
Cause: The NEXT_TRANSACTION navigation option was used in a dequeue when
there were no more messages that belong to the same transaction.
Action: Use the NEXT_TRANSACTION navigation option to move to the next also
use the FIRST_MESSAGE option to start from the head of the queue again.
ORA-25236: buffer too small for user data
Cause: The variable or buffer used for the out parameter payload is too small for the
user data dequeued.
Action: Increase the size of the buffer or the size of the variable. Maximum size
allowed is 32K.
ORA-25237: navigation option used out of sequence
Cause: The NEXT_MESSAGE or NEXT_TRANSACTION option was specified after
dequeuing all the messages.
Action: Reset the dequeuing position using the FIRST_MESSAGE naviagtion option
and then 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 given
destination (address).
Action: Reduce the number of recipients to 32 or less, and retry the call.
ORA-25239: message ID not supplied when dequeuing from exception queue
string.string
Cause: An attempt was made to dequeue from a release 8.0-compatible exception
queue without including a message ID in the dequeue options.
Action: Check the application to ensure that the queue name has been specified
correctly. If the queue name is correct supply a message ID when dequeuing from a
release 8.0-compatible exception queue. Otherwise, upgrade the queue_table
containing the queue to release 8.1-compatible using the
DBMS_AQADM.MIGRATE_QUEUE_TABLE procedure.
ORA-25240: message ID and dequeue condition/correlation ID specified in
dequeue options
Cause: An attempt was made to dequeue by including both a message ID and a
dequeue condition/correlation ID in the dequeue options. In the dequeue options,
you are permitted to specify either message ID or dequeue condition/correlation ID,
or neither.
ORA-24280 to ORA-28709 72-45
Action: To dequeue a message, specify a message ID or a dequeue condition/

correlation ID in the dequeue options, but do not specify both. If you want to dequeue
in the queue's sort order, then do not specify either the message ID or dequeue
condition/correlation ID in the dequeue options.
ORA-25241: cannot change correlation ID from string to string without
FIRST_MESSAGE option
Cause: An attempt was made to change the correlation ID while using the
NEXT_MESSAGE or NEXT_TRANSACTION option for dequeuing.
Action: To use a correlation ID that is different from the previous dequeue call, reset
the dequeuing position by using the FIRST_MESSAGE navigation option.
ORA-25242: cannot change subscriber name from string to string without
FIRST_MESSAGE option
Cause: An attempt was made to change the subscriber name while using the
NEXT_MESSAGE or NEXT_TRANSACTION option for dequeuing.
Action: To use a subscriber name that is different from the previous dequeue call,
reset the dequeuing position by using the FIRST_MESSAGE navigation option.
ORA-25243: CONSUMER_NAME cannot be specified when dequeuing from
exception queue string.string
Cause: An attempt was made to dequeue from an exception queue by specifying the
CONSUMER_NAME in the dequeue options. CONSUMER_NAME can only be
specified when dequeuing from a normal queue created for multiple consumers.
Action: Specify only the message id in the dequeue options to dequeue a message
from an exception queue.
ORA-25244: dequeue index key not found, QUEUE string, rowid string
Cause: An internal error was encountered. There may be an inconsistency in the
queue table index.
Action: Contact your Oracle customer support representative. You may need to
provide the trace file and information about reproducing the error.
ORA-25245: agent name cannot be specified if address is a single-consumer queue
or an exception queue
Cause: The agent name for the agent in the LISTEN call was specified when the agent
address was a single-consumer queue or an exception queue.
Action: Do not specify the agent name.
ORA-25246: listen failed, the address string is an 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 normal 8.0 style queue or an 8.1 style queue in the agent-list.
ORA-25247: string is not a recipient of specified message
Cause: The consumer name specified in the dequeue options is not a recipient of the
message specified by the message id.
Action: Ensure that the agent specified by the consumer name is a recipient of the
message specified by the message id.
ORA-25248: duplicate agent specified in the agent list
Cause: An agent was specified more than once in the agent list of the LISTEN call.
Action: Remove the duplicate agent specification(s), and retry the call.
ORA-25249: dequeue failed, dequeue not allowed for queue string.string
Cause: An attempt was made to dequeue from a non-persistent queue.
Action: Dequeue from a different queue.
ORA-25250: Cannot specify a remote recipient for the message
Cause: A recipient for the message enqueued to a non-persistent queue had a nonlocal address.
Action: Do not specify the address field or specify the queue which is the target of the
enqueue
ORA-25251: exceeded maximum number of recipients for message
Cause: An attempt was made to issue an ENQUEUE call that exceeded the the
maximum number (1024) of recipients per message.
Action: Reduce the number of recipients to 1024 or less, and retry the call.
ORA-25252: listen failed, the address string is a non-persistent queue
Cause: A non-persistent queue was specified as an address for an agent in the LISTEN
call.
Action: Specify a normal queue as address for the agent, and retry the the LISTEN
call.
ORA-25253: listen failed, queue string.string is not enabled for dequeue
Cause: An attempt was made to specify a queue that is not enabled for dequeue in a
LISTEN call.
Action: Enable the queue for dequeue using START_QUEUE, and retry the LISTEN
call.
ORA-25254: time-out in LISTEN while waiting for a message
Cause: The specified wait time has elapsed and there were no messages for any of the
agents in the agent-list.
Action: Try the LISTEN call with an appropriate time-out.
ORA-25255: incorrect subscription string string
Cause: An incorrect subscription string was specified with OCIRegister.
Action: Specify a subscription string using the [CONSUMER:]SCHEMA.QUEUE
form.
ORA-25256: consumer cannot be specified with a single-consumer queue or an
exception queue
Cause: An attempt was made to specify a consumer in the subscription string when
registering for notification on a single-consumer queue or an exception queue.
Action: Do not specify the consumer in the subscription string.
ORA-25257: consumer must be specified with a multi-consumer queue
Cause: An attempt was made to register on a multi-consumer queue without
specifying a consumer in the subscription string.
Action: Specify a consumer in the subscription string.
ORA-24280 to ORA-28709 72-47
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
subscription string of OCIRegister.
Action: Specify a normal queue or a non-persistent queue.
ORA-25259: cannot specify protocol for agent
Cause: The user specified the protocol attribute for an agent in the agent list.
Action: Do not specify the protocol attribute of the agent object type.
ORA-25260: AQ latch cleanup testing event
Cause: N/A.
Action: event used for AQ statistics latch cleanup testing.
ORA-25261: JOB_QUEUE_PROCESSES must be at least 2 for AQ propagation
Cause: AQ Propagator encountered 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 a multi-consumer queue
Cause: The name for the agent in the LISTEN call was not specified when the agent
address was a multi-consumer queue.
Action: Specify a non-NULL name for the agent.
ORA-25263: no message in queue string.string with message ID string
Cause: An attempt was made to dequeue a message with a specific message ID, but
no such message exists in the queue.
Action: Try dequeue again with a valid message ID.
ORA-25264: cant get signature for this queue
Cause: An attempt was made to dequeue the signature from this queue, which is not
reciever non-repidiable.
Action: Try dequeue again without the get signature option
ORA-25265: specified signature for a queue which does not support reciever nonrepudiation
Cause: An attempt was made to dequeue the message from a queue which does not
support reciever non-repudiation, but the signature was specified for verification
Action: Try dequeue again without the signature
ORA-25266: didnt try to dequeue by message id. with the signature
Cause: The signature was specified for a queue, but the dequeue was not done by
message id.
Action: Try dequeue again by message id.
ORA-25267: didnt specify the signature for a reciever non-repudiable queue
Cause: The signature was not specified for a reciever non-repudiable queue
Action: Try dequeue again along with the signature
ORA-25268: didnt dequeue in browse mode with get signature option
Cause: The dequeue was not performed in browse mode with get signature option
Action: Try dequeue again in browse mode
ORA-25269: cant specify sognature with get signature option

Cause: The signature is not required for the dequeue with get signature option
Action: Try dequeue again without the signature in dequeue options
ORA-25270: sender info does not match with the actual sender of the message
Cause: The sender info. and the message id. do not match
Action: Provide the right sender info. Try dequeue again without the signature in
dequeue options
ORA-25271: queue table not found for the given queue
Cause: The queue table does not exist for the given queue
Action: Provide the right queue name
ORA-25272: Signature does not exist for the given reciever and message id.
Cause: Signature does not exist for the given reciever and message id.
Action: Check the message id. and the reciever's information
ORA-25273: AQ QMN process alternate cleanup event
Cause: N/A.
Action: event used for AQ QMN alternate cleanup mode.
ORA-25274: AQ Buffered Queue event
Cause: N/A.
Action: event used for AQ Buffered Queue mode.
ORA-25276: table specified is not a queue table
Cause: An invalid queue table name is specified.
Action: Check the dictionary views to see if the table is a queue table.
ORA-25277: cannot grant or revoke object privilege on release 8.0 compatible
queues
Cause: An attempt was made to grant or revoke object privilege on release 8.0 style
queues.
Action: Convert the release 8.0 compatible queue table to release 8.1 compatible using
DBMS_AQADM.MIGRATE_QUEUE_TABLE before granting or revoking object
privilege.
ORA-25278: grantee name cannot be NULL
Cause: An attempt was made to specify NULL for the grantee parameter.
Action: Specify a valid grantee parameter.
ORA-25279: dequeue as select not supported before 8.2
Cause: Dequeue as select not supported before 8.2.
Action: Dont use select condition while dequeuing
ORA-25280: complete sender information not provided to non-repudiate sender
Cause: complete sender information not provided to non-repudiate sender
Action: Provide the complete sender information
ORA-25281: complete reciever information not provided to non-repudiate reciever
Cause: complete reciever information not provided to non-repudiate reciever
ORA-24280 to ORA-28709 72-49
Action: Provide the complete reciever information

ORA-25282: message id. not provided for non-repudiation
Cause: message id. was not provided
Action: Provide the message id.
ORA-25283: either agent's name or address needed for non-repudiation
Cause: neither agent's name nor address provided for non-repudiation"
Action: Provide the agent info.
ORA-25284: Invalid value string for string
ORA-25285: Invalid value string for array_mode
Cause: An Invalid value or NULL was specified for the array_mode.
ORA-25286: Invalid number of elements in the message properties array
Cause: Number of elements in the message properties array do not match the number
of elements in the payload array.
Action: Create a message property array with one element (that applies for all the
elements in the payload array) or create a message property array with the same
number of elements as there are in the payload array.
ORA-25287: Invalid value string, string should be non-negative
Action: Specify a non negative integer.
ORA-25288: AQ HTTP propagation encountered error, status-code number, string
Cause: AQ propagation's HTTP request to the propagation servlet at the specified
address encountered an error
Action: Specify a valid address in the connect string of the propagation destination
dblink, the dblink user has the correct permissions, check if the AQ propagation
servlet was properly installed.
ORA-25289: Buffer Already Exists
Cause: Buffer already exists for the specified queue.
Action: None
ORA-25290: Cannot complete operation on queue string with existing messages
Cause: Queue already has messages. Cannot complete operation
Action: Truncate the queue before adding/dropping a buffer
ORA-25291: Buffer does not exist for the specified queue
Cause: Buffer does not exist for the specified queue
Action: Operation on the buffer cannot be performed. create the buffer
ORA-25292: Buffer operations are not supported on the queue
Cause: Buffer operations are not supported on the specified queue type
Action: Buffered operations are only supported on to 8.1 style queues, which do not
have transaction grouping.
ORA-25293: Lob attributes must be null for buffered operations
Cause: Enqueue of a buffered message with a non-null lob attribute was attempted
Action: Set the lob attributes to null before enqueuing the buffered message
ORA-25294: Cannot propagate user buffered messages to a database with version
lower than 10.2
Cause: Propagation of user buffered messages was attempted to a database with
version lower than 10.2.
Action: Do not propagate buffered messages to the database.
ORA-25295: Subscriber is not allowed to dequeue buffered messages
Cause: Subscriber is only allowed to dequeue persistent messages
Action: Drop the subscriber and re-create it, or dequeue only persistent messages for
the subscriber
ORA-25296: Queue Table string has a buffered queue string
Cause: Buffered message was enqueued by specifying delay or sequence deviation.
Action: Do not specify delay of sequence deviation when enqueuing buffered
messages.
ORA-25298: Only immediate visibility mode supported for buffered message
enqueue or dequeue
Cause: A visibility of dbms_aq.ON_COMMIT was supplied with the buffered
message enqueue or dequeue
Action: Supply a visibility of dbms_aq.IMMEDIATE
ORA-25299: Invalid message delivery_mode
Cause: Invalid value was specified for delivery mode
Action: Specify dbms_aq.BUFFERED or dbms_aq.PERSISTENT during Enqueue or
dbms_aq.BUFFERED, dbms_aq.PERSISTENT or
dbms_aq.PERSISTENT_OR_BUFFERED during Dequeue and Listen.
ORA-25300: Cannot drop buffer for queue with buffered subscribers
Cause: Cannot drop buffer for queue with buffered subscribers
Action: Either drop buffered subscribers or forcibly drop the buffer
ORA-25301: Cannot enqueue or dequeue user buffered messages to a database with
version lower than 10.2
Cause: Enqueue or dequeue of user buffered messages was attempted to queues in a
database with version lower than 10.2.
Action: Do not attempt to enqueue or dequeue user buffered messages.
ORA-25302: Operation not possible for non-buffered queue string
Cause: Last enqd/ackd message is only supported for buffered queues
Action: The operation is not supported.
ORA-25303: Buffered operation allowed only on the owner instance
Cause: Operation was not performed on the owner instance.
Action: Perform operation on the owner instance.
ORA-24280 to ORA-28709 72-51
ORA-25304: Cannot use priority order queues for capture LCRs

Cause: Capture LCRs can only use commit time or enqueue time ordered queues.
Action: Use the appropriate type of queue for captured LCRs.
ORA-25305: enqueue failed, expiration must be zero for queue string.string
Cause: An attempt was made to enqueue to a buffered queue with expiration greater
than zero seconds.
Action: Set expiration to zero.
ORA-25306: Cannot connect to buffered queue's owner instance
Cause: cannot connect to the owner instance of the buffered queue
Action: set listener information in REMOTE_LISTENERS or LOCAL_LISTENERS
initialization parameter.
ORA-25307: Enqueue rate too high, flow control enabled
Cause: Subscribers could not keep pace with the enqueue rate.
Action: Try enqueue after waiting for some time.
ORA-25310: Subscriber is Notification only; dequeue not supported
Cause: Notification only subscribers are not allowed to dequeue.
Action: Recreate subscriber if necessary.
ORA-25311: string not supported for non-persistent queue
Cause: Specified QOS is not supported for non-persistent queues.
Action: Specify the right QOS.
ORA-25312: Cannot specify nonzero sender protocol
Cause: Sender protocol was specified during an enqueue operation.
Action: Specify the enqueue sender protocol as null or zero.
ORA-25313: a queue may not subscribe to itself for propagation
Cause: The specified subscriber had a NULL name and an address equal to the queue
name.
Action: Provide a valid subscriber and retry the operation.
ORA-25314: a commit-time queue table cannot be migrated to 8.0
Cause: An attempt was made to migrate a commit-time queue table to an
unsupported compatibility level.
Action: Provide an appropriate compatibility level, and retry the operation.
ORA-25315: unsupported configuration for propagation of buffered messages
Cause: An attempt was made to propagate buffered messages with the database link
pointing to an instance in the destination database which is not the owner instance of
the destination queue.
Action: Use queue to queue propagation for buffered messages.
ORA-25316: Late in the current transaction to begin an Enqueue/Dequeue operation
Cause: Check if the Enqueue/Dequeue operation is performed via triggers on
Materialized Views which isn't supported.
Action: Triggers on materialized views aren't supported. Workarounds are ondemand materialized views or execution of trigger code within an autonomous txn.
ORA-25317: Propagation stopped because of instance shutdown

Cause: A propagation job has stopped because the instance is shutting down.
Action: No user action is required.
ORA-25318: Propagation stopped because of instance affinity change
Cause: A propagation job has stopped because its instance affinity has changed.
Action: No user action is required. The job will restart on the appropriate instance.
ORA-25319: Queue table repartitioning aborted
Cause: During instance restart in an Oracle RAC environment, queue table
repartitioning aborted due to errors.
Action: Look at the incident generated for this error and report the problem to Oracle
Support Services.
ORA-25320: Failed to create, alter, or remove Subscriber
Cause: There is a pending enqueue or dequeue operation on this queue from the same
session.
Action: Either COMMIT or ROLLBACK pending enqueue or dequeue operation
before attempting to create, alter, or remove the subscriber.
ORA-25321: enqueue failed, user property specified but queue string.string is not
an 8.1 style queue
Cause: user properties can only be specified when enqueueing into 8.1 style queues.
Action: Specify an 8.1 style queue or pass user property as NULL.
ORA-25322: message priority is out of range
Cause: The message priority range of 0 to 9 was exceeded.
Action: Set the message priority in the range of 0 to 9.
ORA-25326: Array string operation failed for message at index string
Cause: Array operation fails for the message at specified index. Look at the remainder
of the error stack to see what the problem was.
Action: Fix cause of error and retry array operation.
ORA-25327: Array size is invalid
Cause: Array size must be a positive, non-zero integer.
Action: Use corrected array size and retry array operation.
ORA-25328: string argument size string is smaller than array size
Cause: The size of the argument is smaller than the given array size.
Action: Lower array size or use a larger sized input argument.
ORA-25329: AQ array operations not allowed on 8.0 queues
Cause: An array enqueue/dequeue was attempted on an 8.0 queue.
Action: Use single enqueue/dequeue with this queue.
ORA-25330: PL/SQL associative arrays may not be used with AQ array operations
Cause: A PL/SQL associative array was provided for the payload parameter in an
enqueue/dequeue array operation.
Action: Use VARRAY or NESTED TABLE types with AQ array operations.
ORA-24280 to ORA-28709 72-53
ORA-25331: cannot downgrade because there are commit-time queue tables

Cause: An attempt was made to downgrade a database that has commit-time queue
tables.
Action: Drop all commit-time queue tables before attempting the downgrade.
ORA-25332: Invalid release value string for queue table compatible parameter
Cause: The release level given for the queue table compatible parameter is invalid
Action: Specify a valid release value for the queue table compatible parameter
ORA-25333: Buffered Queue to Queue propagation did not connect to the correct
instance
Cause: Queue to Queue propagation for buffered messages didn't connect to the
correct instance, most likely because service was not started for the destination queue.
Action: No user action is required. Propagation will start the service for the
destination queue and retry.
ORA-25334: Buffered propagation must restart as the destination queue was
recreated/moved
Cause: Buffered propagation destination queue was recreated or its ownership was
moved to another instance during propagation.
Action: No user action is required. Propagation will reinitialize its metadata and retry.
ORA-25335: AQ array operations not allowed for buffered messages
Cause: An array enqueue/dequeue was attempted for buffered messages
Action: Use single enqueue/dequeue for buffered messages or an array size of one.
ORA-25336: Cannot contact instance string during Streams AQ operation
Cause: The specified instance was not responding to AQ requests.
Action: Set parameter aq_tm_processes to a non-zero value. If the problem persists,
ORA-25337: Cannot propagate in queue-to-queue mode to a database with version
lower than 10.2
Cause: Remote subscriber with queue_to_queue mode set to TRUE was added. The
remote subscriber is on a database version lower than 10.2. Propagation was
scheduled to a destination database with version lower than 10.2.
Action: Remove the remote subscriber with queue_to_queue mode and add the
subscriber back with queue_to_queue set to FALSE. Unschedule the queue-to-queue
propagation and schedule propagation in queue-to-dblink mode.
ORA-25338: operation 'string' is not allowed for sync_capture 'string'
Cause: An attempt was made to execute the specified operation for a sync_capture
process.
Action: Remove the offending call.
ORA-25339: STREAMS 'string' must be sync_capture
Cause: The specified capture STREAMS did not exist or was not a sync_capture
process.
Action: Remove the offending call.
ORA-25340: must use commit-time queue for sync_capture

Cause: An attempt was made to create a sync_capture without using a commit-time
queue.
Action: Rerun statement with a commit-time queue.
ORA-25341: sync_capture does not support "string"."string" because of the
following reason:
Cause: sync_capture encountered a table with an unsupported property. The most
common reason is an unsupported column data type.
Action: Revise the Capture rules to skip over the table in question. One option is to
remove the rule that captures changes from the unsupported table. Check
DBA_STREAMS_TABLE_RULES to determine the rule on the table specified in the
error. Also query the DBA_STREAMS_UNSUPPORTED view to determine which
tables are not supported by STREAMS and for what reason. For potential
workarounds to certain unsupported properties, see Metalink.
ORA-25342: cannot downgrade because there are apply processes for user buffered
messages
Cause: An attempt was made to downgrade a database that has apply process for
user-buffered messages.
Action: Drop all the apply processes for user-buffered messages before attempting the
downgrade.
ORA-25343: Streams error queue cannot be exported
Cause: An attempt was made to export a database that has apply errors.
Action: Delete or reexecute errors before attempting the export.
ORA-25344: statement has bind variables
Cause: Current API could not handle a statement with bind variables.
Action: Use alternative API which handles bind variables.
ORA-25345: requested AQ minimum Oracle Streams Pool size string greater than
Oracle Streams Pool size string
Cause: The minimum value requested for the Oracle Streams Advanced Queuing
(AQ) pool size was greater than the Oracle Streams pool size.
Action: Set the minimum value for the Oracle Streams AQ pool size to less than or
equal to the Oracle Streams pool size.
ORA-25346: requested AQ maximum Oracle Streams Pool size string less than AQ
minimum Oracle Streams Pool size string
Cause: The maximum value requested for the Oracle Streams Advanced Queuing
(AQ) pool size was less than the minimum value of the Oracle Streams (AQ) pool
size.
Action: Set the maximum value for the Oracle Streams AQ pool size to greater than or
equal to the minimum value of the Oracle Streams AQ pool size.
ORA-25350: maximum number of concurrent transaction branches exceeded
Cause: the limit on the number of concurrent transaction branches has been reached
Action: Increase the INIT.ORA parameter 'transactions' and restart the system.
ORA-24280 to ORA-28709 72-55
ORA-25351: transaction is currently in use

Cause: The transaction is currently used by a different 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 detach when there is no current transaction.
ORA-25353: branch marked for deletion
Cause: The branch specified cannot be killed immediately because another session is
using the branch, but it has been marked for kill. This means it will be deleted as soon
as possible after the current uninterruptable operation is completed.
Action: No action is required for the branch to be deleted.
ORA-25401: can not continue fetches
Cause: A failure occured since the last fetch on this statement. Failover was unable to
bring the statement to its original state to allow continued fetches.
Action: Reexecute the statement and start fetching from the beginning
ORA-25402: transaction must roll back
Cause: A failure occured while a transaction was active on this connection.
Action: The client must roll back.
ORA-25403: could not reconnect
Cause: The connection to the database has been lost, and attempts to reconnect have
failed.
Action: Manually reconnect.
ORA-25405: transaction status unknown
Cause: A failure occured while a transaction was attempting to commit. Failover
could not automatically determine instance status.
Action: The user must determine the transaction's status manually.
ORA-25406: could not generate a connect address
Cause: Failover was unable to generate an address for a backup instance.
Action: Contact Oracle customer support.
ORA-25408: can not safely replay call
Cause: The connection was lost while doing this call. It may not be safe to replay it
after failover.
Action: Check to see if the results of the call have taken place, and then replay it if
desired.
ORA-25409: failover happened during the network operation,cannot continue
Cause: The connection was lost when fetching a LOB column.
Action: Failover happened when fetching LOB data directly or indirectly. Please
replay the top level statement.
ORA-25411: transaction replay was not successful
Cause: Replay was not able to restore the transaction state to match the pre-failover
state.
Action: Manually determine if it is safe to resubmit the transaction.

ORA-25412: transaction replay disabled by call to string
Cause: The application called an Oracle Call Interface (OCI) function that was not
supported with transactional failover.
Action: Set OCI_ATTR_TRANSACTIONAL_TAF to FALSE to turn off transactional
ORA-25413: transaction replay disabled by user request
Cause: The application explicitly disabled transaction replay by setting attribute
OCI_ATTR_TRANSACTIONAL_TAF=FALSE.
Action: This message is informational only.
ORA-25414: Uncommitted transaction detected after TAF callback.
Cause: The Transparent Application Failover (TAF) callback started a transaction and
did not commit or rollback prior to exiting.
Action: End the transaction with a COMMIT or a ROLLBACK prior to exiting the
TAF callback.
ORA-25415: OCI Transaction TAF replay initiation timeout exceeded.
Cause: Oracle Call Interface (OCI) Transaction TAF replay was attempted after
REPLAY_INITIATION_TIMEOUT expired. The value for
REPLAY_INITIATION_TIMEOUT is configured for the service to which the
application is connected.
Action: Manually recover the pending transaction.
ORA-25416: Retry current call
Cause: Failover sucessfully recovered an in-flight transaction
Action: Re-execute the current call
ORA-25425: connection lost during rollback
Cause: The connection was lost while issuing a rollback and the application failed
over.
Action: The connection was lost and failover happened during rollback. If the
transaction is not externally coordinated, then Oracle implicitly rolled back, so no
action is required. Otherwise examine pending_trans$ to determine if "rollback force"
is required.
ORA-25426: remote instance does not support shared dblinks
Cause: A shared dblink 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 dblink if you need to connect to this instance.
ORA-25427: cannot downgrade database links after database link data dictionary
has been upgraded
Cause: An attempt was made to downgrade after the upgrade of the database link
data dictionary.
Action: Drop the database links before attempting the downgrade.
ORA-25428: authentication failure while connecting through database link
Cause: An attempt to connect using the database link failed.
Action: Ensure connection details for the database link are correct.
ORA-24280 to ORA-28709 72-57
ORA-25429: Break request cannot be propagated over shared database link.

Cause: No call in progress over shared database link.
Action: No action required. This is an informational message only.
ORA-25430: connected user database links are not supported in proxy session
Cause: A connected user database link is being used to connect to a remote database
from a proxy user session.
Action: No action required. This was an informational message only.
ORA-25436: invalid table alias: string
Cause: An attempt to evaluate was made, which failed because one of the table values
specified had an invalid alias.
Action: Check the valid table aliases in the evaluation context, and try again with a
valid alias.
ORA-25437: duplicate table value for table alias: string
Cause: An attempt to evaluate was made, which failed because some of the table
values specified had the same table alias.
Action: Check the table values specified, and try again with only one value per table.
ORA-25438: invalid variable name: string
Cause: An attempt to evaluate was made, which failed because one of the variable
values specified had an invalid name.
Action: Check the valid variable names in the evaluation context, and try again with a
valid name.
ORA-25439: duplicate variable value for variable: string
Cause: An attempt to evaluate was made, which failed because some of the variable
values specified had the same variable name.
Action: Check the variable names specified, and try again with only one value per
variable.
ORA-25440: invalid table alias: string
Cause: An attempt to evaluate was made, which failed because one of the column
values specified had an invalid table alias.
Action: Check the valid table aliases in the evaluation context, and try again with a
valid name.
ORA-25441: duplicate column value for table alias: string
values supplied a value for a table alias, which already had a table value supplied.
Action: Check the table and column values specified, and try again with either a table
value or column values for each table alias.
ORA-25442: too many column values for table alias: string
Cause: An attempt to evaluate was made, which failed because too many column
values were supplied for the specified table alias.
Action: Check the column values specified, and try again with the right number of
column values.
ORA-25443: duplicate column value for table alias: string, column number: string
Cause: An attempt to evaluate was made, which failed because duplicate column
values were supplied for the specified table alias and column number.
Action: Check the column values specified, and try again with only one column value
for each table alias, and column number.
ORA-25444: invalid ROWID: string for table alias: string
Cause: An attempt to evaluate was made, which failed because an invalid ROWID
was supplied for the specified table alias.
for each table alias, and column number.
ORA-25445: invalid column number: string for table alias: string
Cause: An attempt to evaluate was made, which failed because an invalid column
number was supplied for the specified table alias as a part of a column value.
Action: Check the column values specified, and try again with a valid column
number.
ORA-25446: duplicate column value for table alias: string, column: string
Cause: An attempt to evaluate was made, which failed because duplicate column
values were supplied for the specified table alias and column name.
for each table alias, and column name.
ORA-25447: encountered errors during evaluation of rule string.string
Cause: An attempt to evaluate was made, which failed during the evaluation of the
specified rule.
Action: Check the rule and the values passed to evaluate, and try again with valid
values.
ORA-25448: The string string.string has errors.
Cause: An attempt to load the specified rule or expression failed due to errors in the
rule or expression.
Action: Check the rule or expression and retry the operation.
ORA-25449: invalid variable name: string
Cause: An attempt to evaluate was made, which failed because one of the attribute
values specified had an invalid variable name.
Action: Check the valid variable names in the evaluation context, and try again with a
valid name.
ORA-25450: error string during evaluation of rule set string.string
Cause: The specified error occurred during evaluation of the rule set.
Action: Check the error and take appropriate action.
ORA-25451: too many attribute values for variable: string
Cause: An attempt to evaluate was made, which failed because too many attribute
values were supplied for the specified variable.
Action: Check the attribute values specified, and try again with the right number of
attribute values.
ORA-24280 to ORA-28709 72-59
ORA-25452: duplicate attribute value for variable: string, attribute: string

Cause: An attempt to evaluate was made, which failed because duplicate attribute
values were supplied for the specified variable and attribute name.
Action: Check the attribute values specified, and try again with only one attribute
value for each variable, and attribute name.
ORA-25453: invalid iterator: string
Cause: An attempt to get rule hits or to close an iterator was made, which failed
because an invalid iterator was passed in.
Action: Check the iterator, and try again with a valid iterator.
ORA-25454: error during evaluation of rule set: string.string for iterator: string
Cause: An attempt to get rule hits for an iterator was made, which failed because of
an error in evaluation of the specified rule set.
Action: Check the validity of the rule set and try again.
ORA-25455: evaluation error for rule set: string.string, evaluation context:
string.string
Cause: An attempt to evaluate the specified rule set using the evaluation context
specified failed due to some errors.
Action: Check additional errors signalled to determine the problem.
ORA-25456: rule set was modified or evaluation terminated for iterator: string
Cause: An attempt to get rule hits was made, which failed because the underlying
rule set was modified after the iterator was returned.
Action: Try again after re-evaluating the rule set.
ORA-25457: evaluation function string returns failure
Cause: The specified evaluation function returned a failure during evaluation,
causing evaluation to terminate.
Action: Check arguments to evaluate and retry.
ORA-25458: Value not supplied for string string
Cause: Variable or table column values were not supplied for evaluation.
Action: Supply all the required variable and column data points for Independent
Expression Evaluation.
ORA-25459: Data conversion for string string failed
Cause: The attempt to convert data to the data type of the variable or column failed.
Action: Supply the correct data for variable or column.
ORA-25461: rule set not specified
Cause: An attempt to evaluate was made, which failed because the ruleset name
specified was null.
Action: Check the rule set name, and try again with a valid name.
ORA-25462: evaluation context not specified
Cause: An attempt to evaluate was made, which failed because the evaluation context
specified was null.
Action: Check the evaluation context name, and try again with a valid name.
ORA-25463: table alias not specified

Cause: An attempt to evaluate was made, which failed because one of the table values
specified had a NULL alias name.
Action: Check the list of table values, and try again with a valid alias name.
ORA-25464: ROWID not specified for table alias: string
Cause: An attempt to evaluate was made, which failed because the table value for the
specified table alias had a NULL ROWID.
Action: Check the list of table values, and try again with a valid ROWID.
ORA-25465: variable name not specified
Cause: An attempt to evaluate was made, which failed because one of the variable
values specified had a NULL variable name.
Action: Check the list of variable values, and try again with a valid variable name.
ORA-25466: data not specified for variable name: string
Cause: An attempt to evaluate was made, which failed because the variable value for
the specified variable name had NULL data.
Action: Check the list of variable values, and try again with valid data.
ORA-25467: table alias not specified
values specified had a NULL alias name.
Action: Check the list of column values, and try again with a valid alias name.
ORA-25468: column name not specified for alias: string
values for the specified alias name had a NULL column name.
Action: Check the list of column values, and try again with a valid column name.
ORA-25469: data not specified for alias: string column name: string
Cause: An attempt to evaluate was made, which failed because the column value for
the specified alias and column name had NULL data.
Action: Check the list of column values, and try again with valid data.
ORA-25470: duplicate attribute value for variable: string
values supplied a value for a variable, which already had a variable value supplied.
Action: Check the variable and attribute values specified, and try again with either a
variable value or attribute values for each variable.
ORA-25471: attribute name not specified for variable: string
values for the specified variable had a NULL attribute name.
Action: Check the list of attribute values, and try again with a valid attribute name.
ORA-25472: maximum open iterators exceeded
Cause: The open rule hit iterators in the session exceeded 2 * OPEN_CURSORS.
Action: Close some rule hit iterators.
ORA-24280 to ORA-28709 72-61
ORA-25473: cannot store string in rule action context

Cause: The user attempted to put unsupported data types, such as LOBs and evolved
ADTs, into the rule action context.
Action: Use only supported data types in rule action context.
ORA-25476: use pre-5523578 behaviour when looking up enabled roles
Cause: N/A
Action: Derive the enabled roles under the rules engine using the old method that
existed before the fix to bug 5523578.
ORA-25500: database is not open
Cause: Database must be open to perform ALTER SYSTEM QUIESCE RESTRICTED
command.
Action: Open the database and retry this command.
ORA-25501: ALTER SYSTEM QUIESCE RESTRICTED command failed
Cause: Database resource manager failed to change plan.
Action: Look at the alert logs to see detailed description of the error.
ORA-25502: concurrent ALTER SYSTEM QUIESCE/UNQUIESCE command is
running
Cause: There is a concurrent ALTER SYSTEM QUIESCE RESTRICTED or ALTER
SYSTEM UNQUIESCE command running in the system.
Action: Contact the database administrator who is responsible for the concurrent
command.
ORA-25503: cannot open database because the database is being quiesced
Cause: Database cannot be opened because the system is being or has been quiesced.
Action: Open the database after the system has been quiesced.
ORA-25504: the system is already in quiesced state
Cause: Cannot quiesce the system because the system is already quiesced.
Action: n/a
ORA-25505: the system is not in quiesced state
Cause: Cannot unquiesce the system because the system is not in quiesced state.
Action: n/a
ORA-25506: resource manager has not been continuously on in some instances
Cause: Cannot quiesce the system because resource manager has not been
continuously on since startup in this or some other instances.
Action: n/a
ORA-25507: resource manager has not been continuously on
Cause: Cannot quiesce the system because resource manager has not been
continuously on since startup.
Action: n/a
ORA-25508: database is not mounted
Cause: Database must be mounted to perform ALTER SYSTEM UNQUIESCE
command.
Action: Mount the database and retry this command.

ORA-25509: operation on "string"."string".string not allowed
Cause: A column has been added to a replicated table, but replication support
processing has not completed.
Action: Wait until replication support processing has completed before updating the
column
ORA-25510: quiesce not supported for the root container
Cause: Could not quiesce the root container.
Action: This operation is not supported for the root container.
ORA-25511: quiesce not supported for pluggable databases
Cause: Could not quiesce the pluggable database.
Action: This operation is not supported for pluggable databases.
ORA-25526: bad format of _DB_MTTR_SIM_TARGET: string
Cause: One value in _DB_MTTR_SIM_TARGET is not a valid MTTR.
Action: Alter the value of _DB_MTTR_SIM_TARGET.
ORA-25527: bad format of _DB_MTTR_SIM_TARGET
Cause: One value in _DB_MTTR_SIM_TARGET is empty.
Action: Set the value of _DB_MTTR_SIM_TARGET properly.
ORA-25528: too many candidate MTTRs are specified in
_DB_MTTR_SIM_TARGET
Cause: Too many candidate MTTRs are specified in _DB_MTTR_SIM_TARGET.
Action: Alter the value of _DB_MTTR_SIM_TARGET.
ORA-25530: FAST_START_MTTR_TARGET is not specified
Cause: An attempt to start MTTR advisory was made, which failed because
FAST_START_MTTR_TARGET was not specified.
Action: Set FAST_START_MTTR_TARGET.
ORA-25531: MTTR specified is too small: string
Cause: The current FAST_START_MTTR_TARGET setting or a candidate MTTR
setting is too small for MTTR advisory.
Action: Set a larger FAST_START_MTTR_TARGET or candidate MTTR.
ORA-25532: MTTR specified is too large: string
Cause: The current FAST_START_MTTR_TARGET setting or a candidate MTTR
setting is too large for MTTR advisory.
Action: Set a smaller FAST_START_MTTR_TARGET or candidate MTTR.
ORA-25533: FAST_START_IO_TARGET or LOG_CHECKPOINT_INTERVAL is
specified
Cause: An attempt to start MTTR advisory was made, which failed because either
FAST_START_IO_TARGET or LOG_CHECKPOINT_INTERVAL was specified.
Action: Set FAST_START_IO_TARGET and LOG_CHECKPOINT_INTERVAL to 0.
ORA-24280 to ORA-28709 72-63
ORA-25950: missing where clause in join index specification\n

Cause: An attempt to create a join index was made, which failed because no valid
where clause was found.
Action: Ensure that a where clause with valid join conditions is specified in the create
index statement.
ORA-25951: join index where clause cannot contain OR condition\n
Cause: An attempt to create a join index was made, which failed because there was an
OR branch in the where clause.
Action: Reformulate the where clause without using ORs.
ORA-25952: join index must only contain inner equi-joins\n
Cause: An attempt to create a join index was made, which failed because it included a
predicate which wasn't an equi-inner join.
Action: Remove the inappropriate predicate.
ORA-25953: join index cannot be a functional index\n
Cause: An attempt to create a join index was made, which failed because a functional
index was requested or necessary (such as is the case for indexing columns using
timezone).
Action: Remove any functional indexing columns.
ORA-25954: missing primary key or unique constraint on dimension\n
Cause: An attempt to create a join index was made, which failed because one or more
dimensions did not have an appropriate constraint matching the join conditions.
Action: Ensure that the where clause is correct (contains all of the constraint columns)
and that an enforced constraint is on each dimension table.
ORA-25955: all tables must be joined in the where clause\n
Cause: An attempt to create a join index was made, which failed because one of the
tables in the from clause did not appear in the where clause.
Action: Ensure that the where clause contains all from clause tables.
ORA-25956: join index cannot be created on tables owned by SYS\n
tables was owned by SYS.
Action: Ensure that no join index related table is owned by SYS.
ORA-25957: join index where clause cannot contain cycles\n
Cause: An attempt to create a join index was made, which failed because the where
clause contains a cycle.
Action: Ensure that the where clause is in the form of a star or snowflake schema.
ORA-25958: join index where clause predicate may only contain column references
\n
Cause: An attempt to create a join index was made, which failed because a predicate
in the where clause contained something other than a simple column.
Action: Ensure that the where clause only contains columns.
ORA-25959: join index must be of the bitmap type\n

Cause: An attempt to create a join index was made, which failed because no bitmap
keyword was used.
Action: Make the index a bitmap index.
ORA-25960: join index cannot be based on a temporary table\n
tables was temporary.
Action: Ensure no underlying tables are temporary.
ORA-25961: join index prevents dml cascade constraint operation\n
Cause: An attempt to execute dml resulted in the need to perform dml on another
table because of a cascade constraint. The join index only allows one of its underlying
tables to me modified at a time.
Action: Drop the join index or remove the constraint.
ORA-25962: join index prevents multitable insert or merge\n
Cause: An attempt to execute an merge or multitable insert on a table that was used to
create a bitmap join index was made. Merge and multitable inserts are not supported
on tables that were used to create a bitmap join index.
Action: Drop the join index.
ORA-25963: join index must be created on tables\n
Cause: An attempt to create a join index was made, which failed because the from
clause contains non table object.
Action: Ensure that the from clause only contains tables.
ORA-25964: column type incompatible with join column type\n
Cause: The datatype of the join column is incompatible with the datatype of the
joined column.
Action: Select a compatible datatype for the join column.
ORA-25965: fact table must be included in the from clause\n
Cause: An attempt to create a join index was made, which failed because the from
clause does not contain the fact table.
Action: Ensure that the from clause contains the fact table.
ORA-25966: join index cannot be based on an index organized table\n
tables was an index organized table.
Action: Ensure no underlying tables are index organized.
ORA-26000: partition load specified but table string is not partitioned\n
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: Index string specified in SORTED INDEXES does not exist on table
string\n
Cause: A nonexistent index was specified in the SORTED INDEXES clause.
ORA-24280 to ORA-28709 72-65
Action: Do not specify as a SORTED INDEX.

ORA-26002: Table string has index defined upon it.\n
Cause: Parallel load was specified into a table which has index defined upon it.
Action: Drop index(es) defined upon table, or don't use parallel load, or use
SKIP_INDEX_MAINTENANCE option.
ORA-26003: parallel load not supported for index-organized table string.\n
Cause: Parallel load is not supported for index-organized tables.
Action: load the index-organized table without the PARALLEL option.
ORA-26004: Tables loaded through the direct path may not be clustered\n
Cause: User attempted to load a clustered table via the direct path.
Action: Use the conventional path.
ORA-26005: Invalid handle for direct path load\n
Cause: In direct path load, the handle passed in does not match the type listed.
Action: Verify the handle and type are correct.
ORA-26006: Incorrect bind variable in column string's sql expression - string\n
Cause: In direct path load, the bind variables listed in the sql expression do not match
the input argument column names.
Action: Verify all the input arguments are listed in the expression as bind variables,
and all the bind variables are listed as input arguments to the expression. Or verify
that there were no errors in executing the OCI statements when getting the bind
variable list.
ORA-26007: invalid value for SETID or OID column\n
Cause: The value passed in a Direct Path API stream for a column containing a SETID
or OID has an invalid value. SETIDs and Object IDs must be either 16 bytes of RAW
data or 32 bytes of hexidecimal characters.
Action: Regenerate the Direct Path API stream with a valid value for the SETID
column.
ORA-26008: Invalid syntax or bind variable in SQL string for column string.
\nstring\n
Cause: See following error message for more information. A SQL string cannot have
quoted strings improperly terminated. A bind variable in a SQL string cannot have a
length of 0, cannot exceed maximum length of 30 characters, and cannot be missing a
double quote.
Action: Fix the SQL string. See following error for more information.
ORA-26009: stream verification error: string\n
Cause: An error has occurred in a Data Pump stream verification operation.
ORA-26010: Column string in table string is NOT NULL and is not being loaded\n
Cause: A column which is NOT NULL in the database is not being loaded and will
cause every row to be rejected.
Action: Load the column by specifying the NOT NULL column in the INTO TABLE
clause in the SQL*Loader control file.
ORA-26011: Cannot load type string into column string in table string\n
Cause: A column can only store data of type declared for that column. And a
substitutable column can only store data of valid subtypes of the supertype declared
for that column.
Action: Check that the type or subtype specified is valid for that column.
ORA-26012: header in file string has an incompatible version number\n
Cause: A dump file was specified for a load operation whose version number is
incompatible with the dump file version currently produced by the Oracle server on
the system. Usually this message indicates that the dump file was produced by a
newer version of the Oracle server.
Action: Load this dump file using the same version of the Oracle server that created
the file.
ORA-26013: List allocated may not be big enough\n
Cause: There seems to be a discrepancy between the size for a list or buffer allocated
by direct path api and the size needed.
ORA-26014: unexpected error on string string while retrieving string\nstring
Cause: The SQL error was returned from an OCIStmtExecute call.
Action: Correct the SQL error that was returned.
ORA-26015: Array column string in table string is not supported by direct path\n
Cause: User attempted to load an array column via the direct path.
Action: Use the conventional path.
ORA-26016: Virtual column string in table string.string cannot be loaded by direct
path\n
Cause: You attempted to load an virtual column using the direct path.
Action: Virtual columns cannot be loaded using the direct path.
ORA-26017: global indexes not allowed for direct path load of table partition string
Cause: Global indexes are defined on a table when direct path loading a single
partition of the table.
Action: n/a
ORA-26018: Column string in table string does not exist\n
Cause: 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 wrong.
ORA-26019: Column string in table string of type string not supported by direct
path\n
Cause: The Specified column of SQL column type %s is not supported by the direct
path loader.
Action: If the column is NULLable, remove it from the control file description. Then it
will be loaded as a NULL.
ORA-26020: index string.string loaded successfully with string keys
Cause: Non-partitioned index information put to loader log file.
ORA-24280 to ORA-28709 72-67

ORA-26021: index string.string partition string loaded successfully with string keys
Cause: Partitioned index information put to loader log file.
ORA-26022: index string.string was made unusable due to:
Cause: A Non-partitioned index was made index unusable due to the error displayed
below this error.
Action: Depending on the error, either rebuild the index, or drop and re-create it.
ORA-26023: index string.string partition string was made unusable due to:
Cause: A partition of a partitioned index was made index unusable due to error
displayed below this error.
Action: Depending on the error, either rebuild the index partition, or drop and recreate the entire index.
ORA-26024: SKIP_UNUSABLE_INDEXES requested and index segment was
initially unusable
Cause: User requested SKIP_UNUSABLE_INDEXES option, and the index segment *
was in unusable state prior to the beginning of the load.
Action: Informational only. User will need to either rebuild the index * or index
partition, or re-create the index.
ORA-26025: SKIP_INDEX_MAINTENANCE option requested
Cause: User requested that index maintenance be skipped on a direct path load.
Action: The listed index was put into Index Unusable state due to the user requesting
that index maintenance be skipped. Either rebuild the index or index partitions, or
drop and re-create the index.
ORA-26026: unique index string.string initially in unusable state
Cause: A unique index is in IU state (a unique index cannot have * index maintenance
skipped via SKIP_UNUSABLE_INDEXES).
Action: Either 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 partition of a unique index is in IU state (a unique index * cannot have index
maintenance skipped via SKIP_UNUSABLE_INDEXES).
Action: Either 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 IU state prior to the beginning of a direct * path load, it cannot
be maintained by the loader.
Action: Either rebuild the index, re-create the index, or use either *
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 IU state prior to the beginning * of a direct path
load, it cannot be maintained by the loader.
Action: Either rebuild index partition, re-create the index, or use either *
SKIP_UNUSABLE_INDEXES or SKIP_INDEX_MAINTENANCE (Sql*Loader only).
ORA-26030: index string.string had string partitions made unusable due to:
Cause: A logical index error occurred on a partitioned index which * affected one or
more index partitions, which are listed below * this message.
Action: The affected index partitions will have to be re-built, or, the * entire index
dropped and re-created.
ORA-26031: index maintenance error, the load cannot continue
Cause: A index errror occurred during the index maintenance phase of * a direct path
load. The load cannot continue. See error message * below this message.
Action: See action for the error message which follows this one.
ORA-26032: index string.string loading aborted after string keys
Cause: An index error occurred during direct-load of an index-organized table. *
Loading had to be aborted. No rows were loaded.
Action: Check the key just following the number of keys mentioned above. * This key
caused the index problem mentioned in an earlier message. *
ORA-26033: column string.string encryption properties differ for source or target
table
Cause: The source and destination columns did not have the same * encryption
properties.
Action: For security reasons, check that the source and target table have * the same
encryption properties. *
ORA-26034: Column string does not exist in stream\n
Cause: Column specified in the column list does not exist in the stream.
Action: Make sure the column exists or remove it from the list.
ORA-26035: Error attempting to encrypt or decrypt column
Cause: An error occurred while attemping to encrypt or decrypt * a database column.
Action: Verify correct encryption key was specified. *
ORA-26036: subpartition load specified but table string is not subpartitioned\n
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: must specify partition name(s) for system partitioned table string\n
Cause: An attempt was made to load a system partitioned table with no partition
name(s) specified.
Action: Specify the partition name(s) explicitly.
ORA-26038: attempt to write audit record for SQL*Loader direct path load of
string.string failed with error code: number\n
Cause: An attempt to write an audit record during a SQL*Loader direct path load
failed.
ORA-24280 to ORA-28709 72-69
ORA-26040: Data block was loaded using the NOLOGGING option\n

Cause: Trying to access data in block that was loaded without * redo generation using
the NOLOGGING/UNRECOVERABLE option
Action: Drop the object containing the block.
ORA-26041: DATETIME/INTERVAL datatype conversion error\n
Cause: The column could not be converted from DATETIME * datatype to internal
DATETIME/CHARACTER datatype.
ORA-26045: REF column string expects string arguments; found string.\n
Cause: The number of arguments for the REF column is incorrect.
Action: Specify the correct number of input arguments for REFs. 1. Unscoped systemgenerated REFs can have exactly 1 or 2 input arguments. a) It has exactly 1 input
argument (one for the OID value) if a fixed table name was specified through
OCI_DIRPATH_EXPR_REF_TBLNAME. b) It has exactly 2 input arguments (one for
the table name and one for the OID value) if a fixed table name was not specified
through OCI_DIRPATH_EXPR_REF_TBLNAME. 2. Scoped system-generated REFs
can have 1 or 2 input arguments. Because a table name argument is not needed for a
scoped ref, only 1 argument (OID value) is expected. But if the table name argument
is given, it's still accepted. 3. Scoped primary-key REFs with N columns in its
primary-key OID can have N or N+1 input arguments. Because a table name
argument is not needed for a scoped ref, only N arguments (making up the OID
value) is expected. But if the table name argument is given, it's still accepted.
ORA-26046: REF column string expects scoped table name string; user passed in
string.\n
Cause: The scoped table name passed in by the user does not match the name in the
schema.
Action: Specify the correct table name for the scoped REF column.
ORA-26048: Scoped REF column has wrong table name.\n
Cause: The scoped table name passed in by the user does not match the name in the
schema.
Action: Specify the correct table name for the scoped REF column.
ORA-26049: Unscoped REF column has non-existent table name.\n
Cause: The table name passed in by the user does not exist in the schema.
Action: Specify a valid table name for the unscoped REF column.
ORA-26050: Direct path load of domain index is not supported for this column
type.\n
Cause: Direct path can not load a domain index of that column type.
Action: Drop the index and try again or load using conventional path.
ORA-26051: internal error parsing packed decimal format string
Cause: A packed decimal field with a non-zero scale factor is mapped to a character
column. In order to perform the datatype conversion, a numeric format string must be
created based on the input field's precision and scale specifications. Direct path loader
encountered an error in creating this format string.
Action: Examine the packed decimal field's precision and scale specifications and
make sure that they contain valid values.
ORA-26052: Unsupported type number for SQL expression on column string.\n

Cause: The direct path api does not support a SQL expression on a column of that
type.
Action: Make sure the types are correct.
ORA-26053: Row was not loaded due to conversion error.\n
Cause: The current row was not loaded due to a conversion error.
Action: Continue with the load anyways. 260xx - 260xx Direct Path API
ORA-26054: Direct Path Context prepared for a different mode than operation
requested.\n
Cause: The user prepared the direct path context for one operation (Load, Unload,
Convert), but then tried to perform a different operation.
Action: Make sure the direct path context mode and operation matches.
ORA-26055: Invalid buffer specified for direct path unload\n
Cause: The user specified a zero length or null buffer to be used for the Direct Path
Unload operation.
Action: Specify a valid buffer and length.
ORA-26056: Requested direct path operation on a view is not supported.\n
Cause: An attempt was made to load into a view using direct path that has userdefined types, XML data, object type table or SQL expressions.
Action: Do not attempt to use direct path when loading a view that has nonscalar
columns or when using SQL expressions on input columns.
ORA-26057: Conversion is not necessary for this direct path stream.\n
Cause: User attempted to convert a direct path stream that does not require
conversion.
Action: Load the stream without conversion it.
ORA-26058: unexpected error fetching metadata for column string in table string\n
Cause: The direct path API encountered an unexpected error while retrieving
metadata for a column.
ORA-26059: Data is too large for column string\n
Cause: The direct path API encountered a column that can not be loaded because the
input data is too large for a column.
Action: Make the target column larger.
ORA-26060: Can not convert type identifier for column string\n
Cause: The direct path API encountered a type identifier for a column that can not be
loaded because a mapping can not be found for the input value.
Action: Verify the input data.
ORA-26061: Concurrent direct unloads is not allowed.\n
Cause: User attempted a direct unload when another is still in progress.
Action: Complete the current direct unload before starting another.
ORA-24280 to ORA-28709 72-71
ORA-26062: Can not continue from previous errors.\n

Cause: User attempted to continue a direct path load after receiving an error which
indicates the load can not continue.
Action: Address the original error that was returned.
ORA-26063: Can not flashback to specified SCN value - Wrap: string Base: string.\n
Cause: User specified an SCN which occurs before the last time the table definition
was modified.
Action: Specify a more recent SCN.
ORA-26064: Invalid SCN specified - Wrap: string Base: string.\n
Cause: User specified an invalid SCN.
Action: Specify a valid SCN.
ORA-26065: check constraint cannot reference column, string, in direct path load\n
Cause: An enabled check constraint was found on a column stored as a lob.
Action: Either disable the check constraint before loading the table data * using the
direct path mode, or use the conventional path mode * instead.
ORA-26076: cannot set or reset value after direct path structure is allocated
Cause: Client attempted to set or reset the number of rows in a direct path * structure
after it has already been allocated and initialized. * Attributes used is one of the
following: * - OCI_ATTR_NUM_ROWS: to set # of rows in a direct path column array
* - OCI_ATTR_DIRPATH_DCACHE_SIZE: to set size of a date cache * (default is 0) * OCI_ATTR_DIRPATH_DCACHE_DISABLE: to set whether date cache will be *
disabled on overflow (default is FALSE)
Action: Set the following attributes before: * - OCI_ATTR_NUM_ROWS: before
calling OCIHandleAlloc for column array * - OCI_ATTR_DIRPATH_DCACHE_SIZE:
before calling OCIDirPathPrepare * - OCI_ATTR_DIRPATH_DCACHE_DISABLE:
before calling OCIDirPathPrepare
ORA-26077: direct path column array is not initialized
Cause: Client attempted to allocate a column array for a direct path * function context
before allocating a column array for the * table-level direct path context.
Action: Allocate the table-level direct path context's column array * via
OCIHandleAlloc before allocating column arrays for * direct path function contexts.
ORA-26078: file "string" is not part of database being loaded\n
Cause: A parallel load file was specified which is not part * of the database.
Action: Check filename and pathname for correctness.
ORA-26079: file "string" is not part of table string.string\n
Cause: A parallel load file was specified which is not in the * tablespace of the table
being loaded.
Action: Check to make sure that the specified parallel load file * is in the tablespace of
the table being loaded.
ORA-26080: file "string" is not part of table string.string partition string\n
Cause: A parallel load file was specified which is not in the * tablespace of the table
(partition, subpartition) being loaded. * When a partitioned table is being loaded, the
file must be * in the tablespace of every partition or subpartition * (i.e. each

(sub)partition must be in the same tablespace).
Action: Specify a different parallel load file, or no file at all.
ORA-26082: load of overlapping segments on table string.string is not allowed
Cause: Client application is attempting to do multiple direct path load * operations on
the same table, but the segments overlap.
Action: Check the partition names (subname attribute of the direct path * context)
being loaded. Make sure you are not loading a table, * and a partition of the same
table. Make sure you are not * loading a partition, and a sub-partition within the same
* partition.
ORA-26083: unsupported direct path stream version string
Cause: The stream version requested is not supported by the server.
Action: Check to make sure that the VERSION attribute of the direct * stream is not
being set to an invalid value.
ORA-26084: direct path context already finished
Cause: An OCIDirPathLoadStream operation was attempted after * OCIDirPathFinish
was called. Once a direct path operaton * has been finished, no more data can be
loaded.
Action: Check program logic to make sure 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 been started.
Action: Commit the transaction and Prepare the direct path operation again.
ORA-26086: direct path does not support triggers
Cause: A direct path operation is being attempted on a table which * has enabled
triggers.
Action: Disable the triggers on the table and try again.
ORA-26088: scalar column "string" must be specified prior to LOB columns
Cause: All scalar columns (i.e. non-LOB and non-LONG columns) must be * specified
by the client of the direct path API prior to * specifying any LOB columns.
Action: Specify all scalar columns prior to specifying any LOB columns.
ORA-26089: LONG column "string" must be specified last
Cause: A client of the direct path API specified a LONG column to be * loaded, but
the LONG column was not the last column to be * specified.
Action: Specify the LONG column last.
ORA-26090: row is in partial state
Cause: A direct path operation is being finished or a data save request * has been
made, but the table for which the request is being made * on has a row in partial state.
The row must be completed before * the segment high water marks can be moved.
Action: Either complete the row, or abort the direct path operation.
ORA-24280 to ORA-28709 72-73
ORA-26091: requested direct path operation not supported

Cause: A direct path operation was requested that is not supported
Action: Do not use that operation. Currently, UNLOAD is not supported.
ORA-26092: only LONG or LOB types can be partial
Cause: A column which is not a LONG or LOB had the *
OCI_DIRPATH_COL_PARTIAL flag associated with it. * Only LONG or LOB type
columns can be loaded in pieces.
Action: Do not use the OCI_DIRPATH_COL_PARTIAL flag for the column.
ORA-26093: input data column size (number) exceeds the maximum input size
(number)
Cause: The user attempted to specify a column size (%d) that exceeded * the
maximum allowable input size (%d)."
Action: Make sure the input column metadata matches the column definition.
ORA-26094: stream format error: input column overflow
Cause: An input stream contained data for more input columns * than specified by
the client of the direct path API.
Action: Make sure that the stream being loaded is for the * correct table. Check
initialization sequence.
ORA-26095: unprocessed stream data exists
Cause: Either a OCIDirPathLoadStream call was made which provided * more stream
data prior to the server being able to fully * process the stream data that it already
has, or a * OCIDirPathFinish call was made when the server had * unprocessed
stream data.
Action: Most likely an application mis-use of the direct path API. * Make sure that the
stream is not being reset inadvertently * prior to any previous stream data being
processed, or, that * OCIDirPathFinish is not being called prematurely (i.e. stream *
pushed, error encountered and LoadStream not called to process * the remainder of
the stream before Finish is called.)
ORA-26096: transfer size too small for row data (number bytes required)
Cause: Either the transfer buffer size specified, or the default * transfer buffer size (if
you did not specify a size), is * too small to contain a single row of the converted row
data.
Action: Set the transfer buffer size attribute of the direct path * context to be larger.
ORA-26097: unsupported conversion for column string (from 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 is not prepared
Cause: A direct path api function was called with a direct path * context which has
not been prepared.
Action: Make sure all necessary attributes in the direct path * context have been set,
and the context is prepared via * OCIDirPathPrepare.
ORA-26099: direct path context is already prepared

Cause: OCIDirPathPrepare was called with a context that has already * been
prepared.
Action: Free the direct path context, set necessary attributes, and * call
OCIDirPathPrepare.
ORA-26100: unused error
ORA-26101: tablespace # in file header is string rather than string for file string
Cause: The tablespace number in the file header is inconsistent with that in the control
file.
Action: Check if the control file has been migrated correctly. Retry with the correct
control file and data file.
ORA-26102: relative file # in file header is string rather than string for file string
Cause: The relative file number in the file header is inconsistent with that in the
control file.
Action: Check if the control file has been migrated correctly. Retry with the correct
control file and data file.
ORA-26103: V6 or V7 data file used to create control file
Cause: The file header of the referenced file is in V6 or V7 format.
Action: Either remove the file from the create control file command, or somehow
migrate the file header to V8 format.
ORA-26500: error on caching "string"."string"
Cause: Attempt to cache the replication information which is unavailable in the
catalog for the object.
Action: Use dbms_reputil.sync_up_rep to validate the replication catalog, or use
dbms_reputil.make_internal_pkg to validate internal package.
ORA-26501: RepAPI operation failure
Cause: An external RepAPI operation failed.
Action: consult detail error message.
ORA-26502: error resignal
Cause: An internal service failed and signalled an error"
Action: consult detail error message.
ORA-26503: internal RepAPI operation failure on object string.string
Cause: An unexpected internal RepAPI failure was detected
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
Action: Verify that sufficient memory resources are available to RepAPI.
ORA-24280 to ORA-28709 72-75
ORA-26506: null global context

Cause: An internal buffer control structure was NULL
Action: Verify that sufficient memory resources are available to RepAPI.
ORA-26507: null master connection
Cause: The master connection handle was or became invalid.
Action: Verify that the master connection is valid.
ORA-26508: null materialized view connection
Cause: The client connection handle was or became invalid.
Action: Verify that the client connection is valid.
ORA-26509: null materialized view control structure
Cause: An internal materialized view control structure could not be obtained.
Action: Check that the owner and users provided are correct.
ORA-26510: materialized view name: 'string' is greater than max. allowed length of
string bytes
Cause: The specified materialized view name was too long.
Action: Shorten the materialized view name.
ORA-26511: master table 'string.string' not found
Cause: A RepAPI operation was attempted against a non-existent or invalid master
table
Action: Verify that the master table object exists.
ORA-26512: error pushing transaction to def$error
Cause: An unexpected error occurred while sending an def$error rpc to the master
site
Action: Verify that the DBMS_DEFER package is valid and executable by the RepAPI
client. Contact the local or master site administrator, if necessary.
ORA-26513: push error: master proc. string$RP.string failed for trans:string
seq:string
Cause: A conflict/error occurred at the master site while executing a $RP.rep_insert(),
rep_update(), or rep_delete() function which was not handled by conflict resolution
logic at the master.
Action: Notify master site system adminstrator or DBA.
ORA-26514: object 'string.string' not found
Cause: The specified object was expected but not found.
Action: Verify that the specified object exists and is valid.
ORA-26515: no master log available for 'string.string'
Cause: The specified master log was not found or available for the named table.
Action: Create the master log at the master site or correct any problems that may exist
with the log.
ORA-26516: no push transaction acknowledgement
Cause: RepAPI was unable to confirm that the last pushed transaction was
successfully commited by the master site.
Action: Verify that the communications link between the local site and the master site
is still valid. If the transaction has not been committed at the master, repush the
transaction.
ORA-26517: materialized view control entry for 'string.string' was not found
Cause: The specified materialized view catalog control reocrd was not found.
Action: Verify that the local materialized view catalog is valid and that the local
materialized view is properly defined.
ORA-26518: push queue synchronization error detected
Cause: Client tried to repush a transaction has already been committed at the master
site. A common cause of this problem is an error at the local site in initializing or
updating the local site transaction sequence mechanism.
Action: Verify that transaction data that RepAPI was attempting to repushed to the
master site exists at the master table and is valid and consistent with the local site. If
this error occurs, redundantly identified transactions are ignored and then purged
from the local updatable materialized view logs. Check that the local site is correctly
assigning new transactionIDs and is not accidently generating non-unique values.
ORA-26519: no memory available to allocate
Cause: There was no memory left for the RepAPI process. This error may occur when
RepAPI is trying to allocate a new table buffer area.
Action: Shutdown one or more local applications to attempt to free heap memory and
retry the RepAPI operation.
ORA-26520: internal memory failure
Cause: An internal memory error was detected.
Action: Check if other errors have occurred or determine if any local application may
have corrupted the memory subsystem.
ORA-26521: rpc initialization error
Cause: An error occurred during the initialization of a PL/SQL rpc.
Action: Verify that the procudure to be invoked exists and is valid at the master site
and is executable by the RepAPI user.
ORA-26522: rpc execution error
Cause: An error occurred during the execution of a PL/SQL rpc.
Action: Check the error messages from the remote procedure and fix any remote site
problems that may be preventing the execution of the invoked rpc.
ORA-26523: rpc termination error
Cause: An error occurred during the termination of a PL/SQL rpc. This is usually
caused by master site being unable to close an opened cursor or if RepAPI cannot
deallocate internal memory.
Action: Fix any server side problems first, determine if the RepAPI memory
subsystem has been corrupted.
ORA-26524: nls subsystem initialization failure for product=string, facility=string
Cause: The NLS product/facility error message file could not be located or properly
initialized.
Action: Check that the error message directory and file(s) have been properly
installed.
ORA-24280 to ORA-28709 72-77
ORA-26525: session connection attempt failed for string (@string)

Cause: A connection could not be established to the specified database using the
provided connection string.
Action: Check that the user, password, connect string, names services, network, and
any remote site listener process are properly installed and working.
ORA-26526: materialized view sql ddl parse/expansion failed for string.string
Cause: The client sql materialized view definition query could not be properly parsed
by the master Oracle site.
Action: Check that materialized view ddl sql is compatible with the currently
connected version of Oracle and does not violate any of the RepAPI sql limitations or
restrictions.
ORA-26527: local store callback init phase failed for 'string.string'
Cause: The client callback failed during its INIT phase for the named object.
Action: Verify that the objects referenced by the client callback exist and are valid.
Refer to the vendor-specific callback error code reference to diagnose the local
problem. Record all error state and notify Oracle support.
ORA-26528: local store callback proc phase failed for 'string.string'
Cause: The client callback failed during its PROC phase for the named object.
Action: Refer to the vendor-specific callback error code reference to diagnose the local
ORA-26529: local store callback term phase failed for 'string.string'
Cause: The client callback failed during its TERM phase for the named object.
Action: Refer to the vendor-specific callback error code reference to diagnose the local
ORA-26530: unable to build materialized view refresh control list
Cause: The materialized view control list could not be constructed. This is generally
the result of an error while accessing the local materialized view catalog.
Action: Verify that the named materialized view(s) are properly defined and valid.
ORA-26532: replication parallel push simulated site failure
Cause: A parallel push executed with event 26531 enabled raises this error to
simulation failure of network or destination site.
Action: Do not enable the event for normal operation.
ORA-26534: collision: tranID number ignored and purged
Cause: A transaction that was pushed had a transaction ID that collided with a
transaction that was previously pushed and committed at the master site.
Action: See the action section for E_QUEUESYNC (26518).
ORA-26535: number byte row cache insufficient for table with rowsize=number
Cause: A transaction that was pushed had a transaction ID that collided with a
transaction that was previously pushed and committed at the master site.
Action: Increase the RepAPI row buffer size or reduce the width of the replicated
tables.
ORA-26536: refresh was aborted because of conflicts caused by deferred

transactions
Cause: There are outstanding conflicts logged in the DEFERROR table at the
materialized view's master site.
Action: Resolve the conflicts in the master DEFERROR table and refresh again after
the table is empty. Alternatively, refresh with REFRESH_AFTER_ERRORS, even if
there are conflicts in the master's DEFERROR table. Proceeding despite conflicts can
result in an updatable materialized view's changes appearing to be temporarily lost,
until a refresh succeeds after the conflicts are resolved.
ORA-26562: last RepAPI error
ORA-26563: renaming this table is not allowed
Cause: Attempt to rename a replicated table, an updatable materialized view table or
the master table of a materialized view for which a materialized view log has
beencreated.
Action: If desired, unregister the replicated table with
dbms_repcat.drop_master_repobject, or use the recommended procedure to rename
the master table of a materialized view.
ORA-26564: string argument is not of specified type
Cause: User passed type of the given argument number doesn't match with the type
of the argument in the stored arguments.
Action: Invoke correct type procedure (i.e. get_XXX_arg)
ORA-26565: Call to type_arg made before calling dbms_defer.call
Cause: User invoked type_arg procedure before starting a deferred call
Action: Invoke various procedures in the correct order.
ORA-26566: Couldn't open connect to string
Cause: Failed to open connection using given dblink
Action: Make sure that the dblink is valid and 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
Action: examine total number of arguments for the rpc call
ORA-26572: string.string.string: argument string does not match replication catalog
Cause: the (rpc) call is corrupted
Action: examine total number of arguments and each argument for the rpc call
ORA-26575: remote database does not support replication parallel propagation
Cause: The remote database has a version lower than Oracle 8.0 and hence does not
understand replication parallel propagation.
Action: Use serial propagation or upgrade the remote database to Oracle 8.0 or above.
ORA-26576: cannot acquire SR enqueue
Cause: An attempt to acquire the SR enqueue in exclusive mode failed.
Action: n/a
ORA-24280 to ORA-28709 72-79
ORA-26577: PRESERVE TABLE can not be used when dropping old style
materialized view string.string\n
Cause: The materialized view consists of a view and a container table.
Action: Drop the materialized view without PRESERVE TABLE option.
ORA-26578: No capture in this multitenant container database associated with
queue "string".
Cause: An outbound server's queue was not associated with a capture from the same
multitenant container database (CDB) before adding or starting an outbound server.
Action: Execute the DBMS_STREAMS_ADM.CREATE_CAPTURE procedure to
create a capture before adding or starting an outbound server.
ORA-26650: string string background process string might not be started
successfully
Cause: An error occurred during creation of a capture or apply background process.
Action: Review V$STREAMS_CAPTURE and V
$STREAMS_APPLY_COORDINATOR views for the status of these processes. Also
check the trace file for more information.
ORA-26651: Unable to start or stop capture process string
Cause: An attempt was made to start or stop a capture process while another capture
process was concurrently starting or stopping.
Action: You cannot concurrently start or stop capture processes. Wait before
attempting to start or stop additional capture processes.
ORA-26652: Capture string did not start properly and is currently in state string
Cause: An attempt to restart a capture process failed.
Action: Review V$STREAMS_CAPTURE view for the state of the capture process.
Also check the trace files for more information.
ORA-26653: Apply string did not start properly and is currently in state string
Cause: An attempt to restart an apply process failed.
Action: Streams: Review V$STREAMS_APPLY% views for the state of the apply
process. Also check the trace files for more information. XStream: Review V
$XSTREAM_APPLY% views for the state of the apply process. Also check the trace
files for more information. GoldenGate: Review V$GG_APPLY% views for the state
of the apply process. Also check the trace files for more information.
ORA-26654: Capture string attempted to connect to apply string already configured
for string
Cause: An attempt was made by a GoldenGate, XStream or Streams Capture or
XStream In to connect to an Apply that is already connected in the other mode.
Action: You cannot connect a capture to an apply already configured for another
apply mode. Create or connect to another apply.
ORA-26655: Invalid string specified for string procedure
Cause: An attempt was made to execute the specified procedure with an invalid SCN
value.
Action: Resubmit procedure with a valid SCN value.
ORA-26656: supplemental logging version error: string

Cause: The supplemental logging versions of capture side and apply side are
incompatible.
Action: For incompatibility caused by a newer apply side, please bypass or migrate
the incompatible logs manually and consider upgrading or patching the capture side.
For incompatibility caused by an unrecognizable version group or an older apply
side, please upgrade or patch the apply side. For invalid versions, the logs might have
been corrupted; please verify the integrity of the supplemental logging data on the
capture side.
ORA-26660: Invalid action context value for string
Cause: The value specified in the action context is invalid for use in GoldenGate,
XStream or Streams.
Action: Check that the type and value are correct.
ORA-26662: unable to process string Data Dictonary information for object
Cause: The database is unable to process GoldenGate, XStream or Streams Data
Dictionary for this object.
Action: Check that the compatibility for the database supports the object, and check
the trace file for information about the object.
ORA-26663: error queue for apply process string must be empty
Cause: The error queue for this apply process contains error entries.
Action: Execute or delete errors in the error queue.
ORA-26664: cannot create string process string
Cause: An attempt was made to create a GoldenGate, XStream or Streams process
when another was being created concurrently.
Action: Wait for the creation of the other GoldenGate, XStream or Streams process to
finish before attempting to create the process.
ORA-26665: string process string already exists
Cause: An attempt was made to create a GoldenGate, XStream or Streams process
that already exists.
Action: Either specify another process or remove the existing GoldenGate, XStream or
Streams process.
ORA-26666: cannot alter string process string
Cause: An attempt was made to alter a GoldenGate, XStream or Streams process that
is currently running.
Action: Stop the GoldenGate, XStream or Streams process with FORCE parameter set
to TRUE and reissue the command.
ORA-26667: invalid string parameter string
Cause: An attempt was made to specify an invalid parameter.
Action: Check the documentation for valid parameters.
ORA-26668: string process string exists
Cause: An attempt to remove the component failed because it is associated with the
GoldenGate, XStream or Streams process.
ORA-24280 to ORA-28709 72-81
Action: Either remove the process manually or specify the "cascade" option in
dbms_streams_adm.remove_queue.
ORA-26669: parameter string inconsistent with parameter string
Cause: An attempt was made to specify a subprogram parameter value that is
inconsistent with another parameter value.
Action: Check the documentation for valid parameter values.
ORA-26670: No capture is found for queue 'string'
Cause: An attempt was made to add an XStream outbound server to a queue using
uncommitted data mode when no co-located XStream capture was configured for that
queue.
Action: Change to committed data mode or configure a local XStream capture for the
specified queue then retry the operation.
ORA-26671: maximum number of string processes exceeded
Cause: Cannot create additional GoldenGate, XStream or Streams processes since the
maximum number of processes has been reached.
Action: Remove existing GoldenGate, XStream or Streams processes and retry the
operation.
ORA-26672: timeout occurred while stopping string process string
Cause: Timeout occurred while waiting for a GoldenGate, XStream or Streams
process to shut down.
Action: Retry the operation. If the error persists, try stopping the process with the
FORCE option, or contact Oracle Support Services.
ORA-26673: duplicate column name string
Cause: An attempt was made to specify a duplicate column name in an LCR.
Action: Remove the duplicate column and retry the operation.
ORA-26674: Column mismatch in 'string.string' (LCR: string type=string; DB: string
type=string)
Cause: The columns in the LCR were not the same or not found in the database table.
Action: Alter the database table.
ORA-26675: cannot create string capture process string
Cause: GoldenGate, XStream or Streams capture process could not be created because
one or more parameters contain invalid value.
Action: Refer to trace file for more details.
ORA-26676: Table 'string.string' has string columns in the LCR and string columns
in the replicated site
Cause: The number of columns in the LCR was not the same as the the replicated site.
Action: Alter the table structure
ORA-26677: string downstream capture process string cannot proceed
Cause: Database global name has been set to a value which is same as the source
database name of the downstream capture process.
Action: Change database global name to a value other than the source database name
for the downstream capture.
ORA-26678: string downstream capture process for source database string must be
created at database string first
Cause: A GoldenGate, XStream or Streams downstream capture process was
nonexistent when this operation was attempted.
Action: Create a GoldenGate, XStream or Streams downstream capture process, then
ORA-26679: operation not allowed on LOB or LONG columns in LCR
Cause: Certain operations on LOB/LONG columns of the LCR through rule-based
transformations, DML handlers, or error handlers were not allowed.
Action: Do not perform restricted operations on LOB or LONG columns in LCRs. See
the documentation for operations that are restricted on LOB/LONG columns in
LCRs.
ORA-26680: object type not supported
Cause: The specified object type is not supported.
Action: Retry with a supported object type.
ORA-26681: command type not supported
Cause: The specified command type is not supported.
Action: Retry with a supported command type.
ORA-26682: invalid value for publication_on
Cause: The publication_on parameter should be either 'Y' or 'N'
Action: Retry with a proper value for publication_on.
ORA-26683: invalid value for value_type
Cause: The value_type parameter should be either 'OLD' or 'NEW'
Action: Retry with proper value_type.
ORA-26684: invalid value for value_type
Cause: The value_type parameter should be one of 'OLD', 'NEW' or '*'
Action: Retry with proper value_type.
ORA-26685: cannot apply transactions from multiple sources
Cause: Transactions from multiple sources were sent to the same apply process.
Action: Create multiple apply processes and create appropriate rules so that
transactions from only one source reach an apply process.
ORA-26686: cannot capture from specified SCN
Cause: An attempt was made to specify an invalid SCN.
Action: Retry with a valid SCN.
ORA-26687: no instantiation SCN provided for "string"."string" in source database
"string"
Cause: Object SCN was not set. If the object is a table, then both fields will be filled,
for example "SCOTT"."EMP". If the object is a schema, only one field will be set, for
example "SCOTT"."". And if the object is the entire database, no fields will be set, for
example ""."".
Action: Set the SCN by calling DBMS_APPLY_ADM.SET_%_INSTANTIATION_SCN
ORA-24280 to ORA-28709 72-83
ORA-26688: missing key in LCR

Cause: Metadata mismatch, or not enough information in the user generated LCR.
Action: Alter the database object, or provide all defined keys in the LCR.
ORA-26689: column datatype mismatch in LCR
Cause: The datatypes of columns in the LCR are not the same as the datatypes in the
database object.
Action: Alter the database object.
ORA-26690: datatype not supported at non-Oracle system
Cause: One of the columns of the LCR being applied was of a datatype not supported
by either the target non-Oracle system or by the Oracle transparent gateway through
which the apply is being done.
Action: Do not apply data of this type. If possible, filter out columns containing such
datatypes before applying.
ORA-26691: operation not supported at non-Oracle system
Cause: The apply process attempted an operation that is either not supported by the
non-Oracle system or by the Oracle transparent gateway through which the apply is
being done. Some kinds of DML (like procedure and function calls) and all DDL will
cause this error to be raised.
Action: Do not attempt to apply such LCRs to non-Oracle systems. If possible, filter
out such LCRs before applying.
ORA-26692: invalid value string, string should be in string format
Cause: The parameter specified was not in the correct format.
Action: Specify the parameter value in the correct format.
ORA-26693: string string process dropped successfully, but error occurred while
dropping rule set string
Cause: An attempt to drop an unused rule set failed after dropping the GoldenGate,
XStream or Streams proccess successfully.
Action: Check existence of rule set and manually drop if necessary.
ORA-26694: error while enqueueing into queue string.string
Cause: An error occurred while enqueueing a message.
Action: If the situation described in the next error on the stack can be corrected, do so.
ORA-26695: error on call to string: return code string
Cause: A locking related call failed.
Action: Try the call again after fixing the condition indicated by the return code.
ORA-26696: no string data dictionary for object with number string and version
number string from source database string
Cause: An attempt to access the database object failed because the data dictionary for
the object was either never populated or it was purged.
Action: Make sure the GoldenGate, XStream or Streams data dictionary is created by
calling DBMS_CAPTURE_ADM.PREPARE_%_INSTANTIATION.
ORA-26697: LCR contains extra column 'string'
Cause: The LCR contained more columns than the replicated table.
Action: Alter the database object.

ORA-26698: string did not have a string rule set
Cause: The GoldenGate, XStream or Streams client does not have a rule set of the
indicated type.
Action: Verify that the GoldenGate, XStream or Streams client has a rule set of the
specified type, and retry the operation.
ORA-26699: string message consumer string already exists
Cause: An attempt was made to create a GoldenGate, XStream or Streams message
consumer that already exists.
Action: Either specify another message consumer or remove the existing GoldenGate,
XStream or Streams message consumer.
ORA-26701: string process string does not exist
Cause: An attempt was made to access a GoldenGate, XStream or Streams process
which does not exist.
Action: Check with the relevant security views for the correct name of the object.
ORA-26704: The Owner instance string of the queue table is not up or the QMN0
process is down.
ORA-26705: cannot downgrade capture process after Streams data dictionary has
been upgraded
Cause: An attempt was made to downgrade a capture process after it has upgraded
the GoldenGate, XStream or Streams data dictionary.
Action: Drop the capture process before attempting the downgrade.
ORA-26706: cannot downgrade capture process
Cause: An attempt was made to downgrade a capture process that has a higher
version than the downgrade release version.
Action: Drop the capture process after capture has finished consuming all the redo
logs before attempting the downgrade.
ORA-26708: remote DDL not supported by STREAMS : dblink string
Cause: The apply process attempted to apply a DDL LCR via a dblink. This is not
supported.
Action: Do not attempt to apply DDL LCRs via a dblink. If possible, filter out DDL
LCRs before applying.
ORA-26709: Downstream Capture RFS restart
Cause: Remote file server (RFS) process was restarted to reflect a change in
DOWNSTREAM_REAL_TIME_MINE option of the GoldenGate, XStream or Streams
capture process.
Action: No action required. This is an informational message only.
ORA-26710: incompatible version marker encountered during Capture
Cause: Capture process cannot mine redo from a version higher than the current
software release version.
Action: Drop and recreate the capture process.
ORA-24280 to ORA-28709 72-85
ORA-26711: remote table does not contain a primary key constraint

Cause: The master table for remote apply does not constain a primary key constraint
or the primary key constraint has been disabled.
Action: Create a primary key constraint on the master table or enable the existing
constraint.
ORA-26712: remote object is "string"."string"\@"string"
Cause: See the preceding error message to identify the cause. This message names the
remote object, usually a table or view, for which an error occurred when GoldenGate,
XStream or Streams tried to access it for remote apply.
Action: See the preceding error message.
ORA-26713: remote object does not exist or is inaccessible
Cause: GoldenGate, XStream or Streams replication could not access the named table
or view at a remote database to apply changes.
Action: Confirm that the given remote table or view exists and is accessible through
the given database link. When using a Heterogeneous Services database link to access
a non-Oracle system, it may be necessary to check administration details for network
connections at the non-Oracle system.
ORA-26714: User Error string encountered during apply process
Cause: An error was encountered during an apply process.
Action: Query the DBA_APPLY_ERROR view to determine the error and take the
appropriate action.
ORA-26715: time limit reached
Cause: The specified time limit was reached for the GoldenGate, XStream or Streams
process.
Action: Restart the GoldenGate, XStream or Streams process, increasing the
TIME_LIMIT parameter if necessary.
ORA-26716: message limit reached
Cause: The specified message limit was reached for the Capture process.
Action: Restart the Capture process, increasing the MESSAGE_LIMIT parameter if
necessary.
ORA-26717: SCN limit reached
Cause: The specified SCN limit was reached for the GoldenGate, XStream or Streams
process.
Action: Change the MAXIMUM_SCN parameter, then restart the GoldenGate,
XStream or Streams process.
ORA-26718: transaction limit reached
Cause: The specified transaction limit was reached for the Apply process.
Action: Restart the Apply process, increasing the TRANSACTION_LIMIT parameter
if necessary.
ORA-26721: enqueue of the LCR not allowed
Cause: An apply process attempted to enqueue an LCR with a LONG column. This is
not supported.
Action: Modify rules or unset the enqueue destination to prevent LCRs with LONG
columns from being enqueued by the apply process.
ORA-26723: user "string" requires the role "string"
Cause: The caller did not have the specified role or called the procedure from a
definer's rights package or procedure.
Action: Grant the specified role to the caller. If the procedure is called from a definer's
rights package or procedure, change the definer's rights package or procedure to an
invoker's rights package or procedure. Or grant all the privileges for the specified role
explicitly.
ORA-26724: only SYS is allowed to set the Capture or Apply user to SYS.
Cause: The Capture or Apply user was specified as SYS by a user other than SYS.
Action: Set SYS as the Capture or Apply user while logged in as SYS.
ORA-26725: cannot downgrade apply handlers
Cause: An attempt was made to downgrade apply handlers that are not associated
with a local database object, or the apply handlers are associated with a specific apply
process.
Action: Drop the associated apply handlers before attempting the downgrade.
ORA-26726: standby and DOWNSTREAM_REAL_TIME_MINE are incompatible
Cause: An attempt was made to set the standby database and
DOWNSTREAM_REAL_TIME_MINE option of the Oracle GoldenGate, XStream or
Oracle Streams capture process on the same database.
Action: Do not attempt to set the DOWNSTREAM_REAL_TIME_MINE option for a
Oracle GoldenGate, XStream or Oracle Streams capture process on a standby
database. Do not attempt to change a database role to standby if there exists a capture
process with the DOWNSTREAM_REAL_TIME_MINE parameter set to Y.
ORA-26727: Cannot alter queue_to_queue property of existing propagation.
Cause: The queue_to_queue property was specified for an existing propagation.
Action: Pass NULL for the queue_to_queue argument.
ORA-26730: string 'string' already exists
Cause: An attempt to use FILE GROUP, FILE GROUP VERSION, or FILE GROUP
FILE failed because the item in question already exists.
Action: Remove the object if appropriate and re-attempt the operation.
ORA-26731: string 'string' does not exist
Cause: A FILE GROUP, FILE GROUP VERSION, or FILE GROUP FILE was specified
that does not exist.
Action: Make sure the object exists and re-attempt the operation.
ORA-26732: invalid file group string privilege
Cause: The specified privilege number that was specified is invalid.
Action: Check specification of dbms_file_group for valid privileges.
ORA-26733: timed-out waiting for file group lock
Cause: The procedure waited too long while getting a lock to perform a file group
repository operation.
ORA-24280 to ORA-28709 72-87
ORA-26734: different datafiles_directory_object parameter must be specified

Cause: The attempted operation involved datafiles platform conversion which
required the datafiles_directory_object parameter to be specified for placing the
converted data files.
Action: Retry the operation after specifying a valid datafiles_directory_object
parameter. This directory must be different from the directory objects for any of the
datafiles for the specified file group version.
ORA-26735: operation not allowed on the specified file group version
Cause: One or more datafiles or export dump file(s) were missing from the specified
file group version.
Action: Retry the operation after adding all the data files and Data Pump dump file(s)
to the specified version.
ORA-26736: Data Pump error
Cause: A Data Pump error occurred when the procedure performed a File Group
Repository operation.
Action: Check the error stack and trace file for error details.
ORA-26737: version string already has an export dump file
Cause: A Data Pump dump file was added to a file group version that already has a
dump file.
Action: Remove the existing dump file if appropriate, and retry the operation.
ORA-26738: string 'string' is not empty
Cause: The FILE GROUP or FILE GROUP VERSION being dropped contained
objects.
Action: Remove the child objects, then retry the operation.
ORA-26740: cannot downgrade because there are file groups
Cause: An attempt was made to downgrade a database that has file groups.
Action: Drop all file groups before attempting the downgrade.
ORA-26741: cannot assemble lobs
Cause: An attempt was made to assemble lobs, but the compatibility of the source
database for the LOB information is lower than 10.2.0.
Action: Set ASSEMBLE_LOBS to FALSE in the DML or error handler while this
handler is processing LOB information from a source database with a compatibility
level lower than 10.2.0.
ORA-26742: Maximum number of ignored transactions exceeded
Cause: An attempt was made to add more than the allowed number of ignored
transactions.
Action: Please clear the current list of ignored transactions.
ORA-26744: string capture process "string" does not support "string"."string"
because of the following reason: string
Cause: GoldenGate, XStream or Streams capture encountered a table with an
unsupported property. The most common reason is an unsupported column data
type.
Action: Revise the Capture rules to skip over the table in question. One way might be
to add a negative rule excluding changes from the unsupported table from being
captured. Streams: Also query the DBA_STREAMS_UNSUPPORTED view to
determine which tables are not supported by Streams and for what reason. Consider
adding negative rules for any tables that may be captured, but are present in this
view. XStream: Also query the DBA_XSTREAM_OUT_SUPPORT_MODE view to
determine which tables are not supported by XStream and for what reason. Consider
adding negative rules for any tables that may be captured, but are present in this
view. GoldenGate: Also query the DBA_GOLDENGATE_SUPPORT_MODE view to
determine which tables are not supported by GoldenGate and for what reason.
Consider adding EXCLUDETABLE statements for any tables that may be captured,
but are present in this view. For potential workarounds to certain unsupported
properties, see Metalink.
ORA-26745: cursors (string) are not sufficient
Cause: The maximum number of open cursors was too small for GoldenGate,
XStream or Streams Apply.
Action: Increase the value of open_cursors.
ORA-26746: DDL rule "string"."string" not allowed for this operation
Cause: A DDL rule was specified for this operation.
Action: Specify a non-DDL rule for this operation.
ORA-26747: The one-to-many transformation function string encountered the
following error: string
Cause: The specified transformation function encountered an error.
Action: Ensure that the function does not process or return DDL LCRs. Also ensure
that the function does not return NULL.
ORA-26748: The one-to-one transformation function string encountered the
following error: string
Cause: The specified transformation function encountered an error.
Action: Ensure that the function does not return an LCR that has a different type from
the LCR which was passed to the function. Also ensure that the function does not
return NULL. For DDL transformation functions, creating and returning a new DDL
LCR is not allowed.
ORA-26752: Unsupported LCR received for "string"."string"
Cause: GoldenGate, XStream or Streams capture process received an LCR with
unsupported operation from LogMiner.
Action: Stream:If this object is listed in DBA_STREAMS_UNSUPPORTED view,
modify rules to prevent changes made to this object from getting captured. XStream:
If this object is listed in DBA_XSTREAM_OUT_SUPPORT_MODE view, modify rules
to prevent changes made to this object from getting captured. GoldenGate: If this
object is listed in DBA_GOLDENGATE_SUPPORT_MODE view, modify rules to
prevent changes made to this object from getting captured.
ORA-26753: Mismatched columns found in 'string.string'
Cause: The columns in the LCR were not the same as the table in the database.
Action: Alter the database table.
ORA-24280 to ORA-28709 72-89
ORA-26754: cannot specify both one-to-one transformation function string and oneto-many transformation function string
Cause: Both a one-to-one transformation function and a one-to-many transformation
function were specified for a rule.
Action: Remove either the one-to-one transformation function, or the one-to-many
transformation function.
ORA-26757: Timed out waiting for remote operation on instance string to finish
ORA-26760: Could not find message number string for transaction with id string
Cause: Error
Action: Contact Oracle support"
ORA-26761: Standby Redo Logs not available for real time mining
Cause: Standby Redo Logs required for real time mining by downstream capture
process were not available.
Action: Check the configuration of Standby Redo Logs and retry the operation at a
later time. To start the capture process without real time mining property, reset
DOWNSTREAM_REAL_TIME_MINE parameter of the capture process and retry the
operation.
ORA-26762: Cannot autogenerate name for parameter string because of the
following reason: string
Cause: An error was encountered while attempting to generate a name for a
parameter which was passed a NULL value.
Action: If possible, fix the error, otherwise specify the parameter name explicitly.
ORA-26763: invalid file type "string"
Cause: An invalid file type was specified for the ASM file.
Action: Check documentation for valid ASM file types.
ORA-26764: invalid parameter "string" for local capture "string"
Cause: An invalid parameter was specified for the local capture process.
Action: Check documentation for valid parameters.
ORA-26765: invalid parameter "string" for downstream capture "string"
Cause: An invalid parameter was specified for the downstream capture process.
Action: Check documentation for valid parameters.
ORA-26766: Unexpected redo pattern encountered by LogMiner
Cause: LogMiner encountered an unexpected redo pattern. This is usually caused by
tables with unsupported data types or newer table features.
Action: Remove the capture rule for the table and restart capture.
ORA-26767: Not enough redo log information for LogMiner
Cause: Direct-path SQL with NOLOGGING option or a SQL*Loader operation with
UNRECOVERABLE clause was specified for the table.
Action: Remove the capture rule for the table and restart capture.
ORA-26768: Maximum number of unsupported tables exceeded

Cause: An attempt was made to add more than the allowed number of unsupported
tables.
Action: Clear the current list of unsupported tables.
ORA-26770: Index-organized table not supported
ORA-26771: User-defined column type not supported
ORA-26772: Encrypted column not supported
ORA-26773: Invalid data type for column "string"
ORA-26774: Queue table not supported
ORA-26775: Temporary table not supported
ORA-26776: Subordinate object not supported
ORA-26777: External table not supported
ORA-26778: File column not supported
ORA-26779: Materialized view not supported
ORA-26780: Object table not supported
ORA-26781: Nested table not supported
ORA-26782: Function-based index not supported
ORA-26783: Column data type not supported
ORA-26785: Object has a NULL value
Cause: A method was invoked on a NULL object.
Action: Initialize the object with a non-NULL value.
ORA-26786: A row with key string exists but has conflicting column(s) string in
table string
Cause: The row to update or delete exists in the table but had conflicting value for
some columns.
Action: For Streams and XStream, please define a conflict resolution, or resolve the
conflict and execute the error transaction using
DBMS_APPLY_ADM.EXECUTE_ERROR. For logical standby, please verify the status
of the database guard to ensure local modifications are not allowed, then reinstantiate the table and contact support if the problem persists. For GoldenGate,
configure Conflict Resolution (CDR) or REPERROR handler for the table and restart
replicat.
ORA-26787: The row with key string does not exist in table string
Cause: The row to update or delete does not exist in the table.
Action: For Streams and XStream, please define a conflict resolution, or resolve the
conflict and execute the error transaction using
DBMS_APPLY_ADM.EXECUTE_ERROR. For logical standby, please verify the status
ORA-24280 to ORA-28709 72-91
of the database guard to ensure local modifications are not allowed, then reinstantiate the table and contact support if the problem persists. For GoldenGate,
configure Conflict Resolution (CDR) or REPERROR handler for the table and restart
replicat.
ORA-26788: The column string is not encrypted in the local database.
Cause: The column in the destination database is NOT encrypted while it is encrypted
in the source database.
Action: Set the corresponding column property in the destination database to
'encrypted' or change the apply parameter, PRESERVE_ENCRYPTED_COLS, to 'N' to
supress the error.
ORA-26789: Cannot split propagation string because only one propagation
originates from its source queue "string"."string"
Cause: Only one propagation originated from the propagation source queue.
Action: Please do not split this propagation.
ORA-26790: Requesting a lock on string "string" timed out
Cause: Could not get a lock on the object because another process was holding the
lock.
Action: Please try later.
ORA-26791: Cannot split or merge propagation "string"
Cause: A process tried to split or merge this propagation, but failed and left
STREAMS in an inconsistent state.
Action: Query DBA_RECOVERABLE_SCRIPT_BLOCKS view, and roll back the script
which tried to split or merge this propagation.
ORA-26792: Invalid source database name string
Cause: The value for the source database global name was not valid.
Action: Specify a valid database global name. If the source database is not the local
database, check the listener is up and running.
ORA-26793: Number of capture processes that enqueued message to queue
"string"."string" not equal to one
Cause: Split-merge API requires only one capture process enqueued message to the
queue where the propagation originated
Action: Please drop one capture, or split or merge another propagation.
ORA-26794: Hierarchically enabled tables not supported
Cause: Hierarchically enabled tables are not supported.
Action: Disable hierarchy for the table.
ORA-26795: Cannot modify an LCR received from an XStream outbound server
Cause: An attempt was made to modify an LCR generated by an XStream outbound
server.
Action: Clone the LCR generated by the XStream outbound server by using the
provided OCILCR* functions, such as OCILCRNew, OCILCRHeaderSet, and
OCILCRRowColumnInfoSet. Then modify the cloned LCR.
ORA-26798: LOB logical change record (LCR) missing LOB column in table
"string"."string"
Cause: The apply slave could not fill update LOB because of missing LOB column.
Action: Check that all LOB columns have been sent correctly.
ORA-26799: unique constraint string.string violated for table string.string with
column values string
Cause: The row to update or insert violated the unique constraint.
Action: For XStreams, define a conflict resolution, or resolve the conflict and execute
the error transaction using DBMS_APPLY_ADM.EXECUTE_ERROR.
ORA-26800: Apply not the only subscriber for "string"."string".
Cause: The combined capture and apply optimization could not be used since Apply
was not the lone subscriber to the queue.
Action: Apply has to be the only subscriber to the queue.
ORA-26801: More than one subscriber for "string"."string".
Cause: Multiple subscribers were found when the combined capture and apply
optimization was configured to only work for one subscriber.
Action: Configure a single subscriber, apply or propagation for the queue, or enable
the optimization for multiple subscribers.
ORA-26802: Queue "string"."string" has messages.
Cause: The combined capture and apply optimization could not be used since the
queue had messages.
Action: Make sure queue is empty before starting apply and capture.
ORA-26803: Subscribers have changed for queue "string"."string".
subscribers had changed.
Action: Optimization can be used only if the queue has a single subscriber.
ORA-26804: Apply "string" is disabled.
Cause: The apply process was disabled or aborted.
Action: Start the apply process.
ORA-26805: Queue "string"."string" has rule based subscribers.
queue had rule based subscribers.
Action: Make sure queue has no rule based subscribers before starting apply and
capture.
ORA-26806: Remote database could not support combined capture and apply
optimization.
Cause: The remote database has a version lower than Oracle 11.0 and hence does not
understand combined capture and apply optimization.
Action: Upgrade the remote database to Oracle 11.0 or above in order to use the
combined capture and apply optimization.
ORA-24280 to ORA-28709 72-93
ORA-26807: Database link is not NULL for Apply with the name "string" .
Cause: The combined capture and apply optimization could not be used since
apply_database_link was not NULL.
Action: Drop and recreate the apply with NULL value for apply_database_link.
ORA-26808: Apply process string died unexpectedly.
Cause: Apply process died unexpectedly.
Action: Check your system for anomalies and restart apply. If this error persists,
contact Oracle Support Services. See trace file for more details.
ORA-26809: Capture aborted: checkpoint-free mode requires combined capture and
apply mode.
Cause: The requirements for combined capture and apply mode were broken.
Action: Restore the combined capture and apply mode and then restart the capture. If
combined capture and apply mode is no longer desired, drop the existing checkpointfree capture and create another one that will take checkpoints.
ORA-26810: Apply "string" on database "string" is in the mode of combined capture
and apply.
Cause: The combined capture and apply optimization could not be used because
Apply was already in the mode of combined capture and apply.
Action: Do not configure two captures for one apply.
ORA-26811: Client has already attached to string apply "string".
Cause: The client has already attached to the specified apply process.
Action: Detach apply process before reattach.
ORA-26812: An active session currently attached to XStream server "string".
Cause: An attempt was made to attach to the specified XStream server while another
session was attached to it.
Action: Retry when there is no session attaching to the specified XStream server.
ORA-26813: The value for argument "ARRAY_SIZE" is too small
Cause: The value for argument "ARRAY_SIZE" was less than the number of columns
in the requested column list.
Action: Check the return value for "NUM_COLUMNS" parameter then allocate all
input arrays to at least that size and invoke the same OCI function again.
ORA-26814: The value for argument string exceeds maximum string
Cause: The value for specified value exceeded the maximum allowed.
Action: Correct the value of specified argument.
ORA-26815: Error from Apply Network Receiver for Apply "string" and Capture
"string".
Cause: The Apply Network Receiver aborted due to an unexpected error.
Action: Query DBA_APPLY_ERROR to determine the error and then restart the
Capture and Apply.
ORA-26816: string apply process "string" (OS id string) is exiting due to ORAstring.
Cause: An apply process encountered an unexpected error.
Action: Query DBA_APPLY to examine the status of Apply and restart Apply if
needed.
ORA-26817: string capture process "string" is unable to communicate with capture
server string during initialization.
Cause: Capture server might not be started properly
Action: Fix any errors during capture server creation and re-start capture process
ORA-26818: string capture process string receives an error from capture server.
Cause: Capture server received an error.
Action: Check log for error details.
ORA-26819: string capture server for apply "string" and capture "string"encounters
disabled or aborted propagation "string".
Cause: Propagation was disabled or aborted.
Action: Start propagation.
ORA-26820: string capture server for apply "string" and propagation "string"
becomes active and needs join capture process "string".
Cause: Capture server was waiting for propagation or apply to start
Action: Capture process needs restart (done automatically).
ORA-26821: No propagation process found between source queue "string"."string"
and destination queue "string"."string".
Cause: Propagation has not been configured.
Action: Configure a propagation between specified queues and restart capture.
ORA-26822: Failure in creating capture servers (ksv error code string).
Cause: Failure in ksv slave creation.
Action: Identify the actual ksv error and act accordingly.
ORA-26823: string capture server string is unable to communicate with capture
process "string".
Cause: Capture process was not started properly or was aborted.
Action: If Oracle GoldenGate, XStream or Streams capture process was stopped, then
restart the capture process. Otherwise, fix any errors during the capture process
creation and restart the capture process.
ORA-26824: user-defined XStream callback error
Cause: A value other than OCI_CONTINUE or OCI_SUCCESS was returned for the
user-defined XStream callback function. Any returned value other than
OCI_CONTINUE or OCI_SUCCESS is invalid.
Action: Verify that either OCI_CONTINUE or OCI_SUCCESS is returned from the
user-defined XStream callback function.
ORA-26825: STREAMS process "string" is not configured as an XStream outbound
server.
Cause: An attempt was made to attach to a STREAMS apply process, which was not
configured as an XStream outbound server.
Action: Check the apply name or re-create the apply process as an XStream outbound
server.
ORA-24280 to ORA-28709 72-95
ORA-26826: string apply coordinator and apply slave are unable to communicate.
Cause: GoldenGate, XStream or Streams Apply process may have died unexpectedly.
Action: Check your system for anomalies and restart apply. If this error persists,
contact Oracle Support Services. See trace file for more details.
ORA-26827: Insufficient privileges to attach to XStream outbound server "string".
Cause: Sufficient privileges were not granted to attach to the specified XStream
outbound server.
Action: Query DBA_XSTREAM_OUTBOUND view to get the connect_user value for
the specified outbound server. Then modify the application to connect to the
outbound server's database using this value.
ORA-26828: XStream outbound server "string" requires combined capture and
apply mode.
Cause: The specified XStream outbound server was not in combined capture and
apply mode.
Action: Restore the combined capture and apply mode and then restart the capture.
ORA-26829: Cannot set "DISABLE_ON_ERROR" parameter to 'N'.
Cause: An attempt was made to change the "DISABLE_ON_ERROR" parameter for an
XStream outbound server to 'N'.
Action: Remove invalid statement.
ORA-26830: Cannot define handler for an XStream outbound server.
Cause: An attempt was made to define a handler for an XStream outbound server.
ORA-26831: Cannot delete or execute error transaction from XStream outbound
server "string".
Cause: An attempt was made to delete or execute an error transaction from the
specified XStream outbound server.
ORA-26832: Unable to create XStream outbound server "string" due to existing
handler.
Cause: An attempt was made to create the specified XStream outbound server while
there was a handler defined for the specified server.
Action: Use DBMS_APPLY_ADM.SET_DML_HANDLER procedure to remove all
handlers defined on the specified server then retry statement.
ORA-26833: string failed to update acknowledgment SCN for propagation "string"
from capture "string" to apply "string".
Cause: propagation might have been modified after GoldenGate, XStream or Streams
was started.
Action: Ensure propagation is configured properly and restart GoldenGate, XStream
or Streams.
ORA-26834: Unable to alter parameter 'string' because string capture process is not
configured to run locally
Cause: An attempt was made to alter the specified capture parameter when the
GoldenGate, XStream or Streams capture process was not configured to run on the
local database.
Action: Remove the invalid parameter or use
DBMS_CAPTURE_ADM.ALTER_CAPTURE procedure to alter the parameter.
ORA-26835: The source database for XStream outbound server "string" is invalid
Cause: An attempt was made to add an XStream outbound server with a source
database that was different from the associated capture's source database.
Action: Correct the value for the 'source_database' parameter in the call.
ORA-26836: The specified rules must be created from the same subsetting
condition
Cause: An attempt was made to remove an outbound server's subset rules when the
specified INSERT, UPDATE, and DELETE rules were not created from the same
subsetting condition.
Action: Correct the rules in the statement.
ORA-26837: Server "string" is not an XStream inbound server
Cause: An attempt was made to execute a procedure not appropriate on an XStream
inbound server.
Action: Replace with a procedure appropriate for an XStream inbound server and
resubmit.
ORA-26838: Setting apply parameter "string" is not permitted for XStream
Outbound Server
Cause: An attempt was made to set an apply parameter that was not applicable for
XStream Outbound Server.
Action: Configure XStream Outbound Server using valid parameters. Check the
documentation for valid parameter values.
ORA-26839: Apply tag for apply "string" is not permitted for XStream Outbound
Server
Cause: An attempt was made to set an apply tag that was not applicable for XStream
Outbound Server.
Action: Do not set the apply tag when using XStream Outbound Server.
ORA-26840: Combined capture and apply optimization is disabled because string is
unable to identify an apply for the source database "string".
Cause: There were multiple Streams apply processes using the same queue which
made combined capture and apply (CCA) optimization not possible.
Action: If Streams performance is an issue, check the "Combined Capture and Apply
Optimization" chapter in the "Oracle Streams Concepts and Administration" book.
Then reconfigure the Streams processes to meet this optimization's requirements.
ORA-26841: No subscribers are found for queue "string"."string".
Cause: No propagation or apply was configured for the specified queue.
Action: Configure propagation or apply for the specified queue.
ORA-24280 to ORA-28709 72-97
ORA-26842: Setting apply directive "string" is not permitted for XStream Outbound
Server
Cause: An attempt was made to set an apply directive that was not applicable for
XStream Outbound Server.
Action: Configure XStream Outbound Server using valid directives. Check the
documentation for valid directives.
ORA-26843: Local propagation "string" found for capture queue "string"."string".
Cause: The combined capture and apply optimization could not be used because a
local propagation was attached to the capture queue.
Action: Remove the local propagation and restart capture.
ORA-26844: Found "string" active automatic split jobs for string Capture "string" in
DBA_STREAMS_SPLIT_MERGE
Cause: Only one active split job is allowed for each GoldenGate, XStream or Streams
Capture, but multiple active automatic split jobs were found in
DBA_STREAMS_SPLIT_MERGE.
Action: Check trace to see how the jobs were submitted and drop them.
ORA-26845: Found "string" active split rows with the same cloned string Capture
"string" in DBA_STREAMS_SPLIT_MERGE
Cause: In DBA_STREAMS_SPLIT_MERGE, for active split rows, the column
CLONED_CAPTURE_NAME should be unique. However, multiple rows were found
whose ACTION_TYPE column is 'SPLIT', ACTIVE column is 'ACTIVE' and have the
same CLONED_CAPTURE_NAME.
Action: Check trace to see how the rows were inserted and call
DBMS_STREAMS_ADM.RECOVER_OPERATION() for error recovery.
ORA-26846: Found "string" active automatic merge jobs for cloned string Capture
"string" in DBA_STREAMS_SPLIT_MERGE
Cause: Only one active merge job is allowed for each cloned GoldenGate, XStream or
Streams Capture , but multiple active automatic merge jobs were found in
DBA_STREAMS_SPLIT_MERGE.
Action: Check trace to see how the jobs were submitted and drop them.
ORA-26847: Found invalid string type: "string"
Cause: Invalid GoldenGate, XStream or Streams type to split off was found. Type
should only be 'PROPAGATION'(1) or 'APPLY'(2).
Action: Check trace to see how the invalid GoldenGate, XStream or Streams type was
created and correct it.
ORA-26848: Split a nonexistent Streams Capture process "string" in job "string"
Cause: The job attempted to split a non-existent original Streams Capture.
Action: Drop the split job, or wait until the Streams Capture comes to existence.
ORA-26849: Split a nonsplittable string Capture process "string" in job "string"
Cause: The job tried to split a GoldenGate, XStream or Streams Capture that was not
splittable. That is, the Capture either had less than two subscribers, or it was not the
only Capture of its queue.
Action: Drop the split job, or wait untill the GoldenGate, XStream or Streams Capture
becomes splittable.
ORA-26850: Changes to queue subscribers were detected by string capture process.

Cause: The subscribers for capture queue might have changed.
Action: Capture process will restart automatically.
ORA-26851: Unable to connect to apply "string" because it has connected to another
capture.
Cause: Another capture process is already connected to apply.
Action: Wait for the connected capture process to terminate or abort the connected
capture process.
ORA-26852: Invalid NULL value for column_value parameter.
Cause: NULL is not allowed to be passed as the column value.
Action: Replace NULL with a proper AnyData instance containing NULL, e.g.,
sys.AnyData.ConvertVarchar2(NULL), as the column value if the column value is
NULL.
ORA-26853: invalid cca maximum percentage string
Cause: Specified percentage value was not in range 0 - 100.
Action: Specify a percentage value in the range 0 - 100.
ORA-26854: string string has no enqueue or dequeue privileges to the queue.
Cause: The GoldenGate, XStream or Streams user did not have enqueue or dequeue
privilege to the queue.
Action: Grant GoldenGate, XStream or Streams user enqueue or dequeue privileges to
the queue.
ORA-26855: string string has insufficient database privilege to access the queue.
Cause: The GoldenGate, XStream or Streams user did not have sufficient database
privilege to access the queue.
Action: Grant GoldenGate, XStream or Streams user database privileges to access the
queue.
ORA-26856: STREAMS string has insufficient database privilege to access the
queue.
Cause: The GoldenGate, XStream or Streams user did not have sufficient database
privilege to access the queue.
Action: Grant GoldenGate, XStream or Streams user database privileges to access the
queue.
ORA-26857: LCR position cannot be null (XID=string).
Cause: The position of an LCR in the specified transaction was null.
Action: Use OCILCRHeaderSet to define the LCR position.
ORA-26858: LCR position must be strictly increasing (XID='string', LCR
position='string', previous position='string').
Cause: The position of an LCR in the specified transaction was less than or equal to
the previous LCR in transaction.
Action: Use OCILCRHeaderSet to correct the LCR position.
ORA-24280 to ORA-28709 72-99
ORA-26859: Server "string" is not an XStream outbound server

Cause: An attempt was made to execute a procedure not appropriate on an XStream
outbound server.
Action: Replace with a procedure appropriate for an XStream outbound server and
resubmit.
ORA-26860: Different transactions must have different transaction IDs
(XID='string', LCR position='string', previous commit position='string').
Cause: The position of an LCR in the specified transaction was greater than the
position of the previous commit LCR in transaction with same transaction ID.
Action: Use different transaction IDs for different transactions.
ORA-26862: LCR position must be greater than the processed low position of the
XStream inbound server (XID='string', LCR position='string').
Cause: The position of an LCR in the specified transaction was less than or equal to
the processed low postion of the XStream inbound server.
Action: Use OCILCRHeaderSet to correct the LCR position.
ORA-26863: Job "string" showing as an active job in
DBA_STREAMS_SPLIT_MERGE does not exist in DBA_SCHEDULER_JOBS.
Cause: An active job showing in DBA_STREAMS_SPLIT_MERGE did not exist. It
may have been dropped accidently or something was wrong with it.
Action: Check trace to identify the problem and call
DBMS_STREAMS_ADM.RECOVER_OPERATION() for error recovery.
ORA-26864: Error occurred in string automatic job: "string"
Cause: An error has happened inside GoldenGate, XStream or Streams automatic job.
Action: Check trace for more detail.
ORA-26865: must send a COMMIT LCR to end transaction 'string' before sending
another transaction
Cause: An attempt was made by a client application to send LCRs for a new
transaction before sending a COMMIT LCR for the specified transaction.
Action: Modify the client application to send a COMMIT LCR at the end of the
specified transaction.
ORA-26866: The Queue of string Apply process "string" is not changeable.
Cause: Not all of the conditions for the Queue of a GoldenGate, XStream or Streams
Apply process to be changeable were met. Conditions are: -The Apply process is not
running. -The Apply process has no error. -The Apply process has no spilling. -The
Apply process is not used for XStream Outbound or Inbound Servers. -The Apply
process is a local Apply process. -The corresponding GoldenGate, XStream or Streams
Capture process should be stopped.
Action: Make sure all of the conditions are met.
ORA-26867: string must be called during OCIXStreamOutLCRReceive execution
Cause: An attempt was made to execute the specified function while
OCIXStreamOutLCRReceive call was not in progress.
Action: Check your program and make sure the specified call is invoked during
OCIXStreamOutLCRReceive callback function.
ORA-26868: string must be called during OCIXStreamInLCRSend execution

Cause: An attempt was made to execute the specified function while
OCIXStreamInLCRSend call was not in progress.
Action: Check your program and make sure the specified call is invoked during
OCIXStreamInLCRSend callback function.
ORA-26869: must attach to an XStream inbound server before executing string
function
Cause: An attempt was made to invoke the specified function before executing
OCIXStreamInAttach call.
Action: Add OCIXStreamInAttach call before the specified function.
ORA-26870: cannot call string while OCIXStreamInLCRCallbackSend call is still
executing.
Cause: An attempt was made to invoke the specified call while
OCIXStreamInLCRCallbackSend call was executing.
Action: Check your program and remove the specified call when there is an
OCIXStreamInLCRCallbackSend call in progress.
ORA-26871: unexpected string call (expecting string)
Cause: Could be one of the following reasons: 1) An attempt was made to invoke
OCIXStreamInChunkSend when the most recent LCR or chunk sent did not have the
OCI_XSTREAM_MORE_ROW_DATA flag set; 2) An attempt was made to invoke
OCIXStreamInLCRSend when the most recent LCR or chunk sent had
OCI_XSTREAM_MORE_ROW_DATA flag set.
Action: n/a
ORA-26872: must attach to an XStream outbound server before executing string
function
OCIXStreamOutAttach call.
Action: Add OCIXStreamOutAttach call before the specified function.
ORA-26873: cannot call string while OCIXStreamOutLCRCallbackReceive call is
still executing.
Cause: An attempt was made to invoke the specified call while
OCIXStreamOutLCRCallbackReceive call was executing.
Action: Check your program and remove the specified call when there is an
OCIXStreamOutLCRCallbackReceive call in progress.
ORA-26874: string Capture process "string" cannot be split.
Cause: An attempt was made to split a GoldenGate, XStream or Streams Capture
process that could not be split. That is, the Capture process either had less than two
subscribers, or it was not the only Capture process of its queue.
Action: Wait until the GoldenGate, XStream or Streams Capture process can be split.
ORA-26875: Timeout while string automatic split job "string" waits for the
subscriber "string" of Capture process "string" to acknowledge split
Cause: To split a subscriber of a GoldenGate, XStream or Streams Capture process, an
automatic split job needs to wait until the subscriber acknowledges the split. The wait
timed out.
Action: n/a
ORA-24280 to ORA-28709 72-101
ORA-26876: invalid processed low-watermark (current position=string; new

position=string)
Cause: An attempt was made to set the processed low-watermark to a value that was
less than the current processed low-watermark.
Action: Correct the processed low-watermark in OCIXStreamOutProcessedLWMSet
call.
ORA-26877: must reattach after an OCIXStreamOut call was interrupted
Cause: An attempt was made to execute another OCIXStreamOut API when an earlier
call was interrupted because the XStream outbound server was disabled or the client
requested cancellation of the operation.
Action: Execute OCIXStreamOutAttach call to reattach to the same XStream outbound
server.
ORA-26878: inconsistent input LCR (LCR is 'string' type, expecting 'string')
Cause: An attempt was made to send an LCR that was not consistent with the
specified LCR type.
Action: Correct your application to specify an LCR type that agrees with the LCR to
be sent.
ORA-26879: "SET_ENQUEUE_DESTINATION" directive is not permitted on rules
used by XStream outbound server "string"
Cause: One or more rules, used by the specified XStream outbound server, had
SET_ENQUEUE_DESTINATION directive defined.
Action: Execute the following: 1) Execute query SELECT xr.rule_owner, xr.rule_name,
xr.rule_set_owner, xr.rule_set_name FROM dba_apply_enqueue e,
dba_xstream_rules xr WHERE e.rule_owner = xr.rule_owner AND e.rule_name =
xr.rule_name AND xr.streams_name = specified outbound server; 2) For each rule
returned, execute DBMS_APPLY_ADM.SET_ENQUEUE_DESTINATION procedure
to set the destination queue to null, or execute DBMS_RULE_ADM.REMOVE_RULE
to remove that rule from its associated rule set.
ORA-26880: "SET_EXECUTE" directive is not permitted on rules used by XStream
outbound server "string"
Cause: One or more rules, used by the specified XStream outbound server, had
SET_EXECUTE directive defined.
Action: Execute the following: 1) Execute query SELECT xr.rule_owner, xr.rule_name,
xr.rule_set_owner, xr.rule_set_name FROM dba_apply_execute e, dba_xstream_rules
xr WHERE e.rule_owner = xr.rule_owner AND e.rule_name = xr.rule_name AND
xr.streams_name = specified outbound server; 2) For each rule returned, use
DBMS_APPLY_ADM.SET_EXECUTE procedure to set the EXECUTE parameter to
TRUE, or use DBMS_RULE_ADM.REMOVE_RULE to remove that rule from its
associated rule set.
ORA-26881: ORA-string: string raised in string automatic string job:"string"."string"
for Capture process "string" and cloned Capture process "string".
Cause: An error was raised in a GoldenGate, XStream or Streams automatic split/
merge job for the given original and cloned Capture processes.
Action: Check the corresponding split/merge row in
DBA_STREAMS_SPLIT_MERGE view, alert log and trace file for details.
ORA-26882: Timeout while string automatic split/merge job:"string"."string" tried to

lock Capture process "string".
Cause: The GoldenGate, XStream or Streams Capture process could be locked by
other automatic split/merge jobs.
Action: No action required. The GoldenGate, XStream or Streams automatic split/
merge job will retry automatically.
ORA-26883: Timeout due to string Apply process "string" while merge original
Capture process "string" and cloned Capture process "string".
Cause: When merging two GoldenGate, XStream or Streams Capture processes, the
merge needs to wait untill the Apply process of the cloned Capture process goes
ahead of the slowest subscriber of the original Capture process. This wait timed out.
Action: Make sure the GoldenGate, XStream or Streams Apply process still works
properly.
ORA-26884: Not allowed to specify OCI_LCR_ROW_COLVAL_OLD with
OCILCR_NEW_ONLY_MODE.
Cause: An attempt was made to call OCILCRRowColumnInfoGet function with
OCI_LCR_ROW_COLVAL_OLD and OCILCR_NEW_ONLY_MODE.
Action: Change OCI_LCR_ROW_COLVAL_OLD to OCI_LCR_ROW_COLVAL_NEW
or remove OCILCR_NEW_ONLY_MODE argument.
ORA-26885: OCIXStreamInCommit called before OCIXStreamInFlush
Cause: An attempt was made to call OCIXStreamInCommit before calling
OCIXStreamInFlush.
Action: Call OCIXStreamInFlush prior to calling OCIXStreamInCommit.
ORA-26886: LCR commit position ('string') must be greater than the applied high
position of the XStream inbound server (position='string').
Cause: The position of the commit LCR was less than or equal to the applied high
postion of the XStream inbound server.
Action: Set the commit position higher than the applied high position.
ORA-26887: Insufficient privileges to attach to XStream inbound server "string".
Cause: Sufficient privileges were not granted to attach to the specified XStream
inbound server.
Action: Query DBA_XSTREAM_INBOUND view to get the apply_user value for the
specified XStream outbound server. Then, modify the application to connect to the
inbound server's database using this value.
ORA-26888: Redo compatibilty must be 10.2 or greater
Cause: XStream Out requires redo comptibility to be 10.2 or greater.
Action: Drop the outbound server.
ORA-26889: LOB assembly not supported for PDML parent transaction string, child
transaction string.
Cause: LOB assembly is not supported for PDML transactions.
Action: Disable LOB assembly, or filter out the PDML transaction.
ORA-24280 to ORA-28709 72-103
ORA-26890: Invalid update LCR on Oracle Sequence "string"."string"

Cause: The new value column list of an update LCR on an Oracle Sequence did not
have non-null columns "CYCLE#", "INCREMENT$", "CACHE" and "HIGHWATER".
Action: Make sure the new value column list has all the required columns. This might
be a user error if the LCR is from an XStream In client.
ORA-26891: Target Oracle Sequence "string"."string" has inconsistent parameters
with the source.
Cause: The source and target Oracle Sequences did not have the identical cache size,
increment value, and cycle flag needed for replication purposes.
Action: Make sure the source and target Oracle Sequences have identical parameters.
This might be a user error if the LCR is from an XStream In client.
ORA-26892: XStream feature not supported
Cause: The XStream feature was not supported.
Action: No action necessary.
ORA-26893: Input LCR must be a commit LCR
Cause: The input LCR was not a commit LCR.
Action: Make sure the input LCR is a commit LCR.
ORA-26894: Invalid "string" in Apply Progress redo
Cause: The value of the field reported was possibly corrupted.
ORA-26895: Setting parameter "string" of Streams process "string" is only permitted
for Oracle GoldenGate or XStream.
Cause: An attempt was made to set a parameter that is only allowed for XStream.
Action: Oracle GoldenGate license is needed to use this parameter.
ORA-26896: Attempted to connect multiple Oracle GoldenGate Capture processes,
including "string", with XStream outbound server "string" through queue
"string"."string"
Cause: An attempt was made to connect multiple Oracle GoldenGate Capture
processes through a queue with the XStream outbound server.
Action: Each XStream outbound server can only connect with one co-located Capture
process. Remove extra Capture processes.
ORA-26897: Unable to start string capture "string" because its subscribers "string"
and "string" have different purpose
Cause: An attempt was made to start an Oracle Capture process but it failed to start
because its subscribers had conflicting purpose.
Action: Remove one of the specified subscribers from the capture queue.
ORA-26898: Unable to create "string" because there is an Oracle Capture process
using the same queue "string"."string"
Cause: An attempt was made to create an inbound server using the same queue that
was used by an Oracle Capture process.
Action: Resubmit the statement using another queue name.
ORA-26899: internal string error

Cause: An internal Streams, XStream or GoldenGate error has occurred.
ORA-26900: Streams failed to update data dictionary table for propagation "string"
from capture "string" to apply "string".
Cause: The data dictionary table was corrupted.
Action: Validate the data dictionary table to restart GoldenGate, XStream or Streams
capture process.
ORA-26901: string propagation sender in the combined capture and apply mode is
to be suspended while apply is disabled.
Cause: The corresponding subscriber was dropped or split.
ORA-26902: string propagation sender in the combined capture and apply mode is
to be suspended while apply is enabled.
Cause: The corresponding subscriber was dropped or split.
ORA-26903: Invalid edition name "string"
Cause: The edition associated with the LCR did not exist in the destination database.
Action: Check if the edition needs to be created manually on the destination database
or if the CREATE EDITION statement for this edition has been applied properly on
the destination database.
ORA-26904: Invalid bind variable "string" in LCR field expression.
Cause: In the statement handler, the bind variables listed in the SQL expression did
not match the allowed Logical Change Record field names.
Action: Verify that all the bind variables listed in the expression are legal Logical
Change Record fields.
ORA-26905: Invalid LCR method expression "string" in statement handler.
Cause: The Logical Change Record method listed was not allowed in the statement
handler.
Action: Verify that the Logical Change Record method listed in the expression is a
legal DBMS_LCR method.
ORA-26906: No change handler exists.
Cause: There was no change handler for the specified apply, operation, source table,
change table, and capture values.
Action: Query DBA_APPLY_CHANGE_HANDLERS view to find the correct change
handler.
ORA-26907: Insufficient privileges to set converge tag
Cause: Privileges were insufficient to set converge tag.
Action: The invoker needs EXECUTE_CATALOG_ROLE or execute privilege on
DBMS_STREAMS_ADM to set converge tag. Grant appropriate privileges to the
invoker.
ORA-24280 to ORA-28709 72-105
ORA-26908: XStream API must be executed using a dedicated server process.

Cause: An attempt was made to execute XStream API using a shared server process.
Action: Replace the connect string in the client application to use a dedicated server
process.
ORA-26909: cannot reexecute an eager error
Cause: An attempt was made to reexecute an eager error transaction. An eager
transaction is applied before the apply process sees the commit or rollback for the
transaction.
Action: Fix the cause of the eager error and restart the apply process. When apply is
restarted, capture will automatically resend the transaction, and the transaction will
be applied by the apply process.
ORA-26910: user error string encountered in eager mode
Cause: An error was encountered during eager apply. An eager transaction is applied
before the apply process sees the commit or rollback for the transaction. If an error
occurs during an eager transaction, the transaction will be rolled back.
Action: Query the DBA_APPLY_ERROR view to determine the error and take the
appropriate action. The apply process will need to be restarted to apply the
transaction that had the error. When apply is restarted, capture will automatically
resend the transaction, and the transaction will be applied by the apply process.
ORA-26911: invalid oldest position (current position=string; new position=string)
Cause: An attempt was made to set the oldest position to a value that was less than
the current value.
Action: Correct the oldest_position argument in OCIXStreamOutProcessedLWMSet2
call.
ORA-26912: not allowed to invoke 'string' while in committed data-only mode
Cause: An attempt was made to call the specified API while the attached XStream
server was in committed data-only mode.
Action: Perform one of the following: 1) If the invalid call is
OCIXStreamOutProcessedLWMSet2, then change it to
OCIXStreamOutProcessedLWMSet or pass a null oldest_position to
OCIXStreamOutProcessedLWMSet2 call. 2) If the invalid call is
OCIXStreamInProcessedLWMGet2, then change it to
OCIXStreamInProcessedLWMGet or pass a null oldest_position to
OCIXStreamInProcessedLWMGet2 call.
ORA-26913: must connect to instance string where string string server "string" is
running
Cause: The client application was not connected to the same Oracle RAC instance as
the specified Oracle GoldenGate or XStream server.
Action: Connect to the specified instance using the network service name obtained
from the following query: SELECT network_name FROM all_queues q,
all_xstream_outbound ob WHERE q.owner = ob.queue_owner AND q.name =
ob.queue_name AND server_name = '<server_name>';
ORA-26914: Unable to communicate with string capture process "string" from
outbound server "string".
Cause: Capture process might not haven been started properly or was aborted.
Action: If Oracle GoldenGate or XStream capture process was stopped, then restart
the capture process. Otherwise, query the DBA_CAPTURE view to determine the
reason and take the appropriate action. If the error is ORA-4031, either increase the
initialization parameter STREAMS_POOL_SIZE or increase the capture parameter
MAX_SGA_SIZE or increase both. Refer to the XStream documentation for additional
information on these parameters.
ORA-26915: Unable to return Logical Change Record (LCR) information due to
missing data dictionary.
Cause: The current session was unable to return the requested information on the
given LCR due to missing dictionary data on that LCR.
Action: Detach and reattach the XStream outbound server. Then retry the current call.
ORA-26916: Must call OCIPOGGRedoLogOpen function before
OCIPOGGRedoLogRead
Cause: An attempt was made to call OCIPOGGRedoLogRead before calling
OCIPOGGRedoLogOpen.
Action: Add OCIPOGGRedoLogOpen call before OCIPOGGRedoLogRead.
ORA-26917: OCIPOGG API must be executed using a dedicated server process.
Cause: An attempt was made to execute OCIPOGG API using a shared server
process.
process.
ORA-26918: Must use 'string' procedure for outbound server "string".
Cause: An attempt was made to execute START_APPLY on an outbound server that
uses uncommitted data mode.
Action: Use the specified procedure instead.
ORA-26919: Capture "string" is not associated with queue "string"."string".
Cause: The capture specified in the ADD_OUTBOUND procedure was not associated
with the specified queue.
Action: Resubmit the ADD_OUTBOUND procedure after removing either the
capture_name or the queue_name argument.
ORA-26920: string outbound server "string" has been stopped.
Cause: The specified outbound server was stopped.
Action: Execute START_OUTBOUND procedure to restart the outbound server or
execute OCIXStreamOutAttach function to reattach to the outbound server.
ORA-26921: Cannot alter the start SCN or time of string Capture "string".
Cause: An attempt was made to alter the start SCN or time for a capture while other
outbound servers were still attached to it.
Action: Execute the following: 1) Get the names of other outbound servers currently
attached to the specified Capture using the query: SELECT server_name FROM
dba_xstream_outbound WHERE (status = 'ATTACHED') AND (server_name
'<altered_server>') AND (capture_name = '<specified_capture_name>'); 2) Detach the
client application from each server_name returned. 3) Retry the operation.
ORA-24280 to ORA-28709 72-107
ORA-26922: user string does not have LOGMINING privilege

Cause: An attempt was made to start the capture process or attach to an outbound
server when the specified user did not have LOGMINING privilege.
Action: Grant LOGMINING privilege to the specified user and resubmit the failed
operation.
ORA-26923: cannot configure string outbound server "string" with string capture
"string" due to different purpose
Cause: An attempt was made to configure an outbound server with a capture used for
different purpose.
Action: Execute the following: 1) Get the purpose of each capture and its associated
queue: SELECT capture_name, queue_owner, queue_name, purpose FROM
dba_capture; 2) Resubmit the statement using a queue or capture with the same
purpose.
ORA-26924: cannot configure string using "string"."string" queue because it is used
by "string" for string purpose
Cause: An attempt was made to configure the specified process using a queue already
used by another process for different purpose.
Action: Resubmit the statement using another queue of the same purpose.
ORA-26925: cannot configure outbound server "string" with capture "string"
because it is not using apply-state checkpoint
Cause: An attempt was made to configure an outbound server with a capture not
using apply-state checkpoint.
Action: Specify a different capture in the ADD_OUTBOUND procedure or re-create
the capture and resubmit the statement.
ORA-26926: Unable to attach because capture "string" is missing dictionary redo
logs
Cause: The specified capture was unable to locate the dictionary redo log.
Action: Check the state of the specified capture from gv$streams_capture to
determine the SCN or filename of the missing log file. Confirm that the filename
exists and is accessible online and also in the DBA_REGISTERED_ARCHIVED_LOG
view. In addition, for local capture, confirm that an entry exists for the file in the V
$ARCHIVED_LOG view. If an entry is missing, it can be added using the ALTER
DATABASE REGISTER .... LOGFILE command, specifying the keyword LOGICAL
LOGFILE or PHYSICAL LOGFILE as appropriate.
ORA-26927: Unable to communicate with string capture process "string" from
outbound server "string".
Cause: A timeout occurred while waiting for capture to respond.
Action: Check the state of the specified capture from GV$XSTREAM_CAPTURE
view. Determine the reason for capture's unresponsiveness. If streams_pool_size is
not set or set with an inadequate value, consider setting or increasing the value of this
parameter.
ORA-26928: Unable to communicate with string apply coordinator process "string"
from outbound server "string".
Cause: A timeout occurred while waiting for apply coordinator to respond.
Action: Check the state of the specified apply coordinator from GV
$STREAMS_APPLY_COORDINATOR view. Determine the reason for apply
coordinator's unresponsiveness. If streams_pool_size is not set or set with an

inadequate value, consider setting or increasing the value of this parameter.
ORA-26929: altering an outbound server with a remote capture is not allowed
Cause: An attempt was made to alter an outbound server with a remote capture.
Action: None
ORA-26930: User "string" does not have privileges to perform this operation
Cause: An attempt was made to create, alter, or drop a process that has a different
user (such as capture user or apply user) than the invoking user.
Action: Use the DBMS_XSTREAM_AUTH.GRANT_ADMIN_PRIVILEGE or
DBMS_GOLDENGATE_AUTH.GRANT_ADMIN_PRIVILEGE procedures to grant
the invoking user proper privileges.
ORA-26931: This procedure can only be invoked from the root container.
Cause: An attempt was made to create an outbound server in non-root PDB.
Action: Create the outbound server from the root container.
ORA-26932: Streams configuration is not allowed in a container database.
Cause: An attempt was made to configure a Streams environment in a container
database.
Action: None
ORA-26933: Cannot start Streams process "string" while in a container database.
Cause: An attempt was made to start the specified Streams process while in a
container database.
Action: None
ORA-26934: Streams synchronous capture is not supported in a container database.
Cause: An attempt was made to perform a DML operation on a table being captured
by a Streams synchronous capture in a container database.
Action: Remove all Streams synchronous captures then reexecute the DML operation.
ORA-26935: Unsupported type string.string for parameter for procedure
string.string.string.\n
Cause: Apply encountered a procedure call with a parameter with an unsupported
type.
Action: Modify the rules to filter out the procedure call.
ORA-26936: must execute OCIPOGGCaptureAttach before invoking string
function
OCIPOGGCaptureAttach call.
Action: Add OCIPOGGCaptureAttach call before the specified function.
ORA-26937: client has already attached to string capture "string".
Cause: The client was already attached to the specified capture.
Action: Detach from the specified capture before reattaching.
ORA-24280 to ORA-28709 72-109
ORA-26938: cannot pack LCR into LCR buffer (buffer size is string, LCR size is
string)
Cause: The logical change record (LCR) buffer was not large enough to store the
current LCR.
Action: Increase the buffer size in the OCIPOGGCaptureAttach call.
ORA-26939: string capture "string" is disabled.
Cause: The capture process was disabled or aborted.
Action: Start the capture process.
ORA-26940: OCIPOGGCapture API must be executed using a dedicated server
process.
Cause: An attempt was made to execute OCIPOGGCapture API using a shared server
process.
process.
ORA-26941: unable to perform LOB assembly for table string.string
Cause: The apply process was unable to perform the LOB assembly for a DML for the
specified table.
Action: Verify that the storage type for the columns are compatible at the source and
destination.
ORA-26942: LCR should not contain old value for column string in table
string.string
Cause: The LCR contained old values for LOB, XMLType and object columns.
Action: Remove old values for any LOB, XMLType and object columns in the LCR.
ORA-26943: cross PDB operation not allowed
Cause: An attempt was made to perform an operation on a container database
different from the container database where the call was made.
Action: Log into the root container or into the container where you want to perform
the requested action.
ORA-26944: User "string" attempted to invoke a procedure without proper
permissions.
Cause: An attempt was made to invoke a procedure without proper permissions.
Action: Use the DBMS_GOLDENGATE_AUTH.GRANT_ADMIN_PRIVILEGE to
grant the invoking user proper privileges.
ORA-26945: unsupported hint string
Cause: The specified hint was not supported.
Action: Remove the hint from the SQL statement.
ORA-26946: OCIPOGGRedoLog API not supported in CDB.
Cause: An attempt was made to call an OCIPOGGRedoLog API in a multitenant
container database (CDB).
Action: Do not call the OCIPOGGRedoLog API in a CDB.
ORA-26947: Oracle GoldenGate replication is not enabled.
Cause: The 'enable_goldengate_replication' parameter was not set to 'true'.
Action: Set the 'enable_goldengate_replication' parameter to 'true' and retry the

operation. Oracle GoldenGate license is needed to use this parameter.
ORA-26948: Streams API must be executed using a dedicated server process.
Cause: The dblink configured for the propagation from the capture queue to the
apply queue is using a shared server connection.
Action: Modify the dblink for this propagation to use a dedicated server connection.
ORA-26949: Advanced Replication is not allowed in a container database.
Cause: An attempt was made to configure an advanced replication in a multitenant
container database (CDB).
Action: Do not call the Advanced Replication API in a CDB.
ORA-26951: table "string"."string" has column data type not supported by conflict
resolution
Cause: A conflict was detected, but unsupported columns prevented resolving the
conflict.
Action: Remove conflict resolution configuration for tables with LOB, LONG, XML,
object, or extended types.
ORA-26952: could not clone from the specified clone_capture_name string while
creating capture process string
Cause: The specified clone_capture_name could not be used as a clone candidate
while creating the capture process.
Action: Re-create the capture without setting clone_capture_name.
ORA-27000: skgfqsbi: failed to initialize storage subsystem (SBT) layer
Cause: sbtinit returned an error, additional information indicates error
Action: verify that vendor's storage subsystem product is operating correctly
ORA-27001: unsupported device type
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: internal error, aditional information indicates which function encountered
error
Action: check for trace file and contact Oracle Support
ORA-27003: cannot open file on device allocated with NOIO option
Cause: internal error, a file is being created/retrieved on a device allocated with
NOIO option, additional information indicates which function encountered error
ORA-27004: invalid blocksize specified
Cause: internal error, blocksize specified is incorrect for the device on which file is
being created, aditional information indicates blocksize specified, and the function
that encountered the error
ORA-24280 to ORA-28709 72-111
ORA-27005: cannot open file for async I/O on device not supporting async
Cause: internal error, a file is being opened for async I/O on a device that does not
support async I/O, additional information indicates which function encountered
error
ORA-27006: sbtremove returned error
Cause: additional information indicates error returned by sbtremove, and the
function that encountered the error
ORA-27007: failed to open file
Cause: sbtopen returned error, additional information indicates error returned from
sbtopen, and the function that encountered the error
ORA-27008: function called with invalid file structure
error
ORA-27009: cannot write to file opened for read
ORA-27010: skgfwrt: write to file failed
Cause: sbtwrite returned error, additional information indicates error returned from
sbtwrite
ORA-27011: skgfrd: cannot read from file opened for write
ORA-27012: skgfrd: read from file failed
Cause: sbtread returned error, additional information indicates error returned from
sbtread
ORA-27013: skgfqdel: cannot delete an open file
ORA-27014: skgfqpini: translation error while expanding SS_UDMPDIR
Cause: Failure of sltln in skgfqpini
ORA-27015: skgfcls: failed to close the file
Cause: sbtclose returned error, additional information indicates error returned from
sbtclose
ORA-27016: skgfcls: sbtinfo returned error

Cause: additional information indicates error returned from sbtinfo
ORA-27017: skgfcls: media handle returned by sbtinfo exceeds max
length(SSTMXQMH)
Cause: media handle string length exceeds SSTMXQMH
Action: verify that vendor's storage subsystem product is operating correctly, and that
the platform limit (SSTMXQMH) is atleast 64 (the limit specified for sbtinfo).
additional information indicates the media handle string length returned by sbtinfo,
and the limit (SSTMXQMH)
ORA-27018: BLKSIZE is not a multiple of the minimum physical block size
Cause: User-specified BLKSIZE (blocking factor) is not a multiple of the minimum
block size that is permitted on this platform.
Action: Two ADDITIONAL INFORMATION messages are displayed which show the
blocking factor provided by the user and the minimum physical block size. Specify a
BLKSIZE that is an integral multiple of the minimum block size.
ORA-27019: tape filename length exceeds limit (SBTOPMXF)
Cause: length of tape filename provided to sequential I/O OSD functions is too long
Action: additional information indicates in which function this error is encountered,
the length of filename provided, and the limit on filename
ORA-27020: named devices not supported
Cause: the platform or the specified device type does not support named devices
Action: do not specify device name or use a device type that supports named devices.
Use 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 filename which will be passed to sbtopen was not specified.
Action: Specify a filename and continue. If this is a backup set being created via
Recovery Manager, use the 'format' option to specify the backup piece handle name.
ORA-27022: skgfqsbi: could not allocate memory for media manager
Cause: Oracle could not allocate memory required by the media management
software which is linked with Oracle to provide backup/restore services.
Action: Increase the amount of memory available to the Oracle process and retry the
backup/restore.
ORA-27023: skgfqsbi: media manager protocol error
Cause: The media management software which is linked with Oracle to provide
backup/restore services did not provide its function pointer structure to Oracle.
Action: This is an internal error in the media management product. Contact the media
management vendor.
ORA-27024: skgfqsbi: sbtinit2 returned error
Cause: sbtinit2 returned an error. This happens during a backup or restore operation.
Action: This error is returned from the media management software which is linked
with Oracle. There should be additional messages which explain the cause of the
error. This error usually requires contacting the media management vendor.
ORA-24280 to ORA-28709 72-113
ORA-27025: skgfqsbi: invalid media manager context area size

Cause: The media management software requested a context area size which is
greater than the maximum allowable size.
management vendor.
ORA-27026: skgfrls: sbtend returned error
Cause: sbtend returned an error. This happens during a backup or restore operation.
ORA-27027: sbtremove2 returned error
Cause: sbtremove2 returned an error. This happens when deleting a backup file.
ORA-27028: skgfqcre: sbtbackup returned error
Cause: sbtbackup returned an error. This happens when creating a backup file during
a backup operation.
ORA-27029: skgfrtrv: sbtrestore returned error
Cause: sbtrestore returned an error. This happens when retrieving a backup file
during a restore operation.
ORA-27030: skgfwrt: sbtwrite2 returned error
Cause: sbtwrite2 returned an error. This happens while writing a backup file during a
backup operation.
ORA-27031: mirror resilvering functions not supported
ORA-27032: failed to obtain file size limit
Cause: getrlimit system call returned an error
Action: check errno
ORA-27033: failed to obtain file size limit
Cause: ulimit system call returned an error
Action: check errno
ORA-27034: maximum length of ORACLE_SID exceeded

Cause: too many characters in the ORACLE_SID string
Action: rename the 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: logical block size for oracle files must be a multiple of the physical block size,
and less than the maximum
Action: block size specified is returned as additional information, check init.ora
parameters, additional information also indicates which function encountered the
error
ORA-27036: translation error, unable to expand file name
Cause: additional information indicates sltln/slnrm error, and also indicates which
function encountered the error
Action: check additional information
ORA-27037: unable to obtain file status
Cause: stat system call returned an error, additional information indicates which
Action: check errno
ORA-27038: created file already exists
Cause: trying to create a database file, but file by that name already exists
Action: verify that name is correct, specify reuse if necessary
ORA-27039: create file failed, file size limit reached
Cause: an attempt was made to create a file that exceeds the process's file size limit,
additional information indicates which function encountered the error
Action: raise the file size limit
ORA-27040: file create error, unable to create file
Cause: create system call returned an error, unable to create file
Action: verify filename, and permissions
ORA-27041: unable to open file
Cause: open system call returned an error, additional information indicates which
Action: check errno
ORA-27042: not enough space on raw partition to fullfill request
Cause: internal error, file too large for raw partition, additional information indicates
which function encountered the error
ORA-27043: unable to seek to beginning of file
Cause: seek system call failed, additional information indicates which function
encountered the error
Action: check errno
ORA-24280 to ORA-28709 72-115
ORA-27044: unable to write the header block of file

Cause: write system call failed, additional information indicates which function
Action: check errno
ORA-27045: unable to close the file
Cause: close system call failed, additional information indicates which function
Action: check errno
ORA-27046: file size is not a multiple of logical block size
Cause: file size as indicated by stat is not correct, additional information indicates
which function encountered the error
Action: verify that the file has not been overwritten or truncated
ORA-27047: unable to read the header block of file
Cause: read system call failed, additional information indicates which function
Action: check errno
ORA-27048: skgfifi: file header information is invalid
Cause: possibly trying to use a non-database file as a database file
Action: verify that file is a database file
ORA-27049: unable to seek to and read the last block
Cause: an attempt was made to seek to and read the last block in file, additional
information indicates which function encountered error
Action: check errno
ORA-27050: function called with invalid FIB/IOV structure
error
ORA-27052: unable to flush file data
Cause: fsync system call returned error, additional information indicates which
Action: check errno
ORA-27053: blocksize in file header not a multiple of logical block size
Cause: the logical block size is invalid, additional information indicates the logical
block size and the blocksize in the file header
Action: use a different logical block size, or do not reuse file
ORA-27054: NFS file system where the file is created or resides is not mounted
with correct options
Cause: The file was on an NFS partition and either reading the mount tab file failed or
the partition wass not mounted with the correct mount option.
Action: Make sure mount tab file has read access for Oracle user and the NFS
partition where the file resides is mounted correctly. For the list of mount options to
use refer to your platform specific documentation.
ORA-27056: could not delete file

Cause: unlink system call returned error
Action: check errno
ORA-27057: cannot perform async I/O to file
Cause: internal error, query is being asked about async vector I/O when the file does
not support async I/O
ORA-27058: file I/O question parameter is invalid
Cause: internal error, invalid query is being asked
ORA-27059: could not reduce file size
Cause: ftruncate system call returned error
Action: check errno
ORA-27060: could not set close-on-exec bit on file
Cause: fcntl system call returned error
Action: check errno
ORA-27061: waiting for async I/Os failed
Cause: aiowait function returned error
Action: check errno
ORA-27062: could not find pending async I/Os
Cause: There should have been some async I/Os in the system but a blocking aiowait
indicates that there are no more I/Os. It could be either because of an Oracle bug or
the vendor OS bug or due to a NFS server not responding
Action: check Oracle trace file, OS message files and contact Oracle Support
ORA-27063: number of bytes read/written is incorrect
Cause: the number of bytes read/written as returned by aiowait does not match the
original number, additional information indicates both these numbers
Action: check errno
ORA-27064: cannot perform async I/O to file
Cause: internal error, asked to perform async I/O when IOV indicates that it cannot
be performed on the file
ORA-27065: cannot perform async vector I/O to file
Cause: internal error, asked to perform async vector I/O when it cannot be performed
on the file
ORA-27066: number of buffers in vector I/O exceeds maximum
Cause: internal error, number of buffers in vector I/O exceeds maximum allowed by
the OSD, additional information indicates both these numbers
ORA-24280 to ORA-28709 72-117
ORA-27067: size of I/O buffer is invalid

Cause: internal error, buffer size is either 0, or greater than SSTIOMAX or not a
multiple of logical block size, additional information indicates where in function the
error was encountered and the buffer size
ORA-27068: I/O buffer is not aligned properly
Cause: internal error, buffer is not aligned to SSIOALIGN boundary, additional
information indicates where in function the error was encountered and the buffer
pointer
ORA-27069: attempt to do I/O beyond the range of the file
Cause: internal error, the range of blocks being read or written is outside the range of
the file, additional information indicates the starting block number, number of blocks
in I/O, and the last valid block in the file
ORA-27070: async read/write failed
Cause: aioread/aiowrite system call returned error, additional information indicates
starting block number of I/O
Action: check errno
ORA-27071: unable to seek to desired position in file
Cause: lseek system call returned error, additional information indicates block
number in file to which seek was attempted
Action: check errno
ORA-27072: File I/O error
Cause: read/write/readv/writev system call returned error, additional information
indicates starting block number of I/O
Action: check errno
ORA-27073: Trying to close a file which has async I/Os pending to be dequeued
Cause: internal error, the file is being closed but not all async I/Os to the file have
been dequeued, additional information indicates number of I/Os pending on the file
ORA-27074: unable to determine limit for open files
Cause: The getrlimit() system call returned an error.
ORA-27075: SSTMOFRC constant too large
ORA-27076: unable to set limit for open files
Cause: The setrlimit() system call returned an error.
ORA-27077: too many files open

Cause: internal error, the number of files opened through skgfofi has reached the limit
Action: Check for trace file and contact Oracle Support.
ORA-27078: unable to determine limit for open files
Cause: The getrlimit() system call returned an error.
ORA-27079: unable to set async IO limit
Cause: The setting of the limit for async I/O has failed.
ORA-27080: too many files open
Cause: The number of files opened has reached the system limit.
Action: Check the error, and set system configuration values.
ORA-27081: unable to close the file
Cause: The close() system call failed.
ORA-27083: waiting for async I/Os failed
Cause: The aio_waitn() library call returned an error.
ORA-27084: unable to get/set file status flags
Cause: The fcntl() system call with F_GETFL/F_SETFL flag returned an error.
ORA-27086: unable to lock file - already in use
Cause: the file is locked by another process, indicating that it is currently in use by a
database instance.
Action: determine which database instance legitimately owns this file.
ORA-27087: unable to get share lock - file not readable
Cause: share lock request was made on a file not open for read access.
Action: file must be open read-only or read-write to get a share lock.
ORA-27088: unable to get file status
Cause: file not open or file descriptor is invalid.
Action: n/a
ORA-27089: unable to release advisory lock
Cause: release of file lock failed
Action: see errno
ORA-27090: Unable to reserve kernel resources for asynchronous disk I/O
Cause: The system call to reserve kernel resources for asynchronous I/O has failed.
Action: Check errno
ORA-24280 to ORA-28709 72-119
ORA-27091: unable to queue I/O

Cause: read/write/readv/writev system call returned error, additional information
indicates starting block number of I/O
Action: check errno
ORA-27092: size of file exceeds file size limit of the process
Cause: an attempt was made to open a file that exceeds the process's file size limit
(ulimit), additional information shows the current limit (logical blocks) and the size of
the file (logical blocks)
Action: increase the processes file size limit (ulimit) and retry
ORA-27093: could not delete directory
Cause: rmdir system call returned error
Action: check errno
ORA-27094: raw volume used can damage partition table
Cause: A raw device with VTOC information was provided as a database file.
Action: Make sure the disk partition that is provided to Oracle does not start at sector
0
ORA-27095: fail to get the disk sector size
Cause: The system call to get the sector size failed. Additional information indicates
which function encountered the error.
Action: Check error number.
ORA-27096: fail to get file size
Cause: The system call to get file size failed. Additional information indicates which
function encountered the error.
Action: Check error number.
ORA-27097: failed to set Access Control List ownership for ASM devices
Cause: The system call to set ACL ownership for ASM devices failed. Additional
information indicates which function encountered the error.
Action: Refer to Microsoft documentation for an explanation of the accompanying
error code and text.
ORA-27098: failed to rename file
Cause: The system call to change the file name failed. Additional information
indicates which function encountered the error.
Action: Check the Oracle trace file for additional information on file name and reason
for failure.
ORA-27099: failed to create file
Cause: The system call to create this file type in this file system failed. Check if the
creation of this file type is supported in this file system. Additional information
indicates which function encountered the error.
Action: Refer to Oracle documentation for additional details.
ORA-27100: shared memory realm already exists
Cause: Tried to start duplicate instances, or tried to restart an instance that had not
been properly shutdown
Action: Use a different instance name, or cleanup the failed instance's SGA
ORA-27101: shared memory realm does not exist
Cause: Unable to locate shared memory realm
Action: Verify that the realm is accessible
Cause: Out of memory
Action: Consult the trace file for details
ORA-27103: internal error
ORA-27104: system-defined limits for shared memory was misconfigured
Cause: System-defined shared memory limits were inadequate for Oracle.
ORA-27105: unable to support any system page size for shared memory allocation
Cause: Current configuration was not supported by any system page size.
ORA-27106: system pages not available to allocate memory
Cause: System page count for supported page sizes was misconfigured.
Action: Configure system page count as recommended in the alert file.
ORA-27107: AUTO value for USE_LARGE_PAGES parameter is no longer
supported
Cause: The USE_LARGE_PAGES configuration parameter was set to AUTO.
ORA-27120: unable to remove shared memory segment
Cause: shmctl() call failed
Action: check permissions on segment, contact Oracle support
ORA-27121: unable to determine size of shared memory segment
Cause: shmctl() call failed
ORA-27122: unable to protect memory
Cause: mprotect() call failed
ORA-27123: unable to attach to shared memory segment
Cause: shmat() call failed
ORA-27124: unable to detach from shared memory segment
Cause: shmdt() call failed
ORA-24280 to ORA-28709 72-121
ORA-27125: unable to create shared memory segment

Cause: shmget() call failed
ORA-27126: unable to lock shared memory segment in core
Cause: insufficient privileges to lock shared memory segment in core
Action: make sure process is running with necessary privileges.
ORA-27127: unable to unlock shared memory segment
Cause: insufficient privileges to unlock shared memory segment
Action: make sure process is running with necessary privileges.
ORA-27128: unable to determine pagesize
Cause: sysconf() call failed
ORA-27133: unable to determine stacksize
Cause: getrlimit() call failed
ORA-27134: unable to set stacksize
Cause: setrlimit() call failed
ORA-27135: Operating System hard stack limit is set too low
Cause: Operating System hard stack limit was set too low.
Action: Check additional information for current and minimum limit. Increase the
Operating System hard stack limit and retry.
ORA-27136: MPMT and VLM are both enabled
Cause: When the _mpmt_enabled parameter is set to TRUE, none of the following
parameters should be set to TRUE: * use_indirect_buffers * _db_block_cache_protect *
_db_block_cache_clone
Action: Either turn off Multi Process Multi Threads (MPMT) or turn off all the other
parameters.
ORA-27137: unable to allocate large pages to create a shared memory segment
Cause: Parameter USE_LARGE_PAGES set to only, but large pages were not
configured properly
Action: Check alert file for more information
ORA-27138: unable to allocate large pages with current parameter setting
Cause: With parameter USE_LARGE_PAGES set to only, none of the following
parameters can be set: * memory_target/memory_max_target *
_db_block_cache_protect * use_indirect_data_buffers
Action: Either turn off the USE_LARGE_PAGES parameter setting, or turn off all the
other parameters. Large pages are compatible with sga_target, sga_max_size and
shared_pool_size.
ORA-27139: unable to reserve Oracle VM mapping in process address space
Cause: The address space region was already mapped.

ORA-27140: attach to post/wait facility failed
Cause: The program attempted to initialize the post/wait facility, but the facility
could not be attached.
Action: Check for additional errors and contact Oracle Support.
ORA-27141: invalid process ID
Cause: process operation attempted using invalid process ID
ORA-27142: could not create new process
Cause: OS system call
Action: check errno and if possible increase the number of processes
ORA-27143: OS system call failure
Cause: OS system call failed
Action: check errno and contact Oracle support
ORA-27144: attempt to kill process failed
Action: check errno and contact Oracle Support
ORA-27145: insufficient resources for requested number of processes
ORA-27146: post/wait initialization failed
ORA-27147: post/wait reset failed
ORA-27148: spawn wait error
ORA-27149: assignment out of range
Cause: internal error, requested conversion too large for type
ORA-27150: attempt to notify process of pending oradebug call failed
Cause: OS system call
Action: check errno contact Oracle Support
ORA-27151: buffer not large enough to hold process ID string
ORA-24280 to ORA-28709 72-123
ORA-27152: attempt to post process failed

ORA-27153: wait operation failed
Cause: OS system called failed
Action: check errno contact Oracle Support
ORA-27154: post/wait create failed
Cause: internal error, multiple post/wait creates attempted simultaneously
ORA-27155: could not execute file
ORA-27156: request for process information failed
ORA-27157: OS post/wait facility removed
Cause: the post/wait facility for which the calling process is awaiting action is
removed from the system
ORA-27158: process control failure
Cause: Oracle was unable to set the specified process control.
Action: Consult the Oracle Administrator's Guide.
ORA-27159: failure setting process scheduling priority
Cause: Oracle was unable to set the scheduling priority desired.
Action: Consult the Oracle Administrator's Guide.
ORA-27160: process requested to perform operation
Cause: The current process was requested to perform an operation by another
process.
Action: This is used internally; no action is required.
ORA-27161: request for Oracle binary information failed
Cause: The program was unable to get information about the Oracle binary.
Action: Check for additional errors and contact Oracle support.
ORA-27162: thread creation failed
Cause: The program was unable to create a thread.
Action: Check errno and contact Oracle support.
Cause: The program ran out of memory when allocating a temporary data structure.
Action: Increase the amount of memory on the system.
ORA-27164: tried to join detached thread

Cause: The program tried to join a detached thread.
Action: This is an internal error; contact Oracle support.
ORA-27165: tried to join thread that does not exist
Cause: The program tried to join a thread that does not exist.
ORA-27166: tried to join current thread
Cause: A thread in the program tried to join itself.
ORA-27168: Translation from hostname to network address failed
ORA-27170: Oracle RAC option of current Oracle binary differs from running
instance
Cause: The Oracle installation environment may have been modified while the
instance was running.
Action: Restore the environment to its original state when the instance was started or
shutdown (abort) and restart the instance.
ORA-27190: skgfrd: sbtread2 returned error
Cause: sbtread returned an error. This happens while reading a backup file during a
restore operation.
ORA-27191: sbtinfo2 returned error
Cause: sbtinfo2 returned an error. This happens while retrieving backup file
information from the media manager's catalog.
ORA-27192: skgfcls: sbtclose2 returned error - failed to close file
Cause: sbtclose2 returned an error. This happens while closing a backup file during a
backup or restore operation.
ORA-27193: sbtinfo2 did not return volume label
Cause: sbtinfo2 did not return the volume label information for the backup file that
was just created.
management vendor.
ORA-24280 to ORA-28709 72-125
ORA-27194: skgfdvcmd: sbtcommand returned error

Cause: sbtcommand returned an error. This happens when an rman SEND command
is issued.
ORA-27195: proxy copy not supported
Cause: An attempt was made to do a proxy backup or restore, but the media
management software installed with Oracle does not support proxy copy.
Action: Re-run the backup in non-proxy mode, or contact the media management
vendor if the software is supposed to support proxy copy.
ORA-27196: skgfpbk: sbtpcbackup returned error
Cause: sbtpcbackup returned an error. This happens when a proxy backup is begun.
ORA-27197: skgfprs: sbtpcrestore returned error
Cause: sbtpcrestore returned an error. This happens when a proxy restore is begun.
ORA-27198: skgfpvl: sbtpcvalidate returned error
Cause: sbtpcvalidate returned an error. This happens during a proxy backup or
restore.
ORA-27199: skgfpst: sbtpcstatus returned error
Cause: sbtpcstatus returned an error. This happens during a proxy backup or restore.
ORA-27200: skgfpgo: sbtpcstart returned error
Cause: sbtpcstart returned an error. This happens during a proxy backup or restore.
ORA-27201: skgfpcm: sbtpccommit returned error
Cause: sbtpccommit returned an error. This happens during a proxy backup or
restore.
ORA-27202: skgfpen: sbtpcend returned error

Cause: sbtpcend returned an error. This happens during a proxy backup or restore.
ORA-27203: skgfpqb: sbtpcquerybackup returned error
Cause: sbtpcquerybackup returned an error. This happens during a proxy backup.
ORA-27204: skgfpqr: sbtpcqueryrestore returned error
Cause: sbtpcqueryrestore returned an error. This happens during a proxy restore.
ORA-27205: skgfpcn: sbtpccancel returned error
Cause: sbtpccancel returned an error. This happens during a proxy restore.
ORA-27206: requested file not found in media management catalog
Cause: A backup file used in a recovery manager catalog maintenance command was
not found in the media management catalog.
Action: Retry the command with a different file.
ORA-27207: syntax error in device PARMS - parentheses mismatch or missing
Cause: User-supplied PARMS value has incorrect syntax.
Action: Retry the command with correct syntax: ENV=(..) BLKSIZE=nnnn
ORA-27208: syntax error in device PARMS - environment variable value missing
Action: Retry the command with correct syntax: ENV=(var1=val1,var2=val2,..)
ORA-27209: syntax error in device PARMS - unknown keyword or missing =
Cause: User-supplied PARMS value has incorrect syntax. The server expected to find
ENV or BLKSIZE, but found an unknown keyword.
ORA-27210: syntax error in device PARMS
ORA-27211: Failed to load Media Management Library
Cause: User-supplied SBT_LIBRARY or libobk.so could not be loaded. Call to dlopen
for media library returned error. See Additional information for error code.
Action: Retry the command with proper media library. Or re-install Media
management module for Oracle.
ORA-24280 to ORA-28709 72-127
ORA-27212: some entrypoints in Media Management Library are missing

Cause: media library does not have one of the following entrypoints : sbtinfo, sbtread,
sbtwrite, sbtremove, sbtopen, sbtclose, sbtinit
Action: Retry the command with proper media library.
ORA-27213: failed to unload Media Management Library
Cause: dlclose for media library returned error. See Additional Additional
information for error code.
Action: contact Oracle Support.
ORA-27214: skgfrsfe: file search failed
Cause: The FindNextFile function returned unxpected error.
Action: Check errors on the error stack for an explanation why the search for files
could not be successfully executed.
ORA-27215: skgfgsmcs: sbtinfo2 returned unknown file
Cause: During an sbtinfo2() call, the media management software returned
information about an unknown backup file.
Action: Contact the media management vendor.
ORA-27216: skgfgsmcs: sbtinfo2 returned a malformed response
Cause: The media management software returned a malformed response during an
sbtinfo2() call.
Action: Contact the media management vendor.
ORA-27217: failed to load Media Management Library from secure location
Cause: SBT libraries were not installed in a secure location.
Action: Remove SBT_SECURE parameter or Request third party vendors to provide
patch that installs SBT libraries in secured locations as mandated by Oracle.
ORA-27218: failed to read ACFS mirror
Cause: An attempt to communicate with the Oracle Automatic Storage Management
Cluster File System (Oracle ACFS) kernel driver failed.
Action: Check errors on the error stack for an explanation of why communication
with ACFS was not successful.
ORA-27231: unable to close file
Cause: A file could not be closed.
ORA-27232: unable to get file information
Cause: Information about the file could not be obtained.
ORA-27233: file is not an ELF file
Cause: A file was not an ELF file.
Action: Check for file corruption and contact Oracle Support Services.
ORA-27234: unable to read file

Cause: A file could not be read.
ORA-27235: unable to map file region into memory
Cause: A file region could not be mapped into memory.
ORA-27236: unable to unmap file from memory
Cause: A file region could not be unmapped from memory.
ORA-27237: ELF file is not a relocatable object file
Cause: An ELF file was not the expected type.
Action: Supply the expected type of file.
ORA-27238: ELF file is not an executable
ORA-27239: ELF file is not a shared object file
ORA-27240: ELF file does not have a required section
Cause: An ELF file did not have a required section.
ORA-27241: ELF-shared library has multiple sections of the same type
Cause: An ELF-shared library had multiple sections of the same type.
ORA-27242: ELF file has invalid hash table entry size
Cause: An ELF file had an invalid hash table entry size.
ORA-27243: ELF file has too many relocation sections
Cause: An ELF file had too many relocation sections.
ORA-27244: unable to determine base value for data relocation from ELF file
Cause: An ELF file was missing important information.
ORA-27245: unable to dlopen() binary image
Cause: A file could not be accessed via dlopen().
Action: See accompanying errors and make file available.
ORA-27246: unable to open file
Cause: A file could not be opened.
ORA-24280 to ORA-28709 72-129
Action: See accompanying errors and make file available.

ORA-27270: szingroup: malloc failed
Cause: The malloc library call failed to allocate space for a group list.
Action: This is possibly an operating system error. Contact Oracle Support Services.
ORA-27271: szingroup: group lookup failure
Cause: The 'getgrnam_r' library call failed to determine the members of a UNIX
group.
ORA-27300: OS system dependent operation:string failed with status: string
ORA-27301: OS failure message: string
ORA-27302: failure occurred at: string
ORA-27303: additional information: string
ORA-27351: conflicting values of job attributes string and string
Cause: The values of two attributes passed in to the CREATE_JOBS call or the JOB
object constructor conflicted with each other. This is usually because both attributes
cannot be non-NULL at the same time.
Action: Resolve the conflict by changing the value of one of the attributes and issue
the call again.
ORA-27353: job attribute string is missing
Cause: An attribute needed to fully specify a job was not passed in to a call to
CREATE_JOBS or the JOB object constructor.
Action: Issue the call again with the required attribute set.
ORA-27354: attribute string cannot be set for lightweight jobs
Cause: The CREATE_JOBS call or the JOB object constructor was called with an
argument that is illegal in the case of lightweight jobs.
Action: Set the argument to the default value and issue the call again.
ORA-27356: invalid job argument
Cause: An invalid job argument was passed into either the CREATE_JOBS call or the
JOB object constructor.
Action: Correct the argument value and issue the call again.
ORA-27357: duplicate reference to job object string
Cause: The scheduler CREATE_JOBS call had two or more references to the same job.
Action: Eliminate the duplicate references and issue the call again.
ORA-27359: duplicate reference to attribute string of job string
Cause: The scheduler SET_JOB_ATTRIBUTES call had two or more references to a
specific atrribute of a job.
Action: Eliminate the duplicate references and issue the call again.
ORA-27361: scheduler API invoked with illegal or inconsistent arguments
Cause: A DBMS_SCHEDULER API call was invoked with either illegal or
inconsistent arguments.
Action: Refer to scheduler documentation for the call, make the necessary changes
and issue the call again.
ORA-27362: batch API call completed with errors
Cause: Some of the commands submitted to a scheduler batch API call could not be
successfully carried out because of errors. Other commands in the batch may have
Action: Check the view SCHEDULER_JOB_ERRORS to see which commands failed
and why. Make the appropriate corrections and submit the failed commands again.
ORA-27363: invalid program for lightweight job
Cause: You tried to create a lightweight job using an invalid program. A program
used in a lightweight job has to be enabled, has to be in the same schema as the job,
and the program action has to be either a PL/SQL block or a stored procedure.
Action: Use a valid program for the lightweight job.
ORA-27364: remote database "string" already registered as string
Cause: The user attempted to register a remote database that was already registered.
Action: To update the registration information, the REPLACE argument of the
REGISTER_REMOTE_DATABASE procedure should be set to TRUE. If the
registration information is already current, no further action is needed.
ORA-27365: job has been notified to stop, but failed to do so immediately
Cause: The job specified in the stop_job command cannot be stopped
immediately(because it is rolling back or blocked on a network operation), but it has
been notified to stop. This means it will be stopped as soon as possible after its
current uninterruptable operation is done.
Action: No action is required for the job to be stopped, but calling stop_job with force
(if you have the privilege) may cause the job to be stopped sooner.
ORA-27366: job "string"."string" is not running
Cause: An attempt was made to stop a job that was not running.
Action: Verify the status of the job. If the job is running but this message is still being
returned, contact Oracle support.
ORA-27367: program "string"."string" associated with this job is disabled
Cause: An attempt was made to run a job whose program has been disabled.
Action: Reenable the program before running the job.
ORA-24280 to ORA-28709 72-131
ORA-27369: job of type EXECUTABLE failed with exit code: string

Cause: A problem was encountered while running a job of type EXECUTABLE. The
cause of the actual problem is identified by the exit code.
Action: Correct the cause of the exit code and reschedule the job.
ORA-27370: job slave failed to launch a job of type EXECUTABLE
Cause: The scheduler ran into an error when the job slave tried to start a job of type
EXECUTABLE. The rest of the error stack will provide more detailed information on
what the exact problem was.
Action: Correct the problem specified in the error stack and reschedule the job.
ORA-27371: jobs of type EXECUTABLE are not supported on this platform
Cause: The user tried to create a job or program of type EXECUTABLE on a platform
where such jobs are not supported.
Action: Switch to a different platform or create a different type of job or program.
ORA-27372: length of action and arguments exceeds platform limit string
Cause: The total length of the job or program action and the arguments exceeds the
platform limit specified.
Action: Reduce the total length by specifying fewer and/or shorter arguments
ORA-27373: unknown or illegal event source queue
Cause: The source queue specified for the event based job or event based schedule
was either not found or was of the wrong type.
Action: Check if the queue exists. If it does make sure it is a multiple consumer queue
and it is a post 8.1 compatible queue. Single consumer queues and old-style queues
cannot be used as event source queues.
ORA-27374: insufficient privileges on event source queue
Cause: The job owner had insufficient privileges on the event source queue that was
specified for the job.
Action: The job owner has to have dequeue privileges on event source queue or he
has to have manage queue or dequeue any queue system privileges. Make sure one of
these privileges is granted.
ORA-27375: valid agent name must be specified for secure queues
Cause: The queue specified for the event based job or schedule was a secure queue
and either no agent name was specified or an invalid agent name was specified.
Action: If no agent name was specified, retry the call with a valid agent name. If the
agent name was valid, check if the agent is currently subscribed to the queue and, in
the case of jobs, check is the agent has been authorized to act as the job owner.
ORA-27376: event condition cannot be NULL
Cause: A null event condition was passed in for an event based job or schedule. This
is not allowed.
Action: Pass in a legal event condition.
ORA-27377: windows cannot have event based schedules
Cause: Event based schedules for windows are currently not supported.
Action: Use a time-based schedule instead.
ORA-27378: cannot stop jobs of type EXECUTABLE on this platform

Cause: An attempt was made to stop a job of type EXECUTABLE on a platform where
the stop operation was not supported.
Action: If the attempt to stop the job was made with the FORCE option set to FALSE,
try again but change the FORCE option to TRUE.
ORA-27379: INSTANCE_ID attribute conflicts with job class settings
Cause: The value of the INSTANCE_ID attribute of the job conflicted with the value
of the SERVICE attribute of its job class.
Action: Change the value of the INSTANCE_ID attribute or place the job in a job class
whose settings do not conflict with the INSTANCE_ID attribute. Then re-enable the
job.
ORA-27399: job type EXECUTABLE requires the CREATE EXTERNAL JOB
privilege
Cause: The owner of a job of type EXECUTABLE does not have the CREATE
EXTERNAL JOB system privilege.
Action: Grant the CREATE EXTERNAL JOB system privilege to the job owner or
create another job in a schema which does have the CREATE EXTERNAL JOB system
privilege.
ORA-27411: empty string is not a valid repeat interval.
Cause: An empty string '' was provided as a repeat interval for a window or a
schedule.
Action: Specify a valid repeat interval, e.g.,
'FREQ=DAILY;BYHOUR=8;BYMINUTE=0;BYSECOND=0' for a job that executes
daily at 8am.
ORA-27412: repeat interval or calendar contains invalid identifier: string
Cause: The calendar string or calendar definition for the repeat interval of a job,
schedule or window contained an unsupported keyword or reference to an undefined
calendar.
Action: Correct the repeat interval such that it no longer contains the invalid
keyword.
ORA-27413: repeat interval is too long
Cause: The repeat interval consisted of a calendar string larger than the maximum
size allowed.
Action: Use a shorter calendar string for the repeat interval.
ORA-27414: Invalid string clause value
Cause: The BY clause value was not recognized or was out-of-range for the frequency
specified.
Action: Specify a valid BY clause value.
ORA-27415: repeat interval or calendar must start with a frequency clause
Cause: The specified calendar string for the repeat interval did not start with a
frequency clause.
Action: Create a repeat interval that starts with a frequency clause,for example
'FREQ=YEARLY;BYMONTH=FEB'
ORA-24280 to ORA-28709 72-133
ORA-27416: BYDAY clause in repeat interval or calendar contains an invalid

weekday
Cause: The BYDAY clause of the repeat interval contained a value that did not
represent a weekday.
Action: Use the correct three letter abbreviations for weekdays, for example MON for
Monday and FRI for Friday.
ORA-27417: BYWEEKNO clause requires YEARLY clause
Cause: A repeat interval or calendar contained a BYWEEKNO clause with a
frequency other than yearly.
Action: Remove the BYWEEKNO clause or change the frequency to YEARLY.
ORA-27418: syntax error in repeat interval or calendar
Cause: The repeat interval or calendar definition was not recognized as valid syntax.
Action: Specify a valid repeat interval.
ORA-27419: unable to determine valid execution date from repeat interval
Cause: The specified repeat interval contained conflicting clauses that made it
impossible to ever find a matching date, e.g.,
'FREQ=YEARLY;BYMONTH=FEB;BYMONTHDAY=31'. Alternatively, the scheduler
reached its maximum number of attempts to try to find a valid execution date. This
occurs when theoretically there is a valid execution date far in the future, but the
scheduler took too many attempts to determine this date.
Action: Remove the conflicting clauses, or simplify the repeat interval so that it is
easier to determine the next execution date.
ORA-27420: Following message from string interval interpreter
Cause: The repeat interval or calendar definition was not recognized as valid syntax.
Action: Specify a valid repeat interval.
ORA-27421: calendar expression restriction string encountered
Cause: The calendar expression was not valid because a limit test failed. For example,
the maximum value of the interval that can be specified in the INTERVAL clause is
limited to a value derived from the frequency clause.
Action: Specify a valid calendar definition.
ORA-27422: usage of string not supported in embedded calendar application
"string"."string"
Cause: The main calendar definition used an embedded calendar in an INCLUDE,
EXCLUDE, INTERSECT, or FREQ clause for which extra limitations apply.
Action: Remove the specific clause from the calendar definition.
ORA-27423: calendar clause string specified more than once
Cause: The calendar definition contained a clause that was specified twice or more
times.
Action: Append the values in the second clause to the first clause and remove the
second clause.
ORA-27424: calendar clauses string and string are incompatible
Cause: The calendar definition contained clauses that were incompatible.
Action: Change or remove either clause.
ORA-27431: chain "string"."string" has a user-managed rule set

Cause: An attempt was made to modify a rule set that is not managed by the
Scheduler.
Action: Modify the rule set directly using the dbms_rule_adm package or create
another chain without specifying a rule set.
ORA-27432: step "string" does not exist for chain "string"."string"
Cause: The step specified does not exist for the given chain.
Action: Reissue the command using a step that exists for this chain.
ORA-27433: cannot alter state of step "string" for job "string"."string" to string
Cause: The step cannot be changed to the requested state. The state of a running step
cannot be changed. A step which is running or has already run cannot be run again.
Action: Wait until the step has finished running.
ORA-27434: cannot alter chain step job "string"."string"."string"
Cause: A step job of a running chain cannot be altered, only stopped or dropped.
Action: Stop or drop the chain step job or alter the running chain step instead.
ORA-27435: chain job terminated abnormally
Cause: A chain job has ended abnormally. The error code for the running chain could
not be retrieved.
Action: No action necessary. The job will run again when it is scheduled to.
ORA-27451: string cannot be NULL
Cause: An attempt was made to set a NOT NULL scheduler attribute to NULL.
Action: Reissue the command using a non-NULL value for the specified attribute.
ORA-27452: "string" is an invalid name for a database object.
Cause: An invalid name was used to identify a database object.
Action: Reissue the command using a valid name.
ORA-27453: "string" is an invalid job or program argument name.
Cause: An invalid job or program argument name was specified.
Action: Reissue the command using a valid name for this argument.
ORA-27454: argument name and position cannot be NULL
Cause: The name or position of a program or job argument was defined as NULL.
Action: Reissue the command providing either a valid argument name or valid
argument position.
ORA-27455: Only "SYS" is a valid schema for a string.
Cause: A non-SYS schema was specified for an object that must be in the SYS schema.
Action: Reissue the command, leaving out the schema name or using the schema
name of SYS.
ORA-27456: not all arguments of program "string"."string" have been defined
Cause: The number_of_arguments attribute of the named program did not match the
actual number of arguments that have been defined.
Action: Define as many arguments as the number of arguments, or change the
number of arguments.
ORA-24280 to ORA-28709 72-135
ORA-27457: argument string of job "string"."string" has no value

Cause: No value was provided for the job argument with the specified position.
Action: Provide a value for the job argument using any of the set_job_xxxx_value()
routines. Or, when using a named program, specify a default value for the
corresponding argument of the program.
ORA-27458: A program of type PLSQL_BLOCK cannot have any arguments.
Cause: An attempt was made to create or enable a program of type PLSQL_BLOCK
with arguments. This is not allowed.
Action: Change the number of arguments to zero, or change the type of the program.
ORA-27459: A program of type EXECUTABLE must have character-only arguments.
Cause: A program of type EXECUTABLE was created or enabled with one or more
arguments of non-character datatypes.
Action: Change the arguments to be of character-only datatypes.
ORA-27460: cannot execute disabled job "string"."string"
Cause: An attempt was made to run a job that is disabled.
Action: Enable the job and then reschedule the job.
ORA-27461: The value for attribute string is too large.
Cause: The value that was provided for the specified attribute was too large.
Action: Reissue the command using a smaller or shorter value.
ORA-27463: invalid program type string
Cause: An invalid program type was specified.
Action: Reissue the command using a valid program type.
ORA-27464: invalid schedule type string
Cause: An invalid schedule type was specified.
Action: Reissue the command using a valid schedule type.
ORA-27465: invalid value string for attribute string
Cause: An invalid value was provided for the specified attribute.
Action: Reissue the command using a valid value for this attribute.
ORA-27467: invalid datatype for string value
Cause: The value provided for the named scheduler attribute was of an invalid
datatype.
Action: Reissue the command using a value of the correct datatype.
ORA-27468: "string"."string" is locked by another process
Cause: An attempt was made to read or modify the state of the named scheduler
object when another process was also updating the same object and held the lock.
Action: Retry the operation. Scheduler locks are held for a very short duration. If the
error persists, contact Oracle Support.
ORA-27469: string is not a valid string attribute
Cause: A non-existant attribute was specified.
Action: Reissue the command using a valid attribute for that specific scheduler object.
ORA-27470: failed to re-enable "string"."string" after making requested change

Cause: A change was made to an enabled scheduler object that caused it to become
disabled.
Action: Alter the object so that it becomes valid and then enable it.
ORA-27471: window "string"."string" is already closed
Cause: An attempt was made to close a window that was not open.
ORA-27472: invalid metadata attribute string
Cause: An invalid metadata attribute was specified.
Action: Reissue the command using a valid metadata attribute.
ORA-27473: argument string does not exist
Cause: An argument which was specified does not exist.
Action: Reissue the command using an argument name defined by the program or
using a valid argument position.
ORA-27474: cannot give both an argument name and an argument position
Cause: An argument was specified using both a name and a position.
Action: Reissue the command using either the argument name or the argument
position but not both.
ORA-27475: unknown string "string"."string"
Cause: The specified object did not exist, privileges were not granted, or the object
was of the wrong type.
Action: Specify an object of the correct type on which you have privileges.
ORA-27476: "string"."string" does not exist
Cause: A database object was specified that does not exist.
Action: Reissue the command using an object that exists or create a new object and
then reissue this command.
ORA-27477: "string"."string" already exists
Cause: An attempt was made to create an object with a name that has already been
used by another object in the same schema.
Action: Reissue the command using a different name or schema.
ORA-27478: job "string"."string" is running
Cause: An attempt was made to drop a job that is currently running.
Action: Stop the job and then reissue the command, or reissue the command
specifying the force option to stop the job first.
ORA-27479: Cannot string "string"."string" because other objects depend on it
Cause: An attempt was made to drop or disable a scheduler object that has jobs
associated with it without specifying the force option.
Action: Alter the associated jobs so they do not point to the scheduler object being
dropped or disabled and then reissue the command. Alternatively reissue the
command specifying the force option. If the force option is specified and a scheduler
object is being dropped, all associated jobs will be disabled.
ORA-24280 to ORA-28709 72-137
ORA-27480: window "string" is currently open

Cause: An attempt was made to drop a window that is currently open, or to manually
open a window while another window is already open.
Action: Close the window that is open and then reissue the command, or reissue the
command while setting the force option to TRUE.
ORA-27481: "string"."string" has an invalid schedule
Cause: An attempt was made to enable a job or window that has an invalid schedule.
Action: Alter the schedule of the job or window so that it is valid and then reissue the
enable command.
ORA-27483: "string"."string" has an invalid END_DATE
Cause: An attempt was made to enable a job or window that has an invalid end_date.
Either the end_date is before the start_date or the end_date is in the past.
Action: Alter the job or window so that the end date becomes valid (possibly null)
and then reissue the command.
ORA-27484: Argument names are not supported for jobs without a program.
Cause: An attempt was made to set or reset a job argument by using the name of the
argument. Identifying job arguments by their name is only supported in combination
with jobs that are based on programs. Jobs that are not using a program cannot have
named arguments.
Action: Use argument position instead of name and then issue the command again.
ORA-27485: argument "string" already exists at a different position
Cause: An attempt was made to create or replace an argument with a name that is
already used by an argument at a different position.
Action: Use a different name for the argument or drop or alter the argument which
already exists with this name and then reissue the command.
ORA-27486: insufficient privileges
Cause: An attempt was made to perform a scheduler operation without the required
privileges.
Action: Ask a sufficiently privileged user to perform the requested operation, or grant
the required privileges to the proper user(s).
ORA-27487: invalid object privilege for a string
Cause: The granted object privilege is not valid for the specified scheduler object.
Action: Check the scheduler documentation to verify which object privileges can be
granted on which scheduler objects.
ORA-27488: unable to set string because string was/were already set
Cause: An attempt was made to set an object's attribute even though one or more
conflicting attributes of the same object had already been set.
Action: Set the other conflicting attributes to NULL and then reissue the command.
ORA-27489: unable to process job "string"."string" from job class "string"
Cause: An error was encountered while processing the named job from the specified
job class.
Action: Resolve the error for this job and then reissue the command. See the next error
message on the stack to find out what the error for the job is.
ORA-27490: cannot open disabled window "string"."string"

Cause: The user tried to open a disabled window.
Action: Enable the window and then try to open it again.
ORA-27491: repeat_interval and start_date cannot both be NULL
Cause: An attempt was made to set both repeat_interval and start_date to equal
NULL for a Scheduler window or schedule.
Action: If either repeat_interval or start_date is set to equal NULL, the other should
be set to a non-NULL value.
ORA-27492: unable to run job "string"."string": scheduler unavailable
Cause: A job run with current session set to false can not be issued if the scheduler is
not active. Check value of job_queue_processes parameter, issue
dbms_ijob.set_enabled(true), database is in upgrade/migrade mode, database is in
data guard mode, or scheduler attribute SCHEDULER_DISABLED is set to TRUE
Action: Run the job in the current session or activate the scheduler
ORA-27493: In-memory job "string.string" cannot be modified
Cause: Once enabled, the full in-memory job could not be further modified.
Action: The only actions that can be taken now are to stop or drop the job.
ORA-27494: operation not permitted on in-memory job
Cause: An attempt was made to perform an action that was not permitted on an inmemory job.
Action: Check Oracle Scheduler documentation to see which actions can be
performed on in-memory jobs.
ORA-27495: attribute string cannot be set for in-memory jobs
Cause: An attempt was made in a CREATE or SET_ATTRIBUTE call to set an
attribute that could not be set for run-time in-memory jobs.
Action: If you need to set this attribute, use either regular or lightweight jobs.
ORA-27496: credential "string"."string" is disabled
Cause: An attempt was made to run a job, file watcher or external procedure whose
credential was disabled.
Action: Reenable the credential before running the job, file watcher or external
procedure.
ORA-27497: operation is not permitted inside a pluggable database
Cause: This operation was not permitted in a pluggable database.
Action: Log into the root database and retry the operation.
ORA-27498: resource constraint object type mismatch
Cause: all resource constraints of a resource must be of the same type
Action: Delete existing constraints for the resource
ORA-27499: in-memory job metadata is too large
Cause: The in-memory job was too large. Due to the need to keep in-memory jobs
efficient and performing well,we limit the size of in-memory job metadata to 8
kilobytes. This includes the space used for job argument values.
ORA-24280 to ORA-28709 72-139
Action: Reduce the size of the job metadata and try again. If all the metadata is
needed, then you should create some other type of job.
ORA-27500: inter-instance IPC error
Cause: This is an operating system/cluster interconnect error.
Action: Check the extra information and contact Oracle Support Services.
ORA-27501: IPC error creating a port
Action: Check the value of errno and contact Oracle Support Services.
ORA-27502: IPC error deleting OSD context
ORA-27503: IPC error attempting to cancel request
ORA-27504: IPC error creating OSD context
ORA-27505: IPC error destroying a port
ORA-27506: IPC error connecting to a port
ORA-27507: IPC error disconnecting from a port
ORA-27508: IPC error sending a message
ORA-27509: IPC error receiving a message
ORA-27510: IPC error waiting for a request to complete
ORA-27512: IPC error posting a process
ORA-27513: parameter string contains invalid value string

Cause: The program could not identify the value as an IP address.
Action: Change the value to be a valid IP address.
ORA-27514: IPC error copying memory to remote process
ORA-27532: IPC global name service error
ORA-27542: Failed to unprepare a buffer prepared for remote update
ORA-27543: Failed to cancel outstanding IPC request
ORA-27544: Failed to map memory region for export
ORA-27545: Fail to prepare buffer for remote update
ORA-27546: Oracle compiled against IPC interface version string.string found
version string.string
Cause: A misconfiguration or installation error occurred.
Action: Install the IPC library for this release of Oracle.
ORA-27547: Unable to query IPC OSD attribute string
Cause: This is an operating system-dependent IPC error.
Action: Contact Oracle support Services.
ORA-27548: Unable to unprepare IPC buffer
Cause: This is an operating system-dependent IPC error.
Action: Contact Oracle support Services.
ORA-27550: Target ID protocol check failed. tid vers=string, type=string, remote
instance number=string, local instance number=string
Cause: The local Oracle Real Application Cluster instance and remote instance are
running with incompatible implementation of the inter-instance IPC protocol library.
A misconfiguration or installation error occurred.
Action: Check additional error messages in the alert log and the process trace file.
ORA-27601: Cell storage initialization failed, cell library error code [string]
Cause: Cell storage client did not succeed in initializing.
ORA-27602: Failure to publish network status information, cell library error code
[string]
Cause: Network status information publishing failed.
ORA-24280 to ORA-28709 72-141
ORA-27603: Cell storage I/O error, I/O failed on disk string at offset string for data
length string
Cause: Cell storage I/O read or write failed, possibly due to a configuration problem
or a hardware failure.
ORA-27604: Cell storage ioctl error, ioctl failed on disk string
Cause: Ioctl operation on a cell storage disk failed.
ORA-27605: Smart I/O failed as a handle could not be obtained to the cell "string"
as the cell is not accessible.
Cause: The cell could have been unavailable.
Action: Ensure the cell is available. Check the network connectivity.
ORA-27606: Smart I/O failed because the diskgroup was found to be unmounted.
tablespace number: "string", file number: "string"
Cause: The diskgroup to which the specified file belongs was found to be unmounted.
Action: Ensure that the diskgroup to which the specified file belongs is mounted.
ORA-27607: Smart I/O failed because there were no online disks. tablespace
number: "string", file number: "string"
Cause: There were no online disks found for the specified file.
Action: Ensure the diskgroup to which the specified file belongs to is mounted.
Ensure that the disks are online. Check the availability of cells and check the network.
ORA-27608: Smart I/O failed because the disk "string" on the cell "string" was not
open. error code: "string", "string"
Cause: The specified disk on the specified cell could not be opened.
Action: Ensure the cell is available. Check the network.
ORA-27609: Smart I/O failed due to a network error to the cell "string". error code
"string", "string"
Cause: The specified cell could not be connected to.
Action: Ensure that the cell is available. Check the network.
ORA-27610: Smart I/O failed due to shortage of memory on the cell "string"
Cause: The specified cell had a shortage of memory to perform smart I/O.
Action: Reduce the parallel degree or number of Oracle sessions executing smart I/O.
ORA-27611: Smart I/O failed due to a block corruption detected on the host. The
block was received from cell "string". disk: "string", block: "string", disk offset:
"string"
Cause: The data block indicated was corrupted on the host, but a corruption was not
found on the cell.
Action: This may be due to a transient network error or a real block corruption. Check
your network for any errors. Analyze the segment to which the file belongs. If there is
indeed a corruption, try to restore the block using RMAN block recovery. If there is a
trace file, report the errors in it to Oracle Support Services. If analyze did not report
an error and network did not have any error, report the problem to Oracle Support
Services as this appears to be a software error.
ORA-27612: Smart I/O failed due to a block corruption detected on the cell "string".
disk: "string", block: "string", disk offset: "string"
Cause: The data block indicated was found to be corrupted on the cell.
Action: This may be due to a software error or a real data corruption. Analyze the
segment. If there is indeed a block corruption, try to restore the block using RMAN
block level recovery. If there is a trace file, report the errors in it to Oracle Support
Services. If analyze did not report an error, report the problem to Oracle Support
Services as this appears to be a software error.
ORA-27613: Smart I/O failed due to an I/O error on the cell "string". disk: "string",
block: "string", disk offset: "string" I/O size: "string"
Cause: An I/O request failed on the specified cell and disk.
Action: Check the specified disk on the cell.
ORA-27614: Smart I/O failed due to an error "string, string" from the cell "string".
disk: "string", block: "string", disk offset: "string" I/O size: "string"
Cause: An I/O request failed, due to an internal error on the specified cell and disk.
Action: Report the problem to Oracle Support Services along with the process trace
file and alert log.
ORA-27615: Smart I/O file to ASM disk translation failed with error: string.
Cause: An internal error caused a smart I/O operation to fail.
file and alert log.
ORA-27616: ASM Allocation Unit: string
Cause: This error message is usually accompanied by another message, indicating the
real problem. This message exists to provide additional information to Oracle Support
Services.
Action: Check the next error message.
ORA-27617: Smart I/O failed because of an internal error. Cell "string", disk
"string", cell library error code "string, string", error information "string"
file and alert log.
ORA-27618: Smart I/O failed because of an internal error. Cell "string", cell library
error code "string, string", error information "string"
file and alert log.
ORA-27619: Smart I/O failed because of an internal error when determining the
time zone file version. Error code "string"
file and alert log.
ORA-24280 to ORA-28709 72-143
ORA-27621: The value of string is not valid for parameter string

Cause: Incorrect value is specified for an internal parameter.
Action: This parameter should only be set by Oracle Support Services. Check the
additional diagnostic information in the trace file and contact Oracle Support Services
for recommendations on setting this parameter.
ORA-27623: Cell automation SQL action failed
Cause: Cell automation manager or worker process failed to execute SQL action
through OCI recursive call.
Action: Check the alert log and process trace file for additional information. Contact
Oracle Support Services if the errors specified in the trace file cannot be corrected.
ORA-27624: Smart I/O failed because the number of reconnects to the cell "string"
exceeded the maximum allowed "string".
Cause: The number of reconnects to a cell exceeded the maximum allowed. This
problem indicates a possible network problem or a software problem on the cell.
Action: If the cellsrv is being restarted repeatedly, in a short interval, check the system
load. The problem may be corrected by rebooting the cell. If the system is not
overloaded, the repeated restarts are likely due to software problem. Report the
problem to Oracle Support Services along with alert log and trace files. If the cellsrv is
not restarting, the problem may be in the IB network. Check the network between the
host and all the cells.
ORA-27625: Exadata configuration failed.
Cause: One or both of the files, cellinit.ora and cellip.ora, were either invalid or
missing.
Action: Check if the files, cellinit.ora and cellip.ora, are both present. They can be
found in the $OSSCONF directory. If both are present, check if their contents are valid
and correct. If the files are invalid or missing, produce files with valid information in
the $OSSCONF directory. For information on how to set up these files, see the
Exadata Users Guide.
ORA-27626: Exadata error: string (string)
Cause: The cause of this error is dependent on the context in which this error is
reported.
Action: See the primary error reported with this error.
ORA-27627: Software edition incompatible with Exadata storage.
Cause: Oracle Exadata can be used only with Oracle Database Enterprise Edition.
Action: Check if Oracle is linked with the Enterprise Edition options.
ORA-27628: An invalid value was specified for the parameter string.
Cause: An invalid value was specified for a parameter.
Action: Check the additional diagnostic information in the trace file and contact
Oracle Support Services if further help is required.
ORA-27629: External table smart I/O failed because cell is not accessible.
Cause: The cell was unavailable.
Action: Ensure the cell is available.
ORA-27631: External encryption or decryption is disabled.

Cause: Either decryption was disabled in the cellinit.ora initialization parameter file,
or the cryptography mode requested by the database was incompatible with what
was available on the cell.
Action: No action is necessary. The Exadata cell returns data in pass-through mode
when encryption or decryption is required.
ORA-28000: the account is locked
Cause: The user has entered wrong password consequently for maximum number of
times specified by the user's profile parameter FAILED_LOGIN_ATTEMPTS, or the
DBA has locked the account
Action: Wait for PASSWORD_LOCK_TIME or contact DBA
ORA-28001: the password has expired
Cause: The user's account has expired and the password needs to be changed
Action: change the password or contact the DBA
ORA-28002: the password will expire within string days
Cause: The user's account is about to expire and the password needs to be changed
Action: change the password or contact the DBA
ORA-28003: password verification for the specified password failed
Cause: The new password did not meet the necessary complexity specifications and
the password_verify_function failed
Action: Enter a different password. Contact the DBA to know the rules for choosing
the new password
ORA-28004: invalid argument for function specified in
PASSWORD_VERIFY_FUNCTION string
Cause: The password verification function does not have the required number and
type of input/output arguments and/or the return argument
Action: Check the manual to find out the format of the password verification function
ORA-28005: invalid logon flags
Cause: The flags are not properly set or conflicting flags are set in making calls
Action: Call the function with appropriate flags set.
ORA-28006: conflicting values for parameters string and string
Cause: The parameters PASSWORD_REUSE_TIME and PASSWORD_REUSE_MAX
cannot both be set. One parameter should be unlimited while other is set
Action: Set one value to UNLIMITED explicitly
ORA-28007: the password cannot be reused
Cause: The password cannot be reused for the specified number of days or for the
specified nunmber of password changes
Action: Try the password that you have not used for the specified number of days or
the specified number of password changes Refer to the password parameters in the
CREATE PROFILE statement
ORA-24280 to ORA-28709 72-145
ORA-28008: invalid old password

Cause: old password supplied is wrong; Hence user cannot be authenticated using
old password
Action: Supply the correct old password for authentication
ORA-28009: connection as SYS should be as SYSDBA or SYSOPER
Cause: connect SYS/password is no longer a valid syntax
Action: Try connect SYS/password as SYSDBA or connect SYS/password as SYSOPER
ORA-28010: cannot expire external or global accounts
Cause: If a user account is created as IDENTIFIED EXTERNALLY, or IDENTIFIED
GLOBALLY, this account cannot be expired
Action: Try to expire the password of the user that has database password
ORA-28011: the account will expire soon; change your password now
Cause: The user's account is marked for expiry; the expiry period is unlimited.
Action: Change the password or contact the DBA.
ORA-28012: connection as string should use AS string
Cause: An attempt was made to connect as an administrative user without using AS
SYSBACKUP, AS SYSDG, or AS SYSKM.
Action: Try connecting with AS SYSBACKUP, AS SYSDG, or AS SYSKM.
Cause: The password of the proxy user expired.
Action: Connect directly as proxy user to change the password or contact the DBA.
ORA-28014: cannot drop administrative users
Cause: An attempt was made to drop administrative users. Administrative users can
be dropped only by SYS during migration mode.
Action: Try dropping administrative users during migration mode.
ORA-28015: account unlock attempted on read-only database but a conflicting
account lockout on the primary exists
Cause: An attempt to unlock an account on a read-only database was prevented,
because the account was previously marked as locked on the primary database. All
attempts to unlock the account on the read-only database will be prevented as long as
the overriding "account locked" condition exists at the primary database.
Action: If this database is part of a Data Guard configuration, perform the account
unlock action on the primary database. If this database is read-only, then set the
database to read/write and perform the account unlock action.
ORA-28016: Privilege string cannot be granted to SYS.
Cause: An attempt was made to grant SYSBACKUP, SYSDG or SYSKM to the SYS
user. These administrative privileges cannot be granted to SYS.
Action: Try granting the administrative privilege to other users.
ORA-28017: The password file is in the legacy format.
Cause: There are multiple possibilities for the cause of the error: * An attempt was
made to grant SYSBACKUP, SYSDG or SYSKM. * These administrative privileges
could not be granted unless the password file used a newer format ("12" or higher). *
An attempt was made to grant a privilege to a user who has a large password hash
which cannot be stored in the password file unless the password file uses a newer
format ("12" or higher). * An attempt was made to grant or revoke a common
administrative privilege in a CDB
Action: Regenerate the password file in the newer format ("12" or higher). Use the
newer password file format ("12" or higher) if you need to grant a user the
SYSBACKUP, SYSDG or SYSKM administrative privileges, or if you need to grant a
privilege to a user who has a large password hash value.
ORA-28018: This operation requires connection as SYS or SYSBACKUP.
Cause: An attempt was made to execute a command even though the user was not
connected as SYS or SYSBACKUP.
Action: Connect as SYS or SYSBACKUP and retry this command.
ORA-28019: audit cannot be configured on administrative privileges
Cause: An attempt was made to configure audit on an administrative privilege using
either the AUDIT, NOAUDIT, CREATE AUDIT POLICY, or ALTER AUDIT POLICY
command.
Action: For traditional audit, use AUDIT_SYS_OPERATIONS to audit administrative
privileges. If this is a unified audit, use action-based auditing to audit administrative
users.
ORA-28020: IDENTIFIED GLOBALLY already specified
Cause: The IDENTIFIED GLOBALLY clause was specified twice.
Action: Use only one IDENTIFIED GLOBALLY clause.
ORA-28021: cannot grant global roles
Cause: The role granted was IDENTIFIED GLOBALLY. Global roles can only be
granted via a central authority for the domain.
Action: Use ALTER ROLE to change the type of role (from IDENTIFIED GLOBALLY
to other, such as IDENTIFIED BY password), or allocate it to a global user via the
central authority.
ORA-28022: cannot grant external roles to global user or role
Cause: The role granted was IDENTIFIED EXTERNALLY. External roles cannot be
granted to global users, to global roles or to any other roles.
Action: Use ALTER ROLE to change the type of the role being granted (from
IDENTIFIED EXTERNALLY to other, such as NOT IDENTIFIED) or use ALTER
USER to change the type of the user that is the grantee.
ORA-28023: must revoke grants of this role to other user(s) first
Cause: The role altered to IDENTIFIED GLOBALLY was granted to one or more other
users and/or roles. Global roles cannot be granted to any user or role.
Action: Use REVOKE to revoke the role from other users or roles first.
ORA-28024: must revoke grants of external roles to this role/user
Cause: The user or role altered to IDENTIFIED GLOBALLY has external roles directly
granted - these must be revoked, since external roles cannot be granted to global users
or roles.
Action: Use REVOKE to revoke the external roles from the user or role to be
ALTERed.
ORA-24280 to ORA-28709 72-147
ORA-28025: missing or null external name

Cause: The IDENTIFIED EXTERNALLY AS or IDENTIFIED GLOBALLY AS clause
was specified with a valid external name.
Action: Provide a valid external name.
ORA-28026: user with same external name already exists
Cause: The external name specified for the user being created or altered already exists
for another user.
Action: External names must be unique among users. Specify another.
ORA-28027: privileged database links may be used by global users
Cause: Only users IDENTIFIED GLOBALLY may use a privileged database link.
Action: Either change the user to a global user or try to use a different database link.
ORA-28028: could not authenticate remote server
Cause: During the course of opening a privileged database link, the remote server
was not securely identified using the network security service. Additional errors
should follow.
Action: Consult the network security service documentation on how to properly
configure the remote server.
ORA-28029: could not authorize remote server for user string
Cause: During the course of opening a privileged database link, the remote server
was found to lack the necessary authorizations to connect as the current global user.
This may be because the server was not authorized by the network security service.
Or it may be because the local server is restricting access by the remote server using
the DBMS_SECURITY_DOMAINS_ADMIN package.
Action: Grant the remote server the proper authorization to connect as the given
global user, and check that the local server is not restricting access.
ORA-28030: Server encountered problems accessing LDAP directory service
Cause: Unable to access LDAP directory service
Action: Please contact your system administrator
ORA-28031: maximum of string enabled roles exceeded
Cause: The user attempted to enable too many roles.
Action: Enable fewer roles.
ORA-28032: Your password has expired and the database is set to read-only
Cause: Your password expired and needs to be changed before your login request can
be processed. Because the database is currently open in read-only mode, the
password change operation cannot be performed on this database.
Action: Log in to the primary database to change your password, then retry your
login request at the standby database.
ORA-28034: cannot grant string to an Oracle supplied user
Cause: The KEEP DATE TIME, KEEP SYSGUID or KEEP SEQUENCE privilege could
not be granted to an Oracle supplied user.
Action: Grant privilege directly to the application user.
ORA-28035: Cannot Get Session Key for Authentication

Cause: Client and server cannot negotiate shared secret during logon
Action: User should not see this error. Please contact your system administrator
ORA-28037: Cannot Get Session Key for RACF Authentication
Cause: Client and server cannot negotiate shared secret during logon
Action: User should not see this error. Please contact your system administrator
ORA-28038: disallow O2LOGON
Cause: turn off O2LOGON
Action: n/a
ORA-28039: cannot validate Kerberos service ticket
Cause: The Kerberos service ticket provided was invalid or expired
Action: Provide a valid, unexpired service ticket.
ORA-28040: No matching authentication protocol
Cause: There was no acceptable authentication protocol for either client or server.
Action: The administrator should set the values of the
SQLNET.ALLOWED_LOGON_VERSION_SERVER and
SQLNET.ALLOWED_LOGON_VERSION_CLIENT parameters, on both the client
and on the server, to values that match the minimum version software supported in
the system. This error is also raised when the client is authenticating to a user account
which was created without a verifier suitable for the client software version. In this
situation, that account's password must be reset, in order for the required verifier to
be generated and allow authentication to proceed successfully.
ORA-28041: Authentication protocol internal error
Cause: Authentication protocol failed with an internal error
Action: n/a
ORA-28042: Server authentication failed
Cause: Server failed to authenticate itself to the client
Action: Confirm that the server is a valid database server.
ORA-28043: invalid bind credentials for DB-OID connection
Cause: The Database password stored in the wallet did not match the one in OID .
Action: Use DBCA to reset the database password so that it is the same in database
wallet and in OID.
ORA-28044: unsupported directory type
Cause: The database tried to work with a directory which is not OID.
Action: Enterprise User Security works only with Oracle Internet Directory. Update
the ldap.ora file to reflect an appropriate OID.
ORA-28045: SSL authentication between database and OID failed
Cause: Server failed to authenticate itself to the Directory.
Action: Make sure the sqlnet.ora used is pointing to the wallet with the right
certificate.
ORA-24280 to ORA-28709 72-149
ORA-28046: Password change for SYS disallowed

Cause: REMOTE_LOGIN_PASSWORDFILE is set to SHARED, prohibiting SYS
password changes.
Action: Change setting of REMOTE_LOGIN_PASSWORDFILE to EXCLUSIVE or
NONE.
ORA-28047: database is not a member of any enterprise domain in OID
Cause: An enterprise user login was attempted on a database that is not a member of
any enterprise domain in OID.
Action: An administrator should put the database into an enterprise domain in OID,
and then the user should reconnect.
ORA-28048: database is a member of multiple enterprise domains in OID
Cause: An enterprise user login was attempted on a database that is a member of
multiple enterprise domains in OID.
Action: An administrator should put the database into only one enterprise domain in
OID, and then the user should reconnect.
Cause: The enterprise user's password has expired and the password needs to be
changed.
Action: change the password in the directory or contact the directory administrator.
ORA-28050: specified user or role cannot be dropped
Cause: The user or role specified in the DROP statement was a reserved Oracle object
that could not be dropped.
Action: None
ORA-28051: the account is locked
Cause: The enterprise user has consecutively entered the wrong password for
maximum number of times specified in the realm's password policy profile.
Action: Contact the directory administrator.
ORA-28052: the account is disabled
Cause: The enterprise user's account in the directory has been disabled.
ORA-28053: the account is inactive
Cause: The enterprise user's account in the directory is currently not active.
ORA-28054: the password has expired. string Grace logins are left
Cause: The enterprise user's password has expired. The user is able to login because
he has gracelogins left.
Action: change the password in the directory or contact the directory administrator.
ORA-28055: the password will expire within string days
Cause: The enterprise user's password is about to expire.
Action: Change the password in the directory or contact the directory administrator.
ORA-28056: Writing audit records to Windows Event Log failed

Cause: Unable to write an audit entry to the Windows event log used as the audit
trail.
Action: Check the error number for a possible operating system error. If there is no
error, contact Oracle Support Services.
ORA-28057: name of the password file could not be constructed
Cause: Possibly environment variable ORACLE_SID was not set.
Action: Set value for the ORACLE_SID environment variable.
ORA-28058: login is allowed only through a proxy
Cause: This account is marked "proxy only connect".
Action: Connect through a proxy user.
ORA-28059: Cross-instance call failed
Cause: An attempt to inform other Oracle RAC instances of a security event failed.
Action: Log into each instance to perform the administrative action.
ORA-28060: A data redaction policy already exists on this column.
Cause: A data redaction policy was already in existence on this column.
Action: Specify a colunm which does not already have a redaction policy defined on
it, or use DBMS_REDACT.ALTER_POLICY to alter the existing redaction policy for
this column.
ORA-28061: This object cannot have a data redaction policy defined on it.
Cause: An attempt was made to define a data redaction policy on an object other than
a table or view. Note that a data redaction policy cannot be defined on an editioned
view, or on specialized tables created internally by the server in conjunction with
various features such as materialized view.
Action: Specify the name of a table or view.
ORA-28062: The policy expression is too long.
Cause: The policy expression was longer than 4000 characters.
Action: Specify a policy expression of at most 4000 characters.
ORA-28063: The policy expression is empty.
Cause: The EXPRESSION parameter to DBMS_REDACT.ADD_POLICY was empty.
Action: A nonempty policy expression must be specified in the EXPRESSION
parameter to DBMS_REDACT.ADD_POLICY.
ORA-28064: The redaction function is not valid.
Cause: The FUNCTION_TYPE parameter to DBMS_REDACT.ADD_POLICY was
invalid.
Action: Specify the FUNCTION_TYPE parameter to DBMS_REDACT.ADD_POLICY
as one of the following: DBMS_REDACT.NONE, DBMS_REDACT.FULL,
DBMS_REDACT.RANDOM, DBMS_REDACT.PARTIAL, DBMS_REDACT.REGEXP,
or NULL. Note that only full redaction may be applied to columns of type BLOB,
CLOB, or NCLOB.
ORA-28066: invalid column "string"
Cause: An invalid column was specified in the COLUMN_NAME parameter.
ORA-24280 to ORA-28709 72-151
Action: Check the columns in the object and specify the right column name.
ORA-28067: missing or invalid column name
Cause: A valid column name was not specified in the COLUMN_NAME parameter
when a column name was required. Note that when using
DBMS_REDACT.ALTER_POLICY, the default action is
DBMS_REDACT.ADD_COLUMN
Action: Specify the name of a column.
ORA-28068: The object "string" does not have a data redaction policy.
Cause: The specified object did not have a data redaction policy defined on it.
Action: Specify the name of an object which has a data redaction policy, or use
DBMS_REDACT.ADD_POLICY to add a data redaction policy.
ORA-28069: A data redaction policy already exists on this object.
Cause: A data redaction policy was already in existence on this object.
Action: Specify a table or view which does not already have a redaction policy
defined on it, or use DBMS_REDACT.ALTER_POLICY to alter the existing redaction
policy for this object.
ORA-28070: The column "string" does not have a data redaction policy.
Cause: The specified column did not have a data redaction policy defined on it.
Action: Specify the name of a column which has a data redaction policy.
ORA-28071: The action is not valid.
Cause: The ACTION parameter to DBMS_REDACT.ALTER_POLICY was invalid.
Action: Specify the ACTION parameter to DBMS_REDACT.ALTER_POLICY as one
of the following values: DBMS_REDACT.MODIFY_EXPRESSION,
DBMS_REDACT.MODIFY_COLUMN, DBMS_REDACT.ADD_COLUMN, or
DBMS_REDACT.DROP_COLUMN.
ORA-28072: The specified policy name is incorrect.
Cause: The POLICY_NAME parameter was incorrect.
Action: Specify the POLICY_NAME parameter with the name of the redaction policy
currently defined on the object.
ORA-28073: The column "string" has an unsupported data type.
Cause: The column had a data type which is not supported by data redaction. The
supported data types are CHAR, NCHAR, VARCHAR2, NVARCHAR2, NUMBER
types, BINARY_FLOAT, BINARY_DOUBLE, DATE, and TIMESTAMP. For regular
expression-based redaction, with FUNCTION_TYPE of DBMS_REDACT.REGEXP,
only the string data types (VARCHAR2, NVARCHAR2, CHAR, and NCHAR) are
supported by data redaction. Virtual columns are not supported by data redaction.
Action: Specify the name of a column which has a supported data type.
ORA-28074: The "string" field of the redaction parameters is not valid.
Cause: The redaction parameters specified had one or more fields that were invalid.
Action: Specify the redaction parameters according to Oracle documentation.
ORA-28075: The data redaction policy expression has an error.
Cause: The data redaction policy expression had an error.
Action: Contact the data redaction policy administrator. To correct this error, when
invoking the ADD_POLICY and ALTER_POLICY procedures of the data redaction
DBMS_REDACT package, the policy administrator must specify a valid policy
expression for the EXPRESSION parameter. Check the trace file for the name of the
affected policy and the error, and correct the data redaction policy expression.
ORA-28076: An attribute was not specified for SYS_SESSION_ROLES.
Cause: An attribute was not specified for the SYS_SESSION_ROLES namespace in the
policy expression.
Action: Specify an attribute for SYS_SESSION_ROLES in the policy expression.
ORA-28077: The attribute specified (string) exceeds the maximum length.
Cause: The attribute specified in the policy expression for the SYS_SESSION_ROLES
namespace exceeded the maximum length.
Action: Change the policy expression to use a valid attribute for
SYS_SESSION_ROLES namespace.
ORA-28078: A regular expression parameter is missing or invalid.
Cause: The FUNCTION_TYPE was DBMS_REDACT.REGEXP, but one or more of the
regular expression parameters were missing or invalid, the REGEXP_PATTERN
failed to compile properly, or the regular expression replacement operation failed.
Action: Specify the regular expression parameters according to Oracle
documentation. At a minimum, the REGEXP_PATTERN and the
REGEXP_REPLACE_STRING must be specified. Ensure that the REGEXP_PATTERN
can compile properly as a regular expression, for example by testing it with
REGEXP_REPLACE in a SQL query against a column containing some of the data to
be redacted.
ORA-28079: The policy was already enabled.
Cause: The redaction policy specified has already been enabled.
Action: Only disabled redaction policies can be enabled.
ORA-28080: The policy was already disabled.
Cause: The redaction policy specified has already been disabled.
Action: Only enabled redaction policies can be disabled.
ORA-28081: Insufficient privileges - the command references a redacted object.
Cause: The command referenced a redacted column in an object protected by a data
redaction policy.
Action: If possible, modify the command to avoid referencing any redacted columns.
Otherwise, drop the data redaction policies that protect the referenced tables and
views, or ensure that the user issuing the command has the EXEMPT REDACTION
POLICY system privilege, then retry the operation. The EXEMPT REDACTION
POLICY system privilege is required for creating or refreshing a materialized view
when the materialized view is based on an object protected by a data redaction policy.
The EXEMPT REDACTION POLICY system privilege is required for performing a
data pump schema-level export including any object protected by a data redaction
policy. All data redaction policies are listed in the REDACTION_COLUMNS catalog
view.
ORA-28082: The parameter string is invalid.
Cause: The specified parameter was either empty or too long.
ORA-24280 to ORA-28709 72-153
Action: Specify a parameter of correct length. See the documentation for length
requirements.
ORA-28083: A redacted column was referenced in a virtual column expression.
Cause: This redacted column was referenced in a virtual column expression.
Action: Ensure the column expression definition for any virtual column does not refer
to any redacted columns. To check for columns with redaction policies, use the
REDACTION_COLUMNS catalog view which lists all data redaction policies.
ORA-28085: The input and output lengths of the redaction do not match.
Cause: As specified, the redaction parameters produced an output with a length
different to that of the input.
Action: Use regular expression redaction instead of partial redaction.
ORA-28086: The data redaction policy expression has an error.\nstring
Cause: The data redaction policy expression had an error.
Action: Specify a valid policy expression. The data redaction policy expression must
be written in SQL, and must be a valid predicate to use in the following SQL query.
SELECT 1 FROM DUAL WHERE policy_expression;
ORA-28087: The policy expression has an unsupported (use of) operator 'string'.
Cause: The policy expression used an unsupported operator, or used an operator in
an unsupported way.
Action: Modify the policy expression to use only the supported operators in a
supported way. Supported operators include "=", "!=", ">", "<", ">=", "<=", the length
operators, the substring operators, and the context operators (SYS_CONTEXT and
XS_SYS_CONTEXT). For a complete list of the supported operators, and the
supported ways the allowed operators can be used, refer to the section on data
redaction policy expressions in the Oracle documentation.
ORA-28088: The policy expression has an unsupported PL/SQL function
string.string.string.
Cause: The policy expression had an unsupported PL/SQL function.
Action: Modify the policy expression to use a supported PL/SQL function. Supported
PL/SQL functions include the Oracle Label Security dominates functions, and the
Oracle Apex session state functions (V and NV). For a complete list of the supported
PL/SQL functions, refer to data redaction in the Oracle documentation.
ORA-28089: invalid SYS_CONTEXT namespace string in policy expression
Cause: The SYS_CONTEXT (or XS_SYS_CONTEXT) namespace used in the policy
expression was not valid.
Action: Modify the policy expression to use a valid namespace. Supported
namespaces include USERENV, SYS_SESSION_ROLES, XS$SESSION and the
namespaces listed in the DBA_CONTEXT catalog view.
ORA-28090: unsupported nesting of function string.string.string within function
string.string.string in policy expression
Cause: The policy expression had an unsupported PL/SQL function nesting.
Action: Modify the policy expression to use only supported PL/SQL function nesting.
The Oracle Label Security functions NUMERIC_LABEL, CHAR_TO_LABEL, and
SA_SESSION can only be used from within the Label Security dominates functions.
For a complete list of supported

Oracle Database 12c Error Messages

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Oracle Database 12c Error Messages

Caricato da

Copyright:

Formati disponibili

Oracle Database

Oracle Database Error Messages, 12c Release 1 (12.1)

Locating Message Documentation ................................................................................................

Oracle Database Messages ..................................................................................................

Product Specific Messages ..................................................................................................

Operating System-Specific Messages ................................................................................

Accuracy of Messages .....................................................................................................................

Message Format ...............................................................................................................................

Recognizing Variable Text in Messages .......................................................................................

Message Stacks .................................................................................................................................

Contacting Oracle Support Services .............................................................................................

Oracle Exception Messages ............................................................................................................

Trace Files .........................................................................................................................................

The Alert File ....................................................................................................................................

Boldface type indicates graphical user interface elements associated

Italic type indicates book titles, emphasis, or placeholder variables for

Monospace type indicates commands within a paragraph, URLs, code

1.1 Locating Message Documentation

1.1.1 Oracle Database Messages

1.1.2 Product Specific Messages

1.1.3 Operating System-Specific Messages

Using Messages 1-1

1.2 Accuracy of Messages

1.3 Message Format

1.4 Recognizing Variable Text in Messages

The preceding message might actually appear as follows:

1.5 Message Stacks

The following message stack is a VAX/VMS example:

1-2 Error Messages

Contacting Oracle Support Services

1.6 Contacting Oracle Support Services

1.7 Oracle Exception Messages

An actual message might appear as follows:

Using Messages 1-3

1.8 Trace Files

1.9 The Alert File

1-4 Error Messages

ACFS-00501 to ACFS-11111 2-1

ACFS-00514: unable to close handle

2-2 Error Messages

ACFS-00501 to ACFS-11111 2-3

2-4 Error Messages

ACFS-00501 to ACFS-11111 2-5

2-6 Error Messages

ACFS-00604: Failed to retrieve the Oracle Local Registry, OLR, configuration

ACFS-00501 to ACFS-11111 2-7

ACFS-00624: The path specified is too long.

2-8 Error Messages

ACFS-00501 to ACFS-11111 2-9

ACFS-01044: write of file entry table failed

2-10 Error Messages

ACFS-00501 to ACFS-11111 2-11

2-12 Error Messages

ACFS-00501 to ACFS-11111 2-13

2-14 Error Messages

ACFS-02127: unable to transfer mount data to the ACFS driver

ACFS-00501 to ACFS-11111 2-15

2-16 Error Messages

ACFS-03106: Invalid combination of arguments. stringa was previously specified to

ACFS-00501 to ACFS-11111 2-17

ACFS-03122: failed to create Oracle Registry ACFS key string string

2-18 Error Messages

ACFS-00501 to ACFS-11111 2-19

2-20 Error Messages