Init parameterData Guard
FAL_SERVER
What it controls
Net service names a standby asks for missing archived logs.
Know this before you change it
Point it at the primary, and at other standbys if you have them.
Check and change it
1-- Current value on every instance2SELECT inst_id, name, value, isdefault, ismodified3FROM gv$parameter4WHERE name = 'fal_server';5 6-- Value stored in the spfile7SELECT sid, value FROM v$spparameter WHERE name = 'fal_server' AND isspecified = 'TRUE';8 9-- Dynamic: takes effect now and is kept after a restart10ALTER SYSTEM SET fal_server = 'ORCL' SCOPE = BOTH SID = '*';11 12-- Remove it from the spfile to go back to the default at the next restart13ALTER SYSTEM RESET fal_server SCOPE = SPFILE SID = '*';Related scripts
- Archive gaps and last applied sequenceMissing log sequences the standby is waiting for, then the last applied sequence per thread. Compare with the current sequence on the primary.
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.
- 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.