redo logs not getting applied [message #255152] |
Mon, 30 July 2007 19:20 |
Koolwant
Messages: 49 Registered: June 2007 Location: new jersey
|
Member |
|
|
Hi Guru's
I have 10.2.0.1 on two servers RHEL Enterprise 4 .
My redo logs are not being shipped .
select sequence#,applied from v$archived_log ; GIVES
no rows selected
When I see alert.log I get following errors
PING[ARC0]: Heartbeat failed to connect to standby 'OHIO1_204'. Error is 1031.
*** 2007-07-30 20:10:07.329 58941 kcrr.c
kcrrfail: dest:2 err:1031 force:0 blast:1
kcrrwkx: nothing to do (end)
*** 2007-07-30 20:11:07.334
Redo shipping client performing standby login
OCISessionBegin failed -1
.. Detailed OCI error val is 1031 and errmsg is 'ORA-01031: insufficient privil
eges
'
*** 2007-07-30 20:11:07.366 60679 kcrr.c
Error 1031 received logging on to the standby
Error 1031 connecting to destination LOG_ARCHIVE_DEST_2 standby host 'OHIO1_204
'
Error 1031 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'OHIO1_204'
ORA-01031: insufficient privileges
*** 2007-07-30 20:11:07.366 60679 kcrr.c
PING[ARC0]: Heartbeat failed to connect to standby 'OHIO1_204'. Error is 1031.
*** 2007-07-30 20:11:07.366 58941 kcrr.c
kcrrfail: dest:2 err:1031 force:
|
|
|
Re: redo logs not getting applied [message #255378 is a reply to message #255152] |
Tue, 31 July 2007 10:50 |
DreamzZ
Messages: 1666 Registered: May 2007 Location: Dreamzland
|
Senior Member |
|
|
Quote: | My redo logs are not being shipped .
|
post querry result
• SQL> Select Status, Error
from v$Archive_dest
where dest_id=2;
Quote: | select sequence#,applied from v$archived_log ; GIVES
no rows selected
|
If logs are not shipping then how could you except applied?
Post The parameteres you set for DG configuration.
Enable dead connection detection on the primary and standby sites
sqlnet.expire_time=2
|
|
|
Re: redo logs not getting applied [message #255419 is a reply to message #255378] |
Tue, 31 July 2007 15:45 |
Koolwant
Messages: 49 Registered: June 2007 Location: new jersey
|
Member |
|
|
Hi DremzZ
Thanks For your reply.
I figured out the problem .
That error is due to the password file.
What my mistake was I spelled it wrong.
So my dataguard started working fine .
And I have checked Failover and switchover also.
NOW I have a question.
203-Primary ,204-Standby
Pulled power cable of 203.
alter the database on 204 to PRIMARY .And It works fine too.
The question is what happens if I put the power cable back into 203
.And My database on 203 comes up with init.d scripts.
Is it like 203 will also try to come up as Primary.
And would there be like two Primary's.
Or what should I do.
Thanks in Advance.
|
|
|
|
Re: redo logs not getting applied [message #255424 is a reply to message #255422] |
Tue, 31 July 2007 16:57 |
Koolwant
Messages: 49 Registered: June 2007 Location: new jersey
|
Member |
|
|
Thanks for sending me the document link.
CAn we do that when 203 comes up ,we can switchover it to physical standby and then when it synchronizes with 204 , we again swithover it to same old configuration
as 203-Primary and 204-Standby
Is it possible or we have take backup of datafiles on 204 and apply it to 203 and then create standby controlfile for 204 and shutdown both 203 and 204 and then startup again as 203-Primary and 204-Standby
Thanks
|
|
|
|
Re: redo logs not getting applied [message #255737 is a reply to message #255429] |
Wed, 01 August 2007 11:07 |
Koolwant
Messages: 49 Registered: June 2007 Location: new jersey
|
Member |
|
|
Hey DreamzZ
One more thing what should we do if the Original primary comes up.Do we have to shut it down till it synchronizes or it would be okay if we dont even shut it down.
Thanks
|
|
|
Re: redo logs not getting applied [message #255754 is a reply to message #255737] |
Wed, 01 August 2007 12:03 |
DreamzZ
Messages: 1666 Registered: May 2007 Location: Dreamzland
|
Senior Member |
|
|
Actually In DG enviroment when your Primary goes down your Standby starts works ,in the mean while you recover the primary database syncronize it with standby after that you put it back as a PRIMARY and your primary(standby) again goes to STANDBY.
Quote: |
One more thing what should we do if the Original primary comes up.Do we have to shut it down till it synchronizes or it would be okay if we dont even shut it down
|
you can DEFER ARCHIVING at PRIMARY for a while no need of SHUTDOWN.
log_archive_dest_state_2=DEFER.
|
|
|
|
|