A Brief Overview of Oracle Database Startup and Shutdown

• Kiran Dalvi
• 07 Mar, 2024
• 0 Comments
• 1 Min Read

A Brief Overview of Oracle Database Startup and Shutdown

 

Whether you’re diving into the world of Oracle Database Administration or looking to brush up on your skills, understanding the startup and shutdown procedures is fundamental. Let’s break it down in simple terms:

Startup Procedure

1. Nomount StateWhat? Control files, redo log files and database files are closed.Why? For operations like creating a database or recreating the control file.Tip: Dynamic views like v$session come alive in this state.
2. Mount StateWhat? Control file opens, verifying the existence of the database and redo log files.Why? Use cases include backup, recovery, and switching to archive log mode.Insider Info: Query v$database for open_mode, and it responds with “mounted.”
3. OpenWhat? The database is fully opened, and ready for action.Why? Check open_mode in v$database for status (read-only or read-write).Reminder: Log in as “sys as sysdba” for smooth startup or shutdown.

Shutdown Procedure

Oracle offers three shutdown modes – normal, immediate, and abort.

1. Shutdown NormalHow? Default mode; waits for users to disconnect before shutting down.
2. Shutdown TransactionalHow? Waits for ongoing transactions to complete; no new connections allowed.
3. Shutdown ImmediateHow? Swiftly disconnects all sessions, and rolls back transactions.Bonus: No instance recovery is needed during the next startup.
4. Shutdown AbortHow? Abrupt shutdown without rolling back transactions.Word of Caution: Not ideal for consistent backups; stick to the first three methods.

Misconceptions about Shutdown Abort

In large databases, the abort option can be used judiciously for a quicker shutdown:

1. Shu abort
2. Startup restrict
3. Shu immediate
4. Startup mount restrict

While quicker, experienced DBAs often prefer waiting for a cleaner shutdown with conventional methods.