Call now: 252-767-6166  
Oracle Training Oracle Support Development Oracle Apps

 E-mail Us
 Oracle Articles
New Oracle Articles

 Oracle Training
 Oracle Tips

 Oracle Forum
 Class Catalog

 Remote DBA
 Oracle Tuning
 Emergency 911
 RAC Support
 Apps Support
 Oracle Support

 SQL Tuning

 Oracle UNIX
 Oracle Linux
 Remote s
 Remote plans
 Application Server

 Oracle Forms
 Oracle Portal
 App Upgrades
 SQL Server
 Oracle Concepts
 Software Support

 Remote S


 Consulting Staff
 Consulting Prices
 Help Wanted!


 Oracle Posters
 Oracle Books

 Oracle Scripts

Don Burleson Blog 







Oracle 11g connect as sysdba causes ORA-01031

Oracle Database Tips by Donald BurlesonUpdated January 7, 2015

Question:  I am on 11gr2 trying to connect to Oracle as SYSDBA and I am getting the ORA-01031 error.  Is this the new strong authentication I've read about?

Answer:  Starting in Oracle 11g, all SQL*Plus sessions must be configured for remote login or you will get the ORA-01031: insufficient privileges error.  Connections with sysdba or sysoper privileges must always be authenticated. This is possible through OS authentication by assigning the appropriate OS group to the OS user.   

Another method is the use of a password file. If an 11g client is not configured you will get the ORA-01031: Insufficient privileges error when connect to Oracle in SQL*Plus as the SYS or SYSTEM user.  Oracle remote login is commonly configured with a password file using the orapwd utility.

Here are the steps to prevent the ORA-01031 error when connecting as sysdba in 11g:

1 - Create the password fileThis is done by executing the following command:

$ orapwd file=filename  password=password entries=max_users

The max_users is the number of database users that can be granted SYSDBA or SYSOPER.  This parameter should be set to a higher value than the number of anticipated users to prevent having to delete and recreate the password file. 

2 - Edit the init.ora parameter remote_login_passwordfile

This parameter must be set to either SHARED or EXCLUSIVE.  When set to SHARED, the password file can be used by multiple databases, yet only the SYS user is recognized.  When set to EXCLUSIVE, the file can be used by only one database, yet multiple users can exist in the file. 

SQL> show parameter password
NAME                          TYPE        VALUE
----------------------------- ----------- ----------remote_login_passwordfile     string      EXCLUSIVE

3 - Grant SYSDBA or SYSOPER to users When SYSDBA or SYSOPER privileges are granted to a user, that user's name and privilege information are added to the password file.

SQL> grant sysdba to scott;
Grant succeeded.

If you like Oracle tuning, you may enjoy my bestselling book Oracle Tuning: The Definitive Reference", with over 900 pages of BC's favorite tuning tips & scripts. 

You can buy it direct from the publisher for 30%-off and get instant access to the code depot of Oracle tuning scripts.



Oracle Training at Sea
oracle dba poster

Follow us on Twitter 
Oracle performance tuning software 
Oracle Linux poster


Burleson is the American Team

Note: This Oracle documentation was created as a support and Oracle training reference for use by our DBA performance tuning consulting professionals.  Feel free to ask questions on our Oracle forum.

Verify experience! Anyone considering using the services of an Oracle support expert should independently investigate their credentials and experience, and not rely on advertisements and self-proclaimed expertise. All legitimate Oracle experts publish their Oracle qualifications.

Errata?  Oracle technology is changing and we strive to update our BC Oracle support information.  If you find an error or have a suggestion for improving our content, we would appreciate your feedback.  Just  e-mail:  

and include the URL for the page.


Burleson Consulting

The Oracle of Database Support

Oracle Performance Tuning

Remote DBA Services


Copyright © 1996 -  2020

All rights reserved by Burleson

Oracle ® is the registered trademark of Oracle Corporation.