<?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>topic Re: Need HP UX command in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/need-hp-ux-command/m-p/5725011#M481002</link>
    <description>&lt;P&gt;The command you need is "find".&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;PRE&gt;find /some/directory -name "*arch*.dbf" -mtime +1 -exec rm {} \+&lt;/PRE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;-mtime +1 means "older than 1 full day, ignoring fractional days" = "at least 2 full days old" = "48 hours old or older". If this is not what you want, adjust the value. (-mtime +2 would be "72 hours old or older")&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This looks like you're removing database archivelogs. If the archivelogs are used for on-line database backups, why does the backup software not delete the old archivelogs when (and *only* when) they've been successfully stored on tape?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If you delete all archivelogs older than 2 days without making sure they're successfully backed up first, and the tape backup system fails on a Friday evening and cannot be fixed until Monday, this will start removing archivelogs that are not backed up, breaking the archivelog chain. A broken archivelog chain makes it difficult to restore the database state to any point in time after the break.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;To recover from a broken archivelog chain, a full database backup may be required so that a new chain of archivelogs can be started. If your database is large, a full backup might take a very long time. With multi-terabyte databases, accepting that the database will stop if the backup hardware fails and archivelog space fills up might result in a shorter service break than breaking the log chain and making the full backup before resuming normal service (been there, learned the lesson!).&lt;/P&gt;</description>
    <pubDate>Mon, 16 Jul 2012 10:15:23 GMT</pubDate>
    <dc:creator>Matti_Kurkela</dc:creator>
    <dc:date>2012-07-16T10:15:23Z</dc:date>
    <item>
      <title>Need HP UX command</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/need-hp-ux-command/m-p/5724857#M481000</link>
      <description>&lt;P&gt;HI,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Since we maintain database files regularly, i'm looking for an hp-ux command to remove files that:&lt;/P&gt;&lt;P&gt;1-have the word "arch" in their names.&lt;/P&gt;&lt;P&gt;2-have "dbf" extension.&lt;/P&gt;&lt;P&gt;3-older than two days.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;please provide me with the single command so that i remove all files that meet the three conditions above at once.&lt;/P&gt;</description>
      <pubDate>Mon, 16 Jul 2012 09:11:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/need-hp-ux-command/m-p/5724857#M481000</guid>
      <dc:creator>Afaq</dc:creator>
      <dc:date>2012-07-16T09:11:15Z</dc:date>
    </item>
    <item>
      <title>Re: Need HP UX command</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/need-hp-ux-command/m-p/5725011#M481002</link>
      <description>&lt;P&gt;The command you need is "find".&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;PRE&gt;find /some/directory -name "*arch*.dbf" -mtime +1 -exec rm {} \+&lt;/PRE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;-mtime +1 means "older than 1 full day, ignoring fractional days" = "at least 2 full days old" = "48 hours old or older". If this is not what you want, adjust the value. (-mtime +2 would be "72 hours old or older")&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This looks like you're removing database archivelogs. If the archivelogs are used for on-line database backups, why does the backup software not delete the old archivelogs when (and *only* when) they've been successfully stored on tape?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If you delete all archivelogs older than 2 days without making sure they're successfully backed up first, and the tape backup system fails on a Friday evening and cannot be fixed until Monday, this will start removing archivelogs that are not backed up, breaking the archivelog chain. A broken archivelog chain makes it difficult to restore the database state to any point in time after the break.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;To recover from a broken archivelog chain, a full database backup may be required so that a new chain of archivelogs can be started. If your database is large, a full backup might take a very long time. With multi-terabyte databases, accepting that the database will stop if the backup hardware fails and archivelog space fills up might result in a shorter service break than breaking the log chain and making the full backup before resuming normal service (been there, learned the lesson!).&lt;/P&gt;</description>
      <pubDate>Mon, 16 Jul 2012 10:15:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/need-hp-ux-command/m-p/5725011#M481002</guid>
      <dc:creator>Matti_Kurkela</dc:creator>
      <dc:date>2012-07-16T10:15:23Z</dc:date>
    </item>
  </channel>
</rss>

