Posts Tagged ‘Oracle EBS Application’

Oracle EBS Application [UNEXPECTED]

September 4th, 2022, posted in Oracle EBS Application

The concurrent program the output of which is XML report is failing in warning and the log shows the below message:
Beginning post-processing of request 5292785 on node AP6105RT at 02-AUG-2006 04:47:48. Post-processing of request 5292785 failed at 02-AUG-2006 04:49:48 with the error message:

The Output Post-processor is running but has not picked up this request. No further attempts will be made to post-process this request, and the request will be marked with Warning status.
Setting the profile option Concurrent: OPP Response Timeout to a higher value may be necessary. Example if the response time is set to 60 make it at-least 180. Bounce the concurrent manager once this is done. This will resolve the issue.

If the issue still persist, check the OPP log file. You follow below navigation

System Administrator -> Concurrent : Manager -> Administrator

On this screen click on Output Post Processor and then click on Processes button -> Manager Log button


Error : 


[11/10/19 10:27:07 AM] [OPPServiceThread1] Post-processing request 16359131.
[11/10/19 10:27:07 AM] [820550:RT16359131] Executing post-processing actions for request 16359131.
[11/10/19 10:27:07 AM] [820550:RT16359131] Starting XML Publisher post-processing action.
[11/10/19 10:27:07 AM] [820550:RT16359131] 
Template code: XXSD_RDF_TO_XML_PROC
Template app:  AR
Language:      en
Territory:     00
Output type:   EXCEL
[11/10/19 10:27:07 AM] [UNEXPECTED] [820550:RT16359131]
        /usr/tmp/xml/ (No such file or directory)
	at Method)
	at oracle.apps.xdo.common.tmp.TmpFile.createTmpFileJDK118(
	at oracle.apps.xdo.common.tmp.TmpFile.createTmpFile(
	at oracle.apps.xdo.template.FOProcessor.createFO(
	at oracle.apps.xdo.template.FOProcessor.generate(
	at oracle.apps.xdo.oa.schema.server.TemplateHelper.runProcessTemplate(
	at oracle.apps.xdo.oa.schema.server.TemplateHelper.processTemplate(
	at oracle.apps.xdo.oa.schema.server.TemplateHelper.processTemplate(
	at oracle.apps.fnd.cp.opp.XMLPublisherProcessor.process(

[11/10/19 10:27:07 AM] [820550:RT16359131] Completed post-processing actions for request 16359131.


Cause :

The Temporary directory for XML Publisher has not been modified after making the clone so it was pointing to non existing location and getting error out.


Issue :

Issue was with XML Publisher temporary directory path.


Solution :

1. Create a new Temporary Directory on OS level for the cloned environment.
2. Make sure that the application owner (APPLMGR) has Read and Write permission this directory.
3. Setup this new directory for XML Publisher via :
XML Publisher Administrator responsibility: Properties -> General -> Temporary Directory.

3. Restart the Server.
4. Test again with a XML Publisher Report.



June 13th, 2020, posted in Oracle


Features on this R12 INST_TOP

-All the logs files have been moved from APPL_TOP,ORACLE_HOME to this to top

  • All configuration files have been moved to INST_TOP
    DBc file
    All the http related config files
    All the start or stop scripts
    all the OC4J related config files

-we can now share the Apps and technology stack among multiple nodes and even instances (Dev,Test, Production) as all the log and config are located in this top.We will have INST_TOP for each context.

-Configuration and log files are co-located

-Easier collection of instance state
-Minimize disk usage and maximize performance

Filesystem look

/inst/apps/ ($INST_TOP)
/scripts ($ADMIN_SCRIPTS_HOME) All the start and stop are here
/appl ($APPL_CONFIG_HOME) All the apps env are here
/fnd/12.0.0/secure ($FND_SECURE) dbc file lis located here
/logs ($LOG_HOME) all the logs are located
/10.1.3 ($ORACLE_CONFIG_HOME) all the techstack(oacore,forms) related config files

Some more changes to variable

OA_HTML =$COMMON_TOP/webapps/oacore/html

Advantage  of INST_TOP

-Clear distinction between the shared file system and the file system unique to an instance
-Ability to share code (Apps, technology stack) among multiple  nodes and even instances (Development ,Test, Production)
-Enables split ownership of applications and technology stack file systems
-Improves code safety by making shared file system read-only while not patching
-Configuration and log files are co-located
-Easier collection of instance state
-Ability to use network or local storage for various file system portions
-Minimize disk usage and maximize performance

R12.2 Changes

-R12.2 contains the Fusion Middleware 11g tech-stack. The logfile and configuration files is located in that Oracle Home

Concurrent Manager log/out files have been moved in Non editioned File system

Where to Put INST_TOP in shared file system

It is recommended to put INST_TOP on local filesystem  in shared APPL_TOP filesystem  architecture. This is because of the Apache mutex problem.Apache performance is highly sensitive to mutex file access latency, and at higher loads is also sensitive to I/Os per second. In case you have INST_TOP on shared filesystem, it is suggested to point these context variable to local file-system





Hope you like the post on R12 INST_TOP, all the advantages and R12.2 changes.  Please do provide the feedback.