Search found 5 matches

by Pankaj
Sun Oct 17, 2004 12:13 pm
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: Cascading Joins
Replies: 4
Views: 2891

Hi I was thinking what happens if i do not provide any partitioning ? Do i need to do the hash partition, and i am not very sure how this works, but i am looking forward to read on this.. I tried the same thing today with some other tables... i still dont get the right thing out ... I dont know what...
by Pankaj
Thu Oct 07, 2004 6:05 am
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: Cascading Joins
Replies: 4
Views: 2891

Cascading Joins

Hi All, I dont know if i can explain this. I have three table T1, T2, T3. Relations T1 and T2 are related on column A (like T1.A = T2.A ) T2 and T3 are related on column Z (Like T2.z = T3.z) Now, When In datastage i join the T1 and T2 on A using Join Stage and then the o/p from this join stage is co...
by Pankaj
Thu Oct 07, 2004 5:57 am
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: Fatal Error : setOutputFieldAsString()
Replies: 4
Views: 2573

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 pull...
by Pankaj
Thu Sep 30, 2004 5:54 am
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: Fatal Error : setOutputFieldAsString()
Replies: 4
Views: 2573

Fatal Error : setOutputFieldAsString()

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 Tra...
by Pankaj
Wed Sep 29, 2004 9:44 pm
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: Fatal Error : Primary Key Violated
Replies: 1
Views: 1881

Fatal Error : Primary Key Violated

I have already loaded records into the table. Now when I run the job again it checks that the records exist so no records to be added. I have a surrogate key generator right before loading into the final table. Although there are no records to enter... I get this error... oraD_Channel: Oracle call f...