This content has been marked as final. Show 10 replies
You might be testing too early.
My system :
Once you have MRP running consider testing using this :
SQL> select SEQUENCE#, thread#, process, status from V$MANAGED_STANDBY; SEQUENCE# THREAD# PROCESS STATUS ---------- ---------- --------- ------------ 9754 1 ARCH CLOSING 0 0 ARCH CONNECTED 9755 1 ARCH CLOSING 9749 1 ARCH CLOSING 9756 1 ARCH CLOSING 9751 1 ARCH CLOSING 9752 1 ARCH CLOSING 9753 1 ARCH CLOSING 9757 1 MRP0 WAIT_FOR_LOG 0 0 RFS IDLE 9757 1 RFS IDLE SEQUENCE# THREAD# PROCESS STATUS ---------- ---------- --------- ------------ 0 0 RFS IDLE 0 0 RFS IDLE 13 rows selected. SQL>
if you have not started managed recovery then your standby database is lagging and archive gap is there..
I just mounted my physical standby for the first time. managed recovery is not turned on yet. Why do I have an archive gap?
thanks for the replies.
I am concerned because:
The reason I cannot turn on MRP now is because the standby database is not restored yet.
I don't want to send my backup tapes for restore (means $$ + few days), if my standby is not properly mounted.
I attempted to create standby control file + mount standby database several times.
Each attempt still shows similar gap in the beginning before MRP starts.
With all due respect you have put the cart before the horse. You need to have a working Standby, then test for gaps.
Its a little like trying to test a boat that's still being built, results will vary.
I get the exact same results when I query a database without Data Guard setup!!
Start MRP and see if its still lagging and Share the output
Please read the posts carefully:
h2. I cannot turn on MRP now is because the standby database is not restored yet...
My bad :-)
Hope u ave set each and everything fine.
Firstcheck whether u have configured ur standby properly.
means using same mounts or different mount pointsand according to that parameters has been set rename ur password,and pfile name on ur standby server.
after all doing this just fire.
alter database recover managed standby database disconnect from session;
If not please share ur alert log details of ur standby server.
And if u are using ur database in maximum performance mode no need to create standby redologs.
Thanks and regards
And in ur standby pfile just remove old locations of ur controlfiles '/control01.ctl'/../control03.ctl and ur new controlfile location in ur standby pfile'standby.ctl' which u have been created and transfer from ur Production server
Else mail me ur setup info at firstname.lastname@example.org
what parameters u have used and all
Edited by: user2998224 on Dec 2, 2012 3:55 AM