[Date Prev][Date Next][Thread Prev][Thread Next]
[Author Index]
[Date Index]
[Thread Index]
[SQR-USERS Info]
[SQRUG Home Page]
ORACLE/NT & DB2/OS390 using Oracle DB Link
- Subject: ORACLE/NT & DB2/OS390 using Oracle DB Link
- From: Sandra Sparks <sparsand@PSNC.COM>
- Date: Thu, 10 Dec 1998 12:39:48 -0500
- Organization: PSNC
We are getting an ORA-01002 Fetch out of sequence using SQR to access a
DB2/OS390 table through an Oracle NT Database Link going through SQL Net
to Oracle's Transparent Gateway for DB2. This only occurs if we first
access an Oracle Database table on NT first and then the DB2 table.
When we access the DB2 table first and then the Oracle NT Peoplesoft
table everything works fine. I've been doing some research on this and
I did find an Oracle bug report #239128 documenting a problem with
Oracle version 7.1.3 with SQR 2.5 when selecting null values from a
remote table through a database link. We are on Oracle Enterprise
Server 7.3.4, but I asked the client to Select a single non-null column
just to make sure it wasn't an old bug re-surfacing. The same problem
still occurs. We are using DB2/OS390 Release 4, Oracle Transparent
Gateway 4.0.1.1 and Windows NT 4.0.
Has anybody else had this problem? Am I doing something really dumb?
I'm new to Oracle NT and SQR. The problem is behaving as if a dynamic
SELECT was PREPAREd, the cursor OPENed the DB2 unit of work ended, then
a second unit of work started with FETCH being the first statement and
of course no open cursor exists. But I can't tell what SQR is doing
internally since there are no DECLARE CURSOR's OPEN's or FETCHes in
SQR. No COMMIT's exist in the SQR code.
Heeeeeelllllllllp, pleeeeeeeze, anybody?