Skip to main content

Oracle VDB unquiesce/enable may fail after a failed quiesce/disable on 10.0.0.X or 11.0.0.X




KBA# 10094



After a virtualization engine upgrade, the enable job for Oracle VDBs may fail due to:

SOURCE_UNQUIESCE job for "<VDB NAME>" failed due to an error during execution: Virtual database with name "<VDB NAME>" cannot be enabled as another database instance with same name "<DATABASE NAME>" already exists on host "<HOSTNAME>" in either MOUNTED or OPEN state.


This issue can occur when the associated pre-upgrade quiesce job failed to disable the Oracle VDB for any reason, leaving the VDB running on the target host.

This issue only occurs during "Apply Now" upgrades, deferred upgrades are not affected by this issue.

Applicable Delphix Versions

Click here to view the versions of the Delphix engine to which this article applies
Date Release
May 25, 2023
Apr 13, 2023 | May 6, 2023 |
Mar 13, 2023 | Mar 20, 2023 |


After upgrade, the VDB will be in an inconsistent state, appearing in the Delphix GUI as being disabled, however still having artifacts on the target host. To resolve this inconsistent state, the VDB should be disabled via the CLI and then re-enabled.

ip-10-110-240-158> /source
ip-10-110-240-158 source> select MYVDB
ip-10-110-240-158 source 'MYVDB'> disable
ip-10-110-240-158 source 'MYVDB' disable *> commit

The VDB can then be enabled via the GUI or CLI

ip-10-110-240-158> source
ip-10-110-240-158 source> select MYVDB
ip-10-110-240-158 source 'MYVDB'> enable
ip-10-110-240-158 source 'MYVDB' enable *> commit


Related Articles

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