SIGSEGV error
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 251
- Joined: Tue Dec 02, 2008 3:09 pm
SIGSEGV error
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
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
-
- Participant
- Posts: 251
- Joined: Tue Dec 02, 2008 3:09 pm
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
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
Not a very good assumption.suneelchallagali wrote:If there is a source issue job should not ran earlier, but it has ran earlier.
![Wink :wink:](./images/smilies/icon_wink.gif)
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
"You can never have too many knives" -- Logan Nine Fingers
-
- Participant
- Posts: 597
- Joined: Fri Apr 29, 2005 6:19 am
- Location: Singapore
-
- Participant
- Posts: 251
- Joined: Tue Dec 02, 2008 3:09 pm
-
- Participant
- Posts: 251
- Joined: Tue Dec 02, 2008 3:09 pm
Issue/Error Message: Operator terminated abnormally, receive
Issue/Error Message: Operator terminated abnormally, received signal SIGSEGV
please follow the above mentioned steps..
please follow the above mentioned steps..
-
- Participant
- Posts: 251
- Joined: Tue Dec 02, 2008 3:09 pm
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
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.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.