DSXchange

Just to bring people up to speed, we 'chatted' about this problem over in the developerWorks forums. I pointed them to this post by Daddy Doma which seemed to have a solution to their problem: m This was the OP's LIBPATH that was posted. Note I'm adding returns to it to keep the post from going wide...

Seconding the sageness. Especially the build of an automated out request, something I always build into any process like this.

Which typically means that the Oracle target type is a DATE field with the DataStage datatype declared as a Timestamp, the default when importing metadata via the OCI plug-in. With that combination and generated SQL, the stage wraps a TO_DATE around the field: TO_DATE(YourField,'YYYY-MM-DD HH24:...

I wonder if this will require Vista?

All well intentioned, but nothing we do can really keep people from doing things like that. Items number 2 and 3 are already in place but I don't believe all forums have a moderator. Plus there are rules for post deletion - you can only delete your post if there are no replies to it. Once someone re...

Sorry, but that date is not ok if the field has been declared as a Timestamp in the job and the stage is generating the DML. And I've already posted what the stage expects in that case.

Have you used User Defined SQL to do lookups with the Teradata stage before this? If not or you're not completely sure what the sql should look like - let the stage generate it for you first. Get it close and see what the generated sql looks like. Switch it User Defined and tweak from there. Then th...

Sorry, didn't realize you were this mystery IBM group, Kim.

Have you looked in the job's log? All of the warnings will be logged there, posting a sample or two would go a long way towards letting us help you solve your problem.

Well, keep the technique in mind for those times when you can't do the aggregation in the source database - times where you are aggregating on transformed data, for instance.

Example? And you are converting from UTF-8 to what?

I suggest you contact the 'IBM SOFTWARE GROUP' that provided the jobs to you. They would be best equipped to resolve any issues with them.

Make sure you sort the data in such a manner that supports the aggregation being done. Get it wrong and the stage will ignore your sort work and handle it itself. Also make sure you 'assert' the sort order correctly in the stage, get that wrong and the job will abort with a 'Row out of seqeunce' err...

but iam getting Error as: Attempt to convert String value " 15-AUG-2006 " to Timestamp type unsuccessful That would be because the format you chose is not appropriate for a Timestamp datatype. You would need to convert it to YYYY-MM-DD format, not DD-MON-YYYY. Technically, the OCI stage is expectin...

Best place to start would be the XMLPACK_20_Designer.pdf document you'll find on your client PC. There is a 'Docs' directory under wherever you installed your client that you'll find it in.