Database Error Messages

The database is unable to open the security module wallet due to an incorrect wallet path or password. It is also possible that a wallet has not been created. Ensure that the TDE_CONFIGURATION is set to "OKV|FILE" if an external keystore (OKV/KMS) is being used.

If the database is configured to use external keystore (OKV/KMS) as the TDE keystore, the database may be having difficulty finding the external configuration file of the keystore.

Execute the command again using the correct wallet password or verify that a wallet exists in the specified directory. If necessary, create a new wallet and initialize it.

When using external keystore (OKV/KMS), check if the configuration file is in the right directory. When the instance initialization parameter WALLET_ROOT is configured, the Oracle Key Vault configuration file should be located at one of the following paths:

$WALLET_ROOT/okv/conf (for CDB$ROOT and united PDBs) $WALLET_ROOT/PDB-GUID/okv/conf (for an isolated PDB)

The pluggable database (PDB) GUID can be obtained by querying GUID from the DBA_PDBS view.

Also in the case of an external keystore, refer to the documentation for information on endpoint enrollment and provisioning.

The database was unable to open the security module wallet due to an incorrect wallet path or password. It is also possible that a wallet had not been created. Type mkwallet from command line for instructions.

If the database is configured to use Oracle Key Vault as the TDE keystore, the database may be having difficulty finding the Oracle Key Vault configuration file.

If Oracle Key Vault is used as the keystore, check if the Oracle Key Vault configuration file is in the right directory. When the instance initialization parameter WALLET_ROOT is configured, Oracle Key Vault configuration file should be located at the following paths $WALLET_ROOT/okv/conf for CDB$ROOT and $WALLET_ROOT/PDB-GUID/okv/conf for a pluggable database (PDB) in isolated mode. The PDB GUID can be obtained by querying GUID from DBA_PDBS view. When WALLET_ROOT is not set, Oracle Key Vault configuration file should be under $OKV_HOME/conf.

Execute the command again using the correct wallet password or verfying that a wallet exists in the specified directory. If necessary, create a new wallet and initialize it.

When Oracle Key Vault is used, refer to the documentation for information on endpoint enrollment and provisioning.

The database was unable to open the security module wallet due to an incorrect wallet path or password. It is also possible that a wallet had not been created. Type mkwallet from command line for instructions.

If the database is configured to use Oracle Key Vault as the TDE keystore, the database may be having difficulty finding the Oracle Key Vault configuration file.

If Oracle Key Vault is used as the keystore, check if the Oracle Key Vault configuration file is in the right directory. When the instance initialization parameter WALLET_ROOT is configured, Oracle Key Vault configuration file should be located at the following paths $WALLET_ROOT/okv/conf for CDB$ROOT and $WALLET_ROOT/PDB-GUID/okv/conf for a pluggable database (PDB) in isolated mode. The PDB GUID can be obtained by querying GUID from DBA_PDBS view. When WALLET_ROOT is not set, Oracle Key Vault configuration file should be under $OKV_HOME/conf.

Execute the command again using the correct wallet password or verfying that a wallet exists in the specified directory. If necessary, create a new wallet and initialize it.

When Oracle Key Vault is used, refer to the documentation for information on endpoint enrollment and provisioning.