Skip to main content
Delphix

Provisioning an Oracle vPDB Results in Offline Tablespaces (KBA6183)

 

KBA

KBA# 6183

 

Issue

Provisioning an Oracle vPDB from a source having one or more tablespaces where the corresponding datafiles are 2TB or a multiple thereof, results in those tablespaces being marked offline and missing the related datafiles after the provision completes. This is due to Oracle bug 30999708

The issue starts after the vPDB is recovered and unplugged from an auxiliary vCDB resulting in a corrupt unplug xml file. Later in the provision, Delphix attempts to plugin the vPDB using the resulting corrupt unplug xml file. This results in the following error in the vCDB alert.log:

ORA-65139 signalled during: create pluggable database PDBTEST as clone using '/mnt/provision/VPDBTEST-CDBTEST/datafile/delphix_group_writable/VPDBTEST.xml' nocopy tempfile reuse...

It is unclear which versions of Oracle are affected from the Oracle bug. At this point internal testing indicates that 12.1.0.2 is affected, but we were unable to reproduce using Oracle18c.

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

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

4.3

4.3.1.0, 4.3.2.0, 4.3.2.1, 4.3.3.0, 4.3.4.0, 4.3.4.1, 4.3.5.0

4.2

4.2.0.0, 4.2.0.3, 4.2.1.0, 4.2.1.1, 4.2.2.0, 4.2.2.1, 4.2.3.0, 4.2.4.0 , 4.2.5.0, 4.2.5.1

4.1

4.1.0.0, 4.1.2.0, 4.1.3.0, 4.1.3.1, 4.1.3.2, 4.1.4.0, 4.1.5.0, 4.1.6.0

Resolution

Workaround

Contact Delphix support to verify the issue. Once verified, you can resize the datafile(s) in question by adding 1M on the source database. Snapshots taken after the resize should provision as expected.

Resolution

Create a SR with Oracle support referencing bug 30999708 to get a patch based on your current Oracle version and patch level. You can install the resulting patch on your target vPDB host without installing on the production source host to resolve the issue. 

 

Related Articles

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

  • n/a