RE: New shared memory segments,while performing a backup with ontape. Why?

One other issue that I have run into is that the docs are WRONG. The engine will only use 1 (one) temp dbspace during the archive with ontape. It appears to pick the temp space with the most room, but when that fills, the archive crashes. If you have a data dbspace that has more space, consider setting the DBSPACETEMP variable at the O/S just prior to running the ontape session. -d -----Original Message----- From: Doug Bowman [SMTP:dougb@etcscan.com] Sent: Wednesday, August 27, 1997 5:48 PM To: informix-list@rmy.emory.edu Subject: Re: New shared memory segments,while performing a backup with ontape. Why? I'm on 7.2x but I think this applies to 7.1x also. The ISAM error: no free disk space is probably due to DBSPACETEMP being filled up. Ontape creates temp tables for each dbspace that it is backing up. If you have heavy system activity during the backup you will most likely blow out your temp dbspaces, if they are too small. See the ontape chapter in the "Archive & Backup Guide" for a more detailed explaination. Doug B On Wed, 27 Aug 1997 20:31:47 +0200, Fernando Collalti <fernando.collalti@orbit.net> wrote: >Hello, > >In the last days, while performing an "ontape" backup, >the engine allocated new shared memory segments. > >During normal operational activity, the primary shared memory >segment is used on an average of 50-60%, so I think that for >now the segment is big enough. > >I would like to know which disk space, physical disk or dbspacetemps, >the error is refering to(ISAM error: no free disk space) > << snip >>