My Oracle Support Banner

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 15.2.16.0 and later
Primavera P6 Enterprise Project Portfolio Management Cloud Service - Version 15.2.16.0 and later
Information in this document applies to any platform.

Symptoms

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). 

Note:

Executable:    PM.exe
Application:   Primavera P6 Professional R15.2
Event Code:    PRMDB-0396-9
Message:      
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.


Cause

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
Symptoms
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.