Sie sind auf Seite 1von 7
Document: Hyperion Planning Tips and Tricks Description: Author Amit Sharma We have collected some common

Document:

Hyperion Planning Tips and Tricks

Document: Hyperion Planning Tips and Tricks Description: Author Amit Sharma We have collected some common issues

Description:

Author Amit Sharma
Author
Amit Sharma

We have collected some common issues we found while working in Hyperion Planning. These common issues I want to consolidate and share with learner. Join our professional training program to learn from the experts.

Description Change Review 01
Description
Change
Review 01

History:

Publish Date

01-Feb-2011

Change Review 01 History: Publish Date 01-Feb-2011 Version 0.1 Learnhyperion.wordpress.com | Hyperion Planning

Version

0.1

Learnhyperion.wordpress.com | Hyperion Planning Tips and Tricks

1

Table of Contents

1)

2)

3)

4)

5)

Dealing with "Out Of Memory" errors in the Planning web application logs. Changing the start year of an existing Planning application.

Copy Versions in Planning.

existing Planning application . Copy Versions in Planning . Deleting a Planning user from the Define

Deleting a Planning user from the Define Users list.

Optimizing Business Rule Performance

the Define Users list. Optimizing Business Rule Performance Learnhyperion.wordpress.com | Hyperion Planning Tips and
the Define Users list. Optimizing Business Rule Performance Learnhyperion.wordpress.com | Hyperion Planning Tips and
the Define Users list. Optimizing Business Rule Performance Learnhyperion.wordpress.com | Hyperion Planning Tips and

Learnhyperion.wordpress.com | Hyperion Planning Tips and Tricks

2

Dealing with "Out Of Memory" errors in the Planning web application logs

There are three things you can do to improve the performance of the Planning application.

I. Increase the Java heap size: You can increase the heap to a maximum of 1Gb (1024Mb). If you have the available RAM to dedicate to Planning, it is recommended to increase both the minimum (Xms) and maximum (Xmx) heap size to 1024Mb. Inceasing the minimum heap size will help because it lowers the overhead needed to manage garbage collection in a dynamically expanding heap. Do not exceed 1024Mb or you may see performance actually decrease.

exceed 1024Mb or you may see performance actually decrease. The step by step procedure for modifying

The step by step procedure for modifying the Java heap size varies from one web application server to another. Contact your web application administrator for assistance.

II. Turn off process management for Version and Scenario members for which it is not needed: By default, new Scenario and Version members are enabled for process management. Each Entity-Scenario-Version combination (each Planning unit) costs resources because Planning must check who currently owns the Planning unit and check the security settings. If you have many Scenarios and Versions the number of combinations increases rapidly.

and check the security settings. If you have many Scenarios and Versions the number of combinations

Decide what Versions and Scenarios need to be available for process management, and then disable the others. If you are not using process management at all then you can disable process management support for all Version and Scenario members. To disable process management support, edit a member of the Scenario or Version dimension. In the member properties, uncheck the "Enable for process management" checkbox. Repeat for each member you want to disable process management for. When finished, do a database refresh using the Administration> Manage Database page and restart the Planning service.

Manage Database page and restart the Planning service. III. Optimize the design of web forms: Large
Manage Database page and restart the Planning service. III. Optimize the design of web forms: Large

III. Optimize the design of web forms: Large web forms impose by far the heaviest load on the Planning JVM. Optimizing the design of forms can make a big difference to how fast a form opens and how many users can open it concurrently.

Learnhyperion.wordpress.com | Hyperion Planning Tips and Tricks

3

Changing the start year of an existing Planning application.

A backup of the Planning application relational database is required prior to making any of the changes listed below.

The following steps will enable you to change the application start year:

steps will enable you to change the application start year: 1. are 3 years) adjust accordingly:

1.

are 3 years) adjust accordingly:

Update the following tables and fields (example assumes FY01 is the Start Year and that there

HSP_CALENDAR Change FIRST_YEAR to 2002

HSP_OBJECT Change OBJECT_NAME for FY03 to FY04, FY02 to FY03, and FY01 to FY02 (in that order)

FY03 to FY04, FY02 to FY03, and FY01 to FY02 (in that order) HSP_OBJECT - Update

HSP_OBJECT - Update MODIFIED and MOVED fields for the above years for the current date (or at least a date after the last refresh)

HSP_UNIQUE_NAMES - update FY01 to FY03 to values FY02 to FY04 starting with FY03

FY01 to FY03 to values FY02 to FY04 starting with FY03 2. Admin console. After making

2.

Admin console.

After making these changes, the Fiscal Start Year will be changed on the Calendar Tab in the

Refresh the database. Open Essbase Application Manager. Move FY04 underneath FY03 and save. Stop and
Refresh the database.
Open Essbase Application Manager.
Move FY04 underneath FY03 and save.
Stop and start the web application server.

4.

5.

6.

7.

8.

replaced with FY03, etc.

3.

You will need to make adjustments in the applicable Start Year and End Year in the Scenarios

dimension.

Review your web forms and any form with FY01 will be replaced with FY02, FY02 will be

9.The data for FY02 and FY03 will stay with the appropriate year, but the data for FY04 will be the FY01 data.

Learnhyperion.wordpress.com | Hyperion Planning Tips and Tricks

4

Copy Versions in Planning

You can copy versions using the Hyperion Planning Web client. You use the Copy Versions page to copy data from one bottom-up or target version of a selected scenario to another bottom- up or target version within the same scenario. You can copy between bottom-up and target versions, but keep in mind the following:

and target versions, but keep in mind the following: When you copy to a bottom-up version,

When you copy to a bottom-up version, only selected level zero entities are copied. When you copy to a target version, all selected entities are copied.

For example, you can create a Best Case version and then copy some or all of the data in that version to a Worst Case version to quickly create a starting point for the new version.

To copy a version:

a starting point for the new version. To copy a version: 1. Open an application in

1. Open an application in the Hyperion Planning Web client.

2. From the Hyperion Planning Home page, click Copy Versions.

3. In the Scenario drop-down list, select the scenario you want to copy.

drop-down list, select the scenario you want to copy. 4. In the Copy From drop-down list,

4. In the Copy From drop-down list, select the version from which you want to copy data.

5. In the Copy To drop-down list, select the version into which you want to copy data.

6. Click Go.

Note: The entities for the selected version display in the Available Entities list.

7.

selected version display in the Available Entities list. 7. 9. 10. Copy Account Annotations check box.

9.

10.

Copy Account Annotations check box.

11.

In the Available Entities list, select the entities to which you want to copy data.

Note: The Available Entities list displays only the entities to which you have write access.

8.

Click > to add the selected entity to the Selected Entities list or click >> to add all of the

entities in the Available Entities list. Click < to remove a selected entity from the list, or click << to remove all entities from the list.

Repeat steps 7 and 8 until the Selected Entities list is complete.

Optional: To copy any comments or annotations that are associated with ccounts, select the

Optional: To copy any supporting details that are associated with versions, elect the Copy

Supporting Details check box.

Note: Only annotations for selected entities are copied. If you are copying to a bottom-up version, only level zero entities and their annotations are copied.

12. Click Copy Data.

Learnhyperion.wordpress.com | Hyperion Planning Tips and Tricks

5

Deleting Hyperion planning user from the Define Users list

Follow the below steps to delete the Hyperion Planning user.

1. Go to SQL Server Enterprise Manager

2. Go to databases, then the database the Planning application is based on

then the database the Planning application is based on 3. Go to tables, then look for

3. Go to tables, then look for the HSP_USER_PREFS, Highlight this table, right click on it then select, open tables, and return all rows. Look for the user you are trying to delete in Planning highlight the whole row and hit the delete key and yes to confirm.

You will now be able to delete user in Planning.

to confirm. You will now be able to delete user in Planning. Learnhyperion.wordpress.com | Hyperion Planning
to confirm. You will now be able to delete user in Planning. Learnhyperion.wordpress.com | Hyperion Planning
to confirm. You will now be able to delete user in Planning. Learnhyperion.wordpress.com | Hyperion Planning

Learnhyperion.wordpress.com | Hyperion Planning Tips and Tricks

6

Optimizing Business Rule Performance

Check that compression settings are still present. In EAS, expand the application and database. Right-click on the database > Edit > Properties > Storage tab. Check that your "Data compression" is not set to "No compression" and that "Pending I/O access mode" is set to "Buffered I/O". Sometimes the compression setting can revert to "no compression", causing the rapid growth of the data files on disk.

On the Statistics tab, check the "Average clustering ratio". This should be close to 1. If it is

This will

not, restructure you database, by right-clicking on it and choosing "Restructure

by right-clicking on it and choosing "Restructure ". reduce any fragmentation caused by repeated data

".

reduce any fragmentation caused by repeated data import and export. Fragmentation will naturally reduce performance over time, but this can happen quite quickly when there are many data loads taking place.

Check the caches and block sizes.

data loads taking place. Check the caches and block sizes. Recommended block size: 8 to 100Kb

Recommended block size: 8 to 100Kb Recommended Index Cache:

Minimum=1 meg Default=10 meg Recommendation=Combined size of all ESS*.IND files if possible; otherwise as large as possible given the available RAM. Recommended Data File Cache:

given the available RAM. Recommended Data File Cache: Minimum=8 meg Default=32 meg Recommendation=Combined size of

Minimum=8 meg Default=32 meg Recommendation=Combined size of all ESS*.PAG files if possible; otherwise as large as

A
A

possible given the available RAM, up to a maximum of 2Gb. NOTE this cache is not used if the database is buffered rather than direct I/O (Check “Storage” tab). Since all Planning databases are buffered, and most customers use buffered for native Essbase applications too, this cache setting is usually not relevant. Recommended Data Cache:

Minimum=3 meg Default=3 meg Recommendation=0.125 * Combined size of all ESS*.PAG files, if possible, otherwise as large as possible given the available RAM.

good indication of the health of the caches can be gained by looking at the “Hit ratio” for

the cache on the Statistics tab in EAS. 1.0 is the best possible, lower means lower performance. Check system resources:

Recommended virtual memory setting (NT systems): 2 to 3 times the RAM available. 1.5 times the RAM on older systems. Recommended disk space:

A minimum of double the combined total of all .IND and .PAG files. You need double

because you have to have room for a restructure, which will require twice the usual storage space

whilst it is ongoing

Learnhyperion.wordpress.com | Hyperion Planning Tips and Tricks

7