Copy Grid home from one node to another

  BUG 26126676 - CLUSTER DOWN ON DENS13ADM02 SERVER AFTER ONEOFF PATCH ROLLBACK 

 

 *** PBRYS  philippe.brys 05/23/17 02:52 am ***

 Since the software installation are identical on all nodes

 it is possible to copy over the whole software from one of the correct node

 to the bad third node

 

 a. tar as root the whole software tree on e.g. node1

 e.g. for the GRID_HOME

 cd $GRID_HOME

 cd ..

 tar cvf grid.tar ./grid

 

 b. untar it as root in the same recreated directory on the failed node

 

 cd $GRID_HOME

 cd ..

 mv grid grid.old  /* preserve the bad grid home

 tar xvf grid.tar

 

 c. set back the configuration

 

 rm -Rf grid/log/*

 rm -Rf grid/crf/*

 rm -Rf grid/cdata/*

 rm -Rf grid/gpnp/*

 rm -Rf grid/ccr/hosts/*

 rm -Rf grid/dbs/*

 rm -Rf grid/network/admin/*

 

 mv grid.old/log/* grid/log

 mv grid.old/crf/* grid/crf

 mv grid.old/cdata/* grid/cdata

 mv grid.old/gpnp/* grid/gpnp

 mv grid.old/ccr/hosts/* grid/ccr/hosts

 mv grid.old/dbs/* grid/dbs

 mv grid.old/network/admin/* grid/network/admin

 

 mv grid/auth/crs/<host1> grid/auth/crs/<host2>

 mv grid/auth/css/<host1> grid/auth/css/<host2>

 mv grid/auth/evm/<host1> grid/auth/evm/<host2>

 mv grid/auth/ohasd/<host1> grid/auth/ohasd/<host2> 


*** PBRYS  philippe.brys 05/23/17 03:35 am ***

after the above action plan, gipcd still failing due to


[root@dens13adm02 .oracle]# ls -ltr *GI*

-rw-r--r-- 1 oracle oinstall 0 Feb  8 23:57

ora_gipc_dens13adm02_DBG_GIPCD_lock

srwxrwxrwx 1 root   root     0 May 22 04:17 ora_gipc_dens13adm02_DBG_GIPCD

[root@dens13adm02 .oracle]# rm *GIPC*

rm: remove socket `ora_gipc_dens13adm02_DBG_GIPCD'? y

rm: remove regular empty file `ora_gipc_dens13adm02_DBG_GIPCD_lock'? y


afterwards, gipcd running.

*** PBRYS  philippe.brys 05/23/17 03:38 am ***

crsctl query crs activeversion -f

Oracle Clusterware active version on the cluster is [12.1.0.2.0]. The cluster

upgrade state is [ROLLING PATCH]. The cluster active patch level is

[1085656618].


so we have to end the rolling upgrade following note:1968727.1, i.e.


[root@dens13adm02 .oracle]# clscfg -patch

clscfg: -patch mode specified

clscfg: EXISTING configuration version 5 detected.

clscfg: version 5 is 12c Release 1.

Successfully accumulated necessary OCR keys.

Creating OCR keys for user 'root', privgrp 'root'..

Operation successful.

crsctl stop rollingpatch

CRS-1161: The cluster was successfully patched to patch level [0].

[root@dens13adm02 .oracle]# crsctl query crs activeversion -f

Oracle Clusterware active version on the cluster is [12.1.0.2.0]. The cluster

upgrade state is [NORMAL]. The cluster active patch level is [0].

Comments

Post a Comment

Popular posts from this blog

Oracle Materialized View In-Depth and Materialized View refresh issues in 19c

   We    had  situation demanding  tuning of  MV  refresh and  options  like  TUNE_MVIEW  and Atomic_Refresh was explored . Hence  Documenting materialized view sample commands  and views in this  blog .     After migration if we are  facing slowness  in  Materialized View refresh , we can explore to re-create  Materialized View   Since  main topic for this blog   was MV issues  in 19c ,  posting that topic   first in line below  We also   have Real-Time Materialized Views  to explore .  To Note :  1) We can  create Mv  on ON PREBUILT TABLE  2) We can create Index on Mv  3) We can  gather stats on mv  just like other table .  4) Mv can be REFRESH_MODE ON COMMIT / REFRESH ON DEMAND. 5) Mv  REFRESH_METHOD can be  Complete / FAST or FORCE . A FORCE attempts a FAST...
Read more

Troubleshooting Oracle Rac Crs/Cluster Startup Issues

  We need to check what  component  are started and what are pending based on that we need to  take approach .  Known Issues  / Issues faced :  1)  ora.crsd remains in INTERMEDIATE and commands like crsctl hang and Logical corruption check failed (Doc ID 2075966.1) 2) CRSD Failing to Start or in INTERMEDIATE State Due to OLR corruption. (Doc ID 2809968.1)  3) CRS is not starting up on the cluster node (Doc ID 2445492.1)  --  Missing execute permission  on <GRID_HOME>/srvm/mesg directory 4)  Crs activeversion is different on both nodes after patching/upgrade  5)  Permission of Voting/Ocr disk was changed  6)  ohasd process was no started due to missing /etc/systemd/system/ohasd.service  7)  Asm startup issues faced  due to  below  -->  asm disk were not shared between nodes  --> asm_diskstring parameters were somehow removed  7) asm not s...
Read more

How To Purge Optimizer Statistics Advisor Old Records From 12.2 Onwards (Doc ID 2660128.1)

  In this Document Goal Solution References APPLIES TO: Oracle Database - Enterprise Edition - Version 12.2.0.1 and later Oracle Cloud Infrastructure - Database Service - Version N/A and later Information in this document applies to any platform. GOAL Goal of this document is to provide the method to purge the old records of Optimizer Statistics Advisor Task namely AUTO_STATS_ADVISOR_TASK that consumes huge SYSAUX space. Huge no.of old records retained in WRI$_ADV_OBJECTS for AUTO_STATS_ADVISOR_TASK or INDIVIDUAL_STATS_ADVISOR_TASK incurs heavy SYSAUX space. AUTO_STATS_ADVISOR_TASK is meant for Automatic Statistics Advisor task while INDIVIDUAL_STATS_ADVISOR_TASK is for Manual Statistics Advisor task.  DBA_ADVISOR_PARAMETERS displays all advisor task parameters and their current values in the database. There is a parameter name called EXECUTION_DAYS_TO_EXPIRE. This parameter is set in no.of days. Executions older than the value(no.of days) set would be purged automaticall...
Read more