Upgrading a Primary-Standby Oracle Key Vault Server

This upgrade includes the Oracle Key Vault server software and utilities that control the associated endpoint software

About Upgrading a Primary-Standby Oracle Key Vault Server

To benefit from new features and security enhancements, Oracle recommends that you upgrade Oracle Key Vault server to the latest release.

You must upgrade in the following order: first perform a full backup of Oracle Key Vault, upgrade the Oracle Key Vault primary-standby server pair, upgrade the endpoint software, and last, perform another full backup of the upgraded server. Note that upgrading requires a restart of the Oracle Key Vault server.

Oracle recommends using multi-master cluster deployment for production use. During upgrade of a multi-master cluster, there is no downtime of databases or business applications. A 2-node cluster provides read-only availability, and 4 or more node clusters provide continuous read-write availability. You can enable the persistent cache feature to enable endpoints to continue operation during the upgrade process.

When you upgrade the Oracle Key Vault server software, to access the latest enhancements, also upgrade the endpoint software. While endpoint software from the previous Oracle Key Vault release will continue to function with the upgraded Oracle Key Vault server, new endpoint functionality may not work.

Before you begin the upgrade, refer to Oracle Key Vault Release Notes for additional information about performing upgrades.

Related Topics

Step 1: Back Up the Server Before You Upgrade

Before you upgrade the Oracle Key Vault server, perform a one-time backup to a remote destination so that you can recover data in case the upgrade fails.

Caution: Do not bypass this step. Back up the server before you perform the upgrade so that your data is safe and recoverable.

Step 2: Perform Pre-Upgrade Tasks for the Primary-Standby Oracle Key Vault

To ensure a smooth upgrade to Oracle Key Vault, you should prepare the server you are upgrading.

  1. In the server where Oracle Key Vault is installed, log in as user support, and then switch to the root user.

  2. Ensure that the server meets the minimum disk space requirements for an upgrade. For example, 6 GB of free space in the /usr/local/dbfw/tmp directory. See the Oracle Key Vault Readme for this release to determine the disk space requirements for the upgrade.

  3. Ensure that you disable diagnostics and clean up disk space in /usr/local/dbfw/tmp before you upgrade by performing the following steps:

    If the Oracle Key Vault system being upgraded is from release 21.6 or later, log in to the Oracle Key Vault management console as a user with the System Administrator role, and navigate to the System tab, and then click the Diagnostics button.

    If the Diagnostics Package Files pane is displayed, then click Clear to disable diagnostics. Note that the Diagnostics Package Files pane will be displayed only if the diagnostics bundle was previously generated, and the files were not cleared.

    If the Diagnostics Package Files pane is not displayed, or if the diagnostics bundle was previously generated using the dbfw-diagnostics-package.rb utility, then log in to the Oracle Key Vault system and run the following commands to disable diagnostics and clean up disk space in /usr/local/dbfw/tmp:

    1. SSH into the Oracle Key Vault system as user support, then switch to user root:

      ssh support@<OKV_IP_Address>
su - root

    2. Delete the generated diagnostics zip file and remove the package using the following commands:

      /usr/local/dbfw/bin/priv/dbfw-diagnostics-package.rb --clean
/usr/local/dbfw/bin/priv/dbfw-diagnostics-package.rb --remove

  4. Check the boot partition size. If any of the nodes in question have a boot partition that is less than 500 MB, then you cannot upgrade that system to the new release. You can check this size as follows:

    1. Mount the /boot partition.

      mount /boot

    2. Check the Size column given by the following command:

      df -h /boot

    3. Unmount the /boot partition:

      umount /boot

    If the boot partition given by this command shows less than 488 MB, then you cannot upgrade to the current release. Oracle recommends that you restore a backup of the current configuration to a freshly installed system of the same release as the current system, and upgrade that to the new release instead.

  5. If Oracle Key Vault is using the BIOS boot mode, then ensure that the disk size is not greater than 2 TB. If this is the case, then you cannot upgrade to the current release. Oracle recommends that you restore a backup of the current configuration onto a system with a disk that is less than 2 TB in size, and upgrade that to the new release instead.

  6. If you need to increase available disk space, then remove the temporary jar files located in /usr/local/okv/ssl. Be careful in doing so. If you accidentally delete any files other than the jar files in /usr/local/okv/ssl, then the Oracle Key Vault server becomes non-functional.

  7. Increase your disk space by extending the vg_root size.

    You must increase the disk space by extending vg_root before you perform the upgrade.

  8. Ensure that no full or incremental backup jobs are running. Delete all scheduled full or incremental backup jobs before the upgrade.

  9. Plan for downtime according to the following specifications:

    Oracle Key Vault Usage Downtime required
    Wallet upload or download NO
    Java Keystore upload or download NO
    Transparent Data Encryption (TDE) direct connect YES (NO with persistent cache)
    Primary Server Upgrade in a primary-standby deployment YES (NO with persistent cache)

  10. Plan for downtimes.

    • If Oracle Key Vault uses an online master encryption key, then plan for a downtime of 15 minutes during the Oracle Database endpoint software upgrades. Database endpoints can be upgraded in parallel to reduce total downtime.

    • Plan for a downtime of a few hours. The persistent cache allows you to upgrade Oracle Key Vault servers without database downtime. The default duration of the persistent cache from the moment the Oracle Key Vault server becomes unavailable is 1,440 minutes (one day).

  11. If the Oracle Key Vault system has a syslog destination configured, ensure that the remote syslog destination is reachable from the Oracle Key Vault system, and that logs are being correctly forwarded. If the remote syslog destination is not reachable from the Oracle Key Vault system, then the upgrade process can become much slower than normal.

  12. If Oracle Audit Vault was integrated with Oracle Key Vault in Oracle Key Vault release 21.2 or earlier, then do the following on the primary server (but not the standby) to disable and remove the Oracle Audit Vault integration:

    1. Disable the Oracle Audit Vault integration: Log into the Oracle Key Vault management console as a System Administrator, select the System tab and then Settings from the left navigation bar. In the Monitoring and Alerts pane, select Audit Vault. In the Audit Vault integration pane that appears, disable Oracle Audit Vault. Click Save.

    2. Perform the remaining steps in this procedure on each server where the Oracle Audit Vault integration was configured.

    3. Log in to the Oracle Key Vault server through SSH as user support, switch user su to root and then switch user su to oracle.

    4. Stop the agent by executing the following command:

      agent_installation_directory/bin/agentctl stop

    5. Log in to the Oracle Audit Vault Server console as an Oracle Audit Vault administrator.

    6. Delete the corresponding agent and target.

    7. Log in to the Oracle Key Vault server through SSH as user support, then switch user su to root.

    8. Delete the installation directory for the Oracle Audit Vault agent.

  13. Ensure that the Oracle Key Vault server certificate has not expired, nor is close to expiry, before you begin the upgrade.

    You can find how much time the Oracle Key Vault server certificate has before it expires by checking the OKV Server Certificate Expiration setting on the Configure Alerts page in the Oracle Key Vault management console.

  14. If you are performing an upgrade while using an HSM as a Root of Trust, then consult Oracle Key Vault Root of Trust HSM Configuration Guide for any additional steps that may be needed.

  15. Ensure that the backup of the orapwdbfwdb file matches the original file.

    1. SSH into the Oracle Key Vault system as user support, then switch to user root:

      ssh support@<OKV_IP_Address>
su - root

    2. Verify that the backup file exists:

      su - oracle
ls -ltr /var/lib/oracle/okv_orapwd_backup_dir/orapwdbfwdb

    3. If the backup file exists, then perform the following steps:

      • Compare the original file with the backup file:

        diff /var/lib/oracle/dbfw/dbs/orapwdbfwdb /var/lib/oracle/okv_orapwd_backup_dir/orapwdbfwdb

      • If there is a difference between the files, then update the backup file by copying the original file:

        cp /var/lib/oracle/dbfw/dbs/orapwdbfwdb /var/lib/oracle/okv_orapwd_backup_dir/orapwdbfwdb

Related Topics

Step 3: Add Disk Space to Extend the vg_root for the Release 21.16 Upgrade

Before upgrading to Oracle Key Vault release 21.16, you will need to extend the vg_root to increase disk space.

If you are upgrading from an earlier Oracle Key Vault release 21.x release and have already extended the vg_root, then you can bypass this step.

Before you start this procedure, ensure that all endpoints have persistent cache enabled and in use.

  1. Log in to the server for which you will perform the upgrade and switch user as root.

  2. Ensure that the persistent cache settings for Oracle Key Vault have been set.

    You will need to ensure that the persistent cache has been enabled because in a later step in this procedure, you must shut down the server. Shutting down the Oracle Key Vault server will incur downtime. To avoid any downtime, Oracle recommends that you turn on persistent cache.

  3. Run the vgs command to determine the free space

    vgs

    The VFree column shows how much free space you have (for example, 21 GB).

  4. Power off the server in order to add a new disk

    /sbin/shutdown -h now

  5. Add a new disk to the server with a capacity of 100 GB or greater

  6. Start the server.

  7. Log in to the Oracle Key Vault server through SSH as user support, then switch user su to root.

    ssh support@okv_server_IP_address
su - root

  8. Stop the Oracle Key Vault services.

    service tomcat stop;
service httpd stop;
service kmipus stop;
service kmip stop;
service okvogg stop;
service javafwk stop;
service monitor stop;
service controller stop;
service dbfwlistener stop;
service dbfwdb stop;
service rsyslog stop;

  9. Run the fdisk -l command to find if there are any available partitions on the new disk.

    fdisk -l

    At this stage, there should be no available partitions.

  10. Run the fdisk disk_device_to_be_added command to create the new partition.

    For example, to create a disk device named /dev/sdb:

    fdisk /dev/sdb

    In the prompts that appear, enter the following commands in sequence:

    • n for new partition

    • p for primary

    • 1 for partition number

    • Accept the default values for cylinder (press Enter twice).

    • w to write and exit

  11. Use the pvcreate disk_device_partition command to add the newly added disk to the physical volume.

    For example, for a disk device named /dev/sdb1, which is the name of the disk partition that you created (based on the name used for the disk device that was added).

    pvcreate /dev/sdb1

    Output similar to the following appears:

    Physical volume "/dev/sdb1" successfully created

  12. Use the vgextend vg_root disk_device_partition command to extend the logical volume with this disk space that you just added.

    For example, for the partition /dev/sdb1, you would run:

    vgextend vg_root /dev/sdb1

    Output similar to the following appears:

    Volume group "vg_root" successfully extended

  13. Run the vgs command again to ensure that VFree shows an increase of 100 GB.

    vgs

    Output similar to the following appears:

    VG      #PV #LV #SN Attr   VSize   VFree
vg_root   2  12   0 wz--n- 598.75g <121.41g

  14. Restart the Oracle Key Vault server.

    /sbin/reboot

    For primary-standby deployments, ensure that the primary and standby nodes sync up before proceeding further with next steps.

Related Topics

Step 4: Upgrade the Oracle Key Vault Primary-Standby Pair

You can upgrade a pair of Oracle Key Vault servers in a primary-standby deployment.

About Upgrading an Oracle Key Vault Server Primary-Standby Pair

In a primary-standby deployment you must upgrade both primary and standby Oracle Key Vault servers.

Note that persistent caching enables endpoints to continue to be operational during the upgrade process.

Note: If you are upgrading from a system with 4 GB RAM, first add an additional 12 GB memory to the system before upgrading.

Related Topics

Upgrading a Pair of Primary-Standby Oracle Key Vault Servers

You should allocate several hours to upgrade the primary server after upgrading the standby.

You must perform the upgrade of standby and primary servers in one session with as little time between the standby and primary upgrade. The upgrade time is approximate and a function of the volume of data stored and managed by Oracle Key Vault. For large volumes of data, the upgrade time may be longer than several hours.

  1. For both primary and standby servers in the primary-standby configuration, prepare for upgrade.

    • Ensure that both the primary and standby systems have at least 16 GB memory.

    • Add disk space to extend the vg_root.

    • While the upgrade is in progress, do not change any settings or perform any other operations that are not part of the upgrade instructions below.

    • Upgrade the Oracle Key Vault server during a planned maintenance window because the upgrade process requires the endpoints to be shut down during the upgrade, if no persistent cache has been configured. With persistent cache enabled, endpoints will continue to be operational during the upgrade process.

  2. Ensure that you have backed up the server you are upgrading so your data is safe and recoverable.

    Ensure that in the time between the backup and shutting down the Oracle Key Vault servers for upgrade, that no databases perform a set or rekey operation (for example, using the ADMINISTER KEY MANAGEMENT statement), since these new keys will not be included in the backup. Do not proceed without completing this step.

  3. First, upgrade the standby server while the primary server is running.

    1. Log into the Oracle Key Vault management console as a user who has the System Administrator role.

    2. Ensure that SSH access is enabled.

    3. Ensure you have enough space in the destination directory for the upgrade ISO files.

    4. Log in to the Oracle Key Vault server through SSH as user support, then switch user su to root.

      ssh support@okv_server_IP_address
su - root

      If the SSH connection times out while you are executing any step of the upgrade, then the operation will not complete successfully. Oracle recommends that you ensure that you use the appropriate values for the ServerAliveInterval and ServerAliveCountMax options for your SSH sessions to avoid upgrade failures.

      Using the tmux command prevents network disconnections interrupting the upgrade. If the session terminates, resume as follows:

      tmux a

    5. Copy the upgrade ISO file to the destination directory using Secure Copy Protocol or other secure transmission method.

      Note that the upgrade ISO file is not the installation ISO file that you downloaded from eDelivery. You can download the Oracle Key Vault upgrade software from the My Oracle Support website at https://support.oracle.com/portal/.

      scp remote_host:remote_path/okv-upgrade-disc-new_software_release.iso /var/lib/oracle

      In this specification:

      • remote_host is the IP address of the computer containing the ISO upgrade file.

      • remote_path is the directory of the ISO upgrade file. Do not copy this file to any location other than the /var/lib/oracle directory.

    6. Make the upgrade accessible by using the mount command:

      /bin/mount -o loop,ro /var/lib/oracle/okv-upgrade-disc-new_software_release.iso /images

    7. Clear the cache using the clean all command:

      yum -c /images/upgrade.repo clean all

    8. Apply the upgrade with the upgrade.rb command:

      ruby /images/upgrade.rb --confirm

      If the system is successfully upgraded, then the command will display the following message:

      Reboot now to continue the upgrade process.

      If you see an error message, then check the log file /var/log/messages for additional information.

      If the upgrade of the Oracle Key Vault system fails with the following message:

      Failed to apply update: The Oracle Key Vault upgrade has detected issues with FIPS mode. Please consult the Oracle Key Vault upgrade documentation or contact Oracle Support.

      Perform the following steps:

      1. Log in to the Oracle Key Vault server through SSH as user support, then switch user su to root.

        ssh support@<Oracle_Key_Vault_IP_address>
su - root

      2. Run the following command:

        /images/preupgrade/okv_check_fips_status_utility fix_fips_mode_consistency

      3. Follow the instructions displayed in the output and reboot the system when prompted.

      4. After the system has successfully rebooted, SSH into the system again. As user root, mount the upgrade ISO and run the following command to verify that there is no FIPS mode inconsistency on the system:

        /images/preupgrade/okv_check_fips_status_utility check_for_fips_mode_consistency

        The return value 0 indicates that there is no more FIPS inconsistency.

        The return value 1 indicates that there is FIPS mode inconsistency. Run the following command to correct it:

        /images/preupgrade/okv_check_fips_status_utility fix_fips_mode_consistency

    9. Restart the Oracle Key Vault server by running the reboot command:

      reboot

      On the first restart of the computer after the upgrade, the system will apply the necessary changes. This can take a few hours. Do not shut down the system during this time.

      The upgrade is completed when the screen with heading: Oracle Key Vault Server new_software_release appears. The revision should reflect the upgraded release.

  4. Ensure that the upgraded standby Oracle Key Vault server is restarted and running.

  5. Upgrade the primary Oracle Key Vault server following same steps that you followed for the standby server in Step 3.

    After both the standby and primary Oracle Key Vault servers are upgraded, the two servers will automatically synchronize.

  6. Log in to the Oracle Key Vault management console as a user with the System Administrator role.

  7. Select the System tab, and then Status.

  8. Verify that the Version field displays the new software version.

  9. If your site uses the Commercial National Security Algorithm (CNSA) suite, then re-install these algrorithms onto the primary and standby servers.

Related Topics

Step 5: If Necessary, Add Disk Space to Extend Swap Space

If necessary, extend the swap space on both the primary and standby servers.

Oracle Key Vault release 21.16 requires a hard disk size greater than or equal to 1 TB in size with approximately 64 GB of swap space. If your system does not meet this requirement, follow these instructions to extend the swap space. You can check how much swap space you have by running the swapon -s command. By default, Oracle Key Vault releases earlier than release 18.1 were installed with approximately 4 GB of swap space. After you complete the upgrade to release 18.1 or later, Oracle recommends that you increase the swap space allocation for the server on which you upgraded Oracle Key Vault. A new Oracle Key Vault installation is automatically configured with sufficient swap space. However, if you upgraded from a previous release, and your system does not have the desired amount of swap space configured, then you must manually add disk space to extend the swap space, particularly if the intention is to convert the upgraded server into the first node of a multi-master cluster.

  1. Log in to the server in which you upgraded Oracle Key Vault and connect as root.

  2. Check the current amount of swap space.

    swapon -s

    Output similar to the following appears. This example shows that the system has 4 GB of swap space.

    Filename Type Size Used Priority
/dev/dm-0 partition 4194300 3368 -1

    There must be 64 GB of swap space if the disk is greater than 1 TB in size.

  3. Run the vgs command to determine how much free space is available.

    vgs

    The VFree column shows how much free space you have (for example, 21 GB).

  4. Power off the server in order to add a new disk.

    /sbin/shutdown -h now

  5. Add a new disk to the server of a size that will bring the VFree value to over 64 GB.

  6. Start the server.

  7. Log in to the Oracle Key Vault server through SSH as user support, then switch user su to root.

    ssh support@okv_server_IP_address
su - root

  8. Run the fdisk -l command to find if there are any available partitions on the new disk.

    fdisk -l

    At this stage, there should be no available partitions.

  9. Run the fdisk disk_device_to_be_added command to create the new partition.

    For example, to create a disk device named /dev/sdc:

    fdisk /dev/sdc

    In the prompts that appear, enter the following commands in sequence:

    • n for new partition

    • p for primary (for primary partition)

    • 1 for partition number

    • Accept the default values for cylinder (press Enter twice).

    • w to write and exit

  10. Use the pvcreate disk_device_partition command to add the newly added disk to the physical volume.

    For example, for a disk device named /dev/sdc1, which is the name of the disk partition that you created (based on the name used for the disk device that was added).

    pvcreate /dev/sdc1

    Output similar to the following appears:

    Physical volume "/dev/sdc1" successfully created

  11. Use the vgextend vg_root disk_device_partition command to extend the logical volume with this disk space that you just added.

    For example, for the partition /dev/sdc1, you would run:

    vgextend vg_root /dev/sdc1

    Output similar to the following appears:

    Volume group "vg_root" successfully extended

  12. Run the vgs command again to ensure that VFree shows an increase of 64 GB.

    vgs

  13. Disable swapping.

    swapoff -v /dev/vg_root/lv_swap

  14. To extend the swap space, run the lvresize command.

    lvresize -L +60G /dev/vg_root/lv_swap

    Output similar to the following appears:

    Size of logical volume vg_root/lv_swap changed from 4.00 GiB (128 extents) to 64.00 GiB (2048 extents)
Logical volume lv_swap successfully resized.

  15. Format the newly added swap space.

    mkswap /dev/vg_root/lv_swap

    Output similar to the following appears:

    mkswap: /dev/vg_root/lv_swap: warning: don't erase bootbits sectors
on whole disk. Use -f to force.
Setting up swapspace version 1, size = 67108860 KiB
no label, UUID=fea7fc72-0fea-43a3-8e5d-e29955d46891

  16. Enable swapping again.

    swapon -v /dev/vg_root/lv_swap

  17. Verify the amount of swap space that is available.

    swapon -s

    Output similar to the following appears:

    Filename Type Size Used Priority
/dev/dm-0 partition 67108860 0 -1

  18. Restart the Oracle Key Vault server.

    /sbin/reboot

    For primary-standby deployments, ensure that the primary and standby nodes sync up before proceeding further with next steps.

Step 6: If Necessary, Remove Old Kernels

Oracle recommends that for both the primary and standby servers, you clean up the older kernels that were left behind after the upgrade.

While the older kernel is not in use, it may be marked as an issue by some code analysis tools.

  1. Log in to the Oracle Key Vault server as the support user.

  2. Switch to the root user.

    su - root

  3. Mount /boot if it was not mounted on the system.

    1. Check if the /boot is mounted. The following command should display /boot information if it was mounted.

      df -h /boot;

    2. Mount it if /boot is not mounted.

      /bin/mount /boot;

      For EFI-based systems, you may need to mount /boot/efi if it is not already mounted.

      /bin/mount /boot/efi

  4. Check the installed kernels and the running kernel.

    1. Search for any kernels that are installed.

      rpm -q kernel-uek | sort;

      The following example output shows that two kernels are installed:

      kernel-uek-4.1.12-103.9.4.el6uek.x86_64
kernel-uek-4.1.12-112.16.7.el6uek.x86_64

    2. Check the latest kernel.

      uname -r;

      The following output shows an example of a kernel version that was installed at the time:

      4.1.12-112.16.7.el6uek.x86_64

      This example assumes that 4.1.12-112.16.7.el6uek.x86_64 is the latest version, but newer versions may be available by now. Based on this output, you will need to remove the kernel-uek-4.1.12-103.9.4.el6uek.x86_64 kernel. You should remove all kernels that are older than the latest kernel.

  5. Remove the older kernel and its associated RPMs.

    For example, to remove the kernel-uek-4.1.12-103.9.4.el6uek.x86_64 kernel:

    yum --disablerepo=* remove `rpm -qa | grep 4.1.12-103.9.4.el6uek`;

    Output similar to the following appears:

    Loaded plugins: security
Setting up Remove Process
Resolving Dependencies

--> Running transaction check

---> Package kernel-uek.x86_64 0:4.1.12-103.9.4.el6uek will be erased

---> Package kernel-uek-devel.x86_64 0:4.1.12-103.9.4.el6uek will be erased

---> Package kernel-uek-firmware.noarch 0:4.1.12-103.9.4.el6uek will be erased

--> Finished Dependency Resolution

Dependencies Resolved

=================================================================================================================
Package               Arch    Version                Repository                                            Size
=================================================================================================================
Removing:
kernel-uek            x86_64  4.1.12-103.9.4.el6uek  @anaconda-OracleLinuxServer-201410181705.x86_64/6.6  241 M
kernel-uek-devel      x86_64  4.1.12-103.9.4.el6uek  @anaconda-OracleLinuxServer-201410181705.x86_64/6.6   38 M
kernel-uek-firmware   noarch  4.1.12-103.9.4.el6uek  @anaconda-OracleLinuxServer-201410181705.x86_64/6.6  2.9 M

Transaction Summary
=================================================================================================================
Remove        3 Package(s)

Installed size: 282 M
Is this ok [y/N]:

  6. Enter y to accept the deletion output.

  7. Repeat these steps starting with Step 4 for all kernels that are older than the latest kernel.

Step 7: If Necessary, Remove SSH-Related DSA Keys

For both the primary and standby servers, you should remove SSH-related DSA keys left behind after the upgrade, because they can cause problems with some code analysis tools.

  1. Log in to the Oracle Key Vault management console as a user with the System Administrator role.

  2. Enable SSH.

    Log in to the Oracle Key Vault management console as a user who has the System Administrator role. Select the System tab, then Settings. In the Network Details area, click SSH Access. Select IP address(es) and then enter only the IP addresses that you need, or select All. Click Save.

  3. Log in to the Oracle Key Vault support account using SSH as the support user and then switch to the root user.

    ssh support@OracleKeyVault_serverIPaddress
    su - root

  4. Change directory to /etc/ssh.

    cd /etc/ssh

  5. Rename the following keys.

    mv ssh_host_dsa_key.pub ssh_host_dsa_key.pub.retire
mv ssh_host_dsa_key ssh_host_dsa_key.retire

  6. Disable SSH access.

    Log in to the Oracle Key Vault management console as a user who has the System Administrator role. Select the System tab, then Settings. In the Network Details area, click SSH Access. Select Disabled. Click Save.

Step 8: Upgrade the Endpoint Software

When you upgrade the Oracle Key Vault server software appliance, also upgrade the endpoint software to get access to the latest enhancements.

Oracle Key Vault client software is backward-compatible. While older versions of Oracle Key Vault client software are fully functional with an upgraded Oracle Key Vault server, some new Oracle Key Vault features are only available with the current client software.

You can upgrade an endpoint by upgrading the endpoint software or re-enrolling the endpoint. Upgrading the endpoint software does not affect the existing endpoint certificate or okvclient.ora, the endpoint configuration file. Re-enrolling an endpoint invalidates an existing endpoint certificate, and a new endpoint certificate as well as okvclient.ora are installed. Oracle recommends that you upgrade the endpoint software for minor version upgrades, and consider re-enrolling the endpoint when upgrading across major versions.

Before an endpoint that uses Oracle Key Vault for TDE key management can take advantage of new Oracle Key Vault features, for example non-extractable TDE master keys, it must be upgraded to match the new Oracle Key Vault release.

For more information and detailed steps to upgrade an endpoint, see Upgrading Oracle Key Vault Endpoints.

Related Topics

Step 9: Back Up the Upgraded Oracle Key Vault Server

You must perform server backup and user password tasks after completing a successful upgrade.

  1. Take a full backup of the upgraded Oracle Key Vault Server Database to a new remote destination. Avoid using the old backup destination for the new backups.

  2. Schedule a new periodic incremental backup to the new destination defined in the preceding step.

  3. Change the Oracle Key Vault administrative passwords.

    Password hashing has been upgraded to a more secure standard than in earlier releases. This change affects the operating system passwords, support and root. You must change Oracle Key Vault administrative passwords after the upgrade to take advantage of the more secure hash.