RE: Oracle 24x7 shops and Patches-Upgrades.
- From: "Laimutis Nedzinskas" <Laimutis.Nedzinskas@xxxxxxxxxxxxx>
- To: <oracle-l@xxxxxxxxxxxxx>
- Date: Thu, 21 Dec 2006 14:58:44 -0000
> From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Alex Gorbachev
> But this would be tremendous efforts and require the feature working
really well.
I worked on a system which required no more than 5 minutes downtime for
a good reason.
Those 5 minutes were actually required for physical rewire of some
serial input devices.
And yes, the effort was relatively tremendous keeping in mind that the
application was relatively simple.
Database "rolling" upgrades were implemented by setting up a new server
and establishing data synchronization of critical tables between "old"
and "new" databases.
We used Oracle 24x7 features at full. Application changes were tracked
almost as carefully as Oracle tracks it's core data dictionary changes.
Many non 7x24 Oracle features were not used. For example, until "index
online" feature one would carefully consider creating a new index on a
critical table. On the other hand we had such a design that either
critical tables were small or they were in a separate DW database. That
was a deal.
It all worked but one has to understand that true 24x7 costs. We managed
the cost by relaxing some constraints like functional complexity of the
application, ideal performance during the upgrade, even 100% data
availability during and after the upgrade.
If someone thinks that 24x7 is just for free then one has to redefine
24x7 as it was advised in this thread. It's politics but not a technical
discussion then.
Fyrirvari/Disclaimer
http://www.landsbanki.is/disclaimer
--
//www.freelists.org/webpage/oracle-l
Other related posts:
