infcfgcheck -a warning
All, During the infcfgcheck -a execution we are getting the following warning: parameter -- origin class... ALLOC_PAGES_TABLE_cosb -- DBGENERAL performance check?.......... N expected.................... <= 11744050 (70.0 perc) FOUND value................. 13479989 (80.3 perc) check source................ <SAP original> detail message.............. [D-060 in note '64001'] number of alloca ted pages is near to limit '16777215' We have inherited the Informix 10 FC7XC environments. Research points that you should fragment the table. But the last owner of these environments also mentioned that you could set the limit to unlimited in I10. If true can you point me in the proper direction syntax wise? Is it at the DB level or the objects level where this needs to be set? I see nothing in the onconfig file for that setting. Thanks in Advance
2008/12/16 Cappellano, John J <john.cappellano@tycoelectronics.com>: > All, > During the infcfgcheck -a execution we are getting the following warning: > > parameter -- origin class... ALLOC_PAGES_TABLE_cosb -- DBGENERAL > > performance check?.......... N > > expected.................... <= 11744050 (70.0 perc) > > FOUND value................. 13479989 (80.3 perc) > > check source................ <SAP original> > > detail message.............. [D-060 in note '64001'] number of alloca > > ted pages is near to limit '16777215' > > We have inherited the Informix 10 FC7XC environments. Research points that you > should fragment the table. But the last owner of these environments also > mentioned that you could set the limit to unlimited in I10. If true can you > point me in the proper direction syntax wise? Is it at the DB level or the > objects level where this needs to be set? I see nothing in the onconfig file > for that setting. > > Thanks in Advance > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > John The 16,7775,134 page limit per fragment is hard and fast and not changable upto and including v11.5. You have two options, fragment the table thus ahving 'no of fragments' * 16.7 milliion pages available, or move the table to a dbspace with a larger page size (you don't mention your platform so it is most likely you are on a 2k platform). You could get some sensible milage out of a dbspace with 8k pages. However, you still have over 3 million pages available, SAP seems a little aggressive with its warnings, how quickly is this table growing? Are records in it regularly removed? Will any be removed at year-end? Monitor the fragment size over the next few days/weeks and see what is happening to it, it may be the best thing is to change the warning percentages to something more sensible !! Keith
Keith, Thanks for the information. -----Original Message----- From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of Keith Simmons Sent: Tuesday, December 16, 2008 11:26 AM To: ids@iiug.org Subject: Re: infcfgcheck -a warning [14330] 2008/12/16 Cappellano, John J <john.cappellano@tycoelectronics.com>: > All, > During the infcfgcheck -a execution we are getting the following warning: > > parameter -- origin class... ALLOC_PAGES_TABLE_cosb -- DBGENERAL > > performance check?.......... N > > expected.................... <= 11744050 (70.0 perc) > > FOUND value................. 13479989 (80.3 perc) > > check source................ <SAP original> > > detail message.............. [D-060 in note '64001'] number of alloca > > ted pages is near to limit '16777215' > > We have inherited the Informix 10 FC7XC environments. Research points that you > should fragment the table. But the last owner of these environments also > mentioned that you could set the limit to unlimited in I10. If true can you > point me in the proper direction syntax wise? Is it at the DB level or the > objects level where this needs to be set? I see nothing in the onconfig file > for that setting. > > Thanks in Advance > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > John The 16,7775,134 page limit per fragment is hard and fast and not changable upto and including v11.5. You have two options, fragment the table thus ahving 'no of fragments' * 16.7 milliion pages available, or move the table to a dbspace with a larger page size (you don't mention your platform so it is most likely you are on a 2k platform). You could get some sensible milage out of a dbspace with 8k pages. However, you still have over 3 million pages available, SAP seems a little aggressive with its warnings, how quickly is this table growing? Are records in it regularly removed? Will any be removed at year-end? Monitor the fragment size over the next few days/weeks and see what is happening to it, it may be the best thing is to change the warning percentages to something more sensible !! Keith ******************************************************************************* Forum Note: Use "Reply" to post a response in the discussion forum.