For example, if you know a power shutdown is going to happen in a minute or you experience some problems when starting up a database instance.

It is recommended to use the SHUTDOWN ABORT only when you want to shut down the database instantaneously. If you try to do so, you may not be able to recover the backup. Therefore, you should never use the SHUTDOWN ABORT command before backing up the database. The database will be in an inconsistent state. The SHUTDOWN ABORT has a similar effect as you unplug the power of the server. The SHUTDOWN ABORT is not recommended and only used on some occasions. This option is useful in some cases e.g., a scheduled outage maintenance. The optional LOCAL mode waits for only local transactions to complete, not all the transactions. The SHUTDOWN TRANSACTIONAL does not require any instance recovery procedure on the next database startup. When completing all transactions, the database instance disconnects all the currently connected users from the database and shuts down. The database instance also does not accept any new transaction after a SHUTDOWN TRANSACTIONAL. This saves the work for all users without requesting them to log off.

The SHUTDOWN TRANSACTIONAL waits for all uncommitted transactions to complete before shutting down the database instance. The SHUTDOWN or SHUTDOWN NORMAL is not really practical because you practically cannot wait for all users to come back to their desks and disconnect from the database. Therefore SHUTDOWN and SHUTDOWN NORMAL commands have the same effect. The NORMAL is the default option if you donвЂ™t explicitly specify any option. The SHUTDOWN NORMAL does not require an instance recovery on the next database startup.

The database instance will not accept any further database connection. The SHUTDOWN NORMAL option waits for the current users to disconnect from the database before shutting down the database. LetвЂ™s examine each option of the SHUTDOWN command. SHUTDOWN ]Д¬ode language: SQL (Structured Query Language) ( sql )

Clockx will not shutdown