Remember Oracle CRS cannot restart an incident

Today after modifying the database parameters, shut down the database and CRS, and then restart the server, after the server started, the discovery database can not start, the process is as follows:

Step1: Restarting the database

   Su--su-/grid/11.2. 0/grid/bin#. /crsctl Stop CRS  #所有节点执行

step2: Restart the server:

Xxxdb1#[/root]reboot

When the server restarts, we find that CRS does not come up:

Xxxdb1$[/home/grid]crs_stat-TCRs-0184: Cannot communicate with the CRS daemon.

Based on previous experience, the CRS can be started after the server has been up for about 5 minutes. However, the wait for 15 minutes, still unable to start.

step3: So request assistance, by manually starting the CRS, found that the CRS started.

su - root# CD $ORACLE _home/bin#. /crsctl start CRS      CRS-4123: Oracle High Availability Services have been started.

After about 4 minutes of waiting, the database resources up, the process is longer, need to wait patiently

Xxxdb1$[/home/grid]crsctl Status Res-T--------------------------------------------------------------------------------NAME TARGET State SERVER state_details--------------------------------------------------------------------------------Local Resources--------------------------------------------------------------------------------Ora.       ARC.DG Online online xxxdb1 online online Xxxdb2 Ora.       DAT.DG Online online xxxdb1 online online Xxxdb2 Ora.       INX.DG Online online xxxdb1 online online Xxxdb2 Ora. Listener.lsnr Online online xxxdb1 online onlin E xxxdb2 Ora.       OCRVOTE.DG Online online xxxdb1 online online XXXDB2 ora.asm Online Online xxxdb1 Star Ted Online Online Xxxdb2 Started ora.gsd OFFLINE OFFLINE xxxdb1 OFFLINE OFFLINE xxxdb2 ora.net1.network Onli                                       NE online xxxdb1 Online online xxxdb2                                                      Ora.ons Online Online xxxdb1                                        Online online XXXDB2--------------------------------------------------------------------------------Cluster Resources--------------------------------------------------------------------------------Ora. Listener_scan1.lsnr1Online online xxxdb1 ora.cvu1ONLINE OFFLINE ora.xxxdb.db1Online Online xxxdb1 shutdown immediate2Online Online xxxdb2 shutdown immediate ORA.XXXDB1.VIP1Online online xxxdb1 ora.xxxdb2.vip

1         online  online       xxxdb2                                       ora.oc4j      1        OFFLINE OFFLINE                                                   ORA.SCAN1.VIP      1        online  online       xxxdb1                              

step4: Starting a DB instance

Srvctl start instance-d {oracle_name}-i {instance_name}

Here, the database is up, why the CRS did not start the reason has not been found, after viewing the CRS self-starting parameters, found that since the boot is not available (disable) status

Xxxdb1#[/grid/11.2.  0/grid/bin]./crsctl config Hascrs-4622: Oracle High Availability Services autostart is disabled.

Change it to enable:

Xxxdb1#[/grid/11.2.  0/grid/bin]./crsctl Enable CRS

Check again:

Xxxdb1#[/grid/11.2.  0/grid/bin]./crsctl config Crscrs-4622: Oracle High Availability Services autostart is enabled.

Ok,crs Unable to self-start problem resolution completed.

Remember Oracle CRS cannot restart an incident