9.2.0.6 Blobs JDBC bug ?

From: Pip <prk_at_exemail.com.au>
Date: 18 May 2005 15:23:37 -0700
Message-ID: <1116455017.245665.206290_at_o13g2000cwo.googlegroups.com>

[Quoted] I posted this on Metalink and have had no response from Oracle, I think this is a bug in 9.2.0.6 howevere I cannot get confirmation or find any oracle do that identifies as such .... I think this is a general JDBC error in 9.2.0.6, it is just that I am using the message gateway that I see it - please help ?

 I have upgraded a 9.2.0.5 solaris 8 based database to 9.2.0.6 because of advice of Oracle and bug number #3566420. Oracle JDBC version is 9.2.0.6

After the upgrade sending BLOBS from AQ to MQ via the Message Gateway returns the below error in the message gateway log file. The error appears when I enque a BLOB message only and not a simlpe text message - using sys.mgw_basic_msg_t (header, text_body, raw_body ).

The error I cannot find documented and the getBytes() error indicates something wrong in the Oracle distributed jar files.

Please can someone advise asap ( this is urgent ) as I cannot stay on 9.2.0.5 and currently I cannot go to 9.2.0.6

oracle.mgw.common.GatewayException: [243] SQL error: 17068 at oracle.mgw.common.MgwUtil.GatewayException(MgwUtil.java:542) at
oracle.mgw.drivers.aq.MapConsumerMsg_MgwBasicMsg.mapMessage(MapConsumerMsg_MgwBasicMsg.java:127) at

oracle.mgw.drivers.aq.AQMsgConsumer.doDequeue(AQMsgConsumer.java:557)
at oracle.mgw.drivers.aq.AQMsgConsumer.dequeue(AQMsgConsumer.java:317)
at oracle.mgw.drivers.aq.AQLink.receive(AQLink.java:1659)
at oracle.mgw.engine.Worker.deqMessages(Worker.java:207)
at oracle.mgw.engine.Worker.processJob(Worker.java:1112)

at oracle.mgw.engine.Worker.myRun(Worker.java:87) at oracle.mgw.engine.ManagedThr.run(ManagedThr.java:58)

[Linked-exception]
java.sql.SQLException: Invalid argument(s) in call: getBytes()

at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:134)
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:179)
at oracle.sql.BLOB.getBytes(BLOB.java:194)

at
oracle.mgw.drivers.aq.MapConsumerMsg.blobToBytes(MapConsumerMsg.java:260) at
oracle.mgw.drivers.aq.MapConsumerMsg_MgwBasicMsg.mapBody(MapConsumerMsg_MgwBasicMsg.java:201) at
oracle.mgw.drivers.aq.MapConsumerMsg_MgwBasicMsg.mapMessage(MapConsumerMsg_MgwBasicMsg.java:121) at

oracle.mgw.drivers.aq.AQMsgConsumer.doDequeue(AQMsgConsumer.java:557)
at oracle.mgw.drivers.aq.AQMsgConsumer.dequeue(AQMsgConsumer.java:317)
at oracle.mgw.drivers.aq.AQLink.receive(AQLink.java:1659)
at oracle.mgw.engine.Worker.deqMessages(Worker.java:207)
at oracle.mgw.engine.Worker.processJob(Worker.java:1112)

at oracle.mgw.engine.Worker.myRun(Worker.java:87) at oracle.mgw.engine.ManagedThr.run(ManagedThr.java:58)

My testing has narrowed the issue to

It seems that if I swap the 9.2.0.6 jdbc directory - ORACLE_HOME\jdbc\lib - contents with 9.2.0.5 jdbc directory it works!

Is there a patch or a known issue here whereby I can use the 9.2.0.5 jdbc lib. Is this a supportable solution ?

I think this is a general JDBC error in 9.2.0.6, it is just that I am using the gateway.

pip Received on Thu May 19 2005 - 00:23:37 CEST