At work today, when the operation deletes all the tables under the Oracle user, a sudden error occurs, and then the problem with Plsql is not linked. Tried a variety of ways, without fruit. The final decision is to restart the Oracle service. I logged into Oracle's server through the CRT, scheduled to restart Oracle, and found that using sqlplus /As Sysdba not go in, directly let me enter the user name and password. Then try to use the DBA and any other user to link, the result will let me re-enter. Later, after restarting the server, it was determined that the Oracle service was still not started. The final steps to resolve are as follows:
1. start the Oracle listener: cmd the command-line window, enter Lsnrctl start, and enter to start monitoring.
2. Configure Sid:cmd Command window, set oracle_sid= instance name (ORCL)
3. Connect to Oracle: Input sqlplus /nolog, enter and then enter Conn/as SYSDBA; return
4. Start:startup.
This would have solved the problem, but I have a new problem on my side and I will report No space on device when I start. There is not enough disk space on the device.
So using DF has seen that Oracle's installation using the directory is nearly 100% already used.
So I deleted some useless things. Then the restart succeeds.
Then I use the previous user login, found the error ora-01012:not logged on.
Then use the following name: Sqlplus "/As SYSDBA" after landing, shutdown abort.
Then found the login ora-01017 invalid Username/password error.
Use the following actions:
Sqlplus/nolog, enter. , then enter connect old username/old password as SYSDBA; Enter
After that, all users will be able to log in.
This article is from the "Woodcutter's shoulder Pole" blog, please be sure to keep this source http://8582235.blog.51cto.com/8572235/1974354
Listener in Oracle is not valid