Hi..
I got a fatel error in my server job.
"Pipe Broken"
Any one help me pls. why it is come.
Regards,
Ragunathna J
Pipe Broken
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 50
- Joined: Mon Sep 25, 2006 11:18 pm
- Location: Chennai
- Contact:
Please elaborate on the problem. The error message you have given is not sufficient to get you a valid answer. We can just guess.
Give the scenario in which you get this error message.
Also copy and paste the entire error/warning message, rather than typing it out.
Give the scenario in which you get this error message.
Also copy and paste the entire error/warning message, rather than typing it out.
Narasimha Kade
Finding answers is simple, all you need to do is come up with the correct questions.
Finding answers is simple, all you need to do is come up with the correct questions.
-
- Participant
- Posts: 50
- Joined: Mon Sep 25, 2006 11:18 pm
- Location: Chennai
- Contact:
Hi..
Actuly i write a records into flat file, using sequential file stage as "Pre_CDC_namedPipe_write" And also read records from same flat file , using sequential file stage as "Pre_CDC_namedPipe_read" by parallel.
when i was run this job i get the following error.
Fatal ds_setup:error in 'write()'-Broken pipe
Info AiSfaEcmsPrmntlAct.Pre_CDC_namedPipe_read.Valid_source:Run stopes after 700 rows
Regards,
Ragunathan J
Actuly i write a records into flat file, using sequential file stage as "Pre_CDC_namedPipe_write" And also read records from same flat file , using sequential file stage as "Pre_CDC_namedPipe_read" by parallel.
when i was run this job i get the following error.
Fatal ds_setup:error in 'write()'-Broken pipe
Info AiSfaEcmsPrmntlAct.Pre_CDC_namedPipe_read.Valid_source:Run stopes after 700 rows
Regards,
Ragunathan J
hi,
in a lot of situations, abort after 700 rows is the same about 0 rows, job treating 700 rows each time. then I think you have aborted directly
then, pipe file is not a file you want to write in, but it's only a null file, always 0 bytes, where your data is traveling but never it stops..
your design have then to be like
entrance_stage -> flat_file_stage_pipe_option -> ending_stage
if you put the ending_stage in pipe_option, it can't work
Bertrand
in a lot of situations, abort after 700 rows is the same about 0 rows, job treating 700 rows each time. then I think you have aborted directly
then, pipe file is not a file you want to write in, but it's only a null file, always 0 bytes, where your data is traveling but never it stops..
your design have then to be like
entrance_stage -> flat_file_stage_pipe_option -> ending_stage
if you put the ending_stage in pipe_option, it can't work
Bertrand