DSXchange

ODBC_Connector_73,0: Fatal Error: Attempt to setIsNull() on the accessor interfacing to non-nullable field "unique_row_id"

The job was fine with input and output suddenly when I tried to run it again

I had this error,can anyone suggest me about this error?

Check whether you have defined the field "unique_row_id" as nullable anywhere in your job

Check the input table for the ODBC stage if any data has been updated in the second run.
If not please provide me with the stages you are using and also where ISNull() function is used.

As mentioned by "creatingfusion", I too am wondering if there is a Null that is coming in your data. Post more details on this so that we can provide a better solution.

No unique_row_id is not nullable in any of the stages.

I used SetNull() in the transformer stage for some fields in the field description.

"Null that is coming in your data"

Do you mean the input data?

stages used are transformers,copy,funnel,look-up,odbc,file.

In transformer use the derivation as......

If IsNull(%inputcol%) Then SetNull(%inputcol%) Else ''

Actually I used SetNull() for dummy columns to use funnel for the other output.

there are two outputs and to make them as a single output

I used transformer to create same columns as of the other output.
and I used SetNull() for that.

I am also getting the below errors searched the forum but cannot find a single solution.

main_program: APT_PMsectionLeader(1, node1), player 1 - Unexpected exit status 1.

main_program: APT_PMsectionLeader(1, node1), player 3 - Unexpected exit status 1.
APT_PMsectionLeader(1, node1), player 8 - Unexpected exit status 1.
APT_PMsectionLeader(1, node1), player 9 - Unexpected exit status 1.

please suggest me!!!

in the transformer derrivation you have a function @NULL
Please use that in place of SetNull()

Let us know if that works

No thats not working

The quess the reason is because of the APT...........errors........

I used SetNull() in many of the the fields,probably thats not the issue

The error is in ODBC Connector Stage, but is it during read or write?

is that column defined as not null in database?

are you performing cast on that field or any other function?

Which database?

The job was fine with input and output suddenly when I tried to run it again

This is not correct. Something must have changed, either Job or data or table metadata.

Thanks to everyone.

Yesterday I had all that errors in that particular job but today its working good with no errors or warnings.

I did not change anything in the job but why do we get that kind of errors?

Any answer would be a guess as there are too many factors that could be involved. You are assuming it is a DataStage problem, however, it could be a problem with the database, or it could have been another developer changing your file definition inside the database.

Since the problem is gone away, I'd say wait until it comes back and then repost.