HPE Community read-only access December 15, 2018
This is a maintenance upgrade. You will be able to read articles and posts, but not post or reply.
Hours:
Dec 15, 4:00 am to 10:00 am UTC
Dec 14, 10:00 pm CST to Dec 15, 4:00 am CST
Dec 14, 8:00 pm PST to Dec 15, 2:00 am PST
Operating System - OpenVMS
cancel
Showing results for 
Search instead for 
Did you mean: 

ODBC connection failed with fatal error.

 
Jayshankar K J
Occasional Advisor

ODBC connection failed with fatal error.

Hello Forum.

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.

I can see that following errors in SQL log

------------EVENT BEGIN: EVENT_LOG at Mon Oct 16 2006 15:47:49.660-------------
%SQLSRV-I-EVENT_LOG, event logged at line 977 in file SM_OP.C;1
%SQLSRV-I-SM_STARTSVRSHUT, Starting server shutdown sequence
------------EVENT END : EVENT_LOG at Mon Oct 16 2006 15:47:49.660-------------

------------EVENT BEGIN: EVENT_LOG at Mon Oct 16 2006 15:47:49.720-------------
%SQLSRV-I-EVENT_LOG, event logged at line 3835 in file COM_DIALOG.C;1
%SQLSRV-E-READERR, Error on read
%SYSTEM-F-LINKDISCON, network partner disconnected logical link
------------EVENT END : EVENT_LOG at Mon Oct 16 2006 15:47:49.760-------------

------------EVENT BEGIN: EVENT_LOG at Mon Oct 16 2006 15:48:05.230-------------
%SQLSRV-I-EVENT_LOG, event logged at line 4304 in file SM_OP.C;1
%SQLSRV-I-SM_MONSHUT, Shutting down monitor SQLSRV_71
------------EVENT END : EVENT_LOG at Mon Oct 16 2006 15:48:05.230-------------

But the same query is working on another node with same HW configuration and OS version with out any issues.

I have tried to match the user job and process quotas. But no imrovement.

Thanks
Shankar

8 REPLIES
Bojan Nemec
Honored Contributor

Re: ODBC connection failed with fatal error.

Shankar,

I dont know much about RDB and ODBC but the error:

%SYSTEM-F-LINKDISCON, network partner disconnected logical link

seems very familiar. This probably means that the client disconnected the TCPIP link. Maybe a client program crash or mallfunction?

Bojan
Karl Rohwedder
Honored Contributor

Re: ODBC connection failed with fatal error.

Are the SW versions (RDB, SQLSRV, ODBC version) identical on both sites, same network protocol?
Perhaps you are running into timeouts, because the database on one side is bigger, more fragmented...

regards Kalle
Karl Rohwedder
Honored Contributor

Re: ODBC connection failed with fatal error.

Another thought: do small queries run successfully (to rule out any login problems...)?

regards Kalle
Chris Barratt
Frequent Advisor

Re: ODBC connection failed with fatal error.

The first message tells you that the SQL Services monitor is starting to shut down.
The next message tells you that there was one person connected when that shutdown occurred and they are now being booted off.
The 3rd message occurs when the shutdown is complete.

So you may well have picked out the wrong errors from the log - do the times match when you have the problem ?

If so, some query could well be causing the shutdown of SQL services - although this looks pretty orderly to me.

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.

There might be more info there.

Also look for a .dmp file for SQLSRV - this might get created if SQL Services is crashing.

If you don't find an obvious answer from the dispatcher log, then it would be best to log a call with Oracle support.

Cheers,
chris
Chris Barratt
Frequent Advisor

Re: ODBC connection failed with fatal error.

oh and the dispatch log file has the name format something like,

sqs__sqlsrv_dis000371.log

the 71 is the version of Rdb
not sure what the 003 is, but could be different on your system.
Jayshankar K J
Occasional Advisor

Re: ODBC connection failed with fatal error.

Hello Everybody,

Many thanks for the quick responses.

Yes, Link disconnected error occures for many reasons and always it attached with a read error, write error..etc.

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?

DIGITAL TCP/IP Services for OpenVMS VAX Version V4.2 - ECO 1
on a VAX 7000-730 running OpenVMS V7.1


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.

Infact the the extract of the log messaages I have pasted is from the following log file

SQS_ATYV02_SQLSRV_MON_00.LOG;15845

You can see that version number us big as the system keep creating many logs everday as SQL servers dies and restarts itself.

Any suggestions please?

Thanks
Shankar



Karl Rohwedder
Honored Contributor

Re: ODBC connection failed with fatal error.

Shankar,

which versions are involved (SQLSRV/RDB)? Note, that UCX V4.2 Eco1 ist quite old, there was at least a Eco5 I think.

What does a SHOW SERVER show:
$ MCR SQLSRV_MANAGE71
SQLSRV>CONNECT SERVER;
SQLSRV>SHOW SERVER;
SQLSRV>SHOW SERVICE FULL;

regards Kalle
Jayshankar K J
Occasional Advisor

Re: ODBC connection failed with fatal error.

Hi Kalle,

Here we go with the output of those SQL commands in the attached file.

As afr as UCX ECO concerned, I have another machine, where this query works with out any issues with same ECO 1.

regards
shankar