DSXchange

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

definitely there will be source issue.
please check the source file
try to split the files and load.

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

suneelchallagali wrote:If there is a source issue job should not ran earlier, but it has ran earlier.

Not a very good assumption.

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.

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?

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

SEQ>TRANSFORMER>ODBC_STAGE

I mean seq_File>Transformer>Odbc stage

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

please follow the above mentioned steps..

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.

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).