Custom Pre and Post Scripts for Exadata Patching
You can configure optional custom scripts for Exadata Gold Image Deploy and Gold Image Update operations. Select scripts for the stages applicable to the maintenance operation.
Table 18-3 Custom Script Stages for Exadata Patching
| Operation | Script Stage | When the Script Runs |
|---|---|---|
| Gold Image Deploy | Pre Deploy | Before the FPP deploy operation. |
| Gold Image Deploy | Post Deploy | After the FPP deploy operation and retrieval of its operation details and status. |
| Gold Image Update | Pre Update | Before the blackout and FPP update operation. |
| Gold Image Update | Post Update | After retrieval of the FPP operation details and status, and after the blackout has ended. |
You can configure a pre-operation script, a post-operation script, or both.
Before selecting a script, ensure that its Software Library directive meets the following requirements:
- The directive is accessible to the Enterprise Manager user submitting the operation.
- The directive contains a main executable file. If you upload multiple files, designate the driver script as the main file.
- The directive declares the command-line property
INPUT_FILE. - The script is suitable for execution on the host associated with the Exadata maintenance operation.
For instructions on preparing and uploading scripts, see Custom Script Considerations and Software Library Entity For Uploading The Script.
Enterprise Manager generates a properties file containing
maintenance-operation context and passes its absolute path to the script
through INPUT_FILE. The script can read the properties
required for its processing.
Scripts execute on the host targets associated with the operation. For compute-node maintenance, scripts run on the Exadata host. For storage-server and switch maintenance, scripts run on the Exadata host or FPP client host that drives the maintenance operation.
Scripts can run as a normal operating-system user or as root. Select Run as Root separately for each script that requires root privileges. The following credential requirements apply:
Table 18-4 Credential Requirements for Exadata Custom Scripts
| Script Configuration | Normal Host Credential | Privileged Host Credential |
|---|---|---|
| No custom scripts configured. | Not required solely for custom scripts. | Not required solely for custom scripts. |
| All configured scripts run as a normal operating-system user. | Required. | Required only if another selected feature requires it. |
| At least one configured script runs as root. | Required. | Required. |
Providing a privileged host credential does not automatically enable root execution. The Run as Root setting determines the execution mode for each script.
To configure custom scripts for an Exadata Deploy or Update operation:
- In the Fleet Maintenance wizard, locate the Custom Scripts region and click Add.
- Select the applicable Stage and choose the Software Library directive containing the script. Use Pre Deploy or Post Deploy for deployment, and Pre Update or Post Update for an update.
- Select Run as Root if the script requires root privileges. Otherwise, leave this option unselected.
- Repeat for any other applicable script stages. Provide the host credentials required by the script configuration, as described in the credential requirements table.
- On the Review page, verify the selected scripts, stages, root-execution settings, and credentials. Continue with validation and submission of the maintenance operation.
Note:
Custom scripts do not execute during prerequisites-only operations. Enterprise Manager skips the pre-operation and post-operation script stages and does not generate the custom-script input file. Script credentials are not required solely because custom scripts are configured for a prerequisites-only operation.