Interested to Buy Any Domain ? << Click Here >> for more details...
RMAN-06055: could not find log sequence string thread string
- 1 Answers
- 3610 Views
- I also Faced
- E-Mail Answers
Answer / guest
Cause: A log which was on disk at the start of media
recovery or which should have been restored from a backup
set could not be found.
Action: Check the Recovery Manager message log to see if the
log was restored by a previous job step. If so, then check
the V$ARCHIVED_LOG view to see if the log is listed in the
controlfile. If so, then validate that the log exists on
disk and is readable. If the log was not restored, or was
restored but no record of the log exists in V$ARCHIVED_LOG,
then contact Oracle Customer Support.
Please add more information about this Error
| Is This Answer Correct ? | 0 Yes | 0 No |
ORA-38418: ADT associated with the attribute set string does not exist
KUP-04012: file length is too large for output field
ORA-16075: standby database destination mismatch
NNL-00023: SET command is missing an argument
ORA-24434: OCIStmtRelease called before OCIStmtPrepare2.
ORA-28028: could not authenticate remote server
ORA-12831: Must COMMIT or ROLLBACK after executing INSERT with APPEND hint
NNC-00424: invalid address "string"
ORA-00438: %s Option not installed
PLS-00990: Index Tables of Cursor Variables are disallowed
ORA-30387: invalid rewrite mode for REWRITE_EQUIVALENCE API
TNS-04048: Specified service does not exist.
Oracle Errors 
