Sunday, 22 December 2013

Creating and Refreshing Application Databases

Creating and Refreshing Application Databases

How to Navigate?
Hyperion Workspace --> Navigate --> Administer --> Planning --> Select Application --> Administration --> Manage Document --> Create and Refresh Application Databases.

When I need to do?
Refresh the application database whenever we change the application structure.

What is the purpose of doing it?
Changes made to applications (modify properties of an Entity member or change access permissions) are not reflected to users, these changes are stored in the Planning relational database. Once refreshed it will move to Essbase (Essbase.SEC) file.

What are the Actions perform while during Refresh?   
  • Essbase security filters are updated
  • Currency conversion calc scripts are updated
  • Accounts or associated properties are propagated from the relational database to the Essbase database
  • Custom attributes are added, modified, or deleted in the Essbase database
  • Exchange rate values are repopulated in the Essbase outline
  • Member formulas for certain accounts are generated or updated
  • Additions or changes to alias tables and their association to dimensions or members are updated
  • The Essbase database is restructured
  • UDAs are added to the Essbase database
What happens to Planning Users while Refreshing?
When an administrator uses Manage Database, all other tasks are unavailable to other users, including the application owner. All users must be logged off from the Planning application before Essbase databases can be refreshed. Oracle recommends that administrators send a broadcast message to all users, asking them to save their work and close the application before the Essbase application is refreshed.

How long the Refresh process will be run?
Application refresh time depends on factors such as the number of entities and users in the application. A larger number of users and security filters increase the refresh time.

Steps to be followed to Create or Refresh the application database
  • Back up the application.
  • Select Administration --> Manage Database.
  • Select options:
  • Database: Creates or refreshes an Essbase database for the application.
  • Security Filters: Generates security filters in Essbase for use by third-party applications. Stores access permissions in an encrypted data file (Essbase.sec). select Security Filters but do not select Validate Limit.
  • Shared Members: Applies access permissions based on access to shared members and base members. Clear this option if you apply access permissions based only on access to base members.
  • Validate Limit: Identifies security filters that exceed the Essbase security filter limit of 64 KB per row. This validates filter size to ensure it does not exceed the size limit before building Essbase security filters.

To create or refresh data in the Essbase database, select an option:  
  • Click Create.
  • Click Refresh.
  • Review the confirmation message. To continue, click Create or Refresh. After the update completes, click Finish.

To refresh application database using a utility:
  • Back up the application.
  • Locate the CubeRefresh.cmd utility by navigating to the bin folder with the command prompt. By default, Planning utilities are installed in the EPM_ORACLE_INSTANCE/Planning/planning1 directory.
  • Launch CubeRefresh.cmd by entering the command and its parameters in the command line: CubeRefresh.cmd [-f: password File] /A: application name /U: username [/C|/R] /D [/F [S|V]][/RMIPORT:rmi_port] [/L] [/DEBUG]

Optional: If an encrypted password file is set up, you can specify [-f:passwordFile] as the first parameter in the command line, where password File is the full file path and name for the password file. See Suppressing Password Prompts in Planning Utilities.

  • Application name: The name of the Planning application on which to run the create or refresh.
  • Username: The administrative user who has rights to create or refresh the application.
  • /C or /R: The function to perform on the application:
        •  /C: Create the database outline.
        • /R: Refresh the database outline.  
  • /D: Specify the database during create or refresh.
  • /F: Use security filters for all users of the application. Optionally, use with S, V, or  SV
      • /FS: Generate shared member security filters.
      • /FV: Validate security filters, but do not save the filters.
      • /FSV: Validate the shared member security filters.  
  • /RMIPORT: Specify an RMI port number different from the preset value of 11333
  • /-L: Default option, to create or refresh by connecting to an application server on a Local or remote machine. (You can use /L to create or refresh without connecting to an application server, for example, if the application server is not running.)
  • /DEBUG: Specify detailed error messages.  
  • If prompted, enter your password.
  • View the result of the application refresh, including errors. Completion status is shown on the console.
  • This example shows a command line used to refresh a database for all users logged on to the specified application. It uses the default RMI port and includes shared member security filters:        
      • CubeRefresh.cmd /A: app1 /U: admin /R /D /FS

1 comment:

  1. Thank you for your blog... I have inherited a script which runs the under linux without specifying either /C or /R. I assume the script processes based on what it finds (create if no application and refresh if application found). Can you confirm. Thank you.