How To: Refreshing RefDb from another environment

When refreshing the RefDb from another environment (such as PROD or UAT) please ensure the following:

  1. The data in DATABASECHANGELOG table must be copied from the source database to the target RefDb.

    1. For multi-schema projects, the schema for these tables can be found by checking the datical.project file for the trackingSchema attribute on row 2.

    2. For single schema projects the tables will be present in the managed schema.

  2. Grants: Ensure any necessary grants are added to the RefDb.

  3. ORACLE: In the event of server outage or unexpected shutdown which requires a refresh of the RefDb, check that no orphan datapump jobs remain on the server.

    1. https://www.oracle-scripts.net/cleanup-orphaned-datapump-jobs

    2. Orphan jobs may result in the following error during the restore operation of a Packager job:

      1.  

        ORA-06512: at "SYS.DBMS_DATAPUMP", line 7143 ORA-06512: at "SYS.DBMS_SYS_ERROR", line 79 ORA-06512: at "SYS.DBMS_DATAPUMP", line 4932 ORA-06512: at "SYS.DBMS_DATAPUMP", line 7137

Failure to copy the DATABASECHANGELOG table data will result in re-deployment of all changesets in the changelog.xml file to the RefDb. This will cause errors for non-rerunnable scripts. Users may find that scripts that were added months ago are suddenly trying to Package again which will lead to confusion.

 

Copyright © Datical 2012-2020 - Proprietary and Confidential