DSXchange

DataStage has problems with XML files larger than 200MBs.

A better solution is to write a simple program which will parse the file and create f.e. a comma delimited sequential file from the XML.

HTH

Have You tried the Convert function - it should satisfy all Your requirements and You won't have to write a routine:

IMHO Whale's solution is much more readlable and easy to maintain - if You have a complex query then it's hard to see the concatenation and You end up wondering: "Why the hell do I have these strings here?". If You do it in Transformer You can give it a name "AppendX" and at a gl...

If it's a fixed list of tables You can hard-code the tablenames in the sequence by setting the job's parameter.
If it should by dynamic (the table list changes) then store the list of tables f.e. in a sequential file and do the table row counts in a loop for each record in the sequential file.

Remove it an check what happens

Here: https://www.ascential.com/eservice/public/welcome.do

DATE datatype has nothing to do with the data format you get when you issue a SELECT statement - the format You see depends on your client settings. Oracle performs some datatype conversions automatically but it's better to do it explicity. If you have a varchar datatype in your OCI stage then you w...

That's a really smart - thanks for the tip DSguru2B

Count the rollno's using Aggregator and then filter the ones with count > 1.

Create a sequence - put 2 jobs inside and connect them. Job 1 - Sequential File --> Transformer --> Dummy HF. Inside the Transformer in the Derivation from the output link use SetJobUserStatus(link.PARAMETER) where link.PARAMETER is the column from the input. This will set the job's status to the ta...

You can use "Wait For File Activity" in your sequence.

Store the Rejects in a HashedFile with key column set to rollno but this way you will only get the last version of rejected row with given rollno.

In the first job read the file with tablename and use SetJobUserStatus(link.PARAMETER) to set job's user status. In the next job in the sequence You can pass it as parameter f.e. job1.$UserStatus.

It depends whats your source.

Do You want to extract the data in parallel jobs ? IMHO it will be better to extract the data in one job, split it using Transformer and Constraints (f.e. link1 loadyear=2006, link2 loadyear=2005 etc.) and land the data into sequential files which will be transformed in parallel. When all needed tra...