Salesforce

_db-guid changed after dump/load and the audit data's link is broken

Printable View
« Go Back

Information

 
Title_db-guid changed after dump/load and the audit data's link is broken
URL Name000044831
Article Number000164720
EnvironmentProduct: OpenEdge
Version: 10.1x, 11.x
OS: All supported platforms
Other: Auditing
Question/Problem Description
Database GUID _db-detail._db-guid changed after recreating the database with dump and load.
New data has been added to the database since it was recreated which uses the new _db-guid
Original audit data has the references to the old _db-guid.
Audit reports only display data linked to the new _db-guid since audit enabled database was recreated
 
Steps to Reproduce
Clarifying Information
Application / Database uses OpenEdge Auditing.
Dumped all tables and sequences through the Data Dictionary and also the audit data using PROUTIL -C AUDITARCHIVE.
Created a new database and loaded all the files.
Audit data reloaded via PROUTIL ... AUDITLOAD.

 
Error Message
Defect Number
Enhancement Number
Cause
This is expected behaviour. In OpenEdge 10.2A,

Creating a database with PROSTRCT CREATE / PROCOPY (or PRODB) %DLC%\empty / PROCOPY (or PRODB) -newinstance will result in a new _db-guid being generated 
If the database was created without -newinstance, then the subsequent action of migrating the audit data with "PROUTIL -C audit load", will change the _db-guid.
 
For further information on database activities that will change the GUID, refer to Article:
Resolution
Adjust auditing reports to include all the relevant (historical) _db-guids.  

OpenEdge® Getting Started: Core Business Services, "Reporting on a single database with multiple GUIDs":

If a reporting requirement is to group related data for a specific database, note that it is possible that a single database GUID (_db-guid) can change over the lifetime of the database, such as following an update to the database passkey, for example. Therefore, data for a single database could, in fact, require reading multiple database GUID values. 
 
    Workaround
    To preserve the original _db-detail,_db-guid: Dump and Load back into the original database
    1. Dump data.
    2. If the database needs to be moved to a new location, PROCOPY the original database (without the -newinstance parameter).
    3. Truncate data areas, leaving the audit data areas instate
    4. Remove / add  Areas / Extents as the dump and load strategy requires
    5. Reload data.

    As long as the -newinstance parameter is not used with PROCOPY (or PRODB)  then the _db-detail,_db-guid value will remain unchanged.
     
    Notes
    Keyword Phrase
    Last Modified Date11/20/2020 7:34 AM
    Powered by