Solving RAC, ASM, and DataGuard configuration failure

If a Oracle Real Application Clusters (RAC), Automatic Storage Management Instance (ASM), or Dataguard instance fails during configuration, refer to the following solutions.

RAC instance configuration failure

A RAC instance configuration can fail due to one of the following reasons.

• The same TNS service strings cannot be used for multiple RAC instances. The Oracle KM does not support common TNS service strings.
• The service entries must be specified in the tnsnames.ora file for all of the member nodes on the Patrol Agent Host.

ASM instance configuration failure

An ASM instance configuration can fail due to one of the following reasons.

• The ASM instance configuration must be completed with one of the following SYS account types:
  • sysdba
  • SYSASM
  • Any other user account that has SYSASM privileges
• The Patrol OS user must have one of the following groups as a main group:
  • dba
  • asmadmin
  • asmdba
  • asmoper
• Complete the following SQL*Plus queries to confirm that it returns a value other than 0:select count(*) from v$asm_disk_stat;
  select count(*) from v$asm_diskgroup_stat;
  

DataGuard instance configuration failure

An DataGuard instance configuration can fail due to one of the following reasons.

• The primary instance is not running and not enabled for for monitoring.
• The standby database is not functioning correctly and no archive transfer is occuring.
• There is a problem with the SQL*PLUS connection. To check the connectivity from the Primary instance to the Standby instnce, enter the following spring:
  sys/<standby sys password>@<standby-tns-entry> as sysdba
• Confirm that you have read access to the tnsnames.ora file, and the service entries are present.