ORA-01031 while connecting as sysdba from remote machine
ORA-01031 while connecting as sysdba from remote machine: "The problem scenarios and solution described in this topic is only applicable for HP-UX Itanium. Whenever database server you are using if you ever face ORA-01031 while connecting as sysdba immediately you should look at the broader topic which is described in ORA-1031 insufficient privileges during OS and password file authentication.
Problem Description
Remote connections as SYSDBA are failing with ORA-01031 like below.
$ sqlplus sys/syspassword@tnsnames as sysdba
SQL*Plus: Release 10.2.0.3.0 - Production on Sun Mar 20 19:12:45 2011
Copyright (c) 1982, 2006, Oracle. All Rights Reserved.
ERROR:
ORA-01031: insufficient privileges
The REMOTE_LOGIN_PASSWORDFILE parameter is set to EXCLUSIVE :
SQL> show parameter remote_login
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
remote_login_passwordfile string EXCLUSIVE
Recent Changes
Created a passwordfile with nosysdba=y.
Cause of the Problem
The issue is caused by the fact that the passwordfile was created with the NOSYSDBA option set to Y. When this is set to Y the remote SYSDBA connections are banned, irrespective to the fact that Database Vault is enabled or not.
The parameter nosysdba was added to the orapwd utilty as part of the Database Vault product, however it was made available with the Standard and Enterprise Edition databases that do not have Database Vault installed too, nosysdba=y can be used to lockout remote sysdba connections, when set it will still allow you to connect as SYSOPER, thus still leaving some purpose to having a remote login passwordfile at all.
Solution of the Problem
1) If the privileges associated with SYSOPER are sufficient, login as SYSOPER, this will allow you to perform some basic task such as to shutdown or startup the database:
$ sqlplus sys/pass@tnsnams as sysdba
SQL*Plus: Release 10.2.0.3.0 - Production on Sun Mar 20 19:12:45 2011
Copyright (c) 1982, 2007, Oracle. All Rights Reserved.
ERROR:
ORA-01031: insufficient privileges
Enter user-name: sys/pass@tnsnams as sysoper
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL>
2) Create the passwordfile with the NOSYSDBA option set to N :
$ orapwd file=orapwsidname entries=3 password=syspassword force=y nosysdba=n
$ sqlplus sys/pass@tnsnams as sysdba
SQL*Plus: Release 10.2.0.3.0 - Production on Sun Mar 20 19:12:45 2011
Copyright (c) 1982, 2006, Oracle. All Rights Reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - 64bit Production
With the Partitioning, Oracle Label Security, OLAP and Data Mining Scoring Engine options
SQL>
"
Problem Description
Remote connections as SYSDBA are failing with ORA-01031 like below.
$ sqlplus sys/syspassword@tnsnames as sysdba
SQL*Plus: Release 10.2.0.3.0 - Production on Sun Mar 20 19:12:45 2011
Copyright (c) 1982, 2006, Oracle. All Rights Reserved.
ERROR:
ORA-01031: insufficient privileges
The REMOTE_LOGIN_PASSWORDFILE parameter is set to EXCLUSIVE :
SQL> show parameter remote_login
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
remote_login_passwordfile string EXCLUSIVE
Recent Changes
Created a passwordfile with nosysdba=y.
Cause of the Problem
The issue is caused by the fact that the passwordfile was created with the NOSYSDBA option set to Y. When this is set to Y the remote SYSDBA connections are banned, irrespective to the fact that Database Vault is enabled or not.
The parameter nosysdba was added to the orapwd utilty as part of the Database Vault product, however it was made available with the Standard and Enterprise Edition databases that do not have Database Vault installed too, nosysdba=y can be used to lockout remote sysdba connections, when set it will still allow you to connect as SYSOPER, thus still leaving some purpose to having a remote login passwordfile at all.
Solution of the Problem
1) If the privileges associated with SYSOPER are sufficient, login as SYSOPER, this will allow you to perform some basic task such as to shutdown or startup the database:
$ sqlplus sys/pass@tnsnams as sysdba
SQL*Plus: Release 10.2.0.3.0 - Production on Sun Mar 20 19:12:45 2011
Copyright (c) 1982, 2007, Oracle. All Rights Reserved.
ERROR:
ORA-01031: insufficient privileges
Enter user-name: sys/pass@tnsnams as sysoper
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL>
2) Create the passwordfile with the NOSYSDBA option set to N :
$ orapwd file=orapwsidname entries=3 password=syspassword force=y nosysdba=n
$ sqlplus sys/pass@tnsnams as sysdba
SQL*Plus: Release 10.2.0.3.0 - Production on Sun Mar 20 19:12:45 2011
Copyright (c) 1982, 2006, Oracle. All Rights Reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - 64bit Production
With the Partitioning, Oracle Label Security, OLAP and Data Mining Scoring Engine options
SQL>
http://romance-scam.blogspot.com/
http://banscam.blogspot.com/
http://neverscam.blogspot.com/
http://hatescam.blogspot.com/
http://reportyourscam.blogspot.com/
http://bamscam.blogspot.com/
http://igotscam.blogspot.com/
http://arjudba.blogspot.com/
http://scamhack.blogspot.com/
http://scam-mails.blogspot.com/
http://banscam.blogspot.com/
http://neverscam.blogspot.com/
http://hatescam.blogspot.com/
http://reportyourscam.blogspot.com/
http://bamscam.blogspot.com/
http://igotscam.blogspot.com/
http://arjudba.blogspot.com/
http://scamhack.blogspot.com/
http://scam-mails.blogspot.com/
Comentarios
Publicar un comentario