My Oracle Support Banner

CRS was not coming up as node name changed to "ocid1" after reboot (Doc ID 2882831.1)

Last updated on JULY 16, 2022

Applies to:

Oracle Database Cloud Service - Version N/A to N/A [Release 1.0]
Information in this document applies to any platform.

Symptoms

CRS was not coming up after reboot as the hostname got changed.
The hostname was different at the time of install and the crs config file, /u01/app/19.0.0.0/grid/crs/install/crsconfig_params also shows different hostname than
returned by "hostname" or "uname -a". 

 

dbcli ,  CRS logs prior to reboot show different hostname:

alert.log of Grid
------
022-05-23 07:03:08.953 [CLSECHO(16355)]CLSRSC-0567: Beginning Oracle Grid Infrastructure configuration.

2022-05-23 07:04:50.985 [OHASD(22480)]CRS-8500: Oracle Clusterware OHASD process is starting with operating system process ID 22480
2022-05-23 07:04:51.089 [OHASD(22480)]CRS-0714: Oracle Clusterware Release 19.0.0.0.0.
2022-05-23 07:04:51.102 [OHASD(22480)]CRS-2112: The OLR service started on node myxxxxprod19c. <<========= node name prod19c
2022-05-23 07:04:51.327 [OHASD(22480)]CRS-1301: Oracle High Availability Service started on myxxxxprod19c.

 

2022-05-23 07:06:42.987 [OHASD(26813)]CRS-1301: Oracle High Availability Service started on myxxxxprod19c.

-------

 

OS prompt and hostname show different, "ocid1", hostname :

 

-------

[opc@ocid1 etc]$ uptime                
12:21:02 up 16 min, 1 user, load average: 1.06, 1.00, 0.70

---------

 

Changes

 Issue started after node reboot.

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
Changes
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.