Salesforce

Data Administration - Cannot Load Application Auditing Events, Database Details or Database Options

« Go Back

Information

 
TitleData Administration - Cannot Load Application Auditing Events, Database Details or Database Options
URL Name000045950
Article Number000171165
EnvironmentProduct: OpenEdge
Version: 11.1x, 11.2x, 11.3.1, 11.3.2
OS: All supported platforms
Other: Data Administration, Auditing
Question/Problem Description
Cannot Load Application Auditing Events (.ad)
Loading Database Options fails (_db-option.d).
The Directory listed in the error message is the file name to be loaded.
Steps to Reproduce
Clarifying Information
Table definitions and data load without error.
Application Auditing Events (events.ad) Database Options (_db-option.d) and Database Details ( (_db-detail.d) load without error in OpenEdge 10.2x
Error MessageDirectory of \aud\mynewevents.ad/ does not exist
Directory of \aud\_db-option.d/ does not exist
Directory of \aud\_db-detail.d/ does not exist
Defect NumberDefect PSC00286760
Enhancement Number
Cause
Data Administration/Load Utilities expect  file as an input, but the input (file) is interpreted as a directory, so the file cannot be loaded.  This is as a result of code modification in OpenEdge 11.1.0.0 to handle the load LOB files for tenants (PSC00239756).
Resolution
Upgrade to OpenEdge 11.3.3, 11.4.0 or later. Where load operations in Data Administration that require the file-name as input have been fixed.
Workaround
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 Maintenance

Select: New DB Passkey/Identifier
A 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 History

Alternatively the following ABL can be used:
 
FIND FIRST _db-detail.
UPDATE _db-guid.

 
Notes
Keyword Phrase
Last Modified Date11/20/2020 7:31 AM

Powered by