CA Datacom - DB
CA Datacom - AD
CA Datacom - Server
Some CA Datacom/DB Data Dictionaries may have had problems from the past which caused upgrade DDUPDATE steps with…
…where version TEST or PROD (or both) fail with error…
**** ERROR **** RETURN CODE = DDPUPN004 INTERNAL ERROR - SEE MESSAGE MANUAL
ERRORS DETECTED, NO MAINTENANCE APPLIED
In this example, KEY SYSCONSTRSRC is seen in the error message, but it may be a different KEY.
The problem is caused by a broken RELATIONSHIP from either KEY to TABLE or TABLE to KEY.
How to address DDPUPN004 error running DDUPDATE -UPG KEY,ALL,ALL(version)?
To determine the cause, run the following DDUPDATE or DDUTILTY request for the version:
The report may show one of two things….
1. If the TABLE to KEY relationship is missing but the KEY to TABLE relationship exists, the report will show TBL with “* * nnn” in the report.
T T001 ATBK2 020
* *001 000
If no “* *nnn” in the DD report, the TABLE to KEY relationships do exist.
2. Then, if the relationship from the KEY to TABLE is missing, the report will show only the KEY occurrence and no TBL occurrence.
So, given the results for SYSCONSTRSRC…
SQL SYSTEM CONSTRAINT SOURCE
To determine the versions of that key named SOURCE-KEY, run DDUTLTY /DDUPDATE with:
Then run DDUPDATE to delete those KEYs which have broken relationships:
-DEL KEY, SYSCONSTRSRC.SOURCE-KEY(version)
After the orphan KEYs have been deleted, rerun the DDUPDATE:
Then run DDCBLD with -HSD RESET.