3 Replies Latest reply on Jan 13, 2011 2:59 PM by David Debish

    FM Application restore

    AndyWhiteford
      Hi All,

      We have a test environment in which a user has trashed an FM application. As far as I am aware, all app data is stored in the database. To restore this to a previous back up, would we just need to replace the existing app tables (i.e. table names starting with the app name) in the database HFM schema with the tables from the database backup?
      Are there any other steps involved or do I have this wrong?

      Thanks in advance.
        • 1. Re: FM Application restore
          David Debish
          Hi Andy,

          It looks like you're restoring this schema from dump files? If so, I would recommend that you truncate the tables that you are going to replace and import those tables from the dump file. Individual tables can be restored from the dump file using the IMP command.

          If the backup is going to be restored using RMAN then the whole HFM schema will be replaced.

          As you might be aware, the metadata will also be restored and back to a version you may not want. So before you perform the restore, it would be advisable to take a soft extract of the metadata from HFM for purposes of reloading back.

          Let me know if you have any questions.

          Let me know how you get on.

          G'Luck
          -David
          • 2. Re: FM Application restore
            AndyWhiteford
            Thanks (yet again) for the reply David.

            A quick question. How would we go about the following - both the extract and loading it back?

            +"soft extract of the metadata from HFM for purposes of reloading back"+
            • 3. Re: FM Application restore
              David Debish
              Hi Andy,

              For the most part these steps are covered off in the HFM Admin and User Guide.

              I've distilled them down for either Extracting or Loading.

              Bear in mind that these steps should be performed in the sequence from top to bottom depending if your following the extracting steps or the loading steps.
              Any question drop me note.


              STEPS FOR SOFT BACKUPS (HFM Desktop Client):+

              Extracting Metadata_
              When you extract metadata, you save the file as an XML or APP file and specify the file name and location. You can extract metadata to view or modify it in Metadata Manager. After you modify metadata, you must load the modified file into the application for the changes to take effect.

              You cannot extract members of system-defined dimensions, such as the Value dimension. In addition, you cannot extract members of dimensions that are defined in application profiles, such as Year and Period.

              Windows Procedure
              - To extract metadata:
              1 Open the application.
              2 From the navigation frame, click Extract Metadata.
              3 In the Metadata Filename text box, enter a name for the file to extract, or click browse button (magnifying glass) to find the file.

              Note:
              Metadata files use the APP or XML file extension.
              4 In the Log Filename text box, enter a name for the log file, or click browse button (magnifying glass) to find the file.
              5 In the Delimiter Character text box, enter the character to be used to separate the metadata in the file.
              Delimiter characters are necessary only for ASCII files using the APP file extension. Delimiter characters are not necessary for XML files. The following characters are valid:
              , ~ @ # $ % ^ | : ; ? \

              Note:
              Use a character that is not used in the file name or in any other way in the file. For example, if you use the comma in an entity description, you cannot use the comma as the delimiter.
              6 Select the types of metadata to extract.

              Tip:
              Use the Select All and De-select All buttons to quickly select or clear all metadata types.

              7 Click Extract.

              Note:
              After you extract metadata, you can click the View button next to the Log Filename text box to display errors encountered during the process.

              Extracting Member Lists_
              Extracted member lists are saved to an ASCII file that supports multibyte character sets (MBCS). By default, member list files use the LST file extension. After you extract member lists, you can view and modify the member list information in a text editor.

              Windows Procedure
              - To extract member lists:
              1 Open the application.
              2 From the navigation frame, select Extract Member Lists.
              3 For Member List Filename, enter a file name to extract, or click browse button (magnifying glass) to find the file.

              Note:
              By default, member list files use the LST file extension.
              4 For Log Filename, enter the log file name, or click browse button (magnifying glass) to find the file.
              5 Click Extract.

              Note:
              After you extract member lists, you can click the View button to display errors encountered during the extract.

              Extracting Rules_
              When you extract rules, they are saved to an ASCII file that supports multibyte character sets (MBCS). Rules files use the RLE file extension. After you extract rules, you can view and modify them in a text editor.

              Windows Procedure
              - To extract rules:
              1 Open the application.
              2 From the navigation frame, select Extract Rules.
              3 For Rules Filename, enter a file name to extract, or click browse button (magnifying glass) to find the file.

              Note:
              Rules files use the RLE file extension.
              4 For Log Filename, enter a log file name, or click browse button (magnifying glass) to find the file.
              5 Click Extract.

              Note:
              After you extract rules, you can click the View button next to Log Filename to display the log file which notes errors encountered during the extract.

              Extracting Data_
              You can extract base-level input data and some calculated data from an application. When you extract data, it is saved to an ASCII file. By default, data files use the .DAT file extension. After you extract data to a data file, you can view and modify it in a text editor.

              When you extract data, you must specify a member for the Scenario and Year dimensions. You can specify one or more members for the Period, Entity, and Account dimensions.

              You can also extract these types of calculated data:
              - Consolidated data for parent entities
              - Base accounts and custom dimension members that are calculated by rules
              - Parent accounts that intersect with their respective CustomTop member and ICPTop member. If the CustomTop metadata attribute is blank or ALL, then the None member is used. Only valid data intersections are extracted.

              In Windows, specify the name of the file to extract and a log file name.

              Note:
              The log file stores information about the process, such as the start and end time of the extract and the number of extracted records.

              Windows Procedure
              - To extract data:
              1 Open the application from which to extract data.
              2 From the navigation frame, select Extract Data.
              3 For Data Filename, enter a file name, or click browse button (magnifying glass) to find the file.

              Note:
              You can click View to display the contents of the data file that you specified. By default,
              data files use the DAT file extension.

              4 For Log Filename, enter a file name, or click browse button (magnifying glass) to find the file.
              5 Select a data view to extract:
              - Year to Date
              - Periodic
              - Scenario Default
              6 For Delimiter Character, enter the character used to separate the data in the file. Valid characters are
              as follows: , ~ @ $ % & ^ | : ; ? \

              Note:
              You can use any of the valid characters as long as the character is not used in the file name or in any other way in the file. For example, if you are using the ampersand ( & ) in an entity member name, you cannot use the ampersand as the delimiter character.

              7 From Data Subset, specify the subset of dimension members or member lists as follows:
              - For Year and Scenario, highlight one year and one scenario member.
              - For Period, Entity, and Account, select the check boxes next to the dimension members to specify.

              Note:
              You can click browse button (magnifying glass) to select a member list for each dimension and select individual members from the member list.

              Tip:
              Click Select All or De-Select All to select or clear all check boxes.

              8 Optional: Select Calculated to extract calculated data.
              9 Click Extract.

              Note:
              After you click Extract, you can click browse button (magnifying glass) View next to the Log Filename text box to display any errors encountered during the extract.

              Extracting Journals_
              You can extract journals, recurring journals, and journal templates from an application. You can select the Scenario, Year, Period, Entity, and Value dimensions for which to extract journals. You can select the journal status, journal type, and journal balance type to extract.

              When you extract journals, they are saved to an ASCII file that supports multibyte character sets (MBCS). By default, journal files use the JLF file extension. After you extract journals, you can view and modify the journal information in a text editor.

              You can extract automated consolidation journals to external systems, however you cannot reimport them into Financial Management. When you extract these journals, the Balance type is blank for automated consolidation journals.

              Windows Procedure
              - To extract journals:
              1 Open the application.
              2 From the navigation frame, select Extract Journals.
              3 For Journal Filename, enter a file name to extract, or click browse button (magnifying glass) to find the file.

              Note:
              By default, journal files use the JLF file extension.
              4 For Log Filename, enter a log file name, or click browse button (magnifying glass) to find the file.
              5 Select items to extract:
              - Templates
              - Recurring Templates
              - Journals

              Loading Metadata_
              Load Options
              There are several options for how to load metadata to an application. You must select one type of load method: merge or replace. You have the option to clear all metadata before loading the new metadata and you have the option to check data integrity.

              Metadata Load Options

              Load Option 1
              Merge

              Load Description 1
              If a dimension member exists in the load file and in the application database, then the member in the database is replaced with the member from the load file. If the database has other dimension members that are not referenced in the load file, the members in the database are unchanged.

              For example, a database contains entities CT, MA, and CA. You use the merge method to load a metadata file containing new information for CA only. In the database, CA is updated with the new information and MA and CT remain in the database and remain unchanged.

              Load Option 2
              Replace

              Load Description 2
              All dimension members in the application database are deleted and the members from the load file are put into the database.

              For example, a database contains entities CT, MA, and CA. You use the replace method to load a metadata file containing new information for CA only. In the database, CT and MA are deleted and the only entity will be CA with the new info from the load file.

              Load Option 3
              Clear All Metadata Before Loading

              Load Description 3
              All dimension members and corresponding data, journals, and intercompany transactions in the application database are deleted.

              Note:
              If this option is selected it overrides the function of the merge and replace methods.

              Load Option 4
              Check Integrity

              Load Description 4
              Checks the metadata against the data to ensure integrity.

              Windows Procedure
              - To load metadata:
              1 Open the application.
              2 From the navigation frame, select Load Metadata.
              3 In the Metadata Filename text box, enter the file name to load; or click browse button (magnifying glass) to locate the file.

              Note:
              By default, metadata files use the APP or XML file extension. The load process accepts other file extensions such as TXT or CSV, however, Oracle recommends that you use the APP or XML file extension.

              You can click View (next to the Metadata Filename text box) to open the metadata file that you selected.

              4 In the Log Filename text box, enter a name for the log file; or click browse button (magnifying glass) to find the file.
              5 If you are loading an APP file, in the Delimiter Character text box, enter the character to be used to separate the metadata in the file.
              Delimiter characters are necessary only for ASCII files that use the APP file extension. Delimiters are not necessary for XML files. These characters are valid:
              , ~ @ $ % ^ } | : ; \
              Note: Use a character that is not used in the file name or in any other way in the file. For example, if you use the comma in an entity description, you cannot use the comma as the delimiter.
              6 Optional: In the Load Options section, select Clear All Metadata Before Loading.
              Note: If you select this option, you lose data or journals that are currently active in the application, and you cannot select elements in the Metadata Options section.
              7 Optional: Select Check Integrity to check the metadata file against the metadata in the current application.

              It is highly recommended that you select this option as it ensures that the application is not adversely affected by the metadata in the load file.

              Note:
              If integrity errors occur, they are written to the metadata log file, and no portion of the file is loaded into the application.

              You must fix the errors before you can continue with this procedure.

              8 In the Load Method section, select one of these options:
              - Merge
              - Replace
              9 In the Metadata Options section, select the types of metadata to load.

              Tip:
              Use the Select All and De-select All buttons to quickly select or clear all metadata types.

              10 Optional: Click Scan to verify that the file format is correct.
              11 Click Load.

              Note:
              After you load the metadata file, you can click View (next to the Log Filename text box) to display errors encountered during the load process.

              Loading Member Lists_
              When you load member list files, the system waits for other tasks such as consolidation, data entry or other load processes to finish before proceeding to load the files. Oracle recommends that you load member lists during periods of light activity across the server cluster instead of, for example, during a long-running consolidation. You can check the Running Tasks page to see which consolidations or data loads, for example, are in progress.

              After you load a member list file into an application, users using that application are notified that the system has changed and that they must log off from the application and log back on.

              Windows Procedure
              - To load member lists:
              1 Open the application.
              2 From the navigation frame, select Load Member Lists.
              3 For Member List Filename, enter the file name to load, or click browse button (magnifying glass) to find the file.

              Note:
              By default, member list files use the LST file extension. The load process accepts other file extensions such as TXT or CSV, however, Oracle recommends that you use the LST file extension.
              You can click View (next to Member List Filename) to open the file that you selected.

              4 For Log Filename, enter a log file name, or click browse button (magnifying glass) to find the file.
              5 Optional: Click Scan to verify that the file format is correct.
              6 Click Load.

              Note:
              After you load the file, you can click the View button next to Log Filename to display errors encountered during the load.

              Loading Rules_
              Rules changes can affect data and are dependent on metadata. As a result, a rules load operation has to put a global lock on the Financial Management server cluster. The rules load cannot proceed until any previously started operations of these types have finished:
              - Consolidation
              - Data entry
              - Data, Journal or Security Load
              - Extended Analytics
              - Metadata load
              - Member list load

              Rules scan follows the same restrictions as rules load to enable the system to validate dimension members and other parameters. Rules scan and load processes are queued up and started automatically after the blocking tasks are finished. Oracle recommends that you load rules during periods of light activity across the server cluster instead of, for example, during a long-running consolidation. You can check the Running Tasks page to see which consolidation or data loads, for example, are in progress.

              After you load a rules file to an application, users using that application are notified that the system has changed and that they must log off from the application and log back on.

              For intercompany transactions, there is an option to check the posted transactions in the application against new transactions in the rules file. The Sub Transactions section of the rules file defines the accounts that support intercompany transaction detail.

              Windows Procedure
              - To load rules:
              1 Open the application.
              2 From the navigation frame, select Load Rules.
              3 For Rules Filename, enter the file name to load, or click browse button (magnifying glass) to find the file.

              Note:
              By default, rules files use the RLE file extension. The load process accepts other file extensions such as TXT or CSV, however, Oracle recommends that you use the RLE file extension.

              4 For Log Filename, enter a log file name, or click browse button (magnifying glass) to find the file.
              5 Optional: Select Check Integrity for Intercompany Transactions to verify that posted transactions are valid with the statements in the Sub Transactions section of the rule file that you are loading.
              6 Optional: Click Scan to verify that the file format is correct.
              7 Click Load.

              Caution! If you make changes to existing rules, you must load the updated RLE file into the application before your changes take effect.

              Loading Data_
              You should not run reports, books, or batches while data is being loaded.

              In Windows, specify the name of the data file to load and a log file name.

              Note:
              The log file stores information about the load process; for example, syntax errors and invalid records.

              Windows Procedure
              - To load data:
              1 Open the application to which to load data.
              2 From the navigation frame, select Load Data.
              3 For Data Filename, enter the file name, or click browse button (magnifying glass) to find the file.

              Note:
              You can click View to display the contents of the data file that you specified. By default, data files use the DAT file extension. The load process accepts other file extensions such as TXT or CSV, however, Oracle recommends that you use the DAT file extension.

              4 For Log Filename, enter a file name, or click browse button (magnifying glass) to find the file.
              5 Select an option:
              - Merge to overwrite data in the application
              - Replace to replace data in the application
              - Replace by Security to replace data to which you have access, depending on your security rights
              - Accumulate to add data to data in the application
              6 Optional: Select Accumulate Within File to add up multiple values for the same cells in the load file before loading them into the application.
              7 Optional: Select File Contains Ownership Data if the load file contains ownership data, such as shares owned.

              Caution! If ownership data is included in the file, you must select this check box, or an
              error occurs when you load the file.

              8 For Delimiter Character, enter the character used to separate data in the file. Valid characters are as follows:
              , ~ @ $ % & ^ | : ; ? \

              Note:
              You can use any of the characters above as long as the character is not used in the file name or in any other way in the file. For example, if you are using the ampersand ( & ) in an entity member name, you cannot use the ampersand as the delimiter character.

              9 Optional: Click Scan to verify that the file format is correct.

              Note:
              After you scan the file, click View next to the Log Filename text box to see if there were any errors.
              10 Click Load.

              Loading Journals_
              Journals are loaded using the Replace mode, which clears all data for a particular journal label before loading the new journal data.

              You can load working, rejected, submitted, approved, and posted journals as well as standard and recurring journal templates. You must load posted journals to periods that are open. If you load a posted auto-reversing journal, an approved reversal is automatically generated in the next period. You must manually post the generated reversal.

              Note:
              You cannot load automated consolidation journals; they are created by the consolidation process.

              If you load large journal files on the Web, you should modify IIS settings to increase the AspBuffering limit to avoid errors.

              Windows Procedure
              - To load journals:
              1 Open the application.
              Note: Before you can load journals, you must first open the periods to which to load journals.
              2 From the navigation frame, select Load Journals.
              3 For Journal Filename, enter the file name to load, or click browse button (magnifying glass) to find the file.
              Note: By default, journal files use the JLF file extension. The load process accepts other file extensions such as TXT or CSV, however, Oracle recommends that you use the JLF file extension.
              4 For Log Filename, enter a log file name, or click browse button (magnifying glass) to find the file.
              5 For Delimiter Character, enter the character used to separate the journal data in the file. These characters are valid:
              , ~ @ $ % & ^ | : ; ? \

              Note:
              Use a character that is not used in the file name or in any other way in the file. For example, if you use the comma in an entity description, you cannot use the comma as the delimiter.

              6 Click Load.

              Note:
              After you load journals, you can click the View button next to Log Filename to display errors encountered during the load.




              G'Luck

              -David

              A good place to start for Hyperion documentation is:
              http://www.oracle.com/technetwork/middleware/epm/documentation/epm-096302.html

              A good place for learning about the Hyperion products and their features is:
              http://www.oracle.com/technetwork/tutorials/index.html
              Hyperion specific tutorials:
              http://apex.oracle.com/pls/apex/f?p=9830:hyperion:1797489450022582::NO:::


              A good place to read about best practices and find white papers is:
              http://www.oracle.com/technetwork/middleware/bi-foundation/resource-library-090986.html


              A great place to get an excel macro that tells you what new product features have been added since the last version is:
              https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=1092114.1

              My Oracle Support - Knowledge Base is a collection of articles, examples, illustrations, solutions, resources, and services.
              My Oracle Support is a service provided by Oracle
              My Oracle Support is available as part of your Oracle Premier Support subscription. To get started, visit oracle.com/support, click on My Oracle Support, and begin reaping the benefits of this exclusive Web support portal:
              https://support.oracle.com/