Rep:RE: providing 24*7 database ---

     If the only time the data is updated is through a batch process then you could have 2 databases, and just run the batch updates at different times. The databases would always be in sync except during the load process.

     On the other hand, if you have OLTP type updating, you need to think about something similiar to what Guy Hammond said.

-----Message d'origine-----
De: "Guy Hammond" <guy.hammond_at_avt.co.uk> A: Multiple recipients of list ORACLE-L
<ORACLE-L_at_fatcity.com>
Date: 19/10/01
Objet: RE: providing 24*7 database ---

The thing that immediately springs to mind would be to use two
databases, one for queries, one for loading. Then, when the data was
ready, use a transportable tablespace to plug it in. There might be some
post processing or redefining of views necessary. This is better than
using two schemas to do it, because you can have two instances on two
different machines, each instance tuned for exactly what you want to do
with it, and the loading and the queries won't need to share I/O and
CPU. Altho' I guess you could use resource consumer groups and spread
the I/O across controllers. That way you could have one big machine and
all its CPU would be available while loads weren't running. Hmmm.

g

-----Original Message-----
Sent: Thursday, October 18, 2001 10:30 PM To: Multiple recipients of list ORACLE-L

hi gurus,

Our shop ( GIS oracle spatials ) attempting to provide a production
database
(7x 24 hours) , currently we have to offline database for users while
loading of data.
we donot what users to access data while loading. We are thinking of provide 24* 7 services to customers with out going
offline.
What are the best possible solutions ? I had few but I donot know its
right

direction .................

Possible Solutions

Replication -
* not possible until Oracle 9i spatial (because of the
restriction on
replicating objects).
* Even then expense of additional licensing/machinery may be too
great

Duplicate instances - have 2 instances and users switch from one to
other
after production load.-- how to implement ?

Duplicate schema within current database. Have 3 schemas inside a
single
TIPSPROD instance. The schema with the current data remains in
production
until the second schema is loaded with the new data. This is can only
work
if we introduce a third schema that holds the views. At certain time,
we
redefine all the views in the DATAVIEWS schema. --- its kind of
duplication
--- certainly not my option

Can some body direct me where to look or any ideas ? TIA
> narender.akula
>

-

-- 
Please see the official ORACLE-L FAQ:
http://www.orafaq.com
-- 
Author: Guy Hammond
  INET: guy.hammond_at_avt.co.uk

Fat City Network Services    -- (858) 538-5051  FAX:
(858) 538-5051
San Diego, California        -- Public Internet
access / Mailing Lists
-----------------------------------------------------
---------------
To REMOVE yourself from this mailing list, send an
E-Mail message
to: ListGuru_at_fatcity.com (note EXACT spelling of
'ListGuru') and in
the message BODY, include a line containing: UNSUB
ORACLE-L
(or the name of mailing list you want to be removed
from).  You may
also send the HELP command for other information
(like subscribing).

--------------------------------------------------------
You too can have your own email address from Eurosport.
http://www.eurosport.com





--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author:
  INET: adba_at_eurosport.com

Fat City Network Services    -- (858) 538-5051  FAX: (858) 538-5051
San Diego, California        -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from).  You may
also send the HELP command for other information (like subscribing).