Page 1 of 1

DS job failed due to SQl Loader issue

Posted: Wed Oct 28, 2009 3:37 am
by Nareshkurra
Hi,

Please find the error below.

Oracle_Enterprise_285,0: The call to sqlldr failed; the return code = 35072;
please see the loader logfile: /abc/ac/02/scratch/ora.20269.404983.0.log for details.


The job is inserting data to theoracle table using Load option, and is getting failed with the error mentioned above.

We have upgraded our DS version from 7.5.1 to 7.5.3. Previously the job use to run successfully with out anny issues, we are facing the issue after upgradation.

Help required.

Thanks

Re: DS job failed due to SQl Loader issue

Posted: Wed Oct 28, 2009 3:47 am
by sanjay
Naresh

what is error in log file

Thanks
Sanjay
Nareshkurra wrote:Hi,

Please find the error below.

Oracle_Enterprise_285,0: The call to sqlldr failed; the return code = 35072;
please see the loader logfile: /abc/ac/02/scratch/ora.20269.404983.0.log for details.


The job is inserting data to theoracle table using Load option, and is getting failed with the error mentioned above.

We have upgraded our DS version from 7.5.1 to 7.5.3. Previously the job use to run successfully with out anny issues, we are facing the issue after upgradation.

Help required.

Thanks

Posted: Wed Oct 28, 2009 7:16 am
by chulett
:!: Please don't post the same question multiple times.

This is being discussed here, please respond there if you'd like to help:

viewtopic.php?t=130190

Posted: Wed Oct 28, 2009 10:02 pm
by Nareshkurra
Hi Sanjay,

Please find the warning it gives us before it gets failed.

Oracle_Enterprise_1,0: ld.so.1: sqlldr: fatal: /opt/oracle/client/10.2.0/lib32/libclntsh.so.10.1: wrong ELF class: ELFCLASS32

And there is no log file created for this and when searched for log file in the below location it just displays only control files, but log file is not there


/abc/ac/02/scratch/ora.20269.404983.0.log for details.

Oracle_Enterprise_1,0: Unable to access the log file.

Posted: Tue Feb 01, 2011 7:32 am
by brownnt
Was this issue ever resolved? I am getting the same error message in an 8.1 Windows environment.

Posted: Tue Feb 01, 2011 8:40 am
by chulett
Please start your own thread with the details of your particular error message.