Ora-01031: insufficient privileges, privilege
Sqlplus "/as sysdba" cannot be connected or connect auxiliary sys/oracle @ sdyprod;
Reporting ora-01031: insufficient privileges Solution
Note that when multiple database instances are used, set ORACLE_SID = '',
1. Check whether sqlnet. ora (in the % ORACLE_HOME % NETWORKADMIN directory in WINDOWS) contains this sentence: SQLNET. AUTHENTICATION_SERVICES = (ETS). If not, add
2. Check whether the user logging on to windows (administrator or the user used when installing oracle) is included in the ORA_DBA group. This may occur when the domain user does not connect to the domain server.
3. Ensure that the remote_login_passwordfile parameter is EXCLUSIVE.
4. Check whether you need to use orapassw to generate a password file.
One solution case:
1. Check System parameters:
SQL> show parameter password
NAME TYPE VALUE
-----------------------------------------------------------------------------
Remote_login_passwordfile string EXCLUSIVE
2,
Select * from v $ pwfile_users;
SQL>
Null
3,
SQL> grant sysdba to sys;
Grant sysdba to sys
*
ERROR at line 1:
ORA-01994: GRANT failed: password file missing or disabled
4. Create a password file
D:/> orapwd file = "D:/oracle/product/10g/db_1/database/PWDoratest. ora" password = gp
Oswong entries = 10
5,
SQL> select * from v $ pwfile_users;
USERNAME SYSDB SYSOP
----------------------------------------
SYS TRUE
SYS is displayed normally.
6. log on remotely with SYSDBA and use it properly.
If the password file is created incorrectly, the following error is reported:
Ora-01031: insufficient privileges
The password file must be named in orapwsid, And the sid is case sensitive. Because the Target Database needs to verify the password when connecting to the Auxiliary Database,
If the above rule is violated, a prompt is displayed for ORA-01031: insufficient privileges.
This error occurs when I create a duplicate database in linux because the path and name of the password file are incorrect.
----- End -------
-- This article