Partially Documented Parameters - Secrets of the Oracle Database - page 22

Next, we create a database user whose name is formed by prepending the string ops$ to the
operating system user name, in this case “ndebes”, and grant the privileges CONNECT and SYSOPER
to the new user.
SQL> CREATE USER ops$ndebes IDENTIFIED BY secret;
User created.
SQL> GRANT CONNECT, SYSOPER TO ops$ndebes;
Grant succeeded.
SQL> SELECT * FROM v$pwfile_users;
USERNAME SYSDBA SYSOPER
------------------------------ ------ -----
SYS TRUE TRUE
OPS$NDEBES FALSE TRUE
As evidenced by Figure 1-3, the database user OPS$NDEBES can connect via the Oracle
Net TCP/IP adapter from a Windows system. Password authentication is required, since
REMOTE_OS_AUTHENT=FALSE is set.
Figure 1-3. SQL*Plus Session via the Oracle Net TCP/IP Adapter
Back on UNIX, the operating system user “ndebes” can connect without entering a password.
$ id
uid=500(ndebes) gid=100(users) groups=100(users)
$ sqlplus /
SQL*Plus: Release 10.2.0.3.0 - Production on Wed Sep 5 08:02:33 2007
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - Production
SQL> SHOW USER
USER is "OPS$NDEBES"
Thanks to password authentication and a password file, connecting AS SYSOPER works too.
SQL> CONNECT ops$ndebes/secret AS SYSOPER
Connected.
SQL> SHOW USER
USER is "PUBLIC"
SQL> SELECT * FROM session_privs;
PRIVILEGE