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.

High cpu usage?

3 posts in NT Last posting was on 2011-08-23 19:43:20.0Z
Alex Schaft Posted on 2011-08-23 10:00:48.0Z
Date: Tue, 23 Aug 2011 12:00:48 +0200
From: Alex Schaft <alexs@quicksoftware.co.za>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
Newsgroups: Advantage.NT
Subject: High cpu usage?
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: 196.36.8.34
Message-ID: <4e537ac9@solutions.advantagedatabase.com>
X-Trace: 23 Aug 2011 03:02:49 -0700, 196.36.8.34
Lines: 13
Path: solutions.advantagedatabase.com
Xref: solutions.advantagedatabase.com Advantage.NT:1843
Article PK: 1130956

Hi,

We have a client on 10.10.0.17 with very high cpu usage after a hardware
issue caused the server to reboot, in turn causing architect and other
apps unable to start.

We're still running on dbf/cdx at this time. What is the easiest way to
determine what's causing the high cpu usage? Last time this happened it
was a bad cdx file.


Thanks,
Alex


Alex Schaft Posted on 2011-08-23 10:19:15.0Z
Date: Tue, 23 Aug 2011 12:19:15 +0200
From: Alex Schaft <alexs@quicksoftware.co.za>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
Newsgroups: Advantage.NT
Subject: Re: High cpu usage?
References: <4e537ac9@solutions.advantagedatabase.com>
In-Reply-To: <4e537ac9@solutions.advantagedatabase.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: 196.36.8.34
Message-ID: <4e537f1b@solutions.advantagedatabase.com>
X-Trace: 23 Aug 2011 03:21:15 -0700, 196.36.8.34
Lines: 17
Path: solutions.advantagedatabase.com
Xref: solutions.advantagedatabase.com Advantage.NT:1844
Article PK: 1130961

Worker threads hit a limit of 20 as well

On 2011/08/23 12:00 PM, Alex Schaft wrote:
> Hi,
>
> We have a client on 10.10.0.17 with very high cpu usage after a hardware
> issue caused the server to reboot, in turn causing architect and other
> apps unable to start.
>
> We're still running on dbf/cdx at this time. What is the easiest way to
> determine what's causing the high cpu usage? Last time this happened it
> was a bad cdx file.
>
>
> Thanks,
> Alex


Edgar Sherman Posted on 2011-08-23 19:43:20.0Z
Date: Tue, 23 Aug 2011 13:43:20 -0600
From: Edgar Sherman <no@email.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
Newsgroups: Advantage.NT
Subject: Re: High cpu usage?
References: <4e537ac9@solutions.advantagedatabase.com> <4e537f1b@solutions.advantagedatabase.com>
In-Reply-To: <4e537f1b@solutions.advantagedatabase.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: 10.6.193.121
Message-ID: <4e5402aa@solutions.advantagedatabase.com>
X-Trace: 23 Aug 2011 12:42:34 -0700, 10.6.193.121
Lines: 25
Path: solutions.advantagedatabase.com
Xref: solutions.advantagedatabase.com Advantage.NT:1845
Article PK: 1130960

You might check the error log and look for errors 7154/7156.

If the server (ADS) was not shutdown cleanly (i.e. System Crash), any
open indexes will be "dirty" and require a rebuild.

Edgar

On 8/23/2011 4:19 AM, Alex Schaft wrote:
> Worker threads hit a limit of 20 as well
>
> On 2011/08/23 12:00 PM, Alex Schaft wrote:
>> Hi,
>>
>> We have a client on 10.10.0.17 with very high cpu usage after a hardware
>> issue caused the server to reboot, in turn causing architect and other
>> apps unable to start.
>>
>> We're still running on dbf/cdx at this time. What is the easiest way to
>> determine what's causing the high cpu usage? Last time this happened it
>> was a bad cdx file.
>>
>>
>> Thanks,
>> Alex
>