MQSeries.net :: View topic - Message Broker 7 Oracle 12 C Connectivity

MQSeries.net

Tech Exchange

Education

Certifications

Library

Info Center

SupportPacs

FAQÂ Â

Usergroups

RSS Feed - WebSphere MQ Support

RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Message Broker 7 Oracle 12 C Connectivity

Message Broker 7 Oracle 12 C Connectivity

« View previous topic :: View next topic »

Author

Message

NaginWife

Posted: Thu May 22, 2014 2:09 am Post subject: Message Broker 7 Oracle 12 C Connectivity

Newbie

Joined: 22 May 2014
Posts: 4

hey all have been on this site a while and have found many items that have helped me out.

I have an issue with a client's Broker environment.

The Environment is

MQ 7.0.1.2}SunOS z-gcsu1 5.10 Generic_142900-13 sun4v sparc SUNW,Sun-Fire-T200
MB 7.0.0.5}SunOS z-gcsu1 5.10 Generic_142900-13 sun4v sparc SUNW,Sun-Fire-T200
Oracle 12.01

The client will be upgrading Broker shortly and are in the process of upgrading Oracle.

As part of a new project we are connecting to a new instance of Oracle (12.01) from the existing Message Broker.

We first hit an issue with client connectivity in Oracle whereby the sqlnet.ora needed to be updated on Oracle side to allow older client connections.

I now have an issue whereby I am running a message that as part of ESQL calls a stored proc in Oracle.

I now receive an error

Code:

2014-05-20 16:04:41.375480 246 RecoverableException BIP2934E: Error detected whilst executing the function or procedure ''InsertCaseDetailsTable''.
The message broker detected an error whilst executing the function or procedure ''InsertCaseDetailsTable''. An exception has
been thrown to cut short the processing of the message.
See the following messages for details of the error.
2014-05-20 16:04:41.375588 246 DatabaseException BIP2321E: Database error: ODBC return code '-1' using ODBC driver manager ''libbipodbc.so''.
The message broker encountered an error when processing a database operation. The ODBC return code was '-1'. See the followi
ng messages for information obtained from the database concerning this error.
Use the following messages to determine the cause of the error. Typical problems are an incorrect datasource or table names.
Correct either the database or message broker configuration.
2014-05-20 16:04:41.375696 246 DatabaseException BIP2322E: Database error: SQL State ''HYC00''; Native Error Code '0'; Error Text ''[IBM][ODBC Oracle Wire
Protocol driver]Optional feature not implemented.''.
The error has the following diagnostic information: SQL State ''HYC00'' SQL Native Error Code '0' SQ
L Error Text ''[IBM][ODBC Oracle Wire Protocol driver]Optional feature not implemented.''

A very helpful message saying something is not implemented. No idea what though.

ODBC details

Code:

PSCP=DataDirect 6.0 Oracle Wire Protocol

;# Oracle stanza
[DBNAME]
Driver=/opt/IBM/mqsi/7.0/ODBC/V6.0/lib/UKora24.so
Description=Application database
HostName=servername
PortNumber=xxxx
SID=SIDNAME
CatalogOptions=0
EnableStaticCursorsForLongData=1
EnableNcharSupport=1
ApplicationUsingThreads=1
EnableDescribeParam=1
OptimizePrepare=1
WorkArounds=536870912
ProcedureRetResults=1
ColumnSizeAsCharacter=1
LoginTimeout=0

Am i missing something? Apart from the non-implemented optional feature?

NaginWife

Posted: Tue May 27, 2014 2:18 am Post subject:

Newbie

Joined: 22 May 2014
Posts: 4

I can only assume no one else has seen this before. I suspect it is a rare combination on Broker and Orcale

mqjeff

Posted: Tue May 27, 2014 3:01 am Post subject:

Grand Master

Joined: 25 Jun 2008
Posts: 17447

Well, I do hope it is a rare problem.

Can you confirm that you really are trying to use Broker version 7 to talk to a new level of Oracle?

NaginWife

Posted: Tue May 27, 2014 5:20 am Post subject:

Newbie

Joined: 22 May 2014
Posts: 4

Jeff I can confirm this is so.

This is a mixed environment with Oracle 11 and 12 running. There are no issues connecting to 11.

There was an initial problem on Oracle 12 connection whereby the sqlnet.ora had to be updated on Server end to allow "older" versions of client to connect.

This is after connection though or at least during

gisly

Posted: Wed Sep 10, 2014 10:28 pm Post subject:

Apprentice

Joined: 10 May 2012
Posts: 29

Hi! Sorry for posting into this old thread.
Did you manage to overcome the issue?

Quote:

We first hit an issue with client connectivity in Oracle whereby the sqlnet.ora needed to be updated on Oracle side to allow older client connections.

We are now facing an issue with the connection.
Was the line you added to sqlnet.ora
SQLNET.ALLOWED_LOGON_VERSION_SERVER=8?

Display posts from previous:

Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Message Broker 7 Oracle 12 C Connectivity

Jump to:

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum

Protected by Anti-Spam ACP