Why Do Hyperion System 9 and EPM 11 Jobs Fail If They Run Over 10 Hours?

Why Do Hyperion System 9 and EPM 11 Jobs Fail If They Run Over 10 Hours? [ID 1085881.1]
		Modified 28-MAR-2011     Type HOWTO     Status PUBLISHED

In this Document
  Goal
  Solution
  References

---

Applies to:

Hyperion BI+ - Version: 9.3.1.1.00 and later   [Release: 9.3 and later ]
Information in this document applies to any platform.

Goal

Why do Hyperion System 9 and EPM 11 jobs fail if they run over 10 hours?

Solution

This is a known limitation. Unpublished bug 6844276 states: ABSOLUTE 10 HOUR JOB TIMEOUT SHOULD BE ADJUSTABLE AND NOT PROVIDE SPURIOUS ERROR. Since jobs run as emulated user sessions, an absolute limit of 10 hours was built into the system so if no result was received within 10 hours, a job process would be killed.

Happily development worked on this and they have made the EMULATED_CLIENT_MAX_IDLE_TIME configurable in EPM 11.1.2.0. The setting may be adjusted to a value (in minutes) for emclient.maxidlemin in JAVA_OPT in CMC to some value greater than 600 minutes.

The only workaround for the time being would be to ensure the jobs do not run 10 hours or longer (for example for SQR jobs: add indices to database tables, pull frequently used information into memory-based arrays, split processing into two or more reports, put SQR or the database on faster hardware, run the job when there are less CPU cycles being taken by other processes, etc). Some problem applies for SQR, BQY and generic jobs.