Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

Lock up?

6 posts in Performance and Tuning Last posting was on 2007-11-19 20:52:42.0Z
Paul Womack Posted on 2007-11-16 16:40:09.0Z
From: Paul Womack <bugbear@diss.papermule.co.uk>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.12) Gecko/20070530 Fedora/1.0.9-1.fc5 SeaMonkey/1.0.9
MIME-Version: 1.0
Newsgroups: sybase.public.ase.performance+tuning
Subject: Lock up?
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: papermule.plus.com
X-Original-NNTP-Posting-Host: papermule.plus.com
Message-ID: <473dc7e9$1@forums-1-dub>
Date: 16 Nov 2007 08:40:09 -0800
X-Trace: forums-1-dub 1195231209 212.159.73.74 (16 Nov 2007 08:40:09 -0800)
X-Original-Trace: 16 Nov 2007 08:40:09 -0800, papermule.plus.com
Lines: 33
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.ase.performance+tuning:10472
Article PK: 89096

We have a Solaris Machine (SunOs 5.8/Solaris 8)
running Sybase 11.9.2

Both products are effectively legacy,
and out of maintainance.

Sometimes Sybase simply LOCKs. We cannot connect
in order to get any stats or reports from it
(making analysis difficult).

We have (thus far) failed to spot any incremental
difficulties prior to these lock ups.

A full dbcc check reports nothing amiss.

I am aware that diagnosis from these
thin facts is impossible.

Our present solution is to kill -9
Sybase, and hope that Sybase will restart.

Which it has so far. This is not comforting.

Is there anything more detailed/thorough than
dbcc?

Is there anything (simple!) we can look at
from the Unix side to work out what
Sybase is up to during a lock?

Any suggestions welcomed.

BugBear


Paul Womack Posted on 2007-11-16 16:59:47.0Z
From: Paul Womack <bugbear@diss.papermule.co.uk>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.12) Gecko/20070530 Fedora/1.0.9-1.fc5 SeaMonkey/1.0.9
MIME-Version: 1.0
Newsgroups: sybase.public.ase.performance+tuning
Subject: Re: Lock up?
References: <473dc7e9$1@forums-1-dub>
In-Reply-To: <473dc7e9$1@forums-1-dub>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: papermule.plus.com
X-Original-NNTP-Posting-Host: papermule.plus.com
Message-ID: <473dcc83$1@forums-1-dub>
Date: 16 Nov 2007 08:59:47 -0800
X-Trace: forums-1-dub 1195232387 212.159.73.74 (16 Nov 2007 08:59:47 -0800)
X-Original-Trace: 16 Nov 2007 08:59:47 -0800, papermule.plus.com
Lines: 16
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.ase.performance+tuning:10473
Article PK: 89097


Paul Womack wrote:
> A full dbcc check reports nothing amiss.

Specifically:
dbcc checkalloc (maps_db)
go
dbcc checktable (maps_db)
go
dbcc checkdb (maps_db)
go
dbcc checkcatalog (maps_db)
go
sp_dboption maps_db,"single user",false
go

BugBear


SybaseNeal Posted on 2007-11-19 20:52:42.0Z
From: SybaseNeal <nstack@nospam.com>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
Newsgroups: sybase.public.ase.performance+tuning
Subject: Re: Lock up?
References: <473dc7e9$1@forums-1-dub>
In-Reply-To: <473dc7e9$1@forums-1-dub>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: nstackxp.sybase.com
X-Original-NNTP-Posting-Host: nstackxp.sybase.com
Message-ID: <4741f79a$1@forums-1-dub>
Date: 19 Nov 2007 12:52:42 -0800
X-Trace: forums-1-dub 1195505562 10.20.19.203 (19 Nov 2007 12:52:42 -0800)
X-Original-Trace: 19 Nov 2007 12:52:42 -0800, nstackxp.sybase.com
Lines: 46
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.ase.performance+tuning:10477
Article PK: 89098

Hello,

I'm a little confused but it sounds like no new connections can
be made to this server to perform diagnostics but existing
connections can issue commands such as "dbcc". Is this correct?

It could be one of the following Sun issues. I think getting
"pstack" output of the hung server as others have suggested would
be the first step in determining if you are hitting one of these
known issues:

4924525 - TLI Interface issue
=============================
On Solaris, with ASE 12.5.1 ESD#2 or later, using tli type entries in interfaces file used by ASE,
when a spid within ASE is killed ('kill <spid>') it could result in ASE hang.
Running pstack (unix command) on ASE pid would show functions kill_proc, drop_connection, tli_nclose,
_tx_getinfo, _t_do_ioctl, ioctl on the stack. This problem is due to Solaris bug # 4924525.
If you are using tli type entries in the interfaces file that is used by ASE contact SUN
quoting Sun BugID 4924525 and request a patch (110955-05 or later) to fix the problem.

http://sunsolve.sun.com/search/document.do?assetkey=1-1-4924525-1


6243697 - TCP Listener hangs
============================
We tracked this issue in Sybase CR 432111.

The cases who ran into this Solaris bug had the following symptoms in common:
1. kpsched scheduler was running on the hanging engine
2. eachkioticks was much smaller than eaclock_ticks for the hanging ENGINE output
3. some process was running BULK INSERT in who output

In the pstack output we would look for ncheck_checkconn() calling recv() and
the final parameter for recv() being set to 2:
% pstack 3253
3253: /stars/sybase/ASE-12_5/ASE-12_5/bin/dataserver -d/stars/sybase/ASE-12_
----------------- lwp# 1 / thread# 1 --------------------
ffffffff7d9a5e78 recv (67, 10001135a8f, 1, 2)
00000000808d2974 ncheck_checkconn (100000e03d8, 10001136028, 9d, 10001136a08, 9d, 2) + 80
00000000802231d8 soc_ncheck (100002c5140, 69, 100000e03d8, 15c0, 1000, 1400) +32c
0000000080211298 kpcheckio (8186f400, 81284c00, 0, 1, 1000e494800, 5c) + 1c0
00000000801e05cc kpsched (100000d0740, 0, 8186f510, 1528, 10225184000, 1) + 314
000000008090914c _coldstart (0, 801e02b8, 0, 0, 0, 0)
0000000000000000 ???????? (0, 0, 0, 0, 0, 0)

http://sunsolve.sun.com/search/document.do?assetkey=1-1-6243697-1


"Mark A. Parsons" <iron_horse Posted on 2007-11-17 00:32:04.0Z
From: "Mark A. Parsons" <iron_horse@no_spamola.compuserve.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
Newsgroups: sybase.public.ase.performance+tuning
Subject: Re: Lock up?
References: <473dc7e9$1@forums-1-dub>
In-Reply-To: <473dc7e9$1@forums-1-dub>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: ool-4357fce9.dyn.optonline.net
X-Original-NNTP-Posting-Host: ool-4357fce9.dyn.optonline.net
Message-ID: <473e3684$1@forums-1-dub>
Date: 16 Nov 2007 16:32:04 -0800
X-Trace: forums-1-dub 1195259524 67.87.252.233 (16 Nov 2007 16:32:04 -0800)
X-Original-Trace: 16 Nov 2007 16:32:04 -0800, ool-4357fce9.dyn.optonline.net
Lines: 57
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.ase.performance+tuning:10474
Article PK: 89099

Anything in the ASE errorlog?

Complete @@version string?

When you say it LOCKs, does this also mean that anyone (or any process) currently logged into the dataserver also sees
their session freeze? Are they kicked out of the dataserver or do they just lose all responsiveness from the dataserver?

Does anything show up the OS system logs?

Does OS monitoring prior to the lock up show any kind of ramp up in system resource usage (eg, memory, swap, cpu, etc)?
Are there any noticeable differences in OS resource usage just prior to the 'kill -9', just after the 'kill -9'?

Does ASE performance gradually degrade until it locks up, or does it just lock up 'out of the blue'?

Does the ASE regularly lock up after a certain amount of uptime? or after any specific jobs/queries/processes run
against the dataserver?

Any plans in place to migrate to a newer OS/hardware/ASE version in the near future? and if not, why not? (Just
curious about any technical and/or business issues as to why you can't upgrade; yeah, I know, if it ain't broke then
don't fix it ... then again, sounds like something's broke, eh?)

Paul Womack wrote:
> We have a Solaris Machine (SunOs 5.8/Solaris 8)
> running Sybase 11.9.2
>
> Both products are effectively legacy,
> and out of maintainance.
>
> Sometimes Sybase simply LOCKs. We cannot connect
> in order to get any stats or reports from it
> (making analysis difficult).
>
> We have (thus far) failed to spot any incremental
> difficulties prior to these lock ups.
>
> A full dbcc check reports nothing amiss.
>
> I am aware that diagnosis from these
> thin facts is impossible.
>
> Our present solution is to kill -9
> Sybase, and hope that Sybase will restart.
>
> Which it has so far. This is not comforting.
>
> Is there anything more detailed/thorough than
> dbcc?
>
> Is there anything (simple!) we can look at
> from the Unix side to work out what
> Sybase is up to during a lock?
>
> Any suggestions welcomed.
>
> BugBear


Mark K Posted on 2007-11-17 05:13:52.0Z
From: "Mark K" <xxxx>
Newsgroups: sybase.public.ase.performance+tuning
References: <473dc7e9$1@forums-1-dub>
Subject: Re: Lock up?
Lines: 43
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
X-RFC2646: Format=Flowed; Response
NNTP-Posting-Host: vpn-concord-034.sybase.com
X-Original-NNTP-Posting-Host: vpn-concord-034.sybase.com
Message-ID: <473e7890$1@forums-1-dub>
Date: 16 Nov 2007 21:13:52 -0800
X-Trace: forums-1-dub 1195276432 158.159.8.34 (16 Nov 2007 21:13:52 -0800)
X-Original-Trace: 16 Nov 2007 21:13:52 -0800, vpn-concord-034.sybase.com
X-Authenticated-User: techsupp
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.ase.performance+tuning:10476
Article PK: 89100

When it happens again, you can run pstack against the dataserver pid(s). If
you have a support contract, you can capture a manual memory dump and open a
case.

Mark Kusma

"Paul Womack" <bugbear@diss.papermule.co.uk> wrote in message
news:473dc7e9$1@forums-1-dub...
> We have a Solaris Machine (SunOs 5.8/Solaris 8)
> running Sybase 11.9.2
>
> Both products are effectively legacy,
> and out of maintainance.
>
> Sometimes Sybase simply LOCKs. We cannot connect
> in order to get any stats or reports from it
> (making analysis difficult).
>
> We have (thus far) failed to spot any incremental
> difficulties prior to these lock ups.
>
> A full dbcc check reports nothing amiss.
>
> I am aware that diagnosis from these
> thin facts is impossible.
>
> Our present solution is to kill -9
> Sybase, and hope that Sybase will restart.
>
> Which it has so far. This is not comforting.
>
> Is there anything more detailed/thorough than
> dbcc?
>
> Is there anything (simple!) we can look at
> from the Unix side to work out what
> Sybase is up to during a lock?
>
> Any suggestions welcomed.
>
> BugBear


A. M. Posted on 2007-11-17 04:32:23.0Z
Message-ID: <473E6ED8.80EA5358@gmail.com>
From: "A. M." <amforums@gmail.com>
X-Mailer: Mozilla 4.61 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
Newsgroups: sybase.public.ase.performance+tuning
Subject: Re: Lock up?
References: <473dc7e9$1@forums-1-dub>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
NNTP-Posting-Host: cust4138.nsw01.dataco.com.au
X-Original-NNTP-Posting-Host: cust4138.nsw01.dataco.com.au
Date: 16 Nov 2007 20:32:23 -0800
X-Trace: forums-1-dub 1195273943 203.171.77.42 (16 Nov 2007 20:32:23 -0800)
X-Original-Trace: 16 Nov 2007 20:32:23 -0800, cust4138.nsw01.dataco.com.au
Lines: 44
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.ase.performance+tuning:10475
Article PK: 89101


Paul Womack wrote:
>
> We have a Solaris Machine (SunOs 5.8/Solaris 8)
> running Sybase 11.9.2
>
> Both products are effectively legacy,
> and out of maintainance.

Solaris 8 is still supported by Sun. Depending on how
old the hardware is, it might still be supported as well.
A search on Sun's web site will provide a definitive
answer on that.

> Sometimes Sybase simply LOCKs. We cannot connect
> in order to get any stats or reports from it
> (making analysis difficult).
>
> We have (thus far) failed to spot any incremental
> difficulties prior to these lock ups.
>
> A full dbcc check reports nothing amiss.
>
> I am aware that diagnosis from these
> thin facts is impossible.
>
> Our present solution is to kill -9
> Sybase, and hope that Sybase will restart.
>
> Which it has so far. This is not comforting.
>
> Is there anything more detailed/thorough than
> dbcc?

If its the bug I think it is, its nothing to do
with Sybase. Earlier versions of Solaris 8 had a
bug that hit Sybase. One symptom would be that
ASE didn't shutdown (i.e. it locks up).

You'll need to install a later kernel patch. I
think you may need a Sun support contract for this.
Check what it says on the SunSolve web site (I
know they have some free patches).

-am © 2007