Job aborts abnormally

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
rumu
Participant
Posts: 286
Joined: Mon Jun 06, 2005 4:07 am

Job aborts abnormally

Post by rumu »

Hi All,

I have following job design.

SeqFile------->Trnsfr----->SeqFile

in transformer i created one stage variable where i used 'NextSurrogateKey()' function,before this job i created one single job with surrogate key generator stage ehre i created stat file.

now coming to the main job I described above,i used the stage variable in the mapping of sequential file.

the src having 1000 records,for 1000 records one surrogate id is created so i used stage variable.

while running the job i got the following error:

'Transformer_9,1: Operator terminated abnormally: received signal SIGSEGV'

could any one pls help me in this regard,
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

Are you using a state file in conjunction with the Surrogate Key Generator stage and, if so, have you established and initialized the state file?
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
rumu
Participant
Posts: 286
Joined: Mon Jun 06, 2005 4:07 am

Post by rumu »

Ray,

I am stating my steps here:

1)In first job,I used only surrogate key generator stage where I created
STATE file.
2)Next job as described in my earlier post,

seq file----trnsf-----seqfile

here in transformer stage,i used the same state file in the surrogate key properties in the transformer stage,in a stage variable i am using 'NextSurrogateKey()' function and using this stage variable in my column derivation of sequential file.

while running the job,job aborts with the following msg:

Transformer_9,0: /bin/echo: Broken pipe
Transformer_9,0: Operator terminated abnormally: received signal SIGSEGV
main_program: APT_PMsectionLeader(1, node1), player 3 - Unexpected exit status 1.
main_program: Step execution finished with status = FAILED.

here is the dump score:

main_program: This step has 2 datasets:
ds0: {op0[1p] (sequential Sequential_File_1)
eAny->eCollectAny
op1[1p] (parallel APT_TransformOperatorImplV0S9_CreateMetaTagTableCopy_Transformer_9 in Transformer_9)}
ds1: {op1[1p] (parallel APT_TransformOperatorImplV0S9_CreateMetaTagTableCopy_Transformer_9 in Transformer_9)
->eCollectAny
op2[1p] (sequential APT_RealFileExportOperator in Sequential_File_16)}
It has 3 operators:
op0[1p] {(sequential Sequential_File_1)
on nodes (
node1[op0,p0]
)}
op1[1p] {(parallel APT_TransformOperatorImplV0S9_CreateMetaTagTableCopy_Transformer_9 in Transformer_9)
on nodes (
node1[op1,p0]
)}
op2[1p] {(sequential APT_RealFileExportOperator in Sequential_File_16)
on nodes (
node1[op2,p0]
)}
It runs 3 processes on 1 node.

regards,
rumu
rumu
Participant
Posts: 286
Joined: Mon Jun 06, 2005 4:07 am

Post by rumu »

Dear All,

Could you kindly help me?

rumu
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

If they can they will. Being pushy like this only generates negative attitudes. Some people are busy earning a living, some people like to think about problems before posting. So learn patience or harrass your support provider, who may require additional payment to provide the kind of rapid response you seem to be demanding.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
rumu
Participant
Posts: 286
Joined: Mon Jun 06, 2005 4:07 am

Post by rumu »

I appologise for my mistake..

i have some deliverables today only.....i understand your point.

I am sorry....
kprama
Charter Member
Charter Member
Posts: 8
Joined: Wed Jul 21, 2004 4:48 pm

Post by kprama »

I know this is a very old thread.

Rumu
have you found out any resolution for the SIGSEGV you are seeing in this design.
pandeesh
Premium Member
Premium Member
Posts: 1399
Joined: Sun Oct 24, 2010 5:15 am
Location: CHENNAI, TAMIL NADU

Post by pandeesh »

SIGSEGV generally reders a kind of memory error and that's not related to design i think.
Have you tried executing the job in sequential mode(or in single node)?
pandeeswaran
Post Reply