My Oracle Support Banner

SaMsgQueueOpen Failed After Switchover (Doc ID 1497584.1)

Last updated on MARCH 04, 2019

Applies to:

Oracle Communications OpenSAFfire - Version 6.2.0 and later
Information in this document applies to any platform.

Symptoms


Start opensaf on SC-b: Active
Start opensaf on PL-x: Active
Start opensaf on SC-a:Standby

Stop opensaf on SC-b>
After switchover SC-a becomes Active.
But failed to open message queue.

After switchover, pm is opening queue with null parameters but failed with error code 12(SA_AIS_ERR_NOT_EXIST).
After this pm is opening queue with proper parameters but failed with error code 18(SA_AIS_ERR_NO_RESOURCES).
After this pm retry to open queue but failed with error code 10(SA_AIS_ERR_BUSY).

First message queue opening failed with error code 12, then after retry it failed with error code 10.

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.