How does onbar use tmpdbs during a backup?

Are the statements below true : IDS7.31.UD8 and AIX 5.3. Please share your thoughts and feedbacks! Onbar  consumes  temp dbspace.  It sorts every before image page into the temp table which created for each dbspaces. Onbar  frees the temp table after the dbspace has been backed up, but with heavy activity on the instance, if there are many dbspaces with big chunks, there will not be enough temp dbspaces for completing the archive. The problem of an archive aborting with the 'Error 131,  no free disk space' error, occurs as a result of Online running out of disk space while writing pages to a temp table. A temp table for each dbspace is created when the archive process is started. These temp tables contains pages that have been modified since the archive started. After an individual dbspace is backed up, the corresponding temp table will then be backed up and dropped. This same process is repeated for each dbspace. Thanks for your anticipated answers. jp

> Onbar consumes temp dbspace. It sorts every before image page into the assume you mean stores... > A temp table > for each dbspace is created when the archive process is started. These temp > tables contains pages that have been modified since the archive started. > After an individual dbspace is backed up, the corresponding temp table will > then be backed up and dropped. This same process is repeated for each > dbspace. Yes. Remarks on running out of space: --you can create bigger temp spaces --you can use DBSPACETEMP env var to make onbar store temp stuff in dbspaces you have configured for it so that not a user who creates an index or does a big sort or creates a huge temp table kills your backup --you can backup one dbspace at a time this means that you need your trx logs!! in order to reduce the risks that you run out of temp space. Or if this takes too long or you can not configure the required space you could also look at external backup and restore. Superboer. On 1 jun, 17:32, jpier...@chubb.com wrote: > Are the statements below true : >  IDS7.31.UD8 and AIX 5.3. > > Please share your thoughts and feedbacks! > > Onbar  consumes  temp dbspace.  It sorts every before image page into the > temp table which created for each dbspaces. > > Onbar  frees the temp table after the dbspace has been backed up, but with > heavy activity on the instance, if there are many dbspaces with big chunks, > there will not be enough temp dbspaces for completing the archive. > > The problem of an archive aborting with the 'Error 131,  no free disk > space' error, occurs as a result of Online > running out of disk space while writing pages to a temp table. A temp table > for each dbspace is created when the archive process is started. These temp > tables contains pages that have been modified since the archive started. > After an individual dbspace is backed up, the corresponding temp table will > then be backed up and dropped. This same process is repeated for each > dbspace. > > Thanks for your anticipated answers. > > jp