Re: How many of you do shutdown your EBS PROD to make a clone?
- From: <oraapps@xxxxxxxxxxxxxxx>
- To: ora-apps-dba@xxxxxxxxxxxxx
- Date: Thu, 11 Jun 2009 10:33:30 -0400
Yury,
We seldom ever shutdown our EBS env -- for just the reasons you mentioned.
To be clean -- we do not shutdown our apps EBS to make clones.
We do however, shutdown our Concurrent Managers and Apache/Web Forms tier from
time to time to free things up.
After everything is down we sometimes have to clean or kill some orpaned
processes that have seemed to hang on to system
resources and not let go.
Regards,
NJAD
---- Jurijs Velikanovs <j.velikanovs@xxxxxxxxx> wrote:
> Hi List,
>
> Just a quick question. Would you mind to at least answer YES or NO
> (any comments are welcome).
> Do you shutdown your EBS production database for cloning purposes?
>
> My answer is: Never! In fact I think it is an awful idea to shutdown
> you production for cloning proposes for the following reasons:
> 1. You introduce unnecessary downtime to a system users. You can use
> hot backups instead.
> 2. You miss a brilliant opportunity to test your recovery (including
> recovery time regular assessment, and DBA training).
> 3. You flush all you cache (shared and "buffer" pool). It will
> slowdown your processes after you start you instance up.
> On the other hand I don't see any benefits!
>
> PS I was told that even big EBS shops shutdown their systems to make
> cold backups. Definitely not the systems that my team is responsible
> for :)
>
> Yury
>
Other related posts:
