E-AD: PSROLEDEFN, PSLOCK And PSVERSION Are Not Synchronized After Project Copy (Doc ID 1341725.1)

Last updated on MAY 05, 2016

Applies to:

PeopleSoft Enterprise PT PeopleTools - Version 8.49 and later
Information in this document applies to any platform.

Symptoms

When running the sysaudit report, seeing hundreds of security role records where the VERSION field is out of sync with the VERSION field on the PSVERSION and PSLOCK tables (for the ROLM and SYS row). The SYS row is also out of sync because of this.
Tried following the recommended procedure to fix this: Shut down all servers, clear all cache, run the VERSION app Engine program from the command line.  This fixes the problem until another project copy of security roles was performed.

For example, security roles from the source DB contain roles with various VERSIONS (e.g. 423, 6502, 6344, 6067). Security roles in the target have all been reset by the VERSION App Engine program. After the project copy from app designer the target database contains PSROLEDEFN record roles with the same version number as they had in the source DB.  The ROLM VERSION and the SYS VERSION are incremented by 1 but remain much lower than the ROLEDEFN VERSION fields in the target DB.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms