E1: KER: DDDict TAM Specs Become Corrupt When Restarting EnterpriseOne Services
(Doc ID 645005.1)
Last updated on JUNE 07, 2021
Applies to:JD Edwards EnterpriseOne Tools - Version SP24 and later
Information in this document applies to any platform.
You occasionally have to delete the data dictionary and global table TAM spec files (dddict*, ddtext*, and glbltbl*) on your Enterprise Server because they become corrupt. You need some help preventing these production outages. It appears to occur when you stop services and then initiate your server backups.
You see the issue when some (not all) UBEs end in error. You restart/bounce services in the morning. Your logs show errors with "DDDict.xdb" that refers to an invalid entry. In the past, GCS has recommended deleting the dddict.ddb, xdb, ddtext.ddb, xdb files to address this issue. Is there a permanent solution to this issue?
Error in server log(s):
11 08:25:27.425171 jdetamp.c2073 TAMFetchByKey (/PD9/specfile/dddict.xdb): Invalid Index ID 2 (No Indices defined) (/PD9/specfile/dddict.xdb)
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