Database Reference
In-Depth Information
Optional Manual Actions
=======================
1. If file +DATA/CDB1/E6CDAD92377F667EE0436638A8C0DB6C/DATAFILE/pdb1_tbs_1.284.826754085
was unintentionally renamed or moved, restore it
2. Automatic repairs may be available if you shutdown the database and restart it in mount mode
Automated Repair Options
========================
Option Repair Description
------ ------------------
1 Restore and recover datafile 13
Strategy: The repair includes complete media recovery with no data loss
Repair script: /u01/app/oracle/diag/rdbms/cdb1/CDB1/hm/reco_2181095021.hm
RMAN>
The repair script has the following contents:
# restore and recover datafile
sql 'PDB1' 'alter database datafile 13 offline';
restore ( datafile 13 );
recover datafile 13;
sql 'PDB1' 'alter database datafile 13 online';
In this particular case the suggested solution worked—but it was a trivial example. However, as with anything that
is automated you are not freed from using common sense and experience to gauge the effectiveness of the solution.
No machine logic is 100% free from error—admittedly the same can be said for human logic—but double-checking
what the situation is and how it can be fixed is important. Some scenarios you will come across are too complex to be
properly addressed by the recovery advisor, and it will not be able to present a solution.
The next sections deal with the recovery of a database from start to finish, detailing everything from the restore of
the server parameter file all the way up to restoring data files. The next few sections will explain how to get the various
parts of the database back into service.
Restoring the server parameter file
Having to restore the server parameter file is very straightforward provided you followed the advice outlined earlier
in the chapter and configured the controlfile autobackup in RMAN. Do not be lazy and operate the database without
controlfile autobackups: one day they could well save your career. A controlfile autobackup will automatically create
spfile and controlfile autobackups after each backup and after structural changes as explained in the section above.
Additionally you can make your life very easy by using a Fast Recovery Area. With such a setup, it is a walk in the park
to restore the spfile. In this example the database is shut down. In preparation of the restore a tiny little parameter
file helps a lot, releasing you from the need to have the database ID at hand. The file only needs to have the following
minimal set of parameters, but yours may need more:
db_name=CDB1
db_recovery_file_dest = '+RECO'
db_recovery_file_dest_size= 60g
cpu_count = 2
# not necessary but can help if the "dummy" instance won't start
# workarea_size_policy = auto
# pga_aggregate_target = 2G
# sga_target = 4G
Search WWH ::
Custom Search