This slide explains how callout configuration scripts can be used to execute specified tasks before and after a fast-start failover operation.
Callout configuration scripts can be used to automatically execute specified tasks before and after a fast-start failover operation. The name of the callout configuration file is
fsfocallout.ora. You cannot use a different name for this file. This file is stored in the
$DG_ADMIN/config_ConfigurationSimpleName/callout directory. If the
DG_ADMIN environment variable is not defined, or the directory specified by this variable does not exist, or the directory does not have the required permissions, fast-start failover callouts will fail.
The name of the callout configuration scripts is specified in
fsfocallout.ora. These scripts must be in the same directory as the callout configuration file. You can create two callout configuration scripts, a pre-callout configuration script and post-callout configuration script. Before a fast-start failover operation, the observer checks if a fast-start failover configuration file exists. If it exists, and it contains a pre-callout script location, this script is run before the fast-start failover is initiated. After fast-start failover succeeds, if a post-callout script is specified in the fast-start failover configuration file this script is run.
VALIDATE FAST_START FAILOVER command parses the callout configuration scripts and checks for errors or misconfigurations. To perform specified actions before or after a fast-start failover operation:
- Create a pre-callout script, or a post-callout script, or both.
- Create or update the fast-start failover callout configuration file and include the names of the scripts created in the previous step.
The example above displays the contents of the fast-start failover configuration file named
fsfo_postcallout callout configuration scripts are stored in the same location as
fsfocallout.ora with the required permissions.