Re: Standby Databases

From: TLP <rstaffor_at_lcp.com>
Date: 1997/02/03
Message-ID: <01bc120a$e0f29b20$72e0bdc0@x3632.roc.lcp.com>#1/1

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"

>

Received on Mon Feb 03 1997 - 00:00:00 CST