I'm wondering it lecturer ever tried to do that in real life, not in a test lab. It all works perfect on PowerPoint presentations, but in real life it's quite challenging. "Simple" bi-directional streams design and rollout could take a while. I'm not saying it's impossible, but it's not as simple as it sounds 8-) There are too many variables to consider and as previous folks said - there is a hefty price tag attached to each solution. --romas On Tue, Nov 25, 2008 at 11:05 AM, Yechiel Adar <adar666@xxxxxxxxxxxx> wrote: > I was in a stream class today and the lecturer mentioned just this thing. > Create a second database and create bi-directional streams between the two. > 1) bring the application down for a minute or two. > 2) change the application to access the second server. > 3) bring down the first database. > 4) bring up the application. It will start to put updates in the queues in > the second database. > 5) upgrade the first database. > 6) bring up the first database and wait for the apply process to catch up. > 7) bring down the application for a minute or two. > 8) point the application to the first database. > 9) start up the application. > > Upgrade completed with only a few minutes down time. > > Need EE for streams and works best in 10.2.0.4. > > Adar Yechiel > Rechovot, Israel > >