ORA-10878: parallel recovery slave died unexpectedly

Posted: March 9, 2013 in StandBy
Tags: ,

Recently i have faced “ORA-10878: parallel recovery slave died unexpectedly” on one standby server running on IBM Power systems AIX 7.1 with database version being 11.2.0.1. Whenever i am putting standby database in managed mode, i got this error after few minutes and recovery process stops. I am using the below command for putting standby in managed mode:

SQL> alter database recover managed standby database disconnect from session;

Database altered.

Here are few lines from init.ora file of standby database.

Exception [type: SIGSEGV, Invalid permissions for mapped object] [ADDR:0x0] [PC:0x100137314, kggibr()+52] [flags: 0x0, count: 1]
Errors in file /u01/app/orahyp_r/admin/diag/rdbms/hfm11sbd/HFM11PRD/trace/HFM11PRD_pr0c_36700316.trc (incident=60321):
ORA-07445: exception encountered: core dump [kggibr()+52] [SIGSEGV] [ADDR:0x0] [PC:0x100137314] [Invalid permissions for mapped object] []
Incident details in: /u01/app/orahyp_r/admin/diag/rdbms/hfm11sbd/HFM11PRD/incident/incdir_60321/HFM11PRD_pr0c_36700316_i60321.trc
Mon Feb 18 05:39:24 2013
Sweep [inc][60321]: completed
Sweep [inc2][60321]: completed
Mon Feb 18 05:39:56 2013
Recovery Slave PR0C died
Mon Feb 18 05:39:56 2013
Errors with log /u05/oradata/HFM11SBD/HFM11PRD_503651737949656.ARC
MRP0: Background Media Recovery terminated with error 448
Errors in file /u01/app/orahyp_r/admin/diag/rdbms/hfm11sbd/HFM11PRD/trace/HFM11PRD_pr00_24117290.trc:
ORA-00448: normal completion of background process
Recovery interrupted!
Recovered data files to a consistent state at change 1066274174
Errors in file /u01/app/orahyp_r/admin/diag/rdbms/hfm11sbd/HFM11PRD/trace/HFM11PRD_pr00_24117290.trc:
ORA-00448: normal completion of background process
Errors in file /u01/app/orahyp_r/admin/diag/rdbms/hfm11sbd/HFM11PRD/trace/HFM11PRD_mrp0_23068818.trc:
ORA-10878: parallel recovery slave died unexpectedly
MRP0: Background Media Recovery process shutdown (HFM11PRD)

After spending few time on google, i got the workaround for this error but exact solution is provided by Oracle support only.
As per Oracle support this is bug 9728806 which is fixed in 11.2.0.2. There is also one patch available for this bug. Please contact Oracle support, for confirmation of bug and before applying any kind of patch on your database.

Workaround for this error is to start the recovery process in “noparallel” mode as by default recovery process starts in parallel mode. Here is the command to start recovery process in “noparallel” mode.

SQL> alter database recover managed standby database disconnect from session noparallel;

Database altered.

Now, recovery process will start with a single process and should not crash.

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s