I summarized a list of (ORA) oracle error codes list with cause and
action, use browser find (CTRL+F) to get your desire error code, cause and
possible action.
Oracle
Database Error Messages (ORA-15000 - ORA-19000)
Her are the complete list of ORA error codes link
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-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 specified diskgroup could
not be mounted.
Action: Check for additional errors
reported.
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.
Action: Check that the ASM_DISKSTRING
parameter specifies only a single path for 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-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: The discovery encountered two
disks claiming to have the same ASM disk number.
Action: Check that the ASM_DISKSTRING
parameter specifies only a single path for each disk.
ORA-15025:
could not open disk 'string'
Cause: The specified disk could not
be opened.
Action: Check the additional error
messages, if any.
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 database client instances with
open files in the diskgroup. Diskgroups cannot be dismounted until all open
files in the diskgroup are closed by the database client instances.
Action: Stop all clients that are
using this diskgroup and retry the ALTER DISKGROUP ... DISMOUNT command. The
V$ASM_CLIENT fixed view in an ASM instance provides a list of its active
database client instances.
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 database instances and
therefore could not be dropped.
Action: Shut down all database
instances that might be accessing this file and then retry the drop command.
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 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, 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' size mismatch with diskgroup [string] [string]
[string]
Cause: An attempt was made to mount
into a diskgroup a disk whose recorded allocation unit size, metadata block
size, or physical sector size was inconsistent with the other diskgroup
members.
Action: Check if the system
configuration has changed.
ORA-15039:
diskgroup not dropped
Cause: An attempt to drop a diskgroup
failed.
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 space exhausted
Cause: The diskgroup ran out of
space.
Action: Add more disks to the
diskgroup, or delete some existing files.
ORA-15042:
ASM disk "string" is missing
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.
Action: Correct the specified ASM file
name.
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.
Action: Correct the specified ASM file
name.
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.
Action: See the alert log for details
of the errors.
ORA-15051:
file 'string' contains string error(s)
Cause: Errors were discovered by the
ALTER DISKGROUP CHECK FILE command.
Action: See the alert log for details
of the errors.
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 DROP
(or CHECK) 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.
Action: Correct the operating system
error and retry the operation.
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 availalable, 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.
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" 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 a
disk from a diskgroup 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 failure groups, discovered
only string
Cause: An attempt was made to create
either a normal redundancy diskgroup for which fewer than two failure groups
were both specified and discovered, or a high redundancy diskgroup for which
fewer than three failure groups 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.
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-15075:
disk(s) are not visible cluster-wide
Cause: An ALTER DISKGROUP ADD DISK
command specified a disk that could not be discovered by one or more nodes in a
RAC cluster configuration.
Action: Determine which disks are
causing the problem from the GV$ASM_DISK fixed view. Check operating system
permissions for the device and the storage sub-system configuration on each
node in a RAC cluster that cannot identify the disk.
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: Start an ASM instance and
mount the required diskgroup.
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 to a disk failed
Cause: A synchronous I/O operation
invoked on a disk has failed.
Action: Make sure that all 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 database instance
Cause: There was a failure when ASM
tried to communicate with a database 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 the ASM
instances may return this error when a database instance is terminated
abnormally.
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-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: Close the hanlde with
DBMS_DISKGROUP.CLOSE() before executing the command, or 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-15095:
reached maximum ASM file size (string GB)
Cause: An ASM file creation or file
resize operation exceeded the maximum file size permitted by ASM.
Action: Use smaller files.
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 RDBMS instance
Cause: A SHUTDOWN command was issued
to an ASM instance that had one or more connected RDBMS instances.
Action: Connect to each RDBMS instance
and shut it down, and then reissue the SHUTDOWN command to the ASM instance.
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.
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-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-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 '_'.
Action: Correct the file name
specification.
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.
Action: Correct the file name
specification.
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.
Action: Correct the file name
specification.
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.
Action: Correct the file name
specification.
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 '_'.
Action: Correct the file name
specification.
ORA-15126:
component within ASM file name 'string' exceeds maximum length
Cause: The maximum identifier length
of 30 characters was exceeded for the diskgroup name, template name, or alias
name field within the ASM file name.
Action: Correct the file name
specification.
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.
Action: Correct the file name
specification.
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.
Action: Correct the file name
specification.
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-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-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 sepcify 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:
cluster in rolling upgrade
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:
cluster not in rolling upgrade
Cause: The cluster was not in rolling
upgrade.
Action: Start the rolling upgrade
using the ALTER SYSTEM START ROLLING command.
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.
Action: Terminate or wait until the
reported operation is complete before attempting 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 not in rolling downgrade
Cause: The cluster was not in rolling
downgrade.
Action: Start the rolling downgrade
using the ALTER SYSTEM START ROLLING command.
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.
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.
Action: Terminate or wait until the
reported operation is complete before attempting 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.
Action: Correct the alias path and try
again.
ORA-15175:
cannot create alias for diskgroup metadata file 'string'
Cause: An attempt was made to create
an alias for a diskgroup metadata file.
Action: Correct the alias path and try
again.
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: Contact ASMLIB library vendor
support with the error details.
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-15192:
invalid ASM disk header [string] [string] [string] [string]
[string]
Cause: ASM encountered an invalid
disk header.
Action: Contact Oracle Support
Services.
ORA-15196:
invalid ASM block header [string:string] [string] [string]
[string] [string != string]
Cause: ASM encountered an invalid
metadata block.
Action: Contact Oracle Support
Services.
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
Cause: A disk specified in a CREATE
DISKGROUP or ALTER DISKGROUP ... ADD DISK command appeared to contain a file
from an existing database. By default, ASM will not allow a diskgroup to be
created using this disk, as a safeguard against damaging an existing database.
Action: Check that the ASM disk
specification is correct. Otherwise, when storage from a defunct database is
reused as part of an ASM diskgroup, specify the FORCE option to the ASM SQL
command.
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 database compatibility of
the diskgroup was advanced to a later version.
Action: Upgrade the database instance
to appropriate version of ORACLE.
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 ZONE 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-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 ZONE 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-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:
attribute string cannot be set in CREATE DISKGROUP
Cause: The specified attribute may
not be set with the CREATE DISKGROUP command.
Action: Check the attribute name or
use ALTER DISKGROUP SET ATTRIBUTE.
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.
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-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-15282:
ASM disk "string" is not visible cluster-wide
Cause: An ALTER DISKGROUP ONLINE
command specified a disk that could not be discovered by one or more nodes in a
RAC cluster configuration.
Action: Check operating system
permissions for the device and the storage sub-system configuration on each
node in the RAC cluster that cannot identify the disk.
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-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:
ASM disk string cannot be resized beyond string M
Cause: A resize disk command
specified a size beyond the maximum allowed for this disk.
Action: Check alert logs from all ASM
instances to identify the reason for the size limitation. If there are any 10g
database instances using this disk group, shut down those instances and retry
the resize operation.
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:
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-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-15463:
volume size of stringK is less then 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 name '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 is currently
operating on the specified volume.
Action: Wait a short time before
retrying the command.
ORA-15468:
operation not permitted; volume 'string' 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.
Action: Warm start instance.
ORA-15471:
volume redundancy incompatible with diskgroup redundancy
Cause: An ADD VOLUME command
specified a volume redundancy that was incompatible with the diskgroups
redundancy.
Action: Specify a valid volume
redundancy. A volume cannot have external redundancy with a high redundancy
diskgroup. Also, a volume cannot have high redundancy with an external
redundancy diskgroup.
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:
resize of OFS volume must use OFS resize command
Cause: An attempt was made to resize
an OFS volume through SQL.
Action: Use the supported OFS commands
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:
OFSC process terminated with error
Cause: The ofs background process
terminated with error
Action: Wait for process restart
ORA-15479:
diskgroup version incompatible with ASM volumes
Cause: The diskgroup's version was
incompatible with creating volumes.
Action: Upgrade the diskgroup version
in order to use volume functionality.
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 path to volume device file
Cause: Improper driver installation.
Action: Check the alert log for device
file creation failure information. Reload the driver using the supported
installation method.
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.
Action: Check the alert log and other
diagnostics in the given instance to diagnose the 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-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.
Action: Check the alert log and other
diagnostics in the given instance to diagnose the problem.
ORA-15507:
cannot start workload replay on instance string
Cause: Given instance encountered
unexpected errors while trying to start a workload replay.
Action: Check the alert log and other
diagnostics in the given instance to diagnose the problem.
ORA-15508:
cannot cancel workload replay on instance string
Cause: Given instance encountered
unexpected errors while trying to cancel a workload replay.
Action: Check the alert log and other
diagnostics in the given instance to diagnose the 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.
Action: Find the root cause or simply
preprocess the workload using only one process.
ORA-15518:
parallel preprocessing encountered an unexpected error
Cause: An unexpected error occured
during parallel preprocessing.
Action: Find the root cause or simply
preprocess the workload using only one process.
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
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.
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-15590:
encountered an incomplete workload capture file
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.
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.
Action: Specify a valid value for this
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-16000:
database open for read-only access
Cause: The database has been opened
for read-only access. Attempts to modify the database using inappropriate DML
or DDL statements generate this error.
Action: In order to modify the
database, it must first be shut down and re-opened 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
re-opened for read-only access.
ORA-16002:
database already open for read-write access by another instance
Cause: The 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
re-opened for read-write access.
ORA-16003:
standby database is restricted to read-only access
Cause: To ensure its integrity, a
standby database can only be opened for read-only access.
Action: Re-issue the ALTER DATABASE
OPEN specifying READ ONLY.
ORA-16004:
backup database requires recovery
Cause: The control file is for a
backup database which requires recovery, and cannot be opened for read-only
access by this instance.
Action: Perform the necessary recovery
and re-open 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 re-open for read-only access.
ORA-16006:
audit_trail destination incompatible with database open mode
Cause: The audit_trail initialization
parameter was set to "DB" (or TRUE), which is incompatible with a
database opened for read-only access.
Action: When the database is opened
for read-only access, the audit_trail initialization parameter can only be set
to "OS" or "NONE" (FALSE).
ORA-16007:
invalid backup control file checkpoint
Cause: The backup control file being
opened for read-only access does not contain a valid control file checkpoint.
Therefore the database cannot be opened for read-only access.
Action: First open the database for
read-write access which will result in valid control file checkpoint. Then
re-open the database 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 via CREATE CONTROLFILE.
Therefore a control file checkpoint could not be calculated and the database
cannot be opened for read-only access.
Action: First open the database for
read-write access which will result in valid control file checkpoint. Then
re-open the database for read-only access.
ORA-16009:
remote archive log destination must be a STANDBY database
Cause: The database associated with
the archive log destination service name is other than the required STANDBY
type database. Remote archival of redo log files is not allowed to non-STANDBY
database instances.
Action: Take the necessary steps to
create the required compatible STANDBY database before retrying the ARCHIVE LOG
processing.
ORA-16011:
Archivelog Remote File Server process in Error state
Cause: The archivelog remote file
server (RFS) process at the specified standby database site has experienced an
unrecoverable error and is unable to receive further archive log data.
Action: Correct the problem at the
standby database site.
ORA-16012:
Archive log standby database identifier mismatch
Cause: The database identifiers of
the Primary and Standby database do not match. Remote archival of redo log
files is not allowed to incompatible STANDBY database instances.
Action: Take the necessary steps to
create the required compatible STANDBY database before retrying the ARCHIVE LOG
processing.
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.
Action: No action is required.
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 archive failed because
there were no archive log destinations specified or all destinations
experienced debilitating errors.
Action: Verify that archive log destinations
are being specified and/or take the necessary step to correct any errors that
may have occurred.
ORA-16015:
log string sequence# string not archived,
media recovery disabled
Cause: An attempt was made to archive
the named log, but the archive was unsuccessful. A standby archive log
destination was specified and the database was not media recovery enabled. This
is not allowed.
Action: Disable the standby
destination or enable media recovery and retry.
ORA-16016:
archived log for thread string sequence# string unavailable
Cause: The managed standby database
recovery operation has timed out waiting for the requested archived log file.
Action: Verify that the primary
database is still archiving redo logs to the standby recovery database site and
reissue the RECOVER STANDBY DATABASE WAIT command.
ORA-16017:
cannot use LOG_ARCHIVE_DUPLEX_DEST without a 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...10)
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...10) 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.
Action: Eliminate any incompatible
parameter definitions.
ORA-16020:
less destinations available than specified by LOG_ARCHIVE_MIN_SUCCEED_DEST
Cause: With automatic archiving
enabled, the number of archive log destinations that could be used for the
database was less than the LOG_ARCHIVE_MIN_SUCCEED_DEST parameter value.
Action: Either adjust the settings of
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...10) 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-16024:
parameter string cannot be parsed
Cause: The value for the indicated
LOG_ARCHIVE_DEST_n (n = 1...10) 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...10) parameter contained either repeated attributes
or attributes that conflicted with each other.
Action: Correct the value for the
indicated LOG_ARCHIVE_DEST_n parameter.
ORA-16026:
parameter string contains an invalid attribute value
Cause: The value for the specified
LOG_ARCHIVE_DEST_n (n = 1...10) parameter contained an attribute with an invalid
value.
Action: Correct the value for the
indicated LOG_ARCHIVE_DEST_n parameter.
ORA-16027:
parameter string is missing a destination option
Cause: The value for the indicated
LOG_ARCHIVE_DEST_n (n = 1...10) parameter failed to include a destination
option. A destination option is specified using either the LOCATION or SERVICE
attrbute.
Action: Correct the value for the
indicated LOG_ARCHIVE_DEST_n parameter.
ORA-16028:
new string causes less destinations than
LOG_ARCHIVE_MIN_SUCCEED_DEST requires
Cause: With automatic archiving
enabled, an attempt was made to change the indicated LOG_ARCHIVE_DEST_n or a
LOG_ARCHIVE_DEST_STATE_n parameter (n = 1...10) 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 LOG_ARCHIVE_MIN_SUCCEED_DEST.
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...10). Then, change the value of parameter
LOG_ARCHIVE_MIN_SUCCEED_DEST.
ORA-16030:
session specific change 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...10)
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:
FROM parameter is incompatible with MANAGED recovery
Cause: Use of the FROM 'location'
parameter is not allowed when MANAGED recovery has been specified.
Action: Correct the syntax and retry
the command.
ORA-16035:
missing required keyword string
Cause: The indicated keyword is
required but was not specified.
Action: Correct the syntax and retry
the command.
ORA-16036:
invalid MANAGED recovery CANCEL option
Cause: A mode other than IMMEDIATE
follows 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.
Action: No action is required.
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.
Action: No action is required.
ORA-16039:
RFS request version mismatch
Cause: A request to archive a redo
log to a standby site failed because the request was incompatible with the
Remote File Server (RFS) at the standby site.
Action: Verify that compatible
versions of Oracle are running on the primary and all standby sites.
ORA-16040:
standby destination archive log file is locked
Cause: The target standby destination
archive log file is currently locked. This indicates that the file is being
archived to by another Remote File Server (RFS) process.
Action: Check for and eliminate
duplicate standby destination archive log service names defined for the primary
database.
ORA-16041:
Remote File Server fatal error
Cause: The Remote File Server (RFS)
process at the standby destination archive log site has encountered a disabling
error and is no longer available. Further archiving to the standby site may not
be possible.
Action: Refer to the appropriate RFS
trace file located at the standby site for details regarding the error
encountered and if possible take corrective action.
ORA-16042:
user requested cancel immediate of managed recovery operation
Cause: The managed standby database
recovery operation has been canceled immediately per user request. Processing
of the current archive log file has been interrupted and therefore the database
is in an inconsistent state.
Action: No action is required.
ORA-16043:
managed recovery session canceled
Cause: The standby database managed
recovery operation has been 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 archive log destination
attribute was attempted to be modified at the session level.
Action: Use the ALTER SYSTEM command
to modify the destination attribute.
ORA-16045:
circular archive log destination dependency chain
Cause: An archive log destination
contains a dependency to another archive log destination that also contains a
dependency.
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-16046:
Archive log destination failed due to failed dependent destination
Cause: The archive log destination is
dependent upon another destination, which has failed. Therefore, this
destination also fails.
Action: No action required.
ORA-16047:
DGID mismatch between destination setting and standby
Cause: The DB_UNIQUE_NAME specified
for the destination does not match the DB_UNIQUE_NAME at the destination.
Action: Make sure the DB_UNIQUE_NAME
specified in the LOG_ARCHIVE_DEST_n parameter defined for the destination
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.
Action: No action is required.
ORA-16051:
parameter string contains an invalid delay time
Cause: The value for the specified
LOG_ARCHIVE_DEST_n (n = 1...10) parameter contained a DELAY attribute with an
invalid numeric value. The valid range is 0-5760 (in minutes).
Action: Correct the value for the
indicated LOG_ARCHIVE_DEST_n parameter.
ORA-16052:
DB_UNIQUE_NAME attribute is required
Cause: The DB_UNIQUE_NAME attribute
is required when DG_CONFIG is enabled.
Action: Use the DB_UNIQUE_NAME
attribute to specify a valid Data Guard Name for the destination. The list of
valid DB_UNIQUE_NAMEs can be seen with the V$DATAGUARD_CONFIG view.
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: FAL server rejects the FAL
request from the FAL client. This may be caused by different reasons.
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: If the archival operation is
correct when using a backup control file, then the USING BACKUP CONTROLFILE
syntax is required.
ORA-16057:
DGID from server not in Data Guard configuration
Cause: The Data Guard name of the
primary database or the FAL server is not in the Data Guard configuration of
the standby.
Action: In order for the primary
database or the FAL server to archive logs to the standby database, the Data
Guard name of the primary or FAL server must be in the Data Guard configuration
of the standby.
ORA-16058:
standby database instance is not mounted
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-16059:
Log file is empty or invalid next available block
Cause: Archiving not allowed of an
empty or invalid log file.
Action: No action is required.
ORA-16060:
Log file is current
Cause: The current log file cannot be
archived using its file name.
Action: No action is required.
ORA-16061:
Log file status has changed
Cause: It is possible the online log
file was reclaimed as a new log file either before archival started, or during
the archival operation.
Action: No action is required.
ORA-16062:
DGID from standby not in Data Guard configuration
Cause: The Data Guard name from the
standby is not in the Data Guard configuration of the server.
Action: In order for the server to be
allowed to archive logs to the standby, the Data Guard name of the standby must
be in the Data Guard configuration of the server.
ORA-16063:
remote archival is enabled by another instance
Cause: Remote archival of database
REDO log files has been enabled by another instance, and cannot be disabled for
this instance.
Action: Set the REMOTE_ARCHIVE_ENABLE
parameter to TRUE and restart this instance.
ORA-16064:
remote archival is disabled by another instance
Cause: Remote archival of database
REDO log files has been disabled by another instance, and cannot be enabled for
this instance.
Action: Set the REMOTE_ARCHIVE_ENABLE
parameter to FALSE and restart this instance.
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: None
ORA-16069:
Archive Log standby database activation identifier mismatch
Cause: The activation identifiers of
the Primary and Standby database do not match. Remote archival of redo log
files is not allowed to incompatible STANDBY database instances. This can occur
when trying to apply an incorrect archive log to a standby database, or when
trying to archive to a standby database that does not match the primary
database.
Action: Take the necessary steps to
create the required compatible STANDBY database before retrying the ARCHIVE LOG
processing.
ORA-16070:
parameter string contains an invalid REGISTER attribute value
Cause: The value for the specified
LOG_ARCHIVE_DEST_n (n = 1...10) parameter 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:
dependency archived log file not found string
Cause: The specified archived log
file was not found at the indicated standby destination.
Action: Verify the correctness of the
dependency archived log file name template specified for the indicated standby
destination against the actual dependency archived log file.
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:
ARCH processes must be active
Cause: There are no active ARCH
processes.
Action: It is required that at least
one ARCH process be active.
ORA-16075:
standby database destination mismatch
Cause: A standby database destination
was specified that is not accessed by another instance.
Action: All database instances must
access the same standby databases.
ORA-16076:
unknown standby database destination
Cause: A standby database destination
was specified that is not accessed by another instance.
Action: All database instances must
access the same standby databases.
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 does not
have archival enabled.
Action: In order to allow the standby
database to access the standby log files, the ARCH process must be enabled and
active.
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:
standby database does not contain available standby log files
Cause: The primary database is in
"no data loss" mode, but the standby database does not contain any
"standby log files".
Action: Add one or more standby log
files to the standby database. This can be done while the standby database is
mounted.
ORA-16087:
graceful switchover requires standby or current control file
Cause: An attempt was made to perform
a graceful switchover operation using a backup or clone control file.
Action: Convert the backup control
file into a current control file prior to attempting a graceful switchover
operation. A clone control file cannot be used for a graceful 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
Cause: An archive log destination
contains a dependency to another archive log 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
Cause: An archive log destination
contains a dependency to another archive log 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 shutdown during archival operation
Cause: The database was shut down
while an online log file archival was active.
Action: None required. The ARCH
process is terminated.
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.
Action: None required.
ORA-16098:
inaccessible standby database forced shutdown to protect primary
Cause: No standby database archive
log destinations remain accessible and the primary database is in
"protected" no-data-loss mode.
Action: Specify an alternate standby
archive log destination in the initialization parameter file.
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-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: . Then, re-issue 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 event for diagnostic
purposes.
ORA-16112:
log mining and apply stopping
Cause: This logical standby process
is cleaning up and stopping Logical Standby apply.
Action: No action necessary, this
informational statement is provided to record the event for diagnostic
purposes.
ORA-16113:
applying change to table or sequence string
Cause: The process is applying
changes to a specific schema object.
Action: No action necessary, this
informational statement is provided to record the event for diagnostic
purposes.
ORA-16114:
applying DDL transaction with commit SCN string
Cause: The process is applying a DDL
change that's committed at the given SCN.
Action: No action necessary, this
informational statement is provided to record the event for diagnostic
purposes.
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.
Action: No action necessary, this
informational statement is provided to record the event for diagnostic
purposes.
ORA-16116:
no work available
Cause: The process is idle waiting
for additional changes to be made available.
Action: No action necessary, this
informational statement is provided to record the event for diagnostic
purposes.
ORA-16117:
processing
Cause: The process is performing its
primary function and is not waiting on any significant event.
Action: No action necessary, this
informational statement is provided to record the event for diagnostic
purposes.
ORA-16119:
building transaction at SCN string
Cause: The transaction being
committed at the given SCN is being prepared for apply.
Action: No action necessary, this
informational statement is provided to record the event for diagnostic
purposes.
ORA-16120:
dependencies being computed for transaction at SCN string
Cause: The transaction committed at
the given SCN is being analyzed for dependencies.
Action: No action necessary, this
informational statement is provided to record the event for diagnostic
purposes.
ORA-16121:
applying transaction with commit SCN string
Cause: The transaction committed at
the given SCN is being applied.
Action: No action necessary, this
informational statement is provided to record the event for diagnostic
purposes.
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.
Action: No action necessary, this
informational statement is provided to record the event for diagnostic
purposes.
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.
Action: No action necessary, this
informational statement is provided to record the event for diagnostic
purposes.
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.
Action: No action necessary, this
informational statement is provided to record the event for diagnostic
purposes.
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.
Action: No action necessary, this
informational statement is provided to record the event for diagnostic purposes.
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.
Action: No action necessary, this
informational statement is provided to record the event for diagnostic
purposes.
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.
Action: No action necessary, this
informational statement is provided to record the 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.
Action: No action necessary, this
informational statement is provided to record the event for diagnostic
purposes.
ORA-16129:
unsupported dml encountered
Cause: DML to tables in the SYS
schema have been updated and are not part of a DDL operation. This may be due
to some DBA activity or DML associated with a kernel PL/SQL request that
Logical Standby does not yet support.
Action: Check the DBA_LOGSTDBY_EVENTS
table for the name of the table being processed. Possibly use Log Miner to
understand the transaction, and provide a compensating transaction on the
standby system. Once complete, call DBMS_LOGSTDBY.SKIP_TRANSACTION with the
associated transaction id, and resume apply.
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.
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 re-issue 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:
standby destination control file enqueue unavailable
Cause: The target standby destination
control file is currently unavailable to the Remote File Server (RFS) process.
This indicates that the target destination is the primary database itself.
Action: Check for and eliminate the
standby destination archive log parameter in question.
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.
Action: No action is required.
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.
Action: No action is required.
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.
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.
Action: No action is required.
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 does not match the other member types. This problem
typically occurs when adding a standby log file member to an online redo
logfile 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
Action: The alert log contains more
problem-specific information
ORA-16165:
LGWR failed to hear from network server
Cause: The LGWR lost its connection
to the network server
Action: The alert log contains more
problem-specific information
ORA-16166:
LGWR network server failed to send remote message
Cause: The LGWR network server could
not communicate with the remote host
Action: The alert log contains more
problem-specific information
ORA-16167:
LGWR network server could not switch to non-blocking mode
Cause: The LGWR network server could
not switch to non-blocking mode
Action: The alert log contains more
problem-specific information
ORA-16168:
LGWR network server could not switch to blocking mode
Cause: The LGWR network server could
not switch to blocking mode
Action: The alert log contains more
problem-specific information
ORA-16169:
LGWR network server invalid parameters
Cause: The LGWR network server could
not switch to blocking mode
Action: The alert log contains more
problem-specific information
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 string-string
Cause: See alert log for more details
Action: Copy missing archived logs
from primary or another standby. Register the logs and re-issue 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: None
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.
Action: No action is required.
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 archivelog manual mode
Cause: The database is operating in
ARCHIVELOG MANUAL 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 the
larger of initialization parameters SHARED_POOL_SIZE and SGA_TARGET.
Action: Specify the value of MAX_SGA
to be less than the maximum of SHARED_POOL_SIZE and SGA_TARGET. Likely only 75%
or lower.
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-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.
Action: No action necessary, this
informational statement is provided to record the event for diagnostic
purposes.
ORA-16201:
Skip procedure requested to apply statement
Cause: Logical standby called a skip
procedure that requested for a particular statement to be applied.
Action: No action necessary, this
informational statement is provided to record the event for diagnostic
purposes.
ORA-16202:
Skip procedure requested to replace statement
Cause: Logical standby called a skip
procedure that requested for a particular statement to be replaced with a new
statement.
Action: No action necessary, this
informational statement is provided to record the event for diagnostic
purposes.
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.
Action: No action necessary, this
informational statement is provided to record the event for diagnostic
purposes.
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.
Action: No action necessary, this
informational statement is provided to record the event for diagnostic
purposes.
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.
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-16210:
Logical standby coordinator process terminated with error
Cause: The logical standby
coordinator process terminated abnormally.
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-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
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
Cause: internal error.
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 logfile 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
Cause: internal error.
Action: This is an internal error.
Contact Oracle support.
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 event for diagnostic
purposes.
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.
Action: No action is necessary. This
informational statement is provided to record the event for diagnostic
purposes.
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 Streams
Cause: An attempt was made to
register the log file for Streams 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 depends is not defined on the Logical Standby
database.
Action: No action is necessary, this
infomational statement is provided to record the event for diagnostic purposes.
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-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.
Action: No action necessary, this
informational statement is provided to record the event for diagnostic
purposes.
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.
Action: No action necessary. This
informational statement is provided to record the event for diagnostic
purposes.
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.
Action: No action necessary. This
informational statement is provided to record the event for diagnostic
purposes.
ORA-16236:
Logical Standby metadata operation in progress
Cause: The requested operation failed
because a Logical Standby metadata operation, such as
DBMS_LOGSTDBY.SET_TABLESPACE or DBMS_LOGSTDBY.INSTANTIATE_TABLE, has not
finished.
Action: Wait for the Logical Standby
metadata operation to finish, then re-enter 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 logfile (thread# string, sequence# string)
Cause: Reader process is idle waiting
for additional logfile to be available.
Action: No action necessary, this
informational statement is provided to record the event for diagnostic
purposes.
ORA-16241:
Waiting for gap logfile (thread# string, sequence# string)
Cause: Reader process is idle waiting
for the logfile to fill the log sequence gap.
Action: No action necessary, this
informational statement is provided to record the event for diagnostic
purposes.
ORA-16242:
Processing logfile (thread# string, sequence# string)
Cause: Reader process is processing
the logfile.
Action: No action necessary, this
informational statement is provided to record the event for diagnostic
purposes.
ORA-16243:
paging out string bytes of memory to disk
Cause: Builder process is paging out
momery to free up space in lcr cache.
Action: No action necessary, this
informational statement is provided to record the event for diagnostic
purposes.
ORA-16246:
User initiated abort apply successfully completed
Cause: SQL Apply was stopped using
the abort option.
Action: No action necessary, this
informational statement is provided to record the event for diagnostic
purposes.
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'.
Action: No action necessary, this
informational statement is provided to record the event for diagnostic
purposes.
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.
Action: This is an internal error.
Contact Oracle support.
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 incomplete terminal apply
Cause: A previous ACTIVATE of the
logical standby failed to complete.
Action: Reissue the ALTER DATABASE
ACTIVATE LOGICAL STANDBY DATABASE FINISH APPLY command.
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 logfile archival after failover
Cause: The standby redo logfiles
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.
Action: No action necessary, this
informational statement is provided to record the event for diagnostic
purposes.
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 EOR
logfile. A minimum of one destination is required.
Action: Ensure all log archive
destinations are properly configured and, if applicable, have network
connectivity before re-issuing the ALTER DATABASE COMMIT TO SWITCHOVER TO
LOGICAL STANDBY DDL operation.
ORA-16260:
Waiting to replace partial or corrupt logfile (thread# string,
sequence# string)
Cause: LogMiner Reader process
reached end of a partial logfile or encountered a corrupted block. It is now
waiting for the logfile to be recovered and re-registered.
Action: No action necessary. Once the
FAL archiver replaces the logfile, standby will automatically restart to process
the replaced file.
ORA-16261:
Identification key mismatch for table "string"."string".
Cause: Internal error in SQL Apply.
Action: Contact Oracle Support
Services.
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 re-issue 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-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.
Action: No action necessary. This
informational statement is provided to record the event for diagnostic
purposes.
ORA-16271:
PL/SQL successfully applied
Cause: A PL/SQL procedure was
successfully applied on the logical standby database.
Action: No action necessary, this
informational statement is provided to record the event for diagnostic
purposes.
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.
Action: No action necessary, this
informational statement is provided to record the event for diagnostic
purposes.
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 DDL on all RAC instances
Cause: One or more instances
encountered an error while performing an operation.
Action: Ensure every instance in the
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.
Action: No action is necessary. This
informational statement is provided to record the event for diagnostic
purposes.
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 must have CONNECT, RESOURCE, and SELECT_CATALOG_ROLE roles
Cause: A dblink was specified to
DBMS_LOGSTDBY.INSTANTIATE_TABLE that lacked one or more of the CONNECT,
RESOURCE, or SELECT_CATALOG_ROLE roles.
Action: Grant the CONNECT, RESOURCE,
and SELECT_CATALOG_ROLE roles to the specified dblink, 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-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.
Action: No action is required.
ORA-16401:
archivelog rejected by RFS
Cause: An attempt was made to
re-archive an existing archivelog. This usually happens because either a
multiple primary database or standby database(s) or both are trying to archive
to this standby database.
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:
ONDEMAND archival requires FAL_CLIENT and FAL_SERVER support
Cause: The archivelog destination
TRANSPORT=ONDEMAND attribute was specified on the primary database. Use of the
TRANSPORT=ONDEMAND attributes requires that the corresponding standby database
explicitly specify the FAL_CLIENT and FAL_SERVER initialization parameters.
Action: Make sure the FAL_CLIENT and
FAL_SERVER initialization parameters are explicitly specified on the standby
database that received this error.
ORA-16403:
shutdown in progress - remote connection is not permitted
Cause: The SHUTDOWN command was used
to shut down a running remote primary or standby ORACLE instance, so the LGWR
or ARCH processes cannot connect to ORACLE.
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 database and
standby database Oracle software is not compatible.
Action: Install the correct Oracle
software and try again.
ORA-16407:
Standby database is in the future of the archive log
Cause: An archive log, from a
different Redo Branch, was received by a standby database that has applied Redo
in the future of Redo contained within the archive log. The standby database
has rejected the REDO Branch archive logs.
Action: No action is required.
ORA-16408:
Incompatible archival Redo Branch lineage
Cause: An archive log, from an
incompatible different Redo Branch, was received by a standby database. The
standby database has rejected the Redo Branch archive logs.
Action: No action is required.
ORA-16409:
Archive log switchover reference number mismatch
Cause: The archive log switchover
reference numbers of the Primary and Standby database do not match. Remote
archival of redo log files is not allowed to incompatible STANDBY database
instances.
Action: No action is required.
ORA-16411:
ONDEMAND archival requires active managed recovery operation
Cause: The use of the ONDEMAND
attribute for a physical standby database destination requires that the managed
recovery operation be active prior to establishing the network connection.
Action: Start the managed recovery
operation on the standby database.
ORA-16412:
ONDEMAND archival requires active SQL apply operation
Cause: The use of the ONDEMAND
attribute for a logical standby database destination requires that the SQL
apply operation be active prior to establishing the network connection.
Action: Start the SQL apply operation
on the standby database.
ORA-16413:
Unsupported database type for ONDEMAND archivelog destinations
Cause: The use of the ONDEMAND
attribute for a standby database destination is supported for only physical and
logical standby database types. Cross-Instance-Archival and repository database
types are not valid for the ONDEMAND attribute.
Action: Verify the database
corresponding to the archivelog destination is either a physical standby
database or a logical standby database.
ORA-16416:
Switchover target is not synchronized with the primary
Cause: The switchover target incurred
an error or has a gap at the time the switchover operation was attempted.
Action: Allow the switchover target to
become synchronized and then re-attempt 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 from physical standby
Cause: The database is not physical
standby.
Action: Convert to physical standby
and retry the operation.
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:
Terminal recovery cannot start due to GAP on Physical Standby
Cause: Terminal Recovery failed
because of gap behind the start point of standby recovery.
Action: Issue ALTER DATABASE ACTIVATE
STANDBY DATABASE
ORA-16425:
Terminal recovery branch string older than target branch string
Cause: Terminal Recovery failed
because of new branch on Physical Standby.
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 terminal recovery.
Otherwise, issue ALTER DATABASE ACTIVATE STANDBY DATABASE
ORA-16426:
log requested by recovery is not the correct log
Cause: Media recovery has selected an
incorrect log
Action: Verify that the proper log has
been properly registered and restart media recovery.
ORA-16427:
Potential archive log gap too large to service
Cause: Standby destination is too far
behind the primary database for automatic archive log gap detection/resolution
to take place.
Action: Standby database should be
recreated with a recent backup copy of the primary database.
ORA-16431:
Cannot expand control file
Cause: More threads were added on the
primary database after this standby control file was created.
Action: Shut down the standby
database, either replace the control file with a new standby control file from
primary database or change the COMPATIBLE parameter to 10.2.0 or above, and
restart the standby database.
ORA-16432:
inconsistent set of terminal logs detected
Cause: Media Recovery stopped because
it detected an inconsistency between the first log in the new incarnation and
the state of the previous incarnation. If this database is a bystander standby
database, this is most likely because there was a failover operation, and this
database applied terminal logs generated from that failover operation for some
redo threads but applied corresponding logs from the old primary database of
that failover operation for some other redo threads.
Action: Flashback or restore this
database to before the standby_became_primary_scn of that failover operation
and restart media recovery. The standby_became_primary_scn of the failover
operation can be obtained from V$DATABASE on the new primary.
ORA-16433:
The database has not been opened in read-write mode
Cause: When a physical standby
database is converted to a read-write database or there was a failed open
resetlogs attempt, the database should be opened in read-write mode to have
correct file access information in the controlfile.
Action: Open the database in
read-write mode and reissue the command.
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-16501:
the Data Guard broker operation failed
Cause: The Data Guard broker
operation failed.
Action: See accompanying messages for
details.
ORA-16502:
the Data Guard broker operation succeeded with warnings
Cause: The Data Guard broker
operation succeeded with warnings.
Action: See accompanying messages for
details.
ORA-16504:
the Data Guard configuration already exists
Cause: A request to create a 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-16505:
site ID is invalid
Cause: The request contained an
invalid site ID.
Action: Make the request again with a
valid site ID.
ORA-16506:
out of memory
Cause: Process exceeded private or
shared memory limits.
Action: Check for memory leaks,
increase system parameters and restart.
ORA-16507:
unrecognized request identifier
Cause: The specified request
identifier was not recognized by the Data Guard broker.
Action: Reissue the request using a
valid request identifier.
ORA-16509:
request timed out
Cause: The Data Guard broker timed
out out the request.
Action: Check the 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
Action: Wait for the broker to
complete processing the requests before issuing more requests.
ORA-16514:
request was not found
Cause: An attempt was made to read a
response but a matching request was not found.
Action: Verify request identifier is
valid and that it references a previously issued request.
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-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 operation
Cause: A command or option was not
supported in this release.
Action: Contact Oracle Support
Services.
ORA-16525:
the Data Guard broker is not yet available
Cause: The 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 Data Guard log for possible errors. Otherwise, retry the
operation.
ORA-16526:
unable to allocate task element
Cause: The Data Guard broker was
unable to allocate memory for a request.
Action: Increase the size of the SGA.
ORA-16527:
unable to allocate broker SGA memory
Cause: The Data Guard broker was
unable to allocate memory within the SGA.
Action: Increase the size of the SGA
memory.
ORA-16528:
unable to allocate PGA memory
Cause: There was insufficient space
in 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:
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.
ORA-16534:
no more requests accepted
Cause: The Data Guard broker returned
this status because either:
- A
failover operation was submitted or was in progress.
- A
switchover operation was submitted or was in progress.
- An
instance restart was pending for one or more databases.
Action: Wait until the operation is
complete and reissue the request.
ORA-16535:
CRS is preventing execution of a broker operation
Cause: The broker was unable to have
CRS stop management of all of the instances of this database.
Action: Suspend CRS management of this
database using the SRVCTL STOP DATABASE -D -O NONE command. Then
reissue the broker request.
ORA-16541:
database is not enabled
Cause: The database specified in the
request was not enabled.
Action: Select an enabled database and
reissue the request.
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-16545:
unable to get response
Cause: The Data Guard broker was
unable to return the result of a previous request.
Action: Contact Oracle Support
Services.
ORA-16546:
missing or invalid value
Cause: The value of the request to
return was not specified or was invalid.
Action: Specify the value of the
response starting from one.
ORA-16547:
cannot disable or delete the primary database
Cause: An attempt was made to disable
broker management of the primary database or delete 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 delete the primary database from the broker configuration while the
configuration is enabled, you must instead delete 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 request.
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.
Action: This is an informational
message only.
ORA-16552:
an error occurred when generating the CLIENT OPERATION table
Cause: An error occurred while Data
Guard broker was generating the CLIENT OPERATION table.
Action: See the next error message for
more detailed information. Execute the action described in the next error or
contact Oracle Support Services.
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.
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-16569:
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 Data Guard
configuration and reissue the request.
ORA-16570:
database needs restart
Cause: The 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, shutdown the Oracle instance and then restart
it.
ORA-16571:
Data Guard configuration file creation failure
Cause: The 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:
Data Guard configuration file not found
Cause: The 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.
ORA-16573:
attempt to change or access configuration file for an enabled broker
configuration
Cause: The operation was rejected
because the 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 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 at broker discretion
Cause: This error was returned when
the broker terminated a command because it was processing a failover command.
Action: Wait for failover to complete
and then retry the command.
ORA-16576:
failed to update Data Guard configuration file
Cause: A failure was encountered
while the broker was updating the Data Guard broker configuration file on
permanent storage.
Action: Verify space, permissions and
file name as indicated by the DG_BROKER_CONFIG_FILE[1|2] initialization
parameters.
ORA-16577:
corruption detected in Data Guard configuration file
Cause: The Data Guard broker detected
errors while loading the configuration file.
Action: Verify space, permissions and
file name as indicated by the 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.
Action: Verify space, permissions and
file name as indicated by the 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-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 an 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-16589:
Data Guard broker detected network transfer error
Cause: The 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.
Action: Contact Oracle Support
Services.
ORA-16594:
DMON background process is not running
Cause: The Data Guard broker
background process, DMON, was not running.
Action: Check the Data Guard broker
log 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.
Action: Contact Oracle Support
Services.
ORA-16596:
database not part of the Data Guard broker configuration
Cause: The specified database is not
in the Data Guard broker configuration.
Action: Retry the command with a
database that is in the broker configuration.
ORA-16597:
Data Guard broker detects two or more primary databases
Cause: The Data Guard broker detected
two or more primary databases in the broker configuration and could not
continue.
Action: Contact Oracle Support
Services.
ORA-16598:
Data Guard broker detected a mismatch in configuration
Cause: The 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.
Action: Contact Oracle Support
Services.
ORA-16599:
Data Guard broker detected a stale configuration
Cause: The 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:
Data Guard broker detected a mismatch in configuration ID
Cause: There was a mismatch in
configuration unique ID. 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 Data Guard
broker configuration files. Finally restart the broker by setting the
DG_BROKER_START initialization parameter to true.
ORA-16606:
unable to find property "string"
Cause: The specified property did not
exist.
Action: Specify a valid property name
and reissue the request.
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 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.
Action: No action required.
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-16613:
initialization in progress for database
Cause: A request was made to modify
the Data Guard broker configuration before the Data Guard broker had completed
initialization.
Action: Wait until the Data Guard
broker has completed initialization before attempting to modify the broker
configuration.
ORA-16614:
Data Guard broker configuration is disabled
Cause: An attempt to enable a
database failed because the Data Guard broker configuration was disabled.
Action: Enable the 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 reissue the request.
ORA-16619:
health check timed out
Cause: The standby database could not
be reached during a routine health check.
Action: This typically indicates a
network problem where the standby database is unable to respond to the primary
database within a predefined time frame. Check the network connections between
the primary and standby databases.
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 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 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 datbases in the broker configuration are running the
same version of Oracle, reenable the standby databases that were disabled.
ORA-16625:
cannot reach the database
Cause: The command could not be
executed because the database required to complete the command was not
reachable from the database where the command was issued. If the command
modifies the configuration, the command must be processed by the copy of the
broker running on an instance of the primary database.
Action: Check the network connections
between all of the databases in the configuration. Alternatively, connect to a
different database in the Data Guard broker configuration and retry the
command. If an attempt was made to determine the status of a particular
database in the configuration, connect to that database and get the current
value of the StatusReport property for that database.
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 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 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 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 Data Guard broker.
ORA-16629:
database reports a different protection level from the protection mode
Cause: The actual or current database
protection level was different from the configured protection mode. This
typically is caused by redo transport problems.
Action: Check the database alert logs
and Data Guard broker logs 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.
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 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 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 the database cannot be removed
Cause: The instance to be removed was
the only instance of the corresponding database that was known to the broker.
Action: Remove the corresponding
database object from the broker configuration instead of the individual
instance object of the database.
ORA-16635:
network connection failed during transmission
Cause: The 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 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:
an instance failed to access the Data Guard broker configuration
Cause: The broker could not access
the broker configuration files on one or more database instances. This can
happen when the DG_BROKER_CONFIG_FILE[1|2] initialization parameter values are
not to the same set of file locations for a RAC database.
Action: Shut off the broker by setting
the DG_BROKER_START initialization parameter to false. Then set the
DG_BROKER_CONFIG_FILE1 and DG_BROKER_CONFIG_FILE2 initialization parameters to
file locations that are shared by all instances of a RAC database. Finally,
restart the broker by setting the DG_BROKER_START initialization parameter to
true.
ORA-16638:
could not get the 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-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-16640:
CRS warns that multiple instances may still be running
Cause: The broker failed to have CRS
stop instance monitoring and shut down all but one instance. CRS instance
monitoring did stop, but CRS may not have been able to shut down all but one
instance. The broker operation was canceled.
Action: Suspend CRS management of this
database using SRVCTL STOP DATABASE -D -O NONE. Reissue the broker
request.
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 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:
unexpected new instance interrupted current operation
Cause: A new instance unexpectedly
joined the Data Guard configuration at a point when the current operation may
proceed only if the set of known instances is not changing dynamically.
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 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 Data Guard broker and will begin observing the Data Guard
configuration for conditions that warrant doing a fast-start failover.
Action: None
ORA-16649:
possible failover to another database prevents this database being opened
Cause: An attempt to open the
database was made either when a failover occurred or while fast-start failover
was enabled and the fast-start failover status could not be evaluated.
Action: Check if a failover did occur.
If fast-start failover is enabled, and a failover did not occur, ensure that
connectivity exists between this database and either the observer or the target
standby database. Then, try opening the database again.
ORA-16650:
command incompatible when fast-start failover is enabled
Cause: An attempt was made to issue a
command that is not permitted when fast-start failover is enabled. The command
was not issued using the Data Guard broker.
Action: The command must be issued
using the Data Guard broker.
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 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 SYNC 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 Data Guard configuration.
Action: Retry the command after
correcting the issue:
- Set the
Data Guard configuration to either MaxAvailability or MaxPerformance protection
mode.
- Ensure
that the LogXptMode property for both the primary database and the fast-start
failover target standby database are set to SYNC 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 the desired target standby database
FastStartFailoverTarget property to the DB_UNIQUE_NAME value of the primary
database.
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 FAST_START FAILOVER FORCE command.
Consult the documentation for more information.
ORA-16653:
failed to reinstate database
Cause: The Data Guard broker failed
to reinstate the specified database because the REINSTATE command failed or
because the database is 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:
Data Guard broker detected role change
Cause: The Data Guard broker detected
a role during database startup or health check.
Action: Additional information about
this failure is recorded in the Data Guard broker log files, one for the
primary database and one for each standby database in the 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 switchover or failover
operation has caused this database to require reinstatement.
Action: Use the DGMGRL REINSTATE
DATABASE command or Enterprise Manager to reinstate the database. If the target
database has flashback enabled and it has sufficient flashback logs, the
database will be reinstated as a standby database for the current primary
database.
ORA-16662:
network timeout when contacting a database
Cause: In response to the issued
command, the Data Guard broker attempted to contact a database in the Data
Guard configuration. That attempt failed because there was no response from
that database after the period of time specified by the NetTimeout property for
that database.
Action: Check the Data Guard broker
log 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 Data Guard broker configuration failed to return a result.
Action: Check Data Guard broker logs
for the details of the failure. Fix any possible network problems and try the
command again.
ORA-16665:
timeout waiting for the result from a database
Cause: The Data Guard broker was
forced to time out a network connection
Action: Check Data Guard broker logs
for the details of the failure. Fix any possible network problems and reissue
the command.
ORA-16666:
unable to initiate fast-start failover on a standby database
Cause: The request to initiate a
fast-start failover using DBMS_DG.INITIATE_FS_FAILOVER was made to a standby
database. An application may only request that fast-start failover be initiated
by calling DBMS_DG.INITIATE_FS_FAILOVER on a primary database.
Action: Call
DBMS_DG.INITIATE_FS_FAILOVER on the primary database.
ORA-16667:
request Data Guard broker client to reissue command
Cause: The 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 Data Guard
broker manually.
ORA-16668:
operation invalid on fast-start failover target database
Cause: The attempted command was not
allowed on the fast-start failover target standby database when fast-start
failover is currently enabled.
Action: Retry the attempted command on
a database other than the fast-start failover target standby database.
Alternatively, disable fast-start failover and reissue the same command to the
fast-start failover target standby database.
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:
Data Guard broker command failed
Cause: Command to modify or query the
database failed.
Action: Check the Data Guard broker
log for the reason for the failure, and reissue the command.
ORA-16702:
Data Guard broker command warning
Cause: A command to modify or query
the database resulted in a warning.
Action: Check the Data Guard broker
log for the warning and, if necessary, reissue the command.
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:
cannot modify a read-only property
Cause: An attempt was made to change
a read-only property.
Action: The property is controlled
internally by the Data Guard broker and cannot be modified.
ORA-16706:
no resource guard is available
Cause: Resource guard was not
available to service the request.
Action: Contact Oracle Support
Services.
ORA-16707:
the value of the property string is invalid, valid values
are string
Cause: An invalid property value was
entered 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 request.
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-16713:
the Data Guard broker command timed out
Cause: The 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.
Action: Contact Oracle Support
Services.
ORA-16717:
clearing parameter LOG_ARCHIVE_DUPLEX_DEST failed
Cause: An attempt to clear the
LOG_ARCHIVE_DUPLEX_DEST parameter failed.
Action: Contact Oracle Support
Services.
ORA-16718:
failed to locate database
Cause: The 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.
Action: Clear one or more
LOG_ARCHIVE_DEST_n initialization parameters so that broker can use them to
setup 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 Data Guard broker
log and Oracle alert logs 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 Data Guard broker
log and Oracle alert logs 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-16727:
cannot close database
Cause: The Data Guard broker could
not close the database.
Action: Terminate any active sessions
connected to the database and then reissue the request.
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:
error executing DBMS_LOGSTDBY.SKIP_TXN procedure
Cause: Logical standby database
package may not be installed.
Action: Install logical standby
database packages and reissue the request.
ORA-16731:
error executing DBMS_LOGSTDBY.UNSKIP_TXN procedure
Cause: Logical standby database
package may not be installed.
Action: Install logical standby
database packages and reissue the request.
ORA-16732:
error executing DBMS_LOGSTDBY.SKIP procedure
Cause: Logical standby database
package may not be installed.
Action: Install logical standby
database packages and reissue the request.
ORA-16733:
error executing DBMS_LOGSTDBY.UNSKIP procedure
Cause: Logical standby database
package may not be installed.
Action: Install logical standby
database packages and reissue the request.
ORA-16734:
error executing DBMS_LOGSTDBY.SKIP_ERROR procedure
Cause: Logical standby database
package may not be installed.
Action: Install logical standby
database packages and reissue the request.
ORA-16735:
error executing DBMS_LOGSTDBY.UNSKIP_ERROR procedure
Cause: Logical standby database
package may not be installed.
Action: Install logical standby
database packages and reissue the request.
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 Data Guard broker, or no entry was
available for the 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 Data Guard broker log and Oracle
alert log 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 Data Guard broker
log and/or the alert log 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 Data Guard broker
log 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 transport-related 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 Data Guard broker
log and Oracle alert log 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 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 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:
Data Guard broker cannot mount the database
Cause: The Data Guard broker failed
to mount the database."
Action: Check the Data Guard broker
log and Oracle alert log for more details.
ORA-16747:
logical standby database guard could not be turned on
Cause: The Data Guard broker could
not turn on the logical standby database guard.
Action: Check the Data Guard broker
log and Oracle alert log for more details.
ORA-16748:
Data Guard broker cannot open the primary database
Cause: The Data Guard broker failed
to open the primary database" the database.
Action: Check the Data Guard broker
log and Oracle alert log for more details.
ORA-16749:
switchover to logical standby database failed
Cause: The Data Guard broker failed
to switch a logical standby database over to a primary database.
Action: Check the Data Guard broker
log and Oracle alert log for more details.
ORA-16750:
failed to activate logical standby database
Cause: The Data Guard broker failed
to activate a logical standby database.
Action: Check the Data Guard broker
log and Oracle alert log for more details.
ORA-16751:
failed to switchover to physical standby database
Cause: The Data Guard broker failed
to switch a physical standby database over to a primary database.
Action: Check the Data Guard broker
log and Oracle alert log for more details.
ORA-16753:
Data Guard broker cannot open standby database
Cause: The Data Guard broker failed
to open the standby database.
Action: Check the Data Guard broker
log and Oracle alert log for more details.
ORA-16754:
failed to activate physical standby database
Cause: The Data Guard broker failed
to activate the physical standby database.
Action: Check the Data Guard broker
log and Oracle alert log for more details.
ORA-16755:
failed to set initialization parameter
Cause: The Data Guard broker failed
to set an initialization parameter using either the ALTER SYSTEM SET or ALTER
SYSTEM RESET command.
Action: Check the Data Guard broker
log and Oracle alert log for more details.
ORA-16757:
unable to get this property's value
Cause: The Data Guard broker failed
to get the value for the specified property, possibly because the specified
property's value is not available for the current database role.
Action: If the specified property's
value is not available for the database's current role, please specify this
property for a database for which it is available. Otherwise, check the Data
Guard broker log for more details.
ORA-16758:
the specified apply instance is not running
Cause: The 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 Data Guard broker failed
to start SQL Apply with an initial SCN.
Action: Check the Data Guard broker
log and Oracle alert log for more details.
ORA-16760:
cannot start SQL Apply
Cause: The Data Guard broker failed
to start SQL Apply.
Action: Check the Data Guard broker
log and Oracle alert log for more details.
ORA-16761:
cannot stop SQL Apply
Cause: The Data Guard broker failed
to stop SQL Apply.
Action: Check the Data Guard broker
log and Oracle alert log for 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 standby database is running
Cause: The redo transport service for
a standby database was running.
Action: Query the StatusReport
property of the primary database for more details. If necessary, stop the redo
transport service for the database.
ORA-16764:
redo transport service to a standby database is not running
Cause: The redo transport service to
a standby database was not running.
Action: Query the StatusReport
property of the primary database for more details. If necessary, start the redo
transport service.
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: If necessary, start Redo
Apply.
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: If necessary, start SQL Apply.
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
Data Guard broker will start Redo Apply services once the physical standby
database has been opened.
Action: No action required.
ORA-16771:
failover to a physical standby database failed
Cause: The Data Guard broker
encountered errors when converting a physical standby database to a primary
database.
Action: Check the Data Guard broker
log and the Oracle alert log for more details about the error.
ORA-16772:
switchover to a standby database failed
Cause: The Data Guard broker
encountered errors when switching over to the specified standby database.
Action: Check the Data Guard broker
log and Oracle alert log for more details.
ORA-16773:
cannot start Redo Apply
Cause: The Data Guard broker failed
to start Redo Apply.
Action: Check the Data Guard broker
log and Oracle alert log for more details. If the database is already open, the
broker will not be able to start Redo Apply if the COMPATIBLE initialization
parameter is set to a value less than 11.0.
ORA-16774:
cannot stop Redo Apply
Cause: The Data Guard broker failed
to stop Redo Apply.
Action: Check the Data Guard broker
log and Oracle alert log for 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 the StatusReport monitorable property. 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 Data Guard broker could
not complete the health check for the redo transport service.
Action: Check the Data Guard broker
log and Oracle alert log for 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 Data Guard.
Action: Check the Data Guard broker
log and the Oracle alert log for 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.
Action: Check the Data Guard broker
log and Oracle alert log for 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 Data
Guard broker failed to update the destination when the redo transport was
turned on.
Action: Check the Data Guard broker
log 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 Data Guard broker
log 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.
Action: Check the Data Guard broker
log and Oracle alert log for 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: Check the StatusReport property
for more details and, if possible, open the instance manually.
ORA-16783:
instance string not open for read and write access
Cause: The database was mounted on an
instance but not opened for read and write access.
Action: Check the StatusReport property
for more details and, if possible open the instance manually.
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 Data Guard broker metadata
Cause: The Data Guard broker configuration
files did not exist or for some other reason the Data Guard broker
configuration metadata could not be accessed.
Action: Check the Data Guard broker
log for more details.
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 Data Guard broker
log to see which property has the problem and set the property to the correct
value.
ORA-16789:
standby redo logs not configured
Cause: Standby redo logs were not
configured for the database.
Action: Standby redo logs are required
when the redo transport mode is set to SYNC or ASYNC. Check the Data Guard
documentation to see how to create standby redo logs.
ORA-16790:
the value of the configurable property is invalid
Cause: An invalid property value was
entered.
Action: Reset 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
Data Guard broker.
Action: Query the
InconsistentProperties property on the database or check the Data Guard broker
log 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 database
Cause: The broker was unable to
import property values for the database being added to the broker
configuration. This error indicates:
- The
Oracle Net service name specified in DGMGRL CREATE CONFIGURATION or ADD
DATABASE command was not one that provides access to the database being added.
- There
were no instances running for the database being added.
Action: Remove the database from the
configuration using the REMOVE CONFIGURATION or REMOVE DATABASE command. Make
sure that the database 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 or ADD DATABASE command.
ORA-16797:
database is not using a server parameter file
Cause: The database 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 database to use it.
ORA-16798:
unable to complete terminal recovery on the standby database
Cause: Terminal recovery on the
standby database failed during the failover operation.
Action: Check the Data Guard broker
log and the Oracle alert logs to see more details on the reason for the
failure.
ORA-16799:
Redo Apply is not running
Cause: Either the Data Guard broker
metadata indicates that Redo Apply was turned off, or the recovery process,
MRP0, was not running. As a result, Redo Apply-related properties could not be
set.
Action: Turn on Redo Apply through
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-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 Data Guard broker.
Action: Query the
InconsistentLogXptProps property on the primary database or check the Data
Guard broker log 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 a RAC database. This was not 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: Failed to query a database
table or fixed view. The database may not be opened or mounted.
Action: Check the Data Guard broker
log for more details.
ORA-16804:
one or more configuration properties in metadata have invalid values
Cause: 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
for more details on which properties have invalid values and reset them through
the 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 be the primary database.
Action: Check the Data Guard broker
log 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.
Action: Check the Data Guard broker
log and the Oracle log for more information.
ORA-16808:
primary database is not open
Cause: A prior attempt to open the
primary database was disallowed because the fast-start failover status could
not be evaluated. The fast-start failover status has since been evaluated and
the 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: Check the StatusReport
monitorable property of the specifed database to get a detailed status report.
ORA-16810:
multiple errors or warnings detected for the database
Cause: The broker detected multiple
errors or warnings for the database.
Action: Check the StatusReport
monitorable property of the specified database to get a detailed status report.
ORA-16811:
apply instance not recorded by the 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.
Action: Reenable the standby database
to clear the error.
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.
Action: Reenable the standby database
to clear the error.
ORA-16814:
incorrect redo transport setting for AlternateLocation for standby database
Cause: The 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 logs 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 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 logs 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 Data Guard broker detected
that the specified database had a database role that was different from the
database role recorded in the Data Guard configuration. This could be the
result of a failed switchover or failover operation, or an out-of-band
switchover or failover operation done to the database.
Action: Manually fix the database to
convert it to the appropriate database role, then issue an ENABLE DATABASE
command to reenable the database.
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 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 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.
Action: Check the StatusReport
monitorable property of the database specified.
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.
Action: Check the StatusReport
monitorable property of the database specified.
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 fast-start
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 trasmitting 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 disallowed on this standby database type
Cause: The Data Guard broker
operation was disallowed on the standby database type.
Action: Check the documentation for
the correct standby database type and reissue the Data Guard broker command to
another standby database that is of the correct standby database type.
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: None
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-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: None
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: None
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: None
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-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.
Action: check additional error
messages
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.
Action: check additional error
messages
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.
Action: check additional error
messages
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: None
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-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.
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.
Action: Check additional error
messages
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.
Action: Check additional error
messages
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-18000:
invalid outline name
Cause: The parser detected a missing
or invalid outline name
Action: None
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: None
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: None
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-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-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
