Can you confirm that the ASM instance has been started up with a password file? srvctl config asm should show this.
Next thing would be to check the list of users returned from querying v$pwfile_users. ASMSNMP should be listed in this resultset.
A final thought is that you should (Ideally) be testing connectivity from a remote machine, so perhaps use your client machine and use SQLcl with an EZ connect string to be sure, e.g. sql.exe sys/<your_asm_password_goes_here>@wccdlora01.wcmbp.pri:1800:+ASM as sysdba
Hope this helps
Thanks a lot for your direction.
Interesting, no equivalent of the ref doc for Linux, but the following was done on Linux per the ref doc for Windows:
- A password file created for ASM
- ASM config modified in OCR
- HAS restarted
- Logged into ASM as "/ as sysasm", but granting sysasm / sysdba to asmsnmp or sys (as per the doc) both returned, "ORA-01918: user 'ASMSNMP' (or 'SYS') does not exist" and "ORA-27037: unable to obtain file status" in both SQL*Plus and the trace file without any more info.
- No diff observed in the behavior in both SQL*Plus remote login and ASM discover / promote in EMCC.
Any more advice on what I'm missing, or have to open an SR with Oracle Support?