KeyStore File Missing: xl.keystore
(Doc ID 763614.1)
Last updated on SEPTEMBER 19, 2019
Applies to:Identity Manager - Version 22.214.171.124 to 126.96.36.199.0 [Release 10gR2]
Information in this document applies to any platform.
***Checked for relevance on 28-Sep-2012***
After applying some patch and manual edits of the xlconfig.xml file on the Oracle Identity Manager (OIM) server, for example after upgrading from version 188.8.131.52 (1705.0), via <Patch 7264480>, errors are seen indicating a missing xl.keystore file.
Below is an example of seeing the error after performing an OIM Server upgrade from 184.108.40.206 to 220.127.116.11. When running the dataUpgrade -initialize PROCESS, the script encounters many of the same exceptions such as those below. Note that this can also happen during other upgrades such as from 9.0.x to 18.104.22.168 or similar and show up in the OIM logs also.
ERROR DEBUG,20 Jan 2009 11:27:42,015, [main], [com.oracle.xl.util.dataupgrade.SetEncryptionSizeUtil],Processing table :UD_SAPHR ERROR,20 Jan 2009 11:27:42,062, [main], [XELLERATE.ACCOUNTMANAGEMENT],Class/Method: tcCryptoHelper/loadKeyStore encounter some problems: Keystore fille is missing ERROR,20 Jan 2009 11:27:42,062, [main], [XELLERATE.ACCOUNTMANAGEMENT],Class/Method: tcDefaultDBEncryptionImpl/initKeyStore encounter some problems: KeyStore File : <OIM_HOME>\xellerate\config\xl.keystore missing. com.thortech.xl.crypto.tcCryptoException: KeyStore File : <OIM_HOME>\xellerate\config\xl.keystore missing. at com.thortech.xl.crypto.tcCryptoHelper.loadKeyStore(Unknown Source) at com.thortech.xl.crypto.tcDefaultDBEncryptionImpl.initKeyStore(Unknown Source) at com.thortech.xl.crypto.tcDefaultDBEncryptionImpl.getCipher(Unknown Source) at com.thortech.xl.crypto.tcDefaultDBEncryptionImpl.getEncryptedSize(Unknown Source) at com.oracle.xl.util.dataupgrade.AlterTableUtility.alterTablesForEncryptionColumnSizeOracle(Unknown Source) at com.oracle.xl.util.dataupgrade.AlterTableUtility.alterTablesForEncryptionColumnSize(Unknown Source) at com.oracle.xl.util.dataupgrade.SetEncryptionSizeUtil.setSizeforEncryptionFields(Unknown Source) at com.oracle.xl.util.dataupgrade.InitializeTablesUtil.initializeTables(Unknown Source) at com.oracle.xl.util.dataupgrade.PatchMain.main(Unknown Source)
The file as named there did not exist and was instead .xlkeystore but even copying this file to xl.keystore still results in errors. The keystore file contains key data as normal, plus there are no permissions issues as the upgrade script is run as the same user that owns the files.
There is a warning in the documentation for the patch as follows and because of this much time is spent restoring the database:
If the initialization of the process tables is interrupted or if it fails, then you must restore the database before you restart the initialization.
This can be caused by a corruption in the OIM Server's xlconfig.xml file, such as unbalanced tags or some other corruption such that the file cannot be parsed by the Java XML parser.
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