Oracle Site Guard allows for custom scripts to be used during operations to perform tasks not natively supported by Site Guard.

NMS provides templates for Site Guard custom scripts in $NMS_BASE/templates. They must be installed in a common location on each NMS server or each database server, depending on the script. Scripts should be installed with .template removed from their names and made executable unless otherwise noted. Some of these scripts must be edited and others can be edited.

This must be configured to run as the user that is running the database.

Shell script that creates a guaranteed restore point in the database named “BEFORE_PATCH_NMS”. If $HOME/.profile does not set ORACLE_HOME, ORACLE_SID, and PATH such that “sqlplus / as sysdba” connects to the database, then this script must be edited to set those environment variables.

SQL script used by sg-createrestorepoint.template. Does not need to be executable.

These must be configured to run as the NMS administrative user. When Dual-Environment Configuration is used, these scripts must be configured twice – once for each environment.

Shell script that calls nms‑read‑only to turn on Read Only mode.

Shell script that calls nms‑all‑start to start NMS services and the WebLogic managed server.

Shell script that calls "nms‑all‑stop ‑fast" to stop NMS services and the WebLogic managed server.

Shell script which handles a switchover. Run from the Standby site that is becoming Primary. This:

This script must be customized to match the sites and hosts at which NMS is installed. See the comments in the template.

Other custom scripts can be added for any other business needs.