Missing Contraint in Schema Validation Report After Database Was Upgraded to P6 EPPM 16.2.9

(Doc ID 2309582.1)

Last updated on OCTOBER 26, 2017

Applies to:

Primavera P6 Enterprise Project Portfolio Management - Version 16.2.9.0 and later
Information in this document applies to any platform.

Symptoms

ACTUAL BEHAVIOR

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

EXPECTED BEHAVIOR

Schema validation report should not show any missing constraints after database is upgraded

STEPS

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

BUSINESS IMPACT

The issue has the following business impact:
Due to this issue, missing constraints are showing in the schema validation report

Changes

 

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