DSXchange

Issue solved by adding an index on the column specified in the Update...where clause.

Thanks to all.
I exported the dsx and sent to IBM. I have a workaround design for the job flow.

ray.wurlod wrote:Or use AS clauses to give your columns names in the user-defined SQL. These column names must match those on the Columns grid.

I tried the 2 proposed solutions above (the view and the AS clause), unfortunately I got the same error in Datastage, while the SQL is correct in the DB2 user interface.

I need to generate N records when reading 1 record in a DB2 table (N = value in a column of the table). In this forum, I have seen solutions with Transformer loop (unfortunately with Datastage 8.5), or with Oracle Connect by (while it is DB2 in my case). WITH N (LEVEL, FREQ_SKEY, FREQ_STARTTIME) AS ...

For absolutely best performance having the DataStage engine co-resident with the database server is the way to go. But performance is usually satisfactory where they are on different machines connected by a very high speed network. I found in Planning,Installation and Configuration guide (page 80):...

We have 1 server for Datastage (with all tiers installed) and 1 server for the DBMS SQL Server. Best practice for performance would be assigning the DB stage (ODBC or other native - when reading from the database or writing to the database) to a node corresponding to the DB server in the configurati...

Hi Group, At last got a patch from IBM Support for this issue. The ECase reference is E119230. The limitation at this time is that this patch only fixes the ODBC Enterprise stage. We had this issue when using the SQL Server enterprise stage and that is still not fixed and is addressed by a separate...

sjordery wrote:Thanks again.

I double-checked and there is no RCP in the previous job (the one that creates the dataset.

I would suggest to import the metadata of the data set and the table (the ODBC look up) and compare with the layout in the current job.

The problem is probably linked to the data set, not to the lookup type (Normal or Sparse). Your data set may be created by another job with RCP "on". Please compare the current layout of the data set with the layout in the Repository (Import / Table Definition / Orchestrate Schema Definiti...

It is possible that your job is a "saved as" (copied) job from an initial job where RCP was "on". In this case, you cannot uncheck RCP. Try to recreate your job from scratch with RCP "off".

ppgoml wrote:it seems you have the same problem as below APAR.

http://www-01.ibm.com/support/docview.w ... wg1JR31652

if so, you need to install either 8.0.1 fixpack 3 or 8.1 fixpack 1

Thank you Jack. Your explanation is plausible.

When you next get the warning, look at the "job starting" event in the log or the "environment variables" event, to determine just what the value of APT_ORCHHOME is for that run. Thanks for your feedback. The same job runs without warning on 25 Feb, and with warning on 28 Feb. T...

I have many daily jobs generating randomly - not every day - the following warning: "Failed to discover JobMonApp port, APT_ORCHHOME environment variable may not be set correctly". APT_ORCHHOME has the following value: E:\IBM\InformationServer\Server\PXEngine Why does this warning appear s...

Post your 2 node configuration file as well. I saw this behavior once with what appeared to be a 2 node configuration at first glance. Ended up that there was an extra set of curly braces misplaced that essentially caused the second node to be ignored. Mike Thanks, Mike. You are probably right. Her...

ArndW wrote:Open up a job monitor from the director after the job has run and set it to show instances. Does it show 2 instances for the transform stage?

Thanks for your help. I keep this issue on hold a few days until I return from another location.