If the database instance is installed on server A, you log on with administrator privileges, using the Sql> conn System/manage as SYSDBA login is fine. But if you set up an ETL account on Server A, make it the remote Desktop users and Users group, as follows:
When you log into the database with the SYS account, you will report ora-01031:insufficient privileges error, exit the ETL account, with the administrator login to the ETL account assigned to the rate belongs to the Oracle DBA group permissions
Then use the ETL account login, the problem solved, if you give the ETL Account Administrator group permissions, but no ORA_DBA permissions, as shown below, the results will be? The answer is to still report a lack of access to the wrong
Situation two: At this time I am on the remote machine B, I use the SYS account to log in to the Times ora-01031:insufficient privileges or ora-01017:invalid Username/password; Logon denied error.
First check to see if there are any sqlnet.authentication_services= (NTS) settings under the Sqlnet.ora file, and how this option has been configured. So let's check the password file parameters next.
It is obvious that the password file exists, if the query does not record, then the password file does not exist, need to rebuild the password file, sometimes we are indeed SYSDBA permissions, why log in but prompted your permission not le? The problem here may appear in the password file, because your password file is defective or non-existent, and Oralce instance to SYSDBA's permission is according to this password file to judge, why do this? If our database does not have open, then some of the dynamic views will not be opened, so Oracle must put the password and username of these users in a separate file, so that the database is not open state write, there is a place to judge. Use the ORAPWD command to rebuild the password file. The use of the ORAPWD command is as follows.
Next look at the system parameters Remote_login_passwordfile
If the value is not exclusive, then you need to set the value of the parameter remote_login_passwordfile is exclusive, once I checked all of the above configuration, the discovery is consistent, after remote with Sql*plus login, Actually reported the following error
Ora-01017:invalid Username/password; Logon denied error, very puzzled, after careful examination of all configuration, finally found that the Server B Guest account is disabled (see below)
Enabled the Guest account, and then in machine A with the SYS account login, and then reported ora-01031:insufficient privileges, hurriedly to the Guest account add ORA_DBA user group, the problem solved.
