Job throws fatal error but does not Abort

[Arpanakhade2009]

Hi All,
There is an ETl job to populate data from oracle (oracle enterprise stage) to Sql server (ODBC stage).

The normal behaviour of an ETL job is to abort teh job in case of any fatal errors with status 'Aborted' and in case of any warnings with status 'Finished (see log)'

The job now prompts with a fatal error:
APT_CombinedOperatorController,0: [Microsoft][SQL Native Client]Invalid character value for cast specification
And the job completes with status 'Finished (see log)'

Can any one please let me know what are the probable reasons for this unusual behaviour about log.
Any specifc patch for this fix.

Thanks
Arpana

[priyadarshikunal]

Can you please mention the exact version of DataStage?

[sureshreddy2009]

Is the data loaded into target database.
Try the following things , if not works any of the following .Think about the patches
1.The warning is mainly related to casting error. Means the datatype mismatch from Oracle to Sql server database.
2.If you used two stages in your job oracle enterprise stage ( for oracle) > ODBC stage (Sql server ),Use transformer stage in between this two stages.Import the metadata in both source oracle enterprise stage and target odbc stage,then match in transformer.Hope it will works.
Thanks :D

[Arpanakhade2009]

The ETL Job is as below
Oracle (Oracle stage) --> Transformer (Where i map data from Nvarchar to Varchar & Number to integer fields) --> SQL server(ODBC stage)

Also data is not completely loaded in database.

DS version : 8.0
Build number : 1.2

[gssr]

Set APT_DISABLE_COMBINATION to true and try to figure out which stage is causing error

[chulett]

Unfortunately, we've all seen behaviour like that, some combination of things can result in fatals that don't abort. Open a case with your offiical support provider, perhaps you are missing a patch. Especially since you're still on 8.0 rather than 8.1.

[priyadarshikunal]

Its a known problem in Datastage 8.0.1. Hope below link helps.

http://www-01.ibm.com/support/docview.w ... wg1JR33966

[Arpanakhade2009]

Thanks for the information.
Actually I have found out that there is a field of type date in oracle but holds data in format '07/10/2004 09:56:20'; target SQL server has datatype timestamp
Tried modifying the datatype in oracle stage from Timestamp(23,3) to Timestamp(19) also Varchar(23,3)
But no change

PLz guide

[priyadarshikunal]

How can you specify scale for varchar

[Microsoft][SQL Native Client] this means the problem is in sqlserver client not in oracle, so why are you changing the metadata in Oracle stage?