Table of Contents
- TROUBLESHOOTING SECTION
- Oracle HTTP Server Logs:
- J2ee Application Logs:
- OPMN Logs:
- Oracle or Windward Reports – Red Bar
- Problem
- Solution
- Oracle Instance Fails to Start After Configuration Changes
- Problem
- Solution
- Unable to view report after running it.
- Problem:
- Solution:
- Unable to write or read from extract or load folder.
TROUBLESHOOTING SECTION #
Wiki Professional and Self-Service utilizes various components of the Oracle Application Server. Therefore, it is important to know where the logs files are stored for each component before proceeding any further.Oracle HTTP Server Logs: #
- AS10G_RL3\Apache\Apache\logs\
- AS1G_BI\Apache\Apache\logs \
J2ee Application Logs: #
- AS10G_RL3\j2ee\instance-name\applicaton-deployments\application-name\instance-name_default_group_1\
- AS10G_BI\j2ee\OC4J_BI_Forms\application-deployments\discoverer|reports\OC4J_BI_Forms_default_island_1
OPMN Logs: #
- AS10G_RL3\opmn\logs\
- AS10G_BI\opmn\logs\
Oracle or Windward Reports – Red Bar #
Problem #
There is an attempt to run a report in Wiki and a red bar is automatically encountered, indicating the report has failed.Solution #
- Review your IMST preferences by ensuring all reports preferences are correct. See step 6: configuring IMST preferences. Configure IMST Preferences
- Review the OPMN logs for any errors with the MEX ID of the report that failed. If you are unable to determine the cause the problem from the logs, please upload the logs to support for review.
Oracle Instance Fails to Start After Configuration Changes#
(For example, RMI port change)Problem #
A configuration change such as changing the OC4J instance port prevents it from starting up due to port conflict.Solution #
Ensure all the OC4J containers are configured with a static port. From a command prompt, run the below command from the following directory: AS10G_RL3|AS10G_BI/binopmnctl status –fmt %prt%por
- Make a note of the RMI ports assigned to each OC4J container and update the OPMN.XML file by assigning a free port to the OC4J instance that failed to start.
- Reload and start the container.