dbTalk Databases Forums  

How does onbar use tmpdbs during a backup?

comp.databases.informix comp.databases.informix


Discuss How does onbar use tmpdbs during a backup? in the comp.databases.informix forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
jpierrot@chubb.com
 
Posts: n/a

Default How does onbar use tmpdbs during a backup? - 06-01-2010 , 10:32 AM






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, butwith
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

Reply With Quote
  #2  
Old   
Superboer
 
Posts: n/a

Default Re: How does onbar use tmpdbs during a backup? - 06-02-2010 , 01:33 AM






Quote:
Onbar consumes temp dbspace. It sorts every before image page into the
assume you mean stores...


Quote:
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... (AT) chubb (DOT) com wrote:
Quote:
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

Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.