Handling Data Loss in an Environment

If you are faced with data loss in an environment, seek immediate help from Oracle.

Applies to

Planning, Planning Modules, FreeForm, Financial Consolidation and Close, Tax Reporting, Account Reconciliation, Profitability and Cost Management, Enterprise Profitability and Cost Management, Oracle Fusion Cloud Enterprise Data Management, Narrative Reporting, Sales Planning, and Strategic Workforce Planning.

To prevent data loss, do not combine operations to move, delete, and rename members in one transaction. Perform these operations separately.

If you are faced with data loss in an environment, attempt to find the root cause as follows:

  • Review these tables in the Activity Report to identify the Clear Data and Clear Block commands that were recently run, the affected cubes, calculation scripts, and the commands in the calculation scripts that resulted in clearing the data or blocks. Verify that these commands did not cause the data loss.
    • Last 15 Calc Script Clear Data Commands
    • Last 15 Calc Script Clear Block Commands

    See Essbase Runtime Data in Getting Started Guide for Administrators for information on these tables.

  • Check if you ran a calculation script that results in clearing of data blocks.
  • Check if you performed move, delete, and rename members operations followed by a data refresh. This may result in a data loss.
  • Review the Last 15 Data Management Clear Data Commands table in the Activity Report to identify the Clear Data commands that were recently run and the Data Management processes that triggered those commands. Verify that these commands did not cause the data loss. See Essbase Runtime Data in Getting Started Guide for Administrators for information on this tables.

  • Check if you ran a data load rule in REPLACE mode using a data load file that did not contain all members of one or more dimensions.

    In this case, if you use the default REPLACE option, the created CLEARDATA script only builds a FIX statement for members of Entity, Year, Period, Scenario, and Version dimensions. If a dimension is not included in the FIX statement, all members of that dimension are included in the CLEARDATA. If you are, for example, loading a specific account without updating the clear filter, the clear script clears all members of accounts, and other dimensions, not specifically cleared by CLEARDATA.

    To avoid this scenario, define clear regions with appropriate dimension filters. For information on defining a clear region, see Defining A Clear Region in Administering Data Integration.

  • Check the job console to find the jobs run from when the data was present to when the data was lost to determine if there were jobs that could have resulted in data loss. You may also review the audit log to identify why the data loss occurred.

If the preceding suggestions do not work, contact Oracle for help.

  • Create a Provide Feedback submission that identifies the actions, if any, that you performed in the environment. Optionally, allow Oracle to access the maintenance snapshot of the environment by consenting to application snapshot submission. See Creating a Provide Feedback Submission.
  • Create a technical service request that identifies the Provide Feedback reference number. See Submitting a Technical Service Request. The service request must contain the following:
    • Detailed steps to reproduce the issue.
    • Details of what data is missing: Examples:
      • Cube names and dimension names where data is missing

      • For the missing data points, for each dimension, identify whether the data is missing for all members, level 0 members or specific members

    • The last known date and time when the missing data was present in the environment.
    • Application changes, if any, that you made after the last time the data was present.
    • A snapshot of the environment, if available, from the last time data was present in the environment.
    • Specify whether this is a critical outage.