Re: problem with extraction of .tgz file on Redhat AS 3.0

From: Girish N (girish.narasanna_at_oracle.com)
Date: 12/20/04

  • Next message: Asplund, Marcus: "Help with RH9/FC installation on new box Please"
    Date: Mon, 20 Dec 2004 21:27:56 +0530
    To: General Red Hat Linux discussion list <redhat-list@redhat.com>
    
    

    Hi Donald,

    Yes, the database is shutting down perfectly without any errors before
    the backup starts up, hence no file is in use during backup.

    Thanks & Regards
    Girish

    O'Neill, Donald (US - Deerfield) wrote:

    >There is a good possibility. I assumed that your shutting down Oracle
    >before your performing the backup?
    >
    >-----Original Message-----
    >From: redhat-list-bounces@redhat.com
    >[mailto:redhat-list-bounces@redhat.com] On Behalf Of Girish N
    >Sent: Monday, December 20, 2004 8:18 AM
    >To: General Red Hat Linux discussion list
    >Subject: Re: problem with extraction of .tgz file on Redhat AS 3.0
    >
    >Hi Donald,
    >
    >Thanks for the reply, does this mean that .tgz will get corrupted if the
    >
    >datafile is in use?
    >
    >Thx & Rgds
    >Girish
    >
    >O'Neill, Donald (US - Deerfield) wrote:
    >
    >
    >
    >>Some Oracle process could still have some open files. I would do a
    >>'fuser -am' on the partition just to make sure there are no open files
    >>before tarring.. You could also do a 'tar -cjvf' which uses bzip
    >>
    >>
    >instead
    >
    >
    >>of gzip..
    >>
    >>-----Original Message-----
    >>From: redhat-list-bounces@redhat.com
    >>[mailto:redhat-list-bounces@redhat.com] On Behalf Of Girish N
    >>Sent: Monday, December 20, 2004 1:56 AM
    >>To: General Red Hat Linux discussion list
    >>Subject: Re: problem with extraction of .tgz file on Redhat AS 3.0
    >>
    >>Hi Linus,
    >>
    >>Thanks again for the reply. As said earlier, wil reschedule the .tgz
    >>dump to a local mount point & will check the same.
    >>
    >>Thanks & Regards
    >>Girish
    >>
    >>C. Linus Hicks wrote:
    >>
    >>
    >>
    >>
    >>
    >>>On Mon, 2004-12-20 at 11:07 +0530, Girish N wrote:
    >>>
    >>>
    >>>
    >>>
    >>>
    >>>
    >>>>Hi Linus,
    >>>>
    >>>>Thanks for the reply,
    >>>>
    >>>>1. The datafile in question if only 1Gb
    >>>>2. This is a low end server with 2Gb memory & the backup is scheduled
    >>>>
    >>>>
    >>>>
    >>>>
    >>to
    >>
    >>
    >>
    >>
    >>>>run at 4 AM when there is no memory resource crunch.
    >>>>
    >>>>The corruption seems to be very inconsistent, 1 day the .tgz is fine,
    >>>>
    >>>>
    >
    >
    >
    >>>>while the 2nd day, the .tgz file gets corrupted. Am planning to
    >>>>reschedule the .tgz backup to one of the local Mount points instead
    >>>>
    >>>>
    >of
    >
    >
    >>>>
    >>>>
    >>>>
    >>>>
    >>
    >>
    >>
    >>
    >>>>the SAN Harddisk & then check the same.
    >>>>
    >>>>You hv commented that "Not with the symptoms you have", does that
    >>>>
    >>>>
    >mean
    >
    >
    >>>>
    >>>>
    >>>>
    >>>>
    >>
    >>
    >>
    >>
    >>>>that this may be one-of-the reasons for file corruption.
    >>>>
    >>>>
    >>>>
    >>>>
    >>>>
    >>>>
    >>>Having an inconsistent datafile will not cause the kind of corruption
    >>>you are getting in the tgz file. If you backup (by whatever means) a
    >>>datafile that is in an inconsistent state, then the result of
    >>>
    >>>
    >restoring
    >
    >
    >>>that file will be a datafile in an inconsistent state, not a problem
    >>>with the restore. The reason tar complained was because of the gzip
    >>>error. When gzip took the error, it was unable to continue ungzipping
    >>>the file and sent EOF to tar.
    >>>
    >>>This means the error will be with corruption either during gzip, or
    >>>writing to disk. This suggests a hardware problem, perhaps in memory,
    >>>
    >>>
    >>>
    >>>
    >>or
    >>
    >>
    >>
    >>
    >>>with writing to the SAN. Trying a local disk rather than the SAN is a
    >>>good idea. You might also try running memtest on this machine. Having
    >>>
    >>>
    >>>
    >>>
    >>no
    >>
    >>
    >>
    >>
    >>>memory resource crunch at the time of the backup doesn't really mean
    >>>much, but I would expect other files to show the same symptom if
    >>>
    >>>
    >memory
    >
    >
    >>>is the problem.
    >>>
    >>>http://www.memtest86.com/
    >>>
    >>>
    >>>
    >>>
    >>>
    >>>
    >>>

    -- 
    redhat-list mailing list
    unsubscribe mailto:redhat-list-request@redhat.com?subject=unsubscribe
    https://www.redhat.com/mailman/listinfo/redhat-list
    

  • Next message: Asplund, Marcus: "Help with RH9/FC installation on new box Please"

    Relevant Pages

    • Re: OT but possibly important: shelf life of CDs
      ... > Donald Tees wrote: ... >>disks in them for backup. ... but very functional for backup. ... I am refering to removable IDE drives. ...
      (comp.lang.cobol)
    • Re: Couple Old Style Space Opera questions...
      ... James A. Donald wrote: ... I must say this is a new tactic for you refusing to backup your claims. ... The new tactic appears to be falsely insisting that you already have. ...
      (rec.arts.sf.science)
    • Re: Auto
      ... Donald, I have one, if you want I will send you a copy, just let me know ... Paul B ... Always backup your data before trying something new ... > Does anyone have a templete or a usable excel formula that can be used ...
      (microsoft.public.excel.misc)
    • Re: New T-Mobile Upgrade Available
      ... I don't know that you can restore on '02 backup onto an '03 OS. ... > of mobile device..." ... >> Thanks to Mark Cohen and Donald, I've been able to get this. ...
      (microsoft.public.pocketpc.phone_edition)
    • Re: Thoughts on Logical Log use requested
      ... LOGBUFF is 64, unbuffered logging is used. ... Regards ... Log backup ... >> IBM Informix Development Munich, ...
      (comp.databases.informix)