Solution : https://service.sap.com/sap/support/notes/4161 (SAP Service marketplace login required)
Summary :
The SAP Note provides guidance on restoring and completing a recovery in Oracle databases. Missing or defective data files, SHUTDOWN or database crash without "END BACKUP," and data files set to "OFFLINE" in ARCHIVELOG mode are common issues addressed. The solution involves detailed steps: SHUTDOWN, taking an offline backup, restoring defective data files, and performing recovery actions without opening the database until redo logs are imported. Steps include using SQL*Plus, handling control files, recovering and bringing data files online, and special procedures for temporary and index tablespaces. The procedure concludes with the necessity of full offline backups if "RESETLOGS" is used.
Key words :
sql> shutdown abortsql> startup mountsql> alter database datafile '<file1>' offline, sql> connect internalsql> startup mountsql> alter database create datafile '<file, sql> shutdown abortsql> startup mountsql> alter database datafile '<file, sql> alter database datafile '<file1>' online, sql> alter database datafile '<file, sql> alter database open [resetlogs], sql> alter tablespace <tsp1> online, sql> alter tablespace <tsp1> offline, provide requested redo log files, sql> recover datafile '<file1>' [
Related Notes :
| 659946 | FAQ: Temporary tablespaces |
| 605062 | FAQ: Restore and recovery |
| 365481 | Block corruptions |
| 72808 | SAPDBA: recovery error: Choice of the Log.Seq.Nr. |
| 44649 | During startsap: page I/O error |
| 43490 | Collective note: SAPDBA - Restore/recovery |
| 26312 | SAPDBA: data file "" could not be created. |
| 23070 | Backup and Recovery: Basic Concepts |
| 4164 | Incomplete Recovery ("...RECOVER UNTIL... "). |