RE: SharePlex info

[Aponte, Tony]

Title: Message

Your bandwidth requirements will be the rate of changes to the actual data.  The traffic consists of the actual data and control information needed to reassemble the transaction on the target.  The source database's other redo payload (i.e., index operations, rollback segment maintenance, etc.) is not used by Shareplex.    In our environment of dual Sun 6800's, 10 CPU's each, we observe less that 1% CPU consumption on the source and target sides combined.  It varies according to the DML load on the source but not by much.  We've never had a problem with it consuming a noticeable amount.   I have a question on the comparison between a physical standby and Shareplex replication.  Isn't 9i's logical standby feature better suited for the comparison to Shareplex?  I'm assuming that you are considering offloading some processing to another host since you are looking to replicate about 50% of the tables in the source database.   HTH Tony Aponte     -----Original Message----- From: Gorbounov,Vadim [mailto:[EMAIL PROTECTED] Sent: Thursday, August 21, 2003 1:49 PM To: Multiple recipients of list ORACLE-L Subject: SharePlex info Hi All,   I'm trying to find some technical details about SharePlex, that is:   - How much network bandwidth I'd expect to replicate from database, generating 1-5 MB/sec redo. Does SharePlex send SQL text over the network or data in some internal (hopefully compressed) format - How much CPU on the source DB server side would it cost  - just a ball park - very little- little - or a lot - Of two options, using 9.2 physical async standby db and clone whole database vs replicate 50% (enough from business requirements) of tables using SharePlex, which one sounds preferrable keeping in mind minimizing CPU burden on the source database.   Any opinion or pointer to any benchmark is highly appreciated.   Thanks a lot Vadim