It is a typical sysdba logon problem. You can try these problems for several reasons: 1. log on to the Oracle database homepage [system/self-built Password] --> Management --> User Management --> set the user to "Unlocked" --> then go to the command line --> connect --> OK! 2. First, check the sqlnet file. Sqlnet. authentication_services = (none) Start Password File verification, and then check whether there is an orapw $ oracle_sid file under $ ORACLE_HOME/dbs. Next, check the value of remote_login_passwordfile. I guess the value of remote_login_passwordfile must be none, instead of exclusive. But how can I determine this inference. Remote_login_passwordfile is the init parameter. You can view it through show parameters remote_login_passwordfile or directly view the spfile file. Although spfile is a binary file, however, the content in the content shows the more $ ORACLE_HOME/dbs/spfile $ SID of the text. ora. finally, whether it is remote_login_passwordfile = none. If it is none, the problem should be fixed, that is, the setting of remote_login_passwordfile. First shield sqlnet. sqlnet. authentication_services = (none) enables the local sqlplus "/As sysdba" to go to SQL> startup Mount SQL> show parameters remote_login_passwordfile; the value is none, change the value to exclusive SQL> alter system set remote_login_passwordfile = exclusive scope = spfile; SQL> shutdown immediate SQL> startup SQL> select * from V $ pwfile_users; check whether the result is OK.