Sysdba cannot log on remotely. What should we do (reprinted) and sysdba log on remotely?
Sysdba cannot log on remotely, which is also a common problem.
How can we solve this problem?
When we use sysdba to log on, it is necessary to manage our database instances, especially when the server is no longer running.
When we use sqlplus "/as sysdba"
Yes.
However, if you use sqlplus "sys/password @ tnsname as sysbda", you cannot log on.
Here, our errors are generally divided into two types:
First type: prompt ORA-01031: insufficient privileges (insufficient permissions)
Reference:
Sqlplus "sys/password@10.0.0.195 as sysdba"
ERROR:
ORA-01031: insufficient Permissions
If this is the case, you are using this sys to log on, and it is indeed the sysdba permission. Why does the logon prompt that your permission is not enough.
The problem occurs in the password file. Because your password file is missing or does not exist, the Oracle instance's permission to sysdba is based on this
Password File to determine, if your user is granted to sysdba, then the user's password and user name are also in this password file.
In this way, you are not a role of sysdba. Of course, as sysdba will prompt that the permission is insufficient.
Why is this done? If our database is not open, some dynamic views cannot be opened. Therefore, oracle must
The user's password and username are put in an independent file, so that the database is not open, and there is a place to judge.
How to solve the problem. Let's first judge
Execute SQL
SQL> select * from v $ pwfile_users;
USERNAME SYSDB SYSOP
----------------------------------------
SYS TRUE
If no record is selected, the password file does not have a token.
The solution here is to recreate the orapwd file.
Use the password file orapwd command orapwd-c file = "$ ORACLE_HOME/dbs/orapwd $ ORACLE_SID" entity = 5 password = changeoninstall
Check v $ pwfile_users again. At this time, there is a record.
Now let's try again. Our problem is basically solved.
There is also a situation that prompts ORA-01017: User Name Password error
This error occurs, but your password and user name are clearly correct. This is why Logging
Check the value of the system parameter remote_login_passwordfile,
If you need to start the password file, you must make sure that the value is set to NONE, EXCLUSIVE, and SHARE.
Both EXCLUSIVE and SHARE are supported. EXCLUSIVE is an EXCLUSIVE file, and SHARE is the sharing mode in the Multi-instance system.
This problem is basically caused by this value.
SQL> alter system set remote_login_passwordfile = EXCLUSIVE scope = spfile;
Restart the service now.
OK.
We have discussed these two issues before.
Let's take a look at the two discussions.
ORA-01017: User Name Password error instance
Solve the Problem of ORA-01031: insufficient privileges on 10 Gb non-local SQLPLUS conn as sysdba
