Archive ABORTED

hi all, when i check the online.log ,i have seen the following message: 21:05:30 Archive on rootdbs, plogdbs, llogdbs, datadbs, idxdbs, = data3dbs ABORTED. also both tfgld418 and tfgld410 tables have allocated new extent ,each = 1,900,000 KB in size . now in our database the total used page in size is 79.647 GB.(it is the = the sum of rootdbs, plogdbs, llogdbs, datadbs, idxdbs, data3dbs) and the = capacity of our Archive tape is 80 GB. we are taking Level 0 archive every night,and before these tables havent = got new extend our Level 0 archives were succesful. Do you think this problem is related with free tape shortage?

Hi, it can well be a problem of tape space shortage. But first of all I would check the error message that was produced by the backup front end : - If you're using "ontape", then you have to check it's output on stdout/stderr to get more info. - if you're using ON-Bar, then check the ON-Bar Activity Log (configured in $ONCONFIG file by BAR_ACT_LOG). Tape capacity is something that can be discussed for hours without end ... Usually a tape device does some compression and often the tape vendor refers on the label of the tape to size of compressed data. Unfortunately all these are (best) guesses. The compression rate (of any data compression without actual data loss) depends on the data itself. If that data is compressed already, then applying another "round of compression" on it may actually INCREASE the size of the data. Common utilities like "gzip" nowadays recognize this and leave such data as is, not compressing it a second time ... But I don't know, what the hardware compression algorithm of your tape device is doing in such a case. In most cases where there are such lengthy discussions with customers, it turns out that they have some kind of BLOBs in their database and these BLOBs contain already-compressed data (e.g. GIF or JPEG files). During backup to a tape with (hardware) compression, it can easily happen that these BLOB data actually become bigger on tape (rather than smaller) with the net-effect that the tape capacity seems to be smaller than what the vendor claims it would be. This is due to the fact that the average compression rate over all the data cannot be achieved ... Apart from that, IDS backup only archives data pages that are in use. If a table has allocated a large extent, that does not mean that all the pages in that extent will be archived. Only those pages of the extent that are actually in use (i.e. data has been written to them) will be archived. Pages that are (still) free (empty) are not archived. Try "oncheck -pT ..." to get a more acurate picture of the pages actually used in your system ... Regards, Martin -- Martin Fuerderer IBM Informix Development Munich Data Management Solutions "Serdar Can" <scan@bellona.com.tr> Sent by: forum.subscriber@iiug.org 29.04.2003 08:44 To: ids@iiug.org cc: Subject: Archive ABORTED [1020] hi all, when i check the online.log ,i have seen the following message: 21:05:30 Archive on rootdbs, plogdbs, llogdbs, datadbs, idxdbs, = data3dbs ABORTED. also both tfgld418 and tfgld410 tables have allocated new extent ,each = 1,900,000 KB in size . now in our database the total used page in size is 79.647 GB.(it is the = the sum of rootdbs, plogdbs, llogdbs, datadbs, idxdbs, data3dbs) and the = capacity of our Archive tape is 80 GB. we are taking Level 0 archive every night,and before these tables havent = got new extend our Level 0 archives were succesful. Do you think this problem is related with free tape shortage?

Serdar What is TAPESIZE set to in your onconfig file? If this is less than your db size then ontape will stop and request a second tape. Did you have any other message in the informix log file, an archive doesn't usually abort on full tape, it just sits and waits for a second tape to be loaded. Do you have some form of tape stacker/library? If not you may have to revise your archive strategy unless you can find some way to reduce your data size to less than one tape. Keith -> -----Original Message----- -> From: Serdar Can [mailto:scan@bellona.com.tr] -> Sent: Tuesday, April 29, 2003 7:44 AM -> To: ids@iiug.org -> Subject: Archive ABORTED [1020] -> -> -> -> hi all, -> when i check the online.log ,i have seen the following message: -> 21:05:30 Archive on rootdbs, plogdbs, llogdbs, datadbs, idxdbs, = -> data3dbs ABORTED. -> -> also both tfgld418 and tfgld410 tables have allocated new -> extent ,each = -> 1,900,000 KB in size . -> now in our database the total used page in size is 79.647 -> GB.(it is the = -> the sum of rootdbs, plogdbs, llogdbs, datadbs, idxdbs, -> data3dbs) and the = -> capacity of our Archive tape is 80 GB. -> -> we are taking Level 0 archive every night,and before these -> tables havent = -> got new extend our Level 0 archives were succesful. -> Do you think this problem is related with free tape shortage? -> -> ******************************************************************************** ** This message is sent in strict confidence for the addressee only. It may contain legally privileged information. The contents are not to be disclosed to anyone other than the addressee. Unauthorised recipients are requested to preserve this confidentiality and to advise the sender immediately of any error in transmission. This footnote also confirms that this email message has been swept for the presence of computer viruses, however we cannot guarantee that this message is free from such problems. ******************************************************************************** **

our TAPESIZE is set to 80000000 and we are using ontape for archiving. when Archive aborted ,server also drop a line to the stdout as "no more extents". after aborting the archive IDS also got a Long Transaction as you see below from the online.log. After all,we did a new Archive 0 at lunch time today, and this time it was OK. 21:03:41 Logical Log 69009 Complete. 21:03:46 Logical Log 69009 - Backup Started 21:04:08 Logical Log 69009 - Backup Completed 21:05:30 Archive on rootdbs, plogdbs, llogdbs, datadbs, idxdbs, data3dbs ABORTED. 21:05:30 Aborted by client. .................. .................. 21:32:09 Logical Log 69024 - Backup Started 21:32:30 Logical Log 69024 - Backup Completed 21:33:50 Logical Log 69025 - Backup Started 21:33:50 Logical Log 69025 Complete. 21:34:10 Logical Log 69025 - Backup Completed 21:35:00 Checkpoint Completed: duration was 15 seconds. 21:35:00 Checkpoint loguniq 69026, logpos 0x19c2018 21:35:47 Checkpoint Completed: duration was 13 seconds. 21:35:47 Checkpoint loguniq 69026, logpos 0x30097e4 21:35:47 Aborting Long Transaction: tx 0xc00000003e8ef5d0 username: b2mhs1 uid: 179 21:35:51 Logical Log 69026 Complete. 21:35:55 Logical Log 69026 - Backup Started 21:36:16 Logical Log 69026 - Backup Completed 21:40:39 Logical Log 69027 Complete. 21:40:43 Logical Log 69027 - Backup Started 21:41:06 Logical Log 69027 - Backup Completed 21:41:29 Checkpoint Completed: duration was 13 seconds. 21:41:29 Checkpoint loguniq 69028, logpos 0x624018 ----- Original Message ----- From: "Simmons, Keith" <keith.simmons@bbslimited.co.uk> To: "'Serdar Can'" <scan@bellona.com.tr> Cc: <ids@iiug.org> Sent: Tuesday, April 29, 2003 11:12 Subject: RE: Archive ABORTED [1020] > Serdar > > What is TAPESIZE set to in your onconfig file? If this is less than your db > size then ontape will stop and request a second tape. > Did you have any other message in the informix log file, an archive doesn't > usually abort on full tape, it just sits and waits for a second tape to be > loaded. > Do you have some form of tape stacker/library? If not you may have to revise > your archive strategy unless you can find some way to reduce your data size > to less than one tape. > > Keith > > -> -----Original Message----- > -> From: Serdar Can [mailto:scan@bellona.com.tr] > -> Sent: Tuesday, April 29, 2003 7:44 AM > -> To: ids@iiug.org > -> Subject: Archive ABORTED [1020] > -> > -> > -> > -> hi all, > -> when i check the online.log ,i have seen the following message: > -> 21:05:30 Archive on rootdbs, plogdbs, llogdbs, datadbs, idxdbs, data3dbs ABORTED. > -> > -> also both tfgld418 and tfgld410 tables have allocated new > -> extent ,each 1,900,000 KB in size . > -> now in our database the total used page in size is 79.647 > -> GB.(it is the the sum of rootdbs, plogdbs, llogdbs, datadbs, idxdbs, data3dbs) and the > -> capacity of our Archive tape is 80 GB. > -> > -> we are taking Level 0 archive every night,and before these > -> tables havent got new extend our Level 0 archives were succesful. > -> Do you think this problem is related with free tape shortage? > -> > -> > > **************************************************************************** ****** > This message is sent in strict confidence for the addressee only. It may > contain legally privileged information. The contents are not to be disclosed > to anyone other than the addressee. Unauthorised recipients are requested > to preserve this confidentiality and to advise the sender immediately of any > error in transmission. > This footnote also confirms that this email message has been swept for the > presence of computer viruses, however we cannot guarantee that this message > is free from such problems. > **************************************************************************** ******

It sounds like you may be running out of tempspace in one of your tempdbs dbspaces during your backup. Clifton ----- Original Message ----- From: "Serdar Can" <scan@bellona.com.tr> To: <ids@iiug.org> Sent: Tuesday, April 29, 2003 10:55 AM Subject: Re: Archive ABORTED [1032] > our TAPESIZE is set to 80000000 and we are using ontape for archiving. > when Archive aborted ,server also drop a line to the stdout as "no more > extents". > > after aborting the archive IDS also got a Long Transaction as you see below > from the online.log. > After all,we did a new Archive 0 at lunch time today, and this time it was > OK. > > 21:03:41 Logical Log 69009 Complete. > 21:03:46 Logical Log 69009 - Backup Started > 21:04:08 Logical Log 69009 - Backup Completed > 21:05:30 Archive on rootdbs, plogdbs, llogdbs, datadbs, idxdbs, data3dbs > ABORTED. > 21:05:30 Aborted by client. > ................. > ................. > 21:32:09 Logical Log 69024 - Backup Started > 21:32:30 Logical Log 69024 - Backup Completed > 21:33:50 Logical Log 69025 - Backup Started > 21:33:50 Logical Log 69025 Complete. > 21:34:10 Logical Log 69025 - Backup Completed > 21:35:00 Checkpoint Completed: duration was 15 seconds. > 21:35:00 Checkpoint loguniq 69026, logpos 0x19c2018 > > 21:35:47 Checkpoint Completed: duration was 13 seconds. > 21:35:47 Checkpoint loguniq 69026, logpos 0x30097e4 > > 21:35:47 Aborting Long Transaction: tx 0xc00000003e8ef5d0 username: b2mhs1 > uid: 179 > 21:35:51 Logical Log 69026 Complete. > 21:35:55 Logical Log 69026 - Backup Started > 21:36:16 Logical Log 69026 - Backup Completed > 21:40:39 Logical Log 69027 Complete. > 21:40:43 Logical Log 69027 - Backup Started > 21:41:06 Logical Log 69027 - Backup Completed > 21:41:29 Checkpoint Completed: duration was 13 seconds. > 21:41:29 Checkpoint loguniq 69028, logpos 0x624018 > ----- Original Message ----- > From: "Simmons, Keith" <keith.simmons@bbslimited.co.uk> > To: "'Serdar Can'" <scan@bellona.com.tr> > Cc: <ids@iiug.org> > Sent: Tuesday, April 29, 2003 11:12 > Subject: RE: Archive ABORTED [1020] > > > > Serdar > > > > What is TAPESIZE set to in your onconfig file? If this is less than your > db > > size then ontape will stop and request a second tape. > > Did you have any other message in the informix log file, an archive > doesn't > > usually abort on full tape, it just sits and waits for a second tape to be > > loaded. > > Do you have some form of tape stacker/library? If not you may have to > revise > > your archive strategy unless you can find some way to reduce your data > size > > to less than one tape. > > > > Keith > > > > -> -----Original Message----- > > -> From: Serdar Can [mailto:scan@bellona.com.tr] > > -> Sent: Tuesday, April 29, 2003 7:44 AM > > -> To: ids@iiug.org > > -> Subject: Archive ABORTED [1020] > > -> > > -> > > -> > > -> hi all, > > -> when i check the online.log ,i have seen the following message: > > -> 21:05:30 Archive on rootdbs, plogdbs, llogdbs, datadbs, idxdbs, > data3dbs ABORTED. > > -> > > -> also both tfgld418 and tfgld410 tables have allocated new > > -> extent ,each 1,900,000 KB in size . > > -> now in our database the total used page in size is 79.647 > > -> GB.(it is the the sum of rootdbs, plogdbs, llogdbs, datadbs, idxdbs, > data3dbs) and the > > -> capacity of our Archive tape is 80 GB. > > -> > > -> we are taking Level 0 archive every night,and before these > > -> tables havent got new extend our Level 0 archives were succesful. > > -> Do you think this problem is related with free tape shortage? > > -> > > -> > > > > > **************************************************************************** > ****** > > This message is sent in strict confidence for the addressee only. It may > > contain legally privileged information. The contents are not to be > disclosed > > to anyone other than the addressee. Unauthorised recipients are requested > > to preserve this confidentiality and to advise the sender immediately of > any > > error in transmission. > > This footnote also confirms that this email message has been swept for the > > presence of computer viruses, however we cannot guarantee that this > message > > is free from such problems. > > > **************************************************************************** > ****** >