Title: RE: I/O contention with external process reading the oracle logs (online redo logs)
Thanks to all of you for the input.
The suggestion of sending the log files and
checking
the size of the resulting Shareplex output is very
good.
I talked today with the sales person and she will put
Title: RE: I/O contention with external process reading the oracle logs (online redo logs)
My experience is that they do nothing for free.
-Original Message-
From: [EMAIL PROTECTED]@SUNGARD On Behalf Of Tim Gorman [EMAIL PROTECTED]
Sent: Thursday, June 13, 2002 9:23 PM
Title: RE: I/O contention with external process reading the oracle logs (online redo logs)
who does? :-)
- Original Message -
From:
[EMAIL PROTECTED]
To: Multiple recipients of list ORACLE-L
Sent: Friday, June 14, 2002 6:28 AM
Subject: RE: I/O contention
Title: RE: I/O contention with external process reading the oracle logs (online redo logs)
Quest.
-Original Message-
From: [EMAIL PROTECTED]@SUNGARD On Behalf Of Tim Gorman [EMAIL PROTECTED]
Sent: Friday, June 14, 2002 10:38 AM
To: Multiple recipients of list ORACLE-L
Subject
Title: RE: I/O contention with external process reading the oracle logs (online redo logs)
Actually, for us the percentage is lower since the OLTP
application we're using itfor is heavily indexed (with the exception
of single SQL that updates many rows.) It's one of those claims
Title: RE: I/O contention with external process reading the oracle logs (online redo logs)
I think Yechiel is referring to a statistical claim by Quest that only 30% of the redo stream is usable in re-assembling the SQL statement. The rest is like you suspect, index maintenance, rbs segment
Title: RE: I/O contention with external process reading the oracle logs (online redo logs)
It shouldn't need to be a "theoretical" or
"statistical" claim at all. A prospective customer should be able to ship
a few archived redo log files (the more the better!) to Que
Hello Tim and Rachel
There is band width problem. The line is 256K (we are checking upgrade to
512k).
The database, during peek time produce 10MB of logs every 2-3 minutes.
On this line it will take 7-8 minutes to pass 10MB if the line was dedicate
and it is not dedicated.
Upgrading the line to
Shareplex reads the log files so if you can't get the log files
over the existing line, Shareplex can't read them.
have you considered using an NFS mounted disk for your archive log
directory?
or a process that copies the archived logs to the nfs mounted disk on
the primary and a another
Just curious, why do you think replication will be less bandwidth? Are you
replicating only certain schemas/accounts and not the entire database?
Is Quest asserting that shipping the SQL statements are more compact than
shipping the redo? That could be possible, but I'm quite certain that it
Hello All
I just had a meeting today about replication.
The situations is: One master db that is currently replicated
(master to master synchronous replication) to a second DB.
Both machines are NT and the is a direct cable connection
between the network cards on both machines.
However, this
why wouldn't you consider simply using the standby database feature?
do you need the remote site to support users also?
- Original Message -
To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED]
Sent: Sunday, June 09, 2002 11:43 AM
(online redo logs)
Hello All
I just had a
and if you need the remote site to support users, you could use the
logical standby feature of 9iR2, which generates SQL statements to be
applied and allows the database to be open and active.
--- Tim Gorman [EMAIL PROTECTED] wrote:
why wouldn't you consider simply using the standby database
NB_ RESENDING in plain text - sorry, Outlook keeps seinding in html no matter what
default i set!
Hi lists,
I am using Quest Shareplex product for Oracle to Oracle one way replication. I
have two systems (source and target) and two environments (dev, demo). On system
one, the
Title: RE: I/O contention with external process reading the oracle logs (online redo logs)
I think they are alluding to UNIX file system contention. If the redo logs are in regular file systems (not raw, Veritas Quick I/O, etc.) then UNIX (at least in my Solaris environment) needs to lock
15 matches
Mail list logo
