Unix Technical Forum

QSF memory use

This is a discussion on QSF memory use within the Ingres forums, part of the Database Server Software category; --> Here's an oddity. It doesn't look like overflow/wraparound. I shall raise it with tech support but the system hasn't ...


Go Back   Unix Technical Forum > Database Server Software > Ingres

FAQ Members List Calendar Search Today's Posts Mark Forums Read
  #1 (permalink)  
Old 04-20-2008, 10:05 PM
Roy Hann
 
Posts: n/a
Default QSF memory use

Here's an oddity. It doesn't look like overflow/wraparound. I shall raise
it with tech support but the system hasn't misbehaved at all.

bigco-prod::ingres# sql bchd
INGRES TERMINAL MONITOR Copyright 2003 Ingres Corporation
Ingres SPARC SOLARIS Version II 2.6/0305 (su4.us5/00) login
Tue Nov 20 12:09:28 2007

continue
* set trace point qs501
* \p\g
/* SQL Startup File */
set trace point qs501
Executing . . .


************************************************** ******************
Tue Nov 20 12:09:40 2007 E_QS0500_INFO_REQ QSF info request #501:
QSF memleft = 84581136
total memory = 56200000
% used = -50.50
************************************************** ******************

Roy


Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #2 (permalink)  
Old 04-20-2008, 10:05 PM
Paul Mason
 
Posts: n/a
Default Re: [Info-Ingres] QSF memory use

On 20/11/2007, Roy Hann <specially@processed.almost.meat> wrote:
>
> Here's an oddity. It doesn't look like overflow/wraparound. I shall
> raise
> it with tech support but the system hasn't misbehaved at all.
>
> bigco-prod::ingres# sql bchd
> INGRES TERMINAL MONITOR Copyright 2003 Ingres Corporation
> Ingres SPARC SOLARIS Version II 2.6/0305 (su4.us5/00) login
> Tue Nov 20 12:09:28 2007
>
> continue
> * set trace point qs501
> * \p\g
> /* SQL Startup File */
> set trace point qs501
> Executing . . .
>
>
> ************************************************** ******************
> Tue Nov 20 12:09:40 2007 E_QS0500_INFO_REQ QSF info request #501:
> QSF memleft = 84581136
> total memory = 56200000
> % used = -50.50
> ************************************************** ******************
>
> Roy
>


Yes, log a tech support call and tell them you're hitting bug 108054.

Regards
--
Paul Mason

Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #3 (permalink)  
Old 04-20-2008, 10:05 PM
Martin Bowes
 
Posts: n/a
Default Re: [Info-Ingres] QSF memory use

Hi Roy,

I've used qs501 extensivle for years and have never seen that before!

Marty

-----Original Message-----
From: info-ingres-bounces@kettleriverconsulting.com
[mailto:info-ingres-bounces@kettleriverconsulting.com] On Behalf Of Roy
Hann
Sent: 20 November 2007 13:18
To: info-ingres@kettleriverconsulting.com
Subject: [Info-Ingres] QSF memory use

Here's an oddity. It doesn't look like overflow/wraparound. I shall
raise
it with tech support but the system hasn't misbehaved at all.

bigco-prod::ingres# sql bchd
INGRES TERMINAL MONITOR Copyright 2003 Ingres Corporation
Ingres SPARC SOLARIS Version II 2.6/0305 (su4.us5/00) login
Tue Nov 20 12:09:28 2007

continue
* set trace point qs501
* \p\g
/* SQL Startup File */
set trace point qs501
Executing . . .


************************************************** ******************
Tue Nov 20 12:09:40 2007 E_QS0500_INFO_REQ QSF info request #501:
QSF memleft = 84581136
total memory = 56200000
% used = -50.50
************************************************** ******************

Roy


_______________________________________________
Info-Ingres mailing list
Info-Ingres@kettleriverconsulting.com
http://www.kettleriverconsulting.com...fo/info-ingres

Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #4 (permalink)  
Old 04-20-2008, 10:05 PM
=?iso-8859-1?Q?Laframboise_Andr=E9?=
 
Posts: n/a
Default Re: [Info-Ingres] QSF memory use

I've seen a similar problem with the logstat output.

The output field width is not big enough and the real value is being truncated.

Maybe that's the case for the 'total memory' display.

Andre

________________________________

From: info-ingres-bounces@kettleriverconsulting.com on behalf of Martin Bowes
Sent: Tue 20/11/2007 8:56 AM
To: Roy Hann; info-ingres@kettleriverconsulting.com
Subject: Re: [Info-Ingres] QSF memory use



Hi Roy,

I've used qs501 extensivle for years and have never seen that before!

Marty

-----Original Message-----
From: info-ingres-bounces@kettleriverconsulting.com
[mailto:info-ingres-bounces@kettleriverconsulting.com] On Behalf Of Roy
Hann
Sent: 20 November 2007 13:18
To: info-ingres@kettleriverconsulting.com
Subject: [Info-Ingres] QSF memory use

Here's an oddity. It doesn't look like overflow/wraparound. I shall
raise
it with tech support but the system hasn't misbehaved at all.

bigco-prod::ingres# sql bchd
INGRES TERMINAL MONITOR Copyright 2003 Ingres Corporation
Ingres SPARC SOLARIS Version II 2.6/0305 (su4.us5/00) login
Tue Nov 20 12:09:28 2007

continue
* set trace point qs501
* \p\g
/* SQL Startup File */
set trace point qs501
Executing . . .


************************************************** ******************
Tue Nov 20 12:09:40 2007 E_QS0500_INFO_REQ QSF info request #501:
QSF memleft = 84581136
total memory = 56200000
% used = -50.50
************************************************** ******************

Roy


_______________________________________________
Info-Ingres mailing list
Info-Ingres@kettleriverconsulting.com
http://www.kettleriverconsulting.com...fo/info-ingres

_______________________________________________
Info-Ingres mailing list
Info-Ingres@kettleriverconsulting.com
http://www.kettleriverconsulting.com...fo/info-ingres



Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #5 (permalink)  
Old 04-20-2008, 10:05 PM
Roy Hann
 
Posts: n/a
Default Re: [Info-Ingres] QSF memory use


"Laframboise André" <andre.laframboise@lac-bac.gc.ca> wrote in message
news:mailman.111.1195567266.18164.info-ingres@kettleriverconsulting.com...
> I've seen a similar problem with the logstat output.
>
> The output field width is not big enough and the real value is being
> truncated.
>
> Maybe that's the case for the 'total memory' display.


Not in this case. The total memory is just what it should be.

I think Paul Mason's posting gives the likeliest explanation.

Roy


Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
Reply


Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On
Forum Jump


All times are GMT. The time now is 06:46 AM.


Powered by vBulletin® Version 3.6.5
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
SEO by vBSEO 3.2.0
www.UnixAdminTalk.com