saCkptCheckpointOpen() API Call Returns SA_AIS_ERR_TIMEOUT for Collocated Checkpoints on New Standby Nodes
Last updated on OCTOBER 10, 2012
Applies to:Oracle Communications OpenSAFfire - Version 6.2.0 and later
Information in this document applies to any platform.
When running an OpenSAFfire cluster with two Service Controllers (SC-1 and SC-2) in Active/Standby mode respectively, after restarting OpenSAFfire on SC-1, it should rejoin the cluster as the new Standy SC and synchronize checkpoints with the active SC..
However a problem exists with the OpenSAFfire checkpoint service where calls to saCkptCheckpointOpen() to syncronize a collocated checkpoint with the active checkpoint results in SA_AIS_ERR_TIMEOUT(5).
Restart of the active SC and it rejoins the cluster as the new standby SC.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms