Professional Documents
Culture Documents
Independent Consultant
Oracle Applications DBA and Developer
Jeff@OracleAppsPro.Com
What Would You Do???
It’s Monday morning.
Fatal production system hardware problem, or
production hardware location is now a smoking hole
Expect Production to be down for an unforseen
amount of time
It is year-end, you have a new manager and your
senior DBA is on vacation
Scenario:
Show stopper problem in Production
Need to test a patch or data fix with current production
data on test system ASAP
Database Database
45mb of which
8-10mb used by
Data Guard
Application Application
# Flash recovery area. This is the default location for control files, online
# redo logs, archived redo logs, flashback logs, RMAN backups.
db_recovery_file_dest=/u01/oracle/flash_recovery_area
# Log gap detection and resolution when this database is the standby
fal_server = 'PROD_LNXDRDB1‘
fal_client = 'PROD_CAMELDB1'
Jeff Slavitz - NorCal OAUG Training Day 2010 v3
Start Data Guard
Start primary and second database and listeners
Primary: startup
Standby: startup mount
Turn on archive redo log transport on primary
alter system set log_archive_dest_state_2=enable;
Put standby in recovery mode
Recover managed standby database using current logfile
disconnect;
Confirm logs are shipping to standby
Primary: alter system archive log current;
Standby: Check archive directory or query v$archive_log
disconnect;
Jeff Slavitz - NorCal OAUG Training Day 2010 v3
Instant Clone or Reporting Database
On standby:
Cancel standby recovery
create restore point STBY_ON guarantee flashback database
Active and open database
Configure application as in Switchover
Users can now login to the standby database through Oracle
Applications, Discoverer or anything.
Apply patches, test, update data in standby database.
To revert to restore point STBY_ON and do further testing as needed:
Shutdown immediate
Startup mount
Flashback database to guaranteed restore point STBY_ON
Alter database open
Jeff Slavitz
Jeff@OracleAppsPro.com
(415) 388 - 3003