Home » Server Options » Data Guard » RFS LogMiner: RFS id [17956926] assigned as thread [1] PING handler (11g, 11.2.0.3, AIX 7.1.0.0)
RFS LogMiner: RFS id [17956926] assigned as thread [1] PING handler [message #618037] Mon, 07 July 2014 01:27 Go to next message
ashishkumarmahanta80
Messages: 231
Registered: October 2006
Location: kolkatta
Senior Member
Dear All,

Due to unavailability of spaces, ODS (logical-standby) server goes out-of-SYNC. After re-generating spaces, we applied log shipping.
In the alert log, its showS AS "RFS LogMiner: RFS id [17956926] assigned as thread [1] PING handler".

below are the part of alert log -

LOGMINER: Begin mining logfile for session 1 thread 1 sequence 9848, +DATADG2/archive_ods/prodods_53b26625_9848_1_836611240.arc
LOGMINER: End   mining logfile for session 1 thread 1 sequence 9848, +DATADG2/archive_ods/prodods_53b26625_9848_1_836611240.arc
Mon Jul 07 10:59:54 2014
LOGSTDBY Analyzer process AS00 started with server id=0 pid=74 OS id=17170604
Mon Jul 07 10:59:54 2014
LOGSTDBY Apply process AS01 started with server id=1 pid=75 OS id=17105002
Mon Jul 07 10:59:54 2014
LOGSTDBY Apply process AS05 started with server id=5 pid=79 OS id=22544588
Mon Jul 07 10:59:54 2014
LOGSTDBY Apply process AS02 started with server id=2 pid=76 OS id=16580694
Mon Jul 07 10:59:54 2014
LOGSTDBY Apply process AS04 started with server id=4 pid=78 OS id=16318578
Mon Jul 07 10:59:54 2014
LOGSTDBY Apply process AS03 started with server id=3 pid=77 OS id=16449706
Mon Jul 07 11:01:16 2014
RFS[558]: Selected log 5 for thread 1 sequence 9865 dbid 1404200485 branch 836611240
Mon Jul 07 11:01:17 2014
RFS LogMiner: Registered logfile [+DATADG2/archive_ods/prodods_53b26625_9864_1_836611240.arc] to LogMiner session id [1]
Mon Jul 07 11:21:03 2014
RFS[559]: Assigned to RFS process 20774960
RFS[559]: Possible network disconnect with primary database
Mon Jul 07 11:21:08 2014
RFS[558]: Selected log 4 for thread 1 sequence 9866 dbid 1404200485 branch 836611240
Mon Jul 07 11:21:08 2014
RFS LogMiner: Registered logfile [+DATADG2/archive_ods/prodods_53b26625_9865_1_836611240.arc] to LogMiner session id [1]
Mon Jul 07 11:21:12 2014
RFS LogMiner: RFS id [17956926] assigned as thread [1] PING handler
Mon Jul 07 11:29:51 2014
Thread 1 advanced to log sequence 83758 (LGWR switch)
  Current log# 1 seq# 83758 mem# 0: +DATADG2/prodods/onlinelog/group_1.11473.845216791
Mon Jul 07 11:29:51 2014
Archived Log entry 83757 added for thread 1 sequence 83757 ID 0x15fd8b3b dest 1:
Mon Jul 07 11:30:12 2014
Thread 1 advanced to log sequence 83759 (LGWR switch)
  Current log# 2 seq# 83759 mem# 0: +DATADG2/prodods/onlinelog/group_2.14380.845216791
Mon Jul 07 11:30:12 2014
Archived Log entry 83758 added for thread 1 sequence 83758 ID 0x15fd8b3b dest 1:


Kindly suggest, what could be the possibilities of error as in logstdby_events, no error is displaying. It's shows apply of logs.
But applied scn is not changing at logstdby_progress.

Regards,
Ashish Kumar Mahanta
Re: RFS LogMiner: RFS id [17956926] assigned as thread [1] PING handler [message #618052 is a reply to message #618037] Mon, 07 July 2014 05:59 Go to previous messageGo to next message
ashishkumarmahanta80
Messages: 231
Registered: October 2006
Location: kolkatta
Senior Member
Dear All,

There was network issues.

RFS[559]: Possible network disconnect with primary database


Also in between the registering the archive log, TNS time-out error generating. Though, now, it's applying the logs but there is delay.

I got my answer.

Regards,
Ashish Kumar Mahanta
Re: RFS LogMiner: RFS id [17956926] assigned as thread [1] PING handler [message #618061 is a reply to message #618052] Mon, 07 July 2014 07:29 Go to previous messageGo to next message
Michel Cadot
Messages: 67294
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator

Thanks to let us know.

Re: RFS LogMiner: RFS id [17956926] assigned as thread [1] PING handler [message #618191 is a reply to message #618061] Wed, 09 July 2014 03:44 Go to previous messageGo to next message
ashishkumarmahanta80
Messages: 231
Registered: October 2006
Location: kolkatta
Senior Member
Dear Michel,

There were some other problems too.
When we check the list of archive log, came to know that there were many logs which were missing (not shipped).
We had shipped and registered those logs manually. Later, it started applying...

May be this would happened due to heavy network congestion?

Regards,
Ashish Kumar Mahanta
Re: RFS LogMiner: RFS id [17956926] assigned as thread [1] PING handler [message #618981 is a reply to message #618191] Thu, 17 July 2014 02:47 Go to previous message
trantuananh24hg
Messages: 742
Registered: January 2007
Location: Ha Noi, Viet Nam
Senior Member
ashishkumarmahanta80 wrote on Wed, 09 July 2014 08:44


May be this would happened due to heavy network congestion?

Regards,
Ashish Kumar Mahanta


May be, or may be not.
Whenever lost contact from Standby to Primary/ Primary to Standby, the Ping repeats at least 3 times, if over, then it put on handling, failed to connect and so that, archivelog can be not shipped from Primary to Standby. Whenever the Standby are corrected by resgistering missed archived log manually, RFS will appear, example:

RFS[4]: Selected log 4 for thread 1 sequence 127942 dbid 1609114703 branch 848585489
Thu Jul 17 13:32:27 2014
Archived Log entry 16977 added for thread 1 sequence 127941 ID 0x5fe90a4c dest 1


The last applied log in Standby is the last archive log in Primary. At this point, you can not analyze the network problem even. But, whenever Standby disconnect to Primary, sometime later, the network is to be done normally, and Standby connect to Primary succsefully, those missing archivelog between break-down time of the network are shipped to Standby. At this point, you can analyze:
- Total size of one archivelog, example 4gb per one
- Total gb each per second by network
- How does network perfomance at time? Application connect, get result, transport request, ...etc.

In my experience, there is no more less effective network hardware on system right now. And normally, the DBA usual does configure private network between Standby and Primary, instead of using Primary. (one IP on one physical NIC for public, one IP on on physical NIC for private at different VLANs).

[Updated on: Thu, 17 July 2014 02:50]

Report message to a moderator

Previous Topic: Temp objects stops log apply at standby
Next Topic: upgradation standby along with physical RAC database
Goto Forum:
  


Current Time: Mon Aug 10 03:14:12 CDT 2020