E1: SEC: F9312 "Violation of PRIMARY KEY constraint" Errors for Security History Logging
(Doc ID 1998618.1)
Last updated on OCTOBER 22, 2019
Applies to:JD Edwards EnterpriseOne Tools - Version SP24 to 9.2 [Release SP24 to 9.2]
Information in this document applies to any platform.
These are some scenarios of the errors encountered:
In Tools Release 126.96.36.199 the Enterprise Server JDE.INI has the parameter HISTORY=1 set (enabled), but the same error appears in the server JDE.LOG file:
Duplicate Key in object F9312
This error occurs when users log in and jobs launching. When HISTORY=TRUE logins/logouts are not recorded in F9312.
Error messages can appear as follows:
"Violation of PRIMARY KEY constraint 'F9312_PK'. Cannot insert duplicate key in object 'SY910.F9312'
The duplicate key errors are caused in the logs because the SHUPMT column in the F9312 table is only 6 characters wide, which is not granular enough to store milliseconds. The primary key for F9312 is SHUPMT (time in seconds). When simultaneous logins occur within a second, the system errors because it cannot record the information into F9312.
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