Hi,

I get the following error when creating and object store in Filenet 5.5.8 container in OCP, with external DB2 Database:

"The database access failed with the following error: ErrorCode -4,497, Message '[jcc][t4][10342][11669][4.26.14] Application must execute a rollback. The unit of work has already been rolled back in the database but other resource managers involved in this unit of work might not. To ensure integrity of this application, all SQL requests will be rejected until the application issues a rollback. ERRORCODE=-4497, SQLSTATE=null ".

It alway happens after about 100s elapsed time during the object store creation step. I've already checked Filenet transaction timeout (300s). I suspect some additional setting (timeout?) in DB2 could be needed, however I cannot find any reference/detail.

Can you help?

Thanks, regards

L.

The way I would debug it:

1. Get the OS database creation code from ACCE. If you can't find the place I have to look it up. I used to modify that code to optimize the physical layout of some real huge object stores (>4 billion documents)
2. Get a DB2 Data Studio to connect to the db server using the same user that you used with your container.
3. Execute code from 1 and see where it fails...

Maybe also looking at the CPIT scripts will give you some inspiration/insight.

/Gerold

Hi Gerold, and thanks for your support I ultimately found out that in my case I had to extend the totalTransactionTimeout to higher then default (300sec). In a container deployment, the quick way would be to change that value by the cpe configmap:

<transaction totalTranLifetimeTimeout="3000s" />

bye,

L.

Hi all,

what would be the usual way to set the totalTransactionTimeout value in a CP4BA deployment.

In which place adding the tag in the Custom Resource file.

Thank in advance