Get a Better Handle on Log File in Oracle EPM 11.1.2.3.x

EPM server administrators may have noticed that log files sizes have been growing lot faster in 11.1.2.3.x than in many of the recent releases. A lot of these log messages reference the JVM’s usage of the Oracle Wallet file. You’ll see messages like these:
OracleFileSSOWalletImpl.getWalletData: enter...
OracleFileSSOWalletImpl.getWalletData: System.getProperty(user.name)=DEMO$
OracleFileSSOWalletImpl.getWalletData: locking (shared) dummy sso file..
OracleFileSSOWalletImpl.getWalletData: locking (shared) sso file...
Oracle Wallet: wallet size 11061
OracleWallet: getSecretStore
OracleSecretStore: loading wallet from stream
OracleSSOKeyStoreImpl: engineLoad
OracleKeyStoreSpi: Loading wallet from stream
OracleKeyStoreSpi: Opening safe 0
OracleKeyStoreSpi: Opening safe 0
OracleKeyStoreSpi: found cert bag
OracleKeyStoreSpi: found cert bag
OracleKeyStoreSpi: found cert bag
OracleKeyStoreSpi: found cert bag
OracleKeyStoreSpi: found cert bag
OracleKeyStoreSpi: found cert bag
OracleKeyStoreSpi: found cert bag

While these messages might be helpful when trying to troubleshoot Oracle Wallet issues, we have seen that it’s extremely rare that there are issues with the wallet file. These messages become extraneous and simply clog up the log files. These messages are now getting logged (in 11.1.2.3.x) because Oracle added a new switch to their Windows service install scripts and their setCustomParams script (primarily used for Unix):  -Doracle.pki.debug=true. If you set this switch to false in the Window registry (and/or in the setCustomParams scripts) for each product, these messages will not get logged and the log files should stay manageable longer, without excessive growth.