D Troubleshooting

This appendix provides troubleshooting information.

This appendix includes the following sections:

D.1 General Troubleshooting Tips

If you encounter an error during installation:

D.2 Suite Installation and Configuration Troubleshooting

This section contains solutions to common problems that you might encounter while installing and configuring Oracle Enterprise Content Management Suite.

D.2.1 Oracle Fusion Middleware Installation and Configuration Log Files

The Oracle Fusion Middleware installer and Fusion Middleware Configuration Wizard create their own sets of log files.

  • On a UNIX operating system, the installer writes the following log files:

    • oraInventory_location/logs/installActionstimestamp.log

    • oraInventory_location/logs/oraInstalltimestamp.err

    • oraInventory_location/logs/oraInstalltimestamp.out

    • ORACLE_HOME/install/make.log

  • On a Windows operating system, the installer writes the following log files:

    • inventory_location\logs\installActionstimestamp.log

    • inventory_location\logs\oraInstalltimestamp.err

    • inventory_location\logs\oraInstalltimestamp.out

    The default inventory_location value follows:

  • Fusion Middleware Configuration Wizard writes log files in the ORACLE_HOME/cfgtoollogs directory (UNIX system) or the ORACLE_HOME\cfgtoollogs directory (Windows system).

If you want to access the log files created by the installer, you need to exit it first. The log files are inaccessible if the installer is still in use.

D.2.2 Oracle IRM Key Store Configuration Issues

If the Oracle Information Rights Management (Oracle IRM) key store has not been configured correctly, then issues will occur during creation of a context. If you cannot create a context, check the server log for one of the following errors.

  • Missing key store file

    If the key store does not exist, you will see a FileNotFoundException message in the log:

    java.io.FileNotFoundException: C:\IRM\oracle\middleware\user_projects
    \domains\base_domain\config\fmwconfig\irm.jceks (The system cannot find the file specified)
  • Missing key

    If the key store exists, but the keys are missing, you will see an UnknownKeyException message in the log:

    The key oracle.irm.wrap does not exist in the key store 
  • Missing password

    If the password is missing or incorrect you will see the following exception in the log:

    java.security.UnrecoverableKeyException: Given final block not properly padded

D.3 Additional Help

If this appendix does not solve the problem you encountered, try these other sources:

If you do not find a solution for your problem, open a service request.