Archive and temp dbspaces
IDS 9.21 FC4 on HP-UX 11.11. Had a problem at a client site overnight. We have 3 x 1 GByte temp dbspaces defined thus: DBSPACETEMP dbspacetemp00,dbspacetemp01,dbspacetemp02 Overnight, an archive stopped to wait for a tape mount. As expected Informix started to fill temp up with modified pages ... but only dbspacetemp01! So we had the situation where dbspacetemp01 was pretty full and the other two empty. Any process that comes along to do even a modest sort attempts to use the spaces in round-robin and failes with a "No temp space for sort" error, even though there is over 2 GBytes free. Is the archive process working as it should by using only one of the three available spaces for modified pages? I have a tech support call open for this: 394351 refers. -- Neil Truby t:01932 724027 Director m:07798 811708 Ardenta Limited e:neil.truby@ardenta.com
Neil Truby wrote: > IDS 9.21 FC4 on HP-UX 11.11. > > Had a problem at a client site overnight. > > We have 3 x 1 GByte temp dbspaces defined thus: > > DBSPACETEMP dbspacetemp00,dbspacetemp01,dbspacetemp02 > > Overnight, an archive stopped to wait for a tape mount. As expected > Informix started to fill temp up with modified pages ... but only > dbspacetemp01! So we had the situation where dbspacetemp01 was pretty > full and the other two empty. > > Any process that comes along to do even a modest sort attempts to use the > spaces in round-robin and failes with a "No temp space for sort" error, > even though there is over 2 GBytes free. > > Is the archive process working as it should by using only one of the three > available spaces for modified pages? > > I have a tech support call open for this: 394351 refers. > Neil, I had the same problems in the past. It seems that only one of the temporary dbspaces is used for storing before images during the online archive. If I remember right, we created one larger temporary dbspace and set the DBSPACETEMP variable to this one ï¿œbefore starting the archive to overcome this limitation without having to increase the size of ï¿œevery temporary dbspace. However I'm not sure if the behaviour changed in the latest releases (>= 9.40). Best regards Eric -- IT-Consulting Herber *********************************************** Download the IFMX Database-Monitor for free at: http://www.herber-consulting.de/BusyBee ***********************************************
Hi, I strongly suggest to have 3 or 4 dbspaces "temp" for instance. The total size of dbspace should be (if it is possible, if you have enough disk space) be 1/3 or 2/5 of total amount of dbspaces "not temp". If you can, create only 1 chunck for each dbspace temp .... Best regards. Atts. R. Ferronato Eric Herber <eric@I-hate-spam.org> wrote in message news:<c1fvgo$qci$1@online.de>... > Neil Truby wrote: > > > IDS 9.21 FC4 on HP-UX 11.11. > > > > Had a problem at a client site overnight. > > > > We have 3 x 1 GByte temp dbspaces defined thus: > > > > DBSPACETEMP dbspacetemp00,dbspacetemp01,dbspacetemp02 > > > > Overnight, an archive stopped to wait for a tape mount. As expected > > Informix started to fill temp up with modified pages ... but only > > dbspacetemp01! So we had the situation where dbspacetemp01 was pretty > > full and the other two empty. > > > > Any process that comes along to do even a modest sort attempts to use the > > spaces in round-robin and failes with a "No temp space for sort" error, > > even though there is over 2 GBytes free. > > > > Is the archive process working as it should by using only one of the three > > available spaces for modified pages? > > > > I have a tech support call open for this: 394351 refers. > > > > Neil, > > I had the same problems in the past. It seems that only one of > the temporary dbspaces is used for storing before images > during the online archive. > > If I remember right, we created one larger temporary dbspace > and set the DBSPACETEMP variable to this one 'before starting the archive > to overcome this limitation without having to increase the size of 'every > temporary dbspace. > > However I'm not sure if the behaviour changed in the latest > releases (>= 9.40). > > Best regards > > Eric