Re: Influencing commit interval of read-only replication's refresh gr

From: Stephane Faroult <sfaroult_at_oriolecorp.com>
Date: Fri, 29 Jun 2001 05:58:42 -0700
Message-ID: <F001.0033D550.20010629054525@fatcity.com>

> Hi,
>
> does some one know of a way to force the refresh process of a read-only
> snapshot group to commit at predefined intervals: by table, by n number of
> rows or any other way? The problem that we are facing is that a refresh
> group has some rapidly changing tables and the rollback segment is not big
> enough.
>
> TIA,
>
> Tamas Szecsy
> --

Tamas,

    A refresh group is a set of related (through FKs and the like) tables. Not committing before everything has been replicated is the Oracle way to fudge the integrity constraint violation issue (don't forget that they have one log per table, not a single chronological log). Either you begin writing your own refresh functions, or you find a way to split your refresh group into subgroups for which referential integrity would not be a problem, or you increase the rate of refresh. I don't see anytging else.

Regards,

Stephane Faroult
Oriole
Corporation

---

Performance tools for Oracle ®
http://www.oriole.com/

-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.com
-- 
Author: Stephane Faroult
  INET: sfaroult_at_oriolecorp.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).

Received on Fri Jun 29 2001 - 07:58:42 CDT