Sqlplus "/As SYSDBA" not connected, ora-01031:insufficient privileges solution
Note When multiple DB instances are set oracle_sid= ',
1, check Sqlnet.ora (under Windows in the%oracle_home%networkadmin directory) contains this sentence: sqlnet.authentication_services= (NTS), no words plus
2. Check whether the user logged in to Windows (Administrator or the user who installed Oracle) is included in the ORA_DBA group, and this behavior may occur when the domain user is not connected to a domain server.
3. To ensure that the remote_login_passwordfile parameter = EXCLUSIVE.
4. See if you need to generate a password file using ORAPASSW.
A solution 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. Establish password file
--d:/>orapwd file= "D:/oracle/product/10g/db_1/database/pwdoratest.ora" PASSWORD=GP
--oswong entries=10
found no password file;
Check that the password file is correct [oracle@guohuias3 dbs]$ CD $ORACLE _home/dbs
[ORACLE@GUOHUIAS3 dbs]$ ls-l ORAPW *
-RW-R-----1 Oracle Oinstall 5120 Jul 9 Orapwauxy. Pwd
-RW-R-----1 Oracle oinstall 2560 20:26 ORAPWORCL
Check the current $ORACLE _SID=ORCL
Find the ORCL of the password file is lowercase, correct it over [ORACLE@GUOHUIAS3 dbs]$ MV Orapworcl ORAPWORCL
and query the related view again:
SQL > select * from v $pwfile _users;
USERNAME Sysdb SYSOP
------------------------------ ----- -----
SYS true True
You can see that there is a corresponding password file.
Now log in again [ORACLE@GUOHUIAS3 dbs]$ sqlplus SYS/KELANTAS@ORCL as Sysdba
SQL * Plus:release 10.2. 0.1. 0-production on Fri Feb 18 20:51:05 2011
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2. 0.1. 0-production
With the partitioning, OLAP and Data Mining options
SQL >
The problem is solved.
5.
Sql> select * from V$pwfile_users;
USERNAME Sysdb SYSOP
------------------------------ ----- -----
SYS true True
SYS shows up normally.
6, re-login at the remote to SYSDBA, can be used normally.
If there is a problem with the password file creation, it will also report the following error:
Ora-01031:insufficient Privileges
The name format of the password file should be Orapwsid, and the SID is case-sensitive. Because the target database needs to verify the password when connecting to auxiliary database,
If you violate the above rules, you will be prompted to ora-01031:insufficient privileges.
When I created the duplicate database with Linux, I encountered this error because the path and name of the password file was not correct.
-----End-------