The Cluster Health Advisor (CHA) detected an unexpected increase in CPU utilization by databases or applications on this node. Identify CPU intensive processes and databases by reviewing Cluster Health Monitoring (CHM) data. Relocate databases to less busy machines, or limit the number of connections to databases on this node. Add nodes if more resources are required

A client keeps receiving the following alerts from OEM:

Host=racnode1.ractest
Target type=Cluster 
Target name=RACTEST-CLUSTER
Incident creation time=15/12/2021 2:11:20 PM AEDT 
Last updated time=15/12/2021 2:11:20 PM AEDT 
Message=Host CPU Utilization on Host racnode1 Database/Cluster RACTEST-CLUSTER Instance . The Cluster Health Advisor (CHA) detected an unexpected increase in CPU utilization by databases or applications on this node. Identify CPU intensive processes and databases by reviewing Cluster Health Monitoring (CHM) data. Relocate databases to less busy machines, or limit the number of connections to databases on this node. Add nodes if more resources are required. 
Severity=Warning 
Incident ID=501920 
Event count=1 
Incident Status=New 
Escalated=No 
Priority=High 
Incident owner=SYSMAN
Incident Acknowledged By Owner=No 
Categories= 
Rule Name=RuleSet - SYSMAN,Email SYSMAN About the Incidents 
Rule Owner=SYSMAN
...
..
.

Now let’s look into further where the alerts come from, the logs, GI processes and related metrics configurations on OEM.

Subscribe to get access

Read more of this content when you subscribe today.

CRS-2878: Failed to restart resource ‘ora.net1.network’ CRS-2769: Unable to failover resource ‘ora.net1.network’

The following messages appear in alert.log:

...
..
.
2021-10-26 6:34:11.701 [CRSD(56455)]CRS-2878: Failed to restart resource 'ora.net1.network'
2021-10-26 6:34:11.705 [CRSD(56455)]CRS-2769: Unable to failover resource 'ora.net1.network'.
2021-10-26 6:34:11.807 [CRSD(56455)]CRS-2878: Failed to restart resource 'ora.net1.network'
2021-10-26 6:34:11.880 [CRSD(56455)]CRS-2769: Unable to failover resource 'ora.net1.network'.
...
..
.

In the mean time, there are other resources failure from scan listeners, VIPs and local listeners, etc.

Subscribe to get access

Read more of this content when you subscribe today.

AFD-0654: AFD is not supported on Exadata systems

The following messages appear in CRS alert.log of ExaCC or Exadata:

2021-10-24 05:10:52.584 [CLSECHO(189590)]AFD-0654: AFD is not supported on Exadata systems
2021-10-24 11:10:53.734 [CLSECHO(288932)]AFD-0654: AFD is not supported on Exadata systems
2021-10-24 17:10:56.450 [CLSECHO(398661)]AFD-0654: AFD is not supported on Exadata systems
2021-10-24 23:10:55.077 [CLSECHO(92820)]AFD-0654: AFD is not supported on Exadata systems
2021-10-25 05:10:54.274 [CLSECHO(195018)]AFD-0654: AFD is not supported on Exadata systems
2021-10-25 11:10:53.935 [CLSECHO(268638)]AFD-0654: AFD is not supported on Exadata systems
2021-10-25 17:10:52.051 [CLSECHO(361889)]AFD-0654: AFD is not supported on Exadata systems
2021-10-25 23:10:52.858 [CLSECHO(37352)]AFD-0654: AFD is not supported on Exadata systems
2021-10-26 05:10:56.178 [CLSECHO(135982)]AFD-0654: AFD is not supported on Exadata systems

AFD protects from unauthorized processes over write to the asm claimed disks
in raw disk environment which is not applicable to exadata disks (non-oracle processes could not recognize / write to exadata disks).

so the message “FD-0654: AFD is not supported on Exadata systems” in alert.log can be ignored.

ExaCC : How to Understand OCPU and How Many Databases can be Created ?

A client created an VM Cluster with four RAC nodes and eight ( 8 ) OCPU assigned in one of VM Clusters  Compartment.

So questions are how many CPUs each RAC node has ? and How many databases can be created in this RAC environment based on current available OCPUs?

Subscribe to get access

Read more of this content when you subscribe today.

ExaCC: How to Register a Database in OCI

Registering a Replacement Database

  • Create a database by using Oracle Database ExaCC console with the same database name, software version and character set.
  • Shutdown the newly created database.
  • Remove the database files and replace them with the replacement database. The replacement database files must be moved into the same location as the database you are replaced. You can manually copy the replacement database files into place from a cold backup, or you can restore from a backup using Oracle Recovery Manager (RMAN).
  • Start the replacement database.
  • Perform the registration prerequisite check and resolve any issues from the following command:

    # dbaascli registerdb prereqs –dbname dbname [ –db_unique_name dbuniquename ]

    The following are the common issues from the above prerequisite check:
    1) Required database attributes such as the database name, software version, or character set do not match the original database.
    2) The database is not in READ WRITE mode.
    3) Flashback, archive log mode and block change tracking are not enabled.
    4) Transparent Database Encryption (TDE) is not configured, or is not properly configured. For example, the TDE keystore is not the expected location, or the TDE keystore type is not AUTOLOGIN.
  • Register the database by running the following command as the root user on one of the database servers:
# dbaascli registerdb begin --dbname dbname [ --db_unique_name dbuniquename ]

Register a Manually Created or Migrated Database

  1. Manually create or migrate the database. Ensure that the database meets the following requirements:
    • The /etc/oratab file contains an entry for the database.
    • Oracle Transparent Database Encryption (TDE) is configured on the database.
    • The database is in READ WRITE mode.
    • Archive log mode and block change tracking are enabled.
  2. Generate a cloud registration file (creg.ini) by running the following command as the root user on one of the database servers:
# dbaascli registerdb registry --action initialize --db dbname [ --udb dbuniquename ]

3. Perform the registration prerequisite check and resolve any issues.

# dbaascli registerdb prereqs --dbname dbname [ --db_unique_name dbuniquename ]

4. Register the database by running the following command as the root user on one of the database servers:

# dbaascli registerdb begin --dbname dbname [ --db_unique_name dbuniquename