Tuesday, April 23, 2013

Required Network Bandwidth Transfer Of Redo In Data Guard


Based on primary database's redo generation rate we need calculate the required network bandwith.
How to calculate Redo rate.

Method 1:

We need run AWR report at periodic intervals. Please note down  "Per Second" value. Take the highest "Redo size" "Per Second" value from AWR report, and that is your peak redo generation rate.


Load Profile

Per Second
Per Transaction
Per Exec
Per Call
DB Time(s):
0.7
0.1
0.00
0.00
DB CPU(s):
0.2
0.0
0.00
0.00
Redo size:
171,813.4
15,421.0
Logical reads:
6,451.7
579.1

 
Method 2:

Query v$sysmetric_history view to find redo generation per second.
select avg (value) from v$sysmetric_history where metric_name = 'Redo Generated Per Sec';

The formula used for calculation the network bandwidth is:

Required bandwith = ((Redo rate bytes per sec./0.7)*8) / 1,000,00


Example

Let us assume the redo rate is a 740 KB/sec.
Required bandwith = ((Redo rate bytes per sec./0.7)*8) / 1,000,000
Required bandwith = ((757760./0.7)*8) / 1,000,000
Required bandwith = 8.66 Mbps

Friday, April 12, 2013

Data Guard monitoring, primary and Standby databases management actions

When I start implement data guard, I find out some helpful hits from Oracle document. In Data Guard monitoring, primary database management actions and where to find information related to these actions.

Database action
Primary Database
Standby Database
Enable or disable a redo thread
Alert log
V$THREAD
Alert log
Display database role, protection
mode, protection level, switchover
status, fast-start failover information,
and so forth
V$DATABASE
V$DATABASE
Add or drop a redo log file group
Alert log
V$LOG
STATUS column of V$LOGFILE
Alert log
CREATE CONTROLFILE
Alert log
Alert log
Monitor Redo Apply
Alert log
V$ARCHIVE_DEST_STATUS
Alert log
V$ARCHIVED_LOG
V$LOG_HISTORY
V$MANAGED_STANDBY
Change tablespace status
V$RECOVER_FILE
DBA_TABLESPACES
Alert log
V$RECOVER_FILE
DBA_TABLESPACES
Add or drop a datafile or tablespace
DBA_DATA_FILES
Alert log
V$DATAFILE
Alert log
Rename a datafile
V$DATAFILE
Alert log
V$DATAFILE
Alert log
Unlogged or unrecoverable
operations
V$DATAFILE
V$DATABASE
Alert log
Monitor redo transport
V$ARCHIVE_DEST_STATUS
V$ARCHIVED_LOG
V$ARCHIVE_DEST
Alert log
V$ARCHIVED_LOG
Alert log
Issue OPEN RESETLOGS or CLEAR
UNARCHIVED LOGFILES statements
Alert log
Alert log
Change initialization parameter
Alert log
Alert log

Thursday, April 11, 2013

Various memory management methods:

Memory Management Mode
For
You Set
Oracle Database Automatically Tunes
Automatic memory management (AMM)
SGA and PGA
  • Total memory target size for the Oracle instance (MEMORY_TARGET)
  • (Optional) Maximum memory size for the Oracle instance (MEMORY_MAX_TARGET)
  • Total SGA size
  • SGA component sizes
  • Instance PGA size
  • Individual PGA sizes
Automatic shared memory management (ASMM)
(AMM disabled)
SGA
  • SGA target size (SGA_TARGET)
  • (Optional) SGA maximum size (SGA_MAX_SIZE)
SGA component sizes
Manual shared memory management
(AMM and ASMM disabled)
SGA
  • Shared pool size (SHARED_POOL_SIZE)
  • Buffer cache size (DB_CACHE_SIZE or DB_BLOCK_BUFFERS)
  • Java pool size (JAVA_POOL_SIZE)
  • Large pool size (LARGE_POOL_SIZE)
  • (Optional) SGA maximum size (SGA_MAX_SIZE)
None
Automatic PGA memory management
PGA
Instance PGA target size (PGA_AGGREGATE_TARGET)
Individual PGA sizes
Manual PGA memory management
(Not recommended)
PGA
Maximum work area size for each type of SQL operator
None