After ora_setup is run during installation, wrong ASM SID entry is made to the paramdb.
Instead of ASM1 entry, ASM2 entry is made to the paramdb.
ASM2 SID does not exist on the system.
This issue can happen if you run 'script' before ora_setup is run.
Do not run script before running ora_setup.
When ora_setup is run it normally makes some entries in the paramdb file.
In Shareplex 6.0, It also makes an entry for the ASM SID in the paramdb.
'script' is run so ora_setup run is logged to a file
This issue was observed in Solaris 9 machine.
© 2025 Quest Software Inc. ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center