Operator terminated abnormally: received signal SIGABRT

major · Post by **major** » Wed Nov 23, 2011 1:11 pm

Hi all,

I'm getting below error message from one of my jobs

XML_Output_2,0: Operator terminated abnormally: received signal SIGABRT
main_program: Step execution finished with status = FAILED.

details of job design

1. Joning 2 datasets using join stage and putting the output in XML 1
2. Output of XML 1 is joined with another dataset to produce XML 2

XML 1 is fine and problem is with output of XML 2

If I'm not physically creating XML 2 there isn't any error at all , only when I try to create it physically this error is coming.

I have read some posts here but didn't find any information.

Thanks
major

major · Post by **major** » Thu Nov 24, 2011 2:31 pm

Any suggestions please

Thanks
Major

major · Post by **major** » Sat Nov 26, 2011 1:58 pm

Any help please..

chulett · Post by **chulett** » Sat Nov 26, 2011 3:30 pm

Note that I have no clue and this is just a fishing expedition... can you explain exactly how you are "joining" the XML output with the dataset? Also the why of it - how does that joining produce the second XML output? I guess I'm looking for the reason for the join and wondering if there is another way to get you your output...

major · Post by **major** » Sat Nov 26, 2011 5:25 pm

Chulett,

I have 3 datasets - Accountline, reinsurance and ult-reinsurance with their own set of attributes . One accountline can have 0-n reinsurers and one reinsurer can have 0-n ult-reinsurers . I need to generate XML in the similar way with accountline attributes under which we should have reinsurer attributes and under reinsurer we should have ult-reinsurer attributes

My design is I have joined reinsurer and ult- reinsurer datasets with a join stage to generate their attributes as XML except the keys , those keys are carried to output stage and the other xml attributes are read like one xml data element(this XML is not created on disk ) to join with accountline dataset for creating target XML on disk which is giving the error.

Thanks
Major

major · Post by **major** » Mon Nov 28, 2011 12:50 pm

Any suggestions

PaulVL · Post by **PaulVL** » Mon Nov 28, 2011 2:18 pm

In our shop, most of our SIGABRTs have been due to bad NLS settings in a job. Folks don't select the proper code page according to the data they try to juggle.

Have you cleaned up the job to get rid of all warning messages?

major · Post by **major** » Tue Nov 29, 2011 2:05 pm

Ahh...finally I found the reason ,
there is an non-english character in one of the column for a single row out of 30k rows .
I have filtered that row and the XML is creating without any issues.

Initially, I was pushing the output of XML 2 to a dataset so I can see only SIGABRT error.
But when I removed the target dataset and tried to create the XML 2 as target stage for the job then this problematic row has popped up in log file making my life easier

Thanks all for suggestions.

Major