DSXchange

A post to close this off which is worth putting on here. With 7.1 working, we have re-installed the 7.5.1.a server. Using a different CD to install off. And guess what - it works. We had 2 new DataStage servers, so just to prove that it wasn't working because of something that the install of 7.1 lef...

We have uninstalled everything, re-installed as the local administratror, logged in and run as the local administrator (not that that should make much difference) - no joy.

We have also now uninstalled everything, and installed DataStage 7.1. And guess what - it works.

We had been, and are hoping to use 9.2.0.4 client. However, we have tried installing and running with 8.1.7 client, but we get exactly the same error. We can read from, but not write to Oracle. As an additional piece of info, we are able to write to the database using the ODBC link, so I don't think...

Had the same error, but with Oracle 8 OCI. Acutually found it was registry settings that were causing the problem, not a "corruption" of Oracle. Did you by any chance install other versions of Oracle, or install Oracle to a different directory at some point? My problem was caused by wantin...

Thanks for the replies. 1. Ray, the input file has 1 row, with one value in it. "X". The target table contains null varchar2 (5) columns, and within datastage itself, the columns are defined as nullable varchar(5) columns. 2. Sainath, using the same username / password in a SQLPLUS session...

A similar issues have been posted before, but with no real clear resolution in them, so here we are again. I have DataStage 7.5 on a Windows 2000 box with Oracle 9.i client. Connecting to an Oracle 8.1.7 database on a Unix box. When using either the 8i, or 9i stage, I am able to read (view data) thr...

The 50000, odd values were me playing around with an installation of DataStage with NLS enabled to find a solution. Thanks for the multibyte pointer Ray. Using the non NLS enabled DataStage i think that a solution to our problem is to use a char(seq(VALUE)). This appears to successfully convert MOST...

Hi All, We have an input file that has an 8 bit character in it, essentially used to identify a transaction type (they have used from 0 to 127, and now they are sending us the character equivelants up to 150 or so). At the moment we are running DataStage 7.1 without NLS support, and our target is a ...