Online DBA

<<Back to PT Main Page Steps to Configure HugePages on Linux 64-bit for Oracle Database Step0: Check if Transparent  HugePages are enabled cat /sys/kernel/mm/transparent_hugepage/enabled [always] madvise never Starting from RHEL6/OL6, Transparent HugePages are implemented and enabled by default. Therefore Oracle recommends disabling Transparent HugePages on all servers running Oracle databases this MOS note (Doc ID 1557478.1) Step1: Verify the current OS Page Size #grep Hugepagesize /proc/meminfo Step2:Configure memlock Set the memlock user limit in /etc/security/limits.conf file. Set the value (in KB) slightly smaller than installed RAM. e.g. If you have 450GB RAM installed, you may set: oracle soft memlock 419430400 oracle hard memlock 419430400 NOTE: There is no harm in setting this value larger than your SGA requirements. Step3: Verify the memlock limit Re-logon to the Oracle product owner account (e.g. 'oracle') and check the memlock

<<Back to Oracle Data Guard Broker Page How Oracle Dataguard Broker Works Oracle Dataguard Broker has server side and client side components. At client side it has OEM and DGMGRL. Both the utilities can be used to read and manipulate Broker Configuration data. At server Side it has got 2 components 1> Binary Configuration File 2> DMON process DMON processes is responsible to monitor the health of the broker configuration and ensures that every database has a consistent description of the configuration. To Ensure this DMON process persistently maintains information about all members of the broker configuration in a binary configuration file. In Configuration file Broker stores various properties associated with each database to control the database's behavior. Whenever you add databases to a broker configuration, or make a change to an existing database's properties, each DMON process records the new information in its copy of the configuration file. The param

<<Back to Oracle Data Guard Broker Page Understanding  Oracle Data Guard Broker and DGMGRL Utility Oracle Data Guard Broker is an Utility which logically groups all the dataguard members in oracle dataguard configuration to centrally  manage and monitor them together as an integrated unit. Oracle Dataguard Broker stores the necessary information in a file locally on each dataguard member server. The file location is configured using following database parameters dg_broker_config_file1 dg_broker_config_file2 The content of above the file is accessed and managed by Dataguard Monitor  ( DMON ) Process. The DMON process is an Oracle background process that runs on every database instance that is managed by the broker. The start/stop of DMON process (which interns enables or disables) broker is managed by database  parameter  called dg_broker_start , the value of which is TRUE (enabled) or FALSE (disabled). The broker configuration can be queried and/or modified using Oracle