Hi,

Can anyone help me on this issue.

we created a master ticket and attached more than 20 duplicate tickets . while closing the master ticket,it gave error ARERR(92).
after that we tried closing the master ticket by reducing the duplicate ticket list attached to master ticket to 20 number.
it worked.
what might be the issue with ?

Thanks and regards
Vijay.

Check if your application is correctly designed, optimized and implemented on the performance point of view.

Perhaps increase the amount of fast/list threads?

chck Server logs 4 more clue on wut caused Db Timeout..

luks like an issue whr too many rows were getting updated...

to avoid the time out, here is the thing...

the workflow:
- Check the push fields that create the new entries and verify the 'push fields if' is null. This will cause the server to not execute an unnecessary select statement for each record created against the target form.
- Reduce the size of the target tables (where the records are created), especially the number of clobs (diary fields and char fields > 4000 bytes on Oracle), try to get to 0 clobs. If you are not using the short description (fid 8), set it to 1 char in length with a default of x (or any other character of your choosing).
- Reduce or eliminate any workflow that updates a clob on the target forms
- Avoid the use of set fields/run process in the target forms' filters
- Check for bottlenecks on the db server, esp. disk io. Alternate disk configurations may give you the boost you need
- Check for filters on the target form that perform set fields actions from other forms. Ensure the set field qualification is tuned (i.e., uses an index)
- Reduce number of or eliminate the indexes on the forms where the records are created

Also:
- Set the QBE for all fields on the target form to equal
- Set the results list to the Entry-id only
- Simplify the permissions model for the form. If everyone needs to read and no-one needs to update, set every field to Public view only and set the form to Public hidden only