Avoid Oracle "Crash Recovery" on system startup

This document (7024200) is provided subject to the disclaimer at the end of this document.

Environment

SUSE Linux Enterprise Server 12 Service Pack 4 (SLES 12 SP4)
SUSE Linux Enterprise Server 15 Service Pack 1 (SLES 15 SP1)

Situation

SQLPLUS is used to startup the Oracle Database.

When server is rebooted, the Oracle Database starts up with crash recovery notifications.

The following could be seen in Oracle log files:

Beginning crash recovery of 1 threads
.....
Completed crash recovery at
Thread 1: RBA 6797.20886.16, nab 20886, scn 0x0000000013040c18

Note: It doesn't matter if server runs single or multiple Instance.

Resolution

When restarting Oracle Database manually using "sqlplus", kindly manually stop Oracle Database service using "systemctl stop oracle.service" to avoid such error.

Once instance stopped via sqlplus, use: "systemctl restart oracle.service" which is basically stop/start of all instances registered in "/etc/oratab".

To avoid restarting a running instances,, adjust "/etc/oratab" to control specific instance. Starting up Oracle Database using systemctl will run it under system slice.

Cause

This is caused by sqlplus start/stop operations, causing systemd to switch process from system to user slice.

Additional Information

Please be aware that sqlplus is not the only Oracle tool which will switch processes to user slice.

For example other command-line Oracle DB management tools (like dbca, etc.) will do the same.

Disclaimer

This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.