oracle00313 ora27037,【DataGuard】ORA-00313, ORA-00312, ORA-27037 in Standby Database

alter database recover managed standby database disconnect  from session

Attempt to start background Managed Standby Recovery process (yangdb)

Thu Sep 08 19:25:33 2011

MRP0 started with pid=24, OS id=18407

MRP0: Background Managed Standby Recovery process started (yangdb)

Serial Media Recovery started

Managed Standby Recovery not using Real Time Apply

Waiting for all non-current ORLs to be archived...

All non-current ORLs have been archived.

Media Recovery Waiting for thread 1 sequence 53

Completed: alter database recover managed standby database disconnect  from session

Thu Sep 08 19:26:02 2011

RFS[1]: Assigned to RFS process 18409

RFS[1]: Identified database type as 'physical standby': Client is ARCH pid 18933

RFS[1]: Opened log for thread 1 sequence 53 dbid -1945915091 branch 761070192

Thu Sep 08 19:26:03 2011

RFS[2]: Assigned to RFS process 18411

RFS[2]: Identified database type as 'physical standby': Client is ARCH pid 18929

RFS[2]: Opened log for thread 1 sequence 55 dbid -1945915091 branch 761070192

Thu Sep 08 19:26:03 2011

RFS[3]: Assigned to RFS process 18413

RFS[3]: Identified database type as 'physical standby': Client is ARCH pid 18935

RFS[3]: Opened log for thread 1 sequence 54 dbid -1945915091 branch 761070192

Thu Sep 08 19:26:08 2011

RFS[4]: Assigned to RFS process 18416

RFS[4]: Identified database type as 'physical standby': Client is ARCH pid 25846

Archived Log entry 9 added for thread 1 sequence 53 rlc 761070192 ID 0x8c044d2a dest 2:

Thu Sep 08 19:26:08 2011

Media Recovery Log /opt/oracle/arch/yangdb1_53_761070192.log

Thu Sep 08 19:26:08 2011

RFS[5]: Assigned to RFS process 18418

RFS[5]: Identified database type as 'physical standby': Client is ARCH pid 25838

Thu Sep 08 19:26:08 2011

RFS[6]: Assigned to RFS process 18420

RFS[6]: Identified database type as 'physical standby': Client is ARCH pid 25848

RFS[4]: Opened log for thread 2 sequence 47 dbid -1945915091 branch 761070192

Archived Log entry 10 added for thread 1 sequence 54 rlc 761070192 ID 0x8c044d2a dest 2:

Media Recovery Log /opt/oracle/arch/2_43_761070192.dbf

RFS[5]: Opened log for thread 2 sequence 49 dbid -1945915091 branch 761070192

RFS[6]: Opened log for thread 2 sequence 48 dbid -1945915091 branch 761070192

Archived Log entry 11 added for thread 2 sequence 47 rlc 761070192 ID 0x8c044d2a dest 2:

Archived Log entry 12 added for thread 2 sequence 48 rlc 761070192 ID 0x8c044d2a dest 2:

Archived Log entry 13 added for thread 2 sequence 49 rlc 761070192 ID 0x8c044d2a dest 2:

RFS[5]: Opened log for thread 2 sequence 46 dbid -1945915091 branch 761070192

RFS[1]: Opened log for thread 1 sequence 56 dbid -1945915091 branch 761070192

Archived Log entry 14 added for thread 2 sequence 46 rlc 761070192 ID 0x8c044d2a dest 2:

RFS[4]: Opened log for thread 2 sequence 45 dbid -1945915091 branch 761070192

Archived Log entry 15 added for thread 1 sequence 55 rlc 761070192 ID 0x8c044d2a dest 2:

RFS[6]: Opened log for thread 2 sequence 44 dbid -1945915091 branch 761070192

Archived Log entry 16 added for thread 2 sequence 45 rlc 761070192 ID 0x8c044d2a dest 2:

Archived Log entry 17 added for thread 2 sequence 44 rlc 761070192 ID 0x8c044d2a dest 2:

RFS[3]: Opened log for thread 1 sequence 57 dbid -1945915091 branch 761070192

RFS[2]: Opened log for thread 1 sequence 58 dbid -1945915091 branch 761070192

Media Recovery Log /opt/oracle/arch/yangdb2_44_761070192.log

Thu Sep 08 19:26:13 2011

Archived Log entry 18 added for thread 1 sequence 56 rlc 761070192 ID 0x8c044d2a dest 2:

Archived Log entry 19 added for thread 1 sequence 57 rlc 761070192 ID 0x8c044d2a dest 2:

Media Recovery Log /opt/oracle/arch/yangdb2_45_761070192.log

Media Recovery Log /opt/oracle/arch/yangdb2_46_761070192.log

Media Recovery Log /opt/oracle/arch/yangdb1_54_761070192.log

Media Recovery Log /opt/oracle/arch/yangdb2_47_761070192.log