DSXchange

If you use more than 2 tables or have multiple criteria in the where clause, you apparently need a client patch for sql builder to function properly.

Lookup ecase 86365 for more information.

One other thing to note, the client machine - laptop, experiences cpu utiliztion of 100%. We have tested this on two laptops.

We use SQL builder extensively in the Oracle Enterprise Stage (we use the 10g syntax), but began having issues opening SQL Builder this afternoon. Generally in jobs where a multiple join(s) exist. SQL builder will open, but may take 10-15 minutes in some cases. This has not been the case until today...

We are using the same exact source data set that we used on the 4-way configuration. The only thing that has changed is the hardware - we failed the 4-way over.

We failed our 4 way dev box (linux RH 3) over to an 8 way yesterday. Without modifing the config file (4 node) several PX jobs ran to completion, albeit without vast improvement in performance. I figured I needed to add some scratch space and modify the config file. Still just testing the waters. Ho...

They are not listed in the environment variables section at the beginning the job log of the job sequence, but do exist in the DSPARAMS file for the project ( checked it via Admininstrator and looking directly at the file on Linux). I just received a patch from Engineering at IBM in the form of a re...

We recently went live (Aug 21) with a complete rearchitecture of our ETL environment and all jobs - from Sever 7.0 to Enterprise 7.5.1a. All has been going well except a set of warnings that occurr intermittently in various Job Sequences. Here are the warnings: DataStage Job 143 Phantom 2086 The var...

Not a problem at all, I really appreciate you replying... Basically i wrote a utility in PL/SQL that identifies the partitioned bitmaps for a specific range of time and marks them unusable. then I run my daily ETL load. Once it's complete, the indexes are rebuilt through another PL/SQL procedure by ...

I do have some lookups that are sourcing Oracle via Oracle Enterprise, but isn't the Upsert a completely different session?

Maybe I am missing something here, but if I have an Oracle Enterprise Stage and choose the Write method as 'Upsert', the open command is not an option. I only see the open and close commands as an option when 'Load' is the chosen Write Method.

Unfortunately, the open command does not seem to be an option when the write method is 'UPSERT'

This has worked for you? Does DataStage accept a delimiter like a / between the alter session statement and the update statement?

We are moving from 7.0 Server to 7.5.1a Enterprise. Our target database is Oracle 9.2. As part of the ETL process, we mark the partitioned bitmap indexes as unusable prior actual loading of data by DataStage and then rebuild the indexes after the load. In the server edition of DataStage, using the O...

We set partitioning on all of the links to 'Auto'. Can I see the method DS chooses to use when using this setting?

So if I had 20 input links to the Merge (one for each lookup and one for the master flow) and set them all to Auto, it is possible that DS would calculate the partitioning strategy for one of the links differently than the other 19 and cause the data to have missing values for columns on the record....