RMAN-06059: expected archived log not found, lost of
archived log compromises recoverability
- 1 Answers
- 5166 Views
- I also Faced
- E-Mail Answers
Answer / guest
Cause: The archived log was not found. The repository thinks
it does exist. If the archived log has in fact been lost and
there is no backup, then the database is no longer
recoverable across the point in time covered by the archived
log. This may occur because the archived log was removed by
an outside utility without updating the repository.
Action: If the archived log has been removed with an outside
utility and the archivelog has already been backed up, then
you can synchronize the repository by running CROSSCHECK
ARCHIVELOG ALL. If the archivelog has not been previously
backed up, then you should take a full backup of the
database and archivelogs to preserve recoverability.
Previous backups are not fully recoverable.
Please add more information about this Error
| Is This Answer Correct ? | 1 Yes | 0 No |
PCC-02011: found identifier greater than 128 characters (truncated)
PCC-00144: UNSAFE_NULL=YES must be used with DBMS=V7 and MODE=ORACLE
TNS-00206: Status Information for Interchange string:
ORA-31610: cannot call this function from a non-master process
ORA-25200: invalid value string, QUEUE_NAME should be [SCHEMA.]NAME
NID-00308: Control File string - dbid changed
PLS-00310: with %%ROWTYPE attribute, 'string' must name a table, cursor or cursor-variable
DRG-11829: Gone
PROC-00004: The cluster registry key to be operated on does not exist.
ORA-12052: cannot fast refresh materialized view string.string
ORA-07588: spdcr: $GETJPIW get image name failure
In my project I am using star schema and only diimension tables are loaded and not fact tables any one can help me why it is happening? Plase guide me.
Oracle Errors 
