Issue in Reading Data in Sequential file

Manu1 · Post by **Manu1** » Fri Sep 11, 2009 1:40 am

Hi All,

I have loaded the Data into the Target Sequentil File.But when I am trying to Read the Same its giving the Below Error.

##E IIS-DSEE-TFOR-00089 13:01:15(704) <_ABORT_IDENT_,0> The runLocally() of the operator failed.
##E IIS-DSEE-TFOR-00089 13:01:15(706) <APT_CombinedOperatorController,0> The runLocally() of the operator failed.
##E IIS-DSEE-TFPM-00040 13:01:15(707) <APT_CombinedOperatorController,0> Operator terminated abnormally: runLocally did not return APT_StatusOk
##E IIS-DSEE-TFSC-00011 13:01:21(000) <main_program> Step execution finished with status = FAILED

I tried different ways to Understand the Issue by analyzing the Data that I have loaded from Source.And I suspected that there is Some Problem with the data in the columns in source which has its Datatype as TIMESTAMP.

So,I have reloaded the Data by removing the Fileds with TIMESTAMP datatype and agian tried to View the Data and could able to View it without any Issue.

Could any one give your thought what is the Problem when I tried to view the data with TIMESTAMP columns.

Thx In Advance.

ArndW · Post by **ArndW** » Fri Sep 11, 2009 3:33 am

As always when an error message is from the "APT_CombinedOperatorController", add "APT_DISABLE_COMBINATION" to your parameters and set the value to "true" in order to discover the stage causing the problem.

chulett · Post by **chulett** » Fri Sep 11, 2009 6:06 am

Manu, please stop with the bold and the blue. Just plain old text like this is fine. Really.

Kryt0n · Post by **Kryt0n** » Sun Sep 13, 2009 3:23 pm

Have you checked the file on your system? Are you getting any warning messages in your logs? It sounds like your job may actually be rejecting the records due to invalid type.

You get that set of error messages when no records are returned... rather annoying but doesn't seem to be one they are looking to fix any time soon.

dxk9 · Post by **dxk9** » Mon Sep 14, 2009 12:12 am

Check out the values of the data of the TIMESTAMP field whether it complies with that of the Default TIMESTAMP value (Job's default settings). If not, change the default setting to match to that of the source data or you can import the TIMESTAMP data also as 'Varchar' and then convert to the desired format in the transformer using StringtoTimestamp() function.

I generally import as Varchar and then convert in the later stages and it works perfectly!!

Regards,
Divya

dxk9 · Post by **dxk9** » Mon Sep 14, 2009 12:13 am

Check out the values of the data of the TIMESTAMP field whether it complies with that of the Default TIMESTAMP value (Job's default settings). If not, change the default setting to match to that of the source data or you can import the TIMESTAMP data also as 'Varchar' and then convert to the desired format in the transformer using StringtoTimestamp() function.

I generally import as Varchar and then convert in the later stages and it works perfectly!!

Regards,
Divya