I'm getting this error in the XML Output stage:
Operator terminated abnormally: received signal SIGSEGV
The catch to this is that I don't always get the error. Somedays it works and some days it does not (with the same input). I've never had this problem before in other jobs, but this time the job contains 120 columns. Is there some sort of limit? The input has only 10 rows.
I've check the forum for SIGSEGV (segmentation fault) errors and I couldn't find anything to fix it.
The job is simple. It has an input data set stage, a transformer, and an output XML stage.
Has anybody had this problem?
XML PACK : SIGSEGV error
Moderators: chulett, rschirm, roy
Give me some idea on job flow..And schema of ur source and target
We have faced this problem..But my flow is entirely differ from U..Actually we had some problem with Timestamp fields ..While loading timestaamp columsn in the target using upsert option we had some problem...But we resolved in some other Way...
SIG SEV means:Segmenattion error from Unix side
We have faced this problem..But my flow is entirely differ from U..Actually we had some problem with Timestamp fields ..While loading timestaamp columsn in the target using upsert option we had some problem...But we resolved in some other Way...
SIG SEV means:Segmenattion error from Unix side