Call to Sqlldr Failed

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
brownnt
Premium Member
Premium Member
Posts: 21
Joined: Tue Feb 03, 2009 6:07 pm

Call to Sqlldr Failed

Post by brownnt »

Our development DataStage environment has stopped running any parallel job that has an Oracle stage. Below is the error log we are receiving. I have checked the permissions on the server for Scratch and the dsadm user has administrator access.


Occurred: 10:24:01 AM On date: 2/1/2011 Type: Fatal
Event: AssetFact,1: The call to sqlldr failed; the return code = 852; (...)

Occurred: 10:24:01 AM On date: 2/1/2011 Type: Fatal
Event: AssetFact,1: Unable to access the log file.

Occurred: 10:24:01 AM On date: 2/1/2011 Type: Fatal
Event: AssetFact,1: The runLocally() of the operator failed.

Occurred: 10:24:01 AM On date: 2/1/2011 Type: Info
Event: AssetFact,1: Input 0 consumed 1 records.

Occurred: 10:24:09 AM On date: 2/1/2011 Type: Fatal
Event: AssetFact,1: Operator terminated abnormally: runLocally did not return APT_StatusOk

Occurred: 10:24:09 AM On date: 2/1/2011 Type: Fatal
Event: main_program: Step execution finished with status = FAILED.

Occurred: 10:24:09 AM On date: 2/1/2011 Type: Info
Event: main_program: Startup time, 0:16; production run time, 5:23.

Occurred: 10:24:14 AM On date: 2/1/2011 Type: Control
Event: Job AssetFactParallel aborted.
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

So, it was working and then stopped? Any idea what changed? And is it literally any job with an Oracle stage or only if that Oracle stage is calling sqlldr?

Also, "(...)" means there is more to the message. Double-click on it and post the full message.
-craig

"You can never have too many knives" -- Logan Nine Fingers
brownnt
Premium Member
Premium Member
Posts: 21
Joined: Tue Feb 03, 2009 6:07 pm

Post by brownnt »

Thats correct everything was working fine on the server until yesterday. There was a new version of anti-virus client installed on the server last week but we removed the anti-virus completely and the problem still exist.

Here is the details behind the error message. Also when you go look for the log file it does not exist anywhere on the server.

AssetFact,1: The call to sqlldr failed; the return code = 852;
please see the loader logfile: E:/IBM/InformationServer/Server/Scratch/ora.5500.73000d.1.log for details.
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

Did you check to see if the anti-virus "quarantined" or removed anything it thought was a threat? They've been known to eat things they shouldn't on a DataStage server and are not recommended there... unless you exlcude those directories from it.

And the log shouldn't exist "anywhere", only in that one specific place noted in your message, which is your scratch area. If it's not there, no need to look elsewhere.

Since it doesn't, then sqlldr wasn't able to create it. Have you tried manually launching sqlldr from the command line? Does that work at all? Wondering if you need to reinstall your Oracle client...
-craig

"You can never have too many knives" -- Logan Nine Fingers
brownnt
Premium Member
Premium Member
Posts: 21
Joined: Tue Feb 03, 2009 6:07 pm

Post by brownnt »

I checked the logs for the anti-virus client and there are no files quarantined. I am able to run the sqlldr from the command line without error also.
Post Reply