Absent Member.. Absent Member..
Absent Member..

PPM Support Tip: Request workflow steps with ksc_store are locking

Knowledge Article: KM01389574


Error Message


One or more references in this Request is being updated by another database session. Please try again later. (KCRT-40186)

Request nnnnnn is being updated by another database session. (KNTA-10026)
at com.kintana.core.server.ServerConnectionImpl.lock(ServerConnectionImpl.java:766)
at com.kintana.core.arch.TransactionContextImpl.lock(TransactionContextImpl.java:42)
at com.kintana.core.arch.TransactionContextImpl.lock(TransactionContextImpl.java:57)
at com.kintana.core.arch.ClientTransactionContext.lock(ClientTransactionContext.java:183)
at com.kintana.core.arch.BatchTransaction.setup(BatchTransaction.java:165)
at com.kintana.core.arch.BatchTransaction.setup(BatchTransaction.java:130)
at com.kintana.crt.util.RequestSaveHelper.saveRequestAdditiveInformation(RequestSaveHelper.java:151)

And the below query returns rows under locking conditions:

select a.OBJECT_ID, a.LOCKED_MODE, c.owner, c.object_name, c.object_type, b.sid, b.serial#, b.status, b.osuser, b.machine from v$locked_object a , v$session b, dba_objects c where b.sid = a.session_id and a.object_id = c.object_id




In a cluster with multiple physical machines only had one SERVER_ENV_NAME defined.


Workaround / Fix


Every section in the server.conf should have


that points to the a PPM Environment(i.e. KINTANA_SERVER_A, KINTANA_SERVER_B, ect) where the node is running.

find all references to KINTANA_SERVER in your knta_command_steps
something like:

select * from knta_command_steps where command like '%KINTANA_SERVER%'

understand what each command is doing.  If there is no reason it should always go to the primary machine then find the command (in the front end interface not directly in DB) and change it to use the "[AS.SERVER_ENV_NAME ]" token

That way you will not get cross linked machine dependencies

Best regards,

-- Remember to give Kudos to answers! (click the KUDOS star)
"If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.”
Tags (3)
0 Replies
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.