My Oracle Support Banner

Grid Infrastructure Starting Message as ERR instead of INFO in SYSLOG (Doc ID 2332091.1)

Last updated on FEBRUARY 03, 2019

Applies to:

Oracle Database - Enterprise Edition - Version 12.1.0.2 to 12.2.0.1 [Release 12.1 to 12.2]
Information in this document applies to any platform.

Symptoms

Starting of Grid Infrastructure (GI) 12c with the text "Starting execution of Oracle Clusterware init.ohasd" logs to syslog as an error and not as an information

Following logs should be lowered to info instead of err priority:

[Thu Aug 31 18:12:16][13844][root@rachost1:~][0]# grep init.ohasd /var/log/messages
May 20 14:15:18 rachost1 logger: Starting execution of Oracle Clusterware init.ohasd
May 21 02:03:28 rachost1 logger: Starting execution of Oracle Clusterware init.ohasd
May 21 05:38:44 rachost1 logger: Starting execution of Oracle Clusterware init.ohasd
May 21 06:22:17 rachost1 logger: Starting execution of Oracle Clusterware init.ohasd

The impact is, monitoring tools scanning for errors in syslog, give false alerts and tickets when a normal GI startup happens.

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.