Traditional packaging requires users to maintain a reference database, but often this is expensive and cumbersome to manage. Using an Oracle Ephemeral Database eliminates the need to manage an additional database on the pipeline. You simply configure Liquibase to create a temporary copy of a database in the pipeline to be used in place of the Reference Database. Once the copy is made, you will ensure that all of your changes work on the copy, implement them on your original database’s changelog, and then destroy the database copy. Follow this guide to learn how to implement this workflow.

Pre-requisites

• Requires Liquibase Enterprise 8.6 and higher

• Ephemeral database connection is based on Oracle multi-tenant PDB technology

• Ephemeral database connection requires a user on ORCLCDB with SYSOPER privileges and the ability to create pluggable databases

Limitations

• Ephemeral database feature works ONLY for PDB databases

• Ephemeral database feature works ONLY for Oracle 19c and 21c

• Ephemeral database feature does not work for Oracle RDS

• You cannot place the temporary copied database in a pipeline or run a status on it because technically it does not exist in the pipeline.

Usage

Using an Oracle Ephemeral Database eliminates the need to manage an additional database on the pipeline. The ephemeral packaging feature creates a pluggable PDB copy when the packager runs, then packages all the changes on it, and drops the PDB copy after packaging is complete. If the final deploy is not skipped - it will deploy newly packaged changes on the desired database (this is the DEV database in most cases).

Open

Backup and Restore Package Methods

In order to implement an Ephemeral Database, the databaseBackupRestoreMethod package method on the deployPackager.properties needs to be configured.

Two new package methods are supported. You can use an internal or external container depending on your needs. If your internal container is secured and permissions do not allow you to make changes within it, the external package method is recommended.

See: Use the Required deployPackager.properties File

1. Choose the Internal or External Method

First you must decide if you are using the internal or external Ephemeral method.

2. Create ORCLCDB SYSOPER User

Once that is decided, you will create a user. You must create a new user on Oracle CDB with the associated privileges to create an ephemeral copy for both internal and external methods.

3a. BackupRestoreOracleEphemeralInternalPdb

These are the Internal method privileges given to the user on the container.

3b. BackupRestoreOracleEphemeralExternalPdb

These are the external method privileges given to the users for both the source and external containers.

The source database is the first database in a pipeline. The external database will be an ephemeral copy of the source database made on the external container.

Source container user privileges:

External container user privileges:

On the external database create a new user on oracle CDB with the following privileges. This allows Liquibase to create an ephemeral copy and create a link to the source database.

This is the database link on the external container to the source database.

TNS option
Also there is a possibility to use TNS name during link creation, e.g.

To check if database link has been created correctly please run query below, if you don’t get errors - database link should be correct.

4. Optional: Only for TNSNAMES/LDAP Users
Use TNSNAMES/LDAP with Oracle Ephemeral Database

Learn more about traditional LDAP connections here: https://datical-cs.atlassian.net/wiki/spaces/DDOC/pages/896566926

If you use TNS names in your dbDef, then you should prepare a TNS name with _eph postfix for the ephemeral copy because Liquibase cannot modify TNS files.

If this is what your dbDefs look like:

Then you should add a dev_eph entry in your TNS configuration that points to a PDB. To determine the service name or SID for the PDB which this TNS will point to, use one of the following methods depending on your situation:

• If you provided a value for oracleEphemeralCopyName , then this value will be what you add to your TNS configuration.

• If you didn’t provide a value for oracleEphemeralCopyName, but provided it for oracleEphemeralSourceName - it will be the oracleEphemeralCopyName value + _eph postfix.

• If you didn’t provide any of these values, add _eph postfix to your source PDB name.

• If your source PDB name is bucket_01, then your value will be bucket_01_eph

If you have a dev entry in your TNS file, then you should create an alias for the dev_eph entry which points to the ephemeral copy (admin_sysoper is just an example entry for a connection pointing to ORCLCDB.)

Example tnsnames.ora file:

5. Methods for creating the Ephemeral dbDef

An ephemeral dbDef must be created in the datical.project file to instruct Liquibase how to connect to the cloned ephemeral copy. Because this database is transient by definition and only exists during the Deploy Packager operation, you are not able to run Status against it.

In order to create a dbDef without including the dbDef on an existing pipeline Liquibase recommends using ONE of the following methods:

• Method 1: Create the dbDef using the Liquibase Enterprise GUI and then delete the dbDef from the pipeline.

• Method 2: Include the ephemeral dbDef on the Project Creation Script but do not include the dbDef on any pipelines.

• Method 3: Manually copy the dbDef from an existing dbDef in the pipeline.

Follow the instructions below based on the desired method.

Method 1: Create the dbDef with the Liquibase Enterprise GUI

1. Create the dbDef using instructions from Creating a Liquibase Enterprise project Using the Liquibase Enterprise GUI

2. Ensure the Name of the database is <dbDef_to_be_cloned>_EPHEMERAL. The <dbDef to be cloned> needs to be the first database in the pipeline.

   Open

   

3. Enter your Connection Settings.

   1. If you are using a TNSNAMES/LDAP connection, see the section above Use TNSNAMES/LDAP with Oracle Ephemeral Database.

   2. If you are using a BASIC connection, the Service Name is ORCLCDB or the name of the container that houses the ephemeral copy. (See Backup and Restore Package Methods section before for more information.)

      1. Enter your container name in the Hostname text box. This entry depends on if you are using an internal or external backup and restore method. (See Backup and Restore Package Methods section before for more information.)
         
         

      2. The username and password are the ORCLCDB user created in step 2. Create ORCLCDB SYSOPER User above.

4. Contexts and Labels

   1. Contexts are left blank or set to the same context as the dbDef to be cloned.

   2. Set your Labels to either of these:

      1. To the name of the pipeline that houses the dbDef to be cloned

      2. Or use the same pattern that is in use for the dbDef to be cloned

5. After creating the dbDef, remove the Step from the Pipeline by selecting Remove Step.

6. Do not select the box to delete the Deployment Step from the Deployment Plan

Method 2: Create the dbDef with the Project Creation Script

1. Create the project using the instructions from https://datical-cs.atlassian.net/wiki/spaces/DDOC/pages/896569181

2. Include the ephemeral database on the ProjectNameOracle.dbdefs.tsv.txt.
   Use name: <dbDef_to_be_cloned>_EPHEMERAL

Method 3: Manually create the dbDef by copying from the existing dbDef in datical.project

If you are manually copying the dbDef in the datical.project file from the dbDef to be cloned:

1. If the password is present in the file, please note this value is Base64 encoded. If modifying this value, the new value will also need to be Base64 encoded.

2. Clear out the dbDefsId for the new _EPHEMERAL dbDef.

3. Do a Test Connection to another database in the pipeline or sync the project to the DMC to populate the dbDefsId field before checking the datical.project changes into source control.

6. Optional Step: Associated deployPackager.properties

These are packaging properties available specifically for the ephemeral database packaging method. They are optional if you would like to override the default values.

See: Use the Required deployPackager.properties File

Troubleshooting:

Potential grants issues

• If oracleEphemeralSourceName packager property is not specified Liquibase attempts to get the PDB name from three different tables on the database. These tables are v$pdbs, dba_data_files, and v$parameter. If the requested grants are in place as listed on , the PDB name can be located. Both GRANT SELECT ANY DICTIONARY TO DATICAL_ROLE; and GRANT IMP_FULL_DATABASE TO DATICAL_PACKAGER_ROLE; provide the proper permissions to query the required tables. If these permissions have not been granted, in order to use ephemeral databaseBackupRestoreMethod, permissions to query v$pdbs, dba_data_files and v$parameter tables must be granted.

Use Oracle Managed Files (OMF) with Oracle Ephemeral Database

If you are using OMF with BackupRestoreOracleEphemeralExternalPdb, then OMF mode should be the same on both instances of the Oracle database.