<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>Question Re: DB2 backup query in Technology Q&amp;A</title>
    <link>https://community.sap.com/t5/technology-q-a/db2-backup-query/qaa-p/8328600#M2963575</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;May be you are right....upon looking at the diag log further, I found the following&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;FUNCTION: DB2 UDB, Automatic Table Maintenance, AtmTable::runstats, probe:900&lt;/P&gt;&lt;P&gt;...skipping...&lt;/P&gt;&lt;P&gt;FUNCTION: DB2 UDB, database application extension for utili, adminListHist, probe:301&lt;/P&gt;&lt;P&gt;DATA #1 : &amp;lt;preformatted&amp;gt;&lt;/P&gt;&lt;P&gt;The recovery history file has been pruned since this&lt;/P&gt;&lt;P&gt;query began.  Query stopped.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Looks the automatic stats job has pruned the history file. But the ibm help says, the  most recent full database backup plus its restore set will always be kept, unless you use the PRUNE utility with the FORCE option.  I am wondering how Automatic table maintenance uses force in this equation. Do you know any inherent setting within the Automatic Table Maintenance that controls this besides the actual DB2 parameters NUM_DB_BACKUPS and REC_HIS_RETENTN&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Kal&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 22 Nov 2011 07:00:02 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2011-11-22T07:00:02Z</dc:date>
    <item>
      <title>DB2 backup query</title>
      <link>https://community.sap.com/t5/technology-q-a/db2-backup-query/qaq-p/8328595</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;In DBACOCKPIT, the database backup section is empty although a DB online backup has run last night. Till yesterday, it was visible. When I check from DB2 Level using db2 LIST HISTORY BACKUP SINCE 20111117 FOR XXX, it returns no matching entries. However surprisingly, when I issue db2 get snapshot for db on XXX, it does state that there was a backup run on 17th with the exact same timestamp as the SAP background job time stamp. The backup runs as Backup ground job with an OS command db2 backup database DB online to tape via netbackup utilities. I am wondering what could be the problem here.  Another point to note here is this applies only to the database backup, there is no problem with the log file backup as I can see them via DB12. May be database and log file backup write to different DB tables. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;db2diag.log shows backup run as per schedule.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Parameters num_db_backups is set to 12,rec_his_retentn is 60 and auto_del_rec_obj is not set&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any thoughts how could the db backup history could have been wiped out. Are there any other command utilities that can delete the history interactively and if so how can I trace it back to it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;One final thing, we have run the online backup without including logs. Do you think this could have any impact at all.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Kal&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 18 Nov 2011 10:50:36 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/db2-backup-query/qaq-p/8328595</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2011-11-18T10:50:36Z</dc:date>
    </item>
    <item>
      <title>Re: DB2 backup query</title>
      <link>https://community.sap.com/t5/technology-q-a/db2-backup-query/qaa-p/8328596#M2963571</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;gt;&amp;gt; One final thing, we have run the online backup without including logs. Do you think this could have any impact at all.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This doesn't impact.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Did this problem (backup history wiped out) happen just once or does it happen everyday ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any parameter in netbackup utility to check and confirm ? Not sure , I never worked on netbackup.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 18 Nov 2011 11:00:23 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/db2-backup-query/qaa-p/8328596#M2963571</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2011-11-18T11:00:23Z</dc:date>
    </item>
    <item>
      <title>Re: DB2 backup query</title>
      <link>https://community.sap.com/t5/technology-q-a/db2-backup-query/qaa-p/8328597#M2963572</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This has not happened atleast in the last six months and I dont know before that as I was supporting oracle databases before that.  It was fine until last night something must have been set off last night and was done probably interactively, not sure how I can track it back to that. Netbackup utilities do not write into the DB2 database actually, the command line just points the backup to be directed to tape.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Kal&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 18 Nov 2011 11:15:28 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/db2-backup-query/qaa-p/8328597#M2963572</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2011-11-18T11:15:28Z</dc:date>
    </item>
    <item>
      <title>Re: DB2 backup query</title>
      <link>https://community.sap.com/t5/technology-q-a/db2-backup-query/qaa-p/8328598#M2963573</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Not sure if someone had executed db2 prune history.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But this is strange that only the full backup history went away, not the log backup.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Let's scan db2diag.log once more to see something latest.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 18 Nov 2011 11:22:35 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/db2-backup-query/qaa-p/8328598#M2963573</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2011-11-18T11:22:35Z</dc:date>
    </item>
    <item>
      <title>Re: DB2 backup query</title>
      <link>https://community.sap.com/t5/technology-q-a/db2-backup-query/qaa-p/8328599#M2963574</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;May be you are right....upon looking at the diag log further, I found the following&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;FUNCTION: DB2 UDB, Automatic Table Maintenance, AtmTable::runstats, probe:900&lt;/P&gt;&lt;P&gt;...skipping...&lt;/P&gt;&lt;P&gt;FUNCTION: DB2 UDB, database application extension for utili, adminListHist, probe:301&lt;/P&gt;&lt;P&gt;DATA #1 : &amp;lt;preformatted&amp;gt;&lt;/P&gt;&lt;P&gt;The recovery history file has been pruned since this&lt;/P&gt;&lt;P&gt;query began.  Query stopped.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Looks the automatic stats job has pruned the history file. But the ibm help says, the  most recent full database backup plus its restore set will always be kept, unless you use the PRUNE utility with the FORCE option.  I am wondering how Automatic table maintenance uses force in this equation. Do you know any inherent setting within the Automatic Table Maintenance that controls this besides the actual DB2 parameters NUM_DB_BACKUPS and REC_HIS_RETENTN&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Kal&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 22 Nov 2011 06:59:45 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/db2-backup-query/qaa-p/8328599#M2963574</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2011-11-22T06:59:45Z</dc:date>
    </item>
    <item>
      <title>Re: DB2 backup query</title>
      <link>https://community.sap.com/t5/technology-q-a/db2-backup-query/qaa-p/8328600#M2963575</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;May be you are right....upon looking at the diag log further, I found the following&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;FUNCTION: DB2 UDB, Automatic Table Maintenance, AtmTable::runstats, probe:900&lt;/P&gt;&lt;P&gt;...skipping...&lt;/P&gt;&lt;P&gt;FUNCTION: DB2 UDB, database application extension for utili, adminListHist, probe:301&lt;/P&gt;&lt;P&gt;DATA #1 : &amp;lt;preformatted&amp;gt;&lt;/P&gt;&lt;P&gt;The recovery history file has been pruned since this&lt;/P&gt;&lt;P&gt;query began.  Query stopped.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Looks the automatic stats job has pruned the history file. But the ibm help says, the  most recent full database backup plus its restore set will always be kept, unless you use the PRUNE utility with the FORCE option.  I am wondering how Automatic table maintenance uses force in this equation. Do you know any inherent setting within the Automatic Table Maintenance that controls this besides the actual DB2 parameters NUM_DB_BACKUPS and REC_HIS_RETENTN&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Kal&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 22 Nov 2011 07:00:02 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/db2-backup-query/qaa-p/8328600#M2963575</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2011-11-22T07:00:02Z</dc:date>
    </item>
  </channel>
</rss>

