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.

Sybase ASE 12 and Managewise

2 posts in Windows NT Last posting was on 2001-04-18 09:30:24.0Z
Retski Posted on 2001-04-17 20:37:04.0Z
From: Retski
Date: Tue, 17 Apr 2001 16:37:04 -0400
Newsgroups: sybase.public.sqlserver.nt
Subject: Sybase ASE 12 and Managewise
Message-ID: <B22697CBE138E110007141B885256A31.007141CA85256A31@webforums>
Lines: 22
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Path: forums-1-dub!forums-master.sybase.com!forums.sybase.com!webforums.sybase.com!news
Xref: forums-1-dub sybase.public.sqlserver.nt:941
Article PK: 1087548

I would like to resolve an issue we were having with Sybase ASE 11.5 and
12. It seems that there is a conflict between Sybase and ManageWise.

It appears that ManageWise is interfering with a Sybase dll concerning
Sybase specific perfmon counters. When Sybase shuts down, ManageWise will
not release the Sybase dll involved. This in turn, is keeping Sybase or the
OS from releasing the memory that Sybase allocates (which is most of the
server memory!). As a result, Sybase could not re-start without re-cycling
the server as there was simply not enough memory left for that to happen!

Basically, the dll involved maps into Sybase's shared memory segment in
order to read internal values to report them to perfmon. Once there,
ManageWise won't let it go of it.

Sybase ASE 12.0 also can't restart because ManageWise is hanging on to that
dll. We are having to stop the SNMP service and restart it after starting
Sybase. With the new Sybase release, additional perfmon counters and
capabilities were introduced and are additional problems.

Is there any other way of getting around this problem without having to
stop SNMP every time?


Tony Imbierski Posted on 2001-04-18 09:30:24.0Z
Message-ID: <3ADD5EB0.48F6F9A8@sybase.com>
Date: Wed, 18 Apr 2001 10:30:24 +0100
From: Tony Imbierski <tonyi@sybase.com>
X-Mailer: Mozilla 4.72 [en] (Windows NT 5.0; I)
X-Accept-Language: en
MIME-Version: 1.0
Subject: Re: Sybase ASE 12 and Managewise
References: <B22697CBE138E110007141B885256A31.007141CA85256A31@webforums>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Newsgroups: sybase.public.sqlserver.nt
Lines: 57
NNTP-Posting-Host: aja.sybase.com 158.76.131.36
Path: forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.sqlserver.nt:939
Article PK: 1087545

This is a known issue and happens with other system management tools too.
However it shouldn't prevent ASE from re-starting, *unless* you increased total
memory in the config file. We detect if the shared memory is held by someone
else and issue a warning message to that effect. If the config settings are the
same as the run which created the shared memory, then the size we need will be
exactly the same, so we just map to the 'old' shared memory, zero it and start
again. If config changed and we require a smaller segment still no problem, we
just zero what we need and use it. Only if we require a larger segment are we
in trouble, as the size cannot be changed. This code went in a good 3 years ago
and so is in all the current versions. Note the dll should not be an issue -
dll's are not 'locked' when another app maps them in, they are shareable at all
times.

cheers, HTH
tonyi (ASE engineering)

Retski wrote:

> I would like to resolve an issue we were having with Sybase ASE 11.5 and
> 12. It seems that there is a conflict between Sybase and ManageWise.
>
> It appears that ManageWise is interfering with a Sybase dll concerning
> Sybase specific perfmon counters. When Sybase shuts down, ManageWise will
> not release the Sybase dll involved. This in turn, is keeping Sybase or the
> OS from releasing the memory that Sybase allocates (which is most of the
> server memory!). As a result, Sybase could not re-start without re-cycling
> the server as there was simply not enough memory left for that to happen!
>
> Basically, the dll involved maps into Sybase's shared memory segment in
> order to read internal values to report them to perfmon. Once there,
> ManageWise won't let it go of it.
>
> Sybase ASE 12.0 also can't restart because ManageWise is hanging on to that
> dll. We are having to stop the SNMP service and restart it after starting
> Sybase. With the new Sybase release, additional perfmon counters and
> capabilities were introduced and are additional problems.
>
> Is there any other way of getting around this problem without having to
> stop SNMP every time?

--
Tony Imbierski
Sybase Engineering

-- how much daylight did you save today? --