Home » Server Options » Data Guard » Redo Application in Failover
 Redo Application in Failover [message #257915] |
Thu, 09 August 2007 10:31  |
Koolwant
Messages: 49
Registered: June 2007
Location: new jersey
|
Member |
|
|
Hey Experts
I am working on 10.2.0.1,Redhat Enterprise linux 4
My dataguard is working fine .But when I'm testing failover the changes which have been done between 1-3 minutes before failover are not being applied to standby.Is there any parameter I'm missing something or It is the lag which is permissible.I am using the following command for redo application
Alter database recover managed standby database using current logfile disconnect;
Thanks
|
|
|
|
|
|
|
|
|
|
| Re: Redo Application in Failover [message #257964 is a reply to message #257946] |
Thu, 09 August 2007 12:32  |
Koolwant
Messages: 49
Registered: June 2007
Location: new jersey
|
Member |
|
|
log_archive_dest_1='LOCATION=/home/oracle/arch
VALID_FOR=(ALL_LOGFILES,ALL_ROLES) db_unique_name=OHIO1_203'
log_archive_dest_2='SERVICE=OHIO1_204
VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE)
DB_UNIQUE_NAME=OHIO1_204 LGWR ASYNC REOPEN=10'
log_archive_dest_state_1='enable'
log_archive_dest_state_2='enable'
And my dataguard configuration is in Max Performance.
[Updated on: Thu, 09 August 2007 12:33] Report message to a moderator |
|
|
|
| Re: Redo Application in Failover [message #257986 is a reply to message #257964] |
Thu, 09 August 2007 13:40 |
DreamzZ
Messages: 1666
Registered: May 2007
Location: Dreamzland
|
Senior Member |
|
|
If you create table on primary is it replicated at the same time on Standby?
SQL> show parameter log_archive_dest_2
NAME TYPE VALUE
------------------------------------ -------------------------------- ------------------------------
log_archive_dest_2 string SERVICE=FLPS2 LGWR ASYNC
VALID_FO
R=(ONLINE_LOGFILES,PRIMARY_ROL
E)
DB_UNIQUE
_NAME=FLPS2
Your LGWR ASYNC is that after DB_UNIQUE_NAME?
[Updated on: Thu, 09 August 2007 13:40] Report message to a moderator |
|
|
|
| Re: Redo Application in Failover [message #257991 is a reply to message #257986] |
Thu, 09 August 2007 14:15 |
Koolwant
Messages: 49
Registered: June 2007
Location: new jersey
|
Member |
|
|
Yes My LGWR ASYNC is after DB_UNIQUE_NAME?
And I just copied from metalink , the way they make pfile.
For my own testing I made a test1 table on primary .. and then checked it on the standby in less than one minute .. It was sitting over there.
But the test which was performed by QA's say that , the users they created within 1-3 mins were not reached on standby side..
Guide me if i am wrong.. When the faiover occurs I execute following ..
alter database recover managed standby database cancel .
If there is some problem I execute
alter database recover managed standby database finish;
or sometimes
alter database recover managed standby database recover managed standby database finish force;
Then alter database commit to switchover to primary with session shutdown.
Then shutdown and Restart the database.
Thanks
[Updated on: Thu, 09 August 2007 14:25] Report message to a moderator |
|
|
|
|
|
|
|
Goto Forum:
Current Time: Wed Mar 12 09:32:21 CDT 2025
|
] 
Blog
Search
Help
Members
Register
Login
Home
