Skip to main content
Delphix

Oracle Compatible Parameter and Delphix dSources and VDB Provision and Refresh Operations (KBA7756)

 

KBA

KBA# 7756

Applicable Delphix Versions

Click here to view the versions of the Delphix engine to which this article applies
Major Release All Sub Releases
6.0 6.0.0.0, 6.0.1.0, 6.0.1.1, 6.0.2.0, 6.0.2.1, 6.0.3.0, 6.0.3.1, 6.0.4.0, 6.0.4.1, 6.0.4.2, 6.0.5.0, 6.0.6.0, 6.0.6.1, 6.0.7.0, 6.0.8.0, 6.0.8.1

5.3

5.3.0.0, 5.3.0.1, 5.3.0.2, 5.3.0.3, 5.3.1.0, 5.3.1.1, 5.3.1.2, 5.3.2.0, 5.3.3.0, 5.3.3.1, 5.3.4.0, 5.3.5.0, 5.3.6.0, 5.3.7.0, 5.3.7.1, 5.3.8.0, 5.3.8.1, 5.3.9.0

5.2

5.2.2.0, 5.2.2.1, 5.2.3.0, 5.2.4.0, 5.2.5.0, 5.2.5.1, 5.2.6.0, 5.2.6.1

5.1

5.1.0.0, 5.1.1.0, 5.1.2.0, 5.1.3.0, 5.1.4.0, 5.1.5.0, 5.1.5.1, 5.1.6.0, 5.1.7.0, 5.1.8.0, 5.1.8.1, 5.1.9.0, 5.1.10.0

5.0

5.0.1.0, 5.0.1.1, 5.0.2.0, 5.0.2.1, 5.0.2.2, 5.0.2.3, 5.0.3.0, 5.0.3.1, 5.0.4.0, 5.0.4.1, 5.0.5.0, 5.0.5.1, 5.0.5.2, 5.0.5.3, 5.0.5.4

The implications of compatible parameter changes.

Oracle upgrades present a number of challenges for Delphix Administrators and Users.  Delphix will capture and hold a set of parameters that are in line with each Delphix snapshot that is captured of the dSource.  As dSource databases are upgraded the compatible parameter value will normally be advanced in line with the new Oracle release being used in the source database.  Snapsync operations occurring after this advance in the compatible parameter will mean that the new value starts being held with the snapshots.  A number of scenarios are presented to the Delphix Administrator as dSources are upgraded and the compatible parameter in the dSource is advanced along Oracle versions.

Scenario 1 - VDB Provision where the new dSource version does not exist on the VDB target host.

The source database is upgraded to a new release, the examples here show a move from 12.1.0.2 to 19.3.0.0.   A new snapshot of the dSource in the new release is captured.  An attempt is then made to provision a new VDB from this new version of the dSource.

 snapshot_id |       container       |     timeflow      |      creation_time      |  version   | compatible_param 
-------------+-----------------------+-------------------+-------------------------+------------+------------------
           3 | ORACLE_DB_CONTAINER-1 | ORACLE_TIMEFLOW-1 | 2021-05-29 05:42:18.336 | 19.3.0.0.0 | '12.1.0.2.0'
           1 | ORACLE_DB_CONTAINER-1 | ORACLE_TIMEFLOW-1 | 2021-05-29 04:09:15.79  | 12.1.0.2.0 | '12.1.0.2.0'
(2 rows)

The snapshot, snapshot_id 3, shows compatible as 12.1.0.2 in the dSource snapshot.

Provisioning a VDB from an upgraded dSource requires the version of the Oracle Home in the dSource aligning with the version of the Oracle Home to be used by the VDB.   If no Oracle Home is present in the target host environment for the yet to be created VDB, Delphix. will prevent creation of the VDB.

Scenario 2 - VDB Provision where the compatible parameter has not been advanced in the dSource.

 

Scenario 3 - VDB Provision where the compatible parameter has been advanced in the dSource.

 

Scenario 4 - VDB Refresh where the compatible parameter has not been advanced in the dSource.

Any VDB's that are provisioned from snapshots where the compatible parameter has the older value can run into errors when a refresh attempt is performed as Delphix will try to establish the new version of the database and maintain the older version of the parameter.

 

Scenario 5 - VDB refresh where the compatible parameter has been advanced in the dSource.

 

 

Scenario 6 - VDB rewind using a snapshot where compatible is a lower release than that currently set in the VDB.

 

 

Scenario 7 - VDB rewind using a snapshot where compatible is set to a higher release than that currently set in the VDB.

 

 

Prerequisites

text

 

Related Articles

The following articles may provide more information or related information to this article:

  • link
  • link
  • link