Answer / guest

Cause: An incomplete recovery session was started, but an
insufficient number of logs were applied to make the
database consistent. This file is still in the future of the
last log applied. The most likely cause of this error is
forgetting to restore the file from a backup before doing
incomplete recovery.

Action: Either apply more logs until the database is
consistent or restore the database file from an older backup
and repeat recovery.

Please add more information about this Error

Answer / suhas d

Hello,

If we use a backup controlfile and do recovery, it is
mandatory to open the database with the RESETLOGS option
(incomplete or point in time recovery).

The Backup and Recovery Basics Oracle doc states this
clearly.

If this is an ARCHIVE mode database and controlfile was
backed up using RMAN 'BACKUP CURRENT CONTROLFILE' or such,
we can do incomplete recovery and open resetlogs.

SQL> recover database until cancel using backup controlfile;

Copy over as many archived logs from source to the local
(target) log_archive_dest folder (suggested) and give full
path directions in the above command.

Recovery can happen until you wish to. Type CANCEL when
done and open the database with resetlogs option.

Regards,
Suhas

RMAN-06500: skipping backupset key string; already backed up string time(s)

1 Answers  

---

PLS-00633: RETURN statement in a pipelined function cannot contain an expression

1 Answers  

---

DRG-50933: parser hash insert failure

1 Answers  

---

ORA-30445: workload queries not found

1 Answers  

---

NZE-28774: file cannot write to disk

1 Answers  

---

ORA-32831: timed out trying to acquire administration lock

1 Answers  

---

ORA-01891: Datetime/Interval internal error

1 Answers  

---

SQL*Loader-00915: Error closing cursor: [number]

1 Answers  

---

ORA-10661: Invalid option specified

1 Answers  

---

ORA-16165: LGWR failed to hear from network server

1 Answers  

---

ORA-16801: Some log transport related property is inconsistent.

1 Answers  

---

SQL*Loader-00622: Column not found before end of logical record (use TRAILING NULLCOLS)

2 Answers  

---