Oracle issue

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
kittu.raja
Premium Member
Premium Member
Posts: 175
Joined: Tue Oct 14, 2008 1:48 pm

Oracle issue

Post by kittu.raja »

Hi,

I am trying to load into the oracle table but I am getting an error saying "Ora_Policy,1: /bin/echo: write error: Broken pipe"
"Ora_Policy,1: Operator terminated abnormally: received signal SIGSEGV".

I am using upsert mode.

My design is FF --- pivot ----Xfm ---- Rmd ----- Oracle

When I run it one more time it is successful.

Tomorrow when I run it again it is not successful and again if I run it it is successful.

The job takes one hour to complete.

I serached in the forum but did not find relevant answer for my case.

Can anyone help me out.

Thanks,
Rajesh Kumar
prasad.bodduluri
Participant
Posts: 30
Joined: Tue Jan 30, 2007 5:21 am
Location: bangalore

Post by prasad.bodduluri »

build index on table columns which are key columns, i think it will fast the job.
prasad
kittu.raja
Premium Member
Premium Member
Posts: 175
Joined: Tue Oct 14, 2008 1:48 pm

Post by kittu.raja »

prasad.bodduluri wrote:build index on table columns which are key columns, i think it will fast the job.
I have indexes on my table. but my problem is not the time its aborting for the first time and successful for the second time.
Rajesh Kumar
Kryt0n
Participant
Posts: 584
Joined: Wed Jun 22, 2005 7:28 pm

Post by Kryt0n »

When it works, is it processing faster than when it doesn't work? In particular, how long does it take before it actually starts pushing data in to Oracle.

If it appears to fail just as data is pushed to Oracle, then check your sqlnet expire_time settings or even just try setting it to a lower value. Oracle may be determining your connection has died and cutting you off, DataStage doesn't realise this until it actually tries to load the data. This was something that caught us out but can't actually remember what the error we received was...
Post Reply