ASM dba_user v$pwfile_users

Applies To

All Users

Summary

How to recreate the ASMSNMP user when its password is forgotten?

Example: DBCA fails because the provided password for ASMSNMP is not valid/proper/correct

Solution

As the ASM home software owner, connect to ASM instance via sqlplus:

Note: If this is a clustered ASM configuration, then connect to one of the clustered ASM instances (say, +ASM1)

$ . oraenv <---- enter the ASM instance name for ORACLE_SID (for non-RAC this is +ASM, but for RAC this can be +ASM1)

$ sqlplus / as sysasm

SQL> select * from v$pwfile_users;

If the previous command lists ASMSNMP then remove it:

SQL> drop user ASMSNMP;

SQL> create user asmsnmp identified by <password here>;

grant sysdba to asmsnmp;

SQL> select * from v$pwfile_users;

Desired output:

USERNAME SYSDB SYSOP SYSAS

SYS TRUE TRUE TRUE

ASMSNMP TRUE FALSE FALSE

Note: If clustered ASM configuration, the above should also cascade to the Oracle (orapw<asm instance name>) files for the other nodes.

To test this, connect to the other ASM instances within the cluster and query v$pwfile_users and verify ASMSNMP user is listed (same as for +ASM1)

Attachments :

----create user

Applies To

All Users

Summary

The present document describes how to create an ASMSYS user.

Solution

On release 11g and onwards, you need to create an ASM user and grant the SYSASM role. The purpose of the SYSASM role is to provide a level of separation between the RDBMS & ASM credentials.

The SYSASM role, which has full capability on the ASM instance, is authenticated through the OSASM user group, similar to the SYSDBA roles, which is authenticated through OSDBA.

The following example shows how to connect as SYSASM and configure a new user for SYSASM role:

+ASM:oracle> export ORACLE_SID=+ASM

+ASM:oracle>sqlplus "/as sysasm "

SQL*Plus: Release 11.1.0.6.0 - Production on Thu Oct 1 15:44:00 2009

Connected to:

Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 - Production

With the Partitioning, OLAP, Data Mining and Real Application Testing options

SQL> create user ASMUSER identified by oracle;

User created.

SQL> grant SYSASM , SYSOPER to ASMUSER ;

Grant succeeded.

SQL> exit

Then connect as ASMUSER:

+ASM:oracle> export ORACLE_SID=+ASM

+ASM:oracle>sqlplus "ASMUSER /oracle as sysasm "

SQL*Plus: Release 11.1.0.6.0 - Production on Thu Oct 1 15:45:26 2009

Connected to:

Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 - Production

With the Partitioning, OLAP, Data Mining and Real Application Testing options

SQL> select * from v$pwfile_users;

USERNAME SYSDBA SYSOPE SYSASM

SYS TRUE TRUE TRUE

ASMUSER FALSE TRUE TRUE