ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Call procedure mysql

Post new topic  Reply to topic
 Call procedure mysql « View previous topic :: View next topic » 
Author Message
ferquirino
PostPosted: Fri Oct 16, 2009 2:27 pm    Post subject: Call procedure mysql Reply with quote

Apprentice

Joined: 05 May 2008
Posts: 34
Location: São Paulo, Brazil

Hi,

I tried to call a procedure from Mysql with ESQL and ODBC driver 5.1 driver on the site of Mysql.

When performing the procedure returns an error of procedure not found in the bank.

Call Mysql:
CALL radius.TratarLinhaTelefonica('teste', 'teste')

ESQL:
CREATE PROCEDURE TratarLinhaTelefonica(
IN pUserName CHARACTER,
IN pValue CHARACTER
)LANGUAGE DATABASE
--DYNAMIC RESULT SETS 1
EXTERNAL NAME "radius.TratarLinhaTelefonica";

Error:

    ExceptionList
    RecoverableException
    File:CHARACTER:F:\build\S610_P\src\DataFlowEngine\ImbDataFlowNode.cpp
    Line:INTEGER:957
    Function:CHARACTER:ImbDataFlowNode::createExceptionList
    Type:CHARACTER:ComIbmMQInputNode
    Name:CHARACTER:br/com/ticket/operacoes/TesteProcOracle#FCMComposite_1_1
    Label:CHARACTER:br.com.ticket.operacoes.TesteProcOracle.MQInput
    Catalog:CHARACTER:BIPv610
    Severity:INTEGER:3
    Number:INTEGER:2230
    Text:CHARACTER:Node throwing exception
    RecoverableException
    File:CHARACTER:F:\build\S610_P\src\DataFlowEngine\ImbComputeNode.cpp
    Line:INTEGER:464
    Function:CHARACTER:ImbComputeNode::evaluate
    Type:CHARACTER:ComIbmComputeNode
    Name:CHARACTER:br/com/ticket/operacoes/TesteProcOracle#FCMComposite_1_2
    Label:CHARACTER:br.com.ticket.operacoes.TesteProcOracle.Compute
    Catalog:CHARACTER:BIPv610
    Severity:INTEGER:3
    Number:INTEGER:2230
    Text:CHARACTER:Caught exception and rethrowing
    RecoverableException
    File:CHARACTER:F:\build\S610_P\src\DataFlowEngine\ImbRdl\ImbRdlStatementGroup.cpp
    Line:INTEGER:612
    Function:CHARACTER:SqlStatementGroup::execute
    Type:CHARACTER:ComIbmComputeNode
    Name:CHARACTER:br/com/ticket/operacoes/TesteProcOracle#FCMComposite_1_2
    Label:CHARACTER:br.com.ticket.operacoes.TesteProcOracle.Compute
    Catalog:CHARACTER:BIPv610
    Severity:INTEGER:3
    Number:INTEGER:2488
    Text:CHARACTER:Error detected, rethrowing
    Insert
    Type:INTEGER:5
    Text:CHARACTER:br.com.ticket.operacoes.Processar_Habilitacao_Terminal_Movel_Tratar_Linha_Telefonica.Main
    Insert
    Type:INTEGER:5
    Text:CHARACTER:6.3
    Insert
    Type:INTEGER:5
    Text:CHARACTER:TratarLinhaTelefonica(Environment.DetalheMovimento[cont].DDI || Environment.DetalheMovimento[cont].DDD || Environment.DetalheMovimento[cont].Nr_Linha, Environment.DetalheMovimento[cont].Ds_Status_Linha);
    RecoverableException
    File:CHARACTER:F:\build\S610_P\src\DataFlowEngine\ImbRdl\ImbRdlRoutine.cpp
    Line:INTEGER:685
    Function:CHARACTER:SqlRoutine::invoke
    Type:CHARACTER:ComIbmComputeNode
    Name:CHARACTER:br/com/ticket/operacoes/TesteProcOracle#FCMComposite_1_2
    Label:CHARACTER:br.com.ticket.operacoes.TesteProcOracle.Compute
    Catalog:CHARACTER:BIPv610
    Severity:INTEGER:3
    Number:INTEGER:2934
    Text:CHARACTER:Error occured in procedure
    Insert
    Type:INTEGER:5
    Text:CHARACTER:TratarLinhaTelefonica
    RecoverableException
    File:CHARACTER:F:\build\S610_P\src\DataFlowEngine\ImbDatabaseManager.cpp
    Line:INTEGER:2079
    Function:CHARACTER:ImbDatabaseManager::getDBProcedureParameterInformation
    Type:CHARACTER:ComIbmDatabaseConnectionManager
    Name:CHARACTER:ComIbmDatabaseConnectionManager
    Label:CHARACTER:ComIbmDatabaseConnectionManager
    Catalog:CHARACTER:BIPv610
    Severity:INTEGER:3
    Number:INTEGER:2920
    Text:CHARACTER:The procedure is unknown to the database and no definition could be found.
    Insert
    Type:INTEGER:5
    Text:CHARACTER:RADIUS.radius.TratarLinhaTelefonica


Thanks in advance.
Back to top
View user's profile Send private message
sridhsri
PostPosted: Fri Oct 16, 2009 6:32 pm    Post subject: Reply with quote

Master

Joined: 19 Jun 2008
Posts: 297

I don't think MQSQL is a supported database. You will find the listed of supported databases here: http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27010522
Back to top
View user's profile Send private message
smdavies99
PostPosted: Fri Oct 16, 2009 10:53 pm    Post subject: Reply with quote

Jedi Council

Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.

MySql is not a supported Database but if you have the right drivers/odbc connection defined then it might work but you are certainly on your own.

Two things to do.

1) test to see if the stored proc is availble using SQL from the command line using the same username/password as defined in the ODBC connection

2) Enable ODBC trace and see what happens.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995

Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions.
Back to top
View user's profile Send private message
rameshtdp
PostPosted: Mon Jun 07, 2010 12:21 pm    Post subject: Reply with quote

Novice

Joined: 11 May 2007
Posts: 18
Location: India

Hi,
Are you using MySQL database with your broker ?
or
Are you using DB2 as database for broker and calling MySQL store procedure from application -- with the help of Java compute node?
Back to top
View user's profile Send private message
Gaya3
PostPosted: Mon Jun 07, 2010 12:49 pm    Post subject: Reply with quote

Jedi

Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US

MySQL is an Open Source DB, and not supported by Broker.

Not supported by broker means, it cant be connected as broker DB

incase application/ business is using MySQL, it is better to use Java Compute node to connect with Open Source DB.

Where java can handle the open source dbs perfectly well
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die
Back to top
View user's profile Send private message
smdavies99
PostPosted: Mon Jun 07, 2010 12:51 pm    Post subject: Reply with quote

Jedi Council

Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.

No I'm not using MySql as the Broker Db. As I said in my post, MySql is not a supported DB and is most definitely not supported as a DB for the broker (i.e. flow data etc)

As other posts have said, JDBC does work. There are plenty of examples on the internet. You just have to be prepared to do a little work and importantly LOTS of EXPERIMENTATION.

There are no OOTB solutions to your problem.

Loot for other post on calling Java from ESQL. Then you can develop a framework for your solution.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995

Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Call procedure mysql
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
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.