Init parameterData Guard

STANDBY_FILE_MANAGEMENT

What it controls

Whether datafiles added on the primary are created automatically on the standby.

Know this before you change it

Keep it AUTO. Set it to MANUAL only briefly, for example while changing online redo logs on a standby.

Default: MANUAL

Check and change it

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

Related scripts

• Redo apply and transport processesWhich Data Guard processes are running and what they're doing. No MRP0 row means redo is arriving but not being applied. Before 12.2, query…

Open in the parameter referenceOracle's reference

More in Data Guard

• DG_BROKER_STARTStarts the Data Guard broker process (DMON).
• 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.
• DB_UNIQUE_NAMEA name that's unique to each database in a Data Guard configuration, used by the broker, services and file naming.