ORACLE EBSR12.2.4
SYMPTOMS
You are attempting to run the Subledger Period Close Exception Report (XLAPEXRPT) and the report shows xml data only.
It is not properly formatted.
Associated logfile shows the following:
---------------------- 1) PUBLISH ----------------
Unable to find an output post processor service to post-process request 45999573
Check that the output post processor service is running
This can happen with other reports besides the one listed above.
CAUSE
The OPP processor did not close down properly and needed to be restarted.
SOLUTION
Bounce OPP processor.
Terminate then restart the OPP Output Post Processor. The following steps were taken from Note 352370.1:
Responsibility: System Administrator
Navigation: Concurrent > Manager > Administer
Query for Name = Output Post Processor
Click button Restart
Click button Refresh, the "Actual" and "Target" values should show "1"
or
Output Post Processor is Down with Actual Process is 0 And Target Process is 1
Go to System Admin>From OAM Dashboard >>CM status> Output Post Processor> select Abort option and clock on GO.
After Abort again select start.
check Output Post Processor actual value & Target Value.
Actual Process is 1 And Target Process is 1.
Issue resolved.
or
- FNDSVC should exist under FND_TOP/bin
- Bring down all application services and relink the FNDSVC through adadmin or using the below command:
adrelink.sh force=y ranlib=y "FND FNDSVC"
- Restart all applications services and retest the issue.
or
Output Post Processor is Down with Actual Process is 0 And Target Process is 1
1. Shutdown Concurrent Managers
2. To ensure concurrent manager down; check there is no FNDLIBR process running.
ps -ef | grep FNDLIBR
3. Run adadmin to relink FNDSVC executable.
a. Invoke adadmin from command prompt
b. Choose option 2 (2. Maintain Applications Files menu)
c. Choose option 1 (1. Relink Applications programs )
d. Then type FND When prompted; ( Enter list of products to link (all for all products) [all] : FND
)1
e. Ensure adrelink is exiting with status 0
4. Start Concurrent Managers
5. Check the Output Post Processor
SYMPTOMS
You are attempting to run the Subledger Period Close Exception Report (XLAPEXRPT) and the report shows xml data only.
It is not properly formatted.
Associated logfile shows the following:
---------------------- 1) PUBLISH ----------------
Unable to find an output post processor service to post-process request 45999573
Check that the output post processor service is running
This can happen with other reports besides the one listed above.
CAUSE
The OPP processor did not close down properly and needed to be restarted.
SOLUTION
Bounce OPP processor.
Terminate then restart the OPP Output Post Processor. The following steps were taken from Note 352370.1:
Responsibility: System Administrator
Navigation: Concurrent > Manager > Administer
Query for Name = Output Post Processor
Click button Restart
Click button Refresh, the "Actual" and "Target" values should show "1"
or
Output Post Processor is Down with Actual Process is 0 And Target Process is 1
Go to System Admin>From OAM Dashboard >>CM status> Output Post Processor> select Abort option and clock on GO.
After Abort again select start.
check Output Post Processor actual value & Target Value.
Actual Process is 1 And Target Process is 1.
Issue resolved.
or
- FNDSVC should exist under FND_TOP/bin
- Bring down all application services and relink the FNDSVC through adadmin or using the below command:
adrelink.sh force=y ranlib=y "FND FNDSVC"
- Restart all applications services and retest the issue.
or
Output Post Processor is Down with Actual Process is 0 And Target Process is 1
1. Shutdown Concurrent Managers
2. To ensure concurrent manager down; check there is no FNDLIBR process running.
ps -ef | grep FNDLIBR
3. Run adadmin to relink FNDSVC executable.
a. Invoke adadmin from command prompt
b. Choose option 2 (2. Maintain Applications Files menu)
c. Choose option 1 (1. Relink Applications programs )
d. Then type FND When prompted; ( Enter list of products to link (all for all products) [all] : FND
)1
e. Ensure adrelink is exiting with status 0
4. Start Concurrent Managers
5. Check the Output Post Processor
No comments:
Post a Comment