[Translated from mos] mosrfs

[Translated from mos] mosrfs

Trace the RFS process in physical dg

Source:
How To Trace The Remote File Server (RFS) Process In Physical Standby Database (Document ID 1481125.1)

Applicable:
Oracle Database-Enterprise Edition-Version 10.1.0.2 to 11.2.0.2.0 [Release 10.1 to 11.2]
Information in this document applies to any platform.
* ** Checked for relevance on 5-Aug-2014 ***

Objectives:
The target is to trace the Remote File Server (RFS) process in the physical dg.
The Remote File Server (RFS) process writes redo data to the standby redo log file in the standby database.
The trace for generating the RFS process may be useful, for example, to diagnose the disk io problem on the standby database (Doc ID 1481124.1)

Solution:
To generate the trace file in RFS, we need to do the following:

1. In the alert log of the master database, we need to find the archiving process that recently started the archive heartbeat, for example:

...Using STANDBY_ARCHIVE_DEST parameter default value as USE_DB_RECOVERY_FILE_DEST...ARC6 started with pid=42, OS id=415...Thu Jun 14 13:08:02 EST 2012ARC6: Becoming the heartbeat ARCH...

In this example, the heartbeat archive process is arc6.

2. on the slave database, we need to find the ID of the RFS process that communicates with the ARC6 process on the master database, for example:

[yourmachine ~]$ ps -ef | grep arcoracle 5352 1 0 Jul25 ? 00:00:00 ora_arc0_dg112i1oracle 5356 1 0 Jul25 ? 00:00:00 ora_arc1_dg112i1oracle 5358 1 0 Jul25 ? 00:00:08 ora_arc2_dg112i1oracle 5360 1 0 Jul25 ? 00:00:00 ora_arc3_dg112i1oracle 5357 1 0 Jul25 ? 00:00:00 ora_arc4_dg112i1oracle 5359 1 0 Jul25 ? 00:00:08 ora_arc5_dg112i1oracle 415 1 0 Jul25 ? 00:00:00 ora_arc6_dg112i1

In this example, we will find that the operating system process ID of the arch6 process is 415. This also confirms what we see in the main database alert Log (id = 415)

3. log on to sqlplus as a user in the v $ managed_standby data dictionary view on the slave database. We will find the RFS process id that matches the archive process 415.

SQL> select process,pid,client_pid from v$managed_standby;PROCESS PID CLIENT_PID--------- ---------- ----------------------------------------ARCH 10451 10451ARCH 10453 10453ARCH 10455 10455ARCH 10457 10457RFS 10627 5358RFS 10597 6201RFS 10601 23000RFS 10653 415 <---RFS 10529 1193RFS 10603 5360MRP0 10643 N/A11 rows selected.

4. Use the oradebug command attach to RFS and set 10046 to obtain SQL/waits, internal queries, and other information.

SQL> oradebug setospid 10653Oracle pid: 25, Unix process pid: 10653, image: oracle@yourmachine.com (ARC6)SQL> oradebug unlimitStatement processed.SQL> oradebug event 10046 trace name context forever, level 12;Statement processed.SQL> -- Keep tracing for some time while the problem is occurringSQL> -- as required by Oracle Support.SQL> -- To stop tracing:SQL> oradebug event 10046 trace name context off;Statement processed.SQL>

5. The last step is to find the new trace file in the diagnostic directory. The file name consists of the database SID. Example: MYDBASE_arc6_415.trc
Upload the file to sr. If diagnosing defect 9695805 please refer to Doc ID 1481124.1.