7.2.20 mktemplate

Create an Exascale template.

Syntax

mktemplate { --file-type file-type | --name template-name } 
           [ --vault vault | --cluster ]
           { --media-type media-type | --storage-pool storage-pool-name ] 
           --redundancy redundancy
           --content-type content-type
           [{ -w | --wallet } wallet-location ] 
           [{ -T | --trace } trace-level ]
           [{ -j | --json } [ --compact ]]

Command Options

The options for the mktemplate command are:

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

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

• --vault: Identifies the vault associated with the template being created.

• --cluster: Specifies the creation of a cluster template.

• --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.

• -w, --wallet: Optionally specifies the path to the Exascale wallet directory.

• -T, --trace: Optionally enables tracing, with the trace level (trace-level) set to 1 (minimum tracing), 2 (medium tracing), or 3 (maximum tracing). If the trace level is not specified, then minimum tracing is enabled by default.

  The trace file is written to the first accessible location in the following list:

  1. If the $ADR_BASE environment variable is set:

     $ADR_BASE/diag/EXC/xsh_<user-name>/<host-name>/trace/xsh_<date>.trc

  2. /var/log/oracle/diag/EXC/xsh_<user-name>/<host-name>/trace/xsh_<date>.trc

  3. /tmp/diag/EXC/xsh_<user-name>/<host-name>/trace/xsh_<date>.trc

• -j, --json: Displays the output in JSON format.

• --compact: Displays JSON formatted output in a compact format, without white space and line breaks.

Usage Notes

Note the following information when using this command:

• If neither --vault nor --cluster is specified, the command creates a cluster template.

Examples

Example 7-33 Create an Exascale template

The following example creates a user-defined template named my-template, which is associated with the my-data vault and contains the specified media type, redundancy, and content type settings.

$ xsh mktemplate --name my-template --vault my-data --media-type EF --redundancy high --content-type DATA