Under rare circumstances, a failed database cannot be restarted. Database administrators need to examine the database, troubleshoot, and fix the issue, before restarting the database. Database administrators must run most diagnostic tools in single-user mode, which creates a bottleneck for disaster recovery in very large databases.

Some diagnostic utilities can run concurrently. Running utilities concurrently while the database is stopped reduces the cost of checking for database corruption in a disaster scenario.

Read-only database connections allow for any number of connections at once, limited by the maximum number of connections.