This content has been marked as final. Show 5 replies
First of all let's look at your environment ... a totally unpatched version of software that is so old it is in desupport mode. You should upgrade to a fully supported version but, if you can't, at least to 10.2.0.5.
That said without seeing any of your code, or a listing showing permissions on the directory and files, there is insufficient information from which to help you.
Please post ALL information required for us to understand what you are doing an your environment.
But before I decided that NOBODY was doing anything ... I'd shell out to the server from SQL*Plus using the HOST command and verify that permissions are as you believe them to be. There is every reason to believe SQL*Loader is having an issue with your file as identified.
Thanks for the reply damorgan.
I cant upgrade the DB.
but here i tried your second instruction and logged into the box and connected via SQLPLUS, now executed the "host /Run.sh"
this works fine and sqlloader loaded data into table.
now still when i run using the run_job or OEM job, it fails with same error.
Any suggestions for this issue?
Under what Unix account (user) you run the test ?
Try it under same user as ORACLE processes are running, you probably don't have set write permissions.
You need to post the syntax you used to create the DBMS_SCHEDULER job that calls these shell scripts. Most likely, when the shell scripts work and the (external) job does not, there is a syntax problem in your CREATE_JOB statement.