Summary of Ora-01031:insufficient Privileges solution method

Author:skate
Time:2009/06/24

Sqlplus "/As SYSDBA" not even on, reported ora-01031:insufficient privileges solution

Note that when multiple database instances, set oracle_sid= ',

1, check whether the Sqlnet.ora (Windows located in the%oracle_home%networkadmin directory) contains this sentence: sqlnet.authentication_services= (NTS), no words plus

2. Check that users who log on to Windows (the administrator or the user who installed Oracle) are not included in the ORA_DBA group and this behavior may occur if the domain user is not connected to the domain server.

3. To ensure the remote_login_passwordfile parameter = EXCLUSIVE.

4. See if you need to use ORAPASSW to generate password files.

A workaround case:

1, check the system parameters:
Sql> Show parameter password

NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
Remote_login_passwordfile string EXCLUSIVE
2,
SELECT * from V$pwfile_users;
Sql>
is empty

3,
sql> Grant SYSDBA to SYS;
Grant SYSDBA to Sys
*
ERROR at line 1:
Ora-01994:grant failed:password file missing or disabled
4, the establishment of password documents
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 True
SYS is displayed normally.
6, the remote to SYSDBA login, can be used normally.

If the password file is created with a problem, it will also be reported as an error:

Ora-01031:insufficient Privileges

The password file should have a named format of Orapwsid and the SID is case-sensitive. Because the target database needs to authenticate the password when it connects to auxiliary database,
If the above rules are violated, ora-01031:insufficient privileges will be prompted.

When I created the duplicate database with Linux, it was because the password file created the wrong path and name.

-----End-------