How To Reset Oracle Payments Encryption Wallet Location After Instance Clone? (Doc ID 1571608.1)

Last updated on MAY 23, 2024

Applies to:

Oracle Payables - Version 12.0.0 and later
Oracle Payments - Version 12.0.0 to 12.2.9 [Release 12.0 to 12.2]
Information in this document applies to any platform.

Goal

When creating a cloned instance, if the directory structure between source (production) and target (test) instances are not identical, payment processing will fail with exception such as:

java.io.IOException: Could not open wallet. java.io.FileNotFoundException:
<path>/cwallet.sso (No such file or directory).

This is because payments engine looks for the wallet file in the directory specified in iby_sys_security_options.SYS_KEY_FILE_LOCATION. Since this is pointing to directory in source instance which does not exists in target, Payments is unable to find the wallet file. To resolve this issue, wallet location in the target instance needs to be updated gracefully to point to a directory in target instance. Steps outlined below accomplish this objective.

Note: If you need to rotate encryption wallet and security key periodically as part of regular maintenance and/or pci compliance requirements, please refer to Note 1300956.1.

Solution

	To view full details, sign in with your My Oracle Support account.
	Don't have a My Oracle Support account? Click to get started!

In this Document

Goal

Solution

References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.

How To Reset Oracle Payments Encryption Wallet Location After Instance Clone? (Doc ID 1571608.1)

Applies to:

Goal

Solution

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!