Shulou(Shulou.com)06/01 Report--

Change the database password file name or location

If you change the database password file name or location, run the following command for the change to take effect:

ALTER SYSTEM FLUSH PASSWORDFILE_METADATA_CACHE

This command refreshes the metadata cache and then logs in to the database using the new password file. In an Oracle RAC environment, this command clears the cache in all Oracle RAC databases, but some databases may still use the old password file until the changes are propagated in all Oracle RAC databases.

After running this command, you can verify the changes by querying the V$PASSWORDFILE_INFO view.

II. Sharing and disabling database password files

Use the initialization parameter REMOTE_LOGIN_PASSWORDFILE to control whether database password files are shared among multiple Oracle database instances. You can also use this parameter to disable password file authentication.

To share a password file or disable password file authentication:

Sets the REMOTE_LOGIN_PASSWORDFILE initialization parameters.

You can set the REMOTE_LOGIN_PASSWORDFILE initialization parameter to one of the following values:

None: setting this parameter to none causes the Oracle database to behave like a password file. That is, no permission connections are allowed on non-secure connections.

Exclusive: (default) the exclusive password file can only be used in one database. Only exclusive files can be modified. Use the exclusive password file to add, modify, and delete users. It also allows you to change the password of SYS, SYSBACKUP, SYSDG, or SYSKM using the ALTER USER command.

When an exclusive password file is stored in an Oracle ASM disk group, it can be used by a single instance database or multiple instances of the Oracle Real Application Clusters (Oracle RAC) database.

When the exclusive password file is stored on the operating system, it can only be used with one instance of a database.

The shared:shared password file can be used by multiple databases running on the same server, or by multiple instances of the Oracle RAC database, even if it is stored on the operating system. The shared password file is read-only and cannot be modified. Therefore, users cannot be added to the shared password file. Any attempt to do so or change the password of SYS or other users with administrative privileges will result in an error. When REMOTE_LOGIN_PASSWORDFILE is set to exclusive, all users who need administrative privileges must be added to the password file. After you add all the users, you can change REMOTE_LOGIN_PASSWORDFILE to shared, and then share the file.

This option is useful if you use a single password file to manage multiple databases.

Shared cannot be specified for Oracle ASM password files.

If REMOTE_LOGIN_PASSWORDFILE is set to exclusive or shared, and the password file is missing, this is equivalent to setting REMOTE_LOGIN_PASSWORDFILE to none.

Delete the database password file

If you no longer need the database password file, you can delete it. If you determine that the database password file is no longer needed to authenticate the user, delete the file:

Delete the database password file and optionally reset the REMOTE_LOGIN_PASSWORDFILE initialization parameter to none.

After you delete this file, only those users who can be authenticated by the operating system can perform SYSDBA, SYSOPER, SYSBACKUP, SYSDG, or SYSKM database management operations.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.