DSXchange

use the sequencer stage as your first stage and send a link to each script in parallel. Otherwise, Datastage will execute them in the order they were dropped on the canvas.

Here is an interesting issue I found when implementing a User defined select or a select list containing a sub select in the Oracle OCI Px stage in 8.0.1 Datastage incorrectly added the partition information to the where clause in the subselect, not the main query body, such as: where (GBI_LA_DW.P_S...

Apparently, Anything can be an issue with Teradata and EE. The EE engine is required to create tables before it can write the data in a EE job. The work around (if this is not allowed) is to create a tmp DB with full permissions, and set the following env vars accordingly: APT_TERA_SYNC_USER APT_TER...

Congratulations Ken and family. That's a tough way to start your own consulting group, but nothing worth while is easy and your growth rate is pretty impressive so far...

tuna

I can forward the BP to anyone who requires it.

I also recieved a compiled version of DS.UNLOCK from Ascential support. This is an unlock command that lets you release jobs as dsadm if you do not have root access. It was an added feature in 6.x, but you can catalog the BP for earlier Dstage versions. It has been invaluable on our project because ...

on Solaris the rsh syntax is:

rsh -l user hpserv test

I think it is the same on HP. It will error out if you put the user param after the host.

you will also need a Call before the DSExecute. I typically use the same invocation of DSExecute all the time: First, test your command in unix. Then in your routine, paste the following lines for your invocation, with your tested command in the quotes (use escape chars for embedded quotes): cmd = &...

I think I saw this when I tried to run a Sequence job and the routine was not compiled, for example when you import the design of a set of jobs/routines.

Try compiling the routine and then running the job.

as ray mentioned, the SEQNAME.NEXTVAL is a great way to replace the IDENTITY function in SQL, keeping the persistence in the DB. you probably only want to use the KeyMgtKeyNextValue if you specifically want to move the persistence out of the database for use by multiple datasources, as Ken describes...

sorry if this is posted to the wrong group - just new to DSXchange. Has anyone had any experiences post Vality Merger ?

I am at a client who may need to buy more product, but I am not sure what the product relationship is with the ETL.

Thanks

mike