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 IndexWebSphere Message Broker SupportOdbc trace not working

Post new topicReply to topic
Odbc trace not working View previous topic :: View next topic
Author Message
vmanel
PostPosted: Fri Mar 13, 2020 10:15 am Post subject: Odbc trace not working Reply with quote

Acolyte

Joined: 12 Mar 2019
Posts: 55

Hi,

We are trying to connect to SQL DB from IIB 10.0.0.16
We are able to ping the server and telnet to port of the DB server. But when we try to execute mqsicvp command or connect from flow, the command/flow takes long time(around 20 minutes) and then throws Socket closed error. So we thought of enabling ODBC trace to check the issue, so modified /var/mqsi/odbcinst.ini file which is set in ODBCINST environment variable, with below parameters.

[ODBC]
Trace=yes
TraceFile=/tmp/odbctrace.out
Threading=2


Restarted the EG/broker and executed command/flow, but the trace is not getting generated. /tmp has full permissions as well. Tried setting other options like TraceOptions,ForceTrace,TraceDll in the file, but still trace is not getting generated. Any idea why trace is not generated? Or what could be the reason for socket closed error. Because same configurations were working in lower environment, the issue is only in production and there is no difference in versions.
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Fri Mar 13, 2020 11:41 am Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20300
Location: LI,NY

Have you made sure using telnet that a TCP connection between the IIB Server and the DB on the DB listener port is successful?
Sounds to me like a possible firewall or (asymetric) routing problem. Can the return communication reach you ?
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
vmanel
PostPosted: Fri Mar 13, 2020 8:06 pm Post subject: Reply with quote

Acolyte

Joined: 12 Mar 2019
Posts: 55

fjb_saper wrote:
Have you made sure using telnet that a TCP connection between the IIB Server and the DB on the DB listener port is successful?


Yes it is successful.
Back to top
View user's profile Send private message
vmanel
PostPosted: Sat Mar 14, 2020 12:48 am Post subject: Reply with quote

Acolyte

Joined: 12 Mar 2019
Posts: 55

This is the first time I am trying to enable ODBC trace, I tried that for another flow with some other DB which is working and even there trace is not getting generated. So, can someone please tell what are the steps to generate ODBC trace in IIB 10, I tried whatever is mentioned in the documentation and that didnt work. What is it that I am doinh wrong?
Back to top
View user's profile Send private message
mgk
PostPosted: Mon Mar 16, 2020 7:11 am Post subject: Reply with quote

Padawan

Joined: 31 Jul 2003
Posts: 1592
Location: IBM Hursley, UK

I suspect that what ever is stopping you accessing the database happens very early on before any calls that would cause ODBC trace to be written.
The last time I had a problem like this it was down to my windows firewall. I used a command like this to allow access to SQL Server from remote machines

Quote:
netsh advfirewall firewall add rule name = SQLPort dir = in protocol = tcp action = allow localport = 1433 remoteip = localsubnet profile = DOMAIN


You may need to change it to fit your environment.
_________________
MGK
IBM Global Blockchain Enablement
The postings I make on this site are my own and don't necessarily represent IBM's positions, strategies or opinions.
Back to top
View user's profile Send private message
mpong
PostPosted: Mon Mar 23, 2020 6:58 pm Post subject: Reply with quote

Disciple

Joined: 22 Jan 2010
Posts: 160

Just to give a context: I have seen Oracle RAC database having multiple IP's such as SCAN, Physical and Virtual. Unless we whitelist each one of the IP's on port 1521, mqsicvp or message flow does not connect to Database.

Is there a similar situation here?
Back to top
View user's profile Send private message
Display posts from previous:
Post new topicReply to topic Page 1 of 1

MQSeries.net Forum IndexWebSphere Message Broker SupportOdbc trace not working
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.