| Resolving Archivelog Gap on Physical Standby Database [message #414732] |
Thu, 23 July 2009 05:48  |
OraKaran
Messages: 183
Registered: March 2008
Location: United Kingdom
|
Senior Member |
|
|
Hi,
Referring the link http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/scenarios.htm#i1032254
Archive gap can happen in following conditions
1)Creation of Physical Standby Database
2)Shutdown of the Standby Database When the Primary Database Is Open
3)Network Failure
To resolve this the solution described is
1) copy the files from Primary database to Standby database
2) startup mount pfile=.. {Assuming that Standby database was shutdown}
3)alter database recover automatic standby database
4)after "Specify log: {<RET>=suggested | filename | AUTO | CANCEL}"
CTL+C
5)alter database recover managed standby database disconnect from session
However in the link http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/log_transport.htm#i1268351
It is mentioned that after copying the files to Standby Database execute following on Standby Database and "restart" Redo Apply
alter database register logfile '/physical_standby1/thread1_dest/arcr_1_7.arc';
Now in case both above methods are compatible to each other which is better?
OR
Both above methods are to be used on some specfic situations?
Thanks and Regards,
OraKaran
|
|
|
|
|
|
|
|
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
