Just the day before yesterday, our system did not know why, and we could not store the database for the data. After restarting, we simply couldn't enter the database. Now it's okay, since the pages are not
It must be because of Tomcat problems or databases. This restart has helped us a lot, because in the morning we were blindly looking for the cause of system problems.
It is far better to narrow down the scope to the two. The first check is that Tomcat and tomcat processes are running normally, so it is reasonable to say that there is no problem.
Oracle, Ah ~ Now we think it is an oracle problem. Since there is a problem with Oracle, restart it and run the following command:
SQL/plus/nolog
Conn as sysdba
Shutdown immediate (or abort, which is forced to close. If it is forced to close, the file may be damaged)
The result page is stuck, so there is no way to check what kind of listening is available. It is also the simplest way to query,
PS-Ef | grep listener is used to check whether the listener exists. After the query, we want both listening processes to be there, and ignore the possibility that the listener has no response. After a while, we did not find a lot of places and finally killed the two listeners. Then we shut down the database and restarted it ~
This is just a record of myself for use in the case of database problems in the future. Otherwise, there will be no idea for a last search ~