ORA-19769: missing FILE keyword
Cause:
Syntax error.
Action:
Use the correct syntax: ENABLE/DISABLE BLOCK CHANGE TRACKING
ORA-19770: invalid change tracking file name
Cause:
The USING clause was specified with ALTER DATABASE ENABLE BLOCK CHANGE
TRACKING, but no file name was given.
Action:
Specify the change tracking file name, or omit the USING clause to allow Oracle
to create a default name for the change tracking file.
ORA-19771: cannot rename change tracking file while
database is open
Cause:
The ALTER DATABASE RENAME FILE command was used to rename the change tracking
file, and the database is open by one or more instances. The database must be
mounted, and not open, to rename the change tracking file.
Action:
Close the database and reissue the command.
ORA-19772: change tracking file name exceeds limit
of string characters
Cause:
The name specified for the change tracking file is too long.
Action:
Specify a shorter change tracking file name.
ORA-19773: must specify change tracking file name
Cause:
No file name was specified with the ALTER DATABASE ENABLE CHANGE TRACKING
command, and the DB_CREATE_FILE_DEST parameter was not set.
Action:
Either specify a file name, or set the DB_CREATE_FILE_DEST parameter.
ORA-19776: PROXY restore to ASM disk group "string"
is not supported.
Cause:
An attempt was made to proxy restore a file to ASM disk group using RMAN
command. This is not supported.
Action:
Use a different file name and reissue RMAN command.
ORA-19777: ASM file string cannot be proxy
backed up.
Cause:
An attempt was made to proxy backup a ASM file. This is not supported.
Action:
Use a different file name and reissue RMAN command.
ORA-19779: could not obtain resilvering status for
change tracking file
Cause:
An error occurred while obtaining the mirror resilvering status of the change
tracking file.
Action:
Refer to other error messages shown for additional details of the problem.
ORA-19800: Unable to initialize Oracle Managed
Destination
Cause:
The name given for an Oracle managed files destination cannot be initialized.
Action:
, if possible, and retry the command or use a different name for destination.
ORA-19801: initialization parameter
DB_RECOVERY_FILE_DEST is not set
Cause:
An attempt was made to create a file in DB_RECOVERY_FILE_DEST when
DB_RECOVERY_FILE_DEST was not set. There are number of possible causes of this error,
including: 1) A LOG_ARCHIVE_DEST_n parameter was specified using a LOCATION
attribute whose value was DB_RECOVERY_FILE_DEST and an archived log file
creation was attempted. 2) STANDBY_ARCHIVE_DEST parameter was specified using a
LOCATION attribute whose value was DB_RECOVERY_FILE_DEST and an archived log
file creation was attempted.
Action:
Specify a valid destination for DB_RECOVERY_FILE_DEST in initialization
parameter file or with the ALTER SYSTEM SET command.
ORA-19802: cannot use DB_RECOVERY_FILE_DEST without
DB_RECOVERY_FILE_DEST_SIZE
Cause:
There are two possible cause for this error: 1) The DB_RECOVERY_FILE_DEST
parameter was in use when no DB_RECOVERY_FILE_DEST_SIZE parameter was
encountered while fetching initialization parameter. 2) An attempt was made to
set DB_RECOVERY_FILE_DEST with the ALTER SYSTEM command when no
DB_RECOVERY_FILE_DEST_SIZE was in use.
Action:
Correct the dependency parameter definitions and retry the command.
ORA-19803: Parameter DB_RECOVERY_FILE_DEST_SIZE is
out of range (1 - string)
Cause:
Parameter DB_RECOVERY_FILE_DEST_SIZE specified was not valid.
Action:
Specify a valid number within the range.
ORA-19804: cannot reclaim string bytes disk
space from string limit
Cause:
Oracle cannot reclaim disk space of specified bytes from the
DB_RECOVERY_FILE_DEST_SIZE limit.
Action:
There are five possible solutions: 1) Take frequent backup of recovery area
using RMAN. 2) Consider changing RMAN retention policy. 3) Consider changing
RMAN archived log deletion policy. 4) Add disk space and increase
DB_RECOVERY_FILE_DEST_SIZE. 5) Delete files from recovery area using RMAN.
ORA-19805: RECID string of string was
deleted to reclaim disk space
Cause:
The file described by the record in control file was deleted in order to reclaim
disk space from flash recovery area for other operations.
Action:
Wait and try again.
ORA-19806: cannot make duplex backups in recovery
area
Cause:
Duplex backup to recovery area is not supported.
Action:
Remove duplex option and try again.
ORA-19808: recovery destination parameter mismatch
Cause:
The value of parameters DB_RECOVERY_FILE_DEST and DB_RECOVERY_FILE_DEST_SIZE
must be same in all instances. instance. All databases must have same recovery
destination parameters.
Action:
Check DB_RECOVERY_FILE_DEST and DB_RECOVERY_FILE_DEST_SIZE values in all
instances.
ORA-19809: limit exceeded for recovery files
Cause:
The limit for recovery files specified by the DB_RECOVERY_FILE_DEST_SIZE was
exceeded.
Action:
The error is accompanied by 19804. See message 19804 for further details.
ORA-19810: Cannot create temporary control file string
in DB_RECOVERY_FILE_DEST
Cause:
An attempt was made to create a control file for a temporary purpose in
DB_RECOVERY_FILE_DEST.
Action:
Retry the operation with a new file name.
ORA-19811: cannot have files in
DB_RECOVERY_FILE_DEST with keep attributes
Cause:
An attempt was made to 1) Create a backup piece or image copy in the recovery
area with KEEP option. 2) Update the KEEP attributes of an existing backup
piece or image copy in the recovery area.
Action:
Reissue RMAN command without KEEP options.
ORA-19812: cannot use string without
DB_RECOVERY_FILE_DEST
Cause:
There are three possible cause for this error: 1) The indicated parameter was
in use when no DB_RECOVERY_FILE_DEST parameter was encountered while fetching
the initialization parameter. 2) An attempt was made to set indicated the
parameter with the ALTER SYSTEM command when no DB_RECOVERY_FILE_DEST was in
use. 3) An attempt was made to clear DB_RECOVERY_FILE_DEST with the ALTER
SYSTEM command when the indicated parameter was in use.
Action:
Eliminate any incompatible parameter definitions.
ORA-19813: cannot have unavailable file string
in DB_RECOVERY_FILE_DEST
Cause:
An attempt was made to change a backup piece or image copy in recovery area to
UNAVAILABLE.
Action:
Correct and resubmit the RMAN command. Do not use messages 19814; it is used
for simulating crash.
ORA-19815: WARNING: string of string
bytes is string% used, and has string remaining bytes available.
Cause:
DB_RECOVERY_FILE_DEST is running out of disk space.
Action:
One of the following:
1. Add disk
space and increase DB_RECOVERY_FILE_DEST_SIZE.
2. Backup files
to tertiary device using RMAN.
3. Consider
changing RMAN retention policy.
4. Consider
changing RMAN archived log deletion policy.
5. Delete files
from recovery area using RMAN.
ORA-19816: WARNING: Files may exist in string
that are not known to database.
Cause:
One of the following events caused this:
1. A database
crash happened during file creation.
2. A backup
control file was restored.
3. The control
file was re-created.
4.
DB_RECOVERY_FILE_DEST has previously been enabled and then disabled.
Action:
Use RMAN command CATALOG RECOVERY AREA to re-catalog any such files. If the
file header is corrupted, then delete those files using an OS utility. Do not
use messages 19817; it is used for simulating lock failure Do not use messages
19818; it is used for space reclamation before backup Do not use messages
19819; it is used to disable clearing file name
ORA-19830: error from target database: string
Cause:
This error should be followed by other errors indicating the cause of the
problem.
Action:
No action required.
ORA-19831: incompatible string.string.string.string
DBMS_BACKUP_RESTORE package: string.string.string.string
required
Cause:
This version of database was incompatible with the the indicated
DBMS_BACKUP_RESTORE package installed in the database.
Action:
If the database has been upgraded from an earlier version, ensure that the catxxxx.sql
script has been run successfully. Re-install dbmsbkrs.sql and prvtbkrs.plb if
necessary.
No hay comentarios:
Publicar un comentario