ORA-19851: OS error while managing auxiliary
database string
Cause:
An OS error was received while managing the automatic auxiliary instance.
Action:
Check the accompanying errors.
ORA-19852: error creating services for auxiliary
instance string (error string)
Cause:
An error was received while managing the services of the auxiliary instance.
Action:
Check the accompanying errors.
ORA-19853: error preparing auxiliary instance string
(error string)
Cause:
An error was received while managing the automatic auxiliary instance.
Action:
Check the accompanying errors.
ORA-19854: error obtaining connect string from
target
Cause:
Could not obtain the connect string from the target database
Action:
Check the accompanying errors.
ORA-19860: piece validation cannot be performed
more than once
Cause:
The user attempted to validate a list of backup pieces more than once.
Validation may only be performed once for a given validation conversation.
Action:
Do not attempt to validate the pieces more than once.
ORA-19861: additional backup pieces cannot be
validated in this conversation
Cause:
The user tried to add new pieces to the list of files being validated after the
validation had already been performed. In a validation conversation, the list
can only be validated once.
Action:
Add all the backup pieces to the list before validating, or start a new
validation conversation for the remaining pieces.
ORA-19862: backup pieces must be validated before
accessing results
Cause:
The user tried to get validation results for backup pieces before the pieces
were actually validated.
Action:
Validate the pieces before trying to access the results.
ORA-19863: device block size string is
larger than max allowed: string
Cause:
The user specified a device BLKSIZE that is larger than the device BLKSIZE
specified during compressed backup.
Action:
Change the device BLKSIZE to be smaller than the maximum allowed.
ORA-19865: Backup piece string has no data
Cause:
No data was returned for the specified backup piece.
Action:
This normally indicates a problem with the media management software which is
linked with Oracle to provide backup and restore services. Contact the media
management software vendor.
ORA-19866: error writing file header for datafile string
Cause:
During a block recovery, the header of the datafile could not be updated.
Action:
Contact Oracle Support Services.
ORA-19870: error while restoring backup piece string
Cause:
This error should be followed by other errors indicating the cause of the
problem.
Action:
See other errors actions.
ORA-19873: cannot apply this backup section to file
string
Cause:
RMAN cannot restore a multi-section backup to the indicated file, because this
section is not a backup of this file, or the file was not prepared correctly
for this restore.
Action:
If this error occurs while running RMAN, then it is an internal error and you
should contact Oracle support.
ORA-19874: cannot finish multi-section restore to
file string
Cause:
During a multi-section restore, the file being restored is not a file in which
a multi-section restore is in progress.
Action:
If this error occurs while running RMAN, then it is an internal error and you
should contact Oracle support.
ORA-19875: multi-section restore not complete for
file string
Cause:
While completing a multi-section restore, it was found that all required
sections for this file were not correctly applied.
Action:
If this error occurs while running RMAN, then it is an internal error and you
should contact Oracle support.
ORA-19880: Corrupted space header for datafile string,
block string
Cause:
When reading the space header block to use Unused Block Optimization for the
backup of the datafile, the space header block had corrupted information.
Action:
The corrupt space header must be fixed before Unused Block Optimization can be
used for this file. Note that you should fix the corruption in any case because
it will affect the availability of the data in the file, beyond just taking
backups.
ORA-19881: Corrupted space bitmap for datafile string,
block string
Cause:
When reading a space bitmap block to use Unused Block Optimization for the
backup of the datafile, the space bitmap block had corrupted information.
Action:
The corrupt space bitmap must be fixed before Unused Block Optimization can be
used for this file. Note that you should fix the corruption in any case because
it will affect the availability of the data in the file, beyond just taking
backups.
ORA-19882: datafile string checkpoint string
is ahead of space bitmap datafile string checkpoint string
Cause:
When checkpointing the datafile containing the space bitmaps for the datafile
being backed up in order to use Unused Block Optimization, the checkpoint of
the datafile containing the space bitmaps did not advance.
Action:
Examine the trace and alert files for possible causes. Fix underlying problem
to use Unused Block Optimization for datafile's backup.
ORA-19883: Unused Block Optimization stopped for
datafile string
Cause:
Accompanying errors detail the problem that prevented Unused Block Optimization
from being used.
Action:
See accompanying errors for appropiate action.
ORA-19900: RESETLOGS must be specified after
recovery to new incarnation
Cause:
Recovery was done to an incarnation after changing the destination incarnation
using RMAN's RESET DATABASE command.
Action:
Open the database with the RESETLOGS option.
ORA-19901: database needs more recovery to create
new incarnation
Cause:
Recovery was done to an incarnation after changing the destination incarnation
using RMAN's RESET DATABASE command, but one or more of the recovered datafiles
still belongs to the parent incarnation. This usually happens when recovery is
ended before any logs from the desired incarnation have been applied.
Action:
Continue recovery.
ORA-19902: incarnation key string not found
Cause:
The specified incarnation was not found in the control file.
Action:
Resubmit request with known incarnation key. To see which incarnations are
available for this target database, query V$DATABASE_INCARNATION or use RMAN's
LIST INCARNATION command.
ORA-19903: test recovery not allowed when
recovering to new incarnation
Cause:
Either a new incarnation was set using RMAN's RESET DATABASE command for a
control file that was CURRENT, or the control file is from a prior incarnation.
As recovery to a new incarnation requires changing the control file, test
recovery is not allowed.
Action:
Perform actual recovery or RESET DATABASE to incarnation that was last opened
using the control file to do test recovery.
ORA-19904: test recovery not allowed for datafile string
Cause:
The specified datafile has been restored from a backup that was taken before
the last RESETLOGS. Recovering this datafile will require a file header update
that is incompatible with test recovery.
Action:
Perform actual recovery.
ORA-19905: log_archive_format must contain %s, %t
and %r
Cause:
log_archive_format is missing a mandatory format element. Starting with Oracle
10i, archived log file names must contain each of the elements %s(sequence),
%t(thread), and %r(RESETLOGS ID) to ensure that all archived log file names are
unique.
Action:
Add the missing format elements to log_archive_format.
ORA-19906: recovery target incarnation changed
during recovery
Cause:
While a media recovery was active, a new incarnation was detected by the server
due to inspection or cataloging of archived logs or backup files.
Action:
If you want recovery to use the new incarnation, restart recovery. This is the
most common action on a standby database when RESETLOGS is done in primary. If
you do not want recovery to use the new incarnation, change the recovery
destination using RMAN's RESET DATABASE TO INCARNATION <incarnation#>
command. To see which incarnations are available for this target database,
query V$DATABASE_INCARNATION or use RMAN's LIST INCARNATION command.
ORA-19907: recovery time or SCN does not belong to
recovered incarnation
Cause:
A point-in-time recovery to an SCN or time stamp prior to the last RESETLOGS
was requested.
Action:
Either change the specified recovery time/SCN, or change the recovery
destination using RMAN's RESET DATABASE command.
ORA-19908: datafile string has invalid
checkpoint
Cause:
The specified datafile has an invalid checkpoint.
Action:
Restore the datafile from a backup.
ORA-19909: datafile string belongs to an
orphan incarnation
Cause:
Either the specified datafile was restored from a backup that was taken during
a period of time that has already been discarded by a RESETLOGS operation, or
Oracle cannot identify which database incarnation the file belongs to. The
alert log contains more information.
Action:
Restore a backup of this file that belongs to either the current or a prior
incarnation of the database. If you are using RMAN to restore, RMAN will
automatically select a correct backup.
ORA-19910: can not change recovery target
incarnation in control file
Cause:
The RESET DATABASE TO INCARNATION command was used while the database is open.
This is not allowed.
Action:
Close the database then re-issue the command.
ORA-19911: datafile string contains future
changes at the incarnation boundary
Cause:
The file did not hit end backup marker redo during recovery at the incarnation
boundary, hence may contain changes discarded by new incarnation.
Action:
Use older backup of the file and then re-issue the command.
ORA-19912: cannot recover to target incarnation string
Cause:
The control file is not in the recovery path of the target incarnation, and
does not contain enough information as to how to recover to the target
incarnation.
Action:
Restore the latest control file from the target incarnation and retry.
ORA-19913: unable to decrypt backup
Cause:
A backup piece could not be decrypted. This message is accompanied with another
message that indicates the name of the encrypted backup that could not be
restored. The reason could be either that an invalid password was entered, or
that, when using transparent decryption, the database external security device
is not open.
Action:
If password-based restore was enabled for this backup, then supply the correct
password using the RMAN SET DECRYPTION command. If transparent restore was
enabled for this backup, then ensure that the database external security device
is open.
ORA-19914: unable to encrypt backup
Cause:
RMAN could not create an encrypted backup. This message will be accompanied by
other messages that give more details about why the encrypted backup could not
be created. The most common reason for this message is that you are trying to
create a backup that can be transparently decrypted, and the database external
security device is not open.
Action:
If the external security device is not open, then open it. If the external
security device is not configured, then the only type of encrypted backup that
you can create is a password-based backup.
ORA-19915: unable to encrypt pre-10.2 files
Cause:
An RMAN encrypted backup was requested, but this backup includes one or more
archived logs that were generated by an older release of Oracle. These archived
logs cannot be encrypted.
Action:
Back up the older logs without encryption. Logs created with Oracle release
10.2 and greater can be encrypted.
ORA-19916: string
Cause:
An error occurred when processing user request.
Action:
Do not use message 19917; it is used internally for testing purpose. Do not use
message 19918; it is an internal event used by encryption.
ORA-19919: encrypted backups to tertiary storage
require Oracle Secure Backup
Cause:
RMAN was configured to create encrypted backups, but the channel is neither a
DISK channel nor an Oracle Secure Backup channel.
Action:
Allocate a DISK channel or an Oracle Secure Backup channel to use backup
encryption.
ORA-19921: maximum number of string rows
exceeded
Cause:
The maximum number of rows in the V$RMAN_STATUS or V$RMAN_OUTPUT table has been
exceeded.
Action:
Close some of existing and unused RMAN connections and sessions.
No hay comentarios:
Publicar un comentario