Missing Constraint in Schema Validation Report After Database Was Upgraded to P6 EPPM 16.2.9
(Doc ID 2309582.1)
Last updated on JULY 25, 2019
Applies to:Primavera P6 Enterprise Project Portfolio Management - Version 22.214.171.124 and later
Information in this document applies to any platform.
Schema validation report shows the following missing constraint after an EPPM database was upgraded:
Object Type Object Name Table Name Message
CONSTRAINT fk_taskrsrc_task TASKRSRC Missing constraint TASKRSRC.fk_taskrsrc_task
Schema validation report should not show any missing constraints after database is upgraded
The issue can be reproduced at will with the following steps:
1.Upgrade P6 EPPM database to 16.2.9
2. Run validate.bat from the 16.2.9 media against the upgraded database
3. Observe missing constraint in the PMDB schema validation report
The issue has the following business impact:
Due to this issue, missing constraints are showing in the schema validation report
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