Probable Cause

Oracle Key Vault Installation may fail due to various reasons listed with solutions in the Solutions section.

Solution

1. Check if the physical server has RAID enabled software.

   Note:

   Oracle Key Vault does not support the use of Software RAID. Ensure that RAID is configured only at the hardware level.
2. On the Oracle Key Vault server, check the network settings. Also check if there is a delay in copying the iso files from the NFS location to the disk.
3. Check system configuration including disk size, number of disks, disk configuration, RAM size, and number of CPU cores. Ensure that the server meets the minimum system configuration requirements of Oracle Key Vault.
4. Verify if the checksum matches with the local iso file.
   1. Copy the checksum of the iso from the specific location where you downloaded the iso file.
   2. Generate the checksum for the downloaded iso file.
   3. Both the checksum values should be the same. If not, download the correct iso file.

      sha256sum isoname.iso

   4. Check if the issue is resolved.

Probable Cause 1

Oracle Key Vault upgrade version is not supported.

Solution

Verify that the Oracle Key Vault upgrade from the current release to the version you want to upgrade is supported. See, Release Notes of specific Oracle Key Vault release for supported upgrade paths.

Probable Cause 2

Oracle Key Vault certificates have expired.

Solution

1. Check if the Oracle Key Vault server or node certificates have expired.
   1. Log in to the Oracle Key Vault management console as a user who has the system administrator role.
   2. To check the server or node certificate expiration status, go to System, Status and check the Server or Node Certificate Expiration Date.
   3. Regenerate the server certificate if it has expired. Go to System, Status.
   4. Click Service Certificates and select Manage Server or Node Certificate to regenerate the new server certificate.
2. Check if the Oracle Key Vault CA certificate has expired.
   1. Log in to the Oracle Key Vault management console as a system administrator.
   2. To check the CA certificate expiration status, navigate to System, Status and check the CA Certificate Expiration Date.
   3. If the CA certificate has expired, contact Oracle support.
3. Verify if all the pre-upgrade steps are performed as described in the Oracle Key Vault Installation and Upgrade guide.

   Note:

   For Oracle Key Vault 21.5 or higher, see the steps listed inManaging CA Certificate Rotation after it has expired, to rotate the expired CA certificate.

Considerations for Multi-Master Cluster Deployment

1. Log in to each node's management console, and check if the replication lag or heartbeat lag is high in other nodes. If yes, then resolve this issue first. See,Heartbeat Lag or High Replication Lag in Multi-Master Cluster Environment.
2. Based on the upgrade scenario, certain restrictions may apply when upgrading nodes of a read-write pair. This includes the order in which the nodes are disabled, upgraded, and then re-enabled after the upgrade. See, Oracle Key Vault Installation and Upgrade guide of the target version for specific instructions.
3. Verify if the node is not disabled beyond the maximum node disabled duration limit.

Considerations for Primary-Standby Environment

1. Verify if the upgrade is performed first on standby and then on the primary. See,Upgrading a Pair of Primary-Standby Oracle Key Vault Servers .
2. Retry the upgrade. If the issue persists, contact Oracle Support.

Example

On the Oracle Key Vault server, the /var/log/messages shows the error,

OAV-46501: invalid IP Address.
java.sql.SQLException: OAV-46501: invalid IP Address.

Probable Cause

The HTTPd server daemon on the Oracle Key Vault server is not started. Oracle Key Vault faced issues in identifying the network adapter on VMware.

Example

Oracle Key Vault upgrade fails with,

Open FDs on: Volume: lv_tmp, Process: sshd

Probable Cause

This error is due to a running SSH process.

Solution

1. Verify if any SSH process is running on the Oracle Key Vault server:

   $ ps -eaf | grep -i "ssh"

2. Stop the running SSH process and retry the upgrade.

Example

After reboot, the following error message appears on VM console.

PXE-M0F: Exiting Intel PXE ROM
         Operating system not Found

Probable Cause

The virtual disk is set to 2 TB and is not allowing the server to boot.

Solution

1. Set the virtual disc size to 1.9 TB.
2. In vSphere 5.5.x and 6.0.x, large capacity virtual disks have these conditions and limitations:
   • The maximum supported VMDK size on an VMFS-5 data store is increased to 62 TB. However, the maximum supported VMDK size on VMFS-3 is still 2 TB.
   • The maximum supported size of a VMDK on NFS is the lesser of 62 TB and 1% less than the maximum file size supported by the NFS filesystem.