Password Files   «Prev  Next»

Lesson 7 Connecting as INTERNAL with a password
Objective Connect to the COIN database using the internal password.

Connecting as INTERNAL using Password

Connecting as an internal user

Now that you have created a password file and set the REMOTE_LOGIN_PASSWORDFILE initialization parameter to EXCLUSIVE, you will need to use a password whenever you connect as the INTERNAL user. Let us say, for example, that you created the password file using the following command: orapwd file=pwdcoin.ora password=herman entries=10

Different ways of entering the password

The password specified in the command, “herman” in this example, becomes the password for the internal user. When you try to connect internally, you can either supply the password as part of the CONNECT command, or you can allow Oracle to prompt you for it. The following series of images illustrate several possibilities:

Connecting as internal using Password

1) In this example, we are connecting to the default database, and allowing Oracle to prompt us for the password.
1) In this example, we are connecting to the default database, and allowing Oracle to prompt us for the password. 
SQL> connect internal
Password:
Connected.
SQL>

2) In this example, we are connecting to a database across the network identified by the Oracle Network Service named coin
2) In this example, we are connecting to a database across the network identified by the Oracle Network Service named coin, but still allowing Oracle to prompt us for the password. 
SQL> connect internal@coin
Password:
Connected.
SQL>

3) In this example, we are connecting to the default database, and supplying the internal password as part of the CONNECT command.
3) In this example, we are connecting to the default database, and supplying the internal password as part of the CONNECT command. 
SQL> connect internal/herman
Connected.
SQL>

4) In this example, we put it all together, and supply both a Oracle Network service name and the internal password as part of the CONNECT command.
4) In this example, we put it all together, and supply both an Oracle Network service name and the internal password as part of the CONNECT command 
SQL> connect internal/herman@coin
Connected.
SQL>

  1. In this example, we are connecting to the default database, and allowing Oracle to prompt us for the password.
  2. In this example, we are connecting to a database across the network identified by the Oracle Network Service named coin, but still allowing Oracle to prompt us for the password.
  3. In this example, we are connecting to the default database, and supplying the internal password as part of the CONNECT comman
  4. In this example, we put it all together, and supply both an Oracle Network service name and the internal password as part of the CONNECT command


As you saw in the series of images above, when you enter a password in response to a prompt, Oracle does not echo these characters to the screen. This prevents other people from seeing what you type. The real utility of password files is that it allows you to grant individual DBAs the ability to perform administrative functions, such as starting and shutting down a database, using his or her own user name. In the next two lessons, you will learn how to grant these administrative privileges to other database administrators.

REMOTE_LOGIN_PASSWORDFILE

Property Description
Parameter type String
SyntaxREMOTE_LOGIN_PASSWORDFILE={shared | exclusive | none}
Default valueexclusive
Modifiable No
Basic Yes
Real Application ClustersMultiple instances must have the same value.

REMOTE_LOGIN_PASSWORDFILE specifies whether Oracle checks for a password file.
Values:
  1. shared: One or more databases can use the password file. The password file can contain SYS as well as non-SYS users.
  2. exclusive: The password file can be used by only one database. The password file can contain SYS as well as non-SYS users.
  3. none: Oracle ignores any password file. Therefore, privileged users must be authenticated by the operating system.