Use and maintenance of Oracle password files 1th/3 page _oracle

The Oracle tutorial you are looking at is: Use and maintenance of Oracle password files.

Summary: Oracle relational database system is widely used for its excellent performance, and ensuring database security is an important part of database management. On the basis of summarizing the security management of Oracle database, this paper introduces the creation, use and maintenance of password files of Oracle database system in detail, for everyone's reference.

In Oracle database systems, There are two ways to authenticate users if they want to log on to an Oracle database as a privileged user (Internal/sysdba/sysoper): Authenticate with an operating system-integrated authentication or a password file that uses an Oracle database. Therefore, the management of password files, for the control of authorized users from remote or local login Oracle database system, the implementation of database management work, has important significance.

The Oracle database password file holds the Superuser internal/sys password and the user name/password of other privileged users, which is generally stored in the Oracle_home\database directory.

　　First, the creation of the password file:

When you create a database instance using Oracle Instance Manager, a corresponding password file is created automatically under the Oracle_home\database directory. The file name is Pwdsid.ora, where the SID represents the corresponding Oracle database system identifier. This password file is the basis for the initial database management effort. After this, the administrator can also use tool ORAPWD.EXE to create the password file manually, as needed, with the following command format:

C:\>orapwd file=< FILENAME > PASSWORD
=< PASSWORD > entries=< max_users >

The meaning of each command parameter is:
FileName: password filename;

PASSWORD: Set the password of the Internal/sys account;

Max_users: The maximum number of users that can be stored in the password file, corresponding to the maximum number of users allowed to log on to the database with Sysdba/sysoper permissions. Because in future maintenance, if the number of users exceeds this limit, the password file needs to be rebuilt, so this parameter can be set larger as needed.

After you have the password file, you need to set the initialization parameter Remote_login_passwordfile to control the use status of the password file.

Current 1/3 page 123 Next read the full text