Password File recovery _ EM logon Failure Solution

Password File recovery _ EM login failure solution 1. The default location of the password file is/u01/oracle/product/10.2.0/db_1/dbs/orapwSID. If the password file is damaged, you cannot log on remotely. em cannot log on. The error "username or password invalid" may occur. 2. You can recreate the password file: cd/u01/oracle/product/10.2.0/db_1/dbs orapwd file = orapwdv11 password = oracle entries = 5 force = y 3, view the Password file: www.2cto.com SQL> select * from v $ pwfile_users; USERNAME SYSDB SYSOP certificate ----- SYS TRUE [oracle @ redhat dbs] $ strings orapwdv11] \ [ZORACLE Remote Password restart
4. If sysoper is assigned to system, system information is written to the password file: SQL> grant sysoper to system; Grant succeeded. SQL> select * from v $ pwfile_users; USERNAME SYSDB SYSOP ------------------------------ ----- SYS TRUE TRUESYSTEM FALSE TRUE 5, sys and sysoper permissions are different: SQL> select * from system_privilege_map where name like '% SYS % '; privilege name property ---------- certificate ----------- 3 alter system 0-4 audit system 0-83 SYSDBA 0-84 SYSOPER 0 www.2cto.com When you connect with SYSDBA or SYSOPER privileges, you connect with a default schema, not with the schema that is generally associated with your username. for SYSDBA this schema is SYS; for SYSOPER the schema is public SQL> conn/as sysdba SQL> show user USER user is "SYS" SQL> conn/as sysoper Connected. SQL> show user USER is "PUBLIC" 6. Password Authentication Type: SQL> show parameter NAME TYPE VALUE =----------- export remote_login_passwordfile string EXCLUSIVE volume = none | exclusive | shared is located at www.2cto.com none in the $ ORACLE_HOME/dbs/spfile $ ORACLE_SID.ora parameter file: exclusive Without Password File authentication: requires Password File authentication and exclusive use (default) shared: requires Password File authentication, different instance dba users can share the password file certificate ---------------------------------------------- www.2cto.com useful scripts: alter user system identified by oracle; alter user scott account unlock; grant sysdba to system; show parameter pfile show parameter spfile show parameter remote_login_passwordfile desc v $ pwfile_users; select * from v $ pwfile_users; cd/u01/oracle/product/10.2.0/db_1/dbs orapwd file = orapwdv11 password = oracle entries = 5 force = y strings orapwdv11 SQL> select * from v $ pwfile_users; USERNAME SYSDB SYSOP
---------------------------- ----- Sys true SQL> grant sysoper to system; Grant succeeded. SQL> select * from v $ pwfile_users; www.2cto.com USERNAME SYSDB SYSOP certificate ----- SYS TRUE TRUESYSTEM FALSE TRUE When you connect with SYSDBA or SYSOPER privileges, you connect with a default schema, not with the schema that is generally associated with your username. for SYSDBA this schema is SYS; for SYSOPER the schema is public SQL> select * from system_privilege_map where name like '% SYS % '; privilege name property ---------- detail ----------- 3 alter system 0-4 audit system 0-83 SYSDBA 0-84 SYSOPER 0 www.2cto.com SQL> show user USER user is "SYS" SQL> conn/as sysoper Connected. SQL> show user USER is "PUBLIC" author whhitgen