Shulou(Shulou.com)05/31 Report--

This article is to share with you about how to maintain ORACLE password files, the editor thinks it is very practical, so I share it with you to learn. I hope you can get something after reading this article.

A database administrator is a user with sysdba or sysoper privileges

If such users need to log in with database administrator privileges, they will use the password file to verify when they log in.

As an external component of the Oracle database, password files can be loaded in three modes:

Remote_login_passwordfile=NONE: do not load the password file, which means it is useless to give database administrator privileges to any number of users, because at this point the database administrator can only log in through a local connection. However, this mode does not affect the password modification of database administrators, the addition of administrators, or the withdrawal of administrator privileges.

Remote_login_passwordfile=EXCLUSIVE: single instance password file. Only in this state can users with database administrator privileges be changed their passwords, or add administrators or withdraw administrator privileges.

Remote_login_passwordfile=SHARED: a password file shared by multiple databases or RAC, in which an administrator can connect to the database remotely, but cannot change the administrator password or add a new administrator.

The following experiment is an error report of changing an administrator's password in shared mode

Click (here) to collapse or open

SYS@PROD1 > alter user sysuser1 identified by 123

2

Alter user sysuser1 identified by 123

*

ERROR at line 1:

ORA-01999: password file cannot be updated in SHARED mode

On the synchronization of password File and password Information in Database

In order to ensure that the password in the password file is consistent with the password information in the database, Oracle forbids the direct modification of the password file. When the password information in the database or the password information and authority ownership of sysdba, sysoper and sysasm are changed, the database automatically synchronizes the password file after changing its own password storage.

There are several scenarios in which the password file is inconsistent with the password information in the database:

1. The password file is not created when the database is built, and the new administrator is authorized or the password of sys is changed in the database. Later, when the password file is newly created, it will naturally be out of sync.

2. When remote_login_passwordfile changes from NONE to several other states, it will encounter a similar situation.

The steps when dealing with password file synchronization are

First create a password file-- > remote_login_passwordfile=EXCLUSIVE-- > use alter user, revoke and grant in the database to re-maintain the authority ownership and user passwords of sysdba, sysoper and sysasm in the database, so that the database can synchronize the password information into the password file-- > decide remote_login_passwordfile=SHARED according to the specific requirements of the environment

When the password file is out of sync with the database file, the user can also log in, and the way of verification is the password file.

The above is how to maintain the ORACLE password file. The editor believes that there are some knowledge points that we may see or use in our daily work. I hope you can learn more from this article. For more details, please follow the industry information channel.

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.