Solution to ORA-01031 error caused by SYS local or remote login

This article analyzes the ORA-01031 error caused by SYS Local login or remote login, but also provides a ORA-01031 error solution, have encountered the same problem of friends can refer to the solution. if the database instance is installed on server A, you can log on as Administrator and use SQL> conn system/manage as sysdba to log on. But if you create an etl account on server A to make it belong to the Remote Desktop Users and Users groups, as shown below: When you log on to the database with the sys account, A ORA-01031 will be reported: insufficient privileges error: exit the etl account, log on to the etl account as an administrator, grant the etl account the permission to belong to the Oracle DBA Group, and then log on to the etl account. The problem is solved, if you grant the etl account Administrator Group permission but do not have the ora_dba permission, as shown in the following figure, what will happen? The answer is still an error with insufficient permissions 2: At this time I am on remote machine B, I use sys account remote login times ORA-01031: insufficient privileges or ORA-01017: invalid username/password; logon denied error. First, check whether sqlnet. AUTHENTICATION_SERVICES = (ETS) settings exist in the SQLNET. ora file. How can I configure this option. Next, let's check the password file parameters. The password file exists obviously. If no record is found, it indicates that the password file does not exist and the password file needs to be rebuilt. Sometimes we do have sysdba permissions, why does the logon prompt that your permissions are insufficient? The problem may occur in the password file. Because your password file is missing or does not exist, the ORALCE instance's permissions to sysdba are determined based on the password file. Why? If our database is not OPEN, some dynamic views cannot be opened. Therefore, ORACLE must put the passwords and usernames of these users in an independent file, in this way, the database is not yet OPEN, and there is a place to judge. Use the orapwd command to recreate the password file. The orapwd command is used as follows. Next, check the system parameter remote_login_passwordfile. If the VALUE is not EXCLUSIVE, you need to set the VALUE of the remote_login_passwordfile parameter to EXCLUSIVE. Once I checked and configured all the above configurations, it was found that they all met, after remotely logging on with SQL * PLUS, the following error ORA-01017 is reported: invalid username/password; logon denied error, it is very puzzled, after carefully checking all the configurations, finally, we found that the Guest account of server B was disabled (as shown below)
Enable the Guest account, and then log on to machine A with sys account, and then reported ORA-01031: insufficient privileges, hurry to the Guest account to add ora_dba user group, the problem solved.