DataStage Jobs failure due to Broken Pipe

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
saur_classic
Participant
Posts: 9
Joined: Tue Aug 01, 2006 9:43 pm

DataStage Jobs failure due to Broken Pipe

Post by saur_classic »

Hi,

I am working on Datastage 7.5 Release and the Underlying OS is LINUX SUSE.

All PX Jobs are Failing due to Broken pipe Error.

The Job contains
2-Dataset stage,1 Change Capture and 1 sequential file.

The Exact ERROR is

Fatal Prev_Snapshot_tbl_Ds,0: /bin/echo: write error: Broken pipe
Fatal Prev_Snapshot_tbl_Ds,0: Operator terminated abnormally: received signal SIGBUS

Is there any solution for the above problem?

Can Someone help to get around this Problem...?


Regards,
ArndW
Participant
Posts: 16318
Joined: Tue Nov 16, 2004 9:08 am
Location: Germany
Contact:

Post by ArndW »

All PX Jobs are Failing due to Broken pipe Error.
Usually broken pipes are not the cause of problems but the most visible symptoms. Something is causing your processes to fail, and then their side of the pipes are being closed down and the other side of the process reports this as an error.
There should be more errors in your log than these, look for an error or warning that occurs before the broken pipe messages. Can you use dataset management to view your datasets? Can you view the contents in the designer?
madhukar
Participant
Posts: 86
Joined: Fri May 20, 2005 4:05 pm

Re: DataStage Jobs failure due to Broken Pipe

Post by madhukar »

sometimes it will be due to user permissions also.
ashwin141
Participant
Posts: 95
Joined: Wed Aug 24, 2005 2:26 am
Location: London, UK

DataStage Jobs failure due to Broken Pipe

Post by ashwin141 »

Hi

Broken pipe may be because of incorrect metadata. Esnure that you are using the right metadata and you are not creating bigger data than waht your fields are. Check properly the metdata of datasets what you have defined and what you are reading here. Sigbus errors is mostly if you try reading an unallocated memory location, which you are not supposed to read.

Regards
Ashwin
perfman
Premium Member
Premium Member
Posts: 46
Joined: Thu Aug 16, 2007 6:19 pm

Post by perfman »

When I changed to Load/Append method instead of Upsert, the problem solved. Is there any reason for that?
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

Probably that Load/Append finishes faster, giving less opportunity for the pipe to break (or to be broken).
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Post Reply