Helpful folks,

I am having a problem getting Oracle's Transparent Gateway for DRDA
product to interface with DB2 UDB for LUW 8.1.14.

The Gateway product is running on Linux and using DRDA protocol to
connect to my DB2 test server, which is running on Win2003. This test
server has recently been migrated to V8. It was previously on V7.2
FP5, and here is where the mystery lies.

For, when my test server wast at V7, the Oracle gateway was able to
connect and read data. But after I migrated to V8, it no longer works.
I have double-checked every dbm/db cfg parameter, env variable, host
file entries I can think of. They all seem identical to what I had in
V7.

The error that is produced is a 30020 sqlcode with 124c return code,
which indicates a syntax error in the data stream. However, the syntax
of the connection info did not change between V7 and V8. Here is the
full error produced by Transparent Gateway for DRDA:

ERROR at line 1:
ORA-04052: error occurred when looking up remote object
ORADW.GTW$_BIND_PKG@UDB.FADV.COM
ORA-00604: error occurred at recursive SQL level 1
ORA-28500: connection from ORACLE to a non-Oracle system returned this
message:
TG4DRDA v10.2.0.3.0 grc=0, drc=-30020 (839C,0000), errp=GDJMRC
errmc=124C
ORA-02063: preceding 3 lines from UDB

On the initial connection to DB2, the Gateway binds a package in DB2.
The permissions (on thel login being used) for CONNECT and BIND
PACKAGE are also identical between V7 and V8.

My question, does anyone have any experience with this scenario, or,
is anyone aware of things that have changed in regard to DRDA
connectivity to V8 (defaults changing, new cfg parameters, etc.)

Any help or feedback would be greatly appreciated.

Thanks,
Sean

Scav wrote:
> Helpful folks,
>
> I am having a problem getting Oracle's Transparent Gateway for DRDA
> product to interface with DB2 UDB for LUW 8.1.14.
>
> The Gateway product is running on Linux and using DRDA protocol to
> connect to my DB2 test server, which is running on Win2003. This test
> server has recently been migrated to V8. It was previously on V7.2
> FP5, and here is where the mystery lies.
>
> For, when my test server wast at V7, the Oracle gateway was able to
> connect and read data. But after I migrated to V8, it no longer works.
> I have double-checked every dbm/db cfg parameter, env variable, host
> file entries I can think of. They all seem identical to what I had in
> V7.
>
> The error that is produced is a 30020 sqlcode with 124c return code,
> which indicates a syntax error in the data stream. However, the syntax
> of the connection info did not change between V7 and V8. Here is the
> full error produced by Transparent Gateway for DRDA:
>
> ERROR at line 1:
> ORA-04052: error occurred when looking up remote object
> ORADW.GTW$_BIND_PKG@UDB.FADV.COM
> ORA-00604: error occurred at recursive SQL level 1
> ORA-28500: connection from ORACLE to a non-Oracle system returned this
> message:
> TG4DRDA v10.2.0.3.0 grc=0, drc=-30020 (839C,0000), errp=GDJMRC
> errmc=124C
> ORA-02063: preceding 3 lines from UDB
>
> On the initial connection to DB2, the Gateway binds a package in DB2.
> The permissions (on thel login being used) for CONNECT and BIND
> PACKAGE are also identical between V7 and V8.
>
> My question, does anyone have any experience with this scenario, or,
> is anyone aware of things that have changed in regard to DRDA
> connectivity to V8 (defaults changing, new cfg parameters, etc.)
>
> Any help or feedback would be greatly appreciated.
>
> Thanks,
> Sean

There is probably something wrong with the package bind.
Maybe you are hitting something similar to this:
http://www-1.ibm.com/support/docview...id=swg1IY50531

Is there anything in DB2's diagnostic log?

--
Jeroen

Not a peep, even when I set diaglevel to 4.

Scav wrote:
> Not a peep, even when I set diaglevel to 4.
>
I suggest you contact DB2 Service. A -30020 error indicates some DRDA
violation has occurred.

Scav wrote:
> Helpful folks,
>
> I am having a problem getting Oracle's Transparent Gateway for DRDA
> product to interface with DB2 UDB for LUW 8.1.14.
>
> The Gateway product is running on Linux and using DRDA protocol to
> connect to my DB2 test server, which is running on Win2003. This test
> server has recently been migrated to V8. It was previously on V7.2
> FP5, and here is where the mystery lies.
>
> For, when my test server wast at V7, the Oracle gateway was able to
> connect and read data. But after I migrated to V8, it no longer works.
> I have double-checked every dbm/db cfg parameter, env variable, host
> file entries I can think of. They all seem identical to what I had in
> V7.
>
> The error that is produced is a 30020 sqlcode with 124c return code,
> which indicates a syntax error in the data stream. However, the syntax
> of the connection info did not change between V7 and V8. Here is the
> full error produced by Transparent Gateway for DRDA:
>
> ERROR at line 1:
> ORA-04052: error occurred when looking up remote object
> ORADW.GTW$_BIND_PKG@UDB.FADV.COM
> ORA-00604: error occurred at recursive SQL level 1
> ORA-28500: connection from ORACLE to a non-Oracle system returned this
> message:
> TG4DRDA v10.2.0.3.0 grc=0, drc=-30020 (839C,0000), errp=GDJMRC
> errmc=124C
> ORA-02063: preceding 3 lines from UDB
>
> On the initial connection to DB2, the Gateway binds a package in DB2.
> The permissions (on thel login being used) for CONNECT and BIND
> PACKAGE are also identical between V7 and V8.
>
> My question, does anyone have any experience with this scenario, or,
> is anyone aware of things that have changed in regard to DRDA
> connectivity to V8 (defaults changing, new cfg parameters, etc.)
>
> Any help or feedback would be greatly appreciated.
>
> Thanks,
> Sean
>
Can you collect db2drdat trace on your V8 server?

Open command window, issue:

db2drdat on

issue connect from Oracle gateway. When you get error, on Windows
machine issue:

db2drdat off

which creates file db2drdat.dmp


If it is not too big (it shouldn't - post it's contents - it is an ASCII
text file.


Jan M. Nelken

Scav wrote:
> Not a peep, even when I set diaglevel to 4.

I assume the problem is on the Gateway side.
Did you follow the scenario described here:
http://download-west.oracle.com/docs....htm#sthref974

More specifically:
- (re)creating the ORACLE2PC table before executing the DRDA package bind
- creating the data dictionary tables/views for UDB v8

HTH

--
Jeroen