Database Transaction Timeout While Inserting Parametric Values To a Role
Last updated on MARCH 08, 2017
Applies to:Oracle Business Process Management Suite - Version 10.3.1 to 10.3.2 [Release AS10gR3]
Information in this document applies to any platform.
***Checked for relevance on 30-May-2012***
A PBL code used to insert parameters to a role is timing out when the number of parameters assigned to the role grows above certain number. The issue is that the time required to insert one parameter increases linearly with the number of parameters already assigned to the role.
We cite the following example as a demonstration of a possible scenario where this issue could be of particular relevance:
In this configuration, there are 60,000 users in the directory. For organization issues, the customer needed to have a role containing as parameters all the user IDs. This means they would have one role with 60,000 parameters, created on the fly as users are created.
The customer tried the following alternatives:
- Create the parameters 1 by 1, and adding the user to the parametric role, while creating the users. But this takes a long time, about 2 to 3 minutes per user.
- Create the role and insert all parameters, and then assign the users to the role with the right parameter. In this case, the process fails to create all parameters for the role, the transaction is longer than the configured JTA timeout (for example, 600s).
- Create the role, and insert the parameters by groups of 10,000 to avoid previous problem. The first 30,000 parameters are inserted without problem, and then the transaction fails with a JTA timeout.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms