Return
-
Title
Capture stopped due to the wrong ASM SID -
Description
Capture stopped due to the wrong ASM SID and the following error logged in the event_log
Error in ASM setup: ASMsetup: ASMQuerySetup: ASMQueryGetHomeFromSID: Entry for SID +ASM2 not found in oratab file. [sp_ocap/20774] -
Cause
The wrong ASMSID picked in the paramdb, which doesn't exist in the oratab file
-
Resolution
1. Issue Unix command to check which ASM SID is running:
ps -ef|grep ASM
2. Modify the paramdb file with the correct ASM SID
3. Bounce Capture process