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

Oracle shutdown immediate has been unresponsive to the solution.

There is a sudden problem with database monitoring. After reconfiguration, restart the database. It was found that whether using shutdown or keeping up with the parameter immediate, it had the same effect, and there was no reaction after waiting for more than 10 minutes.

Checked the information, looked at the usage of each parameter, found that the connection request may still be connected to the database, did not close, so can only wait. A cruel and forcible shut down SSH, the result is miserable.

When you start it, say:

The detailed shutdown and startup parameters are explained as follows:

Shutdown has four parameters: normal, transactional, immediate, and abort. It is normal when there are no parameters by default.

Shutdown normal: do not allow new connections, wait for the session to end, wait for the transaction to end, make a checkpoint, and close the data file. No instance recovery is required at startup.

Shutdown transactional: do not allow new connections, do not wait for the end of the session, wait for the end of the transaction, make a checkpoint, and close the data file. No instance recovery is required at startup.

Shutdown immediate: do not allow new connections, do not wait for the end of the session, do not wait for the end of the transaction, make a checkpoint, and close the data file. Transactions that do not end are automatically ROLLBACK. No instance recovery is required at startup.

Shutdown abort: do not allow new connections, do not wait for the end of the session, do not wait for the end of the transaction, do not checkpoint, and do not close the data file. Instance recovery occurs automatically at startup.

In addition, the contents of normal, transactional, and immediate,db bUFFER cACHE are written to the data file, the uncommitted transactions are rolled back, all resources are released, and the database is "cleanly" closed.

No data files are written to the contents of the abort,db bUFFER cACHE, and transactions that are not committed are not rolled back. The database is not DISMOUNT and closed, and the data file is not closed. When the database is started, the data needs to be recovered through REDO LOG, the transaction is rolled back through the rollback segment, and the resources are released.

Startup [force] [restrict] [pfile= FILENAME] [open [recover] [DATABASE] | mount | nomount]

The default parameter for startup open:startup is open, which opens the database and allows access to the database. All files described in the control file of the current instance are already open.

Startup mount:mount database, only for dba management operations, do not allow users of the database to access. Only the control file of the current instance is opened, and the data file is not opened.

Startup nomount: simply initialize the file, allocate the sga area, start the database background process, and do not open the control file and data file. No access to the database is allowed.

Startup pfile= FILENAME: start the database with FILENAME as the initialization file, not the default initialization file.

Startup force: aborts the current database and starts to restart the database normally.

Startup restrict: only users with restricted session privileges are allowed to access the database.

Startup recover: the database starts and media recovery begins.

When using shutdown, both normal and immediate may fail to restart the database because the connection is not released.

The following two options can be adopted:

SQL > shutdown abort;-this method shuts down the database without waiting for the end of the session and is generally not recommended. If you can't turn it off, there's usually nothing wrong with it. It is similar to the direct KILL process.

SQL > startup-- shutdown abort starts the database later.

SQL > startup force;-this method is to directly shut down the database and then restart the database, this way can also achieve the purpose of shutdown, I personally use both methods.

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.