Go Directly To
Oracle Technology Network Community
My Oracle Support Community
OPN Cloud Connection
Oracle Employee Community
Oracle User Group Community
OTN Speaker Bureau
Get Started Guide
Join the world’s largest interactive community dedicated to Oracle technologies.
Learn from thousands of community experts
Get answers to your technical questions
Share your knowledge with peers
Please enter a title.
You can not post a blank message. Please type your message and try again.
Performance & Availability
This discussion is archived
on Oct 18, 2012 2:48 PM by mseberg
In standby db, can't find sequence number of Last Applied Log.
Oct 18, 2012 2:44 PM
Standby database is behind the primary database for over 200 hours, to repaire this, we are using a incremental backup from primary database and a restored control file.
after starting up standby database, in Grid Control (OEM), can't find "last applied log" sequence number,
go to that standby, do
standby> select max(sequence#) from v$archived_log where applied='YES';
go to primary,
SQL> select max(sequence#) from v$archived_log where applied='YES';
then using OEM grid control, to Verify checks various standby database settings.
Connected to instance standby_server:standby
Starting alert log monitor...
Updating Data Guard link on database homepage...
Skipping verification of fast-start failover static services check.
Data Protection Settings:
Protection mode : Maximum Performance
Redo Transport Mode settings:
Checking standby redo log files.....OK
Checking Data Guard status
primary.com : Normal
standby.com : Normal
Checking inconsistent properties
Checking agent status
Checking applied log on standby........WARNING:
Timed out after 60 seconds waiting for log to be applied.
so how to fix this?
thanks you very much.
Edited by: 951932 on Oct 18, 2012 7:44 AM
I have the same question
Show 0 Likes
This content has been marked as final.
Show 1 reply
Re: In standby db, can't find sequence number of Last Applied Log.
Oct 18, 2012 2:48 PM
in response to
Probably nothing to fix. This is a common warning message.
It even occurs in this example :