allocOperandList

Syntax

allocOperandList::=

Description of the illustration allocoperandlist.gif

Purpose

A subclause specifying control options on a channel, which is a connection between RMAN and a database instance. Specify this clause on the following commands:

Keywords and Parameters

Syntax Element	Description
`CONNECT` `=` connectStringSpec	Specifies a connect string to the database instance where RMAN should conduct the backup or restore operations. Use this parameter to spread the work of backup or restore operations across different instances in an Oracle Real Application Clusters configuration. If you do not specify this parameter, and if you did not specify the `AUXILIARY` option, then RMAN conducts all operations on the target database instance specified by the command-line `CONNECT` parameter or the instance connected to when you issued the `CONNECT` command. Typically, you should not use the `CONNECT` parameter in conjunction with the `AUXILIARY` option. See Also: "connectStringSpec" and "cmdLine"
`FORMAT` `=` formatSpec	Specifies the format to use for the names of backup pieces that are created on this channel. If you do not specify `FORMAT`, RMAN uses `%U` by default, which guarantees a unique identifier. If the flash recovery area is configured, then the files are created in the default disk location. Otherwise, the default disk location is operating system specific (for example, `?/dbs` on Solaris). Because the channels correspond to server sessions on the target database, the `FORMAT` string must use the conventions of the target host, not the client host. For example, if the RMAN client runs on a Windows machine and the target database runs on a UNIX machine, then the `FORMAT` string must adhere to the naming conventions of a UNIX file system or raw device. You can specify up to four `FORMAT` strings. RMAN uses the second, third, and fourth values only when `BACKUP` `COPIES`, `SET` `BACKUP` `COPIES`, or `CONFIGURE` `...` `BACKUP` `COPIES` is in effect. When choosing which format to use for each backup piece, RMAN uses the first format value for copy 1, the second format value for copy 2, and so forth. If the number of format values exceeds the number of copies, then the extra formats are not used. If the number of format values is less than the number of copies, then RMAN reuses the format values, starting with the first one. This parameter is useful if you allocate multiple disk channels and want each channel to write to a different directory. If you specify the `FORMAT` parameter in the BACKUP command, then it overrides the `FORMAT` parameter specified in CONFIGURE `CHANNEL` or ALLOCATE CHANNEL. See Also: "formatSpec" for available `FORMAT` parameters
`MAXOPENFILES` `=` `integer`	Controls the maximum number of input files that a BACKUP command can have open at any given time (the default is 8). Use this parameter to prevent "Too many open files" error messages when backing up a large number of files into a single backup set.
`MAXPIECESIZE` `=` `integer`	Specifies the maximum size of each backup piece created on this channel. Specify the size in bytes, kilobytes (`K`), megabytes (`M`), or gigabytes (`G`). The default setting is in bytes and is rounded down into kilobytes. For example, if you set `MAXPIECESIZE` to 5000, RMAN sets the maximum piece size at 4 kilobytes, which is the lower kilobyte boundary of 5000 bytes.
`PARMS` `=` `'channel_parms'`	Specifies parameters for the device to allocate. Do not use this port-specific string if you have specified `DEVICE` `TYPE` `DISK`. See Also: Oracle Database Backup and Recovery Advanced User's Guide to learn how to integrate media management libraries
`'ENV=(var1=val1,` `var2=val2`,`...)'`	Specifies one or more environment variables required by the media management vendor in the server session corresponding to this RMAN client. Because RMAN is a client program, the `ENV` parameter can be used to set server session specific variables that perform backup and restore operations on behalf of the RMAN client. For example: PARMS="ENV=(TAPE_SERVER=srv1)"
`'SBT_LIBRARY =` `lib_name'`	Specifies which media library should be used on this `sbt` channel. The default library is operating system specific (for example, `libobk.so` in the Solaris Operating Environment and `ORASBT.DLL` on Windows). For example: PARMS="SBT_LIBRARY=/oracle/lib/mmv.so"
`RATE` `=` `integer`	Sets the maximum number of bytes (default), kilobytes (`K`), megabytes (`M`), or gigabytes (`G`) that RMAN reads each second on this channel. This parameter sets an upper limit for bytes read so that RMAN does not consume too much disk bandwidth and degrade performance.
`SEND` `'command'`	Sends a vendor-specific command string to all allocated channels. See Also: Your media manager documentation to see whether this feature is supported and when it should be used.

Examples

Configuring an Automatic Channel: Example This example configures a persistent disk channel:

CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT = '?/oradata/bkup_%U';

Configuring a Channel for a Backup: Example This example manually allocates an sbt channel and then runs a whole database backup:

RUN
{
  ALLOCATE CHANNEL c1 DEVICE TYPE sbt MAXPIECESIZE 800M;
  BACKUP DATABASE;
}

Allocating a Channel for a Backup: Example This example configures a default media management library, then makes a database backup by using this library. Then, the example backs up the database again using a different library, then finally makes a third backup using the default library:

CONFIGURE DEFAULT DEVICE TYPE TO sbt;
CONFIGURE CHANNEL DEVICE TYPE sbt PARMS="SBT_LIBRARY=/mediavendor/lib/mm_lib1.so";
BACKUP DATABASE;
RUN
{
  ALLOCATE CHANNEL c1 DEVICE TYPE sbt PARMS="SBT_LIBRARY=/mediavendor/lib/mm_lib2.so";
  BACKUP DATABASE;
}
BACKUP ARCHIVELOG ALL;