Oracle Reports – Trouble Shooting

Oracle Reports – Trouble Shooting

1. Concurrent Request Logs:-

·         The first step of reports debugging should be to examine the log of concurrent

request.

2. Running from the operating system:-

·         If the problem is not resolved with log, then the report should be run through from the operating system.

·         Along with the standard report arguments, the report should be run along with the arguments passed by the concurrent manager.

·         If it is run successfully then the problem is with the environment from with the concurrent manager was started.

3. Using r25run in place of ar25run:-

·         For this debugging step, AOL provides a report $FND_TOP/ SRW/FNDNOEXT.rdf (Unix path name) which has no user exits.

·         If this step also fails, then the problem could be with Oracle Applications Installation.

4. Running the Print Environment Variable Values Report:-

·         The concurrent manager inherits  its environment variables from the shell from which it was started and then runs report using this environment.

·         This environment could be different from that a user sees logging in to the Applications because the concurrent manager may have been started by a different user with different environment settings.

·         Due to this difference, it is sometimes difficult to determine the cause of error in running reports.

·         To examine the values of few variables, prints environment variable values, Report to print out the variable as seen by the concurrent manager to see if is correct.

·         Very common and often problems such as a problem in compilation or the concurrent managers inability to locate a library happen due to incorrect REPORTS 60_PATH.

5. Emulate Concurrent Manager Environment:-

·         For UNIX plat forms, to assist in determining where the problem lies, Oracle Applications AOL ships a program called $ FND_TOP / Srw / ar60run.oc.

·         This program helps to emulate the concurrent manager environment when testing reports from the OS command line.

·         This program writes all the environment variables and arguments passed to it in a log file ar60run.log. (Located by default in the $FND_TOP / $APPLLOG directory).

·         Save the ar60run.oc source code to a file named ar60run.oc compile it and rename the executable as ar60run.(new).

·         Save $FND_TOP / bin / ar60run in to some other file and place the new ar60run into $FND_top / bin.

·         Compiling and relinking has been incorporated in to fnd.mk which will, by default build an executable $FND_TOP / bin /ar60rund, which can be renamed to ar60run (new).

·         Submit the report from concurrent manager and look at ar60run.log.

·         Then run the report from OS with the same arguments as shown by ar60run.log shows using old ar60run.