Month: May 2007

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 responce time is set to 60 make it atleast 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

A new web page will open showing the manager log. Come to the bottom, you might see followng error

[10/7/08 10:15:56 PM] [1900472:RT5709298] Completed post-processing actions
for request 5709298.
[10/7/08 10:20:07 PM] [OPPServiceThread1] Post-processing request 5709301.
[10/7/08 10:20:07 PM] [1900472:RT5709301] Executing post-processing actions
for request 5709301.
[10/7/08 10:20:07 PM] [1900472:RT5709301] Starting XML Publisher
post-processing action.
[10/7/08 10:20:07 PM] [1900472:RT5709301]
@ Template code: FAXSRPIM
Template app:  OFA
Language:      EN
Territory:     US
Output type:   PDF
[10/7/08 10:20:07 PM] [UNEXPECTED] [1900472:RT5709301]
java.io.FileNotFoundException:
/appslog/fin_top/utl/fintest/out/xdosCfJu5EHsa100708_1020071837.fo (No such
file or directory)
at java.io.FileOutputStream.open(Native Method)
at java.io.FileOutputStream.<init>(FileOutputStream.java:179)
at java.io.FileOutputStream.<init>(FileOutputStream.java:131)
@ at oracle.apps.xdo.common.tmp.TmpFile.createTmpFileJDK118(TmpFile.java:146)
@ at oracle.apps.xdo.common.tmp.TmpFile.createTmpFile(TmpFile.java:113)
at oracle.apps.xdo.template.fo.util.FOUtility.generateFO(FOUtility.java:987)
at oracle.apps.xdo.template.fo.util.FOUtility.generateFO(FOUtility.java:212)
at oracle.apps.xdo.template.FOProcessor.createFO(FOProcessor.java:1657)
at oracle.apps.xdo.template.FOProcessor.generate(FOProcessor.java:967)

So the path /appslog/fin_top/utl/fintest/out/ is not correct. As per the note ID 428855.1 changed the path to valid location

Navigate the following as the responsibility “XML Publisher Administrator”
Select Administration on the Personal Home Page
Under the Configuration tab select Properties and then General.
From there the Temporary directory will be displayed.

Changed the path to some thing that is existing physically.

After that bounce the output post processor. This should resolve the issue.

MWA Service management – Brief

MWA is mobile web application. Using this we can have our applicaiton on mobile. MWA service is used in E-Business suite is for running the applicaiton on mobile. There are very few parameters that needs to be configured for this and we can start MWA service to be used on our mobile.

If we see context file we have a parameter named s_mwastatus which has to be enabled in order to use this service.

(oa_service_status oa_var=”s_mwastatus”)enabled(/oa_service_status)

Other then this, there will be a MWA port on which the service can be started. For ports we have two configuration, one is the telnetl port where we can start the service. If we have multiple telnet ports then we can have a dispatcher port which can load balance the telnet ports.

You can find the telnet port entry in context file as given below.

(mwaTelnetPortNo oa_var=”s_mwaTelnetPortNo” oa_type=”DUP_PORT” base=”10200 step=”6 range=”6 increment=”2 separator=”,” showall=”true” label=”MCSA Telnet Server Port”)10290,10292,10294(/mwaTelnetPortNo)

In E-Business suit we have the configuration file for MWA located at below path

$INST_TOP/admin/install/mwa.cfg

The important configuration setting in thie configuration file is as give below.

DBC file path
mwa.DbcFolder=(Path to $FND_SECURE)

telnet port
mwa.TelnetPortNumber=10290,10292,10294

Dispatcher port
mwa.Dispatcher=ap6003rems.us.oracle.com:10845

Log directory path
mwa.logdir= (Log dir path)

Log file name
mwa.SystemLog=system.log
The above parameters are self explainatory. Also some explaination is provided in config file.

You can use any port which is greated then 1024 and that is not used by any other service and you can start your service on that port. But make sure you make the same port entry in context file and mwa.cfg, else when autoconfig runs it will update mwa.cfg with the port number form context file and your service may not run.

You can start the services by going to $INST_TOP/admin/scripts and running following command

For Telnet port: mwactl.sh start (port number) &

For Dispatcher port: mwactl.sh start (port number) &

MWA URL will be
telnet http://(server name):(telnet port)
telnet http://(server name):(dispatcher port)

Example: telnet://ap6003rems.us.oracle.com:10845

You can use either telnet port or dispatcher port to log into the application. if dispatcher port is used, it will do load balancing.

Some times when we make a concurrent request and try to view the log file after complition of request (may be completed normal or some error) from the concurrent manager form we get following type of error

An error occurred while attempting to establish an Applications File Server connection with the node FNDFS_(Your env_name)_(Your_Server_name). There may be a network configuration problem, or the TNS listener on node FNDFS_(Your env_name)_(Your_Server_name) may not be running. Please contact your system administrator.

In this case you need to set one profile which will fix this issue. You need to set the value for RRA: Service Prefix to FNDFS_(Your_Env_name)_.

This can be done using navigation Profiles –> system.

If the concurrent manager is not responding and there are lot of pending request from long time then those request can be killed from the backend using the following query.

UPDATE fnd_concurrent_requests
SET phase_code = ‘C’, status_code = ‘D’
WHERE status_code =’Q’ OR phase_code = ‘P’
AND REQUEST_ID = ;

You can kill all the long running requests.
Also one more option that can be done is login as apps/apps. Also we can make the internal manager to work like a CRM by setting the profile option
Internal Manager: work like CRM to yes.

Concurrent: Use ICM is the profile name

If u r getting Target node/queue unavailable in status column then in the manager –> define form check the Conflict resolution manager node. It should be set to correct node value. Set it to correct value and bounce the CM. By default this value is never set. It will take the node from FND_NODE table.

Problem Statement
Error Messages:
CSTPACIN.COST_INV_TXN: (70): ORA-20100: File o0086078.tmp creation for FND_FILE failed. You will find more information on the cause of the error in request logSolution
In this case we need to check following 3 things

1) Check the UTL file parameter in DB side. Compare it with the APPLPTMP parameter on application side. Both this should match.

2) The file path mentioned in these 2 parameters should contain the space and permissions.

3) Check also the parameter APPLTMP

Please note that, following parameters should be in synch.

· APPLTMP
· APPLPTMP
· FORMS60_OUTPUT
· REPORTS60_TMP
· TMPDIR
· TMP

Set the same path correctly for all these variables in context file (APPL_TOP/admin/.xml) and run autoconfig. This will resolve the issue.

Some time we come across the issue when trying to connect with database from the application side using apps as a user. This basically requires the listener to be up to make connection with database. We get error similar to
Cannot login to sqlplus using following userid/passwd.

sqlplus apps/apps@dbname.

Gives error
ERROR:
ORA-12547: TNS:lost contact
———————————————————
Error Messages:
ERROR:
ORA-12547: TNS:lost contact
———————————————————

Solution:
In this case first check if the database listener is up or now. If the listener is up then check the sqlnet.ora file present in ORACLE_HOME/network/admin also can be reached using the environment variable TNS_ADMIN. This file contains 2 parameters, which restricts login to the database from the other hosts.

tcp.validnode_checking = yes

tcp.invited_nodes=(hostname1, hostname2, … )

This will allow entry from hostname1, hostname2 servers only. So if these values are commented and listener is bounced then this will resolve the issue.