SIGSEGV error

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
suneelchallagali
Participant
Posts: 251
Joined: Tue Dec 02, 2008 3:09 pm

SIGSEGV error

Post by suneelchallagali »

Hi guys,

i have created the which loads the data from source to the target components i have used for developing the job are in the following order.

2 seq_inputs > join > transformer> 4odbc stage.

this was working fine earlier but suddely it is giving me an error stating SIGSEGV error i have searched the form and tried most of possiblities like
setting APT_CONFIG to 1node,APT_Combination = false.


one more funny thing the same is working fine for another data.

please it will be great if you provide an effective information.

thank you,
suni
laknar
Participant
Posts: 162
Joined: Thu Apr 26, 2007 5:59 am
Location: Chennai

Post by laknar »

definitely there will be source issue.
please check the source file
try to split the files and load.
Regards
LakNar
suneelchallagali
Participant
Posts: 251
Joined: Tue Dec 02, 2008 3:09 pm

Post by suneelchallagali »

Hi lakar,


If there is a source issue job should not ran earlier, but it has ran earlier.
when i have tested the job with test data it was working fine., but when i am testing with actual data it is giving me the following error.

TARGET_SSN,1: Operator terminated abnormally: received signal SIGSEGV

main_program: APT_PMsectionLeader(2, node2), player 4 - Unexpected exit status 1.

main_program: Step execution finished with status = FAILED.

Thank you,
suni
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

suneelchallagali wrote:If there is a source issue job should not ran earlier, but it has ran earlier.
Not a very good assumption. :wink:

Seems pretty obvious you've got something different in your 'actual' data than you ever saw in your test data, something that it causing the job to implode. What that difference is I can't say, but it sure seems like it must be there.
-craig

"You can never have too many knives" -- Logan Nine Fingers
kandyshandy
Participant
Posts: 597
Joined: Fri Apr 29, 2005 6:19 am
Location: Singapore

Post by kandyshandy »

Do you see any stage name in front of the error message. TARGET_SSN is your job name or stage? If stage, which stage it is?
Kandy
_________________
Try and Try again…You will succeed atlast!!
suneelchallagali
Participant
Posts: 251
Joined: Tue Dec 02, 2008 3:09 pm

Post by suneelchallagali »

target_ssn is an odbc database stage. The job has following stages with order mention below

SEQ>TRANSFORMER>ODBC_STAGE
suneelchallagali
Participant
Posts: 251
Joined: Tue Dec 02, 2008 3:09 pm

Post by suneelchallagali »

I mean seq_File>Transformer>Odbc stage
mandyli
Premium Member
Premium Member
Posts: 898
Joined: Wed May 26, 2004 10:45 pm
Location: Chicago

Issue/Error Message: Operator terminated abnormally, receive

Post by mandyli »

Issue/Error Message: Operator terminated abnormally, received signal SIGSEGV

please follow the above mentioned steps..
suneelchallagali
Participant
Posts: 251
Joined: Tue Dec 02, 2008 3:09 pm

Post by suneelchallagali »

Hi mandyli,


I have set the given paramaters as you mentioned in my job and ran it but it is giving me the same error.
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

There are things in your data that might cause a segmentation violation including, though not exhaustively, trying to load a null into a non-null column or trying to load more than N characters into a Char(N) or VarChar(N) column (you would probably generate the signal in the ODBC driver in these cases, and I note that "TARGET_SSN" was indeed the generating stage).
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