In SharePlex versions prior to 7.5, when ora_setup is run for an Oracle instance with ASM, the corresponding ASM SID is entered in the paramdb as the parameter SP_OCT_ASM_SID.
In a RAC environment when ora_setup is run for the second oracle instance SP_OCT_ASM_SID is overwritten with the second instances ASM SID.
Whenever there is a failover or failback the corresponding ASM SID is not found. This issue is seen when the ASM SID for the multiple instances of RAC is not the same.
In versions prior to 7.5, ora_setup uses bequeath connection to connect to ASM instance. Since the paramdb file can only have one entry for SP_OCT_ASM_SID, this entry must be updated each time there is a failover.
Starting with version 7.5, SharePlex automatically queries for the correct ASM instance name. This requires an additional tns_alias that SharePlex would use to connect to a LOCAL Oracle instance, query v$asm_client (capture runs this query) and obtain the proper ASM instance name.
Prior to version 7.5:
WORKAROUND 1:
Paramdb has to be edited with the right ASM SID whenever there is a failover or a failback.
WORKAROUND 2:
Have two paramdb files with two different ASM SIDs and use the appropriate one with failover or a failback.
