Basic Troubleshooting Techniques

The following are some of the most common configuration issues that prevent the Oracle ASM configuration from working properly.

If you encountering errors similar to:

• ORA-15075: disk(s) are not visible cluster-wide

• ORA-15032: not all alterations performed

This could be the result of improper settings for the I/O layer, meaning that your disks are not properly configured.

Perform the following tasks to verify that the settings are correct:

1. On the CipherTrust Manager, in the Host Group that was created for the RAC cluster, verify that the host group for this configuration does NOT have the Cluster Group option set ( this option is only for GPFS, which is not supported with CTE).

2. Ensure that the GuardPoints for the block devices are set at the Host Group level. This ensures that each node receives identical GuardPoints.

3. Verify that the GuardPoints are active on all nodes. When the GuardPoints are set, go to each node and verify that they are set and guarded, using the WebUI or the secfsd –status guard1 command. If they do not guard correctly:

   • Verify that the udev rules are set correctly, as described in Modify the UDEV Rules

   • Make sure the device names are the same across all nodes.

4. From ASM, make sure that the asm_diskstring parameter is modified to include the CTE devices and that the proper pathname is used, see Altering ASM_DISKSTRING on ASM.