High Availability Data Guard, Sharding and Global Data Services (MOSC)

MOSC Banner

Please Help: Single Node Stanby ERROR: SLAVE COMMUNICATION ERROR WITH ASM; TERMINATING

edited Apr 2, 2012 11:00PM in High Availability Data Guard, Sharding and Global Data Services (MOSC) 8 commentsAnswered
How I can resolve the error getting on my single node physical standby database as below,

ERROR: SLAVE COMMUNICATION ERROR WITH ASM; TERMINATING PROCESS 20518

My primary side as 11.2.0.1 ASM RAC, HPUX 11.31,

alert.log stanbdy , kindly view read highlighted below.

ALTER DATABASE RECOVER TO LOGICAL STANDBY imalmir
Media Recovery Start: Managed Standby Recovery (imalmir)
 started logmerger process
Fri Jan 13 14:45:51 2012
Managed Standby Recovery not using Real Time Apply
Parallel Media Recovery started with 4 slaves
Fri Jan 13 14:45:52 2012
Warning: recovery process PR01 cannot use async I/O
Fri Jan 13 14:45:52 2012
Warning: recovery process PR02 cannot use async I/O
Fri Jan 13 14:45:52 2012
Warning: recovery process PR03 cannot use async I/O

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center