Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: Standby Databases

Re: Standby Databases

From: Jim Yoshii <yoshii_at_planet.net>
Date: 1997/02/05
Message-ID: <32F8B682.12E@planet.net>#1/1

TLP wrote:
>
> The one solution would be to create a snapshot database this will allow you
> to point the users at the snapshot database while maintenance is being done
> one the production database. The best recommendation would be to have a
> second system configured the same as the primary system.
>
> This also allows the primary system to be taken offline for maintenance and
> backups.
>
> --
> Ray Stafford
>
> JP Soria <jpsoria_at_saxe.com> wrote in article <32F6290E.35A6_at_saxe.com>...
> > We have a database of 200GB, the client wants 24 hour access to this
> > database with no down time. The database is read-only, and updates
> > are performed on a weekly basis. How can we provide 24 hour access to
> > a database and not suffer a severe performance loss?
> >
> > I realize that standby databases are meant for means of backup/recovery,
> > however, are we able to have a standby database that the users are
> > pointed to with the ability to query the database while the other
> > database is being updated? Then upon completion of the update point
> > them back to the original database? I don't see why not.
> >
> >
> > --
> > JP Soria
> > Oracle7 DBA/Software Tester
> > Email: jpsoria_at_saxe.com
> > "Failing to plan = planning to fail"
> >

From what I've read standby databases use archive logs to keep the primary and standby databases in synch. The standby database is in continuous recovery mode, processing archive logs as they are generated by the primary database. The standby database can't be accessed until you take it out of recovery mode, presumably when the primary fails.

You could take advantage of the fact that all your updates are done at once. While the primary database is being updated you could let your users access the secondary database. After the primary database is updated you can point your users back at the primary and update the secondary database using the archive logs generated by the primary or just re-running your update procedures on the secondary database.

-- 
        James H. Yoshii  
Intellitech Business Solutions
       yoshii_at_planet.net
Received on Wed Feb 05 1997 - 00:00:00 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US