Recommendations for Metadata Issues

You can view metadata validation results and recommendations on the Recommendations page while investigating application issues. Rescan runs metadata validation for all enabled cubes. You can then filter the Recommendations page by one or more cubes to view their results. The Recommendations page includes a recommendation and action to perform when application metadata needs to be synchronized. It includes metadata details about the cube name, dimension, member name, and the issue, for example, Children Count, which indicates there is a mismatch in the number of children in the database. It also includes instructions on how to implement the recommendation, such as performing a Refresh Database with the Validate Metadata option selected.

Reviewing metadata validation recommendations

Service Administrators can review dimension-level metadata validation findings together with other application recommendations. Metadata validation identifies member properties and relationships that can affect application integrity, consolidation results or performance.

To review these findings, filter Category to Metadata Validation. Use the recommendation’s cube and dimension context to identify the metadata to review.

Cube: The cube in which the validation issue occurs. A finding for a member in one cube does not, by itself, establish that the same issue occurs in another cube.
Artifact: The affected dimension, such as Account, Entity or View.
Type: The validation issue identified by the recommendation.
Recommendation Details: The affected members. Multiple members with the same validation issue can be grouped in one recommendation.
How to Resolve: The recommended corrective action or instructions for manually correcting the metadata.

Understanding grouped findings and priorities

A recommendation can represent several affected members. For example, if three members have the same validation issue, one recommendation can list all three members in its details. The number of recommendations can therefore differ from the number of messages in the separate Validate Metadata report. Review the affected members and validation issue when comparing results.

High: Corresponds to an Error in the metadata validation report. Review and correct these findings first.
Medium: Corresponds to a Warning. Review the potential impact and follow the resolution guidance.
Low: Corresponds to an Information message. Review the information and any suggested action.

Metadata properties and synchronization

Dimension-property validation findings are distinct from recommendations that report metadata synchronization problems between the application and Oracle Essbase. Synchronization recommendations can identify a cube, dimension, member and mismatch, such as an inconsistent number of children. Follow the instructions for the specific recommendation; these can include Refresh Database with Validate Metadata selected.

Reviewing and correcting metadata findings

From the Home page, click Recommendations.
From More Actions, select Rescan. The scan runs as a background job. Monitor its completion in the Jobs console, then return to Recommendations and click Refresh. Check Last Scanned On to determine the age of the results.
Filter Category to Metadata Validation. Review high-priority findings first. Inspect the cube, dimension, affected members and How to Resolve instructions.When Resolve is available, select it from the recommendation’s Actions menu and confirm the operation. After the job is completed, click Refresh to review its status. When Resolve is unavailable, use the Dimension Editor to make the changes specified in How to Resolve and save the changes.
After changing metadata, run Refresh Database to apply the changes to the Oracle Essbase application database. You can complete the required corrections before performing the database refresh.
Run Rescan again. After the job completes, click Refresh and review the remaining metadata validation findings. Verify the relevant business results and consolidation behavior.

Automatic resolution and rollback

Resolve is available only for supported recommendations for which the system can determine the appropriate correction. It is not available for every metadata validation finding. For example, when more than one data storage setting is valid, an administrator might need to choose the appropriate setting manually.

Before confirming a resolution, review the affected members and proposed action. Do not assume that individual members within a grouped finding can be selected or excluded.

For a supported resolved recommendation, Roll back restores the metadata values changed by that resolution. It is not a full application restore. After rolling back metadata changes, run Refresh Database and rescan to verify the current findings. The existing recommendation workflow changes the status back to Open after rollback.

Dismissal, feedback, and export

To dismiss a recommendation, select Dismiss, enter the required comment explaining the decision, and confirm. Dismissal changes the recommendation’s status; it does not correct the underlying metadata issue. Use Reopen to return a dismissed recommendation to Open.

You can provide feedback on resolved recommendations using the existing Feedback action. Use Export to download recommendation information as a CSV file for review, preserving the cube context and the list of affected members when investigating grouped findings.