SQL> show parameter password

NAME TYPE VALUE
------------------------------------ ----------- ----------
remote_login_passwordfile string EXCLUSIVE

3. Grant SYSDBA or SYSOPER to users. When SYSDBA or SYSOPER privileges are granted to a user, that user's name and privilege information are added to the password file.

SQL> grant sysdba to scott;

Grant succeeded.

4. Confirm that the user is listed in the password file.

SQL> select * from v$pwfile_users;

USERNAME SYSDBA SYSOPER
------------------------------ ------ -------
SYS TRUE TRUE
SCOTT TRUE FALSE

Now the user SCOTT can connect as SYSDBA. Administrative users can be connected and authenticated to a local or remote database by using the SQL*Plus connect command. They must connect using their username and password, and with the AS SYSDBA or AS SYSOPER clause:

SQL> connect scott/tiger as sysdba;
Connected.

The DBA utilizes the orapwd utility to grant SYSDBA and SYSOPER privileges to other database users. The SYS password should never be shared and should be highly classified.

 

The above is an excerpt from Oracle Utilities - Using Hidden Programs, Import/Export, SQL Loader, oradebug, Dbverify, Tkprof and More by Rampant TechPress (Dave Moore).

It’s only $19.95 and you can order the book and get instant access to the online Oracle utilities scripts:

http://www.rampant-books.com/book_2003_1_utils.htm