Your suggested change has been received. Thank you.

close

Suggest A Change

https://thales.na.market.dpondemand.io/docs/dpod/services/kmo….

Thales Logo

All

  • All
back

Tasks

Upgrade CDP

search

Please Note:

Upgrade CDP

The CDP software is regularly updated to include new features and provide fixes to any issues occurring in previous releases. Upgrading the existing CDP software brings the new features added and enhancements made to the product since the CDP installation. When upgrading from a previous version of the CDP, the reload option must be used. The upgrade process reloads all executables, stored procedures, user defined functions, and the ProtectDB.properties file.

After the upgrade, the old properties file is renamed (version and build number of old CDP software is added as suffix) and archived under the /lib/safenet/archive directory on Linux and \bin\archive on Windows. A new properties file is created in the installation directory. The new properties file contains new values that were entered while upgrading CDP. The remaining parameters are left with default values. To edit these parameters, the values can be copied from the old properties file stored in the archive folder.

To upgrade the CDP software, the installer must be run in the reload mode.

Note

  • Instructions to upgrade any version of CDP to the latest version are same, as given below. For information on CDP and Key Manager compatibility, refer to Release Notes.

  • Before upgrading CDP, make sure that domain indexes and views and triggers are dropped, otherwise, the upgradation fails.

Upgrade CDP

  1. Open a command prompt window.

  2. Navigate to the directory where the script is located.

  3. Run the install script with the reload flag.

    Enter one of the following commands, depending on the operating system:

    • Windows install.bat reload

    • UNIX/Linux install.sh reload

  4. Enter the following information when prompted:

  5. Passwords for the SYS and metadata (INGRIAN) users.

  6. Enter Y if installation is performed in Pluggable Database (PDB) for the Oracle user INGRIAN, else N.

  7. Path to ORACLE_HOME for the installation. (For Windows installation)

  8. Path to the properties file. Read access to this file is required.

  9. NAE Server IP address and port.

  10. Full path and file name for the log file. Write access to this file is required.

Upgrade Oracle Database from 11g to Oracle 12c

After CDP is installed on your Oracle 11g database, follow these steps for each migrated table when upgrading from Oracle 11g to Oracle 12c:

Note

The steps mentioned here can also be used when upgrading:

* From Oracle 11g to Oracle 18c

* From Oracle 12c to Oracle 18c

* From Oracle 12c to 19c

  1. Delete views and triggers for each migrated tables. Refer “Deleting Views and Triggers” for more details.

    Note

    The views and triggers need to be recreated after metadata restoration is performed on Oracle 12c.

  2. Backup the user database.

  3. Backup the CDP metadata by running metadatabackup.sh/metadatabackup.bat from the <installdirecotry>\CDP_for_Oracle\upgradescript directory. The metadatabackup.sh/metadatabackup.bat script does the following for metadata backup:

    a. Creates a spool directory and then backup of the following metadata tables in .csv files:

    • ING_ENCRYPTED_TABLE

    • ING_ENCRYPTED_COLUMN

    • ING_JOB_COLUMN

    • ING_JOB

    • ING_AUTHORIZED_USER

    b. Creates backup of instance ID from ING_PROPERTY table in .csv file.

    c. Creates backup of database ID from ING_PROPERTY table in .csv file.

    d. Creates backup of the following sequences used by CDP:

    • ING_AUTHORIZED_USER_SEQ

    • ING_COLUMN_DEFAULT_SEQ

    • ING_ENCRYPTED_COLUMN_SEQ

    • ING_ENCRYPTED_TABLE_SEQ

    • ING_ERROR_LOG_SEQ

    • ING_JOB_SEQ

  4. Uninstall CDP from Oracle 11g. Refer to Uninstalling CDP for details.

  5. Upgrade Oracle 11g to Oracle 12c.

  6. Install CDP on Oracle 12c.

    Note

    Do not encrypt any new table in Oracle 12c before metadata restoration, else the restoration may fail.

  7. Restore the CDP metadata by executing metadatarestore.sh/metadatarestore.bat scripts from the <installdirecotry>\CDP_for_Oracle\upgradescript directory. The metadatarestore.sh/metadatarestore.bat script does the following for metadata restoration:

    a. Verifies that no tables are encrypted before metadata restoration. It tests the following tables to ensure these are empty:

    • ING_ENCRYPTED_TABLE

    • ING_ENCRYPTED_COLUMN

    • ING_JOB

    b. Restores the following metadata tables:

    • ING_ENCRYPTED_TABLE

    • ING_ENCRYPTED_COLUMN

    • ING_JOB_COLUMN

    • ING_JOB

    • ING_AUTHORIZED_USER

    c. Restores the instance ID.

    d. Restores the database ID.

    e. Restores the following sequences to be used by CDP:

    • ING_AUTHORIZED_USER_SEQ

    • ING_COLUMN_DEFAULT_SEQ

    • ING_ENCRYPTED_COLUMN_SEQ

    • ING_ENCRYPTED_TABLE_SEQ

    • ING_ERROR_LOG_SEQ

    • ING_JOB_SEQ

  8. Recreate views and triggers for the encrypted tables (created on Oracle) to use them.

On this page