RE: how to tune buffer allocated to index data?

Miyaki You are encountering Bug 121515 where the LRU Queues get clogged with index pages rather than being used for data pages. Work around is to export the environmental variable LRUAGE=1 in the session you use to start the engine. I'm not sure at which version this was fixed (if at all) but I am still using the parameter at 7.31 UD5 and can find no reference to it being fixed. Keith -> -----Original Message----- -> From: miyaki [mailto:lcib@yahoo.com] -> Sent: Friday, March 12, 2004 3:53 AM -> To: ids@iiug.org; informix-list@iiug.org -> Subject: how to tune buffer allocated to index data? -> -> -> Hi all, -> -> I noticed that the buffer allocated to the index data -> was extremely high in my database (version 7.31.UC2). -> May I know which parameter (in onconfig) manage this -> buffer and how to tune it? -> -> Percentages: -> Data 12.16 -> Btree 86.52 -> Other 1.32 -> -> TIA, -> Miyaki -> -> __________________________________ -> Do you Yahoo!? -> Yahoo! Search - Find what you're looking for faster -> http://search.yahoo.com -> sending to informix-list -> ******************************************************************************** ** This message is sent in strict confidence for the addressee only. It may contain legally privileged information. The contents are not to be disclosed to anyone other than the addressee. Unauthorised recipients are requested to preserve this confidentiality and to advise the sender immediately of any error in transmission. This footnote also confirms that this email message has been swept for the presence of computer viruses, however we cannot guarantee that this message is free from such problems. ******************************************************************************** **

Keith, In 7.31 and 9.21 and 9.3x setting LRUAGE is the solution for the problem. In IDS 9.4 LRUAGE has been removed from the code, the buffer manager in IDS has been redesigned in 9.4 , PTS 121515 is not an issue anymore in 9.4. With kind regards Tilman Model-Bosch -- Tilman Model-Bosch IBM Data Managment Solutions, Informix Advanced Support c\\\\o SAP AG TECHDEV 05 Neurrotstr.16 69190 Walldorf "Simmons, Keith" <keith.simmons@office2 To: ids@iiug.org office.biz> cc: Sent by: Subject: RE: how to tune buffer allocated to index data? [2663] forum.subscriber@iiug. org 03/12/2004 10:57 AM Miyaki You are encountering Bug 121515 where the LRU Queues get clogged with index pages rather than being used for data pages. Work around is to export the environmental variable LRUAGE=1 in the session you use to start the engine. I'm not sure at which version this was fixed (if at all) but I am still using the parameter at 7.31 UD5 and can find no reference to it being fixed. Keith -> -----Original Message----- -> From: miyaki [mailto:lcib@yahoo.com] -> Sent: Friday, March 12, 2004 3:53 AM -> To: ids@iiug.org; informix-list@iiug.org -> Subject: how to tune buffer allocated to index data? -> -> -> Hi all, -> -> I noticed that the buffer allocated to the index data -> was extremely high in my database (version 7.31.UC2). -> May I know which parameter (in onconfig) manage this -> buffer and how to tune it? -> -> Percentages: -> Data 12.16 -> Btree 86.52 -> Other 1.32 -> -> TIA, -> Miyaki -> -> __________________________________ -> Do you Yahoo!? -> Yahoo! Search - Find what you're looking for faster -> http://search.yahoo.com -> sending to informix-list -> ******************************************************************************** ** This message is sent in strict confidence for the addressee only. It may contain legally privileged information. The contents are not to be disclosed to anyone other than the addressee. Unauthorised recipients are requested to preserve this confidentiality and to advise the sender immediately of any error in transmission. This footnote also confirms that this email message has been swept for the presence of computer viruses, however we cannot guarantee that this message is free from such problems. ******************************************************************************** **

This bug was fixed somewhere between 7.31UC4 & UC6 IB. It's working fine here. We're running UD4 & UD6 without problems. Time to upgrade. Art S. Kagel ----- Original Message ----- From: Keith Simmons <keith.simmons@office2office.biz> At: 3/12 5:28 > Miyaki > > You are encountering Bug 121515 where the LRU Queues get clogged with index > pages rather than being used for data pages. Work around is to export the > environmental variable LRUAGE=1 in the session you use to start the engine. > I'm not sure at which version this was fixed (if at all) but I am still > using the parameter at 7.31 UD5 and can find no reference to it being fixed. > > Keith > > -> -----Original Message----- > -> From: miyaki [mailto:lcib@yahoo.com] > -> Sent: Friday, March 12, 2004 3:53 AM > -> To: ids@iiug.org; informix-list@iiug.org > -> Subject: how to tune buffer allocated to index data? > -> > -> > -> Hi all, > -> > -> I noticed that the buffer allocated to the index data > -> was extremely high in my database (version 7.31.UC2). > -> May I know which parameter (in onconfig) manage this > -> buffer and how to tune it? > -> > -> Percentages: > -> Data 12.16 > -> Btree 86.52 > -> Other 1.32 > -> > -> TIA, > -> Miyaki > -> > -> __________________________________ > -> Do you Yahoo!? > -> Yahoo! Search - Find what you're looking for faster > -> http://search.yahoo.com > -> sending to informix-list > -> > > > ******************************************************************************** > ** > This message is sent in strict confidence for the addressee only. It may > contain legally privileged information. The contents are not to be disclosed > to anyone other than the addressee. Unauthorised recipients are requested > to preserve this confidentiality and to advise the sender immediately of any > error in transmission. > This footnote also confirms that this email message has been swept for the > presence of computer viruses, however we cannot guarantee that this message > is free from such problems. > ******************************************************************************** > **