03/11/2017 Document 736755.

PowerView is Off Nirmal (Available) (0) Contact Us Help

Dashboard Knowledge Service Requests Patches & Updates Community

Service Requests >
Give Feedback...

How To Calculate The Required Network Bandwidth Transfer Of Redo In Data Guard Environments (Doc ID To Bottom
736755.1)

In this Document Was this document helpful?

Goal Yes
No
Solution
The formula used (assuming a conservative TCP/IP network overhead of 30%) for calculating the network bandwidth is :
Document Details

Measuring the Peak Redo Rate

Type:
Example: HOWTO
Status:
PUBLISHED
Last Major
03-Nov-2016
Update:
APPLIES TO: Last Update:
03-Nov-2016

Oracle Database - Enterprise Edition - Version 9.0.1.0 and later

Information in this document applies to any platform. Related Products

Oracle Database - Enterprise

GOAL Edition

Goal is to transfer and apply redo as fast as possible in a Data Guard environment. To achieve this we have to calculate the Information Centers
required network bandwidth based on the redo generation rate on the primary database. Information Center: Overview
Database Server/Client
Installation and
SOLUTION Upgrade/Migration
[1351022.2]

The formula used (assuming a conservative TCP/IP network overhead of 30%) for calculating the network Index of Oracle Database
Information Centers
bandwidth is :
[1568043.2]

Required bandwidth = ((Redo rate bytes per sec. / 0.75) * 8) / 1,000,000 = bandwidth in Mbps インフォメーション・センタ
ー: データベースおよび
Enterprise Manager 日本語ド
キュメント [1946305.2]
Measuring the Peak Redo Rate
Information Center: Overview
Use the Oracle Statspack utility for an accurate measurement of the redo rate. of Database Security Products
[1548952.2]
Based on your business you should have a good idea as to what your peak periods of normal business
activity are. For example, you may be running an online store which historically sees the peak
activity for 4 hours every Monday between 10:00 am - 2:00 pm. Or, you may be running a merchandising Document References
database which batch-loads a new catalog every Thursday for 2 hours between 1 am - 3 am. Note that
we say "normal" business activity - this means that in certain days of the year you may witness much No References available for
this document.
heavier business volume than usual, e.g. the 2-3 days before Mother's Day or Valentine's Day for an
online florist business. Just for those days, perhaps you may allocate higher bandwidth than usual,
and you may not consider those as "normal" business activity.However, if such periodic surges of Recently Viewed
traffic are regularly expected as part of your business operations, you must consider them in your
redo rate calculation. Handling ORL and SRL
(Resize) on Primary and
During the peak duration of your business, run a Statspack snapshot at periodic intervals. For Physical Standby in Data
example, you may run it three times during your peak hours, each time for a five-minute duration. Guard Environment
The Statspack snapshot report will include a "Redo size" line under the "Load Profile" section near [1532566.1]
the beginning of the report. This line includes the "Per Second" and "Per Transaction" measurements General Guideline For Sizing
for the redo size in bytes during the snapshot interval. Make a note of the "Per Second" value. Take The Online Redo Log Files
the highest "Redo size" "Per Second" value of these three snapshots, and that is your peak redo [781999.1]
generation rate. Master Note: Overview of
Redo Logs and Archiving
Note that if your primary database is a RAC database, you must run the Statspack snapshot on every [1503091.1]
RAC instance. Then, for each Statspack snapshot, sum the "Redo Size Per Second" value of each
Oradim and Spfile
instance, to obtain the net peak redo generation rate for the primary database. Remember that for
[378021.1]
a RAC primary database, each node generates its own redo and independently sends that redo to the
standby database - hence the reason to sum up the redo rates for each RAC node, to obtain the net Script to Collect Data Guard
peak redo rate for the database. Primary Site Diagnostic
Information for Version 10g
and Above (Including RAC).
As an Alternative you can also get the 'Redo rate bytes per sec.' from V$SYSMETRIC_HISTORY, eg.
[1577401.1]
SQL> select * from v$sysmetric_history where metric_name = 'Redo Generated Per Sec';
or in a RDA-Output: Show More
Performance - AWR Report - Statistic: "redo size"

https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=531649140451700&parent=SrDetailText&sourceId=3-15828913311&id=736755.1… 1/2
03/11/2017 Document 736755.1

Example:

Let us assume the redo rate is a 500 KB/sec.

Required bandwidth = ((Redo rate bytes per sec. / 0.75) * 8) / 1,000,000 = bandwidth in Mbps
Required bandwidth = ((512000/0.75) * 8) /1,000,000
Required bandwidth = 5.46 Mbps

Also see

Data Guard Redo Transport & Network Configuration

And

Measuring Network Capacity using oratcptest (Doc ID 2064368.1)

for further Hints and Best Practices to setup the Network for Data Guard Log Transport Services

Didn't find what you are looking for? Ask in Community...

Related
Products

Oracle Database Products > Oracle Database Suite > Oracle Database > Oracle Database - Enterprise Edition > RDBMS > Standby database issues

Keywords
ARCHIVELOGS; DATA GUARD; DATAGUARD; NETWORK; PRIMARY; RAC; STANDBY; STANDBY DATABASE; TRANSFER
Errors
ORA-00603; TNS-12535; TNS-00505; TNS-12547; 00600; ORA-16198

Back to Top
Copyright (c) 2017, Oracle. All rights reserved. Legal Notices and Terms of Use Privacy Statement

https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=531649140451700&parent=SrDetailText&sourceId=3-15828913311&id=736755.1… 2/2