Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
Home -> Community -> Mailing Lists -> Oracle-L -> RE: Block size or replication?
Adding a read only standby database used for reporting would also speed
things up.
Another trick would be to utilize so called "data warehouse pull" to do
nightly=20
refreshes of your reporting database and then to add things like tables =
in
the=20
"KEEP" pool, bitmap indexes, reverse key indexes and materialized views
(they
get utilized automatically, when you enable query rewrite). That way =
you'd
have
a data warehouse version of your database. The technology would be to
do SRDF (I don't know your hardware configuration) from one simmetrix =
to
another
and then perform the recovery and, of course, run the DDLs turning the =
whole
thing into a reporting database.
-----Original Message-----
From: Libal, Ivo [mailto:ivo.libal_at_knapp-systems.com]
Sent: Tuesday, June 20, 2000 11:43 AM
To: Multiple recipients of list ORACLE-L
Subject: AW: Block size or replication?
You can try a parallel sql processing first - maybe it will help.
Ivo Libal
Knapp-systems
> -----Urspr=FCngliche Nachricht-----
> Von: Smith, Ron L. [SMTP:rlsmith_at_kmg.com]
> Gesendet am: Dienstag, 20. Juni 2000 17:07
> An: Multiple recipients of list ORACLE-L
> Betreff: Block size or replication?
>=20
>=20
>=20 >=20
>=20> To REMOVE yourself from this mailing list, send an E-Mail message
> Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051
> San Diego, California -- Public Internet access / Mailing =
Lists
> --------------------------------------------------------------------
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 Received on Tue Jun 20 2000 - 19:13:55 CDT