Shulou(Shulou.com)06/01 Report--

The recent test data with a large amount of data have been found through experiments that under normal circumstances, as long as shutdown immediate, we can stop the database, but for the production system, the amount of data running is relatively large, and redolog has hundreds of megabytes, so we must be more careful when we use shutdown database.

Let's introduce the solution based on this situation:

Stop listener snooping

Lsnrctl stop LISTENER_NAME stop listening

Lsnrctl status LISTENER_NAME confirms whether the monitoring stops normally.

Check ps-ef after about 20 minutes | grep LOCAL=NO to see if there are any processes connected to the database that have not been released. If not, execute kill-9 `ps-ef | grep LOCAL=NO | awk'{print $2}'`

Stop instance instance, job, and aq

Alter system set job_queue_processes=0 scope=memory

Alter system set aq_tm_processes=0 scope=memory

Alter system switch logfile; has checked the information and needs to execute it three times.

Alter system checkpoint; has checked the information and needs to execute it three times.

Shutdown immediate; shuts down the database normally.

Note: if the database cannot be shut down normally within 1 hour, try to shut down the database shutdown immediate again after executing shutdown abort; and then startup; startup. If the database cannot be shut down normally within 1 hour, if the restart fails, execute shutdown abort; and then startup; to start the database without any other operations)

Finally, check whether ps-ef still exists in the database process | grep-I ora

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.