DSXchange

Sorry but I have to add one more caveat to this sordid tale. What is described above works but it only works temporarily. for se 7.5.1a and solaris 5.10 Generic_125100-10 sun4u sparc the above works but it will only work for a few days or a few weeks and then you have to do the operations describe a...

Hi, One thing we find that works very well and is easy is some non-intuitive parameters for Oracle stage. Whatever you are doing this helps a lot with SE Oracle. I'm not saying that it will do a 4 mill row table operation in 10 minutes but these things help over the defaults of Oracle SE stage. For ...

Two things to add to what I said above. I just saw some evidence you have to set the Data Direct drivers to work on a project by project basis. You have to do the 3 steps above for every project you want to use the Data Direct Drivers in. It doesn't work for all the projects on the server if you do ...

Hi, I'm glad you asked. I owe it to anyone with this problem to be really clear how to fix it. This is what I think worked and you probably have to be dsadm to edit .odbc.ini 1) Put these two lines in your bci program and compile it: DEFFUN DSAttachODBCDriver(hDBC) Status = DSAttachODBCDriver(hDBC) ...

Leroy,

Thanks for the tip. You have definitely clarified something for me. With VAS there is no userid entry in the password file although VAS id's can be referred to in groups. So this gives us an important perspective on the problem, thanks.

... Flash

Gents, This is Cardinal Richileue. Unfortunately this twisted tale is not over. I am working this problem on two large Sun boxes. I got everything working on one box and then I moved the two lines of bci code over to the other box. The two new lines of bci code did not work on the other box. It appe...

Kenneth, First of all I want to qualify something I said earlier. The entire thread up to a a certain point was not incorrect. I think our license did expire after 30 days as Ray and that other gentleman pointed that out. That was an important point and I was able to keep formal support on the right...

Hi, I really apologize for this but all that is said about this problem above is not true. IBM Ascential support came back and said that Datastage Basic (Ray calls it BCI) is OK for Data Direct calls. If you want to use Data Direct with C++ or Perl you have to buy a "Full" Data Direct Lice...

Kenneth, Thanks. It looks like we are going to need alternatives and you gave us some good ones. Just to completely close this thread out. Last night IBM Ascential support confirmed to me that you need a "Full licence" from Data Direct to use Data Direct odbc calls like the one's I show ab...

And by the way, as slow as I was getting back to you on this stuff, you beat the formal support in figuring out what this was.

... Tom

Teej/Ray, It may be obvious to you guys that I was using the drivers directly and you set me straight. But to poor smuck me, I was using a licensed datastage product with database calls that were in the Ascential documentation and accepted by the compiler. When I read the error message, I thought th...

Teej/Ray, Thanks I think you guys got it. Makes sense. This ran for a while on two different datastage machines and then stopped working. It stopped working on the later datastage install more recently. Ascential isn't building any loyal customers with the obscure error message. I don't why they jus...

Ray, Just to try something, I deliberately made a bad sql update statement in my before job. When I did the error message became more explicit. This is what it said: est..BeforeJob (SQL Client Interface): Error in ODBC interface SQL State = S1000, DBMS code = 6091 [DataStage][SQL Client][ODBC][DataD...

Ray,

All 3 iterations came out with this.

test..BeforeJob (SQL Client Interface): Error in ODBC interface
SQL State Ray = 00000, DBMS code = 5549056

5549056 doesn't seem like an Oracle return code. Any thoughts?

... Flash

Ray, Thanks. I'm trying some of your options. Obviously I need a way to see the return code so I'm calling a Log posting after the line you suggested. Is this the right way to do that? ErrCode = SQLError(hEnv, SQL.NULL.HDBC, SQL.NULL.HSTMT, SQLState, DBMScode, ErrText) Call DSLogInfo("status of...