Home » Server Options » Data Guard » Logical Standby Apply became TOO SLOW !! (Database, 10.2.0.2, RHEL4 U3 2.6.9-34)
icon9.gif  Logical Standby Apply became TOO SLOW !! [message #324422] Mon, 02 June 2008 07:35 Go to next message
armin_noor
Messages: 5
Registered: January 2007
Junior Member
Hi,
I recently have setup a logical standby database. Everything was fine until the apply procedure on the standby became too slow:

SQL> alter session set nls_date_format = 'HH24:MI:SS (MM/DD)';
Session altered.

SQL> SELECT APPLIED_SCN, APPLIED_TIME, READ_SCN, READ_TIME, NEWEST_SCN, NEWEST_TIME FROM DBA_LOGSTDBY_PROGRESS;

APPLIED_SCN APPLIED_TIME READ_SCN READ_TIME NEWEST_SCN
----------- ---------------- ---------- ---------------- ----------
NEWEST_TIME
----------------
3036960310 18:33:28 (05/31) 3035938077 18:12:43 (05/31) 3060387972
16:30:16 (06/02)
SQL>


The applied time changed about 20 minutes during last 46 hours. v$logstdby says:
COORDINATOR: ORA-16116: no work available
READER, BUILDER and PREPARER: ORA-16127: stalled waiting for additional transactions to be applied
All APPLIERs: ORA-16116: no work available

I really don't have any idea about this issue. Any help will be appreciated.
regards
Re: Logical Standby Apply became TOO SLOW !! [message #340004 is a reply to message #324422] Sun, 10 August 2008 23:31 Go to previous message
email.sandeepnaik
Messages: 121
Registered: August 2006
Senior Member
check dba_logstdby_event view by ordering output by event_time to find any issues.
Look for trace files. Also, check alert.log for the period since its stalled

Sandeep
Previous Topic: logs are not in sync (sync problem)
Next Topic: Import a schema (tables, Views, Stored Procedures) on logical standby
Goto Forum:
  


Current Time: Wed Dec 07 16:50:01 CST 2016

Total time taken to generate the page: 0.13779 seconds