Init parameterData Guard

DG_BROKER_START

What it controls

Starts the Data Guard broker process (DMON).

Know this before you change it

Set it on the primary and every standby before creating the broker configuration.

Default: FALSE

Check and change it

1-- Current value on every instance2SELECT inst_id, name, value, isdefault, ismodified3FROM gv$parameter4WHERE name = 'dg_broker_start';5 6-- Value stored in the spfile7SELECT sid, value FROM v$spparameter WHERE name = 'dg_broker_start' AND isspecified = 'TRUE';8 9-- Dynamic: takes effect now and is kept after a restart10ALTER SYSTEM SET dg_broker_start = TRUE SCOPE = BOTH SID = '*';11 12-- Remove it from the spfile to go back to the default at the next restart13ALTER SYSTEM RESET dg_broker_start SCOPE = SPFILE SID = '*';

Related scripts

• Broker health checks (DGMGRL)The broker's own view of the configuration. VALIDATE DATABASE is the best single readiness check before a switchover.

Open in the parameter referenceOracle's reference

More in Data Guard

• LOG_ARCHIVE_CONFIGThe DB_UNIQUE_NAMEs of every database in the Data Guard configuration.
• FAL_SERVERNet service names a standby asks for missing archived logs.
• STANDBY_FILE_MANAGEMENTWhether datafiles added on the primary are created automatically on the standby.
• DB_UNIQUE_NAMEA name that's unique to each database in a Data Guard configuration, used by the broker, services and file naming.