Welcome to Scribd, the world's digital library. Read, publish, and share books and documents. See more
Download
Standard view
Full view
of .
Look up keyword
Like this
52Activity
0 of .
Results for:
No results containing your search query
P. 1
Backups and Recovery Scenarios

Backups and Recovery Scenarios

Ratings: (0)|Views: 1,308 |Likes:
Published by ImraneA

More info:

Published by: ImraneA on Jan 26, 2010
Copyright:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as DOC, PDF, TXT or read online from Scribd
See more
See less

08/14/2013

pdf

text

original

 
Updated Last – 14-01-2010
# ----------------------- Database Recovery Scenarios: --------------------------Summary of Scenarios: (***NOT IN ORDER***)-- Redo Log Group
Scenario 1 - Recovering After Losing a Member of a Multiplexed Online RedoLog GroupScenario 2 - Recovering After the Loss of All Members of an Online Redo LogGroupScenario 3 - Loss of INACTIVE Online Redo Log GroupScenario 4 - Loss of CURRENT Online Redo Log GroupScenario 5 - Recovering After the Loss of All Members of an Online Redo LogGroup Using RMANScenario 6 - Recovering After the Loss of All Members of an Online Redo LogGroup Using RMAN with Catalog with CommVaultScenario 33 - Create new logfile groups and drop old groups
-- Control file
Scenario 7 - Loss of control fileScenario 8 - Recovering After a lost of all control files using RMANScenario 9 - Recovering After a lost of all control files using control filebackup to trace fileScenario 10 - Recovering After a lost of all control files using RMAN withCatalog with CommVaultScenario 11 - Recovering After a lost of all control files and spfile using NOCatalogScenario 12 - Recovering After a lost of all control files and spfile using NOCatalog with CommVault
--Non-System Tablespace/Datafiles
Scenario 13 - One or more of the non-SYSTEM database datafiles havebeen destroyed due to media failure using RMAN with CatalogScenario 14 - One or more of the non-SYSTEM database datafiles havebeen destroyed due to media failure using RMAN with Catalog withCommVaultScenario 17 - Missing Data File - non-SYSTEM tablespace fileScenario 18 - Loss of Non-Essential Datafile When Database is DownScenario 19 - Recover a Lost Datafile with No Backup with RMAN withCatalogScenario 20 - Recover a Lost Datafile with No Backup without RMANScenario 21 - Recover a Lost Datafile with No Backup with RMAN withCatalog with CommVault(***AWAITING RESPONSE FROMCOMMVAULT***)(They don’t know…)Scenario 29 - Loss of an Online Undo Segment Datafile (Open or ClosedDatabase) with RMAN with Catalog
1
 
Scenario 30 - Loss of an Online Undo Segment Datafile (Open or ClosedDatabase) with RMAN with NO CatalogScenario 31 - Loss of an Online Undo Segment Datafile (Open or ClosedDatabase) without RMANScenario 32 - Failure during Open Database - tablespace in backup modewith RMAN with Catalog
--SYSTEM Tablespace/Datafile
Scenario 15 - Loss of a SYSTEM tablespace datafile using RMAN withCatalogScenario 16 - Loss of a SYSTEM tablespace datafile without using RMAN
--User Errors
Scenario 22 - Recover from User Errors - dropped table or deleted data withRMAN with CatalogScenario 23 - Recover from User Errors - dropped table or deleted data withRMAN with NO CatalogScenario 24 - Recover from User Errors - dropped table or deleted data -manual data entryScenario 25 - Recover from User Errors - dropped table or deleted data –Flashback DropScenario 26 - Recover from User Errors - dropped table or deleted data –Flashback Table and QueryScenario 27 - Recover from User Errors - dropped table or deleted data –Using Log Miner Scenario 28 - Recover from User Errors - dropped table or deleted data –Flashback Database
--Archive Logs
Scenario 34 - Recover archive log using RMAN with CatalogScenario 35 - Recover archive log using RMAN with Catalog with CommVault
--Duplicate Database
Scenario 36 – Duplicate Database using RMAN with CatalogScenario 37 – Duplicate Database using RMAN with Catalog with CommVault(***AWAITING RESPONSE FROM COMMVAULT***)(This fails memory scripttakes hours to run, it is mounted and trips….)
--Block Corruption
Scenario 38 – Check and repair block corruption using RMAN with Catalog
2
 
--Background Information
If a media failure has affected the online redo logs of a database, then theappropriate recovery procedure depends on the following:
The configuration of the online redo log: mirrored or non-mirrored
The type of media failure: temporary or permanent
The types of online redo log files affected by the media failure: current,active, unarchived, or inactive
--Views
Select member from v$logfile;Select * from v$log;Select * from v$archived_log;
--DBA Stuff 
Add 1 member to group - mirror alter database ADD logfile member 'E:\ORACLE\ORADATA\BACKUPS\REDO02_2.LOG' to group 2;Drop member alter database DROP logfile member 'E:\ORACLE\ORADATA\BACKUPS\REDO02_2.LOG';Will generate error message ...ORA-01609: log 1 is the current log for thread 1 - cannot drop memberskeep switchingalter system switch logfile;Restore Archive logrestore archivelog from logseq=42 until logseq=42;Relationship between SCN and log filesSelect * from v$log_history-each log file - has series change no's from first to next change...-based on archive log formatArchived Redo Log File Conventions in Oracle
3

Activity (52)

You've already reviewed this. Edit your review.
1 hundred reads
1 thousand reads
kmufasa liked this
Huseyin Sasmaz liked this
Nizam Shaik liked this
wong_13 liked this
Anand Saurabh liked this
sg_mac liked this

You're Reading a Free Preview

Download
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->