<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: ODBC connection failed with fatal error. in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/odbc-connection-failed-with-fatal-error/m-p/3887386#M79710</link>
    <description>The first message tells you that the SQL Services monitor is starting to shut down.&lt;BR /&gt;The next message tells you that there was one person connected when that shutdown occurred and they are now being booted off.&lt;BR /&gt;The 3rd message occurs when the shutdown is complete.&lt;BR /&gt;&lt;BR /&gt;So you may well have picked out the wrong errors from the log - do the times match when you have the problem ?&lt;BR /&gt;&lt;BR /&gt;If so, some query could well be causing the shutdown of SQL services - although this looks pretty orderly to me.&lt;BR /&gt;&lt;BR /&gt;In sys$manager: there should be a log file for the dispatcher, which tells you more info about when clients attached and detached. Do $dir sys$manager:*sqlsrv*.log.&lt;BR /&gt;&lt;BR /&gt;There might be more info there.&lt;BR /&gt;&lt;BR /&gt;Also look for a .dmp file for SQLSRV - this might get created if SQL Services is crashing.&lt;BR /&gt;&lt;BR /&gt;If you don't find an obvious answer from the dispatcher log, then it would be best to log a call with Oracle support.&lt;BR /&gt;&lt;BR /&gt;Cheers,&lt;BR /&gt;chris</description>
    <pubDate>Thu, 26 Oct 2006 23:12:24 GMT</pubDate>
    <dc:creator>Chris Barratt</dc:creator>
    <dc:date>2006-10-26T23:12:24Z</dc:date>
    <item>
      <title>ODBC connection failed with fatal error.</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/odbc-connection-failed-with-fatal-error/m-p/3887382#M79706</link>
      <description>Hello Forum.&lt;BR /&gt;&lt;BR /&gt;One our client is connecting to RDB using ODBC connection . And the above mentioned issue occurs when query is executed only on  table with  large records.&lt;BR /&gt;&lt;BR /&gt;I can see that following errors in SQL log&lt;BR /&gt;&lt;BR /&gt;------------EVENT BEGIN:  EVENT_LOG at Mon Oct 16 2006 15:47:49.660-------------&lt;BR /&gt;%SQLSRV-I-EVENT_LOG, event logged at line 977 in file SM_OP.C;1&lt;BR /&gt;%SQLSRV-I-SM_STARTSVRSHUT, Starting server shutdown sequence&lt;BR /&gt;------------EVENT END  :  EVENT_LOG at Mon Oct 16 2006 15:47:49.660-------------&lt;BR /&gt;&lt;BR /&gt;------------EVENT BEGIN:  EVENT_LOG at Mon Oct 16 2006 15:47:49.720-------------&lt;BR /&gt;%SQLSRV-I-EVENT_LOG, event logged at line 3835 in file COM_DIALOG.C;1&lt;BR /&gt;%SQLSRV-E-READERR, Error on read&lt;BR /&gt;%SYSTEM-F-LINKDISCON, network partner disconnected logical link&lt;BR /&gt;------------EVENT END  :  EVENT_LOG at Mon Oct 16 2006 15:47:49.760-------------&lt;BR /&gt;&lt;BR /&gt;------------EVENT BEGIN:  EVENT_LOG at Mon Oct 16 2006 15:48:05.230-------------&lt;BR /&gt;%SQLSRV-I-EVENT_LOG, event logged at line 4304 in file SM_OP.C;1&lt;BR /&gt;%SQLSRV-I-SM_MONSHUT, Shutting down monitor SQLSRV_71&lt;BR /&gt;------------EVENT END  :  EVENT_LOG at Mon Oct 16 2006 15:48:05.230-------------&lt;BR /&gt;&lt;BR /&gt;But the same query is working on another node with same HW configuration and OS version with out any issues.&lt;BR /&gt;&lt;BR /&gt;I have tried to match the user job and process quotas. But no imrovement.&lt;BR /&gt;&lt;BR /&gt;Thanks&lt;BR /&gt;Shankar&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 26 Oct 2006 10:56:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/odbc-connection-failed-with-fatal-error/m-p/3887382#M79706</guid>
      <dc:creator>Jayshankar K J</dc:creator>
      <dc:date>2006-10-26T10:56:10Z</dc:date>
    </item>
    <item>
      <title>Re: ODBC connection failed with fatal error.</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/odbc-connection-failed-with-fatal-error/m-p/3887383#M79707</link>
      <description>Shankar,&lt;BR /&gt;&lt;BR /&gt;I dont know much about RDB and ODBC but the error:&lt;BR /&gt;&lt;BR /&gt;%SYSTEM-F-LINKDISCON, network partner disconnected logical link&lt;BR /&gt;&lt;BR /&gt;seems very familiar. This probably means that the client disconnected the TCPIP link. Maybe a client program crash or mallfunction?&lt;BR /&gt;&lt;BR /&gt;Bojan</description>
      <pubDate>Thu, 26 Oct 2006 11:14:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/odbc-connection-failed-with-fatal-error/m-p/3887383#M79707</guid>
      <dc:creator>Bojan Nemec</dc:creator>
      <dc:date>2006-10-26T11:14:49Z</dc:date>
    </item>
    <item>
      <title>Re: ODBC connection failed with fatal error.</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/odbc-connection-failed-with-fatal-error/m-p/3887384#M79708</link>
      <description>Are the SW versions (RDB, SQLSRV, ODBC version) identical on both sites, same network protocol?&lt;BR /&gt;Perhaps you are running into timeouts, because the database on one side is bigger, more fragmented...&lt;BR /&gt;&lt;BR /&gt;regards Kalle</description>
      <pubDate>Thu, 26 Oct 2006 11:16:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/odbc-connection-failed-with-fatal-error/m-p/3887384#M79708</guid>
      <dc:creator>Karl Rohwedder</dc:creator>
      <dc:date>2006-10-26T11:16:01Z</dc:date>
    </item>
    <item>
      <title>Re: ODBC connection failed with fatal error.</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/odbc-connection-failed-with-fatal-error/m-p/3887385#M79709</link>
      <description>Another thought: do small queries run successfully (to rule out any login problems...)?&lt;BR /&gt;&lt;BR /&gt;regards Kalle</description>
      <pubDate>Thu, 26 Oct 2006 11:17:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/odbc-connection-failed-with-fatal-error/m-p/3887385#M79709</guid>
      <dc:creator>Karl Rohwedder</dc:creator>
      <dc:date>2006-10-26T11:17:56Z</dc:date>
    </item>
    <item>
      <title>Re: ODBC connection failed with fatal error.</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/odbc-connection-failed-with-fatal-error/m-p/3887386#M79710</link>
      <description>The first message tells you that the SQL Services monitor is starting to shut down.&lt;BR /&gt;The next message tells you that there was one person connected when that shutdown occurred and they are now being booted off.&lt;BR /&gt;The 3rd message occurs when the shutdown is complete.&lt;BR /&gt;&lt;BR /&gt;So you may well have picked out the wrong errors from the log - do the times match when you have the problem ?&lt;BR /&gt;&lt;BR /&gt;If so, some query could well be causing the shutdown of SQL services - although this looks pretty orderly to me.&lt;BR /&gt;&lt;BR /&gt;In sys$manager: there should be a log file for the dispatcher, which tells you more info about when clients attached and detached. Do $dir sys$manager:*sqlsrv*.log.&lt;BR /&gt;&lt;BR /&gt;There might be more info there.&lt;BR /&gt;&lt;BR /&gt;Also look for a .dmp file for SQLSRV - this might get created if SQL Services is crashing.&lt;BR /&gt;&lt;BR /&gt;If you don't find an obvious answer from the dispatcher log, then it would be best to log a call with Oracle support.&lt;BR /&gt;&lt;BR /&gt;Cheers,&lt;BR /&gt;chris</description>
      <pubDate>Thu, 26 Oct 2006 23:12:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/odbc-connection-failed-with-fatal-error/m-p/3887386#M79710</guid>
      <dc:creator>Chris Barratt</dc:creator>
      <dc:date>2006-10-26T23:12:24Z</dc:date>
    </item>
    <item>
      <title>Re: ODBC connection failed with fatal error.</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/odbc-connection-failed-with-fatal-error/m-p/3887387#M79711</link>
      <description>oh and the dispatch log file has the name format something like,&lt;BR /&gt;&lt;BR /&gt;sqs_&lt;NODENAME&gt;_sqlsrv_dis000371.log&lt;BR /&gt;&lt;BR /&gt;the 71 is the version of Rdb&lt;BR /&gt;not sure what the 003 is, but could be different on your system.&lt;BR /&gt;&lt;/NODENAME&gt;</description>
      <pubDate>Thu, 26 Oct 2006 23:15:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/odbc-connection-failed-with-fatal-error/m-p/3887387#M79711</guid>
      <dc:creator>Chris Barratt</dc:creator>
      <dc:date>2006-10-26T23:15:52Z</dc:date>
    </item>
    <item>
      <title>Re: ODBC connection failed with fatal error.</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/odbc-connection-failed-with-fatal-error/m-p/3887388#M79712</link>
      <description>Hello Everybody,&lt;BR /&gt;&lt;BR /&gt;Many thanks for the quick responses.&lt;BR /&gt;&lt;BR /&gt;Yes, Link disconnected error occures for many reasons and always it attached with a read error, write error..etc.&lt;BR /&gt;&lt;BR /&gt;I do suspect about the idle time out, but I am not sure about it. Is that tcpip_keepalive is ON by default? And how do I check it in folllowing ucx version?&lt;BR /&gt;&lt;BR /&gt;DIGITAL TCP/IP Services for OpenVMS VAX Version V4.2 - ECO 1&lt;BR /&gt;  on a VAX 7000-730 running OpenVMS V7.1&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;And small queries works perfectly on this ODBC connection. This is query which is supposed to return almost 15000 records. But it fails after extraction of 1000+ record.&lt;BR /&gt;&lt;BR /&gt;Infact the the extract of the log messaages I have pasted is from the following log file&lt;BR /&gt;&lt;BR /&gt;SQS_ATYV02_SQLSRV_MON_00.LOG;15845&lt;BR /&gt;&lt;BR /&gt;You can see that version number us big as the system keep creating many logs everday as SQL servers dies and restarts itself.&lt;BR /&gt; &lt;BR /&gt;Any suggestions please?&lt;BR /&gt;&lt;BR /&gt;Thanks&lt;BR /&gt;Shankar&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 27 Oct 2006 03:20:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/odbc-connection-failed-with-fatal-error/m-p/3887388#M79712</guid>
      <dc:creator>Jayshankar K J</dc:creator>
      <dc:date>2006-10-27T03:20:59Z</dc:date>
    </item>
    <item>
      <title>Re: ODBC connection failed with fatal error.</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/odbc-connection-failed-with-fatal-error/m-p/3887389#M79713</link>
      <description>Shankar,&lt;BR /&gt;&lt;BR /&gt;which versions are involved (SQLSRV/RDB)? Note, that UCX V4.2 Eco1 ist quite old, there was at least a Eco5 I think.&lt;BR /&gt;&lt;BR /&gt;What does a SHOW SERVER show:&lt;BR /&gt;$ MCR SQLSRV_MANAGE71&lt;BR /&gt;SQLSRV&amp;gt;CONNECT SERVER;&lt;BR /&gt;SQLSRV&amp;gt;SHOW SERVER;&lt;BR /&gt;SQLSRV&amp;gt;SHOW SERVICE FULL;&lt;BR /&gt;&lt;BR /&gt;regards Kalle</description>
      <pubDate>Fri, 27 Oct 2006 03:35:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/odbc-connection-failed-with-fatal-error/m-p/3887389#M79713</guid>
      <dc:creator>Karl Rohwedder</dc:creator>
      <dc:date>2006-10-27T03:35:07Z</dc:date>
    </item>
    <item>
      <title>Re: ODBC connection failed with fatal error.</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/odbc-connection-failed-with-fatal-error/m-p/3887390#M79714</link>
      <description>&lt;!--!*#--&gt;Hi Kalle,&lt;BR /&gt;&lt;BR /&gt;Here we go with the output of those  SQL commands in the attached file.&lt;BR /&gt;&lt;BR /&gt;As afr as UCX ECO concerned, I have another machine, where this query works with out any issues with same ECO 1.&lt;BR /&gt;&lt;BR /&gt;regards&lt;BR /&gt;shankar</description>
      <pubDate>Fri, 27 Oct 2006 05:49:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/odbc-connection-failed-with-fatal-error/m-p/3887390#M79714</guid>
      <dc:creator>Jayshankar K J</dc:creator>
      <dc:date>2006-10-27T05:49:53Z</dc:date>
    </item>
  </channel>
</rss>

