Beruflich Dokumente
Kultur Dokumente
log_archive_dest=/clover/archive
log_archive_duplex_dest=/clover/archive
OR
log_archive_dest_1=LOCATION=/clover/arch
Mandatory Reopen=500(Default 300)
Optional
log_archive_min_succeed_dest=2
log_archive_dest_state_3=DEFER / ENABLE
Selectively Archiving
> ALTER SYSTEM ARCHIVE LOG SEQUENCE 052;
BACKUP AND RECOVERY
Disadvantage
Data is lost and must be reapplied manually
The entire database is restored to the point of the last whole closed backup
Recovery
> shutdown
Restore all files using operating system
> startup
Advantages
Only need to restore lost files
Recovers all data to the time of failure
Recovery time is the time it takes to restore lost files and apply all archived log files
Disadvantages
Must have all archived log files since the backup from which you are restoring
Complete recovery
Closed database recovery for
- System data files
- Rollback segment data files
- Whole database
Opened database recovery, with database initially opened : for file loss
Opened database recovery with database initially closed : for hardware failure
Data file recovery with no data file backup
Incomplete recovery
Time based
Cancel based
Using control file
Change based
Backups
Note : To keep backup, create one subfolder in your main folder Every day before shutdown
delete all your backups.
Recovery
Note : if log sequence no is not changed after taking the backup no need restore all file.
Scenario 1
Recovery
Restore damaged datafile from backup using operating system and recover
cp /oracle/backup /oracle/db01/data
Scenerio 2
Recovery
Restore all files.
> alter database open ;
Disadvantage : Require all archive logs since the backup from which are restored
Requirement : Last valid backup after seting database in archive log mode.
All archive logs and online redologs which are not yet archived
Recovery : Startup the database in mount/open stage
Restore damaged datafile from backup using operating system recover
Recover the datafile.
Recovery syntax
Recovering in mount stage
> Recover database
> Recover datafile <datafile path/name or file no.>;
> Alter database recover database;
Manual recovery
Automatic recovery
Restore system datafile from backup using oprating system and recover the datafile
> Recover datafile /clover/data/sys.dbf ;
> Alter database open ;
Restore the lost datafile from backup and recover the datafile.
> Recover datafile /clover/test.dbf ;
Note : if you want to restore the damaged datafile to different location oracle must
Be informed about new location by renaming recovery
Backup Recovery
check V$Backup
Since the datafile header was frozen the database files were not synchronized.
If redo logs are lost recovery to the time of failure is not possible but if lost redologs are not
current, the redolog has been archived and proper mulltiplexing of redo logs are available no
data will be lost.
Scenario 7
Check V$Logfile for current logfile and delete one fo the redlog file which is not current.
Using operating system. Force the log switch
Possible Failures : A failed complete recovery operation, Important table in the Database
is dropped, A control file is lost, Loss of redolog files
Recovery Guidelines :
Follow all steps: Most errors occur during this type of
recovery.
Whole-database backup before and after recovery assist
future recovery.
Always verify that the recovery is successful.
Back up the control file regularly.
Back up and remove archived logs.
Database are brought forward in time, not bake in time.
Scenerio 8 : A table is dropped at 10 am at 11 am user comes to know that the table view or
table does not exist
Create a table test.
> Create table test ( n number );
Insert values
> Insert into test values (11111);
> Commit ;
> Alter system switch logfile ;
Note down the commit timing. Give some time gap and drop the table
> Drop table test ;
Shutdown the database
> Shutdown
Mount the databse
> Startup mount ;
Restore all datafile from backup (most recent ) using operating system. And recover the
database until time (Specify time before droping the table )
> Recover database until time 2001-11-12:09:30:00;
> Alter database open resetlogs ;
After incomplete recovery take new backup of database.
Scenerio 10 : No back up was taken after reset logs, need is to use cold backup
Backup the data file and control file. ( cold backup )
Perform incomplete recovery ( To bring database in new incarnation you can recover by time
based or cancel based )
Create a table insert some records commit.
Shutdown the database.
> Shutdown
Restore cold data file and control file ( from cold backup)
Startup the database. ( You will get an error )
> Startup
Check V$Log for change seq #)
Recover until Change
> recover database until change < change seq#>;
> Alter database open resetlog :
Check for table created.
Scenerio 11
Recovery using backup controlfile
Tablespace was created at 10am and backup was taken and dropped at 2pm
Create a tablespace and create one table insert records into the table.
Take backup of all datafile and controlfile ( closed/open if you are taking open database
backup first take backup of controlfile than datafile )
Drop the tablespace.
> Drop tablespace test including contents ;
Shutdown the database take backup of existing controlfile first than restore controlfile and
datafile.
Startup the database it will give an error after taking the database in mount stage.
Make sure that all datafiles are online before recovery by checking v$recover_file Perform
recovery using backup controlfile
> recover database until time 2001-11-11:13:10:00 using backup controlfile;
> Alter database open resetlogs ;
Check for the table.
Scenario 12
Backup was taken of both controlfile and datafile at 10 am. At 11 am Tablespace was created
and at 1pm tablespace was dropped. Recover the tablespace using cold backup.
Scenario 13
A table test was created at 10am and dropped at 10.30 am, another table test1 was dropped at
10.45am. Recover the tables without losing any records in both the table.
Scenario 14
Recover the lost current control file, or the current control file is inconsistent with files that
you need to recover
Scenario 15
Recover lost online redo logs.
Scenario 16
Recover new information that was not in the backup and was only stored in the archivelog
files.
Scenario 17
How to recover a database having added a datafile since the last backup.
Scenario 18
If the database crashes during a hot backup.