Posts

Grid Infratstructure Upgrade to 12.2.0.1 Reports Missing Patch 21255373 , 17617807 Even Though Patch Applied in Existing Grid Home.

Cause: Failures were encountered during execution of CVU verification request "stage -pre crsinst".  Verifying Oracle patch:17617807 ...FAILED  drexdbadm02: PRVG-1260 : Command "/tmp/CVU_12.2.0.1.0_grid/cvuhelper  /u01/app/11.2.0.4/grid 11203  /tmp/CVU_12.2.0.1.0_grid/cvuhelper112.jar /u01/app/11.2.0.4/grid  -getOPatchStatus /u01/app/11.2.0.4/grid 17617807" to obtain Oracle  patch status failed  drexdbadm02: PRVG-1261 : Required Oracle patch "17617807" in home  "/u01/app/11.2.0.4/grid" is not found on node "drexdbadm02".  drexdbadm01: PRVG-1260 : Command "/tmp/CVU_12.2.0.1.0_grid/cvuhelper  /u01/app/11.2.0.4/grid 11203  /tmp/CVU_12.2.0.1.0_grid/cvuhelper112.jar /u01/app/11.2.0.4/grid  -getOPatchStatus /u01/app/11.2.0.4/grid 17617807" to obtain Oracle  patch status failed  drexdbadm01: PRVG-1261 : Required Oracle patch "17617807" in home  "/u01/app/11.2.0.4/grid" is not found on node "drexdbadm01"...

[INS-30024] Installer has detected that the location determined as Oracle Grid Infrastructure home (/u01/app/11.2.0.4/grid), is not a valid Oracle home.

Soluation: 1) Can you please unset the again the below variables and try again? unset ORACLE_HOME ORACLE_BASE ORACLE_SID or 2) check the "/etc/oraInst.loc" file have the correct inventory location or not? some times "EBUS" system using more then one inventory location, so Please correct it, then try again.

CELL-02788: The number of cell disks exceeds the maximum allowed.

Symptoms: celldisk can't be create after dropping the celldisk. Error Message : CellCLI> create celldisk CD_07_xxx_ex_mg_cel01 lun=0_7 CELL-04527: Cannot complete the creation of cell disk CD_07_xxx_ex_adm_cel01. Received error: CELL-02788: The number of cell disks exceeds the maximum allowed. Cell disks are not created: CD_07_xxx_ex_mg_cel01 CellCLI> Cause: Please check the Exadata Rack Configuration Type ( Full / Quarter / Half ) : # grep -i MACHINETYPES /opt/oracle.SupportTools/onecommand/databasemachine.xml If out looks below you have limitation to create the celldisk on the eight rack machine. <MACHINETYPES>X3-2 Eighth Rack HP</MACHINETYPES> Solution: 1) Please open a case with oracle support. because you need to enable the Quarter Rack attribute, this is depending with license. How to enable the attribute: From one of the Exadata Compute nodes use the dcli utility to set the EightRack attribute to False: dcli -g cell_group -l celladmin cellcli -e "alte...

Downgrade Grid Infrastructure from 12.2.0.1 to 11.2.0.4.

Take the output of below commands before starting downgrade. [root@lab-tst-rac1 ~]# /u01/app/12.2.0.1/grid/bin/ocrcheck Status of Oracle Cluster Registry is as follows :          Version                  :          4          Total space (kbytes)     :     409568          Used space (kbytes)      :      11472          Available space (kbytes) :     398096          ID                       :  598504973       ...

Supercluster App Domain RAC setup not able to start after ZFS storage rebooted.

11gR2 Grid Infrastructure on Solaris local containers, cssd process fails to start with following symptoms: ** root.sh output CRS-2674: Start of 'ora.cssd' on 'racnode1' failed .. CRS-5804: Communication error with agent process CRS-4000: Command Start failed, or completed with errors. The exlusive mode cluster start failed, see Clusterware alert log for more information Initial cluster configuration failed.  See /oracle_crs/app/11.2.0/grid/cfgtoollogs/crsconfig/rootcrs_racnode1.log for details ** $GRID_HOME/cfgtoollogs/crsconfig/rootcrs_<nodename>.log 2017-03-09 22:33:38: CRS-2674: Start of 'ora.cssd' on 'racnode1' failed .. 2017-03-09 22:33:38: CRS-5804: Communication error with agent process 2017-03-09 22:33:38: CRS-4000: Command Start failed, or completed with errors. 2017-03-09 22:33:38: CSS startup failed with return code 1 .. 2017-03-09 22:33:51: The exlusive mode cluster start failed, see Grid Infrastructure alert log for more ** $GRID_HOM...

[INS-40718] Single Client Access Name (SCAN): could not be resolved. ( LDOMS & Zones)

Cause The name you provided as the SCAN could not be resolved using TCP/IP host name lookup. Action-Provide name to use for the SCAN for which the domain can be resolved Global Zone : ============= # svccfg svc:> select name-service/switch svc:/system/name-service/switch> setprop config/host = astring: "files dns" svc:/system/name-service/switch> select system/name-service/switch:default svc:/system/name-service/switch:default> refresh svc:/system/name-service/switch:default> validate svc:/system/name-service/switch:default> exit # svcadm refresh name-service/switch # svcadm restart /system/name-service-cache; then, I can resolve host using telnet/ping.

How to find ILOM IP's from Compute Nodes

login as: root root@172.44.30.12's password: Last login: Thu Mar  2 10:51:44 2017 from 10.10.34.50 [root@LBRPRD1 ~]# ipmi ipmicmd    ipmievd    ipmiflash  ipmilan    ipmish     ipmitool   ipmi_ui [root@LBRPRD1 ~]# ipmitool sunoem cli Connected. Use ^D to exit. -> -> show /SP/network show /SP/network  /SP/network     Targets:         interconnect         ipv6         test     Properties:         commitpending = (Cannot show property)         dhcp_clientid = none         dhcp_server_ip = none         ipaddress = 192.24.10.56         ipdiscovery = static       ...