Workaround 1: Use
prodict/dump/_loddata.p from OpenEdge 10.2B (if not also loading LOBS for tenants in a Multi-Tenancy enabled database) Refer to Article
How to extract source codes of data dictionary Workaround 2a: Use the Database Administration, Tools, Audit Policy Maintenance, File, Events Maintenance, File, Import to load
Application Auditing Events (.ad)
Workaround 2b: Manually re-create the
Database Options and Database Detail in Database Administration, Admin, Database Options
To modify the DB identifier:
Data Administration > Admin > Database Identification > Database Identification MaintenanceSelect:
New DB Passkey/IdentifierA New DB Identifier will be automatically generated but can be edited to must match the identifier found in the audit data
This change can be viewed from:
Data Administration > Admin > Database Identification > Database Identification HistoryAlternatively the following ABL can be used:
FIND FIRST _db-detail.
UPDATE _db-guid.