DSXchange

It will be pretty difficult to create ixf files from within DataStage. Just create a delimited ASCII outputfile and use the "DEL" option of the DB2 loader.

Ogmios

Or another guess for your problem... old version of DB2 on the AS400, while newer version of DB2 client on your datastage server. Open a ticket with IBM/DB2, in some cases it is possible to install some extra things on the mainframe so that it will work. Another solution would be to downgrade your D...

Just as a warning to other people using a combination of DB2 v8 and DataStage v7. What we've seen during our upgrade is that DB2 v8 returns a lot more warnings than DB2 v7 and DataStage v7.5 handles them in a strange way which screwed up some of our jobs. E.g. a simple insert into a view is done in ...

Not a DataStage error, hand it over to your nearest friendly DB2 DBA. He will be able to fix it.

Ogmios

John, Maybe check with Ascential... we had the same problem when we were on v4.x. I belief they had us put a shared library (lpw or so) in front of the others in the dsenv file which made a huge difference. We did spend a couple of months on it. Unfortunately I don't recall anymore exactly what it w...

Have a look in install.sh and check whether all components referenced in there exist. When you install e.g. DataStage on Solaris depending how you mount your install media (or how you ftp it to the server) you have to make a few manual changes. Then print out the "install and upgrade guide"...

No luck yet... there are gremlins on ADN. Whenever I search for ODBC it bombs out with a PHP error

Ogmios

From experience... the ODBC stage is not very good at spewing out the good error messages, I spent a couple of hours one time on an "row insert error" (as the ODBC stage indicated) while in fact my tablespace was full.

The native stages are usually better integrated.

Ogmios

This is problem I already solved, but just in case someone else encounters the same (or I forget in a couple of months :wink: ). In DataStage v7 in combination with DB2 v8 I got the following error message while importing table definitions: DSR.MetaGeta(GET.TABLES)(SQLTables): BCI Error: SQLSTATE=38...

I've got the following situation: One of my jobs contains a very complex SQL statement running against DB2 v8.2 in an ODBC stage. When the job executed in DataStage version 6 I would get a warning about "statement too complex" from DB2, but the job would execute properly for the rest. In D...

In version 6 of DataStage there were problems with the error codes using ODBC to Oracle (you wouldn't see the specific ORA error message), which wasn't the case when using Ora stage to Oracle. In one case this cost me 4 hours to figure out the "tablespace" was full using ODBC. Haven't trie...

One person for immediate DataStage training :wink: In the server edition it's e.g. just a regular database stage. The first one you connect to a transformer will get a full line, the rest you connect are lookups by default (which broken lines) and use slightly different semantics. The primary stage ...

Then it's not a problem in DataStage but in "DOS"... what about trying to executing in the style as: D:\Ascential\DataStage\Runstats\Runstats_interface.bat & D:\Ascential\DataStage\Runstats\runstats_interface_Rename.bat The & should make for unconditional sequential execution (1 &a...

1. not really sure what your saying in this solution? select on 1 table via a database stage... connect to transformer, connect database stage to transformer as lookup (the underbroken lines) to select on the other table... same problem as 2, in your case you do not have an exact lookup in the seco...

Different solutions: 1) If you equi-join on the primary key you could select from one table and then do a database lookup on the other table (you should have one unique row per key you try to lookup) 2) Load one of the tables in a hash file in DataStage and use that as lookup, disadvantage here is d...