Requirements for Upgrading Databases That Use Oracle Label Security and Oracle Database Vault

You must complete these tasks before starting an upgrade with a database using Oracle Label Security or Oracle Database Vault.

DBUA, AutoUpgrade, and Oracle Database Vault

If you use Database Upgrade Assistant (DBUA) to upgrade Oracle Database 12c Release 2 (12.2), Oracle Database 18c, or Oracle Database 19c, and your system uses Oracle Database Vault, then you must use this upgrade process.

If you use DBUA to perform the upgrade, then DBUA uses the AutoUpgrade utility to complete the upgrade. However, in that case, AutoUpgrade does not automatically disable Oracle Data Vault for upgrades from Oracle Database 12c Release 2 (12.2), Oracle Database 18c (18.3), or Oracle Database 19c (19.3) to the new Oracle Database release. Before you upgrade a source Oracle Database from one of these releases, you must first disable Oracle Data Vault.

Example 2-7 Overview of Upgrade Procedure for Databases Using Oracle Data Vault

You complete an upgrade from a source database where Oracle Database Vault is enabled with the following steps:

  1. Disable Oracle Data Vault.
  2. Install the new Oracle Database release.
  3. Download the latest AutoUpgrade JAR file from My Oracle Support note 2485457.1, and replace the AutoUpgrade JAR file in the new Oracle Database release, in the path Oracle_home/rdbms/admin
  4. Run the AutoUpgrade utility (or Database Upgrade Assistant), and complete the upgrade.
  5. Enable Oracle Database Vault in the upgraded Oracle Database.

Granting the DV_PATCH_ADMIN Role to SYS for Oracle Database Vault

If Oracle Database Vault is enabled, then to perform checks for Oracle Data Vault, the upgrade process requires running three SQL scripts.

The SYS user requires the DV_PATCH_ADMIN role for the following scripts:

OLS_SYS_MOVE runs olspreupgrade.sql:


EM_PRESENT runs emremove.sql:


AMD_EXISTS CHECK runs catnoamd.sql: