Page tree

The following template types are available:

  • Add Instance
  • Apply/Remove Patch
  • Create Database
  • Create Home
  • Create RAC Cluster/Add Node
  • Create RAC Database
  • Remove Cluster
  • Remove Database
  • Remove Home
  • Remove Instance
  • Remove Node
  • Upgrade Database/RAC Cluster

About the standard variables in templates for Oracle on Linux and UNIX

The following table lists the standard variables that can be used to populate fields in the associated provisioning wizard. For example, if a cluster name is entered in step 2 of the wizard, the cluster name can appear as a selectable option or appended to an entry in another area of the wizard.

Template

Standard variable

Details

Create Cluster Template

CLUSTER_NAME

First eight characters of the BMC Database Automation cluster name.

Create Cluster Template Create Oracle Database

VERSION

Specific version, for example, 10.2.0.4.

Create Oracle Database

DB_UNIQUE_NAME

First eight characters of the BMC Database Automation database name.

Create Oracle Database

SID_PREFIX

First seven characters of the DB_UNIQUE_NAME for clustered databases and the first 8 characters for single instance databases.

Create Oracle Database

VERSION_TAG

General version, for instance, 10.2.

Create Oracle Database

VCS_RESOURCE_GROUP

The value from the VCS Cluster Group field that is collected on the first page of the create Oracle Database wizard on a VCS cluster.

Create Oracle Database

ORACLE_BASE

The ORACLE_BASE variable works for these fields only: Control File Filepath, Recovery File Destination, Audit File Destination, Background Dump Directory, Core Dump Directory, User Dump Directory, Diagnostic Directory, SYSAUX Filepath, SYSTEM Filepath, TEMP Filepath, UNDOTBS1 Filepath, USERS Filepath, and Redo Log Member Directory.

 

The following rules apply for standard variables:

  • All tags can be used for any of the elements defined after the first page.
  • Except for {DB_UNIQUE_NAME}, all tags must be in either the editable or non_editable section of the template.

Example

<editable>
  <sid_prefix>{SID_PREFIX}</sid_prefix>
</editable>

Note

If you create custom fields, they can also be used as variables in templates. To add custom fields to a template, see Adding custom fields to a template.