Re: why do we need to shutdown database or application server to backup Oracle Home?

From: joel garry <>
Date: Mon, 17 Mar 2008 13:47:37 -0700 (PDT)
Message-ID: <>

On Mar 15, 11:32 am, NetComrade <> wrote:
> On Thu, 13 Mar 2008 17:52:16 -0700 (PDT), wrote:
> >Dear Group,
> >We are using Oracle 10g on Linux.
> >While it is easy to understand we need to shutdown database to backup
> >database files, I do not quite understand why do we need to shutdown
> >database or oracle application server to backup Oracle Homes.
> >It is my understanding that oracle processes will only read those
> >files inside the Oracle home, but not writing to them, except log
> >files.
> >Any explanations will be highly appreciated.
> learn RMAN, or even 'hot backup'

Do you use RMAN or 'hot backup' to backup your Oracle Homes?

My experience on hp-ux has been that fbackup will not backup at least one oracle executable if it is open (I forget which one and looks like someone cleaned up the mail from that time, dang it). Normally, one wouldn't back up the oracle executables, as one can simply reinstall oracle if some catastrophe wipes out the Oracle Home. However, one might want to make a backup of certain areas (for example, everything _except_ the oracle data files) if one want to make a rapid recovery tape or disk, ie, get new hardware and jam in the disk and everything and be up a lot faster than an RMAN restore and/or reinstall plus patching. Whether such a capability is needed is site dependent, as well as management-bias dependent, but it does seem to require a brief shutdown of Oracle to copy everything.

I don't know if linux has the same issue and have no way to try it, so I personally am curious if anyone has. Not that I don't trust Jerome Vitalis, but I would want to verify.


-- is bogus.
It took 85 years to build Bear Stearns and four days for it to
Received on Mon Mar 17 2008 - 15:47:37 CDT

Original text of this message