Fatal Error : setOutputFieldAsString()

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
Pankaj
Participant
Posts: 5
Joined: Mon Sep 20, 2004 7:29 pm

Fatal Error : setOutputFieldAsString()

Post by Pankaj »

Hi,

i get this Fatal error half way after the job has run :

dynMSSQLPMM003,0: Field type must be string in order to call setOutputFieldAsString() for field '8' in output dataset '0'.

I am using a Dynamic ODBC connecting to MS SQL server on parallel canvas and then i load it into Oracle through a Transformer.

I have looked at the datatypes at both the source and the target and they are same i.e. Varchar(100), also the encoding has been set to same for both, and the "Extended Unicode file has been set to blank" I still get the same Fatal error.

Could someone help me get rid of this Fatal error. ?

Thanks
Pankaj
Eric
Participant
Posts: 254
Joined: Mon Sep 29, 2003 4:35 am

Post by Eric »

As the job seems to start running and then fail, perhaps there is an item of data in the source table that is causing the problem?
pavankvk
Participant
Posts: 202
Joined: Thu Dec 04, 2003 7:54 am

Post by pavankvk »

can you juss check if u r using a basic transformer in a parallel job???

Eric wrote:As the job seems to start running and then fail, perhaps there is an item of data in the source table that is causing the problem?
richdhan
Premium Member
Premium Member
Posts: 364
Joined: Thu Feb 12, 2004 12:24 am

Post by richdhan »

Hi Pavan,

I don't think Basic Transformer has setOutputFieldAsString() function. As Eric mentioned it must be something to do with the input data.

Pankaj, if both the source and target are varchar(100) why do you have to use setOutputFieldAsString() function.

--Rich

Pride comes before a fall
Humility comes before honour
Pankaj
Participant
Posts: 5
Joined: Mon Sep 20, 2004 7:29 pm

Post by Pankaj »

Hi All,

Firstly, I am not using the above mentioned function in any of my stages. Its something that is put in by DS.

I think that the error was due to the source data, some junk characters that caused the DS Code to terminate. To take care of this I made used setting the NLS to None. That just pulls what ever you have at source without any encoding.

Thanks for all your help.

Pankaj
Post Reply