Netsoftmate

Tag: Grid Infrastructure

  • Rename Oracle ASM Disk Group On Exadata

    When Oracle ACS build Exadata Database Machine, they use the OEDA file that you sent them over for Exadata Install. The Exadata is built with default ASM Disk Group name DATAC1, RECOC1 & DBFS_DG. If you want to rename the DATAC1 and RECOC1 to something different to match your Organization standards you can do that by using the Oracle renamedg utility. The number Database version required to rename an ASM Disk Group is 11.2.


    In this article we will demonstrate how to rename ASM Disk Group on Exadata Database Machine running Oracle Database 11.2


    Here we want to change the following ASM Disk Group Names:
    DATAC1 to DATA
    RECOC1 to RECO


    Steps to rename ASM Disk Group


    • Get the Database version

    ORACLE_SID = [+ASM1] ? dbm011
    The Oracle base remains unchanged with value /u01/app/oracle


    [oracle@dm01db01 ~]$ sqlplus / as sysdba


    SQL*Plus: Release 11.2.0.4.0 Production on Thu May 24 16:36:34 2018
    Copyright (c) 1982, 2013, Oracle.  All rights reserved.


    Connected to:
    Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 – 64bit Production
    With the Partitioning, Real Application Clusters, Automatic Storage Management, OLAP,
    Data Mining and Real Application Testing options


    SQL> select * from v$version;


    BANNER
    ——————————————————————————–
    Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 – 64bit Production
    PL/SQL Release 11.2.0.4.0 – Production
    CORE    11.2.0.4.0      Production
    TNS for Linux: Version 11.2.0.4.0 – Production
    NLSRTL Version 11.2.0.4.0 – Production

    • Connect to asmcmd and make a note of the Disk Group Names

    [oracle@dm01db01 ~]$ . oraenv


    ORACLE_SID = [oracle] ? +ASM1
    The Oracle base has been set to /u01/app/oracle


    [oracle@dm01db01 ~]$ asmcmd -p


    ASMCMD [+] > lsdg
    State    Type    Rebal  Sector  Block       AU   Total_MB    Free_MB  Req_mir_free_MB  Usable_file_MB  Offline_disks  Voting_files  Name
    MOUNTED  HIGH    N         512   4096  4194304  272154624  271558968          6479872        88359698              0             N  DATAC1/
    MOUNTED  HIGH    N         512   4096  4194304    2404640    2402468            68704          777921              0             Y  DBFS_DG/
    MOUNTED  NORMAL  N         512   4096  4194304   45389568   45386648           540352        22423148              0             N  RECOC1/

    • Check the versions

    ASMCMD [+] > lsct
    DB_Name  Status     Software_Version  Compatible_version  Instance_Name  Disk_Group
    +ASM     CONNECTED        11.2.0.4.0          11.2.0.4.0  +ASM1          DBFS_DG
    DBM01    CONNECTED        11.2.0.4.0          11.2.0.4.0  dbm011         DATAC1

    • Check the database status

    [oracle@dm01db01 ~]$ srvctl status database -d dbm01
    Instance dbm011 is running on node dm01db01
    Instance dbm012 is running on node dm01db02
    Instance dbm013 is running on node dm01db03
    Instance dbm014 is running on node dm01db04

    • Make a note of the control files, Datafiles, Redo logfiles before stopping the database.

    SQL> select name from v$controlfile;
    SQL> select name from v$datafile;
    SQL> select member from v$logfile;
    SQL> select * from v$block_change_tracking;

    • Stop database database

    [oracle@dm01db01 ~]$ srvctl stop database -d dbm01


    [oracle@dm01db01 ~]$ srvctl status database -d dbm01
    Instance dbm011 is not running on node dm01db01
    Instance dbm012 is not running on node dm01db02
    Instance dbm013 is not running on node dm01db03
    Instance dbm014 is not running on node dm01db04

    • Umount the ASM disk group(s) that you want to rename. Connect to ASM command prompt and umount the disk group. umount the disk group from all nodes.

    ASMCMD [+] > umount DATAC1


    ASMCMD [+] > umount RECOC1


    ASMCMD [+] > lsdg
    State    Type  Rebal  Sector  Block       AU  Total_MB  Free_MB  Req_mir_free_MB  Usable_file_MB  Offline_disks  Voting_files  Name
    MOUNTED  HIGH  N         512   4096  4194304   2404640  2402468            68704          777921              0             Y  DBFS_DG/


    Note: If you don’t stop the databases using ASM disk group you will get the following error message:


    ASMCMD [+] > umount DATAC1
    ORA-15032: not all alterations performed
    ORA-15027: active use of diskgroup “DATAC1” precludes its dismount (DBD ERROR: OCIStmtExecute)


    *** Repeat the above steps on all the remaining nodes in the Cluster***


    [oracle@dm01db01 ~]$ ssh dm01db02
    Last login: Thu May 17 15:23:31 2018 from dm01db01


    [oracle@dm01db02 ~]$ . oraenv
    ORACLE_SID = [oracle] ? +ASM2
    The Oracle base has been set to /u01/app/oracle


    [oracle@dm01db02 ~]$ asmcmd lsdg
    State    Type    Rebal  Sector  Block       AU   Total_MB    Free_MB  Req_mir_free_MB  Usable_file_MB  Offline_disks  Voting_files  Name
    MOUNTED  HIGH    N         512   4096  4194304  272154624  271558968          6479872        88359698              0             N  DATAC1/
    MOUNTED  HIGH    N         512   4096  4194304    2404640    2402468            68704          777921              0             Y  DBFS_DG/
    MOUNTED  NORMAL  N         512   4096  4194304   45389568   45385040           540352        22422344              0             N  RECOC1/


    [oracle@dm01db02 ~]$ asmcmd umount DATAC1


    [oracle@dm01db02 ~]$ asmcmd umount RECOC1


    [oracle@dm01db02 ~]$ asmcmd lsdg
    State    Type  Rebal  Sector  Block       AU  Total_MB  Free_MB  Req_mir_free_MB  Usable_file_MB  Offline_disks  Voting_files  Name
    MOUNTED  HIGH  N         512   4096  4194304   2404640  2402468            68704          777921              0             Y  DBFS_DG/


    [oracle@dm01db01 ~]$ ssh dm01db03
    Last login: Thu May 17 15:23:31 2018 from dm01db01


    [oracle@dm01db03 ~]$ . oraenv
    ORACLE_SID = [oracle] ? +ASM3
    The Oracle base has been set to /u01/app/oracle


    [oracle@dm01db03 ~]$ asmcmd umount DATAC1


    [oracle@dm01db03 ~]$ asmcmd umount RECOC1


    [oracle@dm01db03 ~]$ asmcmd lsdg
    State    Type  Rebal  Sector  Block       AU  Total_MB  Free_MB  Req_mir_free_MB  Usable_file_MB  Offline_disks  Voting_files  Name
    MOUNTED  HIGH  N         512   4096  4194304   2404640  2402468            68704          777921              0             Y  DBFS_DG/


    [oracle@dm01db01 ~]$ ssh dm01db04
    Last login: Thu May 17 15:23:31 2018 from dm01db01


    [oracle@dm01db04 ~]$ . oraenv
    ORACLE_SID = [oracle] ? +ASM4
    The Oracle base has been set to /u01/app/oracle


    [oracle@dm01db04 ~]$ asmcmd umount DATAC1


    [oracle@dm01db04 ~]$ asmcmd umount RECOC1


    [oracle@dm01db04 ~]$ asmcmd lsdg
    State    Type  Rebal  Sector  Block       AU  Total_MB  Free_MB  Req_mir_free_MB  Usable_file_MB  Offline_disks  Voting_files  Name
    MOUNTED  HIGH  N         512   4096  4194304   2404640  2402468            68704          777921              0             Y  DBFS_DG/

    • Verify that renamedg is in PATH

    [oracle@dm01db01 ~]$ which renamedg
    /u01/app/11.2.0.4/grid/bin/renamedg

    • As owner of the Grid Infrastruture software execute the renamdg command. Here the owner of GI home is ‘oracle’ user. First I am renaming DATAC1 disk group to DATA

    [oracle@dm01db01 ~]$ renamedg phase=both dgname=DATAC1 newdgname=DATA verbose=true


    NOTE: No asm libraries found in the system
    Parsing parameters..
    Parameters in effect:


             Old DG name       : DATAC1
             New DG name       : DATA
             Phases            :
                     Phase 1
                     Phase 2
             Discovery str      : (null)
             Clean              : TRUE
             Raw only           : TRUE
    renamedg operation: phase=both dgname=DATAC1 newdgname=DATA verbose=true
    Executing phase 1
    Discovering the group
    Performing discovery with string:
    Identified disk OSS::o/192.168.10.9;192.168.10.10/DATAC1_CD_02_dm01cel01 with disk number:74 and timestamp (33068591 612262912)
    Identified disk OSS::o/192.168.10.9;192.168.10.10/DATAC1_CD_11_dm01cel01 with disk number:83 and timestamp (33068591 612262912)
    Identified disk OSS::o/192.168.10.9;192.168.10.10/DATAC1_CD_07_dm01cel01 with disk number:79 and timestamp (33068591 612262912)
    Identified disk OSS::o/192.168.10.9;192.168.10.10/DATAC1_CD_04_dm01cel01 with disk number:76 and timestamp (33068591 612262912)
    Identified disk OSS::o/192.168.10.9;192.168.10.10/DATAC1_CD_05_dm01cel01 with disk number:77 and timestamp (33068591 612262912)
    Identified disk OSS::o/192.168.10.9;192.168.10.10/DATAC1_CD_10_dm01cel01 with disk number:82 and timestamp (33068591 612262912)
    Identified disk OSS::o/192.168.10.9;192.168.10.10/DATAC1_CD_06_dm01cel01 with disk number:78 and timestamp (33068591 612262912)
    Identified disk OSS::o/192.168.10.9;192.168.10.10/DATAC1_CD_03_dm01cel01 with disk number:75 and timestamp (33068591 612262912)
    Identified disk OSS::o/192.168.10.9;192.168.10.10/DATAC1_CD_00_dm01cel01 with disk number:72 and timestamp (33068591 612262912)
    Identified disk OSS::o/192.168.10.9;192.168.10.10/DATAC1_CD_08_dm01cel01 with disk number:80 and timestamp (33068591 612262912)
    Identified disk OSS::o/192.168.10.9;192.168.10.10/DATAC1_CD_01_dm01cel01 with disk number:73 and timestamp (33068591 612262912)
    Identified disk OSS::o/192.168.10.9;192.168.10.10/DATAC1_CD_09_dm01cel01 with disk number:81 and timestamp (33068591 612262912)
    …
    …
    …
    Identified disk OSS::o/192.168.10.21;192.168.10.22/DATAC1_CD_09_dm01cel07 with disk number:69 and timestamp (33068591 612262912)
    Identified disk OSS::o/192.168.10.21;192.168.10.22/DATAC1_CD_03_dm01cel07 with disk number:63 and timestamp (33068591 612262912)
    Identified disk OSS::o/192.168.10.21;192.168.10.22/DATAC1_CD_06_dm01cel07 with disk number:66 and timestamp (33068591 612262912)
    Identified disk OSS::o/192.168.10.21;192.168.10.22/DATAC1_CD_08_dm01cel07 with disk number:68 and timestamp (33068591 612262912)
    Identified disk OSS::o/192.168.10.21;192.168.10.22/DATAC1_CD_04_dm01cel07 with disk number:64 and timestamp (33068591 612262912)
    Identified disk OSS::o/192.168.10.21;192.168.10.22/DATAC1_CD_07_dm01cel07 with disk number:67 and timestamp (33068591 612262912)
    Identified disk OSS::o/192.168.10.21;192.168.10.22/DATAC1_CD_01_dm01cel07 with disk number:61 and timestamp (33068591 612262912)
    Identified disk OSS::o/192.168.10.21;192.168.10.22/DATAC1_CD_05_dm01cel07 with disk number:65 and timestamp (33068591 612262912)
    Identified disk OSS::o/192.168.10.21;192.168.10.22/DATAC1_CD_02_dm01cel07 with disk number:62 and timestamp (33068591 612262912)
    Identified disk OSS::o/192.168.10.21;192.168.10.22/DATAC1_CD_00_dm01cel07 with disk number:60 and timestamp (33068591 612262912)
    Identified disk OSS::o/192.168.10.21;192.168.10.22/DATAC1_CD_11_dm01cel07 with disk number:71 and timestamp (33068591 612262912)
    Identified disk OSS::o/192.168.10.21;192.168.10.22/DATAC1_CD_10_dm01cel07 with disk number:70 and timestamp (33068591 612262912)
    Checking for hearbeat…
    Re-discovering the group
    Performing discovery with string:
    Identified disk OSS::o/192.168.10.9;192.168.10.10/DATAC1_CD_02_dm01cel01 with disk number:74 and timestamp (33068591 612262912)
    Identified disk OSS::o/192.168.10.9;192.168.10.10/DATAC1_CD_11_dm01cel01 with disk number:83 and timestamp (33068591 612262912)
    Identified disk OSS::o/192.168.10.9;192.168.10.10/DATAC1_CD_07_dm01cel01 with disk number:79 and timestamp (33068591 612262912)
    Identified disk OSS::o/192.168.10.9;192.168.10.10/DATAC1_CD_04_dm01cel01 with disk number:76 and timestamp (33068591 612262912)
    Identified disk OSS::o/192.168.10.9;192.168.10.10/DATAC1_CD_05_dm01cel01 with disk number:77 and timestamp (33068591 612262912)
    Identified disk OSS::o/192.168.10.9;192.168.10.10/DATAC1_CD_10_dm01cel01 with disk number:82 and timestamp (33068591 612262912)
    Identified disk OSS::o/192.168.10.9;192.168.10.10/DATAC1_CD_06_dm01cel01 with disk number:78 and timestamp (33068591 612262912)
    Identified disk OSS::o/192.168.10.9;192.168.10.10/DATAC1_CD_03_dm01cel01 with disk number:75 and timestamp (33068591 612262912)
    Identified disk OSS::o/192.168.10.9;192.168.10.10/DATAC1_CD_00_dm01cel01 with disk number:72 and timestamp (33068591 612262912)
    Identified disk OSS::o/192.168.10.9;192.168.10.10/DATAC1_CD_08_dm01cel01 with disk number:80 and timestamp (33068591 612262912)
    Identified disk OSS::o/192.168.10.9;192.168.10.10/DATAC1_CD_01_dm01cel01 with disk number:73 and timestamp (33068591 612262912)
    Identified disk OSS::o/192.168.10.9;192.168.10.10/DATAC1_CD_09_dm01cel01 with disk number:81 and timestamp (33068591 612262912)
    …
    …
    …
    Identified disk OSS::o/192.168.10.21;192.168.10.22/DATAC1_CD_09_dm01cel07 with disk number:69 and timestamp (33068591 612262912)
    Identified disk OSS::o/192.168.10.21;192.168.10.22/DATAC1_CD_03_dm01cel07 with disk number:63 and timestamp (33068591 612262912)
    Identified disk OSS::o/192.168.10.21;192.168.10.22/DATAC1_CD_06_dm01cel07 with disk number:66 and timestamp (33068591 612262912)
    Identified disk OSS::o/192.168.10.21;192.168.10.22/DATAC1_CD_08_dm01cel07 with disk number:68 and timestamp (33068591 612262912)
    Identified disk OSS::o/192.168.10.21;192.168.10.22/DATAC1_CD_04_dm01cel07 with disk number:64 and timestamp (33068591 612262912)
    Identified disk OSS::o/192.168.10.21;192.168.10.22/DATAC1_CD_07_dm01cel07 with disk number:67 and timestamp (33068591 612262912)
    Identified disk OSS::o/192.168.10.21;192.168.10.22/DATAC1_CD_01_dm01cel07 with disk number:61 and timestamp (33068591 612262912)
    Identified disk OSS::o/192.168.10.21;192.168.10.22/DATAC1_CD_05_dm01cel07 with disk number:65 and timestamp (33068591 612262912)
    Identified disk OSS::o/192.168.10.21;192.168.10.22/DATAC1_CD_02_dm01cel07 with disk number:62 and timestamp (33068591 612262912)
    Identified disk OSS::o/192.168.10.21;192.168.10.22/DATAC1_CD_00_dm01cel07 with disk number:60 and timestamp (33068591 612262912)
    Identified disk OSS::o/192.168.10.21;192.168.10.22/DATAC1_CD_11_dm01cel07 with disk number:71 and timestamp (33068591 612262912)
    Identified disk OSS::o/192.168.10.21;192.168.10.22/DATAC1_CD_10_dm01cel07 with disk number:70 and timestamp (33068591 612262912)
    Checking if the diskgroup is mounted or used by CSS
    Checking disk number:74
    Checking disk number:83
    Checking disk number:79
    Checking disk number:76
    Checking disk number:77
    Checking disk number:82
    Checking disk number:78
    Checking disk number:75
    Checking disk number:72
    Checking disk number:80
    Checking disk number:73
    Checking disk number:81
    Checking disk number:69
    Checking disk number:63
    Checking disk number:66
    Checking disk number:68
    Checking disk number:64
    Checking disk number:67
    Checking disk number:61
    Checking disk number:65
    Checking disk number:62
    Checking disk number:60
    …
    …
    Generating configuration file..
    Completed phase 1
    Executing phase 2
    Looking for o/192.168.10.9;192.168.10.10/DATAC1_CD_02_dm01cel01
    Modifying the header
    Looking for o/192.168.10.9;192.168.10.10/DATAC1_CD_11_dm01cel01
    Modifying the header
    Looking for o/192.168.10.9;192.168.10.10/DATAC1_CD_07_dm01cel01
    Modifying the header
    Looking for o/192.168.10.9;192.168.10.10/DATAC1_CD_04_dm01cel01
    Modifying the header
    Looking for o/192.168.10.9;192.168.10.10/DATAC1_CD_05_dm01cel01
    Modifying the header
    Looking for o/192.168.10.9;192.168.10.10/DATAC1_CD_10_dm01cel01
    Modifying the header
    Looking for o/192.168.10.9;192.168.10.10/DATAC1_CD_06_dm01cel01
    Modifying the header
    Looking for o/192.168.10.9;192.168.10.10/DATAC1_CD_03_dm01cel01
    Modifying the header
    Looking for o/192.168.10.9;192.168.10.10/DATAC1_CD_00_dm01cel01
    Modifying the header
    Looking for o/192.168.10.9;192.168.10.10/DATAC1_CD_08_dm01cel01
    Modifying the header
    Looking for o/192.168.10.9;192.168.10.10/DATAC1_CD_01_dm01cel01
    Modifying the header
    …
    …
    Modifying the header
    Completed phase 2
    Terminating kgfd context 0x7f9d346240a0

    • Now rename RECOC1 ASM disk group to RECO using renamdg command

    [oracle@dm01db01 ~]$ renamedg phase=both dgname=RECOC1 newdgname=RECO verbose=true


    NOTE: No asm libraries found in the system
    Parsing parameters..
    Parameters in effect:


             Old DG name       : RECOC1
             New DG name       : RECO
             Phases            :
                     Phase 1
                     Phase 2
             Discovery str      : (null)
             Clean              : TRUE
             Raw only           : TRUE
    renamedg operation: phase=both dgname=RECOC1 newdgname=RECO verbose=true
    Executing phase 1
    Discovering the group
    Performing discovery with string:
    Identified disk OSS::o/192.168.10.9;192.168.10.10/RECOC1_CD_03_dm01cel01 with disk number:75 and timestamp (33068591 628813824)
    Identified disk OSS::o/192.168.10.9;192.168.10.10/RECOC1_CD_04_dm01cel01 with disk number:76 and timestamp (33068591 628813824)
    Identified disk OSS::o/192.168.10.9;192.168.10.10/RECOC1_CD_05_dm01cel01 with disk number:77 and timestamp (33068591 628813824)
    Identified disk OSS::o/192.168.10.9;192.168.10.10/RECOC1_CD_00_dm01cel01 with disk number:72 and timestamp (33068591 628813824)
    Identified disk OSS::o/192.168.10.9;192.168.10.10/RECOC1_CD_10_dm01cel01 with disk number:82 and timestamp (33068591 628813824)
    Identified disk OSS::o/192.168.10.9;192.168.10.10/RECOC1_CD_07_dm01cel01 with disk number:79 and timestamp (33068591 628813824)
    Identified disk OSS::o/192.168.10.9;192.168.10.10/RECOC1_CD_02_dm01cel01 with disk number:74 and timestamp (33068591 628813824)
    Identified disk OSS::o/192.168.10.9;192.168.10.10/RECOC1_CD_01_dm01cel01 with disk number:73 and timestamp (33068591 628813824)
    Identified disk OSS::o/192.168.10.9;192.168.10.10/RECOC1_CD_11_dm01cel01 with disk number:83 and timestamp (33068591 628813824)
    Identified disk OSS::o/192.168.10.9;192.168.10.10/RECOC1_CD_08_dm01cel01 with disk number:80 and timestamp (33068591 628813824)
    Identified disk OSS::o/192.168.10.9;192.168.10.10/RECOC1_CD_09_dm01cel01 with disk number:81 and timestamp (33068591 628813824)
    Identified disk OSS::o/192.168.10.9;192.168.10.10/RECOC1_CD_06_dm01cel01 with disk number:78 and timestamp (33068591 628813824)
    …
    …
    Identified disk OSS::o/192.168.10.21;192.168.10.22/RECOC1_CD_01_dm01cel07 with disk number:61 and timestamp (33068591 628813824)
    Identified disk OSS::o/192.168.10.21;192.168.10.22/RECOC1_CD_08_dm01cel07 with disk number:68 and timestamp (33068591 628813824)
    Identified disk OSS::o/192.168.10.21;192.168.10.22/RECOC1_CD_06_dm01cel07 with disk number:66 and timestamp (33068591 628813824)
    Identified disk OSS::o/192.168.10.21;192.168.10.22/RECOC1_CD_11_dm01cel07 with disk number:71 and timestamp (33068591 628813824)
    Identified disk OSS::o/192.168.10.21;192.168.10.22/RECOC1_CD_10_dm01cel07 with disk number:70 and timestamp (33068591 628813824)
    Identified disk OSS::o/192.168.10.21;192.168.10.22/RECOC1_CD_05_dm01cel07 with disk number:65 and timestamp (33068591 628813824)
    Identified disk OSS::o/192.168.10.21;192.168.10.22/RECOC1_CD_00_dm01cel07 with disk number:60 and timestamp (33068591 628813824)
    Identified disk OSS::o/192.168.10.21;192.168.10.22/RECOC1_CD_03_dm01cel07 with disk number:63 and timestamp (33068591 628813824)
    Identified disk OSS::o/192.168.10.21;192.168.10.22/RECOC1_CD_09_dm01cel07 with disk number:69 and timestamp (33068591 628813824)
    Identified disk OSS::o/192.168.10.21;192.168.10.22/RECOC1_CD_07_dm01cel07 with disk number:67 and timestamp (33068591 628813824)
    Identified disk OSS::o/192.168.10.21;192.168.10.22/RECOC1_CD_02_dm01cel07 with disk number:62 and timestamp (33068591 628813824)
    Identified disk OSS::o/192.168.10.21;192.168.10.22/RECOC1_CD_04_dm01cel07 with disk number:64 and timestamp (33068591 628813824)
    Checking for hearbeat…
    Re-discovering the group
    Performing discovery with string:
    Identified disk OSS::o/192.168.10.9;192.168.10.10/RECOC1_CD_03_dm01cel01 with disk number:75 and timestamp (33068591 628813824)
    Identified disk OSS::o/192.168.10.9;192.168.10.10/RECOC1_CD_04_dm01cel01 with disk number:76 and timestamp (33068591 628813824)
    Identified disk OSS::o/192.168.10.9;192.168.10.10/RECOC1_CD_05_dm01cel01 with disk number:77 and timestamp (33068591 628813824)
    Identified disk OSS::o/192.168.10.9;192.168.10.10/RECOC1_CD_00_dm01cel01 with disk number:72 and timestamp (33068591 628813824)
    Identified disk OSS::o/192.168.10.9;192.168.10.10/RECOC1_CD_10_dm01cel01 with disk number:82 and timestamp (33068591 628813824)
    Identified disk OSS::o/192.168.10.9;192.168.10.10/RECOC1_CD_07_dm01cel01 with disk number:79 and timestamp (33068591 628813824)
    Identified disk OSS::o/192.168.10.9;192.168.10.10/RECOC1_CD_02_dm01cel01 with disk number:74 and timestamp (33068591 628813824)
    Identified disk OSS::o/192.168.10.9;192.168.10.10/RECOC1_CD_01_dm01cel01 with disk number:73 and timestamp (33068591 628813824)
    Identified disk OSS::o/192.168.10.9;192.168.10.10/RECOC1_CD_11_dm01cel01 with disk number:83 and timestamp (33068591 628813824)
    Identified disk OSS::o/192.168.10.9;192.168.10.10/RECOC1_CD_08_dm01cel01 with disk number:80 and timestamp (33068591 628813824)
    Identified disk OSS::o/192.168.10.9;192.168.10.10/RECOC1_CD_09_dm01cel01 with disk number:81 and timestamp (33068591 628813824)
    Identified disk OSS::o/192.168.10.9;192.168.10.10/RECOC1_CD_06_dm01cel01 with disk number:78 and timestamp (33068591 628813824)
    …
    …
    Identified disk OSS::o/192.168.10.21;192.168.10.22/RECOC1_CD_01_dm01cel07 with disk number:61 and timestamp (33068591 628813824)
    Identified disk OSS::o/192.168.10.21;192.168.10.22/RECOC1_CD_08_dm01cel07 with disk number:68 and timestamp (33068591 628813824)
    Identified disk OSS::o/192.168.10.21;192.168.10.22/RECOC1_CD_06_dm01cel07 with disk number:66 and timestamp (33068591 628813824)
    Identified disk OSS::o/192.168.10.21;192.168.10.22/RECOC1_CD_11_dm01cel07 with disk number:71 and timestamp (33068591 628813824)
    Identified disk OSS::o/192.168.10.21;192.168.10.22/RECOC1_CD_10_dm01cel07 with disk number:70 and timestamp (33068591 628813824)
    Identified disk OSS::o/192.168.10.21;192.168.10.22/RECOC1_CD_05_dm01cel07 with disk number:65 and timestamp (33068591 628813824)
    Identified disk OSS::o/192.168.10.21;192.168.10.22/RECOC1_CD_00_dm01cel07 with disk number:60 and timestamp (33068591 628813824)
    Identified disk OSS::o/192.168.10.21;192.168.10.22/RECOC1_CD_03_dm01cel07 with disk number:63 and timestamp (33068591 628813824)
    Identified disk OSS::o/192.168.10.21;192.168.10.22/RECOC1_CD_09_dm01cel07 with disk number:69 and timestamp (33068591 628813824)
    Identified disk OSS::o/192.168.10.21;192.168.10.22/RECOC1_CD_07_dm01cel07 with disk number:67 and timestamp (33068591 628813824)
    Identified disk OSS::o/192.168.10.21;192.168.10.22/RECOC1_CD_02_dm01cel07 with disk number:62 and timestamp (33068591 628813824)
    Identified disk OSS::o/192.168.10.21;192.168.10.22/RECOC1_CD_04_dm01cel07 with disk number:64 and timestamp (33068591 628813824)
    …
    …
    Checking if the diskgroup is mounted or used by CSS
    Checking disk number:75
    Checking disk number:76
    Checking disk number:77
    Checking disk number:72
    Checking disk number:82
    Checking disk number:79
    Checking disk number:74
    Checking disk number:73
    Checking disk number:83
    Checking disk number:80
    Checking disk number:81
    Checking disk number:78
    Checking disk number:61
    Checking disk number:68
    Checking disk number:66
    Checking disk number:71
    Checking disk number:70
    Checking disk number:65
    Checking disk number:60
    Checking disk number:63
    Checking disk number:69
    Checking disk number:67
    Checking disk number:62
    Checking disk number:64
    Checking disk number:49
    …
    …
    Generating configuration file..
    Completed phase 1
    Executing phase 2
    Looking for o/192.168.10.9;192.168.10.10/RECOC1_CD_03_dm01cel01
    Modifying the header
    Looking for o/192.168.10.9;192.168.10.10/RECOC1_CD_04_dm01cel01
    Modifying the header
    Looking for o/192.168.10.9;192.168.10.10/RECOC1_CD_05_dm01cel01
    Modifying the header
    Looking for o/192.168.10.9;192.168.10.10/RECOC1_CD_00_dm01cel01
    Modifying the header
    Looking for o/192.168.10.9;192.168.10.10/RECOC1_CD_10_dm01cel01
    Modifying the header
    Looking for o/192.168.10.9;192.168.10.10/RECOC1_CD_07_dm01cel01
    Modifying the header
    Looking for o/192.168.10.9;192.168.10.10/RECOC1_CD_02_dm01cel01
    Modifying the header
    Looking for o/192.168.10.9;192.168.10.10/RECOC1_CD_01_dm01cel01
    Modifying the header
    Looking for o/192.168.10.9;192.168.10.10/RECOC1_CD_11_dm01cel01
    Modifying the header
    Looking for o/192.168.10.9;192.168.10.10/RECOC1_CD_08_dm01cel01
    Modifying the header
    Looking for o/192.168.10.9;192.168.10.10/RECOC1_CD_09_dm01cel01
    Modifying the header
    Looking for o/192.168.10.9;192.168.10.10/RECOC1_CD_06_dm01cel01
    Modifying the header
    …
    …
    Modifying the header
    Completed phase 2
    Terminating kgfd context 0x7f8d42f6c0a0

    • Mount the DATA and RECO ASM disk groups on all the nodes.

    [oracle@dm01db01 ~]$ asmcmd -p


    ASMCMD [+] > lsdg
    State    Type  Rebal  Sector  Block       AU  Total_MB  Free_MB  Req_mir_free_MB  Usable_file_MB  Offline_disks  Voting_files  Name
    MOUNTED  HIGH  N         512   4096  4194304   2404640  2402468            68704          777921              0             Y  DBFS_DG/


    ASMCMD [+] > mount DATA


    ASMCMD [+] > mount RECO


    ASMCMD [+] > lsdg
    State    Type    Rebal  Sector  Block       AU   Total_MB    Free_MB  Req_mir_free_MB  Usable_file_MB  Offline_disks  Voting_files  Name
    MOUNTED  HIGH    N         512   4096  4194304  272154624  271558968          6479872        88359698              0             N  DATA/
    MOUNTED  HIGH    N         512   4096  4194304    2404640    2402468            68704          777921              0             Y  DBFS_DG/
    MOUNTED  NORMAL  N         512   4096  4194304   45389568   45385040           540352        22422344              0             N  RECO/


    *** Repeat the above steps on all the remaning compute nodes in the Cluster***


    Note: 

    • renamedg utility cannot rename the associated ASM/Grid disk disk name
    • renamedg utility cannot rename/update the control files, datafiles, redo log files and any other files that reference ASM DG for all databases



    Steps to rename control files, datafiles, redo log files and other database files


    • Update SPFILE location

    [oracle@dm01db01 ~]$ cd $ORACLE_HOME/dbs


    [oracle@dm01db01 dbs]$ cat initdbm011.ora
    SPFILE=’+DATAC1/dbm01/spfiledbm01.ora’


    [oracle@dm01db01 dbs]$ vi initdbm011.ora


    [oracle@dm01db01 dbs]$ cat initdbm011.ora
    SPFILE=’+DATA/dbm01/spfiledbm01.ora’


    [oracle@dm01db01 dbs]$ scp initdbm011.ora dm01db02:/u01/app/oracle/product/11.2.0.4/dbhome/dbs/initdbm012.ora
    initdbm011.ora                                                                                                                                             100%   42     0.0KB/s   00:00


    [oracle@dm01db01 dbs]$ scp initdbm011.ora dm01db03:/u01/app/oracle/product/11.2.0.4/dbhome/dbs/initdbm013.ora
    initdbm011.ora                                                                                                                                             100%   42     0.0KB/s   00:00


    [oracle@dm01db01 dbs]$ scp initdbm011.ora dm01db04:/u01/app/oracle/product/11.2.0.4/dbhome/dbs/initdbm014.ora
    initdbm011.ora                                                                                                                                             100%   42     0.0KB/s   00:00

    • Update control file location

    [oracle@dm01db01 dbs]$ . oraenv
    ORACLE_SID = [dbm011] ?
    The Oracle base remains unchanged with value /u01/app/oracle


    [oracle@dm01db01 dbs]$ sqlplus / as sysdba


    SQL*Plus: Release 11.2.0.4.0 Production on Fri May 25 10:17:49 2018
    Copyright (c) 1982, 2013, Oracle.  All rights reserved.
    Connected to an idle instance.


    SQL> startup nomount;
    ORACLE instance started.


    Total System Global Area 2.5655E+10 bytes
    Fixed Size                  2265224 bytes
    Variable Size            4160753528 bytes
    Database Buffers         2.1341E+10 bytes
    Redo Buffers              151113728 bytes


    SQL> show parameter control_files


    NAME                                 TYPE        VALUE
    ———————————— ———– ——————————
    control_files                        string      +DATAC1/dbm01/controlfile/current.256.976374731


    SQL> alter system set control_files=’+DATA/dbm01/controlfile/current.256.976374731′ scope=spfile;


    System altered.


    SQL> shutdown immediate;
    ORA-01507: database not mounted




    ORACLE instance shut down.
    SQL> startup mount
    ORACLE instance started.


    Total System Global Area 2.5655E+10 bytes
    Fixed Size                  2265224 bytes
    Variable Size            4160753528 bytes
    Database Buffers         2.1341E+10 bytes
    Redo Buffers              151113728 bytes
    Database mounted.


    SQL> select name from v$controlfile;


    NAME
    ——————————————————————————–
    +DATA/dbm01/controlfile/current.256.976374731

    • Update datafile and redo log file locations

    SQL> select name from v$datafile;


    NAME
    ——————————————————————————–
    +DATAC1/dbm01/datafile/system.259.976374739
    +DATAC1/dbm01/datafile/sysaux.260.976374743
    +DATAC1/dbm01/datafile/undotbs1.261.976374745
    +DATAC1/dbm01/datafile/undotbs2.263.976374753
    +DATAC1/dbm01/datafile/undotbs3.264.976374755
    +DATAC1/dbm01/datafile/undotbs4.265.976374757
    +DATAC1/dbm01/datafile/users.266.976374757


    7 rows selected.


    SQL> select member from v$logfile;


    MEMBER
    ——————————————————————————–
    +DATAC1/dbm01/onlinelog/group_1.257.976374733
    +DATAC1/dbm01/onlinelog/group_2.258.976374735
    +DATAC1/dbm01/onlinelog/group_7.267.976375073
    +DATAC1/dbm01/onlinelog/group_8.268.976375075
    +DATAC1/dbm01/onlinelog/group_5.269.976375079
    +DATAC1/dbm01/onlinelog/group_6.270.976375083
    +DATAC1/dbm01/onlinelog/group_3.271.976375085
    +DATAC1/dbm01/onlinelog/group_4.272.976375087
    +DATAC1/dbm01/onlinelog/group_9.274.976375205
    +DATAC1/dbm01/onlinelog/group_10.275.976375209
    +DATAC1/dbm01/onlinelog/group_11.276.976375211
    +DATAC1/dbm01/onlinelog/group_12.277.976375215
    +DATAC1/dbm01/onlinelog/group_13.278.976375217
    +DATAC1/dbm01/onlinelog/group_14.279.976375219
    +DATAC1/dbm01/onlinelog/group_15.280.976375223
    +DATAC1/dbm01/onlinelog/group_16.281.976375225


    16 rows selected.


    SQL> alter database rename file ‘+DATAC1/dbm01/datafile/system.259.976374739’ to ‘+DATA/dbm01/datafile/system.259.976374739’;


    Database altered.


    SQL> alter database rename file ‘+DATAC1/dbm01/datafile/sysaux.260.976374743’ to ‘+DATA/dbm01/datafile/sysaux.260.976374743’;


    Database altered.


    SQL> alter database rename file ‘+DATAC1/dbm01/datafile/undotbs1.261.976374745’ to ‘+DATA/dbm01/datafile/undotbs1.261.976374745’;


    Database altered.


    SQL> alter database rename file ‘+DATAC1/dbm01/datafile/undotbs2.263.976374753’ to ‘+DATA/dbm01/datafile/undotbs2.263.976374753’;


    Database altered.


    SQL> alter database rename file ‘+DATAC1/dbm01/datafile/undotbs3.264.976374755’ to ‘+DATA/dbm01/datafile/undotbs3.264.976374755’;


    Database altered.


    SQL> alter database rename file ‘+DATAC1/dbm01/datafile/undotbs4.265.976374757’ to ‘+DATA/dbm01/datafile/undotbs4.265.976374757’;


    Database altered.


    SQL> alter database rename file ‘+DATAC1/dbm01/datafile/users.266.976374757’ to ‘+DATA/dbm01/datafile/users.266.976374757’;


    Database altered.


    SQL> alter database rename file ‘+DATAC1/dbm01/onlinelog/group_1.257.976374733’  to ‘+DATA/dbm01/onlinelog/group_1.257.976374733’;


    Database altered.


    SQL> alter database rename file ‘+DATAC1/dbm01/onlinelog/group_2.258.976374735’  to ‘+DATA/dbm01/onlinelog/group_2.258.976374735’;


    Database altered.


    SQL> alter database rename file ‘+DATAC1/dbm01/onlinelog/group_7.267.976375073’  to ‘+DATA/dbm01/onlinelog/group_7.267.976375073’;


    Database altered.


    SQL> alter database rename file ‘+DATAC1/dbm01/onlinelog/group_8.268.976375075’  to ‘+DATA/dbm01/onlinelog/group_8.268.976375075’;


    Database altered.


    SQL> alter database rename file ‘+DATAC1/dbm01/onlinelog/group_5.269.976375079’  to ‘+DATA/dbm01/onlinelog/group_5.269.976375079’;


    Database altered.


    SQL> alter database rename file ‘+DATAC1/dbm01/onlinelog/group_6.270.976375083’  to ‘+DATA/dbm01/onlinelog/group_6.270.976375083’;


    Database altered.


    SQL> alter database rename file ‘+DATAC1/dbm01/onlinelog/group_3.271.976375085’  to ‘+DATA/dbm01/onlinelog/group_3.271.976375085’;


    Database altered.


    SQL> alter database rename file ‘+DATAC1/dbm01/onlinelog/group_4.272.976375087’  to ‘+DATA/dbm01/onlinelog/group_4.272.976375087’;


    Database altered.


    SQL> alter database rename file ‘+DATAC1/dbm01/onlinelog/group_9.274.976375205’  to ‘+DATA/dbm01/onlinelog/group_9.274.976375205’;


    Database altered.


    SQL> alter database rename file ‘+DATAC1/dbm01/onlinelog/group_10.275.976375209’ to ‘+DATA/dbm01/onlinelog/group_10.275.976375209’;


    Database altered.


    SQL> alter database rename file ‘+DATAC1/dbm01/onlinelog/group_11.276.976375211’ to ‘+DATA/dbm01/onlinelog/group_11.276.976375211’;


    Database altered.


    SQL> alter database rename file ‘+DATAC1/dbm01/onlinelog/group_12.277.976375215’ to ‘+DATA/dbm01/onlinelog/group_12.277.976375215’;


    Database altered.


    SQL> alter database rename file ‘+DATAC1/dbm01/onlinelog/group_13.278.976375217’ to ‘+DATA/dbm01/onlinelog/group_13.278.976375217’;


    Database altered.


    SQL> alter database rename file ‘+DATAC1/dbm01/onlinelog/group_14.279.976375219’ to ‘+DATA/dbm01/onlinelog/group_14.279.976375219’;


    Database altered.


    SQL> alter database rename file ‘+DATAC1/dbm01/onlinelog/group_15.280.976375223’ to ‘+DATA/dbm01/onlinelog/group_15.280.976375223’;


    Database altered.


    SQL> alter database rename file ‘+DATAC1/dbm01/onlinelog/group_16.281.976375225’ to ‘+DATA/dbm01/onlinelog/group_16.281.976375225’;


    Database altered.

    • Verify the datafiles and redo log files names

    SQL> select name from v$datafile;


    NAME
    ——————————————————————————–
    +DATA/dbm01/datafile/system.259.976374739
    +DATA/dbm01/datafile/sysaux.260.976374743
    +DATA/dbm01/datafile/undotbs1.261.976374745
    +DATA/dbm01/datafile/undotbs2.263.976374753
    +DATA/dbm01/datafile/undotbs3.264.976374755
    +DATA/dbm01/datafile/undotbs4.265.976374757
    +DATA/dbm01/datafile/users.266.976374757


    7 rows selected.


    SQL> select member from v$logfile;


    MEMBER
    ——————————————————————————–
    +DATA/dbm01/onlinelog/group_1.257.976374733
    +DATA/dbm01/onlinelog/group_2.258.976374735
    +DATA/dbm01/onlinelog/group_7.267.976375073
    +DATA/dbm01/onlinelog/group_8.268.976375075
    +DATA/dbm01/onlinelog/group_5.269.976375079
    +DATA/dbm01/onlinelog/group_6.270.976375083
    +DATA/dbm01/onlinelog/group_3.271.976375085
    +DATA/dbm01/onlinelog/group_4.272.976375087
    +DATA/dbm01/onlinelog/group_9.274.976375205
    +DATA/dbm01/onlinelog/group_10.275.976375209
    +DATA/dbm01/onlinelog/group_11.276.976375211
    +DATA/dbm01/onlinelog/group_12.277.976375215
    +DATA/dbm01/onlinelog/group_13.278.976375217
    +DATA/dbm01/onlinelog/group_14.279.976375219
    +DATA/dbm01/onlinelog/group_15.280.976375223
    +DATA/dbm01/onlinelog/group_16.281.976375225


    16 rows selected.

    • Update block change tracking file location

    SQL> alter database rename file ‘+DATAC1/dbm01/changetracking/ctf.282.976375227’ to ‘+DATA/dbm01/changetracking/ctf.282.976375227’;


    Database altered.


    SQL> select * from v$block_change_tracking;


    STATUS
    ———-
    FILENAME
    ——————————————————————————–
         BYTES
    ———-
    ENABLED
    +DATA/dbm01/changetracking/ctf.282.976375227
      11599872

    • Update OMF related parameters

    SQL> show parameter db_create_online_log_dest_1


    NAME                                 TYPE        VALUE
    ———————————— ———– ——————————
    db_create_online_log_dest_1          string      +DATAC1


    SQL> alter system set db_create_online_log_dest_1=’+DATA’;


    System altered.


    SQL> show parameter db_create_online_log_dest_1


    NAME                                 TYPE        VALUE
    ———————————— ———– ——————————
    db_create_online_log_dest_1          string      +DATA

    • Update Fast Recovery Area location

    SQL> show parameter db_recovery_file_dest


    NAME                                 TYPE        VALUE
    ———————————— ———– ——————————
    db_recovery_file_dest                string      +RECOC1
    db_recovery_file_dest_size           big integer 20425000M


    SQL> alter system set db_recovery_file_dest=’+RECO’;


    System altered.


    SQL> show parameter db_recovery_file_dest


    NAME                                 TYPE        VALUE
    ———————————— ———– ——————————
    db_recovery_file_dest                string      +RECO
    db_recovery_file_dest_size           big integer 20425000M

    • Shutdown the database

    SQL> shutdown immediate;
    Database closed.
    Database dismounted.
    ORACLE instance shut down.
    SQL> exit

    • Update the database configuration

    [oracle@dm01db01 dbs]$ srvctl config database -d dbm01
    Database unique name: dbm01
    Database name: dbm01
    Oracle home: /u01/app/oracle/product/11.2.0.4/dbhome
    Oracle user: oracle
    Spfile: +DATAC1/dbm01/spfiledbm01.ora
    Domain:
    Start options: open
    Stop options: immediate
    Database role: PRIMARY
    Management policy: AUTOMATIC
    Server pools: dbm01
    Database instances: dbm011,dbm012,dbm013,dbm014
    Disk Groups: DATAC1,RECOC1,DATA
    Mount point paths:
    Services:
    Type: RAC
    Database is administrator managed


    [oracle@dm01db01 dbs]$ srvctl modify database -p +DATA/dbm01/spfiledbm01.ora -a DATA,RECO -d dbm01


    [oracle@dm01db01 dbs]$ srvctl config database -d dbm01
    Database unique name: dbm01
    Database name: dbm01
    Oracle home: /u01/app/oracle/product/11.2.0.4/dbhome
    Oracle user: oracle
    Spfile: +DATA/dbm01/spfiledbm01.ora
    Domain:
    Start options: open
    Stop options: immediate
    Database role: PRIMARY
    Management policy: AUTOMATIC
    Server pools: dbm01
    Database instances: dbm011,dbm012,dbm013,dbm014
    Disk Groups: DATA,RECO
    Mount point paths:
    Services:
    Type: RAC
    Database is administrator managed

    • Start the database and verify

    [oracle@dm01db01 dbs]$ srvctl start database -d dbm01


    [oracle@dm01db01 dbs]$ srvctl status database -d dbm01
    Instance dbm011 is running on node dm01db01
    Instance dbm012 is running on node dm01db02
    Instance dbm013 is running on node dm01db03
    Instance dbm014 is running on node dm01db04


    [oracle@dm01db01 dbs]$ sqlplus / as sysdba


    SQL*Plus: Release 11.2.0.4.0 Production on Fri May 25 10:40:34 2018
    Copyright (c) 1982, 2013, Oracle.  All rights reserved.


    Connected to:
    Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 – 64bit Production
    With the Partitioning, Real Application Clusters, Automatic Storage Management, OLAP,
    Data Mining and Real Application Testing options


    SQL> select name, open_mode,database_role from gv$database;


    NAME      OPEN_MODE            DATABASE_ROLE
    ——— ——————– —————-
    DBM01     READ WRITE           PRIMARY
    DBM01     READ WRITE           PRIMARY
    DBM01     READ WRITE           PRIMARY
    DBM01     READ WRITE           PRIMARY


    ORACLE_SID = [+ASM1] ? dbm011
    The Oracle base remains unchanged with value /u01/app/oracle


    [oracle@dm01db01 ~]$ sqlplus / as sysdba


    SQL*Plus: Release 11.2.0.4.0 Production on Thu May 24 16:36:34 2018
    Copyright (c) 1982, 2013, Oracle.  All rights reserved.


    Connected to:
    Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 – 64bit Production
    With the Partitioning, Real Application Clusters, Automatic Storage Management, OLAP,
    Data Mining and Real Application Testing options


    SQL> select * from v$version;


    BANNER
    ——————————————————————————–
    Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 – 64bit Production
    PL/SQL Release 11.2.0.4.0 – Production
    CORE    11.2.0.4.0      Production
    TNS for Linux: Version 11.2.0.4.0 – Production
    NLSRTL Version 11.2.0.4.0 – Production




    [oracle@dm01db01 ~]$ . oraenv


    ORACLE_SID = [oracle] ? +ASM1
    The Oracle base has been set to /u01/app/oracle


    [oracle@dm01db01 ~]$ asmcmd -p


    ASMCMD [+] > lsdg
    State    Type    Rebal  Sector  Block       AU   Total_MB    Free_MB  Req_mir_free_MB  Usable_file_MB  Offline_disks  Voting_files  Name
    MOUNTED  HIGH    N         512   4096  4194304  272154624  271558968          6479872        88359698              0             N  DATAC1/
    MOUNTED  HIGH    N         512   4096  4194304    2404640    2402468            68704          777921              0             Y  DBFS_DG/
    MOUNTED  NORMAL  N         512   4096  4194304   45389568   45386648           540352        22423148              0             N  RECOC1/


    ASMCMD [+] > lsct
    DB_Name  Status     Software_Version  Compatible_version  Instance_Name  Disk_Group
    +ASM     CONNECTED        11.2.0.4.0          11.2.0.4.0  +ASM1          DBFS_DG
    DBM01    CONNECTED        11.2.0.4.0          11.2.0.4.0  dbm011         DATAC1


    [oracle@dm01db01 ~]$ srvctl status database -d dbm01
    Instance dbm011 is running on node dm01db01
    Instance dbm012 is running on node dm01db02
    Instance dbm013 is running on node dm01db03
    Instance dbm014 is running on node dm01db04




    Conclusion


    In this article we have learned how to rename an ASM Disk group on Exadata running Oracle Database 11.2. Starting with Oracle Database 11.2 you can use the renamedg command to rename an ASM Disk Group. renamedg utility cannot rename the associated ASM/Grid disk disk name. Also renamedg cannot rename/update the control files, datafiles, redo log files and any other files that reference ASM DG for all databases. You must update database files manually after renaming ASM disk groups.

  • Exadata Grid Infrastructure One-off Patch Application

    There are times when you encounter issues related to Database/ASM/Clusterware and Oracle recommends you to apply one-patches to fix the issue. These one-off patches can be applicable to Grid and Oracle Home or in some cases just specific to a particular home. In my cases we were adding Exadata X7-2 Compute nodes and Storage Cells to an Existing Exadata X6-2 Rack, and the prerequisite to do that was to apply the one-off (27965497) to GI home before upgrading the Exadata Cluster.


    In this article we will demonstrate how to apply a one-off patch to Grid Infrastructure home on Exadata Database Machine. Here my GI version is 11.2.0.4.180116


    Steps to apply the one-off patch to GI home


    Note: Read the readme.txt or readme.html file carefully as the steps may change for your environment.


    • Get the Database Status and role

    dm01db01-orcldb1 {/home/oracle}: sqlplus / as sysdba


    SQL> select name, open_mode,database_role from gv$database;


    NAME      OPEN_MODE            DATABASE_ROLE
    ——— ——————– —————-
    ORCLDB   MOUNTED              PHYSICAL STANDBY
    ORCLDB   MOUNTED              PHYSICAL STANDBY
    ORCLDB   MOUNTED              PHYSICAL STANDBY


    • Set Grid Infrastructure environmental variable

    dm01db01-orcldb1 {/home/oracle}: export ORACLE_SID=+ASM1


    dm01db01-orcldb1 {/home/oracle}: export ORACLE_HOME=/u01/app/11.2.0.4/grid


    dm01db01-+ASM1 {/home/oracle}:echo $ORACLE_HOME
    /u01/app/11.2.0.4/grid


    dm01db01-+ASM1 {/home/oracle}: export PATH=$PATH:/u01/app/11.2.0.4/grid/OPatch


    • List the current GI patches

    dm01db01-+ASM1 {/home/oracle}:opatch lspatches
    26925255;DATABASE PATCH FOR EXADATA (Jan 2018 – 11.2.0.4.180116) : (26925255)
    26609929;OCW Patch Set Update : 11.2.0.4.170814 (26609929)
    23727132;
    22502505;ACFS Patch Set Update : 11.2.0.4.160419 (22502505)


    OPatch succeeded.


    • Download, copy and unzip the one-off patch to a staging directory on Exadata Compute node 1.

    [root@dm01db01 GI]# ls -ltr
    total 442668
    -rw-rw-r– 1 oracle oinstall       267 May  8 02:21 bundle.xml
    -rw-rw-r– 1 oracle oinstall     91939 May 14 15:15 README.html
    -rw-rw-r– 1 oracle oinstall     50971 May 14 15:15 README.txt
    -rw-r–r– 1 oracle oinstall 453130872 May 15 12:02 p27965497_11204160419forACFS_Linux-x86-64.zip
    drwxr-xr-x 5 oracle oinstall      4096 May 17 09:40 27965497


    • Login as root user and Navigate to one-off patch directory

    [root@dm01db01 ~]# cd /u01/GI/27965497


    • Set the PATH to include opatch utility from GI home

     [root@dm01db01 27965497]# export PATH=$PATH:/u01/app/11.2.0.4/grid/OPatch


    • Verify opatch utility location

    [root@dm01db01 27965497]# which opatch
    /u01/app/11.2.0.4/grid/OPatch/opatch


    • Verify opatch version. Here the minimum verion required is 11.2.0.3.6

    [root@dm01db01 27965497]# opatch version
    OPatch Version: 11.2.0.3.18


    OPatch succeeded.


    • Make sure that the ASM and Database is up and running

    [root@dm01db01 27965497]# ps -ef|grep smon
    root     277568 254212  0 09:39 pts/1    00:00:00 grep smon
    root     322798      1  3 May02 ?        13:08:10 /u01/app/11.2.0.4/grid/bin/osysmond.bin
    oracle   326697      1  0 May02 ?        00:00:23 asm_smon_+ASM1
    oracle   328622      1  0 May02 ?        00:00:15 ora_smon_orcldb1


    • Create the OCM file as shown below

    [root@dm01db01 27965497]# /u01/app/11.2.0.4/grid/OPatch/ocm/bin/emocmrsp
    OCM Installation Response Generator 10.3.7.0.0 – Production
    Copyright (c) 2005, 2012, Oracle and/or its affiliates.  All rights reserved.


    Provide your email address to be informed of security issues, install and
    initiate Oracle Configuration Manager. Easier for you if you use your My
    Oracle Support Email address/User Name.
    Visit http://www.oracle.com/support/policies.html for details.
    Email address/User Name:


    You have not provided an email address for notification of security issues.
    Do you wish to remain uninformed of security issues ([Y]es, [N]o) [N]:  Y
    The OCM configuration response file (ocm.rsp) was successfully created.
    [root@dm01db01 27965497]#


    [root@dm01db01 27965497]# ls -ltr
    total 16
    drwxr-xr-x 4 oracle oinstall 4096 May  8 02:18 etc
    drwxr-xr-x 3 oracle oinstall 4096 May  8 02:18 custom
    drwxr-xr-x 6 oracle oinstall 4096 May  8 02:18 files
    -rw-r–r– 1 root   root      621 May 17 09:40 ocm.rsp


    • Apply the one-off patch to GI home as show below

    [root@dm01db01 cfgtoollogs]# /u01/app/11.2.0.4/grid/OPatch/opatch auto /u01/patches/GI -oh /u01/app/11.2.0.4/grid -ocmrf /u01/patches/GI/27965497/ocm.rsp
    Executing /u01/app/11.2.0.4/grid/perl/bin/perl /u01/app/11.2.0.4/grid/OPatch/crs/patch11203.pl -patchdir /u01/patches -patchn GI -oh /u01/app/11.2.0.4/grid -ocmrf /u01/patches/GI/27965497/ocm.rsp -paramfile /u01/app/11.2.0.4/grid/crs/install/crsconfig_params


    This is the main log file: /u01/app/11.2.0.4/grid/cfgtoollogs/opatchauto2018-05-17_10-28-13.log


    This file will show your detected configuration and all the steps that opatchauto attempted to do on your system:
    /u01/app/11.2.0.4/grid/cfgtoollogs/opatchauto2018-05-17_10-28-13.report.log


    2018-05-17 10:28:13: Starting Clusterware Patch Setup
    Using configuration parameter file: /u01/app/11.2.0.4/grid/crs/install/crsconfig_params


    Stopping CRS…
    Stopped CRS successfully


    patch /u01/patches/GI/27965497  apply successful for home  /u01/app/11.2.0.4/grid


    Starting CRS…
    Installing Trace File Analyzer
    CRS-4123: Oracle High Availability Services has been started.


    opatch auto succeeded.


    • Login as GI software owner and verify that the one-off patch is applied successfully

    [root@dm01db01 cfgtoollogs]# su – oracle


    dm01db01-+ASM1 {/home/oracle}:export PATH=$PATH:/u01/app/11.2.0.4/grid/OPatch


    dm01db01-+ASM1 {/home/oracle}:opatch lspatches
    27965497;ACFS Interim patch for 27965497
    26925255;DATABASE PATCH FOR EXADATA (Jan 2018 – 11.2.0.4.180116) : (26925255)
    26609929;OCW Patch Set Update : 11.2.0.4.170814 (26609929)
    23727132;


    OPatch succeeded.


    • Verify GI and Database status

    dm01db01-+ASM1 {/home/oracle}:ps -ef|grep pmon
    oracle   171755      1  0 10:40 ?        00:00:00 asm_pmon_+ASM1
    oracle   173484      1  0 10:41 ?        00:00:00 ora_pmon_orcldb1
    oracle   178926 176700  0 10:43 pts/0    00:00:00 grep pmon


    dm01db01-orcldb1 {/home/oracle}:/u01/app/11.2.0.4/grid/bin/crsctl check crs
    CRS-4638: Oracle High Availability Services is online
    CRS-4537: Cluster Ready Services is online
    CRS-4529: Cluster Synchronization Services is online
    CRS-4533: Event Manager is online
    dm01db01-orcldb1 {/home/oracle}:


    SQL> select name, open_mode,database_role from gv$database;


    NAME      OPEN_MODE            DATABASE_ROLE
    ——— ——————– —————-
    ORCLDB   MOUNTED              PHYSICAL STANDBY
    ORCLDB   MOUNTED              PHYSICAL STANDBY
    ORCLDB   MOUNTED              PHYSICAL STANDBY


    ***Repeat the above steps on all other Compute nodes in the Cluster***


    Start the Media Recovery process if it is not started automatically.


    SQL> alter database recover managed standby database using currently logfile disconnect;



    Conclusion


    In this article we have learned how to apply a one-off patch to Grid Infrastructure home on Exadata Database Machine.