Interested to Buy Any Domain ? << Click Here >> for more details...
RMAN-06166: datafile string cannot be recovered
- 1 Answers
- 4325 Views
- I also Faced
- E-Mail Answers
Answer / guest
Cause: Incremental backups or archived redo logs needed to
recover the datafile cannot be found, and no recoverable
full backup or datafile copy exists.
Action: Use the LIST command to see if there is a backup set
or datafile copy that can be made AVAILABLE. If not, then
the datafile is unrecoverable. If a full or datafile copy
exists, then a point-in-time recovery may be possible.
Please add more information about this Error
| Is This Answer Correct ? | 0 Yes | 0 No |
ORA-12152: TNS:unable to send break message
ORA-01575: timeout waiting for space management resource
QSM-02040: top level query contains GSets and the key is too long for rewrite
RMAN-06056: could not access datafile number
ORA-36637: (XSDUNION05) The concat dimension cannot be defined as UNIQUE because it has a non-unique concat base dimension workspace object.
ORA-29552: verification warning: string
ORA-22293: LOB already opened in the same transaction
SQL*Loader-00516: Control file (string) has no contents
ORA-36976: (XSRELGID00) The format of the GROUPINGID command is: GROUPINGID [relation1] INTO {variable | relation2 | surrogate} [USING levelrelation] [INHIERARCHY {inhvariable | valueset}] [LEVELORDER levelordervs] The source relation can be omitted only when using both surrogate gid and level order valueset.
RMAN-08162: executing Memory Script
ORA-36672: (XSDPART10) A RANGE or LIST PARTITION TEMPLATE can only have a single partition dimension.
ORA-22881: dangling REF
Oracle Errors 
