My Oracle Support Banner

IM Startup Fails - Could Not Retrieve The Encryption Key From Keystore Location: Null (Doc ID 1589436.1)

Last updated on DECEMBER 12, 2019

Applies to:

Oracle Knowledge - Version 8.5.1 and later
Information in this document applies to any platform.
The keystore is used to create and validate passwords. The password can only be validated by the keystore that created it. So an error can suggest a mismatch between password and the keystore. Or it is also possible that the keystore has been corrupted somehow or is not accessible. The corruption of the keystore is very rare but can happen. There are several ways to get a new keystore - install it, copy it from a working install in the same environment that should match the instance that is not working, or use the createkeystore script. If you have more than one keystore in this environment it is recommended to copy it, if you create a new one you have to update all the keystores and passwords in that environment. Each environment has to share one keystore. As the passwords from IM are used by search.
If you know the keystore is good and the same throughout the environment and a password is not decrypting then that password was not created by that keystore and you have to update it.

Symptoms

InfoManager fails to startup. Stack trace is similar to the following:

Case 1 -

 

Cause

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
Symptoms
Cause
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.