The following issue applies to an ODI Enterprise deployment (Java EE agent).
This is the ODI error message I received while running about 35 mappings in parallel within a Load Plan:
| 8000 : null : com.sunopsis.dwg.SQLMasterReposException: weblogic.common.resourcepool.ResourceLimitException: No resources currently available in pool odiMasterRepository to allocate to applications, please increase the size of the pool and retry..
com.sunopsis.dwg.SQLMasterReposException: weblogic.common.resourcepool.ResourceLimitException: No resources currently available in pool odiMasterRepository to allocate to applications, please increase the size of the pool and retry.. |
I found that the issue was caused due to a default setup of the Connection Pool properties for “odiMasterRepository”. In this scenario, the value for the “Maximum Capacity” parameter was ’15’.
This value will depend on requirements or the number of objects that will run in parallel.
Some people have experienced some issues using values about 400 and it has been solved by setting the value to 150
(Reference: https://community.oracle.com/thread/2607175)
As a general rule, the value should be always lesser than the database instance value.
