The Fast Recovery Area is not configured in the database" message in Foglight Oracle monitoring (4381162)

Foglight Oracle monitoring may display the message:  The Fast Recovery Area is not configured in the database.

This alert means Foglight cannot determine usage, capacity, or status for the database’s Fast Recovery Area (FRA).  

As a result, the dashboard and alerting features related to backup/recovery health are unavailable for the instance.

This message appears when Foglight’s Oracle agent is unable to confirm FRA configuration via its standard data collection.  

Common causes include:

1. Oracle FRA Parameters Not Set

• `DB_RECOVERY_FILE_DEST` and/or `DB_RECOVERY_FILE_DEST_SIZE` parameters are missing or set to null in the Oracle database.
• The FRA was never configured, was disabled, or was removed.

2. Insufficient Database Permissions

• The monitoring user lacks SELECT privileges on Oracle system views (`V$PARAMETER`, `V$RECOVERY_FILE_DEST`, `V$FLASH_RECOVERY_AREA_USAGE`, `V$ARCHIVE_DEST`).
• Restricted access can block agent collections of FRA configuration/status.

3. Agent Collection Failures

• Foglight’s internal data collection jobs (especially DBO_Startup_Flashback_Area_Summary) may fail due to network interruptions, Oracle instance downtime, or configuration issues.
• Script or collection errors often log details in the Foglight Oracle agent log file., e.g.: 
  "Skip DBO_Flashback_Area due to FRA s not enabled for db_recovery_file_dest is [/XX/XXXXXXX] and db_recovery_file_dest_size is XXXXXX.XXX and use_db_recovery_dest is false."
• Misconfigurations or mistakes in agent settings and connection profiles can also cause collection failures.

4. Oracle RAC or Instance Metadata Issues

• In Oracle Real Application Cluster (RAC) environments, metadata problems can prevent correct parameter retrieval for all sub-instances.
• The agent may only check one node or have trouble locating the active configuration.

5. FRA Not in Use ('use_db_recovery_dest' is FALSE) / Detection Logic

• Even if FRA parameters are set, Foglight requires at least one archive log destination to use the Oracle special keyword:
  LOCATION=USE_DB_RECOVERY_FILE_DEST     
• If all archive log destinations point to ASM or a diskgroup (e.g. `LOCATION=+FRA`) but not `USE_DB_RECOVERY_FILE_DEST`, the Foglight agent will not consider FRA "configured."
• This is because the internal SQL collections check:

  WHERE destination = 'USE_DB_RECOVERY_FILE_DEST'

  in Oracle system views (`GV$ARCHIVE_DEST`). If no destinations match, `use_db_recovery_dest` is reported as `NO`.

1. Verify FRA Parameter Configuration in Oracle

• Log into the Oracle database with admin rights.
• Use SQL to check parameter values:

  SHOW PARAMETER db_recovery_file_dest
  SHOW PARAMETER db_recovery_file_dest_size

• If these values are not set, configure them using official Oracle procedures.

2. Check Database User Permissions

• Ensure the Foglight monitoring user can query relevant system views. Grant SELECT privileges as needed:
  

  GRANT SELECT ON v_$parameter TO <foglight_user>;
  GRANT SELECT ON v_$recovery_file_dest TO <foglight_user>;
  GRANT SELECT ON v_$flash_recovery_area_usage TO <foglight_user>;
  GRANT SELECT ON v_$archive_dest TO <foglight_user>;

3. Inspect Agent Logs for Data Collection Errors

• On the Foglight server/agent host, review the agent log files for SQL/script errors or connection issues.
• Search for keywords like `FRA`, `collection`, or specific script names and address root causes (e.g. connectivity, privileges, or profile settings).

4. Validate Connectivity and RAC Metadata

• For Oracle RAC: confirm the agent profile targets all required nodes/sub-instances and that configuration is consistent on all.

5. Check if FRA is actually in use

• Check all archive log destinations:

  SHOW PARAMETER log_archive_dest

• Confrim that at least one archive log destination uses:

  LOCATION=USE_DB_RECOVERY_FILE_DEST

• Alternatively, verify explicitly::
  

  SELECT destination FROM v$archive_dest WHERE destination = 'USE_DB_RECOVERY_FILE_DEST';

• The value use_db_recovery_dest' must return 'YES' for Foglight to recognize FRA is in use.
• Work with your DBA to ensure archiving is set up to use FRA as a target. 

6. Test and Confirm in Foglight

• After making corrections, force a re-collection or wait for the next scheduled run.
• Verify the dashboard now displays FRA usage and alerts as expected.