DSXchange

I'm going to expand on this question, as I'm having a similar issue. Our job sounds the same - it is writing out to a Netezza Enterprise stage. In Netezza, the field is a varchar, and is nullable. In DataStage, the field is defined as nullable. However, when the job runs, it complains of the same is...

Did you ever get a fix to this? I am now also running into the same problem. Oddly, we have an IBM consultant on-site, who is able to open a job he created with the XML stage and click on the "Edit Assembly" button, but when we try on any of our laptops it doesn't work. To further complica...

We're working with the Oracle plug-in stage and were running into some optimization issues. There have been at least two instances where a query is completely optimized in Oracle, yet the DataStage job runs extremely slow. Example #1: Reading data from a text file, doing a lookup via Oracle plugin t...

We are currently running DataStage version 5.2 on Solaris. We recently bought DataStage version 7.5 and are prepared to install it. I have read through the forum entries and I know that it is possible to co-locate two versions of DataStage, but only one can be active at a time. Our DS admin was look...

Hello, I've run into a slight snag with my design and was wondering if anyone else had ever encountered a similar problem: I am connecting to a DB2 database using the DB2 stage [not ODBC]. There are a few instances where Japanese characters are stored in fields in addition to English text. One parti...

Sean, Maybe you can save as one of the jobs. Remove the relational stage and replace it with a sequential stage to truly rule out that the DB is/is not causing the problem. If it runs then you probably have a DB problem and if it does not then further research is necessary. Regards, Michael Hester ...

Ogmios, Thanks for the advice, but unfortunately it doesn't fix the problem. Yes, this is something I was aware of as well. When one of the jobs in question is hung and must be aborted, there is a process in the background still connected to the DB. I have verified with the DBA though, that once thi...

Okay, the basic problem is that two out of six jobs in a particular DataStage project are hanging. Below are as many details as I can provide: Originally our DataStage Server was running v6x on a filesystem. The jobs were running fine. We migrated our jobs to a v7.1 server that pointed to this same ...