Discussions
Categories
- 17.9K All Categories
- 3.4K Industry Applications
- 3.4K Intelligent Advisor
- 75 Insurance
- 537.6K On-Premises Infrastructure
- 138.7K Analytics Software
- 38.6K Application Development Software
- 6.1K Cloud Platform
- 109.6K Database Software
- 17.6K Enterprise Manager
- 8.8K Hardware
- 71.3K Infrastructure Software
- 105.4K Integration
- 41.6K Security Software
How to discover / promote HAS for Oracle Restart in EMCC 13c

Can anyone advise on how to discover / promote Oracle HAS (High Availability Service containing ASM) for Oracle Restart in EMCC 13c, please?
Answers
-
Hi,
It's pretty straight-forward and the documentation does a good job of outlining the steps you need to follow
Hope this helps
Ian -
Hi, Ian:
Thanks a lot for the direction. Actually my issue is the setup for monitoring ASM. NP logging in SQL*Plus with any password as sysdba, but no matter what tried in EMCC console it failed.
Any advice / direction / point is appreciated.
Kyle
-
Hi Kyle,
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
Ian
-
Hi, Ian:
Thank you so much for your advice which led to the following interesting findings:
Obviously the password file is missing in the picture. Any more advice on how to fix the issue, please?
Thanks and regards.
Kyle
-
-
Hi, Ian:
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?
Thanks.
Kyle
-
I could be wrong but i think you have to create asmsnmp...
here's a blog i googled once to help a customer with this.
ORACLE, MySQL, POSTGRES BOARD: 12c ASMSNMP user creation in RAC
-
Really surprised on how weird the thing is going.