Shut down the database (below)

4. SHUTDOWNABORT: This is the last move to shut down the database. It is also the method that has to be used when there is no way to shut down the database. It is generally not recommended. If the following situations occur, you can consider using this method to shut down the database. 1. The database is in an abnormal working state and does not support shutdownnormal or shutdownimmediat.

4. shutdown abort: This is the last move to shut down the database. It is also the method that has to be used only when there is no way to shut down the database. It is generally not recommended. If the following situations occur, you can consider using this method to shut down the database. 1. The database is in an abnormal working state. shutdown normal or shutdown immediat cannot be used.

4. SHUTDOWN ABORT

This is the last way to shut down the database. It is also the method that has to be used when there is no way to shut down the database. If the following situations occur, you can consider using this method to shut down the database.

1. The database is in an abnormal working state and cannot be shut down using commands such as shutdown normal or shutdown immediate;

2. immediately shut down the database;

3. problems encountered when starting the database instance;

Any running SQL statement will be aborted immediately. No uncommitted transactions will be rolled back. Oracle does not wait for the user connected to the database to exit the system. The instance must be restored when the database is started next time. Therefore, the next start may take more time than usual.

Table 1 clearly shows the differences and connections between the above four closed databases.

Closing method A I T N

Allow new connections

Wait till the current session is terminated ××√

Wait till the current transaction is aborted ××√ √

Force CheckPoint, close any document * √

Where: A-Abort I-Immediate T-Transaction N-Normal