Marc,
You didn't mention the Oracle version, but I wouldn't
be surprised if it was O7 as the serial push using the
two-phase commit process doesn't scale well at all.
The completely new architecture (AQ, parallel
propagation, min communication, etc...) in O8 makes
replication quite scalable
Title: RE: Your views on Quest - Shareplex
-Original Message-
From: MacGregor, Ian A. [mailto:[EMAIL PROTECTED]]
We are looking into the product as well, but have yet to even
toy with the product. There is a no chained rows
restriction.
I'm not sure what that statement
I verified this today actually. I had a conference call with Quest
regarding SharePlex, and asked specifically about the chained rows. They
said there is a reorganization step on the target database, so chained
rows are not a problem.
Jim
Jim Hawkins
Lead SAPR/3 Oracle Database
Thank you all for giving your time to express your opinions. I would be
consolidating all the opinions I received in the list and send a mail within
the next two days. I hope, this consolidation would help for any future
queries on this subject.
Thanks,
Rao
[EMAIL PROTECTED]
--
Please see
Title: RE: Your views on Quest - Shareplex - Thank you all
If anyone wants to learn more about SharePlex for Oracle by Quest Software, I will be hosting an interactive conference call next Wednesday. This technical presentation describes SharePlex and how it offers live, up-to-the-minute
Title: RE: Your views on Quest - Shareplex
-Original Message-
From: MacGregor, Ian A. [mailto:[EMAIL PROTECTED]]
The person giving the presentation on Shareplex
stated that there could be no chained rows when the sharepex file,
apparently analogous to the log miner dictionary file
You can ask the listserv, send this commmand to [EMAIL PROTECTED]
WHO list
Sends a list of all subscribers to the list specified. This list may be
partially or completely blocked, depending on the configuration specified
by the list administrator. Most subscriber lists are ONLY
Rao,
Contact QUEST and see if they are holding any SURVIVAL deminstrations in your area.
They are very informative and will answer a lot of your questions. I would suggest
that you also invite your damagement to help in making the decision.
ROR mª¿ªm
[EMAIL PROTECTED] 05/29/01 01:16PM
List,
Title: RE: Your views on Quest - Shareplex
As of a year ago it was single threaded and didn't handle long columns.
-Original Message-
From: Rao, Maheswara [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, May 29, 2001 10:17 AM
To: Multiple recipients of list ORACLE-L
Subject: Your views
Rao,
I worked at MCI Teleconferencing for a few years and they were using
SharePlex for a reporting database. Oracle replication was not fast enough
to support their transaction rate and they also could not afford the
overhead on the source database that occurs with Oracle replication. After
a
Standby database? How do you recover a DB using archived redo logs?
Rich Jesse System/Database Administrator
[EMAIL PROTECTED] Quad/Tech International, Sussex, WI USA
-Original Message-
Sent: Tuesday, May 29, 2001 14:41
To: Multiple recipients of
I guess it is in the LOGICALLY. Standby databases are maintained as
asynchronous physical copies - which is why they can at best be opened
read-only. Typical technical doc obfuscation :-).
Jim Hawkins wrote:
Jared,
That's a really good question! I don't know the answer...
Sorry,
Jim
Title: RE: Your views on Quest - Shareplex
-Original Message-
From: Brian MacLean [mailto:[EMAIL PROTECTED]]
As of a year ago it was single threaded
and didn't handle long columns.
I talked to one of the SharePlex developers.
a) Shareplex has handled long columns for as long
Just something. First of all, I have never seen Shareplex in operation
so this is my gut feeling, chiefly based on how I would have coded it.
Most of the arguments against Shareplex has been about their using
undocumented features - which I admit may be a concern but wouldn't keep
me awake at
Title: RE: Your views on Quest - Shareplex
Our productionruns
on amulti-threaded app.
And, it is the Single
threaded nature of Shareplex with the LONG columns in the db that
did
not make it suitable for
us. Shareplex just could not catch up with the DML activity in our
Production
We are looking into the product as well, but have yet to even toy with the product.
There is a no chained rows restriction. Shareplex does not replicate transactions
on sys objects. A table dropped on one side will not be dropped on the other. It
apparently will replicate truncates
16 matches
Mail list logo
