Re: Update schema while new data is coming in

RAC has only one database (i,e shared database).  The moment you make
changes to the schema on one node, all nodes will see the same changes.

  I am guessing that you have 2 databases with bi-directional replication.
Are you using streams for synchronizing the data between the two servers?
As long as you don't drop/rename objects (i.e tables/columns), it should
work.  You need to do thorough testing before implementing in production.

Vijay


On 11/12/07, Don Seiler <don@xxxxxxxxx> wrote:
>
> I haven't personally had the pleasure of playing with this, but isn't
> this exactly the kind of thing that is used in RAC success
> testimonials?  Being able to perform updates on one member of the
> cluster at a time while the others handle the application traffic?
>
> Don.
>
> On Nov 12, 2007 3:47 AM,  <Antje.Stejskal@xxxxxxxxxxx> wrote:
> > Hi,
> >
> > we are having a web application that ist o be online availyble 7x24. We
> plan
> > for the scenario that the application needs a software update (new
> tables ,
> > modified tables et. al.) Management and customer requires that the
> > application is still running while the upgrade goes on. How would you
> solve
> > this, that you have one server with the old schema where new data is
> coming
> > in, meanwhile another server is brought up to latest release. And data
> of
> > the old server (or delta of data) will be send to new server. We will
> > propably have 2 servers anyway because of the traffic.
> > Please help me with your ideas.
> >
> > Regards
> > Antje Stejskal
> > --
> > http://www.freelists.org/webpage/oracle-l
> >
> >
> >
>
>
>
> --
> Don Seiler
> http://seilerwerks.wordpress.com
> ultimate: http://www.mufc.us
> --
> http://www.freelists.org/webpage/oracle-l
>
>
>

Other related posts: