VALIDATE DATABASE SPFILE

The VALIDATE DATABASE SPFILE command performs a comparison of server parameter file (SPFILE) entries between the primary database and a specified standby database.

The validation of the server parameter file detects parameter value discrepancies between the primary and the specified standby database so that they can be rectified before a role change, thus ensuring that after a role change the databases perform at the same level they did prior to the role change. Additionally, using this command frees you from having to restart a database to correct improperly set parameters.

Format

VALIDATE DATABASE [VERBOSE] <db_unique_name> SPFILE;

Command Parameters

db_unique_name

The DB_UNIQUE_NAME initialization parameter value of the standby database whose SPFILE contents you want to compare to the primary database's SPFILE contents..

If the database to be validated is the primary database, then a message is returned saying the command cannot be issued on a primary database.

If the database to be validated is a standby database, then the server parameter file values on the primary database are compared with the server parameter file values on the standby database.

Usage Notes

  • The VALIDATE DATABASE SPFILE command reports No parameter differences foundif there are no differences. If differences are found, a list of the parameters with their differing values on the primary and the specified standby databases will be displayed.

  • When the VALIDATE DATABASE SPFILE command is issued, it makes a connection to the primary database and the specified standby database based on the respective values of the DGConnectIdentifier property. The command fails if a connection attempt cannot complete successfully.

  • Use the VERBOSE keyword to see the list of the parameter settings in the SPFILE for both databases.
  • This command only checks for parameters that are set for all instance. It excludes parameters that are set for a specific instance.
    The following parameters are not checked because they are either managed by Data Guard broker or are allowed to have different values between databases:
    • archive_lag_target, log_archive_config*, db_file_name_convert, log_archive_max_processes, log_archive_min_succeed_dest, log_file_name_convert, standby_file_management, log_archive_dest_n*, log_archive_dest_state_n*, db_unique_name, asm_diskgroups, asm_diskstring control_files fal_server*, db_create_file_dest, db_create_online_log_dest_1, db_create_online_log_dest_2, db_create_online_log_dest_3, db_create_online_log_dest_4, db_create_online_log_dest_5, db_recovery_file_dest, db_recovery_file_dest_size, dg_broker_config_file1, dg_broker_config_file2, dg_broker_start instance_groups, instance_mode instance_name, instance_number, instance_type, listener_networks, local_listener, log_archive_duplex_dest, log_archive_format, remote_listener, service_names spfile, standby_archive_dest

Command Example

Example: Using VALIDATE DATABASE SPFILE to Compare Server Parameter File Values

The following is sample output from the VALIDATE DATABASE SPFILE command when there are no differences between the server parameter file values on the specified standby database and the primary database: 

DGMGRL> VALIDATE DATABASE chicago SPFILE;
Connecting to "boston".

Connecting to "chicago".

No parameter differences found.

The following is sample output from the VALIDATE DATABASE SPFILE command when there are differences (different values, or specified on one and not on the other) between the server parameter file values on the specified standby database and the primary database: 

DGMGRL> VALIDATE DATABASE chicago SPFILE;
Connecting to "boston".

Connecting to "chicago".

Parameter settings with different values:

aq_tm_processes:
boston (PRIMARY) : 8
chicago          : 9

commit_point_strength:
boston (PRIMARY) : NOT SPECIFIED
chicago          : 255

sec_max_failed_login_attempts:
boston (PRIMARY) : 2
chicago          : NOT SPECIFIED

use_large_pages:
boston (PRIMARY) : TRUE
chicago          : NOT SPECIFIED
DGMGRL>