-
I have not checked like that.
select * from v$log;
in prod & standby
it will you the current status (i.e.,)current,Active,Inactive.
If i do Switch log file the current status changes to next log.
check that using select * from v$log;
in both DB.
from that i confirmed.
then added 5 records in test user in prod. after that went to standby checked it shows only previos record, then shutdowned standby.
recoverd..,Opened in read only then checked
Newly added five records displayed in standby.
-
Originally Posted by ams-jamali
I have not checked like that.
select * from v$log;
in prod & standby
it will you the current status (i.e.,)current,Active,Inactive.
If i do Switch log file the current status changes to next log.
check that using select * from v$log;
in both DB.
from that i confirmed.
then added 5 records in test user in prod. after that went to standby checked it shows only previos record, then shutdowned standby.
recoverd..,Opened in read only then checked
Newly added five records displayed in standby.
Please provide output of the following query:
On Primary:
SQL> select max(sequence#) from v$log_history;
On Standby:
SQL> select max(sequence#) from v$log_history;
Should be same.
-
Hi parvesh,
we have worked successfully in standby database.
we opened standby in readonly mode.everything is perfect,but there is one thing controversy.Undo tablespace used in prod is UNDOTBS whereas in standby it is UNDOTBS1.
when we kept standby in read only mode .it shows warning in alert_log file stating that
***Warning - Executing transaction without active Undo Tablespace
everything is perfect,but little bit scared whether it will show err in future.
Thanks to all
*bore,parvesh,ray_dp,dave..& all
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|