Adding Oracle ASM Disk Groups to MIMIX Replication - assure_mimix - 6.0

Assure MIMIX for AIX Guide

Product type
Software
Portfolio
Integrate
Product family
Assure
Product
Assure MIMIX™ Software for AIX
Version
6.0
ft:locale
en-US
Product name
Assure MIMIX for AIX
ft:title
Assure MIMIX for AIX Guide
Copyright
2025
First publish date
2003
ft:lastEdition
2025-10-08
ft:lastPublication
2025-10-08T06:18:25.453000
L1_Product_Gateway
Integrate
L2_Product_Segment
IBM Infrastructure
L3_Product_Brand
Precisely Assure
L4_Investment_Segment
IBM i HA
L5_Product_Group
IBM i HA
L6_Product_Name
Assure MIMIX for AIX
Follow these steps to integrate Oracle ASM Disk Groups into MIMIX replication:
  1. Create a Volume Group on the source and on the target. Refer to Configure/Add Physical Volumes for details.

    For example: Oracle ASM Disk Group DATA is active on the source. ASM Disk Group DATA contains the following disks:

    hdisk15

    hdisk17

    hdisk19

    MIMIX Volume Group DATA containing the disks above should be created by using Create a Volume Group on the source. MIMIX Volume Group DATA containing disks matching the source disk sizes should be created by using Create a Volume Group on the target. Disk names do not have to match, for example hdisk15 can be replicated to hdisk11. In this example, hdisk11, hdisk12, hdisk13 are used on the target.

  2. Add MIMIX Volume Group DATA to a Replication Group (RG) and complete the RG configuration.
  3. Verify the disk mapping on the target system using the following command:
    # /usr/scrt/bin/rtgetlvodm MAP 1
    18 11 MIMIX:hdisk15 -> AIX:hdisk11
    18 12 MIMIX:hdisk17 -> AIX:hdisk12
    18 13 MIMIX:hdisk19 -> AIX:hdisk13
  4. Start replication.
  5. Create a snapshot on the target system once the initial synchronization is complete.

    Example, run the command # /usr/scrt/bin/scrt_ra -XC1 as the Oracle Grid user to get the following output:

    
    Jan 15 12:12:32 Making SNAP /dev/rsnhdisk15, 72.6
    Jan 15 12:12:32 Making SNAP /dev/rsnhdisk17, 72.10
    Jan 15 12:12:32 Making SNAP /dev/rsnhdisk19, 72.14
    Jan 15 12:12:32 Making SNAP /dev/rsnc151lif_bk_1, 72.18
    Jan 15 12:12:32 Making SNAP /dev/rsnc151lif_bk_2, 72.22
    Jan 15 12:12:32 Making SNAP /dev/rsnc151lif_bk_3, 72.26
    Jan 15 12:12:32 Making SNAP /dev/rsnc151dbmf_bk_1, 72.30
    Jan 15 12:12:32 Making SNAP /dev/rhdisk11, 72.4
    Jan 15 12:12:32 Making SNAP /dev/rhdisk12, 72.8
    Jan 15 12:12:32 Making SNAP /dev/rhdisk13, 72.12
    Snap Devs (read only, raw)     Minor rj wj   Snap level     Vdev level    Vdevs (read/write, block)
    ------------------------------ ----- -- -- -------------- --------------  ------------------------------
    /dev/rsnhdisk15                    4 ON ON           4110           4110  /dev/hdisk11
    /dev/rsnhdisk17                    8 ON ON           4110           4110  /dev/hdisk12
    /dev/rsnhdisk19                   12 ON ON           4110           4110  /dev/hdisk13
    /dev/rsnc151lif_bk_1              16 ON --           4110              0  N/A
    /dev/rsnc151lif_bk_2              20 ON --           4110              0  N/A
    /dev/rsnc151lif_bk_3              24 ON --           4110              0  N/A
    /dev/rsnc151dbmf_bk_1             28 ON --           4110              0  N/A
    
    # su - grid
    $ sqlplus / as sysasm
    
    Connected to:
    Oracle Database 12c Enterprise Edition Release 12.2.0.1.0 - 64bit Production
    
    SQL> select name, group_number, state from v$asm_diskgroup;
    
    DATA                                      0  DISMOUNTED
    
    SQL>
    SQL> select path,header_status,GROUP_NUMBER from v$asm_disk;
    
    /dev/rhdisk13   MEMBER                  0
    /dev/rhdisk11   MEMBER                  0
    /dev/rhdisk12   MEMBER                  0
    
    SQL> alter diskgroup DATA mount;
    
    Diskgroup altered.
    
    SQL> quit
  6. Use the Oracle ASM Disk Group DATA to test the application.

  7. After testing is complete, unmount the ASM Disk Group and remove the snapshot.