Insufficient Privileges connecting to ASM instance as SYSASM remotely

In Oracle 11g they introduced the new SYSASM privilege/login for doing ASM specific work. The word is that SYSDBA will be deprecated in later releases. I was in OEM GC (Oracle Enterprise Manager Grid Control) to do some work on on ASM instance and found I could not login this way, it gave me “ORA-01031: insufficient privileges”; however, when I tried to login using the sys, the same password, as SYSDBA then it worked fine.

The solution to this was fairly simple. At this point I’m not sure if this is default behavior or something that was done during installation when you set the groups for ASM access, but you can check for the remote issue and fix it as follows.

Check if remote access is enabled for SYSASM. Login on the local server.

->sqlplus / as sysasm
SQL> select * from v$pwfile_users;
USERNAME SYSDB SYSOP SYSAS
—————————— —– —– —–
SYS TRUE TRUE FALSE

If the SYSASM column is FALSE then it is turned off. If it is turned off then turn it on:

SQL> grant sysasm to sys;
Grant succeeded.

SQL> select * from v$pwfile_users;
USERNAME SYSDB SYSOP SYSAS
—————————— —– —– —–
SYS TRUE TRUE TRUE

Now you should be able to login remotely as SYSASM. Of course you’ll need to consider the security risk of having that access enabled remotely – be sure you at least have a good password set across all nodes.

One response to “Insufficient Privileges connecting to ASM instance as SYSASM remotely

  1. Pingback: Can’t connect remotely to ASM as SYSASM remotely | Jed's

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s