Three login verification mechanisms for Oracle Database

Then, log on to the common user. If the logon succeeds, the lisi user password is successfully modified. 2. Three authentication mechanisms for databases 1) operating system verification: the current user logged on is the administrator, and no user or password verification is required. 2) password file verification: After the System user is deleted, it can only be verified by the password file. For the sake of security, in the actual development process

Then, log on to the common user. If the logon succeeds, the lisi user password is successfully modified. 2. Three authentication mechanisms for databases 1) operating system verification: the current user logged on is the administrator, and no user or password verification is required. 2) password file verification: After the System user is deleted, it can only be verified by the password file. For the sake of security

Then, log on to the common user. If the logon succeeds, the lisi user password is successfully modified.

2. Three database verification mechanisms

1) operating system verification: The current login user is the administrator and does not require user and password verification.

2) password file verification: After the System user is deleted, it can only be verified by the password file. For the sake of security, the operating system verification should be deleted during actual development. If the password of the SYS user is forgotten or lost, delete the password file, then generate a new password file. Specific Operation: change the password file and delete the original file Password File E: \ app \ Administrator \ product \ 11.2.0 \ dbhome_1 \ database \ PWDorcl. ora

Generate a new password file:

C: \ Users \ Administrator> orapwdfile = E: \ app \ Administrator \ product \ 11.2.0 \ dbhome_1 \ database \ PWDorcl. ora passwoed = 123456 entries = 10

Log on to the system again with the password of 123456.

View the number of privileged users in the password file: select * from u $ pwfile_users;

3) database verification: the user and password must be correct before logon.

3. Oracle Startup Process in Linux: first start the listener: lsnrctl start. You can verify sqlplus/nolog, conn sys/oracle as sysdba (sys user is not a database verification, but operating system verification and password file verification), and then start the instance: startup;

Oracle startup in Windows: lsnrctl start, oradim-starup-sid orcl.