Business rules showing in Planning Job Console as running though Completed in Essbase

Applies to:

Hyperion Planning – Version: 11.1 and later Information in this document applies to any platform.

Goal

When running business rules through planning or workspace if the user switches to the job console to track the progress of the business rule, it never completes and always shows as ‘processing’. Some other rules however do complete.

Solution#1:

§         This is a known issue in 11.x but has been resolved in 11.x

§         An alternative that could work would be to do the following:

§         Stop the planning service.

§         Take a relational database repository backup of the planning application.

§         Go the Hyperion Planning Application repository database and clear the HSP_JOB_STATUS table.

§         Start the planning service.

§         Login to the planning application to make sure that the job status are cleared.

§         Go to administration -> Application -> Properties
Add the following parameters in the application properties section:
Enter HBR_MAX_WAIT_FOR_RULE and the interval in milliseconds to wait before running (ie. 290000))business rules in the background. If this property is not set, the feature does not work, and business rules do not run in the background.Enter HBR_MONITOR_DELAY and the interval in milliseconds for checking business rule status (ie. 180000))

§         Save and log off

§         Restart Hyperion Planning service.

Solution#2:

Possible causes are:

§          Business Rules embedded timeout parameter needs to be increased.

§          HTTP server timeout needs to be increased (specific to HTTP server).

§          HTTP server Plug-in timeout settings (specific to HTTP server and web application server).

Changing job status to "Completed”:

1. Access the Planning repository
2. Open the HSP_JOB_STATUS table and locate the job console records which are required to be changed to "Completed"
3. Change the "RUN_STATUS" value of the appropriate records to 2

4. Restart Planning service
5. Restart Apache HTTP server

6. Navigate to the Planning Job Console and verify that Job Console records became available for deletion
7. Delete the required Job Console records by using Planning's Job Console delete functionality

To Check the no of records with status msg "Processing"

select * from HSP_JOB_STATUS where END_TIME is NULL and PARENT_JOB_ID is NULL and RUN_STATUS='2' order by START_TIME desc;

To Update the records (Processing as Completed)

update HSP_JOB_STATUS set RUN_STATUS = '2' where END_TIME is NULL and PARENT_JOB_ID is NULL and RUN_STATUS='1';

Checking the Planning job status from relational table

Select* from HSP_JOB_STATUS where END_TIME is NULL and PARENT_JOB_ID is NULL and RUN_STATUS='2'

 


Note: For more info. Apart from Job console you can check HBRLaunch log.

Solution 3#

You may increase the planning web session timeout in the entry "60" in web.xml available under WEB-INF folder where planning is deployed. The value has to be specified in minutes.

HBR_MAX_WAIT_FOR_RULE = 600000
HBR_MONITOR_DELAY=600000

To optimize the timeout value:

1 Open the Registry Editor.

2 Navigate to this location:

HKEY_LOCAL_MACHINE/SOFTWARE/HyperionSolutions/Planning

If the Timeout registry key exists in the right pane, the timeout value is set to a corresponding value. If the key does not exist, the value is set to the default. Its type must be DWORD.