Event Code "PRMDB-0396-9, Message: SQL Error Code:1205, Level: 13, Procedure: GETNEXTKEYS, Line: 9 Transaction (Process ID 206) was deadlocked" When Scheduling in P6 Professional, Connected to a SQL Server 2014 Database
(Doc ID 2360798.1)
Last updated on JULY 30, 2019
Applies to:Primavera P6 Enterprise Project Portfolio Management - Version 184.108.40.206 and later
Primavera P6 Enterprise Project Portfolio Management Cloud Service - Version 220.127.116.11 and later
Information in this document applies to any platform.
When multiple users are working in the same large project and scheduling, the scheduling sometimes gets stuck at certain percentages (20%) and will freeze for an extended period of time (upwards of an hour).
- This issue occurs when connecting to a SQL Server 2014 database.
- While this is occurring, a different user can log in, open the same project and schedule it quickly (under 1 minute).
- Sometimes, the original stuck scheduling process will end with the following event code:
Application: Primavera P6 Professional R15.2
Event Code: PRMDB-0396-9
PRM DBAccess Error: SQL State: 51, SQL Error Code:1205, Level: 13, Procedure: GETNEXTKEYS, Line: 9
Transaction (Process ID 206) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document