6.2.9.1 chtemplate

Change an attribute for an existing template.

Purpose

The chtemplate command changes an attribute for an existing Exascale file template.

Syntax

chtemplate [ --vault vault | --cluster ] 
           { --file-type file-type | --name template-name }
           [ --media-type media-type ][ --storage-pool storage-pool-name ] 
           [ --redundancy redundancy ]
           [ --content-type content-type ]

Command Options

Specify one or more of the following chtemplate command options to identify the template that is the subject of the operation:

  • --vault: Alters a template associated with the specified vault.

  • --cluster: Alters a template associated with the cluster.

  • --file-type: Alters a template associated with the specified file type.

  • --name: Alters a user-defined template having the specified name.

Use the following command options to specify the file storage attributes:

  • --media-type: Specifies the physical media type used to store files created with the template. Possible values are:

    • HC: Identifies high capacity storage, using hard disk drives (HDDs) on high-performance Exadata storage servers.

    • EF: Identifies extreme flash storage, using low-latency, high-throughput flash devices.

    • XT: Identifies extended storage, using HDDs on Exadata storage servers optimized for cost-effective online storage of less frequently accessed data.

  • --storage-pool: Specifies the name of a storage pool used to store files created with the template.

    This option is available starting with Oracle Exadata System Software release 26.1.0, and is only permitted in conjunction with a vault template.

  • --redundancy: Specifies the number of data copies that are maintained for files created with the template. Currently, the only permitted value is:

    • high: Indicates three mirrored copies of the file data.

  • --content-type: Specifies the type of content in files created with the template. Exascale internally uses this attribute to place file extents on physically separate devices in a manner that maximizes availability in the event of a failure. Possible values are:

    • DATA: Principally associated with user data.

    • RECO: Primarily for data used in backup and recovery operations.

Usage Notes

Note the following information when using this command:

  • When a template includes a storage pool specification, it does not require a media type setting. If a storage pool and media type are both specified, the settings must be compatible. For example, a template cannot specify the use of high capacity (HC) storage media and also specify the name of a storage pool that uses extreme flash (EF) storage.

Examples

Example 6-123 Change a User-Defined Cluster-Wide Template

In this example, the content type is set to DATA for the user-defined template named T1. The template is associated with the cluster, as neither --vault nor --cluster is specified, and the current working directory in the ESCLI session is the root directory. 

@> chtemplate --name T1 --content-type DATA

Example 6-124 Change a User-Defined Vault-Specific Template

In this example, the media type is set to HC and the redundancy is set to high for the user-defined template named T2. The template is associated with the vault named vault2, as neither --vault nor --cluster is specified, and the current working directory in the ESCLI session is inside vault2. 

@vault2> chtemplate --name T2 --media-type HC --redundancy high

Example 6-125 Change a User-Defined Vault-Specific Template

In this example, the media type, content type, and redundancy are all set for the user-defined template named T3 that is associated with the vault named vault2. 

@> chtemplate --vault vault2 --name T3 --content-type DATA --media-type HC --redundancy high

Example 6-126 Change a User-Defined Cluster-Wide Template

In this example, the media type, content type, and redundancy are all set for the cluster-wide user-defined template named T4. The --cluster option overrides the fact that the current working directory in the ESCLI session is inside vault2. 

@vault2> chtemplate --cluster --name T4 --content-type DATA --media-type HC --redundancy high

Example 6-127 Change a Template for a Specific Vault and File Type

This example changes the template associated with the DATAFILE file type and the vault named vault2. 

@> chtemplate --vault vault2 --file-type DATAFILE --content-type DATA --media-type HC --redundancy high

Example 6-128 Change a Cluster-Wide Template for a Specific File Type

This example changes the cluster-wide template associated with the DATAFILE file type. 

@> chtemplate --cluster --file-type DATAFILE --content-type DATA --media-type HC --redundancy high

Related Topics

Parent topic: Template Management