SOFTWARE_INSTALLATION.TROUBLESHOOTING
Back to current versionRestore this version

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: #

J2ee Application Logs: #

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 #




Oracle instance fail 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/bin opmnctl 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


Unable to view report after running it. #

Problem: #

When a user runs a report and an output link is created to open the report, click the link does not open the report.

Solution: #

• Review your IMST preferences ATTACHMENTS_FLDR and ensure the path is correctly specified. The path is relative to the Oracle Application Server.


Unable to write or read from extract or load folder. #

Problem: When a user runs attempt to utilized the EXTRACT OR LOAD DATA