DSXchange

DataStage will run on a stand alone NT machine. Since your source and destination are also on that machine you should not have a problem.

regards
Vincent

I believe conditional lookups are planned for future releases of Datastage. There are some alternatives: - Split your data streams to let the minimum number of rows advance to each DBLookup tranformer. Those rows that are successfully lookup up are outputted to a file, the rest are passed on to the ...

Do you want to join the files or merge them? As DSGuru mentioned you can merge the two files to form a union data stream. However if you want to join the two files using a shared key then you will need to load one of them into a hash file first. Sequential files cannot be used as lookups in DataStag...

You could simplify this lookup by running a job that creates a hash file with pre calculated summed values for all account numbers. This would simplify your DataStage lookup and should provide a huge performance improvement. Example, if you were on SQL Server you would create a custom SQL with the f...

It may help to give a couple examples of the values being matched.

You could put both tables in the same database and then let Oracle join them together. This should be faster than a DataStage row by row join.

regards
Vincent

Have a look at the www.datawarehouse.com web site, it has a lot of forums and one of them is for Datawarehousing ETL tool comparison. Some of these message threads mention web sites where comparison reports or tools are located. Many of the threads cover Informatica versus DataStage and some of the ...

If you have two instances of a batch job running at once you can run child jobs in parallel or code a loop to ensure a child job is only run by one of the batch jobs at any one time. For single instance child jobs retrieve the status of the job, if it is not ready to run you wait a few seconds then ...

I would avoid this stage altogether as it is too slow. There are three options for bulk loads in version 6.0: - The OraBulk stage which creates a ctl and dat file that can then be loaded via a Unix script. - The Sequential file stage can create a dat file. The OraBulk can create the ctl file or you ...

You need the Oracle Migration Workbench, designed to simplify the process of migrating 3rd party databases to Oracle. Have a look at this link: http://otn.oracle.com/tech/migration/workbench/content.html Note that it can migrate stored procedures and triggers. I've been on a couple projects where th...

Have you looked at the Ascential Integrity product? While Quality Manager is good at locating and reporting on data quality problems the Integrity tool can be used to locate and clean problems. Since you are using text files as a source you will also benefit from the Integrity products ability to pr...

It could be a simple path problem. Try searching for the libtli.so file on the Unix drive and then adding that directory to your path. You can modify the PATH in the dsenv file. If you had a previous version of DataStage running on that machine or another machine then open up the old dsenv file to s...

With the one way encryption you can still let users re enter encrypted parameters. This is fairly standard functionality in many products, for example a DataStage database stage will show the password as a set of asterisks but the user can erase the value and type in a new one. You could mimic this ...

Use the Sequencer stage (the one that looks like an arrow with three dots in it) to either split one path into multiple paths to turn multiple paths back into one path. -- Job B -- Job D -- / Job A -- Seq1 --- Job C ------------ Seq2 -- Job E Make sure the Seq2 has been set to "Wait for All&quo...

What you may have done is cut and copied the code that runs the job the first time to run the subsequence instances. This can lead to an incorrect job handle where you end up waiting for the wrong job handle. When you call the wait command make sure you are passing it the most recent job handle from...

You can set up the file name as a job parameter and use this parameter in the file name field in the sequential file stage. Eg.: FileName: #FileDir##FileName# Two job parameters are used, one for the directory location and one for the file name. You can then call this job up multiple times and pass ...