Orphan Rows Should Be Removed From BenAdmin Tables to Avoid Unique Constraint Errors
(Doc ID 2438825.1)
Last updated on JANUARY 15, 2020
Applies to:PeopleSoft Enterprise HCM Benefits Administration - Version 9.1 to 9.2 [Release 9.0 to 9]
Information in this document applies to any platform.
BenAdmin process could fail with the error below due to orphan rows in BAS_PARTICXXX tables:
Error Message : INSERT or UPDATE would result in duplicate rows in a table with a UNIQUE index
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