Oracle Enterprise stage

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
aminsachin
Participant
Posts: 1
Joined: Thu Feb 04, 2010 2:18 pm

Oracle Enterprise stage

Post by aminsachin »

Hello Gurus,

we have installed DS 8.1 on a windows machine and everything is working fine, the only problem we are facing is we created a sample job to read data from flat file to oracle, we are using oracle enterprise stage.

we get below error
(source /source is user id and pass and oracle is the SID )Oracle_Enterprise_6,0: The system(sqlldr source/source@Oracle CONTROL=ora.3232.66000d.0.ctl LOG=ora.3232.66000d.0.log BAD=ora.3232.66000d.0.log.bad SILENT=header PARFILE=ora.3232.66000d.0.par) failed; see the log file for the Oracle specific message.

Oracle_Enterprise_6,0: The runLocally() of the operator failed.

-----------------------

i imported the metadata from flat file and iam using the same metadata to create the table in oracle.


please help....

sachin
sachin amin
nayanpatra
Participant
Posts: 41
Joined: Sat Jun 06, 2009 11:13 pm
Location: Kolkata

Post by nayanpatra »

Can you please clarify which load/write method and partitioning method you are using in the enterprise stage and the connector stage?
Nayan
priyadarshikunal
Premium Member
Premium Member
Posts: 1735
Joined: Thu Mar 01, 2007 5:44 am
Location: Troy, MI

Post by priyadarshikunal »

Please post the content of ora.3232.66000d.0.log which should be present in your scratch disk. This would reveal why the sqlldr failed to write records in oracle table.
Priyadarshi Kunal

Genius may have its limitations, but stupidity is not thus handicapped. :wink:
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

You don't really need to post it... you do however need to look at it. As noted, the reason for the failure will be there which is why the error message directed you to "see the log file for the Oracle specific message".

Afterwards, if you still need help figuring out what went wrong, post the important bits here.
-craig

"You can never have too many knives" -- Logan Nine Fingers
priyadarshikunal
Premium Member
Premium Member
Posts: 1735
Joined: Thu Mar 01, 2007 5:44 am
Location: Troy, MI

Post by priyadarshikunal »

chulett wrote:You don't really need to post it... you do however need to look at it.
Thats correct. Once you look in to the log file you will know what actually went wrong. Also for validate for which record it gave error, you should look at ora.3232.66000d.0.log.bad file which will have the errored out records.
Priyadarshi Kunal

Genius may have its limitations, but stupidity is not thus handicapped. :wink:
Post Reply