Hyperion Planning (MOSC)

MOSC Banner

What should be the recommended JDBC Maximum capacity for EPMSystemRegistry in weblogic

edited Feb 8, 2018 2:39AM in Hyperion Planning (MOSC) 4 comments

We are using Hyperion 11.1.2.3.501 version. Last week our Hyperion application went down without any reason and back online post service restart. As part of RCA we have identified that the JDBC connection pool size for EPMSystemRegistry in weblogic seems to be set low i.e. 30. As per Oracle best practice guide, it is recommended to keep at least max capacity as 150 for EPMSystemRegistry. Can some once suggest on this please? System hardware specifications are listed below

Datasource

Initial Capacity

Maximum Capacity

Minimum Capacity

EPMSystemRegistry

1

30

1

aif_datasource

1

1500

1

calc_datasource

1

15

1

eas_datasource

1

15

1

financialclose_datasource

1

150

1

mds-owsm

0

150

0

mds-soa

0

150

0

odiMasterRepository

1

120

1

odiWorkRepository

1

15

1

OraSDPMDataSource

0

200

0

planning_datasource

1

15

1

raframework_datasource

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center