RE: onbar log backups aborting w/TSM

Martin is the onbar king! :) I would just like to add a comment about the onsmsync utility. It is good and it works, but if you have not used it regularly, please be cautious about using it.... run it first in a test copy of your prod system because if you run it in prod when you have not done so in a long time.... well, it can create a performance issue.... Speaking from experience of course..... Norma Jean Sebastian ERP Support Administration GIS- Enterprise Technical Services -----Original Message----- From: informix-list-bounces@iiug.org [mailto:informix-list-bounces@iiug.org] On Behalf Of Martin Fuerderer Sent: Friday, December 01, 2006 9:54 AM To: Darren_Jacobs@carmax.com Cc: informix-list-bounces@iiug.org; informix-list@iiug.org Subject: Re: onbar log backups aborting w/TSM Hi, right. sysutils in rootdbs, probably some temp table (also in rootdbs) during dbspace backup uses additional space, so that you hit the ceiling ... You should not "purge" things from the sysutils database, at least not by manually connecting to the database and issuing "DELETE" statements. This can easily cause you a lot of trouble in case of a restore. What you can (and should) do (more or less regularly) is to use "onsmsync" utility to expire old backups (dbspaces and log files). This will also delete entries from the systutils database. Please see the manual "Backup and Restore Guide" for more info on "onsmsync". That will avoid this situation in the future. "oncheck -pe" shows which table has allocated how many pages, as already noted. In the short run you will probably have to add a chunk to the root dbspace to make it work again. If you don't have temp dbspaces yet, you can create some (and list them in onconfig file). It may help. It is also possible that setting PSORT_DBTEMP environment variable helps. This would cause the use of file system disk space rather than temp dbspaces (or root dbspace) for sort tasks. The backup of a log file does not only contain the log records from the log file itself, but also any BLOBSpace BLOBs that have been manipulated in corresponding transactions (log records). This is necessary because BLOBSpace BLOBs themselves are not in the logical log files. With that the backup of a log file can be much larger than the log file itself. Regards, Martin -- Martin Fuerderer IBM Informix Development Munich, Germany Information Management Informix URLs list: http://home.arcor.de/mfu1/informix/urls.html informix-list-bounces@iiug.org wrote on 01.12.2006 05:07:43: > On Thu, 30 Nov 2006 21:38:49 -0500, Darren_Jacobs@carmax.com wrote: > > > > >IDS 9.40 FC2XA > >HPUX 11.11 > > > >Greetings, > > > >I have a very interesting situation that started about a week ago. My > >onbar logical log backups are being "Aborted by client" (online.log). The > >bar_act.log file indicates "SQL 4294967025 Could not insert new row into > >table." followed by "ISAM 4294967165 ISAM error: no free disk space". > >The interesting thing is that after a onbar whole system backup completes > >all logical log files backup without issue. Another interesting thing is > >that TSM is indicating a 102 meg log file is being backed up. > > > > Sysutils database is usually in the rootdbs, along with any temp > tables that may be created there as well. > > How much space is free in rootdbs? > > How busy is rootdbs? > > Can you purge any data from the bar_?????? tables? > > JWC > _______________________________________________ > Informix-list mailing list > Informix-list@iiug.org > http://www.iiug.org/mailman/listinfo/informix-list _______________________________________________ Informix-list mailing list Informix-list@iiug.org http://www.iiug.org/mailman/listinfo/informix-list ============================================================ The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any reproduction, dissemination or distribution of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. Thank you. Tellabs ============================================================