General Prerequisites

Setup

• Verify that you have a current backup of the database

• Install and register CTE agents on all RAC node Hosts

• Create a Host Group and add all RAC node hosts as members

• Create an encryption key for the Oracle RAC Database / Application

• Create an Oracle policy using the proper encryption key

Note

If the raw device mappings for the disk(s) are not identical across all nodes in the RAC, then you cannot use a Host Group for managing the GuardPoint within the CipherTrust Manager. You must apply the GuardPoint to each Host individually. This is typically not optimal, as a Host Group is the most effective and consistent way to manage GuardPoints for Oracle RAC environments.

Altering ASM_DISKSTRING on ASM

ASM uses the asm_diskstring setting to identify the path where ASM will attempt to locate available disks to use. If you are using device names when adding the disk, you must modify the string to include the path to SecVM.

1. To retrieve the ASM_DISKSTRING setting, type:

   SQL> SHOW PARAMETER ASM_DISKSTRING

   Copy

2. To modify the setting, type:

   SQL> ALTER SYSTEM SET ASM_DISKSTRING='/dev/mapper/*', '/dev/secvm/dev/mapper/*';

   Copy

   Where the path added is the path to SecVM.

ASMlib manages the binding, not ASM. ASMlib creates ASMlib devices on the SecVM devices and presents it to ASM. ASM automatically recognizes the new device. This creates the need to alter diskstrings for ASM. In addition, Oracle ASM sees a new device created using ASMlib and Raw, by default.

For example:

Using Oracle ASMlib to bind the device:

oracleasm createdisk <devicename> /dev/secvm/dev/<blockdev>

Using the raw command to bind the device:

raw /dev/raw/rawN /dev/secvm/dev/<blockdev>