Hi, > I assume that by data area space you mean the free space > inside the set of > data volumes. Right?
yes > Following that concept, is it correct to assume that > if the problem occurs in spite of large free space in the > data volumes, > then it would be a problem with lack of indexes or the order > of the outer > joins? and yes again. Best regards, Holger > > [EMAIL PROTECTED] wrote > > > >> Is there any document/URL available providing tips to > avoid the "Table > >> space exhausted..." error in SAPDB 7.4? I have searched thru > >> this list and > >> google, and can't find a clear answer to this problem. So far > >> all I got is > >> this: > >> > >> 1.- There is a problem with the JOIN algorithm used by SAPDB > >> 7.4.x - will > >> be fixed in a future release of SAPDB 7.4? > >> > >> 2.- You should have enough indexes as to avoid bad join strategies > >> > >> 3.- The order of the tables in the FROM clause can affect the > >> occurrence > >> of this problem. > >> > >> Is there anything else regarding the CACHE_SIZE parameter > or something > >> like that? > > > > Hi, > > > > there is no special documentation or URL for this topic. > > I think beside the three points you already listed above > > the size of your data area is important. > > The CACHE_SIZE have no influence to this problem and the > > point 3 is only valid for outer joins. > > > > Kind regards, > > Holger > > SAP Labs Berlin > > > > -- > > MaxDB Discussion Mailing List > > For list archives: http://lists.mysql.com/maxdb > > To unsubscribe: > > http://lists.mysql.com/[EMAIL PROTECTED] > > > -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
