Unable to retrieve data due to invalid state

If this error is displayed when accessing Performance Hub reports, here's the likely cause and what you can do to resolve the issue:

Cause: The database status metric is not able to connect to the database or the database is down.

Solution: Ensure that the database user password has not expired and:

• For External Databases and Oracle Cloud Databases in ExaDB-C@C: Ensure that the Management Agent is running.
• For Oracle Cloud Databases in the Base Database Service and ExaDB-D: Ensure that the ingress and egress rules are correct.

Authorization failed or requested resource not found

If this error is displayed when accessing Performance Hub reports, here's the likely cause and what you can do to resolve the issue:

Cause: The required policy is not created.

Allow group DB-MGMT-ADMIN-GROUP to read metrics in tenancy

The specified task or object does not exist for the current user

If this error is displayed when generating an AWR report that includes the ADDM report, here's the likely cause and what you can do to resolve the issue:

Cause: PRVT_HDM.ADDM_REPORTS uses a different interface to obtain ADDM reports and if the original user is not a SYS user, an error may be displayed when generating an AWR report (with the ADDM report section) in Performance Hub.

Solution: Use the SYS user to generate a standalone ADDM report.

Error code = Bad_DB_Response_Exception

If this error is displayed when accessing Performance Hub, here are the likely causes and what you can do to resolve the issue:

• Cause: The temporary tablespace is empty.

  Solution: Verify if the temporary tablespace is empty using the following query:

  SQL> select * from dba_temp_files;

  If the temporary tablespace is empty, add a temporary tablespace and access Performance Hub.

• Cause: ASH package installation left in an incomplete state.

  Solution: Restart the package installation using the following steps:

  1. Run the following statements to drop the existing packages and restart ASH package installation:

     drop package body omc_ash_viewer;
     drop package omc_ash_viewer;
     drop package body dbaas_api_dbperf;
     drop package dbaas_api_dbperf;

     Note
     
     Some of the statements given above may fail. Ignore the status messages and run the statements.
  2. Go to Performance Hub to trigger the ASH package installation.

  Once the ASH package installation is completed, access Performance Hub.

QueryExecutionFailed: IO Error: The Network Adapter could not establish the connection

If the Generate Active Session History Report button is disabled for a PDB and on clicking Cancel this error is displayed, here's the likely cause and what you can do to resolve the issue:

Cause: The CDB associated with the PDB is reporting a warning even when the PDB is up.

Solution: Correct the network issue with the associated CDB and ensure that the connection is established.

No_Mgmt_Agent_Connection_Exception

If this error is displayed when accessing Performance Hub for an External Database, here's the likely cause and what you can do to resolve the issue:

Cause: The SocketTimeoutException and SSLPeerUnverifiedException are reported, and this could be due to proxy or network issues.

Solution: Verify the following:

• The Management Agent used to communicate with the External Database is up and running.
• The correct proxy is configured.
• The connectivity to Oracle Cloud Infrastructure is established and there are no issues.