RE: Oracle EBS fnd_file problem
Date: Thu, 28 Feb 2013 11:13:55 -0500
Message-ID: <017c01ce15ce$9c522b00$d4f68100$_at_rsiz.com>
Same user starts ccmgr? IF not, check whether it is environment or permissions for the user that starts ccmgr. Since it is giving you a full file address, it seems likely the env is correct, unless I suppose the slashes are the wrong direction for your OS.
-----Original Message-----
From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org]
On Behalf Of Jeffrey Beckstrom
Sent: Thursday, February 28, 2013 10:30 AM
To: Innaiah Pudota
Cc: oracle-l-freelists; oracle-db-l; oracle apps oaug dba list
Subject: Re: Oracle EBS fnd_file problem
exec FND_FILE.PUT(FND_FILE.LOG,'TESTING'); works fine.
UTL_FILE works find.
Just when done from the concurrent manager it fails.
>>> Innaiah Pudota <pinnaiah_at_gmail.com> 2/28/13 9:13 AM >>>
Hi Jeffrey,
Please make sure to have the first entry of utl_file parameter to APPLPTMP
location So please check APPLTMP and APPLPTMP . For the Best practice ,
please set APPLTMP and APPLPTMP to the same location and keep the same as
first entry in the utl_file.
Try to execute the below query to test the file whether it is getting
created in the same path.
exec FND_FILE.PUT(FND_FILE.LOG,'TESTING');
Hope this helps to fix your issue.
Thanks and regards,
-Inna
On Thu, Feb 28, 2013 at 2:43 PM, Jeffrey Beckstrom <JBECKSTROM_at_gcrta.org>
wrote:
Getting error that fnd_file unable to create a file.
From manager log we see:
declare
*
ERROR at line 1:
ORA-20100: Error: FND_FILE failure. Unable to create file, l0127129.tmp in the directory, f:\oracle\orapcomn\temp.
You will find more information in the request log.
ORA-06512: at "APPS_APPLMGR.FND_FILE", line 386
ORA-06512: at "APPS_APPLMGR.FND_FILE", line 526
It is NOT a permissions error. If I look in that directory, I DO SEE the file there as being empty. However, the date/time on the file is later than that of the request getting the error. Appears that something else is creating a file with the same name. I looked at a log from a run of this job on 2/19 and it is referencing the SAME tmp file as in the error message from a 2/11 log! Is this supposed to happen this way?
I did some googling and found a script which I altered to do:
select cp.plsql_log, cr.request_id
from apps_applmgr.fnd_concurrent_requests cr,
apps_applmgr.fnd_concurrent_processes cp where cp.plsql_log is not null and
cp.concurrent_process_id = cr.controlling_manager and cp.plsql_log =
'l0127129.tmp'
order by cr.request_id;
This script returned a lot of rows. I checked a couple of the requests and they matched to a workflow concurrent request job along with our failing job. Where does Oracle get the file name from? Really appears that another process is using the same name causing our problem.
Jeffrey Beckstrom
Database Administrator
Greater Cleveland Regional Transit Authority Information Systems
1240 W. 6th Street
Cleveland, Ohio 44113
-- http://www.freelists.org/webpage/oracle-l -- http://www.freelists.org/webpage/oracle-l -- http://www.freelists.org/webpage/oracle-lReceived on Thu Feb 28 2013 - 17:13:55 CET